Former Member

### Pricing - Condition Base Calculation

Hi,

I have a material with price on two unit of measures.

One price at 80MK level and another price at 25Kg Level.

The material can be sold in multiple UOM like 60MK,50MK, 20KG, 10KG etc.

The base price for 60MK or 50MK is 80MK and Base price for 20Kg and 10KG is 25KG price.

How can i achieve this by using one condition type?

On the current condition record, i am able to maintain price either by 80MK or 25Kg not for both.

Thanks

10|10000 characters needed characters exceeded

• Jun 16, 2017 at 03:42 PM

Not sure whether you are aware of alternate UoM in material master

10|10000 characters needed characters exceeded
• Veselina Peykova Former Member

Is my understanding correct: you have at least two ways to sell a certain product - bulk (by KG) and packaged (in MK)?

I am asking, because, apart from different packaging, I cannot think of another reason at the moment why the same quantity of the same product will have different prices.

If you perform subsequent packaging, is it not more appropriate to show the packaging as a separate item or at least a separate condition?

If you produce both in MK and in KG, this could even be treated as separate products - e.g. I buy a sack of coffee beans of 20kg vs I buy 20 cans of 1 kg of the same coffee. What does the controlling expert in your company say about the case, which you mentioned:

80MK = 21.22 KG in UOM but the price for 80MK and 25KG are same

How did he explain this?

To be fair, I have seen a case, where a company decided to treat products in various sales UoM, different packaging, different sales prices and different cost to produce, as the same material. The end-to-end solution was rather complicated and expensive.

Have you discussed the business case with your colleagues and the solution architect?

• Jun 22, 2017 at 11:33 AM

Technically speaking you can create a new condition table which includes sales unit of measure as a key field (for ex: Sales org / Dist. Chn. / Material / UoM). From there on, user can create two separate condition records, differentiating by UoM. User should be alert enough to enter the same UoM both at condition table header level, and condition table item level.