SAP ABAP IMG Activity SIMG_CFMENUOLIAVOP2 (Define Partner Determination Procedure and Partner Function)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM-CIC (Application Component) Interaction Center WinClient
     ⤷ INSC (Package) Application Development R/3 Plant Maintenance Customizing
IMG Activity
ID SIMG_CFMENUOLIAVOP2 Define Partner Determination Procedure and Partner Function  
Transaction Code S_ALR_87000811   IMG Activity: SIMG_CFMENUOLIAVOP2 
Created on 19981222    
Customizing Attributes SIMG_CFMENUOLIAVOP2   Define Partner Determination Procedure and Partner Function 
Customizing Activity SIMG_CFMENUOLIAVOP2   Define Partner Determination Procedure and Partner Function 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name OLQN-OQNP    

In this step, you define the partners for processing notifications.

Several partners are usually involved in processing a notification - internal and external partners. The types of partners and their functions can be different for each notification type. To define the functions, proceed as follows:

  • Certain partners have been predefined in the system; for example, the following partners apply to notifications:
    • Customer (customer number)
    • Vendor (vendor number)
    • Person (personnel number)
    • System user (SAP user)
    • Organizational unit
  • You can centrally define partner functions for all logistics applications. You must assign a partner type to the partner function; for example, you can assign the partner type "Customer" (with customer master and customer number) to the partner function "Complainant." You can also define a higher-level function for a partner function; for example, you can assign the higher-level function "Customer purchasing department" to the partner function "Customer purchasing agent."
  • Next, define the partner determination procedures. In each partner determination procedure, you define which partner functions are allowed. In doing so, you can specify whether a partner function in a notification can be changed or whether it is a mandatory function.
  • Each notification type is assigned a group of partners; for example, author, processed by, person responsible. For this reason, you must assign an appropriate partner determination procedure to each notification type. For each notification type, you must also assign the partner functions that will appear in the notification header. All other partner functions can be maintained in the notification itself, on the partner overview screen.

Standard settings

The internal partner functions (for example, author, coordinator, person responsible) exist for both the partner types 'system user' and 'HR master record.' The partner type 'system user' was selected for internal partner functions. If you are also using the HR module and you want to work with personnel numbers, you only have to exchange the following partner functions:

  • In the view 'Assign Partner Functions to the Notification Type'
    • Author A0 -> AU
    • Coordinator KU -> KO
  • In the view 'Define notification types'
    • Person responsible (person processing the notification) VU -> VW

Recommendation

Use the notification types and their assigned partner determination procedures, as defined in the standard system, unless you want to use your own partner determination procedures.
If your business organization is currently using the SAP application components HR Org. or SD, it may be advantageous to select the partner type "employee" for internal partners, in place of the partner type "system user", as defined in the standard system. Make sure all other applications are in agreement!
If you want to use your own partner determination procedures you can adapt the predefined SAP notification types and partner determination procedures to your own requirements.

Activities

  1. Define the partner functions and the partner determination procedures.
    1. Define the partner functions.
      If required, assign multilingual keys to the partner functions
    2. Define the partner determination procedure and determine which functions are contained in each procedure.
  2. Assign a partner determination procedure to each notification type.
  3. Specify the appropriate partner function in the notification header for each notification type.

Further notes

Multilingual Capability
You can use mnemonic keys for partner functions. The system supports this by assigning multilingual keys to these functions. You can find this function when maintaining the partner functions in the section Environment/ New Key Assignment for Functions. Such multilingual keys are displayed if you log on in a language other than the original language. However, only the original key has an effect in the technical sense, for example, in SE16 or in the transport system.

Partner Objects
Similar partner determination procedures are also used in other applications (for example, for quality certificates)and in the Implementation Guide for the Sales and Distribution component

Business Attributes
ASAP Roadmap ID 203   Establish Master Data 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG OLQN-OQNP 0 ALR0077563 O  
SIMG OLQN-OQNP 1 BIO0000031 O  
SIMG OLQN-OQNP 2 HLA0006831 Creating Quality Notifications 
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
VOP2 T - Individual transaction object VOP2 Define Partner Determination Procedure 
V_TQ80_PAR V - View SM30 Assign Partner Determination Procedure to Notification Type 
V_TQ80_PA V - View SM30 Assign Partner Functions to Notification Type 
History
Last changed by/on SAP  20000201 
SAP Release Created in