on 12-31-2014 1:30 PM
Hi Gurus.
I have some question regarding the customer hierarchy pricing. Let me explain my problem on some example.
Customer X01 represent the highest node in the hierarchy.
Customer X02 the node below X01.
Customer X03 the node below X02.
Pricing in the customer master is set. System is synchronized.
Now we want to set up a condition record (discount). Condition table consists of:
- sales organization (vkorg)
- distribution channel (vtweg)
- division (spart)
- customer hierarchy (hienr)
- material (matnr)
Whereas we have 4 access onto the condition table (access on hienr with HIENR01, HIENR02, HIENR03, HIENR04 respectively).
Now we create a condition record for the customer X02.
When a sales order is created for the customer X03, the discount is determined based on the condition record.
However when we create a sales order for the customer X02, the discount does not get determined at all.
Does anybody have an idea about a quick and standard solution?
Thank you very much.
Hi Norbert,
Go to VDH1N, give the customer, sales area and hierarchy type and execute.
In the structure as shown below, check relevant for pricing is ticked for all or not?
if you find the case as below where it is not ticked for all.
make sure price determination is checked in master data and then from here
Go to Hierarchy- update programs- All as below. It will take few minutes to update and then you will see that relevant for pricing has been checked and then click on save.
After that try to create order and it shall work.
Let me know how it turns out.
Regards,
Aayush Jain
SAP SD Consultant
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Aayush,
thanks a lot for the advice. However, like i wrote, the pricing indicator in all relevant master data is set. As well the system is synchronized (means programs have been updated).
I think it is because the system doesn't use the current customer number when searching through the tables. That means, when an order is created for the customer X02, the system accesses the table with the customer X01 (HIENR01). But not with X02. I think i will extend the access sequence with one additional step (access on HIENR with KUNNR).
Hi Aayush.
i have now realized that the hierarchy partner determination might incorrect. At least i think this based on the available SAP documentation.
In my system the following partner functions get determined when creating an order for the customer X02:
Customer X01 (highest node) -> partner function D1
Customer X02 (the node below X01) -> just partner function AG (sold-to)
I think the customer X02 should as well become the partner function A1 as the lowest node in the hierarchy.
What do you think?
Hi Atul.
It is.
1A Customer hierarchy 1 | B |
1B Customer hierarchy 2 | B |
1C Customer hierarchy 3 | B |
1D Customer hierarchy 4 | B |
I have as well tested in IDES system. It works the same. The entered customer number (sold-to) doesn't get determined as a customer hierarchy partner. Thus, the pricing determination cannot work as expected either (see my original problem).
However based on the documentation it should:
User | Count |
---|---|
89 | |
7 | |
6 | |
3 | |
3 | |
3 | |
3 | |
3 | |
3 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.