Ansicht
Dokumentation

SIMG_CFMENUMAPRLDNR - Define Group Reporting Preparation Ledgers

SIMG_CFMENUMAPRLDNR - Define Group Reporting Preparation Ledgers

rdisp/max_wprun_time - Maximum work process run time   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.
SAP E-Book

Define a group reporting preparation ledger by creating a group reporting preparation ledger configuration for an accounting ledger.

You can define an accounting ledger as a group reporting preparation ledger. This is done by creating a group reporting preparation ledger configuration for an accounting ledger. In addition to defining an accounting ledger as a group reporting preparation ledger, this configuration contains settings used to derive consolidation-relevant information during accounting postings in the accounting ledger.

Verify that the From Year for Group Reporting Preparation Ledgeris set to a specific year in the customizing activity Check Global System Settings. The integration with group reporting preparation ledger is only active in or after this from year.

Verify that the From Year for Group Reporting Preparation Ledgeris set to a specific year in the configuration step Check Global System Settings. The integration with group reporting preparation ledger is only active in or after this from year.

  1. Create a Ledger Mapping Configuration ID as the name of the group reporting preparation ledger configuration. This just serves as a technical name and isn't used outside of this customizing activity. 
  2. Select an accounting ledger that you want to define as a Group Reporting Preparation Ledger. This activates the derivation of group reporting fields in the group reporting preparation ledger. 
  3. Select the Consolidation COA. The value you select is automatically used in accounting postings and determines the FS item values that can be derived during accounting postings.
  4. Optionally, you can assign an FS Item Mapping Version to the group reporting preparation ledger. This is only necessary if you want to use the standard G/L account - FS item mapping from group reporting to derive values for FS item fields during accounting posting. If you don’t want to make use of this, FS items can be derived during accounting posting based on substitution rules.
  5. Optionally, you can assign an FS Item Attributes Version to the group reporting preparation ledger. In general, this is used to make time- and version-dependent FS item master data attributes available for substitution and validation rules in accounting. One practical example for this is the FS item role attribute values S-NOMAPB/S and S-NOMAPP/L. When deriving FS items during accounting posting, the system checks if there are any empty fields for FS items. This is because empty fields for FS items result in errors. If there are empty fields, a substitution rule automatically fills them in with the FS item that’s assigned with the role S-NOMAPB/S (for balance sheet FS items) or the FS item that’s assigned with the role S-NOMAPP/L (for profit and loss FS items) so that the postings can be executed successfully. Afterwards, journal entries can be easily identified where a proper FS item must still be derived. To enable the system to derive the relevant FS items for this substitution based on their time- and version-dependent FS item role attribute assignment, you must assign the relevant FS Item Attributes Version to the group reporting preparation ledger. 
  6. Click Save.

Note:

Each group reporting preparation ledger can only have one corresponding consolidation COA. However, a single consolidation COA can be assigned to more than one group reporting preparation ledger.

Note:

Extension ledgers may also be defined as group reporting preparation ledgers. However, they must be maintained in accordance with their corresponding underlying ledger. In other words, an extension ledger must have the same consolidation COA assigned as its underlying ledger. Also, an extension ledger's entry as a group reporting preparation ledger must be deleted if its corresponding underlying ledger's entry is deleted.

If you need to make corrections to the opening balance of a new fiscal year, you cannot do so directly on the subitem used for the opening balance (Carryforward Subitem). This is because the opening balance of the new fiscal year must exactly match the end balance of the previous fiscal year.

Instead, you can assign a Carryforward Reclassification Subitem to a Carryforward Subitem. To do so, follow these steps:

  1. Select the entry of a group reporting preparation ledger.
  2. Navigate to Opening Reclassification Subitems in the dialog structure and select New Entries. 
  3. Select the Ledger Mapping Configuration ID of the preparation ledger.
  4. Select the Subitem Category. This subitem category contains the subitems used to categorize values recorded on FS items for the opening balance in balance carryforward.  
  5. Select the Carryforward Subitem. This subitem is used for the opening balance that you want to make corrections to.
  6. Select the Carryforward Reclassification Subitem. This subitem is used for corrections that adjust the values of the opening balance. By using this subitem for corrections instead of the Carryforward Subitem, the corrections appear as separate entries. This way, the opening balance on the Carryforward Subitem still matches the end balance, but the values of the opening balance can still be adjusted thanks to the corrections made using the Carryforward Reclassification Subitem.
  7. Click Save.

Note:

It's possible to create multiple entries for the same group reporting preparation ledger in case you have more than one Carryforward Subitem.

More Information

Search for SAP S/4HANA on the SAP Help Portal. Then, in the Product Assistance, under Finance, search for Group Reporting Preparation Ledgers.






TXBHW - Original Tax Base Amount in Local Currency   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 7099 Date: 20240523 Time: 180017     sap01-206 ( 158 ms )