Search Results assign_sales_lead

Overview

AS_SALES_LEADS_PUB_W2 is a public PL/SQL package in the Oracle E-Business Suite (EBS) Applications schema (APPS), belonging to the Oracle Sales (AS) foundation module and the Sales Leads / Opportunity Management functional area. It is a generated wrapper-tier package — the "W2" suffix indicates it sits behind a primary public package and exposes overloaded or extended entry points for the Sales Leads API stack. The package is declared with AUTHID CURRENT_USER, so it executes under the privileges of the calling schema and relies on the caller's synonym and grant model rather than definer's rights.

The package enables standard lead lifecycle operations: converting or copying a sales lead into a sales opportunity, linking an existing lead to an opportunity, creating opportunities, assigning leads to salesforce resources, and retrieving sales access profiles and profile option values. It also provides a wrapper to run lead qualification/processing engines. In EBS 12.1.1 and 12.2.2, this package is part of the infrastructure that the Sales Leads form, the Sales application web pages, and the Leads/Opportunities public APIs use to enforce business rules, security, and territory assignment.

Key Procedures and Functions

• COPY_LEAD_TO_OPPORTUNITY — the most heavily parameterized procedure in the package; copies an existing sales lead into a newly created opportunity, transferring lead attributes and optionally the associated lead detail lines.
• LINK_LEAD_TO_OPPORTUNITY — establishes an association between an existing lead and an existing opportunity without creating a new opportunity record.
• CREATE_OPPORTUNITY_FOR_LEAD — creates an opportunity directly from a lead's data as a discrete creation step, separate from the copy operation.
• ASSIGN_SALES_LEAD — assigns a sales lead to a salesforce resource, applying lead assignment and ownership rules.
• GET_ACCESS_PROFILES — returns the access profiles available to the current user for lead/opportunity operations, supporting security and visibility filtering.
• GET_PROFILE — returns the value of a specified profile option, used to drive configurable behavior.
• RUN_LEAD_ENGINES — invokes the lead processing engines (such as qualification or scoring logic) for a lead.

The extensive JTF_VARCHAR2_TABLE_100/200/300, JTF_NUMBER_TABLE, and JTF_DATE_TABLE parameters on COPY_LEAD_TO_OPPORTUNITY are the standard Oracle Applications API convention for passing DFF/flexfield and multi-row attribute arrays, with indexed parameters (p11_a0 through p11_a36) mapping to attribute columns.

Tables Accessed

ETRM documentation for this package does not enumerate the underlying tables directly; access is made through APPS synonyms. Functionally, the package operates against the AS_SALES_LEADS and AS_SALES_LEAD_LINES tables (lead header and detail attributes), the AS_OPPORTUNITIES and associated opportunity line tables, AS_ACCESS_PROFILES and related security tables, and AS_LOOKUPS / profile option tables (FND_PROFILE_OPTION_VALUES) for GET_PROFILE and access control. It writes into the opportunity tables during copy and creation and reads lead and security data for assignment and access checks.

Usage Notes

The package is typically invoked from the Sales Leads and Opportunities forms, from Oracle Sales web UI flows, and from the higher-level public Sales Leads API rather than called directly. Custom extensions and integrations should call the documented public procedures — not the internal _W2 layer — with p_init_msg_list, p_commit, and p_validation_level set according to the standard Oracle API error-handling pattern, and should always inspect x_return_status, x_msg_count, and x_msg_data before committing.

ETRM records no other packages as referencing AS_SALES_LEADS_PUB_W2, indicating it is a leaf wrapper in the dependency graph. As with any generated wrapper, its signature is tied to a specific patch level (the header shows $Header: asxwsl2s.pls 115.18 2003/09/18 $); direct use risks invalidation across upgrades, so it should be reserved for the Sales module's own internal callers.