Search Results xle_le_interface_n2

Overview

XLE.XLE_LE_INTERFACE is a table in the XLE (Legal Entity) schema within Oracle E-Business Suite, documented in the ETRM reference for releases 12.1.1 and 12.2.2. Its name indicates that it was originally intended as a staging or interface table for the migration and maintenance of legal entity records — the "LE" prefix denotes Legal Entity, and "INTERFACE" denotes a data-loading or integration surface rather than a transactional base table.

The ETRM documentation for this object carries an explicit and important caveat: "This table is no longer used." Despite the VALID status recorded against the object itself in the data dictionary, the table has been superseded by later functional designs and is retained only for historical, upgrade, or backward-compatibility purposes. Consultants should treat it as a legacy artifact — it may still be physically present in the APPS_TS_TX_DATA tablespace, but no current Oracle EBS process writes to or reads from it as part of standard legal entity processing.

With respect to modeling classification, the metadata's FK structure marks this object as standalone, with a single outgoing relationship to FV_LEGAL_ENTITIES on the LEGAL_ENTITY_ID column. This pattern is characteristic of a staging or hub-like structure rather than a dependent satellite or a many-to-many link table. Any Data Vault conversion should therefore treat XLE_LE_INTERFACE as a candidate historical hub for legal entity identifiers, with the various descriptive columns (NAME, REGISTRATION_NUMBER, LEGAL_ENTITY_IDENTIFIER) as potential satellite attributes.

Key Information Stored

The table is documented with 17 columns. The most significant are:

• LEGAL_ENTITY_ID (NUMBER(15)) — the unique identifier for the legal entity, and the sole column of the unique index XLE_LE_INTERFACE_U1. This is both the business-key candidate and the column carrying the foreign key relationship to FV_LEGAL_ENTITIES.
• PARTY_ID (NUMBER(15)) — the associated trading partner party identifier, linking the entity to the TCA party model.
• NAME (VARCHAR2(240)) — the legal entity name; covered by the non-unique index XLE_LE_INTERFACE_N1 for lookup performance.
• GEOGRAPHY_ID and LOCATION_ID (NUMBER(15) each) — references to the entity's location and geopolitical hierarchy.
• REGISTRATION_NUMBER (VARCHAR2(30)) — the entity's statutory registration or tax registration number; indexed by XLE_LE_INTERFACE_N2.
• LEGAL_ENTITY_IDENTIFIER (VARCHAR2(30)) — an alternate identifier for the entity, distinct from the registered number.
• SOURCE (VARCHAR2(30)) — identifies the origin system or process that supplied the row, typical of an interface table.
• REVIEWED_FLAG, MIGRATE_FLAG, DO_NOT_MIGRATE_ALLOWED — control flags used during migration cycles to indicate whether a row has been reviewed and whether it is eligible for migration.
• LAST_UPDATE_DATE, CREATION_DATE, LAST_UPDATED_BY, CREATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER — the standard Oracle EBS WHO columns providing audit and optimistic locking support.

Note that LEGAL_ENTITY_ID is the primary business-key candidate by unique index, not a system-generated surrogate. The table also stores a foreign key to FV_LEGAL_ENTITIES, making it dependent on that table for referential integrity.

Common Use Cases and Queries

Because the table is documented as no longer used, its practical value in current releases is largely historical. Typical scenarios include:

• Upgrade and migration archaeology — during an upgrade from 11i or 12.1.1 to 12.2.2, checking whether orphaned rows remain and whether cleanup scripts are required before the table is dropped or archived.
• Data lineage validation — tracing the SOURCE and MIGRATE_FLAG columns to confirm which legal entities were carried forward and which were flagged for exclusion.
• Reporting — a reconciliation report comparing XLE_LE_INTERFACE rows to FV_LEGAL_ENTITIES to identify entities that failed to migrate.

A representative query pattern is:

• SELECT LEGAL_ENTITY_ID, NAME, REGISTRATION_NUMBER, SOURCE FROM XLE.XLE_LE_INTERFACE WHERE MIGRATE_FLAG = 'N' OR DO_NOT_MIGRATE_ALLOWED IS NOT NULL;
• A join to the dependent entity table: SELECT i.LEGAL_ENTITY_ID, i.NAME, e.NAME FROM XLE.XLE_LE_INTERFACE i, FV_LEGAL_ENTITIES e WHERE i.LEGAL_ENTITY_ID = e.LEGAL_ENTITY_ID;
• Lookups by name or registration number benefit from the XLE_LE_INTERFACE_N1 and XLE_LE_INTERFACE_N2 indexes respectively.

Related Objects

The documented dependencies identify the following significant relationships:

• FV_LEGAL_ENTITIES — referenced by XLE_LE_INTERFACE through the LEGAL_ENTITY_ID foreign key. This is the primary join target and the current system of record for legal entities.
• XLE_LE_INTERFACE_U1 — the unique index on LEGAL_ENTITY_ID, enforcing the business-key constraint on the interface data.
• XLE_LE_INTERFACE_N1 — non-unique index on NAME, supporting name-based retrieval.
• XLE_LE_INTERFACE_N2 — non-unique index on REGISTRATION_NUMBER, supporting registration-number lookups.
• APPS.XLE_LE_INTERFACE — the APPS-side synonym or view granting access to the table's contents within the application schema.

No other database objects are documented as referencing this table, which is consistent with its designation as a legacy, superseded interface object. Any new development should target FV_LEGAL_ENTITIES and its related current-generation view and API layer rather than XLE_LE_INTERFACE.