Skip to Content

Customer Hierarchies

Hi All,

I have never done customer Hierarchies in SAP I need to do for one of my clinets. Can someone has some write up including screenshots regarding the basics, config to be done, master data and transaction data , condition records etc to be maintained.

my mail id is arorasachin2005@gmail.com

regardfs

sachin

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Best Answer
    Posted on Dec 05, 2007 at 10:34 AM

    dear sachin

    gothrough this

    Customizing Customer Hierarchy in SD

    How to configure and maintain the SD Customer Hierarchy?

    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: symbol 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 uses 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 enters the sales area and enters 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

    rewards pls

    siva

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 05, 2007 at 11:05 AM

    hi,

    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 uses 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.

    Customer hierarchies are available in Sales and Distribution, so that you can create flexible hierarchies to reflect the structure of customer organizations. If your customer base includes multi-level buying groups, cooperatives, or chains of retail outlets, for example, you can create hierarchies to reflect the structure of these groups. Use customer hierarchies during sales order processing and billing for determining pricing and running statistics.

     A customer hierarchy consists of nodes.

     To create a customer hierarchy:

    1. Create master records for each node.

    2. Assign the nodes to each other.

    3. Assign the customer master records to the relevant nodes.

     Hierarchy nodes are only valid for a certain period of time. They may also be moved. If a node is moved, the system automatically reassigns all related nodes and customer master records.

    With customer hierarchies, you can assign price or rebate agreements to a higher level node. The agreements are then valid for customer¬ís at all subordinate levels to this node. You can create pricing condition records for each node indicated as relevant for pricing. If one or more nodes in the hierarchy path of a sales order contain pricing information, the system takes them into account automatically during pricing.

    'How to check'

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

    try_this_link_too

    *on your Q about 'how many nodes/customer', answer is they can be till infinity, you decide the nodes as per business requirements.

    CHAN

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.