Configuration Scenario with Order BOM:
For this case, a two-step processing exists:
Single-level and multilevel configuration takes place in Sales and Distribution.
New under AVC: Sales can decide to what extent technical postprocessing is required.
Within technical postprocessing, a multilevel and interactive configuration is also possible. Manual changes can be made to the BOMs in the sales order BOMs.
The following video gives you an overview of these configuration scenarios.
The following figure gives you an impression of the first steps of a configuration scenario with order BOMs.

The following figure gives you an impression of the next steps of a configuration scenario with order BOMs.

Configuration Scenario with Order BOM: Technical Processing
Multilevel interactive configuration:
Characteristic value assignment is stored for each configurable item, but all with reference to the main item in the sales order.
Material requirements:
Material requirements for a sales order item are issued from the sales order.
Order-specific changes of the BOM, manually or via configuration, are taken into account in MRP.
Configuration Scenarios with Order BOM: Summary
- Two-Step Procedure:
- Sales
- Technical Order Processing
- In the sales order, the header material, and possibly also components, are configured interactively.
- In the order BOM, you can create and edit in a separate environment (SAP Fiori app OBOM_WB_MAIN, CU51, CSKB, and so on).
- The header material and the configurable components can be reconfigured here.
- In the order BOM, you can change, delete, copy, or insert any number of components.
- The result is one line in the sales order and one or more newly created BOMs regarding the sales order item.
- Sales order BOMs must be MRP-relevant (set in Customizing under TA OPPQ plant-specific).
Combinations of Configuration Scenarios
The following figure shows you possible configuration scenarios with AVC and LO-VC.

To select the configuration profile of a material, the system first searches for all active profiles. The $parent material is then checked.
If there's no $parent material (that is, you're in the header), all active profiles are considered.
If an AVC configuration profile exists, it has the higher priority and is selected automatically.
If there are several AVC configuration profiles, the highest priority is automatically selected. The priority is as follows:
Planned / Production order without BOM explosion
Planned / Production Order with BOM Explosion
Sales Order (SET)
Order BOM
If only LO-VC configuration profiles exist, a profile selection screen is offered.
If a $parent material exists, all profiles that aren't allowed in combination with the $parent profile are considered inactive and are therefore not offered.
Below the Order BOM scenario, only the order BOM scenario is accepted.
Order BOM

Case 1: The model only has an active profile at header material level. All configurable components (if available) don't have a suitable configuration profile, or the configuration profile hasn't been released. For the model, each configuration has only one instance. This instance can be queried from all items of the multilevel BOM structure with $parent or $root.
Case 2: The model has an active profile at header material level. Configurable components with a suitable, released configuration profile still exist. For such a model, the configuration of two instances with $parent and $root can be queried from the second level.

If the class node isn't purpose, the object search function from the classification system is available under LO-VC (= function of transaction CL30N).
For automatic specialization, the value assignment for the class node is evaluated first. This can be done by a procedure or, under LO-VC, by a constraint.
If this is not successful, the system searches for the characteristics of the class node at the level above it.
If this is still unsuccessful, the system continues to analyze in the direction of the $root material.
Pricing and Scenario Order BOM
The following list answers the following question: What needs to be considered? What is possible? What is recommended?
- Only valuations of the header material from the sales order are relevant for pricing.
- Characteristics of subordinate components and assemblies are not relevant for pricing.
- All valuations and manual changes in technical postprocessing (SAP Fiori app, OBOM_WB_MAIN, CU51, CSKB, and so on) are not relevant for pricing if they are valuation-dependent on the basis of variant conditions (VA00 and VA01).
- Better solution:
Work with price determination based on product costing.
Work with manual Pricing.