With customer hierarchies you can now create flexible hierarchies to reflect the structure of customer organizations. For example, if your customer base includes multi-level buying groups, cooperatives, or chains of retail outlets, you can create hierarchies to reflect the structure of these groups. You use customer hierarchies in order and billing document processing for partner and pricing determination (including rebate determination) and for creating statistics.
You can use customer hierarchies to assign price conditions and rebate agreements to one of the customer’s subordinate levels, to ensure that all subordinate levels are valid for the customer. For each node that you indicate as relevant for pricing, you can create condition records for pricing. If one or more nodes in a hierarchy path for a sales order contain pricing data, this is automatically taken into account in pricing.
You can also use customer hierarchies for evaluations in profitability analysis (CO-PA) and in the Sales Information System (SIS):
To evaluate customer hierarchies with the sales information system and in the profitability analysis, you can maintain the field Hierarchy assignment on the Marketing tab page in the customer master record for a hierarchy customer. Here you can maintain 10 features for hierarchy customers (HIEZU01 to HIEZU10). You can use these to evaluate hierarchies statistically with up to 10 levels. (Field catalogue VHIE)
Note that the hierarchy assignment is statistical. If you change the customer hierarchy, you may need to change the hierarchy level manually in the customer master record in the Hierarchy assignment field.
A customer hierarchy is a flexible structure consisting of customers. Each customer - with the exception of the uppermost customer - refers to another customer at a higher level in the hierarchy (known as a higher-level customer). Customers that are assigned to higher-level customers are known as dependent customers.
To be able to display organizational elements, that are not independent partners, you can assign pure hierarchy nodes (account group 0012) in the hierarchy. Specific data can be assigned to a hierarchy node (for example, address, price conditions, rebate agreements) and this then applies to all subordinate customers.
As all nodes in a hierarchy are time-dependent, you can adapt the customer hierarchy to changes in the structure of a customer at any time.
- Customers can be reassigned in a hierarchy When reassigning a customer, all subordinate customers are moved with it
- You can add new customers to a hierarchy When you assign a new customer to an existing hierarchy, all pricing data, that applies to the higher-level hierarchy node, is automatically copied from the customer
- You can also remove customers from the hierarchy
Customer Hierarchies and Pricing