Search Results inv_office




Overview

The view APPS.PO_SGD_MOD_ADDRESSES_UDA_V is a descriptive flexfield extraction view defined in the Oracle E-Business Suite Purchasing module. It presents header-level address attribute values that are stored against the PO_HEADER_EXT_ATTRS descriptive flexfield context addresses. The view is specifically designed to surface the flexfield segments associated with office-type address records, such as SBA office, procurement administration office, invoicing office, payment office, issuing office, COTR office, administrative office, and requisitioning office.

The name incorporates "SGD" and "MOD", indicating the view belongs to the supplier gateway / modification (draft change) infrastructure that tracks modifications made through the PO change draft process. The _UDA_V suffix denotes a user-defined attribute view. Its principal reporting role is to expose flexfield values in a normalized, name-value format keyed by the purchase order header and the draft identifier, which makes it suitable for change-document comparison, interface extraction, and attribute-level audit reporting.

Underlying Base Objects

The view is defined over five documented base objects, joined to produce a pivoted attribute representation:

  • PO_HEADERS_ALL_EXT_B — the header extension table holding the descriptive flexfield attribute groups for purchase order headers and drafts. It provides the po_header_id, draft_id, and the C_EXT_ATTR / N_EXT_ATTR segment columns that are later unpivoted.
  • EGO_FND_DSC_FLX_CTX_EXT — supplies the attr_group_id and the descriptive_flex_context_code linking header extension rows to the addresses context.
  • FND_DESCR_FLEX_COLUMN_USAGES — defines which flexfield segments are active and displayed for the PO_HEADER_EXT_ATTRS flexfield, application 201, context addresses. Rows with display_flag = 'H' are excluded.
  • HR_LOCATION_EXTRA_INFO — used to derive a description for the address code segment, resolving LEI_INFORMATION1 where information_type = 'CLM_OFFICE_CODE'.
  • PO_GEN_DIFF_PKG — a PL/SQL package supplying getModPK1 and getModPK2, which return the current modification (draft) primary keys against which header extension rows are filtered.

Key Columns

  • PK1_VALUE — the po_header_id, uniquely identifying the purchase order header.
  • PK2_VALUE — the draft_id, identifying the change draft associated with the modification.
  • PK3_VALUE through PK5_VALUE — reserved null placeholders, present to satisfy the uniform key structure expected by ETRM and generic attribute extractors.
  • COL_NAME — the attribute name, constructed as the uppercased concatenation of address_type and the flexfield segment name, for example SBA_OFFICE_ATTRIBUTE1.
  • COL_VALUE — the attribute value retrieved from the unpivoted extension columns (C_EXT_ATTR5, C_EXT_ATTR6, N_EXT_ATTR1 through N_EXT_ATTR3).
  • COL_DESC — a descriptive value populated only for the addresscode segment, resolved from HR location extra information.

Common Use Cases and Queries

The view is typically queried to compare address attribute values across a purchase order and its draft, or to extract office address data for downstream systems. Because po_header_ext_attrs is the searched term, this view is the natural access point for reporting on that flexfield at header level.

A representative query retrieves all address attributes for a given header and draft:

  • SELECT pk1_value, pk2_value, col_name, col_value, col_desc FROM apps.po_sgd_mod_addresses_uda_v WHERE pk1_value = :po_header_id AND pk2_value = :draft_id;
  • Filtering by attribute group, for example WHERE col_name LIKE 'SBA_OFFICE%', isolates a specific office address type.
  • Joining back to PO_HEADERS_ALL on PK1_VALUE = PO_HEADER_ID enriches the output with segment1, vendor, and operating unit context.
  • Aggregating with MAX(DECODE(col_name, ...)) pivots the name-value pairs back into columns for interface files or concurrent program output.

Because the view depends on the draft change package, callers should ensure any active modification context is established before querying, as the PO_GEN_DIFF_PKG values drive which extension rows are returned.