Search Results get_model_init_parameters




Overview
Explore in AI Chat

Overview

ASO_QUOTE_HOOK is an Oracle E-Business Suite PL/SQL package that belongs to the Oracle Advanced Supply Chain Planning / Oracle Quoting (ASO) application family and is owned by the APPS schema. As its name implies, it is a hook package: a deliberately thin extension point that Oracle Development seeded into the Quoting and model configuration flow so that customer-specific logic can be introduced without modifying the underlying seeded code. The header comments describe the package as "a new API to return the model configuration effective date and the model configuration lookup date," indicating that its primary business role is to expose date and parameter information that governs how a configured model is resolved when a quote is priced, validated, or transferred to an order.

The package carries the internal revision marker asoczteb.pls 120.1, dated 2011/04/26, which places it in the Oracle EBS 12.1.1 and 12.2.2 code lines. It is classified in the ETRM repository with an API classification of OTHER rather than as a public, formally versioned API, which is consistent with its role as a customization hook rather than an integration interface.

Key Procedures and Functions

The documented package exposes two procedures, both declared as public and generated from a standard template that includes the usual IN/OUT parameter scaffolding and basic operation.

  • GET_MODEL_CONFIGURATION_DATE — Returns the model configuration effective date and the model configuration lookup date associated with a quote header or quote line. In the seeded body both output values are initialized to NULL and no business logic is supplied, confirming that the procedure is intended to be overridden by customer code. The header comments note that the automatic procedure definition includes standard IN/OUT parameters and that the developer must manually add parameters and business logic as necessary.
  • GET_MODEL_INIT_PARAMETERS — Returns the model configuration initialization parameter as a VARCHAR2 output, again initialized to NULL in the seeded body. This is the procedure referenced by the search term "get_model_init_parameters." Its purpose is to supply the initialization string or parameter set that the model configuration engine consumes when a configured item is instantiated for a quote line.

Both procedures accept an optional quote header identifier and an optional quote line identifier, defaulting to the standard FND_API missing-value constant, so that callers can invoke the hook at header level, line level, or both. No parameter lists are reproduced here beyond what the metadata documents.

Tables Accessed

The ETRM metadata for this package lists no tables accessed via APPS synonyms. This is consistent with the seeded implementation, whose only executable statements assign NULL to the OUT parameters. Any table access—such as reading ASO_QUOTE_HEADERS, ASO_QUOTE_LINES, or model configuration tables—would be introduced by the customer implementation of the hook rather than supplied by Oracle. Because Oracle does not document a table contract for the package, implementers are free to reference whatever configuration or quote tables their business rules require.

Usage Notes

ASO_QUOTE_HOOK is not invoked directly by end users. It is called by the Oracle Quoting framework and related model configuration logic at the point where effective dates and initialization parameters are needed. The ETRM metadata records that the package is referenced by two other packages, indicating that the callers are other seeded PL/SQL units rather than forms or concurrent programs. Typical invocation therefore occurs when a user configures a model on a quote in the Oracle Quoting or Oracle Order Management user interface, when a quote is priced, or when a configuration is validated or copied.

Because the seeded bodies return NULL, the practical use of this package in 12.1.1 and 12.2.2 is as a customization vehicle. Customers copy the package body into a custom schema, implement the required lookups, and rely on the hook being called by the standard flow. Any customization must preserve the documented signatures and treat all parameters as optional, since the framework may pass only the header identifier, only the line identifier, or both. Testing should confirm behavior when both identifiers are supplied as FND_API.G_MISS_NUM, as this is the default state and the most likely source of runtime errors in custom implementations.