SAP ABAP IMG Activity SIMG_CFMENUOLSDVOPA1 (Set Up Partner Determination for Shipments)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ VIZ (Package) Introductory guide R/3 central functions
IMG Activity
ID SIMG_CFMENUOLSDVOPA1 Set Up Partner Determination for Shipments  
Transaction Code S_ALR_87006435   IMG Activity: SIMG_CFMENUOLSDVOPA1 
Created on 19981222    
Customizing Attributes SIMG_CFMENUOLSDVOPA1   Set Up Partner Determination for Shipments 
Customizing Activity SIMG_CFMENUOLSDVOPA1   Set Up Partner Determination for Shipments 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_TRA_PARTNER    

Use

In this activity, you define the rules that should be used to perform automatic partner determination.

  1. Define the partner functions that differentiate the roles of partners in your system.
  2. Define the partner determination procedure, and assign the key of the relevant partner object to this procedure.
  3. Assign the partner functions you define to the account groups.

When you create a customer master record, the SAP system proposes the allowed partner functions for maintenance. The partners are copied from the sold-to party's customer master records into the sales documents, according to the rules you have defined.

For partner determination you must edit the following:

  • Partner function

    You can use the partner function to help you define which roles exist for partners (customers, vendors, employees, and so on) in your system.

  • Allowed partners for each account group

    You assign the allowed partner function for each account group customer.

  • Function key conversion

    You can define language-dependent keys for the partner functions.

  • Partner object

    Partners can exist in the customer master record and the sales documents. These are both partner objects. Select a partner object and define the partner determination rules for the object.

  • Partner determination procedures

    For each partner object, you define partner determination procedures that each contain the allowed partner functions.

  • Assigning procedures

    You use a key to assign each partner determination procedure to a fixed partner object, for example, an account group customer or a sales document type.

Partners are contained in both the customer master records and in the sales documents. You define partner determination separately for each of these objects.

The following partner objects exist:

  • Customer master record
  • Sales document
    • Header
    • Item
  • Delivery
    • Header
  • Shipment
    • Header
  • Billing document
    • Header
    • Item
  • Contact

Activities

After you have defined the partner functions, select the partner objects in turn and define the partner determination procedures for each object.

The "Partner Determination" function is only complete once partner determination has been checked, and changed where required, for all partner objects.

Defining Partner Functions

When defining a partner function, you enter whether the partner is, for example, a customer, vendor, customer employee, or your own employee. Depending on the partner function, the system expects you to enter a customer number, vendor number, a personnel number, or another number of your choice.

You must enter the following parameters for a partner function:

  • Partner function

    Enter an alphanumeric key for the partner function. This key can have up to two characters and a text description.

  • Partner type

    The partner type is an indicator that tells you which type of partner you are dealing with, for example, partner type Customer "KU".

    At this point in time, you cannot change the partner types in Customizing. You can only select partner types that are contained in the standard delivery.

  • Error group

    You use the error group to assign an incompleteness procedure to the partner function (see section "Log of Incomplete Items").

  • Superordinate roles

    You can enter superordinate partner functions for a partner function. In this way you can map the existing relationship between the partner functions.

  • Unique in customer master record

    If you flag a partner function as unique, then you can only enter the partner function one time in the customer master record.

    For example, the sold-to party must be unique in the customer master record, whereas you can enter more than one contact person.

  • Customer hierarchy type

    In this field, you can specify whether a partner function can be used for a customer hierarchy. To do this, enter the customer hierarchy type for which the partner function is allowed. For more information about the customer hierarchy type, see the section "Define Hierarchy Types and Assign Account Groups".

  • Role key conversion

    If you work with several languages in your sales system, you can perform a language-dependent role key conversion.

    This allows you to show the internal key definitions, for example AG and WE, differently on the screen according to the logon language of the user. This means that you can display the German key AG for Anmeldungen in English as CU. (This key conversion is necessary because the partner functions (AG, WE, and so on) are sometimes fixed in the programs.

Note

The key conversion for the role key takes place in the language in which you are logged on when you make the changes to the system.

SAP recommends...

If you define a new partner function, the key should begin with the letters Y or Z, since SAP keeps this name range free in the standard system. Exception: The key ZM in the standard system is already assigned to the partner function "Responsible employee". For this reason you should also avoid this particular key when defining new partner functions.

Activities

  1. Check the settings in the SAP standard version, to see whether you can use them as they stand, and to see if any changes are required.
  2. Define your partner functions.
  3. Make any required key conversions in your logon language.

Defining the Partner Determination Procedure and Assignment to the Relevant Partner Object

You summarize all partner functions that are allowed for a partner object in a partner determination procedure. You then assign a partner determination procedure to a key, for example a sales document type. The partner functions contained in the determination procedure are then relevant in a sales document of this type. In addition to this assignment, a partner determination procedure is valid, for example, for a certain account group customer or a sales document type.

To define a partner determination procedure, choose from the list of all possible partner functions, the particular function that is relevant for the procedure. Then add the following entries:

  • If the partner function should be a required input in the partner object, select the partner function as a mandatory partner function.
  • Specify whether changes to the partner function entries are permitted once they have been entered for the first time.

Note for the Partner Object - Contact

When you define the determination procedure for the partner object 'Contact', you can flag a partner function as unique. This means that you can avoid the function, such as responsible employee, appearing twice in the contact, for example.

Note for the Partner Object - Sales Document (Header)

When you define the determination procedure for the partner object 'Sales Document (Header)', you can make the following additional entries for the partner function:

  • Source

    Under this heading you can control two origin characteristics:

    • Source partner function
      • In this field you can specify that a partner should be determined directly using a partner entered in the sold-to party. If you enter, for example, the source "WE" for the partner function "SP", you can then specify that the forwarding agent is determined from the ship-to party, and not from the sold-to party.
    • Table of origin
      • In this field, you can specify from which table the partner with this particular partner function is determined. In the standard version, this field is blank, and the partner is determined from the customer master table. If you want the partner for this partner function to be determined from the table of credit representatives, you must enter "A". If you want to determine the partner from the customer hierarchy table, enter "B". In the latter case, the partner function must also have been assigned to a hierarchy type.
  • Sequence

    Entries in this field allow you to control the sequence in which partners are determined in the sales document. First, all partner functions are determined that have the ranking order zero, then those with ranking order 1, 2, and so on.

The relationship of partner object and assignment key is as follows:

Partner Object         Key

Customer         Account group

Sales doc. header         Sales document type

Sales doc. item         Item category - sales document

Delivery header         Delivery type

Shipment header         Shipment type

Billing doc. header         Billing document type

Billing doc. item         Billing document type

Contact        

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 1   Critical 
Country-Dependency A   Valid for all countries 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
VC_TPAR_TK C - View cluster SM34 01 Configuration: Partner 
History
Last changed by/on SAP  20020312 
SAP Release Created in