Configuration Overview
Overview
Configuration is defined on the catalog hierarchy in CPQ. For more information on the catalog hierarchy, see the topic Product Family Hierarchy.
Catalog items contain the following attributes:
- Regular attributes that cannot be modified at run time.
- Configuration attributes that can be modified at run time.
- Signed Punch-in attributes, introduced in 19D, function identically to configuration attributes except they require verification of digital signature data before pricing data is provided to the end customer.
Configuration and Signed Punched-in attributes can be created at all levels of the catalog hierarchy.
Using Configuration, the buyer can customize the items they are buying by specifying the values of configuration and signed punch-in attributes.
Administration
Situations Appropriate for Rules
- Guided Selection: This is the process of guiding a user through a series of questions to help them search for one or more product line(s) within a product family or search for one or more model(s) within product line(s). This is similar to selecting a notebook model from a list of available brands.
- Configuration: This is the process of allowing users to customize a model to suit their needs. This is much like configuring a basic notebook computer by adding extra RAM, more hard disk space, warranty services, and so on. Some options may increase cost (pricing rules) and others options may not be possible (constraints) like getting a 3 month warranty with your model.
Types of Rules
The user experience in configuration is controlled by the ability to fire the appropriate rules based on user input. Different types of rules enhance the selection and configuration experience:
| Bill of Materials
|
Builds a BOM string based on Configuration. |
When a user selects crust type = deep dish, a BOM string with sauce, cheese, butter and type of dough is generated and returned to an ERP system. |
| BOM Mapping Rules
|
Associate BOM items and attributes to Oracle CPQ Configuration attributes and Commerce line items. |
- During Configuration, whenever the configuration state is changed, the BOM Mapping Configuration rules are invoked to map Configuration attributes to BOM items.
- During reconfiguration, the Launch Configuration attributes are mapped from the BOM item instance.
|
| Configuration Pricing Rules
|
Calculates a price based on how a product is configured.
For more information about pricing refer to CPQ Pricing.
|
When a user configures a Model, the price is displayed based on the crust type, pizza size and topping selected. |
| Configuration Hiding Rules
|
Hides attributes when a pre-defined condition is met. |
When a user selects pizza type = specialty, the toppings attribute is hidden. |
| Configuration Recommendation Rules
|
Sets items you would like the users to select or items the users must select. |
When a user selects specialty pizza = Meat Lovers, the application recommends only pepperoni and sausage as toppings. |
| Configuration Constraint Rules
|
Determines attributes values users cannot select within a Configuration. |
When a user selects pizza size = small, they cannot select Deep Dish as the crust type. |
| Configuration Recommended Item Rules
|
Assigns parts and pricing to the Configuration, based on certain selections. |
When a user selects sandwich type = Hot, the application will return 4 recommended sandwich options. |
Best Practices
- Avoid using case sensitive text for displayed information or rule conditions (for example, part numbers).
- Use Auto Updates sparingly.
- Avoid the use of JavaScript.
- Combine Configuration Rules when possible; separate Rules are more difficult to maintain and debug.
- Keep Rules on the same level, so they are easier to maintain and debug. Avoid overriding menu attributes at lower levels in the product hierarchy.
- Add relevant comments to explain specific design decisions.
- Avoid using custom templates.
- Create folders to organize your Data Tables.
Notes
A user cannot create or add Quotes from Configuration to Commerce if mandatory items are missing.
- NULL and blank Integer values are treated as separate values:
- Using NULL as an attribute value is strongly discouraged.
- If you use logic that tests for NULL values in rule conditions or BML, confirm that the logic takes this difference into account.
Related Topics
See Also
