Search Results oe_ak_order_lines_v




Overview
Explore in AI Chat

Overview

OE_AK_ORDER_LINES_V is an Oracle E-Business Suite (EBS) view owned by the APPS schema and validated under the Order Management (ONT) product module. It conforms to the "AK" naming convention used by Oracle's extensible attribute/region framework, which generates query-oriented views intended for use by the Oracle Application Framework (OAF), descriptive flexfield, and extension consumers. In release 12.1.1 and 12.2.2 this view exposes the sales order line entity, presenting one row per order line, in a flattened projection whose columns map directly to attributes of the underlying OE_ORDER_LINES_ALL table.

The view is principally a reporting and integration access path. Rather than requiring consumers to join the multi-organization base table directly, OE_AK_ORDER_LINES_V offers a stable, read-only projection of order line data, including priced and fulfilled quantities, scheduling and shipping attributes, and the order line's descriptive and global flexfield segments. This makes it suitable for ad hoc queries, custom concurrent programs, OAF-based extensions, and downstream integration extracts where a broad horizontal slice of the order line record is required.

Underlying Base Objects

The documented referenced base objects for this view are:

  • OE_ORDER_LINES_ALL (SYNONYM) — the primary transactional table holding all sales order line records across operating units.
  • HZ_CUST_ACCOUNTS (SYNONYM) — the Trading Community Architecture (TCA) customer account entity.
  • HZ_PARTIES (SYNONYM) — the TCA party entity representing the customer or organization.

The view text confirms OE_ORDER_LINES_ALL (aliased OOL) as the driving source from which nearly all projected columns are drawn, including ACCOUNTING_RULE_ID, ACTUAL_ARRIVAL_DATE, ACTUAL_SHIPMENT_DATE, AGREEMENT_ID, the ATTRIBUTE1 through ATTRIBUTE20 descriptive flexfield columns, GLOBAL_ATTRIBUTE1 through GLOBAL_ATTRIBUTE20, and the CONFIG_*, DEMAND_*, and FULFILLED_QUANTITY columns. The presence of HZ_CUST_ACCOUNTS and HZ_PARTIES indicates that customer identification data is joined to the line to support account and party context. A literal constant value of 1 appears in the projection, typically used as a flag or synthetic column for framework consumption. Because OE_ORDER_LINES_ALL is an _ALL table, the view is subject to the same multi-organization and org-security behavior as the base table; in 12.2.2, this view is documented as a VIEW owned by APPS and VALID.

Key Columns

Columns exposed by the view fall into several functional groups:

Common Use Cases and Queries

Typical uses include order line reporting, extracting flexfield values, and integration payloads. A representative query:

SELECT line_id, org_id, ordered_item, ordered_quantity,
       fulfilled_quantity, actual_shipment_date,
       attribute1, cust_po_number
FROM   apps.oe_ak_order_lines_v
WHERE  org_id = :p_org_id
AND    booked_flag = 'Y';

Because the view projects the broad OE_ORDER_LINES_ALL record plus customer context, it is well suited to concurrent reporting, OAF extensions, and interface extracts where the consuming program requires both transactional order line attributes and customer account/party context without authoring multi-table joins. As with any _ALL-derived object in 12.1.1 and 12.2.2, callers should apply org-security predicates and avoid treating the view as a substitute for the base table where DML or full column coverage is required.