Search Results col_value




Overview

PO_SGD_MOD_DISTRIBUTIONS_V is an APPS-owned view in the Oracle E-Business Suite Purchasing (PO) module. It is a key-flexfield style view over the purchasing distributions entity, presenting distribution data in a normalized, attribute-per-row format. Each row represents a single attribute (COL_NAME) and its corresponding value (COL_VALUE) for a given purchase order distribution, rather than presenting all attributes across many columns in a single wide row.

The view is intended to support the Supplier Gateway / supplier-facing modification flow, where purchasing documents are staged in draft tables before final submission. Its design makes it straightforward for integration layers and reporting tools to iterate over distribution attributes generically, since consumers can pivot or filter on COL_NAME and COL_VALUE instead of binding to a fixed column list. The view is documented as VALID in the ETRM metadata for 12.1.1 and 12.2.2.

Underlying Base Objects

The view is defined over PO_DISTRIBUTIONS_DRAFT_ALL, which supplies the draft distribution records and the primary key lineage (PO_HEADER_ID, DRAFT_ID, PO_LINE_ID, LINE_LOCATION_ID, PO_DISTRIBUTION_ID). The inner query converts numeric distribution attributes to character strings via TO_CHAR so that they can be represented uniformly in the COL_VALUE column.

The SELECT list also joins or sub-selects from several reference objects to resolve stored codes and IDs into meaningful descriptions:

The package PO_GEN_DIFF_PKG is also referenced in the documented base object list, reflecting its role in the draft and difference-processing logic that feeds this view.

Key Columns

The view exposes five key-flex identifiers that identify the distribution context: PK1_VALUE (PO_HEADER_ID), PK2_VALUE (DRAFT_ID), PK3_VALUE (PO_LINE_ID), PK4_VALUE (LINE_LOCATION_ID), and PK5_VALUE (PO_DISTRIBUTION_ID). Attribute rows are then described by COL_NAME and COL_VALUE.

  • COL_NAME — the attribute being represented, for example CLM_DEFENCE_FUNDING, DESTINATION_TYPE_CODE, DELIVER_TO_LOCATION_ID, DELIVER_TO_PERSON_ID, CODE_COMBINATION_ID, ACCRUAL_ACCOUNT_ID, VARIANCE_ACCOUNT_ID, PROJECT_ID, TASK_ID, EXPENDITURE_ORGANIZATION_ID, or OKE_CONTRACT_LINE_ID.
  • COL_VALUE — the raw stored value for that attribute. The searched term "col_value" is therefore the central column of the view; consumers filter or pivot on it to retrieve a single distribution attribute.
  • COL_DESC — the decoded, human-readable description produced by the DECODE expression. For recognized COL_NAME values it returns the resolved meaning, name, code, or concatenated segments; for all other attributes it returns NULL.

Common Use Cases and Queries

A typical use is to report a single attribute for all draft distributions, for example retrieving the deliver-to location for each distribution:

  • SELECT PK1_VALUE, PK5_VALUE, COL_VALUE FROM PO_SGD_MOD_DISTRIBUTIONS_V WHERE COL_NAME = 'DELIVER_TO_LOCATION_ID';
  • SELECT PK1_VALUE, PK5_VALUE, COL_DESC FROM PO_SGD_MOD_DISTRIBUTIONS_V WHERE COL_NAME = 'DESTINATION_TYPE_CODE';
  • SELECT PK5_VALUE, COL_NAME, COL_VALUE FROM PO_SGD_MOD_DISTRIBUTIONS_V WHERE PK1_VALUE = :po_header_id ORDER BY PK5_VALUE, COL_NAME;

Because the view is normalized, integration code can retrieve all attributes for one distribution and reconstruct a wide record, while reporting tools can pivot COL_NAME and COL_DESC for user-facing displays. Note that COL_DESC returns NULL for attributes not enumerated in the DECODE, so consumers requiring a display value for other attributes must fall back to COL_VALUE or supply their own translation.