Overview
Beginning in Oracle CPQ 24C, an asynchronous task to validate all BOM hierarchies is triggered when any CPQ BOM data table is deployed. The BOM Root Items list now has a new Valid column to display validity of the listed root BOM items.
When the validation task is in progress, a "Pending" state flag is displayed. BOM hierarchies that do not pass the validation checks are flagged as invalid and immediately throw errors if configured on buyside.
The following icons indicate the status of on the BOM Root Items Administration List page.
|
Icon |
Status |
Description |
|---|---|---|
|
|
Valid |
The BOM has no errors. Runtime validations not executed on buyside. Configuration is immediately verified as having no errors. |
|
|
Pending |
BOM has not been validated yet. BOM is in a not yet validated state. Runtime validations run on any BOM in this state configured on buyside. |
|
|
Error |
BOM has at least one error. Runtime validations not executed on buyside. Configuration immediately throws an error if the BOM Mapping rule is triggered. |
After the validation task completes, BOM runtime validations will not execute on BOMs marked as passing validation. If a BOM hierarchy is configured before the validation task is completed, runtime validations are still executed to prevent the user from configuring a BOM with errors.
Administration
Check for Validation Errors
. A BOM item definition is marked as incorrect, if errors exist in the item definitions, attribute definitions, or attribute translations.
Notes
- Errors must be resolved before setting up Configuration BOM Mapping Rules.
-
If the BOM Item Administration page shows that parts or models do not exist when an administrator has created them, deploy the BOM Item Definition table.
-
If the "Buy Direct" field of a part number referenced by a BOM item definition is modified, redeploy the BOM Item Definition data table.
