Variant Issue.

[Former Member]

What is Class & dependencies in variant.

Definition

Use with example.

Points would be rewared accordingly.

David.

[jpfriends079 · Accepted solution]

By taking example from Variant Configuration, let me explain you class and dependencies.

To define the features of a configurable material, you use characteristics. To enable you to use characteristics to configure a material, you assign the material to a class of class type 300. Possible characteristics of a car, for example, are model, country, color, and engine. The customer can choose from among different options for each characteristic (values). So group of characteristics that can be attributed to a product. A CLASS is a grouping of similar objects according to common characteristics.

The only limitations are combinations of features that are not possible for either technical or marketing reasons. You cannot combine all types of car engine with all types of transmission, for example, or certain types of upholstery are only available for more expensive models. So in Variant Configuration, you use dependencies to control this. This prevents combinations of options that are not allowed. Dependencies also select exactly the right BOM components and operations to produce a variant.

Hope it might helped u.

Take care. JP

[Former Member · Accepted solution]

Hello JP,

Thanks for your explaination. Could you please little ilaborate the dependency more.

David

[jpfriends079 · Accepted solution]

These are interdependent data records. The description of relationships between objects and their characteristics. You can use dependencies for example to set characteristic values or to check the consistency of assigned values.

Hope it helped you. Kindly reward points. Take care. JP

[Former Member · Accepted solution]

Hi..

Try the following simple dependencies.

Once you have setup the classification, class type 300 and created a configurable material in MM.

Assign the Material to the Configuration profile in transaction CU41.

Then create a BOM, with 2 variable parts.

So lets say you have two characteristic values possible in class type 300.

Characterisic_1 = 'A' or Part 1 in the BOM or Characteristic 1 = 'B' or Part 2 in the BOM. You must pre-define these before proceeding in transaction CT04 and assign to class type 300 - Class is created in transaction CL02.

To write a 'selection condition' dependency, please create it with the 'selection condition' following syntax using transaction CU01 - you can also create these dependencies locally in the BOM.

Characterisic_1 = 'A'. - Assign this syntax to Part 1

Characterisic_1 = 'B. - Assign this syntax to Part 2.

Try to configure the material using transaction CU50.

Cheerzz..

Subbzz..