Search Results handle_ret_status

Overview

APPS.OE_CONFIG_VALIDATION_PVT is a private PL/SQL package in Oracle Order Management that performs configuration validation for model and option items during the order entry cycle. It belongs to the ETRM (E-Business Suite Table Reference Manual) classification "PVT," indicating it is an internal, private implementation package rather than a public API intended for direct customer invocation. The package validates whether a configured item (a "kit" or model with options) is complete, valid, and consistent with the rules defined in the underlying bill of material structure.

The package body is identified in the source header as OEXVBOMB.pls, with the internal name OE_CONFIG_VALIDATION_PVT. It carries forward declarations for several private validation procedures and functions that check minimum and maximum quantities, ratio and parent relationships, class-option assignments, mutually exclusive options, and mandatory classes. The single documented public entry point is BOM_BASED_CONFIG_VALIDATION, which serves as the orchestrating routine that drives the internal validation logic against a configuration passed in from the order entry flow.

Key Procedures and Functions

• BOM_BASED_CONFIG_VALIDATION — The documented procedure that validates a configuration using bill-of-material-based rules. It is the package's primary callable routine and coordinates the checks that determine whether the set of selected options for a model item forms a valid and complete configuration.
• Check_Min_Max — Internal forward-declared procedure that validates minimum and maximum quantity constraints for options in the configuration.
• Check_Ratio_And_Parent — Internal procedure that verifies ratio and parent-child relationships among components.
• Check_Class_Has_Options — Internal procedure that confirms whether a class has associated options selected.
• Check_Mut_Excl_Options — Internal procedure that detects mutually exclusive options selected together.
• Check_Mandatory_Classes — Internal procedure that ensures mandatory classes have been populated.
• Mutually_Exclusive_Comps_exist — Internal boolean function supporting mutual exclusivity checks.
• Mandatory_Comps_Missing — Internal boolean function supporting mandatory component checks.

Tables Accessed

• BOM_EXPLOSIONS — Read to resolve the exploded bill of material structure for the model, providing the component hierarchy used during validation.
• OE_ORDER_LINES and OE_ORDER_LINES_ALL — Read to obtain order line details, including the top model line and selected configuration options being validated.
• PLITBLM — Used as a PL/SQL index-by table (PLITBLM) type, typically for passing collections of configuration options into and out of validation logic.

Usage Notes

OE_CONFIG_VALIDATION_PVT is typically invoked from the Order Management configuration validation flow. Because the package is classified as PVT, it is not exposed for direct customer or third-party calls; instead it is called internally by Order Management forms, order entry APIs, and related concurrent processes whenever a model/option configuration is created, modified, or booked. The package is referenced by one other package, consistent with its role as a supporting routine within the configuration validation subsystem. The handle_ret_status search term relates to the standard EBS return-status handling pattern used across these procedures, where x_return_status conveys success or error outcomes back to the calling layer. Custom code should invoke the documented public entry point (BOM_BASED_CONFIG_VALIDATION) through Oracle's supported APIs rather than calling the private procedures directly, since private procedures are subject to change without notice between releases such as 12.1.1 and 12.2.2.