3491849 - The number of G/L accounts replicated using the "Replicate G/L Accounts" outbound service is smaller than the G/L accounts selected - SAP S/4HANA Cloud Public edition

You are replicating General Ledger accounts to a target system (for example, a CIM system) using the communication scenario SAP_COM_0179 (Finance - Accounting Master Data Integration) and outbound service CL_FINS_DRF_ARIBA_OUTB_GLACC_SPRX (Replicate G/L Accounts). You find that the number of G/L accounts selected in the log in the output of the replication is greater than the number of G/L accounts that appear to have been replicated on the target system (CIM, Ariba etc)

SAP S/4HANA Cloud Public edition

This apparent mismatch between GL account numbers when comparing the number of accounts on the S4 side to the number of accounts appearing on the CIM side is usually related to a usability issue in the log of the replication.

While the number of G/L accounts selected and replicated is usually accurate and based on selections and specific rules, it is required to make some deeper analysis on the list of accounts in order to understand exactly why some accounts were not replicated. 

There are two filter levels in outbound service CL_FINS_DRF_ARIBA_OUTB_GLACC_SPRX...

• The first filter level provided by the replication framework allows the end-user to restrict the G/L accounts to be replicated directly. That is to say, it allows you to restrict the replication to individual company codes by filtering. If it is clear from the outset that only very few G/L accounts are to be used in the target system, you can replicate these small number of G/L accounts precisely for instance.
  The result of this filter level is visible in the log of the replication.

• The second filter level, which is hard-coded and cannot be influenced from a user standpoint, filters out all G/L accounts that cannot be entered manually in procurement business processes. This was strategically decided because this outbound service was developed for target products that run procurement-like business processes and the list G/L accounts filtered out are not required in such target products.
  Unfortunately, the result of this second filter level is not visible in the log, which can lead to confusion.

Referring to the second filter level, please check the G/L account master data in app 'Manage G/L account master data' for the accounts in question.

The following list are the additional filter criteria for the second filter level that cannot be influenced....

The G/L account:

• Must not be blocked for posting (at company code level ie. skb1);
• Must not be blocked for planning (at chart of accounts level ie. ska1);
• Is not a reconciliation account for customer;
• Is not a reconciliation account for suppliers;
• Is not a reconciliation account for fixed assets;
• Is not a reconciliation account for tax;
• Is not a reconciliation account for cash;
• Allows cost object assignments;
• Is allowed to be posted manually.
• Is Primary cost element Or B/S account 

Each account will go through the combination of checks above and will be automatically filtered out of the replication if any combination of checks fail. 

G/L Account replicate, SAP_COM_0179, CL_FINS_DRF_ARIBA_OUTB_GLACC_SPRX, Accounting Master Data Integration, Ariba Fieldglass, ACDOCA, SKA1, SKB1, Manage G/L Account Master Data App , KBA , FI-GL-GL-N-2CL , Master Data (Public Cloud) , S2P-CIM , SAP Ariba Central Invoice Management , Problem