Ansicht
Dokumentation

FINS_BCF_DOCU - Information: Enrichment of Balance Carryforward

CPI1466 during Backup   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

This document describes the procedure for when you want to enrich the balance carryforward.

Enrichment of the balance carryforward is an optional step as part of the migration to SAP S/4HANA. This step can be carried out any time after the balances have been migrated, even after the system migration is complete. You do not need to schedule any downtime. However, all posting periods of previous years must be closed.

During the system migration to SAP S/4HANA, the balances from the existing system have been transferred from the various applications. The collective balance carryforward is then generated from the balance carryforwards of General Ledger (GL), Asset Accounting (AA), and (if necessary) Material Ledger (ML) or Materials Management (MM). The granularity of the balance carryforward is determined by the granularity in the source system and does not increase for future years.

The balance enrichment recalculates the balance carryforward for accounts that are managed on an open item basis from the open items for the corresponding key date. This is possible because, in this case, the balance must be explained from these documents, provided they have not already been archived. For all other accounts, an opening balance is always required. Note that only documents from the database can be used. All documents that were open on the corresponding key date must still exist in the database and must not have been archived or deleted.

Because the items have the full granularity, you can execute the following Customizing activity to increase the granularity settings for the balance carryforward. The enriched balance serves as the opening balance for future balance carryforwards, which means that the increased granularity is available from this point.

To enrich the balance carryforward, proceed as follows:

1. Execute Customizing activity Make Settings for the Enrichment of Balance Carryforward. Check whether all of the documents required still exist in the database for all years for which you want to perform an enrichment. Your archiving strategy for archiving object FI_DOCUMNT is relevant, and in particular the account type life, which checks against the clearing date.
2. Execute Customizing activity Reconcile Enriched Balance Carryforward. This activity checks whether the balance carryforward corresponds to the total of the open items, on the basis of the previous granularity. If you have already archived documents that were open on the key date, the system issues error messages in this step.
3. Execute the Customizing activity Display Status of Reconciliation of Balance Enrichment. In this activity, you can monitor the reconciliation status and display the calculated reports.
4. Execute Customizing activity Enter Detail Specifications for Balance Sheet Accounts. In this activity, you define the granularity for all balance carryforward accounts.
5. Execute Customizing activity Enrich Balance Carryforward Based on Open Items. In this activity, the balance carryforward is recalculated from the open items.
6. Check the result in Customizing activity Display Balance Enrichment Status. In this activity, you can monitor the enrichment status and display any reports.
7. As you have changed the detail specifications of the balance sheet accounts, the granularity of the data has been changed. Consequently, execute Customizing activity Reconcile Enriched Balance Carryforward.
8. Check the result in Customizing activity Display Status of Reconciliation of Balance Enrichment. In this activity, you can monitor the reconciliation status and display any reports.

For additional information, consult the documentation for the relevant activity.

Fill RESBD Structure from EBP Component Structure   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 4373 Date: 20240523 Time: 201242     sap01-206 ( 85 ms )