customer hierarchy

[Former Member]

Hi Ayub

could you ple send me configuration steps for Partner determination covering customer hierarchy.

I would reward point for same.

Thanks

Shiv

[Manoj_Mahajan78]

Shiv,

Customizing Customer Hierarchy in SD

All the customizing is in SD/Master Data/Business Partner/Customers/Customers hierarchy

1) Define hierarchy type: just put and ID and a name to the new hierarchy.

2) Set partner determination: if you want to user the hierarchy in price determination, then, in the orders, at the header level, you have to have a Partner Procedure with a partner function for each level. In the partner procedure, in each partner function you must indicate the source partner function. With this information, in the order, you obtain the business partner for each partner function.

3) Assign account groups: you indicate which accounts groups are allowed for being part or your hierarchy.

4) Assign sales areas: simple you indicate which sales areas are allowed in your hierarchy. (Here you can customize common sales areas, just for not having to build de hierarchy in all the different sales areas).

5) Assigning hierarchy type for pricing: you indicate which classes of documents use hierarchy in pricing determination.

It is possible to maintain so called customer hierarchies. This might be useful when for example you create a condition discount for a customer that is part of such a hierarchy structure. All sub nodes in the hierarchy below that customer, will thus receive the same discount.

Customer hierarchy setup, firstly decide the hierarchy type to be used.

The standard is type A.

You can also assign a partner function to the customer so that the higher level customer in the hierarchy is copied into a sales order as a partner function - but you don't need that right?

Next assign your customer account group to the hierarchy type. And enter the combinations that will be allowed for creating the hierarchy.

You want to assign a ship-to to a payer. So enter the ship to account group and enter the payer account group as the higher level.

You must also make an entry for permitted sales area assignments. So if you want to a hierarchy for customers in the same sales area then enter the sales area and enter the same one as the higher-level sales area.

All these settings can be found in the IMG. Under SD - master data - business partners - customers - customer hierarchy

You use for example customer hierarchy when you have an company like Unilever and you agree both on a discount. Unilever does have different locations / businesses and you have to maintain the discount for all customers. If you use a customer hierarchy you can maintain the discount for the partner in the top of the hierarchy and in this way it will be valid for all customers in the hierarchy.

AWARD POINTS IF U FINDS THIS AS USEFUL...

Regds

MM

[Former Member]

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.

Integration

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.

Features

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 You can use the customer hierarchy type to determine the following:

the purpose of a specific hierarchy (for example, pricing, statistics)

which account groups are permitted in the hierarchy

which organizational data is permitted in the hierarchy

Use

When you maintain a hierarchy, enter the corresponding hierarchy type.

Customer hierarchy type A is provided in the standard system (standard hierarchy). You can define your own hierarchy types in Customizing for sales and distribution under Master data ® Business partner ® Customer ® Customer hierarchy ® Define hierarchy types.

To be able to use customers for customer hierarchies, you must have defined the following in Customizing for Sales and Distribution,

which account groups are permitted for hierarchies

which account groups are assigned at a higher-level in the hierarchy

which sales and distribution areas are permitted for hierarchies

Process Flow

You create master records for each customer, that you want to use in the hierarchy.

Depending on the function the customers have in the hierarchy and in order processing, create master records for Customer hierarchy nodes or for the sold-to party, payer and so on. You can find further information in Creating Customer Master Records.

In the customer master record you can indicate whether the customer is relevant for pricing, rebate processing, profitability analysis (CO-PA) or evaluations in the sales information system (SIS).

You create a hierarchy, in which you assign the hierarchy customers for the higher-level customer.

Normally the sold-to party or goods recipient are assigned to the lowest hierarchy level. You can, however, also assign a sold-to party to a node, that is at a higher level. For example, you could assign a particularly large branch of a chain of retail outlets to the regional office instead of to the local office.

You can maintain the hierarchy at a later date, by

assigning new customers (these customers are automatically assigned a current validity date)

reassigning available customers

changing the validity period of a customer for the hierarchy

removing customers, if required, from the hierarchy

Result

If you assign a customer in the hierarchy, the system creates a time-dependent assignment for this customer to the higher-level customer. When processing the customer hierarchy, you can change these assignments. You cannot change the customer master data. Changes in the customer master record are made in customer master record maintenance.

You can create special conditions or agreements for higher-level customers in the hierarchy. During order processing, the system takes into account automatically during pricing the current customer hierarchy and chooses the valid conditions.

Example

In the following example, the customer hierarchy represents the Smith nation-wide buying group. The central office - Smith Central - is defined as the top node in the hierarchy. T h e regional offices for the buying group, Smith south, central and north east, are defined as nodes, whereby Smith north is a higher-level node to Smith central and Smith north east.

[Former Member]

hi

[Former Member]

Hi

Refer below link