cancel
Showing results for 
Search instead for 
Did you mean: 

variant determination

Former Member
0 Kudos

Hi

I am trying to configure a product using variant configuration. The configuration includes both priced and non-priced options. The priced options which have the variants maintained in VK30 and conditions mapped in PMEVC (Variant pricing tab) are automatically determined but not the non-priced ones.

Is it always mandatory to have the prices maintained for the variants to be determined? If yes, is there a solution or workaround to get the non-priced variants automatically determined?

Thanks

Satish

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member183879
Active Contributor
0 Kudos

Hi Sathish,

What do you mean by priced and non-priced variants.

I hope priced variants are the values of characteristic for which you have a price. Conversely for non priced variants.

If you want the values of a characteristic to come automatically (irrespective of whether they are priced variants or not), this is possible. You have to enable these rules by means of object dependencies.

If I have not got your question correctly, please rephrase your question so that I can try to help