Integration of RMCA and COPA
RMCA (Receivables Management – Contract Accounting) which is designed for mass processing for Telecommunication companies with huge customer database can be integrated with COPA for profitability Analysis. This article talks about COPA related configuration settings and processes in RMCA.
The key difference between RMCA and FI on COPA integration is that in FI, COPA document is generated at the time when the document is posted to FI. In case of RMCA, COPA transfer needs to be done as a separate activity which will take profitability segments for the documents into COPA and generate COPA documents. This is done as a daily transfer from RMCA to COPA in tune with RMCA GL transfer.
Account determination in RMCA is based on the Main Transaction (MT) and Sub Transaction (ST) settings. Combination of MT and ST determines the GL account to be posted. If the determined GL is set for Profitability Segment as required entry in the field status group, then the Entry in RMCA will always ask for profitability segment input while posting the document.
Defining Characteristic Derivations for CO-PA Update
While transferring data from external systems (Billing Systems) into RMCA through IDocs, configuration settings needs to be done for COPA characteristics derivation
IDoc FKK_EBS_TOI_COPA is used for data transfer in RMCA. Segment E1FKK_EBS_TOI_COPA_ITEM takes care of COPA characteristics for the document which is posted for the external data transfer
Go to > CA Receivable and Payable > Data Transfer> Communication with External Billing Systems> Define Characteristics derivation for COPA update.
In this activity, for each operating concern, you define the characteristics for the update in the profitability analysis (CO-PA). The table is used to derive the characteristics when you post the IDoc characteristic data.
The table is used to derive the characteristics when you post the IDoc characteristic data. The external billing system transfers the characteristic values to the application in the IDoc category FKK_EBS_TOI_COPA or FKK_EBS_DOC in segment E1FKK_EBS_TOI_COPA or E1FKK_EBS_DOC_COPAITEM. If the characteristic values cannot be provided via the IDoc interface, you can determine the value using a function module at runtime.
Transfer to COPA from RMCA
This is done as a periodic processing unlike the real time transfer in GL. Transaction Code to be used is FPG3
The transfer is based on Reconciliation keys and documents having line items with profitability segment numbers are transferred to COPA. The status of the transfer is retained for each reconciliation key so that duplicates are not transferred. All Reconciliation Keys which are selected for transfer should be closed before initiating transfer.
If the line items contain a posting date for which the posting period is already closed, the program tries to determine an alternative posting date. You maintain alternative posting data in transaction FPG0.
Profitability Analysis and System Performance.
A very important factor to be considered while implementing COPA is system performance while posting or transferring documents to COPA. SAP Note 35288 talks about the same . When a document is posted to COPA, system would check for a profitability segment number for the combination of characteristics values to be posted in table CE4xxxx. Creating a secondary index with the most selective fields for this table will make this search faster when external data is transferred or journals are posted. Otherwise there is a risk of considerable slow down in processing each transaction. The most selective fields in the secondary index can be found by running the report RKE_ANALYSE_COPA. Once a new index is created, report RSANAORA to be executed to update DB statistics