Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from KenThomson on Jun 9 at 9:55 PM Hi Philip,
Yes, that is the reason code field I was thinking of. They can be configured to be either simple dumb reason codes that do not do anything other than be a code (with description) for the GL entry being posted or they can have a small functional action where they will do other things.
We have a bunch of these codes set as simple dumb codes and use them regularly on certain GL accounts. (in fact we have that Reason Code field as a mandatory field for certain GL accounts, but that's a separate matter)
We have not tried to carry that reason code into the COPA area so have not done the same thing that you are wanting to do, but in principle it can be done.
I don't have a step by step guide, but as I see it it would be:
1 - In COPA config ? create a new Characteristic value that will be used to hold the same value that is put into the Reason Code field in the GL posting.
2 - After creating the new Characteristic ? then add it into your Operating Concern
3 - Then create a Characteristic Derivation that will copy the Reason Code value from the GL posting entry into this new COPA Characteristic this may require a user exit or function module to achieve the result I think by memory we have used function "EXIT_SAPLKEII_002" and with a bit of ABAP code we get it to do special things outside of the standard COPA Derivation rules.
I hope this helps.
Regards,
Ken
| | | ---------------Original Message---------------
From: padekunle
Sent: Thursday, June 09, 2016 9:09 PM
Subject: Adding Customer Reason Codes to COPA Characteristics
Hi Ken,
The reason code is in table T053R-RSTGR.
I do have limited knowledge of COPA. So, I'm wondering if
you have a step-by-step document I can use to assist me
set-up the COPA characteristics Derivation you described below.
Can you please send such document?
Thanks,
Philip |
| Reply to this email to post your response. __.____._ |    _.____.__ |
