SAP Note 10817 - CCA planning: No planning documents posted to FI-SL

Symptom

Key word: Planning, transfer of planning data, through-posting of
planning data. Program: SAPMGPLV
Planning data from cost center accounting is not transferred to the profit center accounting (online or afterwards).
Planning documents as well as documents planned manually that are created by transaction KP96 'Activate Line Items and Planning
integration' are not posted to FI-SL.

Cause and prerequisites

FI-SL settings are not maintained correctly.

Solution
Transaction GCD1 (Diagnosis) can be used to check the through-posting for CO documents:
o Troubleshooting
With function "Troubleshooting", you can check among other things, why a certain Ledger was not posted to for a certain document.
o Direct posting statistics
With function "Direct posting stat.", you can check which Ledgers were posted to by a certain document.
o Posting test
With function "Posting test", you can output a list of the Ledgers which would be posted to for a certain planning transaction.
The planning transactions must be specified as follows:
RKP1 CO Primary cost planning
RKP2 CO Activity type planning
RKP3 CO Activity input
RKP4 CO Statistical base planning
RKP5 CO Revenue planning
RKP6 CO Activity-dependent primary cost planning
RKP7 CO Activity-dependent activity input planning
RKP8 CO Job costs
RKP9 CO Planning of activity-dependent job costs
RKPW CO Planning of secondary job costs
RKPX CO Activity-dependent secondary job cost planning
In addition, you also have to specify fiscal year, From period, and planning version. The Ledger selection requirements must be met to post to the Ledgers.

The CO planning version for the Ledger to be posted to must also be created in FI-SL for company code and fiscal year. Check with transaction GCP3 (Local Fiscal Year-Dependent Version Parameters).

The most important requirement for the through-posting of the planning documents is that the planning transactions are assigned to company code and Ledger (check with GCL3 'Display Ledger').

If yout try to activate the planning data integration a second time, the following message is displayed:
GPE636 Planning data integration already active for version .../../...
With the report below, you can reset the 'Planning data integration' indicator for a certain planning version/fiscal year:

REPORT ZZRWINKZ.
TABLES: TKA07.
UPDATE TKA07 SET RWINKZ = SPACE
WHERE KOKRS = 'XXXX' "<*** XXXX = Controlling area
AND VERSN = '000' "<*** 000 = Planning version
AND GJAHR = '1994'. "<*** 1994 = Fiscal year

Then you can restart transaction KP96.