Search Results po_doc_style_headers




Overview
Explore in AI Chat

Overview

PO_DOC_STYLE_HEADERS is a Purchasing (PO) module table in the Oracle E-Business Suite 12.1.1 and 12.2.2 schemas, owned by the PO schema. It stores the definition of document styles that an enterprise uses to govern procurement authoring behavior. A document style is a configurable template of rules and feature toggles that determines which purchasing features are available to a user when creating or modifying a purchasing document, including which line types may be entered, whether advanced pricing constructs such as price breaks or price differentials are permitted, and whether approval routing is driven by AME or by workflow. The table therefore acts as the master reference for procurement document policy in a given operating unit or business configuration.

The ETRM metadata classifies the object heuristically as a standalone Data Vault entity, since no foreign key relationships were mined from the schema. In Data Vault modeling terms, this object is best treated as a hub candidate rather than a link or satellite. The natural business key is STYLE_ID, which is also the primary key constraint PO_DOC_STYLE_HEADERS_PK. A secondary unique index, PO_DOC_STYLE_HEADERS_U1, spans STYLE_ID and ZD_EDITION_NAME, reflecting the Editioning feature introduced in 12.2 and indicating that the object is edition-aware in that release. The documented physical schema contains 40 columns.

Key Information Stored

The most operationally significant columns are described below. The surrogate primary key is STYLE_ID, which uniquely identifies each document style record. Business-key candidates are represented by the unique index PO_DOC_STYLE_HEADERS_U1 (STYLE_ID, ZD_EDITION_NAME).

Common Use Cases and Queries

Administrators and developers query this table to audit which features are enabled for a given style, to troubleshoot why a purchasing feature is unavailable to a user, and to reconcile approval routing configuration.

SELECT style_id, style_name, status, line_type_allowed
FROM   po.po_doc_style_headers
WHERE  status = 'ACTIVE';
SELECT style_name, wf_approval_itemtype, wf_approval_process, ame_transaction_type
FROM   po.po_doc_style_headers
WHERE  ame_transaction_type IS NOT NULL;

Reporting use cases include inventorying styles with contract financing or progress payment enabled, identifying styles using AME rather than workflow, and comparing feature flags across editions.

Related Objects