cancel
Showing results for 
Search instead for 
Did you mean: 

Subsequent activation of scenario FIN_CONS (no doc splitting)

Former Member
0 Kudos

Background:

We are live on New GL for a while. We use a third-party tool for consolidation. One of the custom program reads the data, and sends a file to this third party tool for consolidation. We do send trading partner information for P&L. We read the data for these GL accounts from line item tables.

We have a new requirement to send the trading partner information for balance sheet accounts. I would like to read the trading partner information from FAGLFLEXT table as opposed to reading from line item tables.

As of now, FIN_CONS was not assigned to the ledger “0L”. I would like to activate that for “0L”. I have to populate trading partner for small amount of historic data. In order to do this, I am planning to make journal entries in the current period as below

Example:

Credit GL 110000 1000$ Trading partner “Space”

Debit GL 110000 1000$ Trading partner “ABC”

also,we will clear all the inter company invoices before I move the new scenario into production.

As per SAP, we have to create a new ledger and activate the scenario for this new ledger. But I do not want to follow this approach for the following reasons:

  • 1.Our FAGLFLEXA table is huge. If I create a new ledger, the size of this table grows even more.
  • 2.Our historic data conversion is so minimal. I think we will be able to handle this easily with journal entries and clearing all the ICB invoices before we move the change.
  • 3.We are not going to activate doc splitting for this scenario.

Do you see any flaws in this approach? What would you do if you in my position?

Accepted Solutions (0)

Answers (0)