Results for “pv_entity_attrs_v”

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

Overview

PV_ENTITY_ATTRS_V is an Oracle E-Business Suite view owned by the APPS schema and registered as a VALID database object. It belongs to the PV – Partner Management product family, the module historically associated with partner, channel, and entity relationship configuration. The view exposes the full column set of the PV_ENTITY_ATTRS table and is used to present the definition of entity attributes that drive dynamic, attribute-based behavior within Partner Management and its dependent Oracle applications.

The defining characteristic of this view is the SQL_TEXT column, which is the term most frequently searched in connection with it. SQL_TEXT stores the SQL fragment or query string associated with a given entity attribute. In practice, this column supplies the runtime SQL used to resolve a list of values, derive a selection set, or populate a dynamic attribute for an entity. Because the view is a straight projection over the base table, it preserves SQL_TEXT verbatim and is therefore the object of choice for developers and DBAs who need to inspect how a particular entity attribute is resolved.

From a reporting and integration standpoint, the view is read-only in intent. It is safe for ad hoc query, Oracle Reports, OAF-based lookups, and outbound integration extracts, and it carries the standard EBS audit columns together with an OBJECT_VERSION_NUMBER column that supports optimistic locking conventions.

Underlying Base Objects

The documented base object is PV_ENTITY_ATTRS, accessed through a SYNONYM. The view text is a simple SELECT of the table's columns with no joins, filters, or aggregation:

• Referenced base object: PV_ENTITY_ATTRS (via SYNONYM).
• View definition: a direct column-list projection over the base table.
• Because there are no joins or WHERE clauses, the view returns one row per base-table row and performs no row-level security filtering of its own.

The practical implication is that PV_ENTITY_ATTRS_V and PV_ENTITY_ATTRS are effectively interchangeable for query purposes. The view exists to provide a stable, APPS-owned interface over the entity attribute configuration data, shielding callers from direct table access while preserving the full attribute definition, including the SQL_TEXT payload that drives dynamic behavior.

Key Columns

• ENTITY_ATTR_ID – Primary identifier for the entity attribute definition.
• ATTRIBUTE_ID – Identifier of the attribute referenced by the definition.
• ENTITY / ENTITY_TYPE – The entity (and its type) to which the attribute applies.
• SQL_TEXT – The SQL text associated with the attribute, used to resolve values, lists of values, or selection logic at runtime. This is the column most often queried.
• ATTR_DATA_TYPE – Data type of the attribute, governing how the resolved value is interpreted.
• LOV_STRING – List-of-values definition string associated with the attribute.
• ENABLED_FLAG, DISPLAY_FLAG, LOCATOR_FLAG – Status and presentation flags controlling whether the attribute is active, displayed, or locator-enabled.
• ITEM_STYLE, SELECTION_TYPE – UI item style and selection semantics for the attribute.
• Audit columns – LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER.

Common Use Cases and Queries

Typical scenarios include auditing the SQL behind dynamic attributes, troubleshooting value-resolution failures, and extracting attribute configuration for migration or documentation.

Locating the SQL text for a specific entity attribute:

SELECT entity_attr_id, entity, attribute_id, sql_text
FROM   apps.pv_entity_attrs_v
WHERE  entity = :entity
AND    enabled_flag = 'Y';

Listing all enabled attributes with their presentation settings:

SELECT entity, attribute_id, attr_data_type, item_style,
       selection_type, display_flag, lov_string
FROM   apps.pv_entity_attrs_v
WHERE  enabled_flag = 'Y'
ORDER BY entity, attribute_id;

Searching for attributes whose SQL references a particular table or object:

SELECT entity_attr_id, entity, attribute_id, sql_text
FROM   apps.pv_entity_attrs_v
WHERE  UPPER(sql_text) LIKE '%' || UPPER(:object_name) || '%';

Reviewing recent changes to attribute definitions for audit purposes:

SELECT entity_attr_id, entity, attribute_id, last_update_date, last_updated_by
FROM   apps.pv_entity_attrs_v
WHERE  last_update_date >= TRUNC(SYSDATE) - 30
ORDER BY last_update_date DESC;

Because the view is a direct projection of PV_ENTITY_ATTRS, these queries benefit from any indexes defined on the base table, and results can be joined to other PV configuration views using ENTITY_ATTR_ID or ATTRIBUTE_ID as the correlation key.