Enterprise Resource Planning Blogs by Members
Gain new perspectives and knowledge about enterprise resource planning in blog posts from community members. Share your own comments and ERP insights today!
Showing results for 
Search instead for 
Did you mean: 
Active Participant

Until now, we are clear what Initial load is and why it is needed along with what are the limitations from functional standpoint.

In this blog, we will focus on how Initial load can be planned and activities can be sequenced. It is important for both Functional consultants & Architects along with the program PMO to understand what it takes to complete an initial load.

Lets list of the activities involved in Initial Load and what can be the possible sequence based on functional and technical dependency. I will add disclaimer as needed in each step. It is assumed before starting this process that master data loads and mappings are completely updated in the Central Finance system for the relevant objects like GL Accounts, customer, vendors, WBS Elements, activity type, payment terms, Profit Centres etc.

Below are the Objects/data, which are considered as part of SAP Central Finance Initial Load:

  • Order Master Data (AUFK Table in SAP ECC)

  • Financial Accounting documents or Primary postings (BKPF/BSEG table in SAP ECC)

  • Controlling Documents or secondary postings (COBK table in SAP ECC)

Sequence of Objects load: It should be executed in same order

  1. Order Master Data (AUFK Table in SAP ECC)

  2. Financial Accounting document or Primary postings (BKPF/BSEG table in SAP ECC)

  3. Controlling Documents or secondary postings (COBK table in SAP ECC)

More clarity of per objects details:

  • Object – Order Master Data

  • Technology for load – SLT

  • Source Table – AUFK

  • Error Management – AIF


  • Object – Financial Accounting documents

  • Technology for load – RFC

  • Source Table – CFIN_ACCHD (created via implementation of CFIN notes)

  • Error Management – Mass Error management


  • Object – CO Secondary Documents

  • Technology for load – SLT

  • Source Table – COBK

  • Error Management – AIF


Sequence of activities for Initial Load based on which Planning needs to be done:

  1. All configuration is Complete

  2. All Master data loads and mapping is complete

  3. Load & replication objects are defined

  4. Mapping test is done

  5. Run the smoke test for Cost Objects via – CFIN_CO_SIMU

  6. AUFK load Execution

  7. Error resolution related to Order Master Data (in AIF under /FINCF for interface CO_OBJ)

  8. Checking the load and mapping in assignment table – FINS_CFINT_ASGMT

  1. Update Configuration in source system in view - VCFIN_SOURCE_SET

    1. Add the right company codes

    2. Add the period for which data needs to be loaded from source to CFIN

  2. Complete CO Preparatory Activities in transaction - CFIN_CO_INIT_PREP

  3. Smoke test for CO Documents with transaction - CFIN_CO_SIMU

  4. Run Extract for FI documents – In this step system picks the Accounting documents from source tables and park it in CFIN_ACCIT table (details will be covered in another blog)

  5. Complete Simulation postings and error resolution

  6. Complete Actual Initial Load & error resolution

  7. Complete CO Initial Load and error resolution in AIF


Key Activities in Source system:

  1. First and the foremost activity is to ensure source system is sufficient in terms of resources like Memory, DB, SAPS and workload analysis is done along with the assessment and optimization of any custom programs written

  2. RFC connectivity is complete

  3. SM30 > VCFIN_SOURCE_SET is updated

Considerations for Planning:

When Initial Load is planned, below needs to be considered:

  • It should not be executed during the Month end window (like 25th of the month to 5th of next month) as Initial load puts a huge load on system and during MEC/PEC the system is already loaded with business critical tasks

  • Error resolution should be planned with due time. Simulation of load and error resolution will be for sure done several times so it is important that good amount of time should be given depending on the size of the company code in source system. Like for a good amount of data we need to plan around 4-5 days per company code

  • Initial load should not be run in parallel for multiple company codes. Depending on the system capacity 2-3 company codes can be planned at same time but if all those are in same source system so the count should not go more than 2 under any circumstances

  • Any activity listed about should not be run in parallel. It is wise to plan in a sequential way to avoid system performance issues

  • Monitoring should be done during the load period by the basis expert for system performance, logs, memory, db etc

  • AIF Errors should not be reprocessed in mass at the same time. Like customer process 30000 AIF messages in one go and system run down as each AIF message consumes system resources

  • For AUFK and COBK at least 2 background processes and for FI Initial Load at least 10 background processes should be reserved in source system


Next Blog - Simulation of Initial Load Errors


Happy reading...
Labels in this area