With this blog I will be writing a sequence of few blogs in which i will cover the details of end to end process of initial load. Here is the table of content and I will update the link of each time I write about the topic.
- Introduction to Initial Load (this blog)
- Activities to be done prior to Initial Load – CLICK HERE !!!
- Initial Load planning & Sequencing – CLICK HERE !!!
- Execution of Initial Load – Simulation postings – CLICK HERE !!!
- Execution of Initial Load – Actual Posting – CLICK HERE !!!
- Post Initial Load Activities – CLICK HERE !!!
(I will be covering configuration and execution process with screenshots and more detailed. Above links will be activated as blog is published)
Introduction to Initial Load
During any SAP Central Finance project when the organization need the data of the past financial period(s) to be available in the Central System. This is generally being seen due to the reporting requirements. Let’s take an example:
- SAP Central Finance going live in August 2020
- Fiscal Year of the Organization is Jan-Dec
- Scope includes 4 SAP ECC systems (for now to simplify the explanation)
- Now when the Go Live happens on 1st August 2020 reporting requirement is to have the data for the whole fiscal year in one system to run the financial year reporting.
- In this case the initial load duration is from 1st Jan 2020 to 31st July 2020
- From August 1 the replication will start in central system
- So at the end of the year the central finance system will have the data for 1st Jan 2020 to 31st Dec 2020 for reporting purposes.
Now I am sure there will be a question in your mind that of the go live is planned for January 1 then do we need to run the Initial Load?
Answer is YES & NO but now you are thinking why when I don’t want to carry the data from past year.
From functional standpoint the answer is NO as you don’t need to take data from past year to the central system but from technical standpoint the answer is YES as to enable replication of data starting January 1 the technical step of running initial load is needed which is generally known as – EMPTY INITIAL LOAD. This will not take any data from past year or period to central system, but will help to meet system technical requirement to start the data replication.
(Difference between Initial Load and Replication to be detailed out separately in the subsequent blog – Initial Load planning & sequencing)
What data objects are considered as Initial Load?
- Accounting Documents
- Changes to accounting documents
- CO Secondary documents
- Cost Objects
- Profit Center Accounting
- Project System Master Data
- Commitment Documents
- Activity Rates
- Material Cost Estimates
(settings and process of replication will be covered in the subsequent blogs as mentioned in content section)
Don’t be as happy as there are several things which SAP Central Finance cant replicate (this is valid till SAP S/4HANA 1909 FPS1 release & may not be a valid statement in future)
- Sample Documents
- Recurring Postings
- Asset Accounting documents as Sub Ledger (Very important to understand the impact and while designing the overall architecture)
- Parked items
- Balance Carry forward items and few more that are not very much important considering the product scope.
Hope it helps you to understand what is actually Initial Load..
A Quick overview video:
Next blog – Activities to be done prior to Initial Load
Stay tuned, enjoy reading and let me know if you want any topic to be added.