Results for “invoice_tax”

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

Overview

APPS.OKL_CS_TERMQTE_TAX_SUM_UV is a reporting view within the Oracle E-Business Suite (EBS) Enterprise Contracts / Enterprise Tax Management (ETRM) module stack. It presents a consolidated, denormalized summary of estimated tax amounts associated with lease quotation lines. The view surfaces tax data in a business-friendly form, translating internal codes into descriptive names through joins to FND_LOOKUPS and the ZX (E-Business Tax) classification views. Its core role is to support reporting and integration scenarios where tax estimates against quotes must be reconciled or displayed alongside billing, stream, and product classification attributes. The view is owned by APPS and is exposed in both 12.1.1 and 12.2.2 environments, though the metadata documented here corresponds to ETRM 12.2.2.

Underlying Base Objects

The view draws its data primarily from OKL_TAX_SOURCES, which supplies the tax transaction, assessable value, total tax, and classification code columns. It is joined to several supporting objects:

• OKC_K_LINES_B and OKC_LINE_STYLES_B — provide contract line and line style (line type code) context.
• OKL_STRM_TYPE_B — supplies the stream type and its purpose.
• HZ_CUST_ACCOUNTS — resolves the bill-to customer account name and number.
• FND_LOOKUPS (JOINed twice) — decodes OKC_LINE_TYPE line type codes and OKL_STREAM_TYPE_PURPOSE into descriptive meanings.
• ZX_FC_CODES_DENORM_B, ZX_FC_PRODUCT_CATEGORIES_V, ZX_FC_USER_DEFINED_V, ZX_FC_INTENDED_USE_V — E-Business Tax classification sources for transaction business category, product category, user-defined fiscal classification, and intended use.
• OKL_LLA_UTIL_PVT — a PL/SQL package whose get_Asset_location function derives the asset location from KLE_ID and KHR_ID.
• FND_GLOBAL — supplies the USERENV language context for the language-specific ZX joins.

Despite the metadata listing HZ_CUST_ACCOUNTS and others as synonyms, all objects ultimately resolve to the APPS schema.

Key Columns

The view exposes a mix of descriptive and identifying columns:

• BILL_TO_CUSTOMER — concatenated account name and number.
• LINE_TYPE — lookup meaning decoded from OKC_LINE_TYPE against the line style code (OKLS.LTY_CODE).
• LINE_NAME, STREAM_TYPE — textual descriptors of the tax line and stream purpose.
• ASSET_LOCATION — computed via OKL_LLA_UTIL_PVT.get_Asset_location.
• TAX_DATE, TAX_AMOUNT, TOTAL_TAX — temporal and monetary tax measures.
• TRX_BUSINESS_CATEGORY, PRODUCT_CATEGORY, USER_DEFINED_FISC_CLASS, LINE_INTENDED_USE — tax classification dimensions.
• Identifiers such as KLE_ID, KHR_ID, TRX_ID, TRX_LINE_ID, TRY_ID, LEGAL_ENTITY_ID, ORG_ID, plus ENTITY_CODE, EVENT_CLASS_CODE, APPLICATION_ID, TRX_LEVEL_TYPE, TAX_CALL_TYPE_CODE, TAX_LINE_STATUS_CODE, TRX_CURRENCY_CODE, and DEFAULT_TAXATION_COUNTRY.

Common Use Cases and Queries

The view is typically filtered by key tax event attributes. The WHERE clause restricts to TAX_LINE_STATUS_CODE = 'ACTIVE', TAX_CALL_TYPE_CODE = 'INVOICE_TAX', ENTITY_CODE = 'AM_QUOTES', APPLICATION_ID = 540, EVENT_CLASS_CODE = 'ESTIMATED_BILLING', and TRX_LEVEL_TYPE = 'LINE', meaning it reports estimated billing tax at line level for Oracle Assets/Leasing quotes.

A representative query returning line type alongside tax:

• SELECT bill_to_customer, line_type, line_name, tax_amount, total_tax, trx_currency_code FROM apps.okl_cs_termqte_tax_sum_uv WHERE trx_id = :trx_id;
• SELECT line_type, SUM(tax_amount) FROM apps.okl_cs_termqte_tax_sum_uv GROUP BY line_type;
• SELECT kle_id, khr_id, asset_location, product_category, total_tax FROM apps.okl_cs_termqte_tax_sum_uv WHERE legal_entity_id = :le_id;

Note the outer joins (marked with (+)) to OKC_K_LINES_B, OKC_LINE_STYLES_B, OKL_STRM_TYPE_B, and the lookup/classification sources — tax records may persist even when the corresponding contract line or classification data is absent, so consumers must tolerate NULL line_type values. This behaviour is important when the view is used for reconciliation between tax and contract structures. Given the view's dependence on ZX views and OKL_LLA_UTIL_PVT, query performance benefits from filtering on TRX_ID, KLE_ID, or LEGAL_ENTITY_ID.