Results for “line_seq”

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

Overview

POS_PO_REVISIONS_LINE_V is a documented Oracle E-Business Suite view owned by the APPS schema in the PO (Purchasing) product module. It is classified as VALID in the ETRM metadata for release 12.2.2 and is also present in 12.1.1 deployments. The view presents a deduplicated, line-level projection of purchase order revision data, exposing only three columns: LINE_SEQ, LINE_ID, and RELEASE_ID. Its defining characteristic is the DISTINCT operator applied to the result set, which collapses duplicate (LINE_SEQ, LINE_ID, RELEASE_ID) combinations into a single row. The view is therefore not a transactional detail view but a lightweight enumeration of the PO lines and releases that are subject to revision processing at a given point in time.

Because the view filters on LINE_ID IS NOT NULL, it excludes header-level or non-line revision records. This makes it suitable for consumers that must iterate only over concrete document lines, and it explains the view's role as a feeder for revision-related reporting, validation logic, and integration extracts.

Underlying Base Objects

The view is defined over a single documented base object, POS_PO_REVISIONS_TEMP_V, which is itself a view in the APPS schema. The ETRM metadata lists POS_GET (PACKAGE) as a referenced base object as well, indicating that POS_GET supplies server-side logic used by the revision view stack. The documented view text is:

• SELECT DISTINCT LINE_SEQ, LINE_ID, RELEASE_ID FROM POS_PO_REVISIONS_TEMP_V WHERE LINE_ID IS NOT NULL

This means POS_PO_REVISIONS_LINE_V derives no data of its own and holds no storage; it is a pure projection and deduplication layer over POS_PO_REVISIONS_TEMP_V. Any change to the underlying temporary view is immediately reflected here. The relationship to POS_GET is indirect: the package typically prepares or resolves revision context that the underlying view consumes.

Key Columns

• LINE_SEQ — The line sequence number identifying the ordering of the PO line within its document. This is the column most frequently searched, and it is included in the DISTINCT list, so each combination of sequence, line, and release appears only once.
• LINE_ID — The internal unique identifier of the purchase order line. The view enforces LINE_ID IS NOT NULL, guaranteeing that every returned row maps to a real line record.
• RELEASE_ID — The identifier of the associated release or shipment schedule. It is nullable, so rows may represent lines without an explicit release context.

No descriptive attributes (item, quantity, price, status) are exposed. Callers must join back to PO_HEADERS_ALL, PO_LINES_ALL, or equivalent tables to retrieve business detail.

Common Use Cases and Queries

Typical scenarios include identifying revision-affected lines before reprocessing, building validation reports, and feeding interface programs that need a distinct line/release population. A basic query is:

• SELECT line_seq, line_id, release_id FROM apps.pos_po_revisions_line_v WHERE line_seq = 1;

To retrieve descriptive context, join to PO_LINES_ALL:

• SELECT v.line_seq, v.line_id, l.item_description FROM apps.pos_po_revisions_line_v v, apps.po_lines_all l WHERE v.line_id = l.line_id;

Because of the DISTINCT clause, the view is safe for use in EXISTS subqueries and set-based comparisons without duplicate-row hazards. Performance is tied directly to POS_PO_REVISIONS_TEMP_V, so query tuning efforts should target that underlying view and POS_GET.