Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
ME0C (Package) Customizing R/3 Purchasing
IMG Activity
| ID | W_ZF_ST_0112 | Define partner determination for hierarchy categories |
| Transaction Code | S_ALR_87002280 | IMG Activity: W_ZF_ST_0112 |
| Created on | 19981222 | |
| Customizing Attributes | W_ZF_ST_0112 | Define partner determination for hierarchy categories |
| Customizing Activity | W_ZF_ST_0112 | Define partner determination for hierarchy categories |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | W_ZF_ST_0112 |
In this step, you define partner determination for the hierarchy categories.
In addition to the hierarchy category, you must also take the higher-level partner functions which are maintained in partner determination into account when making the vendor hierarchy settings.
Particular partner functions are determined for every node in the hierarchy path depending on the hierarchy category during order processing. Using the default partner function (in the standard system, for example, 2A) as a basis, the higher-level partner functions are determined and assigned to the nodes of the vendor hierarchy path.
The standard system contains the partner functions 2A-2D, with the default partner function on the lowest level. If you want to use more than three vendor hierarchy levels, you must create additional partner functions (table TPAR). Note that the system can process a maximum of 26 hierarchy levels.
Standard settings
SAP provide data up to hierarchy level 4 for partner determination and hierarchy level 3 for the conditions (access sequence).
Activities
If necessary, create further partner functions to allow you to use additional hierarchy levels.
If the depth of the hierarchy is insufficient, you need to make the appropriate settings for partner determination in Partner Settings in Purchasing Documents and conditions (access sequence) in Define Price Determination Procedure.
Further notes
Use at least as many higher-level partner function levels as vendor hierarchy levels. If you do not, "excess" vendors will not be included, since only as many vendor hierarchy levels are taken into account during path determination and pricing as there are higher-level partner function levels.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| 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 | W_ZF_ST_0112 | 0 | HLA0009512 A HLA0001521 |
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_TPAR | V - View | SM30 | 0000000010 | Definition of Partner Roles | ||
| V_TPAUM | V - View | SM30 | 0000000010 | Language-Dependent Key Reassignment for Partner Roles | ||
| V_TPAKL | V - View | SM30 | 0000000010 | Permissible Partner Roles per Account Group |
History
| Last changed by/on | SAP | 19990609 |
| SAP Release Created in |
