Search Results xle_assoc_object_types




Overview
Explore in AI Chat

Overview

XLE_ASSOC_OBJECT_TYPES is a configuration table owned by the XLE schema (Legal Entity Configurator) in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the catalog of object types that participate in Legal Associations within the Legal Entity Configurator (LEC) framework. Legal Associations define relationships between a legal entity and other entities or external objects, and this table determines which underlying source objects (and their columns) are eligible for those associations. Each row represents one association object type, describing the physical source table, an optional restricting WHERE clause, and up to two source columns used to resolve association members at runtime.

From a Data Vault modeling perspective, the heuristic classification for this table is standalone. It does not behave as a classic hub, link, or satellite driven by the surrounding foreign key web; instead it functions as a small reference/seed table that enumerates valid object types. Modeling it as a reference lookup dimension, rather than a hub, is the practical suggestion.

Key Information Stored

  • OBJECT_TYPE_ID — Surrogate primary key identifying each association object type; also a foreign key to JTF_PERZ_LF_OBJECT_TYPE.OBJECT_TYPE_ID (per documented relationship data, this is the only outgoing FK).
  • NAME — Business-facing name of the object type, used to display and select the object type in the Legal Association setup UI.
  • SOURCE_TABLE — The physical database table from which association members are drawn for this object type.
  • WHERE_CLAUSE — Optional filter applied against SOURCE_TABLE to restrict which rows qualify as valid association targets.
  • SOURCE_COLUMN1 and SOURCE_COLUMN2 — The identifying columns in SOURCE_TABLE used to resolve the entity or object instance being associated.
  • ZD_EDITION_NAME — Editioning column enabling Edition-Based Redefinition (EBR). It participates in both unique keys and is essential for online patching in 12.2.x.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle audit columns tracking who created and last modified each object type row.

Two unique indexes act as business-key candidates: XLE_ASSOC_OBJECT_TYPES_U1 (OBJECT_TYPE_ID, ZD_EDITION_NAME) enforces uniqueness of the surrogate key within an edition, while XLE_ASSOC_OBJECT_TYPES_U2 (NAME, ZD_EDITION_NAME) enforces uniqueness of the object type name within an edition. Note that OBJECT_TYPE_ID is both the surrogate key and a foreign key reference in the documented schema.

Common Use Cases and Queries

This table is primarily queried during Legal Association setup, troubleshooting, and metadata reporting. Administrators inspect available object types before defining associations, and developers tracing how an association resolves its source rows inspect SOURCE_TABLE, WHERE_CLAUSE, and SOURCE_COLUMN1/2.

  • Listing all configured object types for the current edition: SELECT OBJECT_TYPE_ID, NAME, SOURCE_TABLE, SOURCE_COLUMN1, SOURCE_COLUMN2 FROM XLE.XLE_ASSOC_OBJECT_TYPES WHERE ZD_EDITION_NAME = 'ORA$BASE';
  • Resolving the underlying JTF object type details: SELECT a.NAME, j.OBJECT_TYPE FROM XLE.XLE_ASSOC_OBJECT_TYPES a, JTF.JTF_PERZ_LF_OBJECT_TYPE j WHERE a.OBJECT_TYPE_ID = j.OBJECT_TYPE_ID;
  • Identifying which source tables and filters drive a given association: filter on NAME and read SOURCE_TABLE and WHERE_CLAUSE to understand the runtime query.
  • Auditing recently modified configuration: order by LAST_UPDATE_DATE descending and join LAST_UPDATED_BY to FND_USER for user names.

Related Objects

The documented FK relationship anchors this table to the JTF object type catalog, while the broader LEC framework consumes these rows elsewhere in the XLE schema. Significant related objects include:

  • JTF_PERZ_LF_OBJECT_TYPE — Referenced via XLE_ASSOC_OBJECT_TYPES.OBJECT_TYPE_ID → JTF_PERZ_LF_OBJECT_TYPE.OBJECT_TYPE_ID; parent catalog of legal-foundation object types.
  • XLE_ASS OC_OBJECTS / XLE_ASSOC_OBJECT_USAGES — Instance-level and usage tables that record actual associations created using these object types.
  • XLE_ENTITY_PROFILES — Legal entity definitions whose associations rely on the object types cataloged here.
  • XLE_ASSOC_OBJECTS_MAP — Mapping metadata linking associations to entity records.
  • XLE_ASSOCIATIONS / XLE_ASSOC_TYPES — Association type configuration that consumes object type definitions.
  • FND_USER — Joined for audit attribution of CREATED_BY and LAST_UPDATED_BY.

Because the documented relationship data classifies this object as standalone, join paths are largely driven by application logic rather than a dense PK/FK web; the single documented FK to JTF_PERZ_LF_OBJECT_TYPE remains the most reliable structural reference point.