Symptom
Implementation Status consistency
Environment
SAP S/4HANA Public Cloud Edition
Resolution
- If Implementation status of accounts are set to I only in the Test system or the Production system then the sequence of steps below cannot be carried out. Please raise a ticket on component FI-GL-GL-N-2CL to correct.
- If you have not accessed any GL account configuration app since the upgrade to 2502, please open either apps Manage G/L Account Master Data or Manage Operating G/L Accounts to initialize the implementation status values of the accounts in each system (i.e. Customizing, Test and Production)
- In one of the G/L configuration apps listed above, maintain the correct G/L Implementation Status property for your accounts.
Please note that changing the implementation status P requires that there is no transactional data on the account in question.
Any status other than "P" (Productive Use) will make sure that the G/L account is not transported to the next systems, and the G/L Account will also lose any Financial Statement Version assignments.
If there is transactional data preventing you from maintaining the correct implementation status please go to step 5. - After configuring the implementation status of your account to "P" and transporting the configuration to Test and Prod, you can re-assign your G/L Accounts to the hierarchy, deactivate and then activate your hierarchy in Manage Global Hierarchies app and transport the re-activation.
- If you are not able to correct the implementation status of your accounts, please raise a ticket on component FI-GL-GL-N-2CL.
Keywords
KBA , FI-FIO-GL-MD-2CL , Master Data Apps (Public Cloud) , Problem
Product
SAP S/4HANA Cloud Public Edition all versions
SAP Knowledge Base Article - Public