Results for “actual_yn”

20 results




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

Overview

OKL_TAX_LINES_ALL is a transactional table in the OKL (Leasing and Finance Management) schema of Oracle E-Business Suite. It stores individual tax lines calculated for lease and finance transactions, and is primarily used to display tax lines that satisfy Value Added Tax (VAT) reporting requirements within the Lease Center application. Each row represents a discrete tax computation event — a single tax type, rate, and amount tied to a specific taxable transaction, asset, or contract.

Because the table's structure is anchored by foreign keys to upstream transactional entities and enriched with descriptive and monetary attributes, a heuristic Data Vault classification of this object leans toward satellite. That classification should be treated as a modeling suggestion rather than a documented fact: the table carries descriptive tax detail around a transactional parent, which is characteristic of satellite design. Note that in EBS 12.x, the "_ALL" suffix conventionally signals multi-organization or multi-set-of-books partitioning, and the presence of ORG_ID and the WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) supports that interpretation.

Key Information Stored

The table's primary key is the ID column, an internally generated surrogate key. Several columns serve as business-key candidates linking the tax line to its owning transaction and contract context: KHR_ID, which joins to the contract header (OKL_PRTFL_CNTRCTS_B); TRQ_ID, which points to the originating transaction request (OKL_TRX_REQUESTS); and SOURCE_TRX_ID, which references an external source transaction record (IGI_DOS_TRX_SOURCES).

Common Use Cases and Queries

The dominant use case is VAT reporting and tax liability reconciliation for leasing portfolios. Analysts commonly query the table joined to the contract header to produce tax summaries by contract, asset, or operating unit, and to isolate lines that were manually entered or overridden for audit review.

  • Tax detail by contract: SELECT t.id, t.tax_type, t.taxable_amount, t.tax_amount FROM okl_tax_lines_all t WHERE t.khr_id = :khr_id AND t.actual_yn = 'Y';
  • Manual or overridden lines for audit: SELECT t.trq_id, t.tax_amount, t.manually_entered_flag, t.overridden_flag FROM okl_tax_lines_all t WHERE t.manually_entered_flag = 'Y' OR t.overridden_flag = 'Y';
  • Tax due schedule: filter by TAX_DUE_DATE to generate period-based accrual or filing extracts.
  • Reconciliation: compare TAX_AMOUNT against CALCULATED_TAX_AMOUNT to flag discrepancies.

Typical consumers include custom VAT extracts, subledger reconciliation reports, and downstream data-warehouse loads that stage tax lines for financial reporting.

Related Objects

The table's most significant relationships are defined by its documented foreign keys. Joining through these keys is essential for any meaningful query.

  • OKL_TRX_REQUESTS — joined on OKL_TAX_LINES_ALL.TRQ_ID = OKL_TRX_REQUESTS.TRQ_ID; supplies the source transaction request driving the tax line.
  • OKL_PRTFL_CNTRCTS_B — joined on OKL_TAX_LINES_ALL.KHR_ID = OKL_PRTFL_CNTRCTS_B.KHR_ID; provides the contract header context.
  • IGI_DOS_TRX_SOURCES — joined on OKL_TAX_LINES_ALL.SOURCE_TRX_ID = IGI_DOS_TRX_SOURCES.SOURCE_TRX_ID; links tax lines to externally originated transaction sources.

These three FK relationships form the backbone for VAT traceability when navigating from a lease contract through its tax computations to the originating transaction source.