on 08-04-2009 1:05 PM
Hi
There is a manual header condition (Z0L1) in one our pricing procedure which I want to set to inactive or make it statistical during sales order (doc type Z9) creation in some scenarios.
How can I achieve?
Can I use user exit USEREXIT_PRICING_CHECK (Program MV61AFZA) and what code should I write here. Any help would be highly appreciated
Regards,
Javed
Thanks for your replies. Basically this condition type is a manual condition type which will be entered in sales order and then will be available in billing document. But when there is a return order created with reference to that billing document then I want that the manual condition is not deteremined in the return order.
I tried by assigning a requirement to the condition type in pricing procedure but seems to be pricing requirement don't work for manual header conditions. Then I tried to assign a condition value formula and tried to set the value to zero in case of return orders but that also did not work.
Then I also tried to apply the same logic in user exit USEREXIT_PRICING_CHECK in the following programs
LV69AFZZ
MV61AFZA
But still it did not work. Any help would be highly appreciated
Regards
Javed
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
For making certain condition type optional, please select your pricing procedure in the following path:
IMG--> SD --> Basic function --> pricing --> pricing control.
Here if you want to make the condition type statistical then put a tick mark on on the check box "Stat". If you want to deactivate
the condition type then remove tick mark on "mdt" check box if present. then write a code in which you have check the
table "komv". For deactivation set komv-kinak = 'X', then the condition type would be inactive.
Regards,
Sarthak
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Javed,
I would suggest you to write a pricing requirement to trigger this header level condition.
Clone the reqirement 2 and add your extra logic.
KOMK and KOMP structures are populated at this level.
KOMK-AUART contains your doucument type.
Regards,
Sai
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Javed Ihsan,
Well, if you want this condition price will be always statistical just define it as statistical in the pricing procedure (there is a check box called statistics). If you want this condition price won't be always statistical, well in this case create a Requirement (the requirement is developed by ABAP) to doesn't allows to enter this condition price when your particular scenarios happened and assign that Requirement into the pricing procedure.
Thanks,
Mariano.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
91 | |
7 | |
7 | |
4 | |
3 | |
3 | |
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.