pricing

[Former Member]

Hello

We do the pricing for BOM’s at component level by marking the parent material as not relevant for pricing…we have a requirement where in we have to apply a particular condition type only if the item is sold by itself & not when it is a part of the BOM . so let s assume the condition type is ZA00 then it should be applied only if component A is sold by itself. It should not be applied when say A is sold inside a BOM.

As of now since we do pricing at component level for BOM’s it picks up. My initial thought was to create a requirement which basically checks for the Higher level item fiels”UEPOS” & if it is blank( Product by itself) the only pass/trigger this condition type

Is there any other way not to apply this condition when it is a part of BOM..Suggestions would be appreciated

[Former Member]

Hello Friend.

There are many ways, and if your company or client is amenable you can differentiate price by using different document types.

One document type can be assigned pricing procedure ZVAA01 with condition type ZA00, and can be used to price the material as a component of a BOM.

Another type can be assigned ZVAA02 with condition type ZB00 to be used for the material as stand alone.

The disadvantage of this is that there is nothing to stop someone from entering the BOM with component in the document type with procedure ZVAA02