Search Results fsc_psc

Overview

The view APPS.PO_SGD_LINES_UDA_V is a purchasing-line descriptive flexfield extraction view within Oracle E-Business Suite. It presents the user-defined attribute (UDA) values attached to purchasing document lines in a vertically unpivoted, name-value format, meaning that each descriptive flexfield segment becomes its own row rather than appearing as a column on the line record. The view derives its data from the purchasing line descriptive flexfield context extension table and joins to a series of lookup and reference sources to render coded values into their human-readable descriptions.

This object is particularly significant in the context of government, defense, and public-sector procurement, where descriptive flexfields are used to capture structured attribute data required by contracting regulations. The term "SGD" relates to the purchasing "Segment/Government Data" descriptive flexfield context used in Oracle's Contract Lifecycle Management and federal procurement extensions. Users investigating the string "fv_psc_type" are typically examining how Product Service Code (PSC) values are resolved through the view, since one branch of the view's DECODE logic explicitly references the lookup type FV_PSC_TYPE.

Underlying Base Objects

The documented base objects include the descriptive flexfield context extension synonym EGO_FND_DSC_FLX_CTX_EXT, which supplies the attribute name and column value pairs, and FND_DESCR_FLEX_COLUMN_USAGES, which supplies the flexfield column metadata via the alias ega in the view text. The purchasing lines are represented through the synonyms PO_LINES_ALL, PO_LINES_ALL_EXT_B, and the draft synonym PO_LINES_DRAFT_ALL. Value resolution is performed against FND_LOOKUP_VALUES, MTL_UNITS_OF_MEASURE_VL, HR_LOCATIONS_ALL, HR_LOCATION_EXTRA_INFO, and the view PO_LOOKUP_CODES.

Supporting program units include the FND_GLOBAL package, used to determine the session language through USERENV('LANG'), and PO_GEN_DIFF_PKG, which participates in the differential change tracking of the underlying purchasing line attributes.

Key Columns

• PK1_VALUE, PK2_VALUE, PK3_VALUE — Surrogate key columns mapped to po_header_id, draft_id, and po_line_id, allowing each attribute row to be traced to its parent purchasing line.
• COL_NAME — The descriptive flexfield segment or column name (ega.col_name) to which the value belongs; this is the attribute identifier.
• COL_VALUE — The raw stored value of the flexfield segment as captured on the line record.
• Resolved display column — The final project column carries the decoded, user-facing value. It resolves 'UOM' to the unit of measure description, 'FSC_PSC' to the meaning in lookup types FV_FSC_TYPE or FV_PSC_TYPE, 'NAICS' to FV_NAICS_TYPE meanings, and operational codes such as 'MDAPS_MAIS', 'PRGM_CODE', 'CUST_PRJ_CODE', 'INSP_RESP', 'INSP_LOC', and 'ACCP_LOC' to their displayed descriptions via PO_LOOKUP_CODES.
• Location-derived columns — Segments 'INSP_ADD_LOC' and 'ACCP_ADD_LOC' resolve to HR_LOCATIONS_ALL.LOCATION_CODE, while 'INSP_ADD_CODE' and 'ACCP_ADD_CODE' resolve through HR_LOCATION_EXTRA_INFO with information type 'CLM_OFFICE_CODE'.

Common Use Cases and Queries

The view is used in reporting and interface extraction where the flexible attribute set must be flattened for downstream consumption. A typical query retrieves all attributes for a given line:

• SELECT pk1_value, pk3_value, col_name, col_value FROM apps.po_sgd_lines_uda_v WHERE pk3_value = :line_id;
• To isolate PSC data and confirm the FV_PSC_TYPE resolution path, filter on the segment name corresponding to 'FSC_PSC' and compare col_value against the decoded output.
• For language-sensitive reporting, the resolution honours userenv('lang'), so multi-language deployments should verify that the lookup values exist for the active session language.

Because the view joins to multiple lookup and reference tables, queries should filter on parent keys to avoid full scans, and consumers should note that unresolvable col_value entries return NULL in the display column.