Description
XPRA for adapting the Customizing settings in partner determination.

Precondition
None

Output
Conversion of Customizing entries for partner processing into tableTPAER.
If errors occur during conversion:
-----------------------------
If problems occur during XPRA´s PUT-run, the conversion must be donemanually. Do the following:
1. After the PUT, call transaction VOPA
2. Click on "partner functions"
3. Note down all partner functions with partner type "KU"
(scroll if necessary)
4. Press "F3"
5. Select partner object "customer master" and click on the partner
procedures
6. Select the first procedure and click on "functions in the
procedure"
7. Under "Source" in the second column, maintain value "C" for all
partner functions you noted in step 3, if they previously had
value SPACE
EXCEPTION: NOT FOR FUNCTIONS AG, WE, RE and RG! These functions
MUST only be maintained in partner object "sales activities"
8. Save the procedure and press "F3"
9. Repeat step 7 and 8 for all further procedures in the current
partner object
10. Repeat steps 6 to 9 for all further partner objects for
transaction VOPA

Example
The following procedures are incomplete and do not necessarily agree
with the current procedures.
Setting before 4.5A: Partner object "Sales doc. header"; Procedure"KAB"
Not changeable Mand.funct. Unique Origin Subs.
AG . X __
AP X __
AW __
VE __
WE __
ZM X __
...
After conversion to 4.5A and XPRA has run:
Not changeable Mand.funct. Unique Origin Subs.
AG X __
AP X __
AW __ C
VE __
WE __
ZM X __
...
Setting before 4.5A: Partner object "Sales activ. (CAS)"; Proc. "CAS1"
Not changeable Mand.funct. Unique
AG Sold-to party X
AP Contact person X
VE Sales representative
WE Ship-to party
ZM Employee responsible X
After conversion to 4.5A and XPRA is run:
|---- NEW ----|
Not changeable Mand.funct. Unique Source Subs.
AG X __ C
AP X __
VE __
WE __ C
ZM X __