Search Results notify_contract_change

Overview

ASO_CORE_CONTRACTS_PUB is a public Oracle E-Business Suite PL/SQL API package owned by the APPS schema and classified as a PUB (public) interface. In Oracle EBS 12.1.1 and 12.2.2, it belongs to the Oracle Sales (ASO) module and provides the contracts integration layer for Oracle Quoting. Its documented purpose is to support the integration of sales contracts originating from quoting activity, allowing a quote to be converted, updated, or linked to a contract record maintained in the contracts schema. The package header carries a revision identifier of 120.1 dated 29 June 2005, indicating that this is an older integration artifact retained for backward compatibility in the EBS code line. Consistent with the Oracle Application Object Library API standards, each procedure accepts the API version, initialization-message-list, and commit parameters (p_api_version, p_init_msg_list, p_commit) and returns the standard x_return_status, x_msg_count, and x_msg_data out parameters, together with business-specific outputs such as the contract identifier and contract number.

Key Procedures and Functions

• CREATE_CONTRACT — Creates a contract from a quote, accepting quote, party, resource, template, and interaction information and returning the newly created contract identifier and contract number. In the documented source, the body of this procedure is effectively an obsolete stub: it logs a debug message noting that create_contract is obsolete and then executes NULL. Earlier integration behavior has therefore been superseded by other contract-creation paths.
• UPDATE_CONTRACT — The procedure returned by the user's search for "update_contract". It provides the public entry point for updating an existing contract associated with a quote, accepting the quote identifier and a contract identifier along with interaction subject/body and party context. Its parameter profile mirrors CREATE_CONTRACT, following the standard EBS API signature conventions.
• NOTIFY_CONTRACT_CHANGE — Documents the notification hook used to signal downstream subscribers that a contract has changed, supporting event or workflow-driven propagation of contract modifications to related quoting records.
• CHECK_CUSTOMER_ACCOUNTS — A validation routine that verifies customer account information, typically used to confirm that the party or customer referenced by a quote carries the account attributes required before contract creation or update proceeds.

Tables Accessed

The documented ETRM metadata does not enumerate the base tables referenced by this package; access occurs indirectly through APPS synonyms. Functionally, the package operates against the contract and quote data structures of the ASO and contracts schemas, reading and writing contract header information and linking records between the quoting and contracts repositories. Because the package is a public API, its DML is generally performed through the underlying private or core contracts packages rather than directly against base tables. Any table-level analysis should be performed against a current system rather than assumed from this metadata.

Usage Notes

ASO_CORE_CONTRACTS_PUB is invoked as a public API from Oracle Quoting and from external integration points, including forms, concurrent programs, and custom code that need to create, update, or notify changes against a quote-linked contract. The package is referenced by one other package in the documented dependency set, indicating it sits within a small integration chain rather than serving as a broadly reused utility. Given that the CREATE_CONTRACT body is explicitly obsolete and simply returns NULL, new development in 12.1.1 or 12.2.2 should not rely on it; callers should instead use the current supported contract integration APIs. Standard API calling conventions apply: initialize the message list, check x_return_status after every call, and pass p_commit only at the outermost call in a transaction. Because the package is a stub in part, developers should confirm runtime behavior in their specific environment before treating any procedure as fully functional.