on 04-07-2008 1:09 AM
Hi ,
Let me explain my scenario ....
New Condition type to be added : ZSUR- surcharge (fix amount)
Access sequence tables : 1 - sales org/division/customer
2 - sales org/division/customer group
Here is what I want to achieve :
If system finds a condition record, it should exclude this surcharge for the customer, instead of applying it.
In other words : I want to maintain condition records for only those customers for which I dont want to apply this surcharge.
Reason being ,there are very few customers for which this surcharge should not be applied and +I do not want to maintain conditioon records for every new customer +
You can also call this requirement as a Customer Specific Surcharge.
Please let me know if this is possible to do ..
thanks
Dona
Edited by: BW FirstStep on Apr 6, 2008 7:14 PM
Edited by: BW FirstStep on Apr 6, 2008 7:17 PM
Dear Dona
You can try with my suggestion given already.
thanks
G. Lakshmipathi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Laxmipathi ,
Thanks for replying and understanding my issue throught two different posts...
I cannot use the method you suggested because :
We have only one pricing procedure right now (we are in live environment), and for such a small change I do not want to build(copy) whole new pricing procedure.It will need lot of training on users part to maintain master data.Instead I would like them to maintain condition records, and make them add this condition type manually for new customes...
Thanks a lot for your sggestion though,it really is an option
Dona,
Refer:
Dear Dona
Let us assume you have some regular 100 customers and 10 special customers. In your customer master, maintain the customer pricing procedure differently for these 10 special customers. That is if you maintain 1 for 100 customer, maintain 4 (you can maintain any numeric value) for these 10 customers.
Now go to OVKK and maintain the same pricing procedure for the combination of sales area, document pricing procedure and customer pricing procedure. So in your case, same sales area, same document pricing procedure and same condition type but different customer pricing procedure. By doing so, whenever you raise sale for those special customers, the new surcharge will flow into your sale order automatically.
thanks
G. Lakshmipathi
Edited by: BW FirstStep on Apr 6, 2008 11:10 PM
Dear Dona
If you once again go through my posting, you come to know that I have suggested to maintain ONLY a different customer pricing procedure in customer master. That means, for regular customers, you maintain 1 and for special customers, maintain some other numeric value.
By doing so, you are not creating a new pricing procedure but assigning different combinations in OVKK as follows:- (this is only an example)
SOrg::::DChl::::Dv:::DoPr:::CuPP:::Pr.Pr:::::::CType
2000:::::50:::::::00:::::A::::::::1::::::::ZPRIPR:::::PR00
2000:::::50:::::::00:::::A::::::::2::::::::ZPRIPR:::::PR00
From the above combination, you are not only maintaining the same pricing procedure but also you are differentiating the customer pricing procedure by which whenever you create sale order for those special customer, the same pricing will be fetched with additional surcharge condition type.
thanks
G. Lakshmipathi
Guys ..
I find out the solution for my problem..
build the access sequence with 2 tables.
1. customer group
2. material
Maintain the first table with the customer group you want to exclude with surcharge of $0.
Maintain the second table with a material with surcharge of $10
This is possible only if we have a material which would be present in all orders and we luckly suppose to have that scenario.
thanks for all your help guys
Dona
I think its possbile by condition exclusion grps where u maintain u r related fixed cnd types that u want to give for a particular customer or a customer group
othr wise
make that cnd type as manual in the pricing procedure and give as to whom u want or to whom not.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
110 | |
12 | |
11 | |
6 | |
5 | |
4 | |
4 | |
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.