Search Results xle_assoc_object_types_u2

Overview

The table XLE.XLE_ASSOC_OBJECT_TYPES is a foundational configuration repository within the Oracle E-Business Suite (EBS) Subledger Accounting and ETRM (Enterprise Tax and Regulatory Management) module. Owned by the XLE schema, it stores the catalog of object types that participate in legal associations. In the context of Oracle EBS 12.1.1 and 12.2.2, this table defines the metadata required to identify, resolve, and link instances of various business entities — such as legal entities, trading partners, or regulatory documents — that are eligible for association rules processing.

From a Data Vault modeling perspective, the heuristic classification returned by Foreign Key mining is standalone, meaning the table does not reference any downstream database object through foreign key constraints. It functions as a reference or lookup hub that enumerates the canonical set of object types, while the associated instances and their relationships are resolved dynamically through the SOURCE_TABLE, SOURCE_COLUMN1, SOURCE_COLUMN2, and WHERE_CLAUSE columns rather than declared foreign keys.

Key Information Stored

The table contains twelve columns, with the following being most significant:

• OBJECT_TYPE_ID (NUMBER 15) — The surrogate primary key uniquely identifying each object type. It is the leading column of the unique index XLE_ASSOC_OBJECT_TYPES_U1.
• NAME (VARCHAR2 80) — The business-facing name of the object type. This is a business-key candidate and is the leading column of the unique index XLE_ASSOC_OBJECT_TYPES_U2.
• SOURCE_TABLE (VARCHAR2 40) — Identifies the physical table where instances of the object type are persisted.
• WHERE_CLAUSE (VARCHAR2 500) — Provides a supplemental predicate that restricts which records within the source table qualify as instances of the object type.
• SOURCE_COLUMN1 (VARCHAR2 30) — The primary column used to uniquely identify a record in the source table.
• SOURCE_COLUMN2 (VARCHAR2 30) — A secondary column that, combined with SOURCE_COLUMN1, completes the unique identification of a source record.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard "Who" audit columns tracking row creation and modification.
• ZD_EDITION_NAME (VARCHAR2 30) — The edition name supporting Oracle's Edition-Based Redefinition (EBR) feature, included as an additional column in both unique indexes to enforce uniqueness per edition.

The query the user searched for, xle_assoc_object_types_u2, refers specifically to the unique index on the NAME column (plus ZD_EDITION_NAME), confirming that object type names are unique within an edition.

Common Use Cases and Queries

Typical usage includes resolving object type metadata during legal association rule evaluation and building dynamic SQL against generic source tables. A standard lookup query follows:

SELECT object_type_id, name, source_table, where_clause, source_column1, source_column2
FROM xle.xle_assoc_object_types
WHERE name = :p_object_type_name;

Reporting use cases include auditing which object types are configured, validating source table and column mappings, and reconciling edition-specific configurations in 12.2.2 environments where EBR is active. Because object resolution is metadata-driven, administrators often review WHERE_CLAUSE entries to ensure correct filtering of source records.

Related Objects

The most significant dependency is the foreign key relationship from OBJECT_TYPE_ID to JTF_PERZ_LF_OBJECT_TYPE, linking the XLE object type catalog to the CRM personalization object type definitions. This table is also referenced by its editioned counterpart XLE.XLE_ASSOC_OBJECT_TYPES#, which holds the underlying EBR-enabled data block. Additional objects that consume or transitively depend on this metadata include the XLE legal association rule tables, the Subledger Accounting event and journal line definition objects, and the Trading Community (JTF) object resolution APIs that interpret SOURCE_TABLE and SOURCE_COLUMN1/2 to instantiate object references at runtime.