Hierarchy
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ KE (Package) Profitability Analysis
Basic Data
Data Element | KEDRCHIERFLAG |
Short Description | Customer Hierarchy Assignment Flag |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | KEDRFLAG | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | AutoAssign |
Medium | 16 | Automat.Assignmt |
Long | 22 | Automatic assignment |
Heading | 22 | Automatic assignment |
Documentation
Definition
When the customer hierachy is read, all higher-level customers (that is, those superior to a given customer) are determined.
There are two ways of assigning these customers to the characteristics in the customer hierarchy in Profitability Analysis:
1) Assignment via the customer master
The "Hierarchy assignment" field is maintained in the customer master for each customer. If, for example, this field contains the value "3", then customers in the hierarchy are assigned to characteristic HIE03 "Customer hierarchy level 3".
If an assignment is missing, then the customer is not transferred.
This method can be very time-consuming but it allows customers to be assigned flexibly to any customer hierarchy level in Profitabiliy Analysis.
2) Automatic assignment according to the customer hierarchy level
With this method, the customer hierarchy is read and all customers are simply entered consecutively into the characteristics of the customer hierachy levels, starting with the highest node in level 1. In this way, the level corresponds to the level visible in customer hierarchy maintenance.
Unlike the above method, this method does not support flexible assignment. However, it circumvents the need for making any maintenance entries in the customer master. Moreover, changes made to the hierarchy (such as moving branches) take immediate effect.
If this method has been activated, then any assignments already maintained for method 1 are ignored.
History
Last changed by/on | SAP | 19991201 |
SAP Release Created in |