Search Results lead_process_after_update

Overview

APPS.ASN_SALES_PVT is a private PL/SQL API package belonging to the Oracle E-Business Suite Sales foundation and lead-to-opportunity integration layer. The package encapsulates server-side processing logic executed against sales lead and opportunity records that originate from an external CRM integration source, in this case identified through a Salesforce identity reference. As a private (PVT) API, it is not intended as a public, customer-facing entry point; it supports internal orchestration and post-write business logic. The package header carries a revision string indicating last modification in 2005, meaning the package is stable and has persisted across the 12.1.1 and 12.2.2 releases without structural change. Its documented procedures cover the lifecycle events of lead creation and update, plus territory assignment for opportunities.

Key Procedures and Functions

The package exposes three documented procedures:

• LEAD_PROCESS_AFTER_CREATE — Invoked after a sales lead record has been created, this procedure performs post-creation processing. Its parameters include the standard Oracle API version number, a message-list initialization flag, a commit flag, and a validation level, followed by the identity Salesforce identifier, sales group identifier, and sales lead identifier. It returns a standard return status, message count, and message data output set consistent with the Oracle Application Object Library error-handling convention.
• LEAD_PROCESS_AFTER_UPDATE — The update counterpart to the create procedure. It carries an identical parameter signature, taking the Salesforce identity, sales group, and sales lead identifiers with the same messaging outputs, and executes the post-update lead logic required to keep the lead synchronized with its originating integration record.
• OPP_TERR_ASSIGNMENT — Performs opportunity territory assignment. Its parameters accept an API version, message-list flag, commit flag, and the lead identifier, returning the standard status, message count, and message data. Despite its name referencing opportunities, the procedure accepts a lead identifier, reflecting the packaging of lead and opportunity processing into a single private unit.

Tables Accessed

The ETRM metadata does not enumerate specific base tables referenced by this package through APPS synonyms. The parameters and procedure names indicate that the package operates against the sales lead and opportunity entity tables within the Oracle Sales application schema, along with supporting sales group, territory, and territory-assignment structures. Because no explicit table list is documented, specific object names should be confirmed by inspecting the package body in a target environment. For 12.1.1 and 12.2.2, these objects reside under the APPS synonym namespace as declared in the package header.

Usage Notes

ASN_SALES_PVT is a private API and is referenced by no other documented packages, indicating it is invoked directly from integration logic, forms-based processing, or custom concurrent programs rather than called through the public API layer. Callers must supply the standard Oracle API preamble parameters, including the API version number, the message-list initialization flag, and the commit flag, and must inspect the returned status, message count, and message data to detect failures. The validation level parameter permits callers to control the depth of validation applied during execution. Given its private classification, direct invocation should be treated as unsupported, and the API version number should be passed consistently to preserve forward compatibility. The identity Salesforce identifier parameter confirms its role in external CRM synchronization flows, where post-create and post-update hooks maintain data consistency between the external system of record and Oracle EBS.