COPA and BSEG-SGTXT

Question

We have postings that are happening in FI, and the users are populating the text fields on these postings.  Is there a way to pass this text field over to COPA to bring into reporting and display of documents in that module?

Answer 1

Your question is more appropriate for the ERP Financials - Controlling forum, but I don't have authority to move it.  So I'll go ahead and try to give you an answer here.  But keep that in mind when posting about CO-PA in the future since a larger audience will be found at the other [forum|SAP ERP Financials - Controlling; This requirement is an unusual request and the only way I think it could be possible is as follows.
1 Define a new characteristic (KEA5) with the option "No check" data validation so that no master data would be expected in CO-PA (KES1).
2 Add this new characteristic to your operating concern (KEA0) and activate and generate the operating concern.
3 Utilize COPA enhancement COPA0005 (SMOD) by defining an enhancement project in (CMOD) and calling the function module EXIT_SAPLKEII_002 and programming your logic to read SGTXT from include INCLUDE ZXKKEU08.  (Notice that use of enhancement COPA0005 is not related to CO-PA derivation (KEDR), rather it is a way to directly modify the CO-PA data passed by the FI/CO document.
Here is some relevant documenation on COPA005.
This enhancement lets you modify how actual data is updated in
Profitability Analysis via the FI/CO interface.
Caution!
Using the components in this enhancement means that you are modifying
the standard update of actual data from Sales and Distribution (SD),
Financial Accounting (FI), or Materials Management (MM) to Profitability
Analysis. To avoid data from being updated inconsistently, you need to
have a solid understanding of the "FI/CO document" interface!
Make changes with extreme caution. If unsure, contact SAP!
The components comprise the following function modules:
o   EXIT_SAPLKEII_001
o   EXIT_SAPLKEII_002
You are responsible for ensuring the consistency of any changes made!
Test each change made extensively before use in the productive system.
For further clarification, contact SAP.
You should strongly consider whether this solution will negatively affect your system performance by growing your segment-level characteristics (table CE4XXXX where XXXX is your operating concern).  You may want to in fact make this new characteristic field a non-segment level characteristic (KEQ3).  This will disable you from viewing this field in summary level CO-PA reports (KE31), but it would available from line item based reports (KE91) or from a custom BW infoprovider which gets line item data.  You could of course use a combination of KE31 reports and KE91 reports by jumping from summary to detail reports and passing the selected characteristics.  This is accomplished via the split report (KE3L) option.
Best regards,
[Jeffrey Holdeman|https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/jeffrey+holdeman]
SAP BusinessObjects
Enterprise Performance Management
Regional Implementation Group
Tried to fix the formatting, but unsuccessful.  Edited by: Jeffrey Holdeman on Jul 28, 2009 10:04 PM
Edited by: Jeffrey Holdeman on Jul 28, 2009 10:10 PM