GRC
HR
SCM
CRM
BI


Blog

 

Making Subsequent postings to CO-PA from other Modules

by Paul Ovigele

August 16, 2011

Paul Ovigele, Ovigele Consulting

In my previous blog, titled “Reversing CO-PA Documents” I wrote about how you can cancel documents in the CO-PA module alone. This is normally needed either when you want to correct a CO-PA document which was posted using transaction KE21N or if there is a reconciliation issue between CO-PA and another module that needs to be fixed. There are also cases where you want to make subsequent postings to CO-PA when the corresponding documents in other modules have already been made. Examples of how this could occur are as follows:

(i)    You activated CO-PA after you went live with your system and postings (which contain profitability segments) have already been made in the relevant modules;

(ii)    You made a change to configuration (for example with a value field assignment to a sales condition) and want to correct the CO-PA document that had already been posted;

(iii)    You deleted a CO-PA document (intentionally or unintentionally) using transaction KE4S00 and want to repost the document to the CO-PA module.

Depending on which module the source transaction exists in, there are different transactions that can be used to subsequently transfer the documents to CO-PA:

(1)    Transfer of SD Billing Documents: You can access this function by going to transaction KE4S. Enter the billing document number (or range) and any other relevant information such as the company code, sales area data and posting dates. In the ‘Control Parameters’ section, you can select the checkbox “Redetermine Profitability Segment” if you want re-derive certain characteristics due to a derivation rule or master data change. In the ‘Update Control’ section, you can select the “Check for existing records” button if you only want the posting to be made if a CO-PA document does not already exist; you can select the “Reversal of line items” button if you want to cancel the original CO-PA document as well as post a new one, or; you can select the “Posting without Check” button if you do not want the system to validate whether a CO-PA document already exists (obviously this option carries a risk of creating duplicate entries, so use with caution).

(2)    Transfer of FI Documents: You can access this function by going to transaction KE4SFI. Enter the relevant company code, fiscal year and period if you want to restrict the documents by these criteria. In the ‘Business Transaction’ section, enter “RFBU” (Financial Postings) in the ‘Transaction’ field and enter “BKPF” (Accounting Document) in the ‘Document Origin’ field. You can further restrict your selection criteria by entering a ‘document number’, ‘document date’, ‘posting date’ or ‘creation date’ in the ‘Doc’ (Document) section. If you want the system to validate whether a CO-PA document exists (which I would recommend that you do), then you can select the “Check for Existing Recor ds” checkbox in the ‘Control’ section.

(3)    Transfer of MM Documents: You can access this function by going to transaction KE4SMM. Enter the relevant company code, fiscal year and period if you want to restrict the documents by these criteria. In the ‘Business Transaction’ section, you can drop-down in the ‘Transaction’ field to choose the relevant business transaction that relates to the document that you want to post (for example you can select “RMWA” for an inventory document). In the ‘Document Origin’ field, you can either choose “MKPF” if it is a material document, or “RMRP” if it is an invoice receipt. The ‘Doc’ and ‘Control’ sections have exactly the same fields and functionality that have been mentioned in the transaction above (KE4SFI).

For more infrormation on how to optimize your SAP Financials landscape, I've put together my top tips in the book 100 Things You Should Know About Financial Accounting with SAP  which is published by SAP Press.

An email has been sent to:






More from SAPinsider



COMMENTS

Please log in to post a comment.

No comments have been submitted on this article. Be the first to comment!


SAPinsider
FAQ