Results for “okl_tal_tcl_map_t”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKL_TAL_TCL_MAP_T is a table within the OKL schema, belonging to the Oracle Leasing and Finance Management (OKL) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. The documented purpose of this object is to support the migration of Asset Disposition transactions. In practical terms, it functions as a mapping or cross-reference table that links two distinct transaction identities — a TAL (transaction accounting layer) identifier and a TCL (transaction control layer) identifier — so that legacy or external disposition records can be aligned with the internal transaction structures used by OKL processing.

The table is physically narrow, containing only two documented columns, and is anchored by the primary key constraint OKL_TAL_TCL_MAP_T_PK on the TAL_ID column. A unique index, OKL_TAL_TCL_MAP_T_U1, also exists on TAL_ID, confirming it as the principal business-key candidate. Based on a heuristic Data Vault classification mined from the foreign key structure, this object is modeled as a standalone entity. That is a modeling suggestion: it is not currently participating as a hub, link, or satellite within a documented Data Vault design, but it can reasonably be treated as an independent reference or bridge table within an analytic or migration framework.

Key Information Stored

The documented physical schema for ETRM 12.2.2 lists exactly two columns, both of which are significant:

• TAL_ID — The surrogate primary key of the table, enforced by OKL_TAL_TCL_MAP_T_PK and additionally protected by the unique index OKL_TAL_TCL_MAP_T_U1. It also serves as the business-key candidate, since the unique index provides the alternate means of enforcing uniqueness. This column identifies the TAL-side transaction record involved in the disposition migration.
• TCL_ID — The correlated TCL-side identifier, completing the mapping pair. It associates the TAL record with its corresponding transaction control layer entry.

Because the metadata documents only these two attributes, no additional descriptive columns (such as dates, status codes, or user audit fields) can be confirmed. Any wider interpretation should be verified directly against the deployed schema in the target environment. The essential point is that the table carries only the relationship between TAL and TCL identities; it stores no payload beyond the mapping itself.

Common Use Cases and Queries

The principal use case is reconciliation during the migration of Asset Disposition transactions. Organizations converting legacy disposition data commonly need to confirm that every migrated TAL record maps to a valid TCL record, and that no orphaned or duplicated mappings exist. Because TAL_ID is unique, any attempt to insert a duplicate mapping will fail at the constraint level, which makes the table self-protecting against double registration.

A representative validity check would join the mapping table back to the item instance table that consumes it:

• SELECT m.TAL_ID, m.TCL_ID FROM okl.okl_tal_tcl_map_t m ORDER BY m.TAL_ID; — a full listing of the mapping pairs.
• SELECT i.TAL_ID FROM okl.okl_txl_itm_insts i WHERE NOT EXISTS (SELECT 1 FROM okl.okl_tal_tcl_map_t m WHERE m.TAL_ID = i.TAL_ID); — identifies item instances lacking a corresponding mapping entry.

Reporting scenarios include migration audit summaries counting total mapped records and duplicate-detection queries grouped by TAL_ID or TCL_ID. These results are typically used as pre-cutover validation evidence.

Related Objects

The most significant dependent object is the item instance table that references this mapping:

• OKL_TXL_ITM_INSTS — references OKL_TAL_TCL_MAP_T through OKL_TXL_ITM_INSTS.TAL_ID, joining on TAL_ID. This foreign key relationship makes OKL_TXL_ITM_INSTS the primary consumer of the mapping data.
• OKL_TAL_TCL_MAP_T_PK and OKL_TAL_TCL_MAP_T_U1 — the primary key constraint and unique index that define and protect TAL_ID.

Given the limited documented relationships, additional OKL transaction-layer tables (TAL- and TCL-prefixed objects) are likely related in practice but are not confirmed by the ETRM metadata. Where further dependencies are required, they should be established by inspecting the deployed foreign key definitions in the OKL schema.