Results for “as_lead_lines”

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

Overview

AS_LEAD_LINES is a Sales Foundation (AS) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the sales opportunity line records maintained by the Oracle Sales and TeleSales applications and is documented in ETRM as "Sales opportunity lines (multi-org)". A lead line represents a distinct product or interest entry attached to a sales lead (opportunity header), carrying quantity, pricing, forecast, and pipeline-stage information used throughout the sales cycle.

The view is a reporting and integration layer rather than a transactional entity. It provides a read interface to opportunity-line data, including descriptive flexfield columns and multi-org operating unit context, allowing concurrent programs, OBIEE/BI Publisher reports, and custom extensions to query lead-line detail without depending directly on the underlying _ALL table. Because it is defined over a multi-org base object, the view returns rows across operating units and requires the appropriate MO security profile or an explicit ORG_ID predicate to constrain results.

Underlying Base Objects

Per the documented metadata, AS_LEAD_LINES is defined over a single referenced base object: the synonym AS_LEAD_LINES_ALL. In the EBS data model, AS_LEAD_LINES_ALL is the multi-org (partitioned by ORG_ID) table that stores the physical lead-line rows; the APPS.AS_LEAD_LINES view is a column-projected wrapper that selects all listed attributes from that table. No joins, filters, or derivations are applied in the view text, so the view is effectively a one-to-one pass-through of AS_LEAD_LINES_ALL.

This structure follows the standard EBS multi-org pattern: the _ALL table holds data for every operating unit, while the unsuffixed view is intended for cross-org querying by privileged or reporting responsibilities. The absence of a WHERE clause means row-level security is not enforced by the view itself.

Key Columns

• LEAD_LINE_ID — Primary key of the lead line; joins to the opportunity header via LEAD_ID.
• LEAD_ID — Foreign key to the parent sales lead/opportunity (AS_LEADS_ALL).
• ORG_ID — Operating unit that owns the line; drives multi-org partitioning.
• INVENTORY_ITEM_ID, ORGANIZATION_ID, UOM_CODE, QUANTITY — Product and quantity detail for the line.
• PRICE, TOTAL_AMOUNT, PRICE_VOLUME_MARGIN — Pricing and margin figures used in pipeline valuation.
• INTEREST_TYPE_ID, PRIMARY/SECONDARY_INTEREST_CODE_ID, INTEREST_STATUS_CODE — Classification of the opportunity interest.
• SALES_STAGE_ID, WIN_PROBABILITY, STATUS_CODE — Pipeline stage, confidence, and line status.
• FORECAST_DATE, ROLLING_FORECAST_FLAG, DECISION_DATE, SHIP_DATE — Forecast and scheduling attributes.
• QUOTED_LINE_FLAG, SOURCE_PROMOTION_ID, OFFER_ID — Quote and campaign linkage.
• PRODUCT_CATEGORY_ID, PRODUCT_CAT_SET_ID — Category hierarchy references.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–15 — Descriptive flexfield context and segments.
• Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY) and concurrent request columns (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID) support auditing and traceability.

Common Use Cases and Queries

Typical scenarios include pipeline reporting by product and stage, forecast analysis by forecast date, and integration extracts feeding data warehouses or CPQ systems. Because the view is a pass-through, a typical query filters on ORG_ID and joins to the lead header:

• Opportunity pipeline by operating unit: SELECT LEAD_LINE_ID, LEAD_ID, INVENTORY_ITEM_ID, QUANTITY, TOTAL_AMOUNT, WIN_PROBABILITY FROM AS_LEAD_LINES WHERE ORG_ID = :p_org_id AND STATUS_CODE = 'OPEN'.
• Forecast extract: SELECT LEAD_ID, FORECAST_DATE, TOTAL_AMOUNT FROM AS_LEAD_LINES WHERE ROLLING_FORECAST_FLAG = 'Y' AND FORECAST_DATE BETWEEN :start AND :end.
• Join to header for context: SELECT l.LEAD_LINE_ID, h.LEAD_NAME, l.TOTAL_AMOUNT FROM AS_LEAD_LINES l, AS_LEADS_ALL h WHERE l.LEAD_ID = h.LEAD_ID AND l.ORG_ID = h.ORG_ID.
• Flexfield reporting: SELECT LEAD_LINE_ID, ATTRIBUTE_CATEGORY, ATTRIBUTE1, ATTRIBUTE2 FROM AS_LEAD_LINES WHERE ATTRIBUTE_CATEGORY = :category.

Analysts should always constrain by ORG_ID where cross-operating-unit visibility is not intended, and should join to AS_LEADS_ALL to resolve header-level attributes absent from this view.