Sale Order Excise Value should not be zero

[Lakshmipathi]

Dear Friends

With the User Exit MV45AFZZ Form:: Userexit_Save_Document_Prepare,

we have written a condition that while saving the sale order, if the excise condition value JEX2 is zero, order could not be saved and this is working fine for normal process.

But in some cases, we need to explode the BOM in sale order. In this case, the above user exit is checking for components excise value which should not be the case. In fact, we tried to distinguish with item category for the above exit but the item category structures are not flowing in a particular area of user exit.

My requirement is that for BOM exploded items, the above condition should not trigger for excise value in sale order. It should trigger ONLY for Header Material. How this should be achieved??

thanks

G. Lakshmipathi

[Former Member · Accepted solution]

Hi,

Please try to assign a requirement against the condition type JEX2, to be triggered only in case of the Header material.

You can distinguish that based on the Item cateogry, as the item cateogry for the header material in the sales order will be different with the other materials.

Once you are able to achieve the same, you can very well move ahead with your earlier development.

Reward points if this helps.

Regards,

Harsh

[Lakshmipathi · Accepted solution]

Dear Harsh

Thank you very much for your suggestion. Will work it out and reward suitably. Till then please bear with me.

Meanwhile, I am also expecting some more suggestions from others.

thanks

G. Lakshmipathi

[Former Member · Accepted solution]

try to define surcharges and discounts that are dependent on the characteristic values assigned, in the form of variant conditions.

you can use dependencies to determine when these conditions are active.

[Lakshmipathi · Accepted solution]

The problem is solved.

Actually in the above user exit, we had looped thru' xvbap for the item category type NOT equal to 'Order Type'.

Then, we read the xkomv table with two keys JEX2 and POSNV ( referring to vbap-posnr) and checked if condition value is null, if so trigger the error message.

In this way, though the xvbap is not dynamic in that form of userexit, the reading of xkomv helped to achieve

our purpose of triggering the error for header materials.

thanks

G. Lakshmipathi