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_CFMENUOLIAOIM9 | Define Partner Functions for Header Data |
| Transaction Code | S_ALR_87000817 | IMG Activity: SIMG_CFMENUOLIAOIM9 |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_CFMENUOLIAOIM9 | Define Partner Functions for Header Data |
| Customizing Activity | SIMG_CFMENUOLIAOIM9 | Define Partner Functions for Header Data |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_V_TQ80_PA |
In this activity, you define the partners for processing notifications. Several partners - internal and external - are usually involved in processing a notification. The types of partner and their functions can be different depending on the notification type. Specific partner types are predefined in the system.
To define the interaction of functions with notification types, proceed as follows:
- You can define partner functions centrally for all applications in Logistics. You must assign a partner type to each partner function. For example, you can assign the partner type "Customer" (with customer master record and customer number) to the partner function "Originator of complaint". You can thereby also specify a superior function for a partner function. For example, you can assign the superior function "Customer purchase" to the partner function "Customer purchaser".
- Next you define the partner determination procedures. In each partner determination procedure, you define which partner functions are permitted. You can define whether a function in the notification should be changeable and whether it is a mandatory partner function.
- A group of partners belongs to each notification type, for example, originator, processor, person responsible. Therefore, you assign a suitable partner determination procedure (one that outlines this group) to each notification type. You also assign the partner functions, which appear on the header screen for the notification, to each notification type. All other partner functions can be maintained in the notification itself in the partner overview.
Standard settings
The internal partner functions (for example, author, coordinator, person responsible) are available with both partner type "System user" and "Personnel master". The partner type "System user" has been selected for all internal partner functions. If you use the HR application and work with "personnel numbers", you simply need to change the following partner functions:
- In view "Partner Functions for Header Screens"
- Author AO -> AU
- Coordinator KU -> KO
- In view "Define Notification Types"
- Person responsible (processor of task) VU -> VW
Recommendation
Use the partner determination procedures and assignments provided in the standard system, unless there are specific reasons not to.
If your company uses the SD and HR-Org components, it may be beneficial to choose the partner type "Personnel" in the partner functions for internal partners, rather than the partner type "System user" used in the standard system. Check here with the other applications.
If you want to use your own partner determination procedures, you can base them on the notification types and partner determination procedures predefined by SAP.
Activities
- Define the partner functions and partner determination procedures.
- Assign a partner determination procedure to each notification type.
- Specify suitable partner functions for the header screens of the notifications.
- Define the partner function, which is responsible for tasks, for each notification type.
Use the view for defining notification types for this.
Further notes
- Similar partner determinations are also used in other applications, for example, for quality certificates and in Sales and Distribution.
- You can create orders in SD from notifications with origin Q1 (customer complaint). The corresponding sales document type is defined for each notification type. For technical reasons, this is performed in the view for defining partner functions for the header screens of the notification type.
Example
Requirements
Standard settings
Recommendation
Activities
Further notes
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 1 | Mandatory 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 |
| V_TQ80_PA | V - View | OQN9 | Special Parameters for Service Notification |
History
| Last changed by/on | SAP | 19991025 |
| SAP Release Created in |
