Custome Partner Function from SD to CO-PA

Question

Hi,
I have created 3 custom partner functions and have assinged in customer master. I need these 3 custom partner function to be transfered to CO-PA during billing. Is there a easy way around to achieve this, coz there are some SAP notes which are sort of confusing and complex, since we are already live in production, we cant take a chance on the SAP Note.
If somebody experienced like this, could you please share the knowledge, how to achieve this.
Thanks.
With Regards
gj

Answer 1

Hi Gj,
There are no simple way around to get the customer partner function in to CO-PA during billing. You must follow the notes to get the correct value transfered to CO-PA. I will outline the steps below so that you do not miss anything.
I am going to try to summarize the basic steps to add one or
more new partner function(s).  For more detailed information
please see the notes 36557, 32878, 12682 and 93658 although some o
these notes are known for you.
Add new domain/data element for the new partner function in the
ABAP/4 Data Dictionary.
  Examples are the data elements KUNAG, KUNWE, KUNRE, KUNRG,
  SPDNR, and VRTNR in structure MCPARTNER. This is where the
  partner functions for the Standard Sales Information System are
  defined.
Save the new partner field in structure MCPARTUSR (user part of
  structure MCPARTNER) or, if available extend structure
  MCPARTUSR by an append structure (ZAMCPARTUS).
Make sure that the check tables and foreign key relationships are
  maintained for the new fields in structure MCPARTUSR
Define the assignment of partner function <  > new partner
  field in the communication structure.
  Program RMCSUZ10, routine USR_PARTNER_GET.
  Add the line as in the example of note 12682 given.
Include the corresponding field via transaction 'KEA0' from the
  structure PAPARTNER into the Profitability Analysis data structures
If your new partnerrole is a representative/sales employee please
  apply note 32878.
Should you have implemented note 43002 (to prevent a field overflow
  in pricing) please follow note 93658 and use userexit
  userexit_pricing_prepare_tkomp instead of
  userexit_pricing_prepare_tkomk.
  userexit_pricing_prepare_tkomp is contained in Include MV45AFZZ
  (sales order) and RV60AFZZ (billing)
Add the new field to the structure 'KOMPAZ' as in note 93658
  described and  NOT  to the structure 'KOMKAZ' (note 36557)
  (you have used both structures)
Generate the operating concern and check if the following entries
  are included in TKEZU:
  Charact.  BTran Table      Field name  Offset  Length
  XXXXX     KEDR  KOMP      YYYYY
  XXXXX     KEDR  KOMP      YYYYY
  XXXXX     KEDR  KOMP      YYYYY
  XXXXX = Field name of the partner function in the  profitability
  analysis
  YYYYY = Field name of the partner function in structure KOMP
(these entries should be made automatically here).
If you need more than one partner function please repeat the
steps as described above for your need.
Regards,
Abhisek