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: 
Former Member

My previous posts on S/4 HANA migration

  1. Getting Ready for SAP S/4 HANA

  2. Migrating to S/4 HANA - Installation and Customizing

This post gives an overview of Universal Journal, activities related to migration and post migration while converting SAP ECC systems to SAP S/4.

Universal Journal Entry

The Universal Journal Entry combines the documents from FI (Finance Accounting) and CO (Managerial Accounting) and stores them in a single table ACDOCA. The Universal Journal Entry table becomes the single source of truth and eliminate the need for most of reconciliation between FI and CO.

Complete details of Universal Journal Entry can be found in SAP Help Portal.

  • Partitioning ACDOCA is must if the total number of records exceeds 2 billion. SAP best practice partition size recommendation is 300 to 500 million records

  • Secondary Cost Elements are migrated as Secondary Cost GL accounts

  • Merging the Cost Elements and GL accounts requires manual changes to authorization as this is NOT done automatically during migration

  • "Analyze Transactional Data" checks all documents are complete and correct. Any inconsistencies should be cleaned before migration. If the inconsistency is not relevant anymore, it can be ignored

  • "Reconcile Transactional Data" checks the following

  1. Zero balance compliance

  2. All line items have header data

  3. Documents have same amount in BSEG and new GL table FAGLFLEXA

  4. New GL secondary index table FAGLBSIS, FAGLBSAS are checked with Accounting Document for Additional Ledgers (BSEG_ADD)

  5. Database views for index tables return the same values as backup tables *_BCK

  6. CO documents have their corresponding header data

  • Data enrichment is done between line item tables and header tables

  • "Check of Migration Documents" check all documents are enriched correctly

  • The data enrichment followed by checking the data should be done even for the clients that do not have transaction data

Migrating to new structure / Filling the ACDOCA Table

The transactional data from the applications FI, FI-GL, FI-AA, CO, ML are combined and enhanced by the characteristics of account based CO-PA (if used) in Universal Journal Entry and there is no change to BSEG

FI and CO documents can possibly have 1:1, 1:N and N:M relationship. The migration of 1:1 and 1:N are somewhat straight forward. Migration of N:M can get complected depending upon the number of FI and CO documents

Migration of Balances

  • For FI balances, delta values from ledger totals, line items of BSEG and line items of FAGLFLEXA are considered

  • Delta of the CO totals to the line items and the aggregated values of line items are considered for CO balances

  • Only the balances are migrated for material inventory totals

  • If there is difference between sum of line items and balances carry forwarded, the "Migrate Balance Activity" posts the delta values at GL total level. This balance adjustment combined with line items migrated will match the original values

Should there be any errors during migration, the following programs can be used to reset the migration to prior state.




Refer the OSS Notes 2138644 and 2270540 to get more information on migration reset

The IMG activity "Check Migration of Accounting Documents to Universal Journal Entry" checks if all documents are migrated correctly. For example, CDS views on FAGLFLEXA is checked against the FAGLFLEXA_BCK table

The calculation of planned depreciation works as before. The new program FAA_DEPRECIATION_CALCULATE is used for recalculation. Please note that it is important to run this program prior to first depreciation run.

Post Processing

Once the migration is completed, following activities need to be completed before releasing the system to regular production use. These activities can be done after the migration is set to complete.

  • CVI number range which was set to external during migration need to be changed as internal.

  • IMG activity "Transfer Application Indexes" is performed for Data Aging (cold storage of index data), for example, BSIS_BCK, BSAS_BCK, BSID_BCK, etc... This requires the business function DAAG_DATA_AGING.

  • IMG activity "Fill Due Dates in FI documents" calculates the net due date and discount due date and stores them in BSEG, BSEG_ADD, VBSEGD, VBSEGK and VBSEGS tables.

  • Offsetting Account Type, Offsetting Account Number, G/L Account of Offsetting Account are filled with the activity "Fill The Offsetting Account in FI Documents".

There are programs/transactions to monitor all the migration and post processing activities. The logs needs to be checked thoroughly as the migration activities will NOT stop if there is an error. The errors will be logged and migration continues. For this reason, it is important to check the migration logs.

It is important to check the report snapshots before and after the migration by stakeholders to make sure the migration is completed successfully.
Labels in this area