Customer Hierarchy in Pricing

Hello,
Please tell me how Customer Hierarchy is used in Pricing? Concept?
What are the config. we have to do?
How do we track it in the pricing?
Thank you.

dear emre
Customer Hierarchies
Use
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 customers 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 refer http://help.sap.com/saphelp_47x200/helpdata/en/dd/55f4d9545a11d1a7020000e829fd11/frameset.htm
rewards if it helps
siva

Similar Messages

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

Pricing not determined based on Customer hierarchy

Hi All,
I searched the forum for the specific issue, but could not find a proper solution.
I have a specific scenario where we are migrating from 4.6C to 6.0. The hierarchy is already maintained in 6.0 version in a way which we need to adopt it. The level 1 in 4.6 C would become level 5 in ECC 6.0. The pricing procedure is adopted as per the 4.6C version where the key field for discounts are maintained as Customer hierarchy level 1 as level 1, now when we are raising a sales order, for none of the levels the price is getting determined, even though the price determination field is checked in the customer master. The system says initialized field, it is not able to trigger the HIENR01, HIENR02, HIENR03 field, even though the pricing records are maintained.
Looking for your feedback.
Thanks & Regards
Aravind

Aravind,
Even though the price determination field is checked in the customer master. The hierarchy may be out of sync. You can verify this by looking at table KNVH for 1 of your hierarchy nodes and viewing field prfre. This is required to = X for the hierarchy fields to be populated during order entry. If you find that it is blank and out of sync with the customer master, then you need to go into Process Customer Hierachy(VDH1N), enter your highest level node and execute, Once in the maintenance view of the hierarchy, click in menu hierarchy-> Update programs-> All; this will sync up the hierarchy from the customer master and make these pricing relevant. You can verify in this screen as well by looking at the 'Relevant for Pricing' flag is set. Hope this helps.
Matt

Customer Hierarchy pricing

Hi
I am trying to create an access sequence including the hierarchy node for which I intend to maintain the pricing, eliminating the need for maintaining condition records for material prices for low level customers.
Could you tell me what field I should use in the field catalogue to achieve the above?
Will be grateful if anyone can help me with the config steps for customer hierarchy pricing.
Thanks
Kumar

Hi Shiva
Thank You for your reply.
We want to maintain list price (PR00) at Hierarchy node level. Does hierarchy level pricing only work with condition types with HI01.
My requirement to maintain one level of hierarchy with pricing maintianed at Hierarchy node level. When a sales order is created for low level customer, system should automatically determine the price from hierarchy node.
Please help.
Thanks
Kumar

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

Authorized Partners for Release Orders with customer hierarchy

Hello everyone,
      I have created a value contract with order type WK1, in the order type WK1 configuration, choose rule B for check partner auth. field, namely we want to use
customer hierarchy to detemine the sold-to-party for the follow-up release order. Also I have created the customer hierarchy with hierarchy type A. There are
four levels under this hierarchy, it contains four customer nodes and four customers. Every customer is belong to a customer node. The partner determination
for the customer hierarchy have alredy done, I can see the customer hierarchy "1D" at the partner tab of header in the contract, but when I release the sales
order against the contract, input a low-level customer number, still got the message "partner X is not authorized to release from contracts.".
     I want to know if I missed some settings in order type configuration or the copy control from WK1 to OR. If this scenario need integrate with CRM system? I
have found some related information, just list below:
    Partners in the hierarchy (Rule B)
If the partner who wants to release against the contract is the sold-to party of the contract or at a lower level in customer hierarchy to the sold-to party in the contract, the system accepts the partner as the sold-to party for the release order.
If rule B is defined for the contract type, you can search for authorized partners for a release order using the contract number. Equally, you can search for the relevant contract for a release order using the partner number. In this case, the partner authorization rule is irrelevant.
Prerequisites
If you wish to use group hierarchies other than pricing hierarchies to determine authorized partners, you must have created a hierarchy category and a hierarchy:
To create the hierarchy category, go to Customizing for CRM under Master Data --> Business Partner--> Business Partner Group Hierarchy.
To create the group hierarchy, go to the SAP Easy Access Menu and choose Master Data --> Business Partners --> Maintain Group Hierarchy.
Note that you can only create group hierarchies in the SAP GUI and not in the People-Centric user interface.
You must have activated the necessary settings for the sales contract and the release order in the IMG for CRM. For more information, see Transactions ---> Settings for Contracts -->Define Settings for Authorized Partners.
Thanks!

Hi,
In transcation VTAA at item level have your own cory requirment code which will calcullate net value of the doc, hope this works out
regards
sriky

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

Customer Hierarchy creation

Hi all,
I encounter a problem when trying to create a Customer Hierarchy in CRM, in the tcode BPH , I enter the hierarchy category as pricing , but i got the error
You cannot create hierarchy trees of this category
If the delta download for the ERP customer hierarchy is active, you cannot create a hierarchy tree of the category "Pricing" in CRM.
For this reason, you should establish that pricing based on the customer hierarchy and BP group hierarchy gives the same results in the ERP System and in CRM".
But I did not understand what does it mean, could anybody throw me a light?
cheers,
hy

Hi Ginnie ,
Have u pulled all the Pricing related Tables from ERP to CRM.
It has a dependency because pricing works on Customer Pricing Procedure and Document Pricing Procedure .
Regds,
Sunil Nair

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

Number of partners that can be linked in a Customer Hierarchy

Hi!
We have requirement to map multiple partners to a customer hierarchy account. Would be glad to have some insights on:
1. Any limitation on the number of partners that can be linked to any hierarchy node (even the highest)?
2. If yes, how many?
S.Kannan

Hello,
This is a community forum for technical questions & issues.
For question regarding pricing / licensing please contact a Microsoft sales partner or licensing expert.
Call (1-800-426-9400), Monday through Friday, 6:00 AM to 6:00 PM PST to speak directly to Microsoft licensing specialist.
http://www.microsoft.com/en-us/server-cloud/products/sql-server/buy.aspx
Olaf Helper
[ Blog] [ Xing] [ MVP]

PLZ provide Scenarios pertaining Customer Hierarchy..

Hi All,
Can u plz provide/explain the Business scenarios pertainng Customer Hierarchy which cna be configured.
I have configured the basic settings pertaining Customer hierarchy but want to know where all is it used.
THNX in advance,
Subbz..

hi,
One use of customer hierarchy is in pricing
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.
reward if helpful
thanks,
Krishna Prasad

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

What is customer hierarchy

hi friends
What is customer hierarchy?
regards

Hi,
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. Customer hierarchies are used during sales order processing and billing for determining pricing, including rebates. Customer hierarchies may be useful for your organization if you trade with customers who have complex, external structures that you need to take into account for pricing.
Hope this will help.
Reward point if helpful
Thanks,
Raja

Customer hierarchy Blueprint

Hi
Could anyone send me any document related to Customer hierarchy blueprint design phase on my id
Removed by Moderatorl
Kind Regards
Sim
Edited by: Lakshmipathi on Aug 16, 2010 7:54 PM
Dont deviate the forum rules by asking to share the information personal mail id

Hi,
To start with you can ask business what is the need for a customer hierarchy at all. Since itu2019s a very complex chain you need to be clear on why you are creating a hierarchy in the first place.
Other areas where you would want clarity could be:
Is it for reporting stuff or pricing? If they want specific controls on account groups, naming conventions of the hierarchy customers so that the end users can easily identify the hierarchy level by looking at the naming convention, if you need to have hierarchy relevant for rebates etc
We can have a hierarchy with 26 levels in SAP. This is the maximum level that is supported by standard SAP.
Hope this will help you to take things forward.
Regards.
Meera

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

Customer Hierarchy in Pricing

Similar Messages

Maybe you are looking for