Results for “xle_associations_v”

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

Overview

XLE_ASSOCIATIONS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the XLE – Legal Entity Configurator product. It presents the association records held in the XLE_ASSOCIATIONS table together with the descriptive context of the association types, object types, and legal constructs involved. In the Legal Entity Configurator data model, associations express relationships between a legal entity or operating unit (the object) and a legal construct such as a legal entity or establishment (the subject), bounded by an effective date range. The view flattens these relationships into a form suitable for inquiry screens, concurrent reporting, and downstream integration, exposing both the technical identifiers and the human-readable names of each participant.

Because the view unites association rows with entity profile and organization information, it removes the need for report authors to join the underlying configuration tables manually. It is therefore a convenient access point for questions such as which legal constructs are associated with a given legal entity or operating unit, when those associations became effective, and whether they have been superseded by a successor construct.

Underlying Base Objects

The view text is built from several documented base objects. XLE_ASSOCIATIONS supplies the association rows, including the object identifier, subject identifier, subject parent identifier, and effective date range. XLE_ASSOCIATION_TYPES provides the association type identifier and the context, while XLE_ASSOC_OBJECT_TYPES is referenced twice — once to resolve the object side and once to resolve the subject side — yielding the entity type and legal construct names. XLE_ENTITY_PROFILES resolves legal entity names and party identifiers, and XLE_ETB_PROFILES supplies the establishment name and party identifier for operating unit associations. HR_ALL_ORGANIZATION_UNITS supplies the organization name used when the object type is an operating unit, and ORG_ORGANIZATION_DEFINITIONS is also listed among the referenced objects. The documented metadata additionally lists FND_FLEX_VALUES, HR_LOCATIONS_ALL, and the HR_GENERAL and HR_SECURITY packages as dependencies, reflecting the view's participation in organization and value-set based security and lookup resolution.

Key Columns

• CONTEXT – the context value carried by the association type, distinguishing associations that share the same structural definition.
• ENTITY_TYPE – the object type name, resolved from XLE_ASSOC_OBJECT_TYPES; the view filters to 'LEGAL_ENTITY' and 'OPERATING_UNIT' in its respective branches.
• LEGAL_CONSTRUCT – the subject type name describing the legal construct side of the association.
• ASSOCIATION_TYPE_ID / ASSOCIATION_ID – identifiers of the association type definition and of the individual association row.
• ENTITY_ID / ENTITY_NAME – the object identifier and its resolved name (legal entity name or organization name).
• LEGAL_CONSTRUCT_ID / LEGAL_CONSTRUCT_NAME – the subject identifier and its resolved name, drawn from the entity profile or establishment profile.
• LEGAL_PARTY_ID – the party identifier of the legal construct.
• LEGAL_PARENT_ID – the parent of the legal construct, used to trace successor or hierarchical relationships.
• EFFECTIVE_FROM / EFFECTIVE_TO – the date range during which the association is effective.

Common Use Cases and Queries

Typical usage includes validating the associations configured for a legal entity before period-close, auditing changes to association effective dates, and feeding legal entity hierarchies into other applications. A simple listing by entity type and effective status can be produced as follows:

• SELECT entity_type, entity_name, legal_construct_name, effective_from, effective_to FROM xle_associations_v WHERE entity_name = :legal_entity ORDER BY effective_from;
• SELECT legal_construct_name, legal_parent_id, effective_from, effective_to FROM xle_associations_v WHERE entity_type = 'OPERATING_UNIT' AND legal_construct_name LIKE :pattern;
• SELECT association_type_id, context, entity_type, legal_construct, entity_name, legal_construct_name FROM xle_associations_v WHERE SYSDATE BETWEEN NVL(effective_from, SYSDATE) AND NVL(effective_to, SYSDATE);

The final query illustrates effective-dated filtering, which is the most common predicate applied when the view is used to determine the associations active on a given date.