Results for “as_leads_pkg”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.AS_LEADS_PKG package body is a foundational PL/SQL program unit within the Oracle E-Business Suite Sales Foundation module. It encapsulates the core create, read, update, and delete (CRUD) logic that governs records in the leads data model used by Oracle Sales and related CRM components. Leads represent unqualified prospects that have not yet been converted into opportunities, and the integrity of these records is central to the top of the sales pipeline. By providing a stabilized Application Programming Interface (API) layer, AS_LEADS_PKG isolates calling applications—such as Oracle Forms, concurrent programs, and external integrations—from the underlying table structure and business validation rules. In Oracle EBS 12.1.1 and 12.2.2, this package submits its operations under the APPS schema and is registered as an OTHER-class API in the E-Business Suite Technical Reference (ETRM) repository, where it is documented as VALID and actively maintained. The package body depends on standard EBS infrastructure utilities, including FND_API for API error handling and return status conventions, APP_EXCEPTION for raising and managing exceptions, and FND_MESSAGE for retrieving user-facing message text. This dependency profile confirms that the package adheres to the Oracle Application Object Library standards for API design, enabling consistent error signaling and transactional behavior across the Sales Foundation schema.

Key Procedures and Functions

The package exposes four documented procedures, each corresponding to a discrete data manipulation operation on the leads entity:

• INSERT_ROW — Creates a new lead record. This procedure performs the initial population of lead attributes, generates or validates the surrogate primary key, and applies the defaulting and validation rules required before a prospect can enter the leads pipeline.
• UPDATE_ROW — Modifies the attributes of an existing lead. It is the standard entry point for changes such as reassigning ownership, updating qualification status, or revising demographic and contact details, while preserving referential integrity with related records.
• LOCK_ROW — Acquires a row-level lock on a specified lead so that a calling session maintains exclusive control during a multi-step update transaction, preventing concurrent modification by other users or processes.
• DELETE_ROW — Removes a lead record. This procedure enforces the deletion rules applicable to leads, including any restrictions that prevent removal of records still referenced by downstream sales activities.

Each procedure follows the standard EBS API convention of returning a status indicator and an error message, rather than allowing unhandled exceptions to propagate to the caller. Note that parameter lists are not enumerated in the documented metadata and should be derived from the package specification at deployment time.

Tables Accessed

The package reads from and writes to two documented tables through APPS synonyms:

• AS_LEADS_ALL — The primary transactional table holding lead records across all organizations. It is the target of INSERT_ROW, UPDATE_ROW, and DELETE_ROW, and the source for the row fetched during LOCK_ROW.
• AS_LEADS_S — The sequence (or secondary surrogate table) used to generate unique identifiers for new lead rows during insertion.

Dependency metadata also shows references to the DUAL and STANDARD objects, reflecting routine SQL and PL/SQL operations. No other APPS database objects reference AS_LEADS_PKG according to the ETRM dependency listing, although the documented package metadata indicates it is referenced by one other package in the broader 12.2.2 repository.

Usage Notes

AS_LEADS_PKG is typically invoked from Oracle Forms used in the Sales Foundation and TeleSales modules, from concurrent programs that perform bulk lead maintenance or import, and from custom PL/SQL integrations that must create or update leads programmatically. Because the package is an API layer rather than a form-specific library, custom code should call these procedures instead of issuing direct DML against AS_LEADS_ALL, ensuring that validation, defaulting, and error handling remain consistent. Callers are expected to initialize the FND_API.G_MISS_* constants and inspect the returned status before committing. The presence of LOCK_ROW supports multi-step interactive and batch flows that require pessimistic locking. When migrating or extending functionality between EBS 12.1.1 and 12.2.2, the package body should be treated as the authoritative implementation, with the package specification consulted for exact signature details.