How can I change the price of purchase orders?

[former_member1132919]

I want to automatically change the price when creating a purchase order based on the rules that have already been designed.

The rules are very complicated，so I put them in the table. I can use some factors such as mantr and vendor to get a rule.

[DominikTylczyn]

Can't you implement your rules with pricing conditions?

[former_member1132919]

I've tried using pricing conditions, but the requirements are too complex and the pricing conditions only meet part of the requirements. I need a way to match more complex pricing in a global way.

[DominikTylczyn]

Why don't you put your logic into condition calculation form? The form is a piece of ABAP that calculates the condition value. This way you don't need to update purchase orders and your logic will trigger during pricing at POs creation.

[former_member1132919]

There are several main reasons. The first is to reduce the filling in of fields when creating materials, only use the material description, the second is that the price of the material is determined according to the formula and its own properties, the formula changes over time, and the third is to minimize the configuration of each material.

Pricing conditions are convenient, but when creating a new item, it means that users without permissions need staff to modify some configurations. This is my current understanding, I hope you can provide better ideas, thank you.

[DominikTylczyn]

I guess now you are talking about pricing conditions determination. Indeed to have pricing determined automatically you need to define pricing conditions in MEK1, MEK2, MEK3 (create, change, display). The conditions are determined based on fields values in purchase orders e.g. material number, vendor number etc. However you can set up pricing procedure any way you need, e.g. based on purchasing organization only. This way a single condition record will cover all purchase orders, for any materials in the purchasing organization.

Then you can put all your custom logic, with all its complexity into pricing into a routine for alternative calculation of condition amount, i.e. this field in the price determination schema:

In my opinion it is a simpler way to implement your requirement as compared to PO creation and change of its price later on.

[former_member1132919]

Thank you very much for your guidance, I have managed to achieve one of the required pricing methods in 'VOFM' and it is really very effective. So if this pricing method needs to be widely used, should I position all the solution groups of suppliers and purchasing organizations as current, or should I define routines to all pricing conditions? What are the drawbacks of both options?