Results for “assoc_obj”

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

Overview

APPS.XLE_ASSOCIATIONS_V is a reporting view in the Oracle E-Business Suite (EBS) Legal Entity Configurator / ETRM (Enterprise Tax, Risk, and Legal) module. It presents the associations that exist between "entities" (such as legal entities and operating units) and "legal constructs" (such as legal entities, establishments, and other registered constructs) within the legal entity model. The view flattens the relationships stored in the XLE_ASSOCIATIONS table together with their type definitions and the descriptive profile information of both sides of the relationship, so that consumers can read the association, the entity involved, the legal construct involved, and the party behind that construct in a single row.

The legal_construct_name column exposed by this view is the reason most users reach for it: it resolves the numeric subject_id of an association into a human-readable name, drawn from XLE_ENTITY_PROFILES.NAME or XLE_ETB_PROFILES.NAME depending on association type. The view is therefore a core source for legal entity hierarchy reports, tax registration reporting, and integrations that need to translate legal entity and establishment IDs into names.

Underlying Base Objects

The view is defined by a UNION of queries, each targeting a different subject/object combination, over the following documented base objects:

• XLE_ASSOCIATIONS — the transaction table holding each association record (entity_id, subject_id, subject_parent_id, effective dates).
• XLE_ASSOCIATION_TYPES — defines association type metadata linking object type and subject type.
• XLE_ASSOC_OBJECT_TYPES — provides the descriptive NAME of the entity type (e.g. 'LEGAL_ENTITY', 'OPERATING_UNIT') and the subject (legal construct) type.
• XLE_ENTITY_PROFILES — the legal entity / establishment profile table, supplying party_id and name.
• XLE_ETB_PROFILES — establishment profiles used in the operating unit branch.
• HR_ALL_ORGANIZATION_UNITS — source of the operating unit name when the entity is an operating unit.
• ORG_ORGANIZATION_DEFINITIONS — organization classification and definitions referenced for organization-side resolution.
• HR_LOCATIONS_ALL, FND_FLEX_VALUES — supporting location and flexfield value lookups.
• HR_GENERAL, HR_SECURITY — packages used to enforce organization-level security predicates.

The join path progresses from XLE_ASSOCIATIONS to XLE_ASSOCIATION_TYPES, then to two aliases of XLE_ASSOC_OBJECT_TYPES (one for the object/entity side, one for the subject/legal construct side), and finally out to the entity profile and organization tables. The documented filter on the first branch is assoc_obj.NAME = 'LEGAL_ENTITY'; the second branch restricts to 'OPERATING_UNIT'.

Key Columns

• CONTEXT — association type context identifier.
• ENTITY_TYPE — the name of the entity object type (e.g. LEGAL_ENTITY, OPERATING_UNIT).
• LEGAL_CONSTRUCT — the name of the subject object type associated with the entity.
• ASSOCIATION_TYPE_ID / ASSOCIATION_ID — identifiers for the type and the specific association instance.
• ENTITY_ID / ENTITY_NAME — the entity's numeric ID and resolved name.
• LEGAL_CONSTRUCT_ID — the subject's numeric identifier.
• LEGAL_PARTY_ID — the party_id behind the legal construct, from XLE_ENTITY_PROFILES or XLE_ETB_PROFILES.
• LEGAL_CONSTRUCT_NAME — the human-readable name of the legal construct, the column most commonly searched.
• LEGAL_PARENT_ID — the parent subject, allowing reconstruction of hierarchical relationships.
• EFFECTIVE_FROM / EFFECTIVE_TO — the date range during which the association is valid.

Common Use Cases and Queries

The view supports legal entity hierarchy validation, operating unit to legal entity mapping, and reporting that must display legal construct names instead of raw IDs. A typical query resolves the legal construct name for a given entity:

• SELECT entity_name, legal_construct_name, effective_from, effective_to FROM apps.xle_associations_v WHERE entity_name = :p_entity;
• SELECT legal_construct_id, legal_construct_name, legal_party_id FROM apps.xle_associations_v WHERE entity_type = 'OPERATING_UNIT';
• SELECT * FROM apps.xle_associations_v WHERE TRUNC(SYSDATE) BETWEEN effective_from AND NVL(effective_to, SYSDATE);

Because the view enforces association-type and organization-security joins, results are automatically restricted to valid, currently applicable associations, making it suitable for integration extracts that feed downstream tax and reporting systems.