PO Condition Value Mandatory

[a_ahmed]

Dear Gurus,

I have an issue where I have to make PO item condition value as mandatory. At present the condition type is populated based on the calculation schema, but the business wants the value to be maintained for that condition type prior to saving the PO.

I tried changing the indicator to "Required" in calculation schema, but it does not work. Meaning, I can create the PO without specifying any value for this condition.

How could I make it mandatory?

Regards,
Azhar

[BijayKumarBarik]

You can use standard routine or design a routine use for the condition type in MM pricing procedure in 12th column for your requirement.

[mathewgeorge]

Hi,

If you select the automatic option in M/08 for the particular condition type and create condition record in MEK1 for the condition type, the condition type and value will flow to the purchase order.

Mathew George

[a_ahmed]

Dear Mathew,

I would not want to maintain the condition record for this condition type. I just need system to ask me for the value for this condition type in Pricing procedure while creating the PO. I have checked "Required" indicator in Calculation Schema - Control Data

but in PO, i can save the PO without giving any value to this condition .

could you please suggest me, how to achieve my requirement?

Regards,

Azhar

[VeselinaPeykova]

Do you see a popup asking you what to do with the purchase order:

If yes, then in my opinion this is the correct behavior - to be able to save the order as held and maintain the required information at a later time.

If you do not see such popup - check first if you are using the correct pricing procedure.

If this is the correct procedure - use the pricing analysis to understand why the condition was not taken into account in this specific order - e.g. there may be a pricing requirement as a result of which the condition is ignored.

If still no luck - debug, the message that you should be looking for is 06209.

[a_ahmed]

Dear veselina.peykova,

My requirement is to make a particular condition type mandatory in PO pricing Procedure. I have checked "Required" indicator in the Calculation Schema - Control Data , but still while creating the PO, I am not being asked for the condition value.

Regards,

Azhar

[VeselinaPeykova]

a.ahmed I already understood that you set a condition as required and that you can still save a PO without maintaining the required data. You wrote about this in the question, there is no need of repeating this information.

Still, it does not answer my question about the popup - do you see it or not?

It is also unclear what is the outcome of the troubleshooting steps performed so far:

• whether the correct procedure was modified;

• whether there is a pricing routine as a result of which the condition is ignored;

• whether there is an existing record that is determined;

• what you discovered after debugging.

[a_ahmed]

Dear Veselina,

I do not see the popup at all while saving the PO. In other terms the PO is saved directly upon clicking on "Save" button in ME21N.

• whether the correct procedure was modified;Yes

• whether there is a pricing routine as a result of which the condition is ignored;

• whether there is an existing record that is determined; No

• what you discovered after debugging.- The condition value is not being checked. Only condition is being checked.

Regards,

Azhar

[nishsivap]

Hi Azhar,

I have used this option in past but the only difference from your case was that the condition type which i used had a condition record been maintained against it and the condition was not allowing manual entries. In those cases, when the system was not able to find a condition record then it was giving a message " Mandatory pricing condition missing ".

In your case since you don't want to have a condition record then i believe writing a logic as part of a requirement would be the next best feasible option.

Regards,

Nish

[VeselinaPeykova]

Nishanth Sivaprasad

Actually, you do not need a pricing requirement to prevent price determination via condition records, you can simply set "Manual only" in M/08.

Azhar Ahmed

If the condition is not determined at all and if you are using the correct procedure - maybe you need to debug a bit more with the help of an ABAP developer to find the root cause, this does not seem to be standard behavior (I assume that you test with newly created documents after you imported the customizing changes).

Edit: now I saw the other screenshot - you have the ZOCR condition determined, which is why you do not see a message for incorrect entries. Your question is not about having a mandatory condition, but about specifying a value greater than zero. Most probably the easiest way would be to use limits for conditions (maintenance view VV_T685Z_M2, IMG node Define Limits).

[a_ahmed]

Dear Veselina,

I tried with limits as well. No luck. I believe, we have to go for an enhancement, whilst saving the PO, checking the value for condition type to be greater than Zero.

Regards,

Azhar

[VeselinaPeykova]

Azhar Ahmed

What I described - the combination of manual mandatory condition and setting condition limits works in my system quite well, probably you did not configure something correctly.

In my test case first I am asked to maintain the missing condition (because it is not determined automatically) in the order. I enter the condition. If I try to save with condition value zero, I see the message:

If I do not enter a suitable value, I cannot add the condition to the PO, if I do not add the condition, I can only hold the document and process it at a later time.

No need for enhancement, this is can be done via standard customizing.