Results for “draft_line_status”

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

Overview

PO_LINES_MERGE_V is an Oracle E-Business Suite Purchasing (PO) view owned by the APPS schema. It is a denormalized reporting construct that joins draft purchasing line data against the associated draft header record, exposing both line-level and draft-level attributes in a single relational interface. Its name reflects its purpose: it is used during the merge of approved draft transactions back into the base purchasing tables, and equally serves as the query surface for reviewing proposed line changes before they are committed to PO_LINES_ALL.

The view carries a STATUS column together with OWNER_USER_ID, OWNER_ROLE, and DRAFT_ID, which indicates that its scope is the draft workflow introduced in Oracle Purchasing to support controlled, auditable change management on existing purchase orders. Rather than presenting live purchasing lines, the view presents the pending state of those lines. This distinction is critical for reporting and integration designs, since a row in this view represents an intent to change rather than a committed transaction.

Underlying Base Objects

As documented in the ETRM metadata for 12.2.2, PO_LINES_MERGE_V is defined over three referenced base objects:

• PO_LINES_DRAFT_ALL — aliased PLD in the view text; the primary source of line-level attributes, keyed by PO_LINE_ID and linked to its parent through PO_HEADER_ID.
• PO_DRAFTS — aliased DFT; supplies the draft envelope metadata including OWNER_USER_ID, OWNER_ROLE, STATUS, and DRAFT_ID.
• PO_LINES_ALL — referenced as the comparison target for committed line definitions, ensuring the draft projection aligns with the canonical line structure.

All three are accessed through APPS synonyms, consistent with standard EBS object resolution and the requirement that custom code never query the underlying tables directly across schema boundaries. Column naming mirrors PO_LINES_ALL almost exactly, which allows the merge process to project draft rows into the base line table without an intermediate mapping layer.

Key Columns

The projection includes a substantial set of line attributes. Notable groups include:

• Identity and lineage: DRAFT_ID, PO_LINE_ID, PO_HEADER_ID, LINE_NUM, LINE_TYPE_ID, FROM_HEADER_ID, FROM_LINE_ID, and REFERENCE_NUM establish provenance for the pending change.
• Change semantics: CHANGE_ACCEPTED_FLAG and DELETE_FLAG indicate whether the draft was accepted by the approver and whether the target line is marked for removal.
• Pricing and quantity: UNIT_PRICE, LIST_PRICE_PER_UNIT, NOT_TO_EXCEED_PRICE, ALLOW_PRICE_OVERRIDE_FLAG, QUANTITY, BASE_QTY, SECONDARY_QTY, MIN_ORDER_QUANTITY, MAX_ORDER_QUANTITY, MARKET_PRICE, and MIN_RELEASE_AMOUNT.
• Status and closure: CLOSED_CODE, CLOSED_FLAG, CLOSED_DATE, CLOSED_REASON, CLOSED_BY, CANCEL_FLAG, CANCEL_DATE, CANCEL_REASON, CANCELLED_BY, FIRM_STATUS_LOOKUP_CODE, USER_HOLD_FLAG, and UNORDERED_FLAG.
• Item and supplier detail: ITEM_ID, ITEM_REVISION, CATEGORY_ID, ITEM_DESCRIPTION, VENDOR_PRODUCT_NUM, CONTRACT_NUM, TAXABLE_FLAG, and UNIT_MEAS_LOOKUP_CODE.
• Descriptive flexfields: ATTRIBUTE_CATEGORY plus ATTRIBUTE1 through ATTRIBUTE15, alongside GLOBAL_ATTRIBUTE_CATEGORY.

Standard EBS audit columns are present throughout: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical applications include draft change auditing, approval workflow diagnostics, and reconciliation of pending line modifications before merge execution.

• Listing all pending line changes for a given draft:

SELECT draft_id, po_header_id, po_line_id, line_num,
       quantity, unit_price, change_accepted_flag, delete_flag
FROM   apps.po_lines_merge_v
WHERE  draft_id = :p_draft_id
ORDER  BY line_num;

• Identifying rejected or unaccepted line changes:

SELECT draft_id, po_line_id, line_num, status
FROM   apps.po_lines_merge_v
WHERE  NVL(change_accepted_flag,'N') = 'N';

Because the view reflects uncommitted draft state, reports built on it should always be scoped by DRAFT_ID or STATUS to avoid presenting stale or superseded change proposals.