SD Customer Hierarchy in COPA customer Hierarchy

[Former Member]

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.

H01

|_H02-1

|_H02-2

|_H03-1

| |_C1

|_C2

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

[Former Member · Accepted solution]

Hi,

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!

Alex

[Former Member · Accepted solution]

Hi Alex,

Thanks for your very clear answer.

I have check all the points you specify, and only for the XD03 where i don't have any fields hierarchy assignment in the Marketing tab.

Everything else is ok when I test the derivation I have not value but the message initial value allowed

Do you know the reason why I don't have the marketing's tab field ?

Thanks

[Former Member · Accepted solution]

Hi,

That field is missing due to the customizing settings concerning the field status for the specific customer account group (transaction "ovt0", double-click on an account group, double-click on "General data" and so on).

Most likely, your problem is SD rather CO so it might be good to also review the customizing settings under SPRO -> Sales and Distribution -> Master Data -> Business Partners -> Customers -> Customer Hierarchy

Regards,

Alex

[Former Member · Accepted solution]

Hi Alex

Many Thanks, You have solved my problem, I could go ahead now.

Merry Christmass and happy new year.

Louis

[waman_shirwaicar]

Hi,

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

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

regards

Waman

[Private_Member_10672]

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.

Thanks,

Nirav