Show TOC
Define and
Assign Partner Determination Procedures
You define the determination procedures in this
menu option and allocate them to the keys of the respective partner
object.
You group together all
partner functions which are allowed for a partner object in a
partner determination procedure. Afterwards, you allocate a partner
determination procedure to a key, for example, the
sales document type. The partner functions contained in the
procedure are then relevant in a sales document of this type.
By this allocation, a partner determination procedure is for example valid for
a specific customer account group or a sales document type.
To define a partner determination procedure,
select the partner function which is relevant for the procedure from the list
of all possible partner functions. In addition, make the following
specifications:
- If a partner function in the partner object is
a required entry, mark the partner function as a mandatory
function.
- Indicate whether you may change the
specifications on the partner function in the object after the first entry or
not.
Note - Partner
object: Sales activity
In the definition of a partner determination
procedure for the partner object sales activity, you can specify a partner
function. This way you can avoid a function occurring twice in one sales
activity, for example employee responsible.
Note - Partner
object: Sales order (header)
When defining partner determination procedures
for the partner object sales order (header), you can make the following
additional specifications for a partner function.
When specifying
origin, you can control two features:
- Partner function of origin
In this field, you
specify whether a partner should be determined directly using a partner
specified in the sold-to party. For example, by entering the origin 'WE' for
partner function 'SP', you can specify that the carrier is not to be
determined from the sold-to party but rather from the ship-to
party.
In this field, you
specify from which table the partner with this partner function is to be
determined. The field is blank in the standard system and the partner is
determined from the customer master table. If you require a partner of this
partner type to be determined from the credit employee table, enter 'A'. If
the partner is to be determined from the customer hierarchy table, enter 'B'.
The partner function, in this case, must be assigned to a hierarchy type as
well.
In this field you
control in which sequence the partner is to be determined in the sales order.
The system first determines all partner functions with an order of precedence
0 then 1 and 2, etc.
The relation between partner object and sort
key is as follows:
Partner object |
|
Key |
Customer |
|
Account group |
Sales document header |
|
Sales document type |
Sales document item |
|
Item category sales document |
Delivery header |
|
Delivery type |
Billing document header |
|
Billing type |
Billing document item |
|
Billing type |
Sales activity |
|
Sales activity type |
Actions
1. Check to
what extent you can use the configurations contained in the standard SAP R/3
System or to what extent you need to change them.
2. Define your
partner determination procedures.
3. Then
allocate the partner determination procedures to the keys of the respective
partner object.
Transport
To initiate transport of this data, select
'Partner - Transport' in the initial screen.