Results for “okx_opp_lines_v”

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

Overview

OKX_OPP_LINES_V is a reporting view owned by the APPS schema within the OKX — Contracts Integration product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes opportunity (lead) line detail in a denormalized, integration-friendly structure that presents a single logical row per lead line. The view is classified as VALID and is intended primarily for use by Oracle's Contracts Integration flows, where opportunity line data must be surfaced for downstream processing, order capture, quoting, or external system consumption.

The view is commonly referenced when a user or report searches on the identifier opp_header_id, which is the column the view maps from the underlying header key. In the view definition, ASL.LEAD_ID is aliased to OPP_HEADER_ID, providing a consistent naming convention that presents the lead header identity alongside its associated line attributes. This makes the view a convenient abstraction layer over the raw lead line table.

Underlying Base Objects

The view is defined over a single documented base object: AS_LEAD_LINES_ALL, accessed through a SYNONYM in the APPS schema. The defining SQL selects columns directly from this table without joins, aggregations, or filters:

• AS_LEAD_LINES_ALL ASL — the source of all line-level and header reference data exposed by the view.

Because the view wraps a single table, there is no join complexity, no outer join semantics, and no data transformation beyond column aliasing. Two synthetic columns, ID1 and ID2, are also projected: ID1 is populated from ASL.LEAD_LINE_ID, while ID2 is a literal '#' character. These appear to support integration or interface formatting requirements. Referential integrity is inherited entirely from AS_LEAD_LINES_ALL.

Key Columns

• OPP_HEADER_ID — The opportunity/lead header identifier, sourced from ASL.LEAD_ID. This is the primary search column and links each line back to its parent opportunity header.
• ID1 — The lead line identifier (ASL.LEAD_LINE_ID), uniquely identifying the line record.
• INVENTORY_ITEM_ID — The inventory item associated with the line.
• ORGANIZATION_ID — The inventory organization context for the item.
• UOM_CODE — Unit of measure for the line quantity.
• QUANTITY — The quantity captured on the opportunity line.
• TOTAL_AMOUNT — The monetary value associated with the line.
• SALES_STAGE_ID — Reference to the sales stage of the opportunity.
• WIN_PROBABILITY — Forecasted probability of winning the opportunity.
• STATUS_CODE — Current status of the line or opportunity.
• DECISION_DATE — Expected or actual decision date.
• ORG_ID — Operating unit identifier supporting multi-org security.

Common Use Cases and Queries

Typical usage centers on retrieving opportunity line detail for a given header, or reporting on lines by item, organization, or operating unit. A common pattern filters by OPP_HEADER_ID when the user has identified a lead. For example:

SELECT opp_header_id, inventory_item_id, organization_id, uom_code, quantity, total_amount, win_probability, status_code, org_id FROM apps.okx_opp_lines_v WHERE opp_header_id = :lead_id;

Reporting queries often aggregate expected revenue by organization or sales stage, or feed integration interfaces that require item, quantity, and amount fields. Because the view maps LEAD_ID to OPP_HEADER_ID and LEAD_LINE_ID to ID1, it can be treated as an opportunity-centric substitute for querying AS_LEAD_LINES_ALL directly, while preserving ORG_ID for multi-org filtering.