Search Results po_document_styles




Overview

PO.PO_DOC_STYLE_VALUES is a configuration table in the Oracle E-Business Suite Procurement (PO) schema that stores the permitted values associated with a purchasing document style. A document style defines the behavior and allowable selections available to a buyer when creating a requisition, purchase order, or similar document. This table acts as the child of PO_DOCUMENT_STYLES, resolving the individual attributes of a style to the discrete values that the style allows. Each row binds a style, an attribute name, and a specific allowed value, with an enablement flag governing whether that combination is currently active. The table resides in the APPS_TS_TX_DATA tablespace and is owned by the PO schema under FND Design Data PO.PO_DOC_STYLE_VALUES.

From a dimensional modeling perspective, the heuristic Data Vault classification for this object is standalone, based on its foreign key structure. In practice, the table functions as a satellite-like attribute set attached to the document style hub (PO_DOCUMENT_STYLES), recording the many allowable values that qualify each style. The classification is offered as a modeling suggestion rather than a prescriptive design.

Key Information Stored

The table contains ten documented columns. The most significant are described below.

The composite primary key is PO_DOC_STYLE_VALUES_PK over (STYLE_ID, STYLE_ATTRIBUTE_NAME, STYLE_ALLOWED_VALUE). The unique index PO_DOC_STYLE_VALUES_U1, which the user searched for, extends that same set of business-key columns with ZD_EDITION_NAME, reflecting the edition-aware uniqueness model in release 12.2.2. The surrogate key is therefore effectively the composite style/attribute/value combination, while the unique index represents the edition-aware business-key candidate.

Common Use Cases and Queries

This table is most frequently queried to validate or report on the configuration of document styles. A typical scenario is verifying which values a given style permits for each attribute. A sample query follows:

  • SELECT style_id, style_attribute_name, style_allowed_value, enabled_flag FROM po.po_doc_style_values WHERE style_id = :p_style_id;
  • SELECT * FROM po.po_doc_style_values WHERE style_attribute_name = 'LINE_TYPES' AND enabled_flag = 'Y';

Reporting use cases include auditing which styles enable a particular pay item type, confirming that a style's allowed purchase bases align with organizational policy, and troubleshooting why a buyer cannot select a given line type during document entry. Joining to PO_DOCUMENT_STYLES supplies the style name for readable output, and joining enabled values to FND_LOOKUP_VALUES validates the coded values against the application lookups.

Related Objects

The following objects are most significant in relation to this table, using the documented foreign key and dependency data.

  • PO.PO_DOCUMENT_STYLES — Parent table; joined on PO_DOCUMENT_STYLES.STYLE_ID = PO_DOC_STYLE_VALUES.STYLE_ID.
  • PO.PO_DOC_STYLE_VALUES# — Editioning companion object referenced by this table in 12.2.
  • FND_USER — Joined on CREATED_BY or LAST_UPDATED_BY = FND_USER.USER_ID for audit reporting.
  • FND_LOGINS — Joined on LAST_UPDATE_LOGIN = FND_LOGINS.LOGIN_ID for session-level auditing.
  • PO_LINE_TYPES, PO_PAY_ITEM_TYPES, PO_PURCHASE_BASES — Reference/validation sources for the coded values stored in STYLE_ALLOWED_VALUE.
  • PO_DOCUMENT_TYPES — Related configuration object affected by document style settings during document creation.

Collectively these relationships position PO_DOC_STYLE_VALUES as the value-level detail of purchasing document style configuration, bridging the style header and the operational values buyers may select.