Introduction
SAP S/4HANA for Central Finance divides the process of data replication into 2 parts;
The first part is the initial load step and the second part is the real time replication step. Initial load step replicates existing data in the source system. Then real time replication step replicates all new created data and also changes existing data in the source system.
There are preparation steps for all these processes that are mentioned above. This post explains the steps in the initial load of FI/CO Postings.
1. General Preperations
Before you start the initial load, necessary settings in Central Finance System must be carried out. Master data maintance, key mappings and value mappings, Central Finance FI/CO configurations, initial load of cost object, steps have to be completed.
2. Configuration in Source System
For each company code you want to transfer from source SAP System, all the settings must be done in view VCFIN_SOURCE_SET. As a summary, in this table; the level of detail of the data that you want to transfer in to the Central Finance System is determined. You can maintain VCFIN_SOURCE_SET, directly from transaction SM30.
3. Initial Load Configurations in Central Finance System
Activate the Business Function "FINS_CFIN", under "Enterprise Business Functions":
4. Initial Load Settings
Following settings must be completed in Central Finance System
Choose Logical System
Define Clearing and Substitution Accounts
The migration clearing account and the substitution accounts to be used for the postings during the initial load need to be configured as seen below
Define Initial Load Groups
There are two existing options for posting and simulation execution of the initial load;
- Initial Load Execution for All Company Codes
- Initial Load Execution for Selected Company Codes
5. SLT Configuration for FI replication
In the SAP LT Replication Server Cockpit;
- Define replication objects for table CFIN_ACCHD
- Start Triggers
- Keep Replication Off
6. Execute and Monitor Initial Load
The Initial Load of FI/CO posting uses MDF (Mass Data Framework). The process is completely triggered from the Central Finance System.
Following steps need to be executed in sequence shown in the table below to complete the initial load.
| Sequence No | Step |
| 1 | Start jobs for extraction of data for initial load* |
| 2 | Monitor status of data extraction (until finished) |
| 3 | Start jobs for (delta) extraction of data for initial load (after 1+ day) |
| 4 | Monitor status of (delta) data extraction (until finished) |
| 5 | Set “Initial Load Finished“ flag for resp. comp. codes (source system) |
| 6 | Start jobs for mapping simulation on extracted data |
| 7 | Monitor status of mapping simulation (until finished) |
| 8 | Create list of aggregated messages from mapping simulation |
| 9 | Analyze and resolve causes for errors |
| 10 | Start jobs for posting simulation on extracted data |
| 11 | Monitor status of posting simulation (until finished) |
| 12 | Create list of aggregated messages from posting simulation |
| 13 | Analyze and resolve causes for errors |
| 14 | Start jobs for posting extracted data |
| 15 | Monitor status of posting extracted data (until finished) |
| 16 | Create list of aggregated messages from posting |
| 17 | Analyze and resolve causes for errors |
| 18 | Start initial load/realtime replication for all comp. codes (table CFIN_ACCHD) |
Below you can see the detailed screens belonging to the steps mentioned above;
6.1. Extraction
Transaction: FINS_CFIN_LOAD_GRP_E - Execute Initial Load by Load Group
Extraction run transfers the FI documents to the Central Finance System in intermediate database tables. Extraction run prepares the upload of the FI documents from the Source SAP System to the Central Finance System.
6.2. Monitor Data Extraction
Transaction: FINS_CFIN_LOAD_GRP_M - Monitor Initial Load by Load Group
In this step you can monitor the progress of the extraction run as follows;
When you see the process status finished, you can move on to the delta extraction step.
6.3. Delta Extraction
Transaction: FINS_CFIN_LOAD_GRP_E - Execute Initial Load by Load Group
Once the extraction process is complete, you must always start the extraction again in delta mode, because there is a possibility that not all the documents are selected in the first run.
6.4. Set “Initial Load Finished“ flag in source system
After the extraction step is completed, set “Initial Load Finished“ flag in the VCFIN_SOURCE_SET table in the Source System.
6.5. Simulation Runs
Transaction: FINS_CFIN_LOAD_GRP_E - Execute Initial Load by Load Group
Mapping Simulation: Missing mappings can be monitored before starting the actual initial load.
Posting Simulation: All the error messages that are due to missing mappings, customisations or master data can be monitiored/analyzed and related causes for these errors can be resolved.
6.6. Monitior Simulation Runs
Transaction: FINS_CFIN_LOAD_GRP_M - Monitor Initial Load by Load Group
This screen displays the estimated completion time and, number of packages according to their status such as unfinished, finished..
This screen displays a list of the errors by grouping and you can select the errors displayed by double clicking on the error messages as shown below;
Once you select a message class as shown above and click on the “Show Detail” button, you can see the list of messages with their corresponding example packages
Example Package: OS4HCLNT1001000202000005360950000532766
O + S4HCLNT100 + 1000 + 2020 + 0000536095 + 0000532766
Package Type + Logical System + Source Comp. Code + Fiscal Year + Source Doc. Number Range
6.7. Post and Simulate Initial Load
Transaction: FINS_CFIN_LOAD_GRP_E - Execute Initial Load by Load Group
You can begin the start posting step for the extracted data.
Transaction: FINS_CFIN_LOAD_GRP_M - Monitor Initial Load by Load Group
You can monitor the status of the postings until the completion of initial load and resolve causes of the errors
When all the error messages are resolved, you will see the “Referenced document/invoice not yet posted” error messages as seen in the screen below therefore, start posting step needs to be run repeatedly until these error messages disappear.
After all the Referenced document/invoice not yet posted” error messages are resolved and the error message count is zero as seen in the table below, initial load data has been completed successfully.
7. Start SLT Replication
In the SAP LT Replication Server Cockpit (SLT), real time replication must be started for table "CFIN_ACCHD" via transaction code "LTRC".
Conclusion
In this blog post, the preparation steps, execute and monitor the initial load of FI/CO postings are explained with detailed screen shots. Hope this post will be useful for following the steps during initial load execution.
[https://help.sap.com/doc/a9616f4a29354fc297c58499b754e3f8/1909.latest/en-US/loio4857c0540cf5ef05e100...]
- SAP Managed Tags:
2 Comments
