Results for “po_sgd_lines_v”

25 results




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

Overview

The APPS.PO_SGD_LINES_V view is a Purchasing (PO) module database object within Oracle E-Business Suite 12.1.1 and 12.2.2. It is a VALID view owned by the APPS schema and serves as a line-level presentation layer for Supplier Goods Documentation (SGD) and related draft purchasing content. Rather than storing transactional data directly, the view pivots and resolves coded attribute values held on purchase order line drafts into human-readable descriptions.

The central mechanism of the view is a DECODE expression keyed on a column named COL_NAME. Depending on the value of COL_NAME, the view substitutes the raw COL_VALUE with a descriptive lookup from a related reference object. This makes PO_SGD_LINES_V particularly valuable for reporting and integration scenarios where consumers require translated, user-facing values instead of internal identifiers. Given the user search term contractor_name, the view is frequently consulted when assembling contractor and contract-related supplier documentation, where descriptive fields must be surfaced alongside the underlying foreign keys.

Underlying Base Objects

The documented referenced base objects indicate that PO_SGD_LINES_V is a join- and subquery-intensive view consolidating data from transactional, reference, and lookup sources. The primary transactional anchors are PO_HEADERS_ALL, PO_LINES_ALL, and PO_LINES_DRAFT_ALL, which supply header, line, and draft-level context. PO_LINE_TYPES and PO_LOOKUP_CODES provide code-to-description translation, while FND_LOOKUPS resolves generic lookup meanings such as YES_NO values. Organizational and item context is drawn from MTL_SYSTEM_ITEMS_VL, MTL_CATEGORIES_KFV, MTL_UNITS_OF_MEASURE_TL, PER_JOBS_VL, and FINANCIALS_SYSTEM_PARAMS_ALL. Contract-related data is sourced from OKC_K_HEADERS_ALL_B. The view also references the PO_GEN_DIFF_PKG package and the FND_GLOBAL package, the latter most likely for session context such as USERENV('LANG') used in unit-of-measure translation.

Key Columns

  • PK1_VALUE / PK2_VALUE / PK3_VALUE — Composite key components mapping to PO_HEADER_ID, DRAFT_ID, and PL_PO_LINE_ID respectively, enabling correlation back to the header, draft, and line.
  • COL_NAME — Identifies which attribute is being presented (for example ITEM_ID, CATEGORY_ID, CONTRACT_TYPE, COST_CONSTRAINT, or CLM_IDC_TYPE).
  • COL_VALUE — Holds the resolved description corresponding to COL_NAME, produced through the DECODE logic.
  • ITEM_ID — Returns the concatenated item segment, revision, and job name, combining MTL_SYSTEM_ITEMS_VL, PER_JOBS_VL, and PO_LINES_ALL.
  • FROM_HEADER_ID / FROM_LINE_ID — Resolve to the originating contract document number and line number display, supporting contractor and contract traceability.
  • OKE_CONTRACT_HEADER_ID — Returns the contract number from OKC_K_HEADERS_ALL_B, relevant for contractor-associated documentation.
  • USER_DOCUMENT_STATUS, CONTRACT_TYPE, COST_CONSTRAINT — Return displayed lookup fields or descriptions for federal and user-defined statuses.

Common Use Cases and Queries

Typical uses include building supplier goods documentation reports, validating draft line attributes, and extracting contractor or contract context for downstream integration. The view is often filtered by COL_NAME to isolate a specific attribute.

Sample query returning item and category descriptors for a given header:

  • SELECT PK1_VALUE, DRAFT_ID, PL_PO_LINE_ID, COL_NAME, COL_VALUE FROM APPS.PO_SGD_LINES_V WHERE COL_NAME IN ('ITEM_ID','CATEGORY_ID') AND PK1_VALUE = :p_header_id;

Sample query surfacing contract-related context for contractor reporting:

  • SELECT PK1_VALUE, OKE_CONTRACT_HEADER_ID, FROM_HEADER_ID, FROM_LINE_ID FROM APPS.PO_SGD_LINES_V WHERE COL_NAME = 'OKE_CONTRACT_HEADER_ID';

Because the view resolves numerous correlated subqueries, queries should constrain by PK1_VALUE or DRAFT_ID where possible to control execution cost, and access should respect the security and language session context established through FND_GLOBAL.