Results for “pl_draft_id”

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

Overview

APPS.PO_SGD_MOD_LINES_V is an Oracle E-Business Suite view that exposes the incremental changes applied to open (draft) purchase order lines by the Seeded Generative Drafting and modification framework — the same change-tracking infrastructure that underpins the PO_ACTIONS / "Track Changes" and Supplier Generative Drafting features. Rather than presenting the purchase order line in its source-table form, the view normalizes each modified attribute of a draft line into a single row, so that a change to a single line can produce multiple rows — one per modified column. Each row is keyed by a composite of purchase order header, draft, and draft line identifiers.

Within EBS 12.1.1 and 12.2.2, this view is used primarily for reporting and integration. It allows a developer or report writer to retrieve the current draft (modified but unapproved) value of a purchase order line attribute alongside the identifying keys needed to link it back to the header and line. It is not a user-facing inquiry view; it is a technical view intended for diagnostics, change auditing, and custom extracts.

Underlying Base Objects

The view is defined entirely as a SELECT over the column/value rows produced by the underlying change-tracking tables, and its most significant characteristic is the heavy use of scalar subqueries in the SELECT list to decode normalized values into their displayed forms. The documented base objects include:

• PO_LINES_DRAFT_ALL — the draft line store; supplies the draft identifier and draft line identifier and, in the ITEM_ID decode, the item revision and job.
• PO_HEADERS_ALL and PO_LINES_ALL — the approved header and line tables, used in the FROM_HEADER_ID and FROM_LINE_ID decodes.
• PO_LINE_TYPES, PO_LOOKUP_CODES, and FND_LOOKUPS — lookup sources for line type, user document status, federal contract/IDC attributes, UOM, and yes/no flags.
• MTL_SYSTEM_ITEMS_VL, MTL_CATEGORIES_KFV, and MTL_UNITS_OF_MEASURE_TL — inventory item, category, and unit-of-measure descriptive flexfields.
• OKC_K_HEADERS_ALL_B — contract header reference for OKC_CONTRACT_HEADER_ID.
• PER_JOBS_VL and FINANCIALS_SYSTEM_PARAMS_ALL — job and inventory organization defaults used in the ITEM_ID decode.
• FND_GLOBAL (package) and PO_GEN_DIFF_PKG (package) — supplied for language context and the generative-diff processing logic.

Key Columns

The user's search term, pl_po_line_id, is the draft purchase order line identifier and is exposed by the view as PK3_VALUE — the third component of the view's composite key. This is the column to join when correlating a modified attribute row back to a specific draft line. Other key columns include:

• PK1_VALUE — the purchase order header identifier (PO_HEADER_ID).
• PK2_VALUE — the draft identifier (PL_DRAFT_ID).
• PK3_VALUE — the draft line identifier (PL_PO_LINE_ID).
• PK4_VALUE/PK5_VALUE — placeholders, returned as NULL in the documented definition.
• COL_NAME — the name of the modified attribute (e.g., LINE_TYPE_ID, ITEM_ID, CATEGORY_ID).
• COL_VALUE — the raw stored value, which the view decodes into a display value via the scalar subqueries.

Common Use Cases and Queries

Typical scenarios include auditing which attributes were changed on a draft line, extracting current draft values for downstream integration, and reproducing the "changes pending approval" display. A representative query that resolves the user's search term is:

• SELECT pk1_value header_id, pk2_value draft_id, pk3_value pl_po_line_id, col_name, col_value FROM apps.po_sgd_mod_lines_v WHERE pl_po_line_id = :line_id;
• Join back to PO_LINES_DRAFT_ALL on pl_po_line_id = pl.po_line_id AND pk2_value = pl.draft_id to retrieve the line context.
• Filter by col_name IN ('ITEM_ID','LINE_TYPE_ID','CATEGORY_ID') to inspect specific decoded attributes.

Because each modified column yields its own row, consumers should aggregate or pivot on PK1/PK2/PK3 and COL_NAME rather than treating the view as one-row-per-line.