Search Results okl_tax_sources_t




Overview
Explore in AI Chat

Overview

The OKL_TAX_SOURCES_T table is a core data object within the Oracle E-Business Suite (EBS) Lease and Finance Management (OKL) module. Its primary function is to serve as a transitional data repository during system upgrade processes. Specifically, it is designed to temporarily store detailed information about taxable lines from legacy data to ensure accurate and consistent tax calculations are maintained when migrating to a newer version of the application. This table is critical for preserving the integrity of financial and tax data during major upgrades, acting as a staging area before data is fully integrated into the standard transactional tables of the upgraded system.

Key Information Stored

The table's structure is defined by its extensive foreign key relationships, which point to the key entities involved in a taxable transaction. While the specific column list is not fully detailed in the provided metadata, the foreign keys reveal the critical data points stored. Each record likely represents a single taxable line and holds identifiers linking it to the core transaction components. The primary key is the ID column. Essential foreign key columns include KLE_ID (linking to the contract line in OKC_K_LINES_B), SEL_ID (linking to the stream element in OKL_STRM_ELEMENTS), and KHR_ID (linking to the contract header). For tax determination, it stores references to customer accounts and sites (BILL_TO_CUST_ACCT_ID, SHIP_TO_CUST_ACCT_SITE_USE_ID), party sites, the operating unit (ORG_ID), the transaction type (TRY_ID), and the stream type (STY_ID).

Common Use Cases and Queries

The principal use case for this table is during an EBS upgrade project for the OKL module. Data is populated into this table from the legacy system's taxable line data and is subsequently processed by upgrade scripts to populate the target tax-related tables in the new environment. Common queries are therefore predominantly administrative and related to the upgrade process. For example, an upgrade script might select records for a specific contract or operating unit to process them in batches. A sample validation query post-upgrade might check for data consistency:

  • SELECT COUNT(*), khr_id FROM okl_tax_sources_t WHERE org_id = 123 GROUP BY khr_id;

Post-upgrade, this table is typically purged or archived. It is not intended for day-to-day transactional reporting or operational processes in a production environment running on the upgraded version.

Related Objects

OKL_TAX_SOURCES_T has defined relationships with numerous fundamental EBS tables, as documented by its foreign keys. These relationships highlight its role as a central junction for upgrade data.