Skip to Content
author's profile photo Former Member
Former Member

SD Customer Hierarchy in COPA customer Hierarchy

Dear all,

First of all I wish you a merry Christmas.

Well, my problem is :

I have a compagny with 1 sales org. and 3 divisions. Every customers are define on the same basis on the 3 divisions on 3 levels of hierarchy.





| |_C1


this for each division.

My problem is the characteristics HIE01 to HIE03 are not filled with the right value (it's blanks)

I have check in KEA0 I check that the fields HIExx were selected and everything is activated

I have create a distribution rule for customer hierarchy

But the fields remain blanks.

Did I miss something that can I do in order to use SD hierarchy in COPA ?

Thanks for your reply

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Dec 22, 2011 at 02:31 PM


    Customer hierarchy is maintained under specific Sales org., Distr. channel, and Division. By default, Division in CO-PA is derived from Product, whereas Customer hierarchies may be maintained under other Divisions. In such case, derivation doesn't work simply because no hierarchy exists for the Division that is populated in CO-PA.

    In general, you need to make sure that your customizing is aligned to the following settings:

    Transaction XD03

    Enter the customer number for which no hierarchy levels appear in CO-PA, and check whether field u201CHierarchy assignmentu201D is filled with value (u201CGeneral datau201D, tab u201CMarketingu201D). The number that youu2019ll see there corresponds to the hierarchy level that should at least have been filled in CO-PA.

    Transaction VDH2N

    Review Customer Hierarchy by filling-in the appropriate selections (as in your CO-PA line item); spot the "_Customer hierarchy type_" (usually has value u201CAu201D) and also check the "_Validity date_".

    Transaction KEDR

    Make sure that a derivation of type u201CCustomer hierarchyu201D exists with the following details:

    u2022 u201CCustomer Hierarchy Typeu201D is the same as in the previous step

    u2022 u201CSource fieldsu201D: VKORG, VTWEG, SPART, KNDNR, HIE03, HIE02, HIE01. For KNDNR, HIE03, HIE02, HIE01 the indicator u201CInitial value is allowedu201D might also need to be checked

    u2022 u201CTarget fieldsu201D: HIE03, HIE02, HIE01

    u2022 Make sure that no inappropriate conditions exist

    u2022 Test the derivation (F8) within initial screen of KEDR by entering appropriate values for fields VKORG, VTWEG, SPART, and KNDNR. If no values appear for HIE03, HIE02, HIE01, then press button u201CAnalyze derivationu201D. On the next screen locate your derivation step, expand the line and review the relevant comments

    Merry Christmas and a happy new year to all of you!


    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 22, 2011 at 11:26 AM


    Merry Christmas to you too.

    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


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



    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Waman/Louis,

      We don't have set up in KES3 nor any WW characteristics nor any derivation rules are defined for customer hierarchy in COPA. However, in KE30 report definition 'hierarchy' box is checked for customer & therefore we could see the customer roll up in COPA report.

      But, something got changed, not sure what, but we're getting the message that "Hierarchy is not unique. Each characteristics value must be assigned to exactly one node. Please check your hierarchy".

      Now, we're able to execute COPA report but unable to show customer roll up based on hierarchy.

      Do you have any suggestion to offer? VDH1N shows nothing abnormal. Please let me know.



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.