Quantcast
Channel: SCN : Document List - SAP ERP PLM - Classification and Variant Configuration
Viewing all articles
Browse latest Browse all 27

Variant Configuration : Another way to hide characterstic

$
0
0

Purpose:

 

In this write up I am trying to define how to use structure SCREEN_DEP  in reference characteristic to influence display options for other
characteristics.

1.gif

 

Scenario:

 

While settings up your VC model you may come across one of below scenarios

 

  • Hide few characteristic based upon value selected for another characteristic
  • Make a characteristic not ready for input (just  display)
  • Make characteristic “Ready for input”  which is originally created as not ready for input
  • Reset previously setup value using an dependency

 

Solutions:

 

There are  different  approaches possible to work around this scenarios and one of the possibleoption is we can use structure  SCREEN_DEP
to achieve same.
This structure basically controlled 4 display option for characteristic INVISIBLE, INPUT, NO_INPUT, RESET

 

 

 

Scenario
1 :
Hide few characteristic based upon value selected for another characteristic

It’s a common scenario and use reference characteristic  along with object dependency (procedure ) to controlled it.

Example :

 

There are 2 characteristic in VC Model  which are interdependent , characteristic & there possible values are like below


Characteristic


Possible Values


CHAR_A


1


CHAR_A


2


CHAR_A


3


CHAR_A


4


CHAR_B


XL


CHAR_B


XXL


Condition :

CHAR_B should be only available only if  characteristic CHAR_A have value 2 or 3

 

Building Masterdata :

 

Create your VC model

Create a characteristic
CHAR_A , CHAR_B  using transaction CT04  along with possible values as shown in above table.

Create characteristic
HIDE_CHAR  using transaction CT04,
 
Go to additional data tab and input the structure  SCREEN_DEP & field INVISIBLE, press
enter

 


2.gif1.gif

 

 

You will get pop up confirming data type and other details will be copied to characteristic ,

 

3.gif

 

 

Go back to basic data screen and change the description as per your need 

4.gif

save this new characteristic.

Create  object dependency using transaction CU01  

       5.gif

Give name of dependency,

7.gif

 

Give description and select dependency type Procedure using  radio button as shown above

 

Click on  

6.gif

 

Write syntax code like below

$self.HIDE_CHAR = 'CHAR_B' if $self.CHAR_A = '1' or
$self.CHAR_A = '4'

 

10.gif

Click on syntax check as highlighted above.   8.1.gif

 

 

Click on save  icon it will take you back to first screen.

 

9.gif


Make sure you change dependency status to 1 (Release) or  your dependency will not work.


Save the dependency.


You can assign this dependency in configuration profile of the model or you can assign it to characteristic CHAR_B.

 

 

Result:

 

Now all the settings are done and our model is ready to be test.We can either create a sales order (VA01) to test or we can use configuration simulation  (CU50)

 

11.gif

Enter material number

12.gif

Push configuration button as highlighted above,

 

You will get pop-up to input characteristic values

 

13.gif

If you assign value 2 or 3 to characteristic A , system will allow you to assign values to characteristic B too.

 

14.gif

If you assign value 1 or 4 to characteristic A, Characteristic B will become invisible.

 

15.gif


Note:

  • You can add reference characteristic in same  class if you want it to appear in classification screen, in one way it showscharacteristic B got invisible as picked by HIDEN reference characteristic.
  • You can assign dependency to either characteristic   you want to hide or to configurationprofile of the material
  • Changes  made with structure SCREEN_DEP only apply to variant configuration, not to  classification

 

.

Thanks for reading it till end  ,  I will cover related topics of how to reset, make no-input  or allowed input in next document. I will try to post it soon. if you like the document please post your comments and ratings, please also suggest if you find any thing missing in flow, I try to cover all possible details.

 

If you have any question or facing any issue , please create a separate thread and use a link to this document if you want to give reference of any steps. It will help forum members to reply and can be useful for other members facing same issue in future.

 

 

References:

  • Help.sap.com
  • Screen shots are from SAP IDES system, data created by me.

Viewing all articles
Browse latest Browse all 27

Trending Articles