Search Results pay_item_type

Overview

APPS.PO_STYLE_ENABLED_PAY_ITEMS is a reporting view in Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2 that exposes the set of payment item types enabled for a given Purchasing document style. The view is a thin projection over the PO_DOC_STYLE_VALUES table, filtering that table's rows to the single style attribute named 'PAY_ITEM_TYPES' and to rows where the ENABLED_FLAG is 'Y'. It therefore answers the question: "which pay item types are available for use on documents governed by a particular document style?"

The view is not a standalone entity; it is a convenience access layer for document style configuration data. Its role in reporting and integration is to let concurrent programs, discoverer reports, and inbound interfaces retrieve the enabled pay item type values without needing to know the internal storage convention (attribute name, enabled flag, or allowed value column) used by PO_DOC_STYLE_VALUES. Searching for "pay_item_types" in the data dictionary typically leads developers to this view, since it is the clearest object exposing that attribute.

Underlying Base Objects

The view is defined over a single base object, PO_DOC_STYLE_VALUES, accessed through a synonym in the APPS schema. As documented in the ETRM metadata for 12.2.2, the only referenced base object is PO_DOC_STYLE_VALUES (SYNONYM).

PO_DOC_STYLE_VALUES stores the individual attribute/answer pairs that make up a document style. Each row associates a style (STYLE_ID) with an attribute name (STYLE_ATTRIBUTE_NAME) and a permitted value (STYLE_ALLOWED_VALUE), together with enablement state. Because the view filters on STYLE_ATTRIBUTE_NAME = 'PAY_ITEM_TYPES' and ENABLED_FLAG = 'Y', it returns one row per enabled pay item type per style. A style that permits multiple pay item types therefore yields multiple rows in this view.

Key Columns

• PAY_ITEM_TYPE — Derived from the underlying STYLE_ALLOWED_VALUE column. This is the pay item type value permitted by the owning document style (e.g., a goods, services, or other pay item category) and is the column of primary interest when searching for "pay_item_types".
• STYLE_ID — The surrogate identifier of the Purchasing document style to which the allowed value belongs. This is the join key back to the document style header (PO_DOC_STYLES.STYLE_ID) and to other style value rows for the same style. It also joins to any document created under that style.

No other columns are exposed. All filtering on attribute name and enablement is applied internally by the view definition, so consumers see only enabled pay item type entries.

Common Use Cases and Queries

Typical uses include validating whether a given pay item type is permitted for a style before entering a purchase order or release, driving LOV-style lookups in custom forms and OAF pages, and reconciling configuration across environments. The following query lists all enabled pay item types for a specific style:

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

To join the allowed values to the document style name for reporting:

• SELECT s.style_name, p.pay_item_type FROM apps.po_style_enabled_pay_items p, apps.po_doc_styles s WHERE p.style_id = s.style_id ORDER BY s.style_name, p.pay_item_type;

To determine whether a specific pay item type is enabled for a style:

• SELECT COUNT(*) FROM apps.po_style_enabled_pay_items WHERE style_id = :p_style_id AND pay_item_type = :p_pay_item_type;

Because the view is defined entirely over PO_DOC_STYLE_VALUES, its contents change whenever document style configuration is updated. Reports and interfaces should therefore query it at runtime rather than caching results.