Search Results construct_appl_param_rec




Overview
Explore in AI Chat

Overview

The ASO_CONFIG_OPERATIONS_INT_W package body is a Rosetta wrapper for the ASO (Oracle Advanced Supply Chain Planning / Configure-to-Order) Configuration Operations public API. Its stated purpose in the package header comments is to provide "Rosetta wrappers for ASO Config Operations Public API," dating from a creation date of 09/12/02. The package serves as an integration layer that translates the standard FND_API (Application Programming Interface) messaging conventions into the calling conventions required by the underlying ASO configuration operations logic, and vice versa.

The package is owned by the APPS schema and is classified under ETRM as API classification OTHER. It is notable within the ETRM 12.2.2 metadata that this package is referenced by zero other packages, indicating it is an entry-point wrapper intended for external invocation rather than an internal building block. A distinctive implementation detail is the use of the ROSETTA_G_MISS_NUM mapping constant, used to translate the FND_API.G_MISS_NUM sentinel into a Rosetta-specific missing-number sentinel (0-1962.0724) and back again, ensuring compatibility between the two API conventions.

Key Procedures and Functions

The ETRM metadata documents four procedures/functions within this package body:

  • IS_CONTAINER — Determines whether a given item/organization context qualified as a "container" within the ASO configuration operations model. This is the procedure most directly implicated by the user's search term "is_container." It takes API-standard parameters covering inventory item, organization, configuration creation/effective/model lookup dates, calling application, usage name, publication mode, and language, and returns a return value along with standard return status, message count, and message data outputs.
  • GET_CONTAINED_MODELS — Retrieves the contained model(s) associated with a parent container configuration, supporting the hierarchical containment relationships used in Configure-to-Order structures.
  • CONFIG_OPERATIONS — The primary operations entry point that dispatches or performs configuration-related operations against the ASO public API.
  • CONSTRUCT_APPL_PARAM_REC — An internal helper that assembles the application parameter record (of type CZ_API_PUB.appl_param_rec_type) required by the downstream Rosetta/ASO calls. The IS_CONTAINER body explicitly logs "Construct appl param record" before invoking this logic.

Tables Accessed

The single table referenced via APPS synonyms is PLITBLM. This is a PL/SQL internal/logging table used by the debug and instrumentation framework (via Aso_Quote_Util_Pvt.Enable_Debug_Pvt and Aso_Quote_Util_Pvt.debug) to store debug and diagnostic output. It is not a business data table in the configuration model sense; rather, it supports the package's embedded debugging instrumentation, which writes trace messages such as "Aso_Config_Operations_Int_W.Is_Container BEGIN."

Usage Notes

Because this package is not referenced by any other package in the ETRM inventory, it is designed as a standalone integration wrapper. It is typically invoked by external systems or custom integration code that needs to query ASO configuration containment facts or invoke configuration operations from outside the ASO module — for example, from order management, planning, or partner integrations that communicate through the public API surface.

The package follows the standard Oracle EBS API invocation contract: callers supply p_api_version (defaulted to 1), pass input parameters defaulted to FND_API.G_MISS_NUM, FND_API.G_MISS_DATE, or FND_API.G_MISS_CHAR, and must inspect x_return_status and the message stack (x_msg_count / x_msg_data) to determine success or failure. Debugging can be enabled through the Aso_Quote_Util_Pvt debug facility. When the "is_container" determination is required, this wrapper is the documented integration path to the underlying ASO configuration operations logic.