3748845 - The difference of data change storage behavior in "Synchronize G/L Account Master Data" app between systems - SAP S/4HANA Cloud Public edition

The  "Synchronize G/L Account Master Data" app in Production system, only current changes are visible instead of historical change records are maintained in Test system. 

SAP S/4HANA Cloud Public Edition

1. Open the "Synchronize G/L Account Master Data" app in Test system.
2. Observe that a long list of historical change entries is displayed rather than only current changes in Production system.

The "Synchronize G/L Account Master Data" app writes changes into staging area tables (SKA1_SA , SKB1_SA, SKA_ISMT_SA,...) before they are committed to the real database. 

Once the syn app is executed in the target system (Production), staging records are processed and written into the real database with full G/L Master save validation checks. Successfully processed records are then removed from the staging area. 

Records that are un processed or failed validation remain in the staging area and continue to appear as "history" within the app. 

This is system standard behavior. 

synchronize g/l account master data, history, staging area, clear staging area tables, g/l account, master data sync, higher system, test system, unprocessed entries, faulty entries, history changes.  , KBA , FI-FIO-GL-MD-2CL , Master Data Apps (Public Cloud) , Problem