The CO planning data is not posted directly to the Special Purpose Ledgers even though the relevant activities have been assigned to a ledger.
Planning data is only transferred if the plan version is also allowed in the Special Purpose Ledgers.
If a version is not allowed, the system does not return an error message because it would not otherwise be possible for specific ledgers to accept data for specific plan versions only.
Example:
Ledger Z1 should store planning data with version 002 and ledger Z2 should store planning data with version 003. The same activities have therefore been assigned to both ledgers.
If CO now transfers planning data with version 002, the system would issue an error message for ledger Z2; with version 003, the system would issue an error message for Z1.
In addition, integrated planning must have been activated in CO.
You should maintain the settings in FI-SL Customizing so that the plan versions transferred from CO are allowed in FI-SL.
To do so, call up the following menu options:
Planning -> Plan versions
The plan version transferred from CO must be assigned to the ledger that is to store the planning data.
Planning -> Version parameters -> Local/global
Here you must maintain the ledger/version/company code/fiscal year assignment accordingly. If you want to write line items when the data is transferred to FI-SL, you must set the appropriate indicator.
If you want line items to be written when the planning data is transferred, you must also perform the following step:
Planning -> Activate line item -> Local/global
Here you can activate the line item update at ledger/version/ company code/fiscal year level.
Afterwards, you must then activate the plan integration in CO.
Cost center acctg -> Planning -> Planning aids -> Plan version ->
LIs and integration
Here you can activate the plan integration for each controlling area/version and fiscal year.
Additional key words
Planning data, direct posting
No comments:
Post a Comment