Hello Guys,

Here I am going to discuss how we can use Multiple value characteristics as a key value in variant table to infer the value of non-key value. It is very simple task to make variant table with the multiple value section as key value. But if we check the consistency of the variant table it shows the ambiguous value maintain message. And as we know we can’t use multiple value selection table in procedure as well as action. The procedure/Action will throw the syntax error. It can’t infer the value too. 

Here with the help of constrain we can achieve it. We will see with the example.

Let me discuss here one case in which we approach this development.

Case: We have characteristics called inspection agency (CT_INS_AGENCY). This is single value Characteristics. Whenever our business produce complex product of steel. Customer request inspection agency for the inspection of the material. Business charge price for the Third party inspection.

In old time customer was asking only one inspection agency for the inspection now product become more complex base on specialty of the inspection agency different agency required to do inspection. Means Business need multiple value selection for the same and price key must be trigger multiple.

The above requirement will not allow you to use  your existing characteristics as a multiple value selection and making single value selection key to multiple value selection is not reasonable too. It can impact to the existing orders configuration.

To resolve the above issue we can user two features of SAP VC and resolve it. One is referencing characteristics value and constrain to infer the value instead of procedure.

Note: It is not reasonable to keep increasing the characteristics in existing design. It can impact to existing product design as well as open order which are already release to production can impact to MRP run. Not required to create one more characteristics.

We have Variant table TABLE_INS_PRICE.

CU61 – Create variant table structure.

CU60 – Maintain variant table data

Note: We are not discussing here on how to create variant table. Assuming everyone know and many document available in this document for the same. (If really needed I will add the steps).

CT_INS_AGENCY (Single Value) CT_VP_PRICE (Multiple Value)
KAR VP_KAR_2016
JDW VP_JDW_2016
IRB VP_IRB_2016
RBI VP_RBI_2016
KUO VP_KUO_2016
NSO VP_NSO_2016
GOV VP_GOV_2016

Above table is inferring value in existing scenario with the help of procedure. Variant table use in procedure.

Tables in Actions and Procedures – Variant Configuration (LO-VC) – SAP Library

Create one more characteristics (CT04) with the multiple value selection

TPI1.PNG

When we make multiple value selection characteristics, it can not be use in procedure and can’t infer the value.Write constrain to infer the vale of inspection agency price.

Run transaction code CU22 open existing net dependency and write new constrain their. (TEST_VP_TPI)

TPI_2.PNG

Here CT_INS_AGENCY_REF is multiple value characteristics. We reference that characteristics to the our single value characteristics (CT_INS_AGENCY).

Now to remove misunderstanding for the users, we will hide this characteristics and make no input general so user will see only one characteristics in sales order product configuration.

TPI_3.PNG

Note: If any Logic is created base on characteristics (CT_INS_AGENCY), take where use list of that object dependency and do relevant changes.

The below link is most helpful to convert any characteristics value of table in to the multiple value features and achieve result.

Multiple-Value Characteristics in Table Calls – Variant Configuration (LO-VC) – SAP Library

This is really small process but it become very helpful to me to achieve complex case result in our business.

Thanks,

To report this post you need to login first.

3 Comments

You must be Logged on to comment or reply to a post.

  1. Ritesh Dube

    Keyur Mistry,

    Thanks for adding a new topic, really appreciate your effort.

    Sorry to say , I am not able to understand it fully , do you mean a single value characteristic can be replaced in table by using a new multi value characteristic along with constraint? 

    By adding a example on what user was selecting earlier and result with how this new logic changed the way can help reader.

    Thanks

    Ritesh

    (0) 
    1. Keyur Mistry Post author

      Ritesh Dube

      Yes You understand correct. We can replace single value characteristics from table, When business required it as multiple value selection.

      In above example CT_INS_Agency was single value. I hide the same for the users to enter and gave one more new characteristics, which have multiple value characteristics features. As you know I can not keep my multiple value characteristics in Variant table as key value.

      So what I did I just gave new cstics as reference to old and allow user to select multiple value. Now from old table I am resulting multiple price base on multiple value selection.

      I have added above post with complete live example with case. It’s really helpful when business change accordingly.

      (0) 

Leave a Reply