cancel
Showing results for 
Search instead for 
Did you mean: 

How to select BOM components in sales order based on characteristics using AVC

snigdhodeep
Explorer
0 Kudos
230

Hello experts!

I am trying to model a scenario where one can select the right BOM component based on characteristic values entered in quotation/sales order.

Here is what what I have done so far:

- Created Finished product with class assigned whose type is 300

- In PMEVC I have created an object dependency as 'procedure AVC' and entered a simple condition like: If characteristic value is = 100.

Now when I try to assign this object dependency to the BOM component, I get the error: 

Dependency type Procedure AVC not allowed for this object

Am I missing something in the setting up the scenario? Does AVC support such scenarios of BOM component selection in sales orders based on the values entered against FG material characteristics?

Any help would be highly appreciated.

Thank you

Snigdhodeep

View Entire Topic
Michael_W
Product and Topic Expert
Product and Topic Expert

Hi @snigdhodeep.

AVC engine is only used for high-level configuration. BOM explosion and dependencies in the BOM are sill executed by classical VC.

Therefore, you must ensure that you choose classical VC instead of AVC when you create selection conditions and procedures that shall be assigned to BOM items.

Should be a VC selection condition in your case.

Br,

Michael

snigdhodeep
Explorer
0 Kudos

Thank you so much for your response.

snigdhodeep
Explorer
0 Kudos
One quick follow up question (sorry) - is Classical VC (LO-VC) available in S/4HANA Cloud Public? I have not seen any option equivalent to CU01.
Michael_W
Product and Topic Expert
Product and Topic Expert
In S/4HANA Public Cloud, LO-VC as a configurator (e.g. in sales documents) is not available. AVC must be used. Single transactions like CU01 that are covered by the modeling environment are not available. See also https://blog.sap-press.com/what-is-sap-avc-and-how-does-it-compare-to-lo-vc and https://me.sap.com/notes/3366124/E