Search Results okl_tbo_pk

Overview

The OKL_TAX_BASIS_OVERRIDE table is a core data object within the Oracle E-Business Suite (EBS) Leasing and Finance Management (OKL) module. Its primary function is to manage tax basis overrides for specific transaction types within defined operating units. This table enables the system to apply a custom calculation formula for determining the tax basis of a transaction, deviating from any standard or default logic. This is a critical component for ensuring accurate tax calculations in complex leasing and financing arrangements, which may be governed by jurisdictional or contractual rules requiring specialized tax treatment. The table's design, linking transaction types and formulas, provides a flexible mechanism for financial and tax rule configuration.

Key Information Stored

The table's structure centers on linking a transaction type with a specific formula for tax basis calculation within an organizational context. While the full column list is not detailed in the provided metadata, the primary and foreign key relationships define its core data elements. The primary key is a composite of TRY_ID (Transaction Type ID) and ORG_ID (Operating Unit ID), enforcing a rule that a tax basis override is uniquely defined per transaction type per organization. The FMA_ID column stores the foreign key to the OKL_FORMULAE_B table, identifying the precise formula used for the override calculation. Additional columns likely exist to store metadata such as creation date, created by, last update date, and last updated by, which are standard in Oracle EBS tables.

Common Use Cases and Queries

A primary use case is configuring the system for a specific tax jurisdiction where the standard method for calculating tax on lease payments or buyouts is insufficient. An administrator would create a formula in the OKL formulae setup and then link it to the relevant transaction type (e.g., "Lease Invoice") for a specific operating unit via this table. Common queries involve validating setups and troubleshooting tax calculations. For example, to list all configured overrides, one might use: SELECT try_id, org_id, fma_id FROM okl_tax_basis_override;. To diagnose a tax calculation issue for a transaction, a support query would join to the transaction types and formulae tables: SELECT tt.name, f.formula_name FROM okl_tax_basis_override tbo, okl_trx_types_b tt, okl_formulae_b f WHERE tbo.try_id = tt.id AND tbo.fma_id = f.id AND tbo.org_id = :org_id;.

Related Objects

The OKL_TAX_BASIS_OVERRIDE table has defined dependencies on two key foundation tables in the OKL module, as per the provided foreign key metadata:

• OKL_TRX_TYPES_B: The table is referenced via the TRY_ID column. This join associates the tax override rule with a specific transaction type, such as an invoice, credit memo, or asset addition.
• OKL_FORMULAE_B: The table is referenced via the FMA_ID column. This relationship points to the executable formula that contains the custom logic for calculating the tax basis amount, which is central to the override's purpose.

The table itself is the parent in a primary key relationship named OKL_TBO_PK on the columns (TRY_ID, ORG_ID).