Results for “contractor_name”

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

Overview

PO_SGD_MOD_LINES_V is a Purchasing (PO) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is a supporting object for the Supplier Goods Description (SGD) modification framework, exposing purchase order line attribute values in a pivoted, key-value format so that downstream processes can compare, display, and apply changes to existing PO lines. Rather than presenting one row per line with a fixed set of columns, the view unpivots draft line attributes into a generic structure consisting of a composite key and a name/value pair (COL_NAME, COL_VALUE), which the SGD comparison package PO_GEN_DIFF_PKG consumes.

The view therefore functions less as an end-user reporting object and more as an integration and internal-processing aid. A user searching for pl_po_line_id will find it surfaced here as PK3_VALUE, which is one of the primary key components that identify each modified line record.

Underlying Base Objects

The view is defined over a mixture of transactional base tables, descriptive/validation lookups, and reference views and packages. Documented referenced objects include:

• PO_LINES_DRAFT_ALL — the draft copy of PO lines that holds the proposed modifications, and the primary source of the unpivoted attribute rows.
• PO_HEADERS_ALL and PO_LINES_ALL — the live PO header and line tables, used in the SELECT list to resolve FROM_HEADER_ID and FROM_LINE_ID references.
• PO_LINE_TYPES and PO_LOOKUP_CODES — provide descriptive decode values for line type, user document status, contract and IDC attributes, cost constants, and similar lookup-driven columns.
• MTL_SYSTEM_ITEMS_VL, MTL_CATEGORIES_KFV, and MTL_UNITS_OF_MEASURE_TL — resolve item, category, and unit-of-measure values into user-facing concatenated descriptions.
• OKC_K_HEADERS_ALL_B — resolves the related contract number.
• FND_LOOKUPS, FND_GLOBAL, PER_JOBS_VL, and FINANCIALS_SYSTEM_PARAMS_ALL — supply lookup meanings, session/language context, job names, and organization parameters.
• PO_GEN_DIFF_PKG — the package that drives the diff/SGD comparison logic over this view.

Key Columns

The view exposes a small, deliberately generic column set:

• PK1_VALUE — the purchase order header identifier (PO_HEADER_ID).
• PK2_VALUE — the draft line identifier (PL_DRAFT_ID).
• PK3_VALUE — the PO line identifier (PL_PO_LINE_ID), the value surfaced when users search for pl_po_line_id.
• PK4_VALUE / PK5_VALUE — reserved placeholders, returned as NULL in the documented view text.
• COL_NAME — the name of the line attribute being represented (for example LINE_TYPE_ID, CATEGORY_ID, ITEM_ID, UNIT_MEAS_LOOKUP_CODE, or USER_DOCUMENT_STATUS).
• COL_VALUE — the raw or decoded value for that attribute, resolved through the DECODE expression in the SELECT list.

Common Use Cases and Queries

Typical usage centers on retrieving the modified attributes for a given draft line or correlating a draft line back to its live PO line.

• Listing all modified attributes for a specific PO line:

SELECT pk1_value, pk2_value, pk3_value, col_name, col_value
FROM   apps.po_sgd_mod_lines_v
WHERE  pk3_value = :pl_po_line_id;

• Filtering for a single attribute across all modified lines:

SELECT pk1_value, pk3_value, col_value
FROM   apps.po_sgd_mod_lines_v
WHERE  col_name = 'ITEM_ID';

Because the view is keyed on draft identifiers, it is most appropriate for change-propagation and validation routines rather than ad hoc financial reporting. Queries should generally be constrained by PK3_VALUE to avoid the full unpivot of all draft lines.