Showing results for 
Search instead for 
Did you mean: 

Variant Configuration, pricing at 'config' level not at 'characteristic'

Former Member
0 Kudos

Hey guys,

I am currently working on Variant Configuration and that works fine, including pricing. Current we have assigned the pricing dependency procedures at characteristic level. So if some chooses characteristic 'x' it has the dependency procedure: $self.YSURCHARGE = 'A4'

('ysurcharge' is the name of my surcharge characteristic)

Like I said, this works fine as long as you use this in ECC but when I create a knowledge base object and a runtime (it needs to be replicated to CRM) I get the following error:

<i>Procedure 0000000114 to Characteristic YCPU - value not supported

Message no. VSCE357


The procedure is assigned to a characteristic or characteristic value.

System response

The procedure is not copied to the knowledge base.


Assign the dependency to the configuration profile, and add a suitable condition such as IF SPECIFIED <characteristic>.</i>

So what I need to do is assign my dependency to the configuration profile instead of the characteristic and I need to change the code for that.

<b>Now my question:</b>

<b>How should my coding have to look when I maintain pricing for Variant Config at configuration profile level instead of characteristic level?</b>

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

And can someone please tell me where I can find an overview of the statements which you can use in the dependency editor?