Variant Configuration

[Former Member]

Hi Frnds

I am facing a unique issue at my clients location and have not been able to find a solution to the problem. I would appreciate if someone can guide me or suggest a possible solution.

There are two configurable materials say A and B. Now the pricing for this material is derived from one of the characteristic(say J). But then characteristic looks up MARA table to validate the entries while creating an order. The MARA table has n number of entries.

My problem is that there are specific(particular) entries wrt A and B for characteristic J but the end user is able to enter any valid material available in MARA table. I want to be able to restrict particular entries in characteristic J for material A(say entrie 1,2,3,4) and Material B(say 6,7,8,9). Currently they are able to assign 6,7,8,9 to material A and like wise for materail B.

I am just not able to logically think of an object dependency to support this.!!!!

Will appreciate your responses....

[Former Member]

I'd go for Variant Tables. or an Variant function (ABAP). most realistically, it will probably end up being a little of both.

Good luck and let me know how it goes. !

[Former Member]

I would definitely look at the variant table functionality in that case.

The inherent problem with this solution is that as you get new cfg materials and cstics/values, which limit the cstic-J selections, you have to go off to the table to maintain the entries. It's like a separation thing, because you have to remember to do this, it is not integrated in the VC model, per-se. That said the variant tables work well, and are quite useful, especially in this situation.

One more thought could be restrictable characteristics (look up the documentation on these) but I tend to stay away from using these at all costs (to many issues and not enough flexibility with those things)

Out of curiosity, what kind of stuff are you folks configuring?

Bill

[Former Member]

putting that detail wont be appropriate but i will explain with an example.:

its similar to say Norton. a user comes and purchases norton but then he may purchase diff versions and diff licenses expiring on specific dates. therefore that something similar to my client only problem is that we have say Norton-A and Norton-B and have to restict the entry of licenses for specific ones.

last resort i think will be using a developer to use a program to restrict it.

[Former Member]

My thought would be to have a Characteristic (cstic) value to dilineate Material A and B. Have this at the top level cfg of A and B and set it accordingly with a precondition for J.

OR

If there are a lot of cfg material scenarios (A.....Z or more) you could look into maintaining this relationship in a variant table and precondition off of that.

let me know if I understand this correctly and if that can work for you

Bill

[Former Member]

HI Bill

Thanks for replying. Yes there are lots of A.....Z materials used as coonfigurable and tons of values to be picked in characteristic(say J) too. I have to limit the values used in characteristic(say J) so that the entries for material A are only picked and all other entries would error out.

I hope i am clear