Search Results contract_renewal

Overview

ASO_CORE_CONTRACTS_INT is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite. It forms part of the Oracle Order Capture / Quoting foundation (the ASO product family) and provides the core integration logic that converts a quote into a contract or order, and that manages contract renewals within the Oracle TCA and Order Management framework. The object is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2 and is classified under the generic API classification "OTHER", indicating that it is an internal, non-public-API utility rather than a published interface intended for direct customer invocation. Its primary business role is to mediate the transition between the quoting process and downstream contract or sales order creation, ensuring that customer account validation, TCA party checks, and change notifications are handled consistently. The package is oriented primarily toward renewal and ordering business flows rather than initial quote capture.

Key Procedures and Functions

The ETRM metadata documents nine procedures and functions exposed by this package. Their documented names and purposes are as follows:

• QUOTE_CONTRACT_RENEWAL — Handles the renewal processing path in which an existing quote or contract is renewed, orchestrating the renewal into the contract structure.
• CONTRACT_RENEWAL — Executes the contract-level renewal operation, applying the renewal business rules to an existing contract record.
• QUOTE_IS_RENEWAL — A validation function that determines whether a given quote qualifies as a renewal, allowing callers to branch logic accordingly.
• QUOTE_CONTRACT_IS_ORDERED — A validation function that determines whether a quote-derived contract has already been ordered, preventing duplicate ordering.
• CREATE_CONTRACT — Creates a new contract record derived from quote data, persisting the contract header and related information.
• UPDATE_CONTRACT — Applies changes to an existing contract record, supporting the maintenance of contract data after creation.
• NOTIFY_CONTRACT_CHANGE — Raises notifications when contract data changes, supporting downstream subscribers and workflow/event consumers.
• CHECK_CUSTOMER_ACCOUNTS — Validates customer account information, typically invoking TCA party validation to confirm that the account data associated with the contract is valid.

Tables Accessed

The supplied documentation excerpts do not enumerate the base tables referenced by ASO_CORE_CONTRACTS_INT through APPS synonyms. However, the dependency list confirms that the package invokes ASO_CHECK_TCA_PVT, ASO_UTILITY_PVT, ASO_DEBUG_PUB, FND_API, FND_GLOBAL, and FND_MSG_PUB. The ASO_CHECK_TCA_PVT dependency shows that customer account validation against TCA is performed through the standard ASO/TCA validation layer rather than direct table access. Because it creates and updates contracts, the package necessarily reads and writes the underlying ASO quoting and contract entities, but the exact table list is not documented in the ETRM metadata and should be confirmed by inspecting the package body or dependency views in the target instance.

Usage Notes

This package is not a public, supported API. It is referenced by only one other package and is not referenced by any database object outside the ASO component. In practice it is invoked indirectly through the standard Oracle Quoting and Order Capture flows — for example, when a user renews a quote or contract from the Quoting user interface, when a concurrent program processes renewals, or when internal package code calls the contract creation routines. Customizations should avoid direct calls to these procedures; integrations should instead use the supported Oracle APIs (such as the quote and order public APIs) that internally rely on this package. The presence of FND_API, FND_MSG_PUB, and FND_GLOBAL indicates standard concurrent-safe error handling and message stack behavior, and ASO_DEBUG_PUB provides diagnostic logging for troubleshooting renewal and contract creation failures. Because the package is documented as VALID, it is safe to assume it is compiled and available, but its internal logic is subject to change across releases and should be treated as Oracle-owned implementation detail.