Results for “ast_ptr_relation_attribs_v”

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

Overview

AST_PTR_RELATION_ATTRIBS_V is a TeleSales (AST) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents partner-related attribute values in a denormalized, presentation-ready form by joining a translated attribute definition table against an entity attribute value table. The view is filtered to include only rows where the attribute entity is 'PARTNER', and it restricts attribute name and description text to the language of the current session via USERENV('LANG').

Because attribute metadata in ETRM is stored in an entity-attribute-value (EAV) model, the raw storage is split between a definition table and a value table. This view collapses that model into a readable, four-column result set that is convenient for reporting, concurrent programs, OAF/Forms regions, and integration extracts. Note that the underlying value object is PV_ENTY_ATTR_VALUES, which matches the search term "pv_enty_attr_values" (the synonym name resolves the entity-attribute values table).

Underlying Base Objects

The documented view metadata identifies two referenced base objects, both exposed through APPS synonyms:

• PV_ATTRIBUTES_TL — the translated attribute definition table. It supplies the attribute name (NAME) and DESCRIPTION, and holds the ATTRIBUTE_ID and LANGUAGE columns used in the join and language filter.
• PV_ENTY_ATTR_VALUES — the entity attribute value table. It supplies ENTITY_ID (the partner identifier), ATTRIBUTE_ID, ATTR_VALUE, and the ENTITY discriminator column.

The view text joins on ATTRIBUTE_ID and constrains ATTR_VAL.ENTITY = 'PARTNER' plus ATTR.LANGUAGE = USERENV('LANG'). Only the current-session language row from the translated definition table is returned, so the view surfaces one language version of each attribute name and description.

Key Columns

The view projects the following columns. The ETRM column list names them PARTNER_ID, ATTRIBUTE, VALUE, and DESCRIPTION, while the underlying SELECT aliases them from ENTITY_ID, NAME, ATTR_VALUE, and DESCRIPTION respectively.

• PARTNER_ID — the partner entity identifier (ENTITY_ID from PV_ENTY_ATTR_VALUES).
• ATTRIBUTE — the attribute name from PV_ATTRIBUTES_TL (NAME), in the session language.
• VALUE — the stored attribute value (ATTR_VALUE) for the given partner and attribute.
• DESCRIPTION — the translated attribute description from PV_ATTRIBUTES_TL.

Common Use Cases and Queries

Typical uses include partner attribute reporting, validation of captured partner data, and feeding downstream integrations that require flat partner-attribute pairs. Because the view is already filtered to PARTNER and to the session language, it simplifies queries that would otherwise require explicit joins and language handling.

Sample: retrieve all attributes and values for a specific partner.

• SELECT partner_id, attribute, value, description FROM apps.ast_ptr_relation_attribs_v WHERE partner_id = :p_partner_id;

Sample: pivot-style lookup for a single attribute name.

• SELECT partner_id, value FROM apps.ast_ptr_relation_attribs_v WHERE attribute = 'MY_ATTRIBUTE';

Sample: list distinct attributes available for partners.

• SELECT DISTINCT attribute, description FROM apps.ast_ptr_relation_attribs_v ORDER BY attribute;

Access is subject to APPS schema privileges and MOAC/security in the calling context; the view itself does not include an org or security predicate, so row filtering should be applied by the consuming report or form.