Customer Hierarchy setup

HI Experts,
Please guide me how to setup the customer Hierarchy in system and what is the table for customer hierarchy.
thanks in advance.
Vivek.

Hi,
The table for customer hierarchy is KNVH.
All the customizing is in SD/Master Data/Bussiness 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 informacition, in the order, you obtain the bussiness partner for each partner function.
3) Assign acount groups: you indicate which accounts groups are allowed for being part or your hierarchy.
4) Assign sales areas: symple you indicate wich 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 documentos 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 subnodes 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.
regards
Vivek.
Edited by: Vievk Vardhan on Dec 7, 2009 1:02 PM

Similar Messages

Customer Hierarchy and product Hierarchy

Hi friends what is customer Hierarchy and what is product hierarchy?
please explain step by step with examples.
mail id: [email protected]
Thanx.

Hi Sirivas,
CUSTOMER 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 customers 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
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 subnodes 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.
Product Hierarchy:
The product hierarchy on the Basic Data screen is used to depict the competitive materials of competitor 1 in relation to those of competitor 2. Here, your own company and its materials are also regarded as a competitor and as competitive materials respectively. You can use this representation as a basis for market analyses.
Normally we enter competitive materials using material type WETT. When entering your own materials as competitive materials, you can, however, display the product hierarchy on the Basic Data screen for other material types too.
Requirement type determination is based on the "Origin of requirement type in requirement type determination"
In this field you can select an alternative search strategy (source):
Source 0 = Material master strategy, then item category and MRP type
Source 1 = Item type and MRP type strategy
Source 2 = Item type and MRP type strategy (as for source 1) with additional check of the allowed requirements type
e.g. If you set value "0" system will first strategy group in material master based on that it will determine requirement type and no value found then it will determine requirement type based on item category and MRP type.
Above settings can be found at SD --> Basic Functions --> Availability Check and transfer of requirement --> Transfer of Requirement --> Determination of Requirement type using Transaction
For make to order std strategy group 20 is used to which req type KE is assigned.
Check
Check in Tcode OVZH, what requirement class is assigned to your requirement type
Check in Tcode OVZG, what value is assigned to field "Consumption" in requirement class because that determines consumption posting.
The product hierarchy is used to group materials by combining different features. It is used for analyses and pricing. A product hierarchy can consist of up to Eighteen characters. Its features can be combined in various ways.
Example: A dishwasher can be described by product hierarchy 000010000200000002. This series of characters states that dishwashers belong to the category electrical appliances (series of characters 00001, position 1-5), and also to wet appliances (series of characters 00002, position 6-10) and, finally, to dishwashers (series of characters 00000002, position 11-18).
One can maintain the product hierarchy via transaction "OVSV" and "V/76.
Path = IMG-Logistics General-Material master-Setting for Key fields-Data relevant to SD-Define Product hierarchy.
The product hierarchy is maintained in the Basic Data view of the material master record, and is used for evaluation as well as price determination in materials management.
The standard SAP allows only 3 levels, but you can go up to 6 levels, for additional 3 levels u will have to take abapper help and add 3 more fields and corresponding data element into structure. So that in material master drop down you will see 6 levels.
The transaction which will be useful to change product hierarchies for material master will be V/76.
Yes, You can print the levels of the product hierarchy through a report.
Use the view SE16 - V_T179 (Table Name) to display Product hierarchy with level numbers.
Field Name is PRODH
Please Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula

What's use for Customer Hierarchy

Dear Guru
What's use for Customer Hierarchy? give me a step to config?
regards
Mohammed Renu.I

Hi Mohammed Renu,
CUSTOMER 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 customers 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
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 subnodes 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.
Please Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula

Customer Hierarchy Partner determination in a Sales Order using Payer ?

Dear SD Experts/Gurus
We use Customer Hierarchies extensively in Sales Orders for Pricing & Rebates and it all works fine.
The Hierarchy structure consists at the bottom level of a SoldTo linked to a Hierarchy Customer and many SoldTos can have the same Hierarchy Customer.
We set price conditions at the Hierarchy Customer and that all works fine.
We would like to change our Customer Hierarchy to link the Hierarchy Customer to the Payer rather than to all the individual SoldTos.
This is because we have many SoldTos linked to 1 Payer and this will allow us to have simpler Customer Hierarchy structures making it easier to setup and maintain.
I have changed the SAP configuration to do this and I can certainly maintain the Customer Hierarchy without any problem using transaction VDH1N.
But when I create a Sales Order, the Hierarchy Customer does not get pulled through to the Sales Order Header Partners based on the Order Payer and hence no Hierarchy Customer price conditions are pulled through.
Is what I'm trying to do possible in SAP ?
If so please advise how this can be achieved.
Thanks David
Edited by: David Steele on Apr 15, 2008 1:57 PM

Hello,
I have a similar requirement, although we are building the hierarchies directly in CRM (as we are with BP's in general), and I am using hierarchy category 01 - PRICING.
What I have found is that a sold-to BP must:
1. be assigned to a hierarchy node
2. appear TWICE (!!!) in the document part.det.procedure, once in partner function 000001 (sold to) and again in partner function 00000121 (Authorized partner: sold to).
When the sold to customer exists in both functions within the document, I am able to determine the hierarchy node properly.
Now, my question is, can anyone guess why the main partner (sold to) must appear twice??? or, is this an error in my customizing?
Thank you in advance for your help, and I do hope my observation can help others find a solution.
Regards,
Allon
PS in terms of customizing, I used the following:
partner function 00000001 - sold to
partner function 00000121 - Auth. Partner: Sold-to Party
access for Auth. Partner: 0017 - current partner: sold to *this copies the sold to partner into this partner*
partner function 00000076 - Hierarchy Node Partner
access for hier.node partner: CRM_PARTNER_G Pricing hierarchy
The last bit presupposes that the hierarchy is set up using hierarchy category '01 - pricing'.
Message was edited by:
Allon Riczker - Added configuration steps

Customer Hierarchy in COPA

I am a newbie and had a question for you gurus. When I am loooking at a profitab document I am noticing the CustHier fields are blank. Where is the customer hierarchy in COPA setup and how does it relate back to the profitab document?

Hi,
Refer to the table CE4XXXX, where XXXX = your Operatinc Concern Id.
The characteristics are stored in the data division of the table CE4XXXX for Operating Concern XXXX.
Other COPA tables are :
CE1XXXX - Line Items (Actual Postings)
CE2XXXX - Line Items (Plan Posting)
CE3XXXX - Summary Table
Hope this helps.
Regards,
Chirag

Customer Hierarchy download in CRM7.0 Web UI

Hi Experts
Need your expert advice on the below issue:
We are using customer hierarchy from ECC to SAP CRM7.0 for one of our client. I have performed the below steps to bring ECC customer hierarchy to CRM.
SAP ECC System:
1.Hierarchy node is created thru tcode- v-12
2.Customer hierarchy is created thru tcode- VDH1N
Replication steps in CRM:
1.Replicate Customer Hierarchy Customizing thru TCode- R3AS, download object DNL_CUST_THIT .
2.Assign ERP Customer Hier. to CRM hierarchy category in SPRO .
3.Replicate Customer Hier thru Tcode u2013R3AS , download object DNL_BUPA_KNVH.
4.Create account hierarchy thru Tcode- BPH_DNL , we need to create the hierarchy only for the sales area 0001,01,01. So I have selected sales the required sales area only.
5.I checked in web ui and found the result for account hierarchies.
Current Result:
a.ECC hierarchy downloaded, however descriptions for the hierarchy nodes are missing in CRM web ui.
b.Customer assigned to ECC hierarchy can be seen in the u201CAccount Hierarchy Detailsu201D assignment block , however I could not see the customers in u201C Assigned Accountsu201D assignment block.
6.Expected Result :
a.ECC hierarchy display with description in u201C Account Hierarchy Detailsu201D assignment block.
b.Display customeru2019s information in u201C Assigned Accountsu201D assignment block.
Can anybody support and provide the information if we are missing any configuration step ? or the result is the correct behavior of standard system ?
I would really appreciate your help on this.
Regards
Satish Rikhi

Hi Tanya
My issue is got sovled with SAP note 1398619 .However, for the second issue there is no finding.
I am assuming ,that is standard SAP CRM behaviour , if we assign any account in crm , that will be shown in the assignment block.
Regards
Satish

How to create a custom Hierarchy in IDT 4.0

Hi All.
I am trying to create a custom hierarchy objects in the Information Design tool, But I am not able to find it here as same sort like the universe designer in 3.1 or 4.0 . I have found the navigational path but I am not sure how I can use it as a hierarchical objects in my reports, Can anyone please suggest how to create a custom hierarchical dimension in IDT 4.0.
Thanks,
Navin

Custom Hierarchy are called navigation path in IDT. I will suggest to go through the navigation path tutorials below
http://scn.sap.com/docs/DOC-22087
Hierarchical objects are no different than any regular objects but they enable the drilling in drill mode in the report and you can create a cascading prompt on top of them..
If after going through this you still have any specific questions just let us know...

Customer hierarchy-Discount not flowing through

I am facing problem in customer hierarchy in pricing.
I have assigned account group 0012 to 001 all customer. 0012 is Main company who is not issuing orders. I think this may be due to Partner determination settings. However, I have set 3 levels 1D mai n office which is not issuing sales orders act group 0012 Set partner determination at customer master level and sales document header TA. In sales order in Partners tab I am getting 1D but not getting other like 1C nor 1B nor 1A.
Assigned sales area as well to hiegher level sales area, order type to "A" cust. hierarchy, VDH1N well maitnined 0012 act grp to lower level 2 company which both are 001 act group.
In VK11 maintained HI01 % discount different for head office & two branch office with same sales org, Distr Channel and division.
Here HO is given 2% discount and one branch office 5% and another 7%
When I am creating sales order for 7% branch, in pricing procedure it shows only 2% (HO) discount but not 7% for branch office. I have also tick marked in XD02 at billing tab price determination. In pricing analysis hirearchy 02 is having Exclaimation in Customer field. So why I am missing this customer field even though I have maintained that customer in VK11. Hope I have summarized all details. If any questions please feel free.
I shall appreciate if you know the resolution.

This is now resolved by proper settings in Customer Hierarchy

Customer Hierarchy not showing in sales document

Hi All,
I have used the standard hierarchy type (A) to create a 2(or 3) level hierarchy (top level node, 2nd level node and sold t party) and the hierarchy assignments look fine at the customer level. I have assigned the hierarchy type to the sales order type as well. But the hierarchy does not get carried over to the sales orders (contracts) when I create the documents. I am sure it is something really silly, but any idea what I might be missing or where to start looking.
Thank you so much for your help in advance...
Shubha Tandon
[email protected]

Have you Mainted Price determination in the custome masrter record of the billing Tab.
Have you correctly maintained the partner determinatin procedures.
Have you assigned Customer hierarchy to your sales area
Have you created Customer with 0012 Account group.
Now you need to assign the customer creatd using 0012 to the customer 0001 account group.
Have you maintainted the Customer heirarchy in VDH1n transaction..
Here you need to assign 0001 account group customer to 0012 customer
If u have maintained all these settings correctly you will get the hierarchy customer in SO.

Step by Tutorial for Creation of Customer Hierarchy in CRM System

Dear Experts,
I want to create a Customer Hierarchy in the CRM System. Need step wise tutorial to do the same with the help of an example. I already have the help.sap.com URL.
Please help.
Thanks & Regards,
Tapan

Customer hierarchies can be created by using transaction code BPH.
Regards.

How can I include Customer Hierarchy in Customer master IDoc -DEBMAS06 ?

Hi,
I am generating Customer master IDoc using basic message type DEBMAS06. But when I include customer hierarchy data while creating customer master, it is not included in any of the segments. The segment containing the data from KNVH is not included in standard.
How do I include this hierarchy data in the IDoc? If I create a segment, under which basic segment should it be included and how to update the data in the segment?
Can anybody help?
Points assured.
Best Regards,
Rajendra

Hi
You can use LSMW :-
1) Create a project , sub project and an object.
2) execute it from 1 st screen to enter the object.
3) You will find proces steps.
4) In Maintain Object Attributes choose Program Name RFBIDE00.
or I-DOC or the way you want the input to be.
5) You can proceed from there following the instruction..

Customer Hierarchy field not showing in change customer master

Hi all,
We are trying to upload customer master Hierarchy field A and Customer Number in XD02 But Customer Hierarchy field not displaying in XD02 i check in account group OBD2 and OB20 setting its showing optional entries only still its not showing in XD02 But while creating customer master in XD01 its showing
can any one guide me where i need config
Thanks
Rajesh

Hi,
You check out in OBD2 & in OB20,
R u selected right account group in OBD2, check it.
Kapil

Modify customer hierarchy in scheduling agreement

Hello everybody,
if I modify the customer hierarchy how can I update it in the scheduling agreement?
Is there a way to update it or I have to delete and create the order after the modification?
Thank you all
Francesca

UP!!!! Please help.

How to download customer hierarchy in Excel sheet?

Hi,
Good day.
I was able to display the customer hierarchy via transaction VDH2N however, I would also like to download and save this hierarchies in Excel but there was no such option in that transaction. Can anyone tell me how and where I can download the customer hierarchy, please? I wanted to downloaded exact details found in VDH2N. Please help.
Thank you and have a good day.
Kindest regards,
Lemily

Hi Saurabh,
Thanks for your immediate reply. The issue I have with SE16N is that it did not generate all complete and exact details for customer hierarchy that is found in transaction VDH2N. In VDH2N, I can see that there are 3 levels and other sub levels. But when I tried to use SE16N, it did not capture all levels, especially the sub levels. And I wanted to download or export all customer level that is found in VDH2N but this is not possible in SE16N.
Thank you and have a nice day.
Kindest regards,
Lemily

Customer Hierarchy Determination in Sales Order Header

Hello Gurus,
I am trying to determine how the customer hierarchy is being determined in the sales order for our instance of SAP. I can see 1D..1H get populated as partners so five levels are being bought in with 1H being the highest. The confusing part is how come 1A..1C is not being populated with any data. Wouldnt the system start at 1A and populate to 1E the five levels. Instead the partners for hierarchy are starting at 1D. How does the system not populate 1A as start point? Is each hierarchy nodes somehow linked to 1A..1H?

Did the hierarchy been assigned in t.code OVH4? If not, assign and test by creating a new sales document.
Regards,

Customer Hierarchy setup

Similar Messages

Maybe you are looking for