Search Results as_sales_lead_lines_pkg




Overview
Explore in AI Chat

Overview

AS_SALES_LEAD_LINES_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that provides the core data manipulation layer for managing individual sales lead line records within Oracle Sales (AS) and related CRM modules. Sales leads in EBS represent unqualified prospects or opportunities that have not yet progressed to a formal opportunity; each lead is composed of a header record (AS_SALES_LEADS) and one or more line records (AS_SALES_LEAD_LINES) that capture individual products, quantities, or interest items associated with the lead. This package encapsulates the insert, update, delete, and locking logic required to maintain the integrity of those lead line records, shielding callers from the physical column layout and business validation rules embedded in the underlying table structures.

The package is classified as an OTHER API in ETRM for both 12.1.1 and 12.2.2, meaning it is not a formally published open interface but a commonly referenced internal API. Its declared status is VALID in the ETRM metadata, indicating that it is compiled and available in the database dictionary. It participates in the standard Oracle dependency graph, referencing only SYS and STANDARD objects at the base level and being referenced by APPS.AS_SALES_LEAD_LINES_PVT, APPS.AML_INTERACTION_ENGINE, and its own body.

Key Procedures and Functions

The ETRM metadata documents four public procedures within this package, each performing a discrete DML operation against the lead lines table:

  • SALES_LEAD_LINE_INSERT_ROW — Inserts a new sales lead line row, populating the line with the caller-supplied attribute values and performing any default or validation logic required before the record is committed.
  • SALES_LEAD_LINE_UPDATE_ROW — Modifies an existing sales lead line row, updating the column values supplied by the caller while preserving the line's identity.
  • SALES_LEAD_LINE_DELETE_ROW — Removes a sales lead line row from the lead lines table, typically invoked when a user removes a product or interest item from a lead.
  • SALES_LEAD_LINE_LOCK_ROW — Acquires a lock on a lead line row, used to serialize concurrent modifications and prevent lost updates when multiple sessions attempt to change the same line.

No parameter signatures are published in the ETRM excerpt, and the procedures listed should be treated as name-level documentation only.

Tables Accessed

Two base tables are documented as referenced through APPS synonyms:

  • AS_SALES_LEAD_LINES — The primary transaction table storing lead line records: the product or item interest, quantity, and related attribution for each line on a sales lead. All four procedures operate against this table.
  • AS_SALES_LEAD_LINES_S — The MLS (multi-lingual support) shadow table holding translatable descriptive columns for the lead lines, such as line-level text attributes. The package reads and writes this table alongside the base table so that language-dependent content remains consistent.

Usage Notes

AS_SALES_LEAD_LINES_PKG is normally invoked indirectly rather than from custom code. In the standard Oracle Sales forms flow, the Sales Leads or Opportunities form blocks call the private-layer package AS_SALES_LEAD_LINES_PVT, which in turn delegates row-level DML to this package, as evidenced by the dependency listing showing AS_SALES_LEAD_LINES_PVT references AS_SALES_LEAD_LINES_PKG. AML_INTERACTION_ENGINE also references the package, indicating that lead line creation can be triggered by interaction and activity engine processing.

Because this is an OTHER-classified API, Oracle does not guarantee the parameter signatures across releases; customizations should prefer the published AS_SALES_LEAD_LINES_PVT entry points where available. If the package is called directly from custom concurrent programs or PL/SQL, the caller must implement its own COMMIT or ROLLBACK strategy, since row-level APIs of this type generally do not commit. All calls execute under the APPS schema and are subject to the standard EBS security and MOAC (multi-org access control) context established by the calling session.