Results for “po_sgd_mod_hdrs_uda_v”

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

Overview

PO_SGD_MOD_HDRS_UDA_V is an APPS-owned reporting view within the Oracle E-Business Suite Purchasing (PO) module. Its name reflects its purpose: it surfaces the descriptive and user-defined attribute (UDA) values attached to purchasing document headers generated through the Supplier Governance / contract modification (SGD) flows. Rather than storing data itself, the view projects key-value pairs from the extensible attribute storage model into a flattened, query-friendly shape.

The view is especially relevant in Public Sector procurement configurations, where header attributes such as contract category, priority code, DPAS rating, NAICS classification, set-aside type and status, size standard, CCR expiration reason, and modification authority drive downstream approvals and reporting. Because these values are stored generically as attribute codes, PO_SGD_MOD_HDRS_UDA_V performs the decode to human-readable descriptions, making it suitable for BI Publisher reports, OAF/ADF list displays, and interface extracts. In 12.1.1 and 12.2.2 the view remains VALID, though available columns and lookup sets may vary by patch level.

Underlying Base Objects

The view is defined over the following documented objects:

• PO_HEADERS_ALL_EXT_B (synonym) — the extensible attribute table holding the header-level attribute rows. This supplies the primary keys PO_HEADER_ID and DRAFT_ID, the attribute column name, and the stored COL_VALUE.
• EGO_FND_DSC_FLX_CTX_EXT (synonym) — the descriptive flexfield context extension, joined to map the internal column reference to the user-facing attribute segment name (ATTR_NAME).
• FND_DESCR_FLEX_COLUMN_USAGES (synonym) — descriptive flexfield column usage metadata used during the mapping of segments.
• PO_LOOKUP_CODES (view) — the Purchasing lookup view supplying the DESCRIPTION or DISPLAYED_FIELD text for each decoded code.
• FND_LOOKUP_VALUES (synonym) — the common lookup table, used here for values such as NAICS through lookup type FV_NAICS_TYPE, with USERENV('LANG') applied for language.
• FND_GLOBAL (package) and PO_GEN_DIFF_PKG (package) — session and utility references supporting context and language resolution.

Key Columns

• PK1_VALUE (PO_HEADER_ID) — identifier of the purchasing document header.
• PK2_VALUE (DRAFT_ID) — identifier of the draft or modification version to which the attribute belongs.
• PK3_VALUE – PK5_VALUE — reserved placeholders, returned as NULL, preserving a uniform multi-part key signature for generic consumers.
• COL_NAME — the physical extensible attribute column name.
• COL_VALUE — the raw stored attribute value (a lookup code) prior to decoding.
• Decoded description — the expression that resolves COL_VALUE to descriptive text. Based on the decode logic, MOD_AUTH and NO_COMP_RSN resolve via DESCRIPTION, while CONTRACT_CATEGORY, ADMIN_SCD, DPAS_RATING, PRIORITY, CUST_PROJ_CODE, SET_ASIDE_TYPE, SIZE_STANDARD, SET_ASIDE_STAT, and CCR_EXP_REASON resolve via DISPLAYED_FIELD from PO_LOOKUP_CODES. NAICS resolves via MEANING from FND_LOOKUP_VALUES.

Common Use Cases and Queries

Typical uses include displaying header UDAs on a purchasing document page, extracting attribute descriptions for contract registers, and validating that required attributes are populated before approval.

SELECT pk1_value        AS po_header_id,
       pk2_value        AS draft_id,
       col_name,
       col_value
FROM   apps.po_sgd_mod_hdrs_uda_v
WHERE  pk1_value = :p_po_header_id;

To list all populated attributes with their decoded text for a set of headers:

SELECT uda.pk1_value,
       uda.col_name,
       uda.col_value
FROM   apps.po_sgd_mod_hdrs_uda_v uda,
       apps.po_headers_all       poh
WHERE  uda.pk1_value = poh.po_header_id
AND    poh.org_id    = :p_org_id;

Because the view performs scalar subquery decoding per row, queries over large document ranges should be filtered by PK1_VALUE or DRAFT_ID and joined to PO_HEADERS_ALL rather than scanned in full, to avoid repeated lookup access and performance degradation.