Enterprise Resource Planning Blogs by Members
Gain new perspectives and knowledge about enterprise resource planning in blog posts from community members. Share your own comments and ERP insights today!
Showing results for 
Search instead for 
Did you mean: 
Active Contributor


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




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




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


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


Possible Values













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





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




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

save this new characteristic.

Create  object dependency using transaction CU01  


Give name of dependency,


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


Click on


Write syntax code like below

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


Click on syntax check as highlighted above.  



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


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.





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)


Enter material number

Push configuration button as highlighted above,


You will get pop-up to input characteristic values


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


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



  • 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.




  • Help.sap.com

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

Labels in this area