Results for “oe_pricing_entities_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The OE_PRICING_ENTITIES_V view is an Oracle E-Business Suite database object owned by the APPS schema and associated with the QP (Advanced Pricing) product family. In both EBS 12.1.1 and 12.2.2, this view carries a documented status of Obsolete. It was historically used by the Order Management and Advanced Pricing modules to identify the subset of Oracle database columns that are eligible to participate in pricing rules, and to expose the translatable, user-facing labels associated with those columns. The view joins object attribute metadata (from the AK object attribute dictionary) with a pricing-specific extension table that flags each attribute as pricing-enabled. The result is a denormalized list of pricing entities, each identified by an entity ID and entity code, with a friendly attribute label supplied by the multilingual attribute label table. Because it is obsolete, the view should not be used as the foundation for new development, but it may still appear in legacy customizations, older reports, and patch-level dependencies that predate its deprecation. The specific reference to ATTRIBUTE_LABEL_LONG in the view definition explains why users searching for that term encounter this object: the label column is sourced from AK_OBJECT_ATTRIBUTES_TL.ATTRIBUTE_LABEL_LONG.

Underlying Base Objects

Per the ETRM metadata, the view is defined over three base objects, each accesssible to APPS through synonyms:

• AK_OBJECT_ATTRIBUTES — the base attribute dictionary table, supplying the physical table name, column name, attribute application ID, and attribute code for each registered attribute.
• AK_OBJECT_ATTRIBUTES_TL — the translation table for attribute metadata, providing the language-dependent ATTRIBUTE_LABEL_LONG value.
• OE_AK_OBJ_ATTR_EXT — the Order Management extension table that stores the PRICING_RULE_ENABLED_FLAG, indicating whether an attribute can be referenced in pricing rules.

The join is driven by matching attribute application ID, attribute code, and database object name across all three sources, with a language filter using USERENV('LANG'), and a restriction that the pricing-rule-enabled flag equals 'Y'.

Key Columns

• ENTITY_ID — aliased from ATTRIBUTE_ID; the unique identifier of the pricing entity.
• ENTITY_CODE — aliased from ATTRIBUTE_CODE; the internal code for the entity.
• COLUMN_TYPE_CODE — the data type classification of the underlying column.
• ENABLED_FLAG — aliased from PRICING_RULE_ENABLED_FLAG; always 'Y' when returned by this view.
• TABLE_NAME and COLUMN_NAME — the physical database table and column to which the entity maps.
• NAME — aliased from ATTRIBUTE_LABEL_LONG; the translated, displayable label for the entity in the session language.

Common Use Cases and Queries

Typical legacy usage involves listing pricing-enabled attributes and their labels for configuration, auditing, or reporting. A representative query is:

SELECT entity_id, entity_code, table_name, column_name, name
FROM apps.oe_pricing_entities_v
WHERE table_name = 'OE_ORDER_LINES_ALL';

Because results are filtered by the session language, the NAME column reflects the label for the connected user's language. Given the obsolete status, consumers should migrate to the currently supported pricing attribute views or the underlying AK tables directly, and verify any dependency before relying on this view in a 12.2.2 environment.