on 01-13-2009 11:40 AM
Hello,
I have created a customer hierarchy as follows :-
high level customer A , acoount group as a node
low level customercustomer B, account group sold to party.
1) if i create pricing condition records for customer A. do the prices get detemined for sales order for customer B ????
2) if i create a material listing condition record. can i create a record for customer A and then when sales order is made for cusomer B, then do the materials which are listed for customer A becomes listvalid for customer B ??
regards
sachin
You have to create pricing conditions with access sequence dedicated for customer hierarchy - you can base it i.e. on standard access sequence HI01 or HI02.
Regards,
Marcin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can use listing/exclusion of sold-to party for many ship-to parties.
As far as I know the customer hierarchy is not supported in standard listing/exclusion. However as it uses standard condition techique it should be possible to biuld such a listing access sequence and tables to use customer hierarchy, probably with a piece of development (transfer of customer hierarchy fields to listing/exclustion communication structures KOMKG, KOMPG or KOMGG).
Regards,
Marcin
Hi,
many thanks for the same. some more adivce needed sinc ei have never done hierarchy pricing.
i just saw in the HI01 access, there is one table 64 repeated 7 times. if i see the techincal field information, it shows information as folllows :-
condition field I/O structure document field
vkorg komk vkorg
vtewg komk vtewg
sprat komk spart
Hienr Hienr01
like wise for all the seven entires Hienr01 is 02,03,..................07
what does hienr and Hienr01 means ?? they originate from where ???
There are several accesses in this access sequence because you have 7 levels customer hierarchy. when you create your won access seq you have to create 7 entries for 7-level hierarchy and assign as the field HIENR with KOMK-HIENR01..07 respectively. When the system determines the price it checks first if condition record for the customer nearest in the hierarchy - if not found it looks for customer deeper in the hierarchy ans so on until it gets to the top of the hierarchy.
Kind regards,
Marcin
Hi,
maitain pricing with customer hirarchy table(64)
Do correct me if iam wrong.
Regards,
Reddyy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Hi,
many thanks for the same. some more adivce needed sinc ei have never done hierarchy pricing.
i just saw in the HI01 access, there is one table 64 repeated 7 times. if i see the techincal field information, it shows information as folllows :-
condition field I/O structure document field
vkorg komk vkorg
vtewg komk vtewg
sprat komk spart
Hienr Hienr01
like wise for all the seven entires Hienr01 is 02,03,..................07
what does hienr and Hienr01 means ?? they originate from where ???
Hi
Heinr (KUNNR-HEINR) feild is related to KUNNR but this is related to customer hierarchy KUNNR only
You might be having customer hirerchy , customer hirerchy 1 etc upto customer hirerchy 7 in the condition table
Go to condition table change mode and check wheather you have customer 1, upto customer 7 (KUNNR-HEINR) combination or not
Regards
Srinath
User | Count |
---|---|
108 | |
12 | |
11 | |
6 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.