Results for “tad_id”
14 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
OKL_XLA_EVE_TAD_MAP_T is a Subledger Accounting (SLA) migration support table owned by the OKL schema, which underpins the Oracle Leasing and Finance Management module. In Oracle EBS 12.1.1 and 12.2.2, the OKL product migrated from its legacy accounting engine to the Subledger Accounting (XLA) framework. The "TAD" designation refers to Transaction Account Definition, the mapping construct that links a business transaction to the accounting event and journal line definitions used by SLA. This table preserves the mapping between a transaction account definition and its associated accounting event identifier during that data migration (SLA Uptake).
From a data modeling perspective, the metadata classifies this object heuristically as a standalone structure. In Data Vault terms it behaves less like a full hub / link / satellite constellation and more like a small reference mapping table: it carries a surrogate primary key and a single foreign-key-like attribute, so it functions as a lightweight lookup rather than a richly normalized hub or satellite.
Key Information Stored
The table is physically compact, with only two documented columns in the 12.2.2 schema. The most important elements are:
- TAD_ID — the Transaction Account Definition identifier. This is the surrogate primary key of the table (constraint OKL_XLA_EVE_TAD_MAP_T_PK) and is also a business-key candidate, as it is carried by the unique index OKL_XLA_EVE_TAD_MAP_T_U1. Uniqueness on TAD_ID confirms that each transaction account definition resolves to exactly one mapping row.
- EVENT_ID — the accounting event identifier associated with the transaction account definition. This attribute ties the mapping to the SLA event model and is the substantive value of the row, enabling the migration process to correlate TAD records with their corresponding event entries.
Although the table exposes only these two columns, the pairing of a keyed TAD reference with an EVENT reference means the object acts as a bridge during the uptake of legacy leasing transactions into the XLA schema.
Common Use Cases and Queries
Because this is a migration-support object, its primary consumption is during and immediately after the SLA Uptake phase for leasing and finance transactions. Typical usage includes validating that every transaction account definition has been assigned an accounting event, reconciling migrated journal entries, and diagnosing missing or duplicate event assignments. A representative query joining the mapping to the global temporary table used by the migration is:
- SELECT m.tad_id, m.event_id, g.* FROM okl.okl_xla_eve_tad_map_t m JOIN okl.okl_xla_acc_data_gt g ON g.tad_id = m.tad_id;
- Detecting orphaned definitions: SELECT tad_id FROM okl.okl_xla_eve_tad_map_t WHERE event_id IS NULL;
- Duplicate protection checks rely on the unique index: SELECT tad_id, COUNT(*) FROM okl.okl_xla_eve_tad_map_t GROUP BY tad_id HAVING COUNT(*) > 1;
Reporting use cases center on migration audit trails, confirming coverage of TAD-to-event mapping, and supporting post-migration SLA reconciliation extracts. Because the table is small, queries are inexpensive and are usually combined with the staging/global temporary tables that drive the uptake.
Related Objects
The documented foreign-key relationship defines the most significant dependency. The following objects are relevant:
- OKL_XLA_ACC_DATA_GT — the migration staging table; its TAD_ID column references OKL_XLA_EVE_TAD_MAP_T.TAD_ID. This is the principal consumer of the mapping.
- OKL_XLA_EVE_TAD_MAP_T_PK — the primary key constraint on TAD_ID, enforcing uniqueness of the mapping key.
- OKL_XLA_EVE_TAD_MAP_T_U1 — the unique index on TAD_ID, confirming TAD_ID as a business-key candidate.
- The broader OKL SLA uptake objects (event and account data entities in the XLA schema) that receive the migrated mappings and complete the accounting-event-to-journal-line chain.
Together these objects show that OKL_XLA_EVE_TAD_MAP_T is a narrow but essential bridge in the Leasing and Finance Management SLA Uptake migration path.
-
This table as part of data migration for SLA Uptake
-
This table as part of data migration for SLA Uptake
-
eTRM - OKL Tables and Views 12.2.2
Translatable columns from OKL_XTL_SELL_INVS_B, per MLS standards
-
eTRM - OKL Tables and Views 12.1.1
Translatable columns from OKL_XTL_SELL_INVS_B, per MLS standards
-
eTRM - OKL Tables and Views 12.2.2
Translatable columns from OKL_XTL_SELL_INVS_B, per MLS standards
-
eTRM - OKL Tables and Views 12.1.1
Translatable columns from OKL_XTL_SELL_INVS_B, per MLS standards