Use of customer hierarchy in CO-PA

I'm new in FI CO-PA modules, but I have to configure CO (cost analysis). We actually used customer hierarchy in SD fully with success but we encoutered a problem with our Customer hierarchy in KE30.
When we try to analyse the sales by the customer hierarchy we have a message saying that the hierarchy is not unique.
Actually we have defined the hierarchy as follow:
first node
customer        480000
sales org        1040
distr chanel    F1
division           F1
customer        480000
sales org        1040
distr chanel    F1
division           F2
customer        480000
sales org        1040
distr chanel    F1
division           F3
We have used this structure because we have different conditions depending of the division
My first question is: Is it this structure that provoque the message in KE30?
The second one is: How I must have structured the hirarchy in order to be able to have different condition on each division for the node 480000?
Thanks for your help on that topic.

Hi,
     The data structures of the hierarchy in SD and CO-PA are not quite the same. In SD, there is a dependency between the customer number and the sales organisation. So you can have the same customer number several times in the hierarchy. However, in CO-PA the dependency with the sales organisation does not exist. A check is performed only on the customer
number.
    We recommend that you create a new hierarchy in CO-PA (transaction KES3). If you use SD customer hierarchy in COPA then there will also be problems in reporting (KE30).
     Check the SAP referenced characteristics CustomerHierarchy01,CustomerHierarchy02 and CustomerHierarchy03 ? (tcode KES1).
regards
Waman

Similar Messages

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

Find contract (outl. agreem.) at order item level by customer hierarchy

Hi Everyone,
I've a requirment for the next functionality is SAP.
Find contract (outl. agreem.) at order item level by customer hierarchie.
Standard SAP can only use the customer hierarchy to find a contract at order header level. This has not the result we want, beceause all or a selected group of items will be copied to the order and this process is not usefull with EDI order input.
Does somebody know how this functionality can be created in SAP? Build the functionality with ABAP is no problem for me.
Thx.

Hi !
I know its quite late for the answer but I just saw your question.
In the customising of the Sales doc type (VOV8), in the 'Transaction flow' section, in the first field for Outline agrmt mess. entry of either B or D or F should help.
Reward if helpful.
Regards,
PATHIK

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

Rebate agreement with customer hierarchy

Hi,
I want to use customer hierarchy for customer rebates where in the accrual rate with scales shall be maintained only the high level customer. Invoice values of all the subordinate customers should e accrued using this rebate agreement.
Have learnt about extended rebate agreement functionality wherein such a scenario can be adopted.
Looking for a solution immediately to meet the week end deadline for POC.
Regards,
Rajesh Mohapatra

Thanks Veera !!
In this case my rebate receiptant is one only.
I am trying to use a customer hierarchy node (scaled down customer code w/o partners, recon account etc.) and made it relevant for Rebates & Price determination.
All the customers in the hierarchy are also relevant for Rebates.
But the condition record maintained with hierarchy node is not getting picked up the billing document as system is looking for the subordinate payer instead of the hierarchy node.
Not using the same node as Rebate Receiptant. Incase of using wrt the below link, am getting error as "Customer for function PY may not have account group 0012".
Ref : http://help.sap.com/saphelp_ides/helpdata/en/5d/363ec3583f11d2a5b70060087d1f3b/content.htm
Regards,
Rajesh Mohapatra

Functional module to obtain the Customer hierarchy

Hello Experts,
I need some information regrading Customer hierarchy step. Could anyone please assist me the function module used in customer hierarchy to obtain the hierarchy.
Thanking you,
SS.

Hello Pratima.
Thank you for your quick response.
Could you please provide me the configuration steps for customer hierarchy as this is our action event.
Thanks in advance.
Regards,
SS.

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

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

Assignment to customer hierarchy(VDH1N)

hi friends,
can anybody help me to assign customers to the customer hierarchy
i am facing issues and getting errors like higher level is not defined,lower level is not defined and sales organization is not permitted etc...
thanks
sreeni...

Hi,
To avoid this need to check or follow the below customization.
1st Need to define Define Hierarchy Type say standard A and assign Partner function 1A ( this as be be defined in partner fucntions)
2nd as said need to define partner functions as 1A, 1B,1C and 1D.
when u frist define 1A give partner type KU, error gruoup 07, higher level as 1B, cust hierarchy type A.
Then defien 1B give partner type KU, error gruoup 07, higher level as 1C, cust hierarchy type A.
Then defien 1C give partner type KU, error gruoup 07, higher level as 1D, cust hierarchy type A.
Then defien 1D give partner type KU, error gruoup 07, cust hierarchy type A.
3rd assign the account group and higher level accout group to customer hierarchy
customer hierarchy type A, account group 0001 and higher level account group 0001.
4th then assign the sales area you are using to customer hierarchy type.
customer hierarchy type is A, and your sales are, same sales area as hight level too.
5th assign the customer hierarchy type to the sales order.
You can change the standard and use Z for partner funtions and for customer hierarchy type
Ensure that the partner functions are assigned to sales document partner procedure too.
Regards
vK

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 using MDM

Hi,
We would like to build customer Hierarchy using MDM that would match the DUNS hierarchy. Is this possible to Model this using MDM?
Thanks,
Sanjay

Hi Sanjay,
I never tried to analyze the DUNS hierarchy. But, hope you know that MDM supports different table types and Hierarchy table is one among them.
Regards,
Rajani Kumar

Customer Hierarchy Creation by using Flat file

Hi all,
I am trying to create Customer hierarchy (Transaction - BPH), from flat fileu2026
Here, I find like BPH transaction using FM u2018BUPA_HIERARCHY_SAVEu2019 to create hierarchyu2026
Nowu2026 I want to do same thing through Flat file and my file contains below information
First section:
1. Hierarchy Category
2. Hierarchy Tree
3. Tree description
Second section:
BP ID information likes u2013
1. ABC (Higher level BP) u2013 First node
2. XYZ (Next level BP) u2013 Second node
Here, I want to create customer hierarchy with header details (given in first sections) and need creates nodes (given in second section),
Can any one tell me in which way I need to pass data to FM to create hierarchy?
Thanks in advance!!!
Regards,
Sreenu Valeti

Try using BAPI_CUSTOMER_HIERARCHIE_INS

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

Use of customer hierarchy in CO-PA

Similar Messages

Maybe you are looking for