Search Results aso_validate_cfg_pvt




Overview
Explore in AI Chat

Overview

The ASO_VALIDATE_CFG_PVT package body is a private PL/SQL API within the Oracle E-Business Suite Order-to-Cash (ASO) module, responsible for validating sales order and quote configurations against the Oracle Configurator engine. In the context of Oracle EBS 12.1.1 and 12.2.2, this package serves as the validation bridge between the Sales Quote/Order application and the Configurator (CZ) schema. It determines whether a given configuration associated with a model line is complete and valid before the quote or order is committed to downstream processing.

The package is classified as a private (PVT) API, meaning it is not intended for direct invocation by external consumers. It is designed to be called by other ASO packages that expose public validation entry points. The ASO_VALIDATE_CFG_PVT package orchestrates a multi-step round trip: it constructs an XML validation request, dispatches that request to the CZ configurator, parses the returning XML response, and persists the validated configuration details back into the ASO tables. The header file reference (asovcfgb.pls, version 120.0.12010000.2, dated 2010) indicates the package has been stable across multiple 12.x releases.

Key Procedures and Functions

The package exposes two documented program units. The metadata lists precisely these two procedures and no additional functions.

  • VALIDATE_CONFIGURATION — The primary procedure of the package. Its documented description states that it "checks if the configuration is complete and valid" and returns success or error as a status indicator. It performs several orchestrated steps internally: it calls Create_header_xml to build the CZ batch validation header XML message; it invokes ASO_CFG_INT.Send_input_xml to transmit that message to the CZ configurator along with a PL/SQL table containing options that have been updated or deleted from the model; it calls ASO_CFG_INT.Parse_output_xml to interpret the CZ response and determine whether the configuration is valid and complete; and finally it calls ASO_CFG_INT.Get_config_details to persist options and model line details. The procedure accepts an API version number, standard initialization and commit flags, a control record, the model line identifier, quote line and detail tables, an update-quote indicator, effective and model lookup dates, and returns the configuration header identifier, configuration revision number, and a validity flag.
  • CREATE_HEADER_XML — A helper procedure responsible for constructing the CZ batch validation header XML message. This XML is the input payload consumed by the configurator's validation batch process. The procedure encapsulates the message-formatting logic so that Validate_Configuration can focus on orchestration and result handling.

Tables Accessed

The package references several tables through APPS synonyms for both reading and writing configuration data:

  • ASO_QUOTE_HEADERS_ALL — The quote header table. It is accessed to associate the configuration validation with the correct quote context and to resolve the model and pricing context required by the CZ validation request.
  • ASO_QUOTE_LINES_ALL — The quote line table. As documented in the procedure comment, validated options are saved along with the model line into ASO_QUOTE_LINES_ALL. This table holds the model line against which the configuration is being validated.
  • PLITBLM — The standard Oracle PL/SQL indexed table of long data used for passing PL/SQL table data between program units. It supports the transfer of the options table to the CZ interface during the send/receive cycle.

The procedure comment additionally references ASO_QUOTE_LINE_DETAILS and ASO_LINE_RELATIONSHIPS as targets for saving configuration details and option relationships.

Usage Notes

Because ASO_VALIDATE_CFG_PVT is classified as a private API, it is not intended for direct invocation from custom code, forms, or concurrent programs. It is invoked indirectly by other ASO packages — the metadata records one referencing package — that provide the public validation entry points exposed through the Oracle Quoting and Order Management user interfaces. Typical invocation scenarios include quote or order save operations, where configuration validity must be confirmed before the transaction proceeds, and any batch validation flow that processes configured model lines.

Developers extending or debugging configuration validation should be aware that the package depends on the ASO_CFG_INT integration package for the actual transmission and parsing of XML against the CZ schema. Any change to the CZ configurator version or XML message contract can affect this package's behavior. The X_valid_configuration_flag output is the definitive indicator of configuration completeness and should be inspected by any wrapper calling the API. Standard FND_API initialization and commit conventions apply, with P_Commit controlling whether the save of configuration details is committed within the caller's transaction. In 12.1.1 and 12.2.2, no functional differences to this package are documented; the implementation remains consistent across both releases.