SAP Central Finance – Improvements 2022

As the Central Finance product is evolving, its also improving. This blog will focus on some latest additional capabilities being available now. Most of them are improvements to the existing functionalities.

Lets discuss each of them in detail.

Mass Update of Cost Objects

When the Initial Load of Order Master data is done via SLT from ECC to CFIN the order status is always set to Released so that the transaction data can be posted.

With this new feature the status of orders can be synced to the real status between source and target. Here system will read the status of objects in source system and will update the target system accordingly. The processing results will be available in AIF under CO-OBJ interface. This is only supported where mapping cardinality is 1:1 only

Central Payment – Flexible Activation

With the latest release the Central Payment can be activated with flexible options. Till now it was applicable for all receivables and payables  – Third Party and Intercompany, but now Central Payment can be activated for Intercompany only and leaving the third party payments still in ECC within same company code.

source – SAP.com

Architecture

This feature calls for additional need for trading partner consistency check. Trading partner can be assigned to customer/vendor master data and is then populated to the corresponding AP/AR line items. However, the trading partner in an AP/AR line item is mapped during replication but is not derived again from customer/master data in the Central Finance system. This can lead to a different trading partner assigned to the line item compared to the trading partner used in the customer/vendor master data in the Central Finance system

Transaction CFINIMG: Central Finance: Target System Settings -> Settings for Accounting Document Replication-> Activate Trading Partner Consistency Check for Source Company Codes

If data is not correct then below error may occur

 Consistency Check for Document types

When a customer have many ECC systems as source systems then the document type setup may be different as its built over a period of time. Till now the difference was only visible when transaction data is posted but now the consistency check for document type is also available which will compare the document types between source and target based on mappings

Comparison Reports enhancement

Standard SAP provides the comparison reports where data from source and target can be reconciled. It was not catering to the below:

• Accounts to Ledger Conversion
• Temporary Postings

Now this is supported. Lets read in more details

In the comparison report we have the option to display which the mapping of source GL to target ledger. This table is maintained during implementation for right ledger determination but now this table is actually used by accountants too

Comparison reports have option to select/deselect the temporary postings which may be the result of the AIF error messages. Want to know more about Temporary postings – CLICK HERE

IDR for Cloud Systems

With latest version SAP support the IDR for source cloud based systems. Till now this feature was not available. Want to know more about IDR – CLICK HERE

Permanent Consistency Check

Till now the consistency check was more of a project activity and was done during the test cycles in project. But now this is also relevant for post go live scenarios as data is changing in systems frequently and it make sense to have this check to avoid errors.

Want to know more about Consistency Check– CLICK HERE

Difference in old and new

Alerts are generated based on the data set being captured for monitoring

Note – Some example images are taken from SAP systems/documentation and are for reference only.

Enjoy reading and i will come with more