Results for “xle_associations”

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

Overview

XLE.XLE_ASSOCIATIONS is a core table within the Oracle E-Business Suite Legal Entity Configurator (XLE) module. It stores legal associations established between legal entities and other entities or reference subjects across the EBS data model. The table functions as the central repository for relationship records that govern how legal entities interact with one another, with operating units, and with external or internal subjects. In EBS 12.1.1 and 12.2.2, this table underpins the Legal Entity Configurator's ability to model hierarchical, temporal, and typed relationships between business entities.

Each row represents a single association between a subject and an object, qualified by an association type and bounded by an effective date range. The design supports auditing, versioning, and multi-context extensions through the ASSOCIATION_ID surrogate key and the flexfield-style ASSOC_INFORMATION_CONTEXT / ASSOC_INFORMATION1–20 attribute columns. The metadata classifies this object heuristically as standalone in Data Vault terms. In practice, it behaves like a link table: it connects a subject (via SUBJECT_ID, with optional SUBJECT_PARENT_ID) to an object (via OBJECT_ID), qualified by ASSOCIATION_TYPE_ID and temporal bounds. Analysts may alternatively model it as a link, though the absence of a native parent hub within XLE limits that interpretation.

Key Information Stored

The table contains 34 columns, of which the following are the most significant for functional and reporting purposes:

• ASSOCIATION_ID — surrogate primary key, uniquely identifying each association row (unique index XLE_ASSOCIATIONS_U1).
• ASSOCIATION_TYPE_ID — foreign reference to the association type defining the nature of the relationship.
• SUBJECT_ID — the entity acting as the source of the association; documented FK targets IGS_UC_COM_EBL_SUBJ.
• SUBJECT_PARENT_ID — parent subject, enabling hierarchical or nested associations.
• OBJECT_ID — the target entity of the association.
• EFFECTIVE_FROM / EFFECTIVE_TO — date-bounded validity of the association.
• OBJECT_VERSION_NUMBER — optimistic locking value used by the OAF/Forms layer.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.
• ASSOC_INFORMATION_CONTEXT and ASSOC_INFORMATION1–20 — descriptive flexfield segments for extensible attributes.

The business key is captured by unique index XLE_ASSOCIATIONS_U2 over (ASSOCIATION_TYPE_ID, SUBJECT_ID, OBJECT_ID, EFFECTIVE_FROM), meaning no two identical typed associations between the same subject and object may begin on the same date. This uniqueness rule is critical when inserting or merging association records.

Common Use Cases and Queries

Typical scenarios include resolving which legal entities are associated with a given subject, auditing association history over time, and reporting on hierarchical relationships. A representative query lists all currently active associations for a subject:

• SELECT a.association_id, a.association_type_id, a.subject_id, a.object_id, a.effective_from, a.effective_to FROM xle.xle_associations a WHERE a.subject_id = :subject_id AND TRUNC(SYSDATE) BETWEEN a.effective_from AND NVL(a.effective_to, SYSDATE);
• Date-range reports join the table against association type lookups to produce human-readable labels.
• Reconciliation queries test for duplicate business keys using the XLE_ASSOCIATIONS_U2 columns.
• Extensibility reports query ASSOC_INFORMATION_CONTEXT and the numbered segments when custom attributes are populated.

Because OBJECT_ID and SUBJECT_ID are generic references, joins must be directed to the appropriate subject or object table depending on ASSOCIATION_TYPE_ID.

Related Objects

• IGS_UC_COM_EBL_SUBJ — referenced by XLE_ASSOCIATIONS.SUBJECT_ID; provides subject canonical data.
• XLE_ASSOCIATION_TYPES (or equivalent lookup) — supplies ASSOCIATION_TYPE_ID meaning.
• XLE_ENTITY_PROFILES — the customary source of legal entity records participating as subjects or objects.
• XLE_ETB_PROFILES — establishing-business profiles frequently referenced via object identifiers.
• HR_OPERATING_UNITS — operating units associated to legal entities through these rows.
• Legal Entity Configurator OAF pages and XLE_ASSOCIATIONS_PKG PL/SQL APIs — responsible for controlled inserts, updates, and effective-date validation.

Together these objects form the relationship fabric underpinning legal entity reporting, intercompany setup, and regulatory compliance in Oracle EBS.