Results for “line_seq”

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

Overview

ICX_PO_REVISIONS_HEADER_V is a database view owned by the APPS schema within Oracle iProcurement (ICX). It functions as a lightweight, distinct projection over the temporary staging structure used during purchase order revision processing. Unlike a conventional reporting view that denormalizes or joins multiple base tables, this view exposes a narrowed set of header-level identifiers — specifically the line sequence, header identifier, and release identifier — drawn from a single temporary object. Its role is to present a de-duplicated list of purchase order revision header references, allowing calling programs and inquiry screens to iterate over distinct revision records without processing redundant rows that may exist in the temporary staging area.

The view is marked VALID across Oracle EBS 12.1.1 and 12.2.2. Because its definition is intentionally minimal, it is best understood as a supporting construct for internal iProcurement revision workflows rather than a general-purpose purchasing reporting view.

Underlying Base Objects

The view is defined over exactly one documented object: ICX_PO_REVISIONS_TEMP, which is exposed through a SYNONYM. The view text is a simple SELECT DISTINCT statement:

• SELECT DISTINCT LINE_SEQ, HEADER_ID, RELEASE_ID FROM ICX_PO_REVISIONS_TEMP

ICX_PO_REVISIONS_TEMP serves as the staging area where revision candidates are accumulated before or during the revision confirmation process. Because temporary data may carry duplicate combinations of header, release, and line sequence values, the DISTINCT operator in the view collapses these to a unique set. HEADER_ID and RELEASE_ID resolve to the underlying PO_HEADERS_ALL and PO_RELEASES_ALL identifiers in the purchasing schema, while LINE_SEQ is a sequence value associated with the staged revision line. The synonym layer allows APPS-owned code to reference the temporary table without hard-coding a schema prefix.

Key Columns

The view exposes three columns, each documented explicitly in the ETRM metadata:

• LINE_SEQ — The line sequence number. This is the column most directly tied to the user's search term. It identifies the ordinal position of a staged revision line, enabling ordering and correlation of revision entries against their purchasing document lines.
• HEADER_ID — The unique identifier of the purchase order header. This is the primary join key to PO_HEADERS_ALL and is used to retrieve the document number, supplier, and status of the purchase order being revised.
• RELEASE_ID — The release identifier for the associated blanket agreement or release. Where revisions apply to releases, this key links the revision reference to PO_RELEASES_ALL.

No additional descriptive columns (such as document numbers or dates) are exposed; consumers must join outward to resolve human-readable attributes.

Common Use Cases and Queries

Typical usage revolves around enumerating distinct staged revision headers, for example when a concurrent program or iProcurement page must confirm which purchase orders have pending revisions.

• Listing all distinct staged revision headers: SELECT DISTINCT HEADER_ID, RELEASE_ID FROM APPS.ICX_PO_REVISIONS_HEADER_V;
• Ordering revision lines per header: SELECT HEADER_ID, RELEASE_ID, LINE_SEQ FROM APPS.ICX_PO_REVISIONS_HEADER_V ORDER BY HEADER_ID, LINE_SEQ;
• Joining to purchasing headers for document detail: SELECT v.HEADER_ID, v.LINE_SEQ, p.SEGMENT1 FROM APPS.ICX_PO_REVISIONS_HEADER_V v, APPS.PO_HEADERS_ALL p WHERE v.HEADER_ID = p.HEADER_ID;

Because the source is a temporary structure, queries are most meaningful during the revision processing window, and results should not be treated as persistent purchasing data.