Search Results xle_le_sob_interface_u2




Overview
Explore in AI Chat

Overview

XLE.XLE_LE_SOB_INTERFACE is a table in the XLE (Legal Entity) application schema of Oracle E-Business Suite. Its name indicates its historical purpose: an interface between legal entities and sets of books, mapping each legal entity to the set of books against which its accounting was recorded. The ETRM metadata records this table with a status of VALID, but the documentation explicitly states that "this table is no longer used." It is therefore best treated as a legacy, dormant object that survives in the 12.1.1 and 12.2.2 data dictionary for backward compatibility rather than as an active transactional component of the Subledger Accounting architecture.

The table is owned by XLE and resides in the APPS_TS_TX_DATA tablespace, with a PCT Free of 10. It has no foreign keys defined within the table itself apart from a documented reference from LEGAL_ENTITY_ID to FV_LEGAL_ENTITIES, and the ETRM relationship data classifies it as standalone under the heuristic Data Vault classification. In Data Vault modeling terms, the combination of a legal entity and a set of books in a single row suggests a link-style structure connecting two business concepts, though the classification should be regarded as a modeling suggestion only, since the object is defunct.

Key Information Stored

The table contains nine documented columns. The most significant are:

  • LE_SOB_ID — A NUMBER(15) surrogate identifier for the legal entity / set of books association. It is the single-column business-key candidate enforced by the unique index XLE_LE_SOB_INTERFACE_U1.
  • LEGAL_ENTITY_ID — A NUMBER(15) reference to the legal entity, pointing to FV_LEGAL_ENTITIES.
  • SET_OF_BOOKS_ID — A NUMBER(15) identifier of the set of books linked to that legal entity.

Together, LEGAL_ENTITY_ID and SET_OF_BOOKS_ID form the second unique business-key candidate, enforced by XLE_LE_SOB_INTERFACE_U2, which guarantees that a given legal entity may be associated with a given set of books only once. The remaining columns are standard EBS audit and concurrency attributes: LAST_UPDATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE, CREATED_BY, and OBJECT_VERSION_NUMBER. These follow the conventional WHO-column pattern and support row-level auditing and optimistic locking. No descriptive or effective-dating columns are present, consistent with a simple mapping table.

Common Use Cases and Queries

Because the table is documented as no longer used, its practical role is limited to historical migration, upgrade validation, and troubleshooting of legacy data. Typical scenarios include verifying whether a legal entity was ever associated with a set of books before a 12.1.1 or 12.2.2 upgrade, and reconciling legacy mappings against the current Subledger Accounting configuration. A basic query follows the documented query text:

  • SELECT LE_SOB_ID, LEGAL_ENTITY_ID, SET_OF_BOOKS_ID FROM XLE.XLE_LE_SOB_INTERFACE;
  • To find all sets of books for one legal entity: SELECT SET_OF_BOOKS_ID FROM XLE.XLE_LE_SOB_INTERFACE WHERE LEGAL_ENTITY_ID = :entity_id;
  • To check uniqueness consistency between the two business keys, join the table to FV_LEGAL_ENTITIES on LEGAL_ENTITY_ID.

For any current reporting requirement, this table should not be used as a source; the active legal entity and ledger configuration tables should be substituted.

Related Objects

The documented dependency data shows the table references FV_LEGAL_ENTITIES through LEGAL_ENTITY_ID. The ETRM metadata also records that XLE.XLE_LE_SOB_INTERFACE is referenced by XLE.XLE_LE_SOB_INTERFACE#, an internal index-organized companion object. Other significant objects in the same functional area include FND_SET_OF_BOOKS (the definition of the set of books identified by SET_OF_BOOKS_ID), XLE_ENTITY_PROFILES (legal entity definitions aligned with FV_LEGAL_ENTITIES), and the Subledger Accounting application programming interfaces that superseded this mapping mechanism. Because the object is dormant, joins should be treated as legacy inspection only and not embedded in production logic.