Results for “bom_config_validation_pub”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.BOM_CONFIG_VALIDATION_PUB is a public PL/SQL API in the Oracle E-Business Suite Bills of Material module responsible for validating configured bills of material before an order line or configuration is accepted. When a user selects options from a model, the resulting configuration must be checked against the rules that govern the model — minimum and maximum option selections, mandatory classes and components, mutually exclusive components, ratio and parent quantity constraints, and the completeness of each option class. This package encapsulates those validation rules so that both the Oracle Configurator/order entry flows and custom extensions can verify a configuration consistently.

The package header declares a series of procedures and functions that perform discrete validation checks and combine them into a single entry point. The body's private functions, such as Mutually_Exclusive_Comps_exist, Mandatory_Comps_Missing, Get_Parent_Quantity, and Check_Option_Exist, support the group-level checks by inspecting the options table passed in by the caller. Return status is communicated through an x_return_status OUT parameter on nearly every procedure, which is why searches for "handle_ret_status" commonly lead to this package: callers must inspect the returned status flag after each validation.

Key Procedures and Functions

The documented public entry point is BOM_BASED_CONFIG_VALIDATION. It orchestrates the configuration validation against the top model bill sequence, model quantity, effective date, and the caller-supplied options table, and reports the outcome via the return-status and valid/complete-configuration output parameters.

• Check_Min_Max — verifies that the number of options selected for each class falls within the minimum and maximum limits defined for that class.
• Check_Ratio_And_Parent — validates ratio quantities and parent component relationships against the top model line.
• Check_Class_Has_Options — confirms that each option class contains at least one selected option, driving the completeness result.
• Check_Mut_Excl_Options — detects selection of mutually exclusive options and marks the configuration invalid when a conflict exists.
• Check_Mandatory_Classes — ensures that all mandatory classes have a qualifying selection before the configuration is considered complete.
• Mutually_Exclusive_Comps_exist and Mandatory_Comps_Missing — private BOOLEAN helpers used by the mutual-exclusion and mandatory checks.
• Get_Parent_Quantity — private function returning the parent quantity for a component code within a model.
• Check_Option_Exist — private function used to test whether a given option is present in the supplied options table.

Tables Accessed

The package reads configuration and order context from the following tables, accessed through APPS synonyms:

• BOM_EXPLOSIONS — supplies the exploded model structure required to resolve classes, components, quantities, and parent-child relationships during validation.
• OE_ORDER_LINES — provides order-line context (model line, ordered quantity, and configuration linkage) against which the selected options are validated.
• PLITBLM — the PL/SQL index-by table type used to pass the caller's option selections into and out of the validation routines.

No direct DML is documented; the package is primarily a read-and-evaluate utility that returns status and correctness flags rather than persisting results.

Usage Notes

BOM_CONFIG_VALIDATION_PUB is invoked during configuration entry, typically from the Oracle Order Management/Configurator flow when a model line's options are submitted for validation, and from any custom code that needs to test a configuration before booking. Callers must declare the options table of type VALIDATE_OPTIONS_TBL_TYPE, pass the top bill sequence id, model quantity, and effective date, and then inspect x_return_status (and where applicable x_valid_config or x_complete_config) before proceeding. Because ETRM lists no inbound references from other PL/SQL packages, the API is generally consumed directly by forms, concurrent programs, or bespoke extensions rather than by peer packages, and its documented owner is APPS with a public API classification in Oracle EBS 12.1.1 and 12.2.2.