In this blog I would like to share some information on replication of COPA postings into Central Finance. How Cost based COPA /Account based COPA data can be integrated into Central Finance. Happy reading!
In COPA, one can choose between Account Based COPA vs Costing based or both can be run in parallel too. Due to various business reasons majority of customers have opted for costing-based COPA in ECC based systems. However, due to various value fields and different tables, reconciliation with GL is always a challenge.
In S/4 HANA due to product advancements and integration with universal journal, Account based COPA (Margin Analysis) is recommended by SAP. Below are some points to note about COPA data integration in CFIN.
Central Finance offers integrating of COPA postings from both accounts based and costing COPA setups.
During transfer of documents FI (Staging Table CFIN_ACCPA_CHAR) and CO COPA data is also sent over to CFIN.
CO Settlements to COPA are also replicated to CFIN.
Below are the steps for activating the COPA replication in CFIN.
Mapping of COPA Characteristics
There is a standard mapping offered by SAP where COPA characteristics from source system are mapped to characteristics in CFIN. Configuration is available at IMG Path
Central Finance >> Central Finance: Target System Settings >> Mapping >> COPA Mapping >> Define COPA mapping.
Characteristics can be mapped from source operating concern to CFIN operating concern.
Unless developed, these values don't go through a mapping and master data check in CFIN system.
Values of source characteristics are posted as-is in CFIN. E.g. a bill to party number would be posted in CFIN with same number unless MDG mapping set-up is updated.
Value field mapping is not relevant if account-based margin analysis is used in CFIN.
In order to carry out this mapping a connection to respective source system is required. It's best to open the client and configure mapping in each respective tier.
Mapping of SD Condition types to G/L Accounts
SAP offers a flexibility to map SD condition types to GL Accounts in CFIN. Both statistical and non-statistical condition types can be mapped in CFIN.
This could particularly be useful:
If something from sales document is posted only to COPA and not to FI module. In my experience there can be some statistical condition types in source which are posted only to COPA, then those can be mapped and posted to a GL account in CFIN.
For Statistical condition types:
You need to configure a G/L account and an offsetting account.
This is required, because the values posted from statistical condition types are posted to an extension ledger and the offsetting account is necessary to balance the posting to zero.
Ledger group should be activated in table FCOV_STAT_ACT
A technical document starting with TA is posted in extension ledger. This document can't be viewed using FB03 but can be viewed with TCODE GD22
For non-statistical condition types, you leave the offsetting account empty.
These documents can be configured to be posted to a different document type.
Mapping of Condition Types to GL Accounts
Transfer of COPA data at time of PGI
In Costing based COPA, values are posted to COPA at time of Billing, whereas in account-based COPA values are posted to at time of PGI.
While integrating costing-based COPA from source to account based COPA (Margin Analysis) in CFIN this is an issue, as COPA data is not generated a time of PGI. At best a COPA derivation can be forced by automatic account assignment (PC) by posting only to a PC.
SAP has released a feature where at time of PGI in source COPA data is generated for CFIN staging tables. Source posting mechanism is not affected, data is generated only in CFIN staging tables.
This enables posting to COPA in CFIN at time of PGI.
Table VCFIN_COGS_COPA needs to be configured in source system for each company code
COPA Data Generation At time of PGI
COPA set-up and integration with CFIN is quite complex and needs a thorough design. Hope information above is useful. Please feel free to leave your feedback in the comments section of this blog.