Search Results po_style_enabled_pay_items




Overview
Explore in AI Chat

Overview

PO_STYLE_ENABLED_PAY_ITEMS is a VALID database view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It resides within the Oracle Purchasing (PO) product family. The view exposes the set of pay item types that are permitted for use against a given Purchasing document style. In other words, it answers the question: for a specific document style, which pay item types are enabled? This mapping is a configuration-level relationship managed through Oracle Purchasing document style setup, and the view presents only the positive (enabled) associations.

Because it is a view rather than a base table, PO_STYLE_ENABLED_PAY_ITEMS does not physically store data; it derives its rows at runtime from the document style value table. Its role in EBS reporting and integration is to provide a clean, filtered, two-column result set that can be joined to document style headers, purchasing documents, or pay item definitions without the caller needing to know the internal filtering logic (ENABLED_FLAG = 'Y' and STYLE_ATTRIBUTE_NAME = 'PAY_ITEM_TYPES').

Underlying Base Objects

According to the documented ETRM metadata, the view is defined over a single referenced base object: PO_DOC_STYLE_VALUES, accessed through a synonym. PO_DOC_STYLE_VALUES is the repository that holds attribute-level values for each Purchasing document style, keyed by style and attribute name. The view text applies two predicates to this table:

  • ENABLED_FLAG = 'Y' — restricts rows to enabled attribute values.
  • STYLE_ATTRIBUTE_NAME = 'PAY_ITEM_TYPES' — restricts rows to the pay item types attribute of the document style.

The SELECT list aliases the column STYLE_ALLOWED_VALUE to PAY_ITEM_TYPE and passes STYLE_ID through directly. Consequently, the view is a projection and filter of PO_DOC_STYLE_VALUES and inherits its dependency on that table. Any change to a document style's enabled pay item types in the base table is immediately reflected in the view.

Key Columns

The documented column list for the view comprises two columns:

  • PAY_ITEM_TYPE — Derived from STYLE_ALLOWED_VALUE in PO_DOC_STYLE_VALUES. Identifies the pay item type that is allowed for the document style. This is the value joined against pay item type lookups or pay item definitions.
  • STYLE_ID — The unique identifier of the Purchasing document style to which the pay item type is associated. This is the foreign key linking back to the document style definition (for example, PO_DOC_STYLES via STYLE_ID).

The pair (STYLE_ID, PAY_ITEM_TYPE) effectively forms the logical key of the view, since duplicate enabled rows for the same style and pay item type are not meaningful.

Common Use Cases and Queries

The view is commonly used when validating or reporting which pay item types a user may select given the document style applied to a purchasing document, and when building configuration or audit reports of document style setup. Because it is pre-filtered, it removes the need to replicate the ENABLED_FLAG and STYLE_ATTRIBUTE_NAME logic in custom SQL.

A straightforward query lists all enabled pay item types for every style:

  • SELECT style_id, pay_item_type FROM apps.po_style_enabled_pay_items ORDER BY style_id, pay_item_type;

A filtered query retrieves the enabled pay item types for one style:

  • SELECT pay_item_type FROM apps.po_style_enabled_pay_items WHERE style_id = :p_style_id;

The view can also be joined to the document style header to present descriptive style names alongside the enabled pay items, and to pay item tables to validate that a selected pay item type is permissible for the style in force on a document. This makes it suitable for validation logic in custom forms, concurrent programs, and integration extracts where document style governs allowable pay item entry.