Search Results trx_business_category




Overview
Explore in AI Chat

Overview

OKL_CS_TAXSCH_TAX_SUM_UV is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKL – Leasing and Finance Management product family. Its documented purpose is to present a consolidated tax summary for tax schedule lines, joining leasing contract structures to the E-Business Tax (ZX) classification model and to customer account data. The view is a read-only summary construct rather than a transactional table; it does not store data and exists solely to project a denormalized, human-readable picture of tax assessments generated for lease contract schedules.

The view is filtered to a narrow, well-defined slice of tax data. It restricts rows to active tax lines (TAX_LINE_STATUS_CODE = 'ACTIVE') raised through the tax schedule call type (TAX_CALL_TYPE_CODE = 'TAX_SCHEDULE'), originating from the entity TAX_SCHEDULE_REQUESTS, application identifier 540, event class TAX_SCHEDULE, and line-level transaction granularity (TRX_LEVEL_TYPE = 'LINE'). This makes it a targeted reporting surface for tax schedule processing rather than a general tax register.

Underlying Base Objects

The view is defined over a mixture of base tables, synonyms, views, and a PL/SQL package. The principal fact source is OKL_TAX_SOURCES (referenced in the view text as the alias TAXS), which contributes the tax amounts, dates, and classification codes. Leasing contract context is supplied through outer joins to OKC_K_LINES_B and OKC_LINE_STYLES_B, and stream information is drawn from OKL_STRM_TYPE_B. Customer identity is resolved via HZ_CUST_ACCOUNTS.

Descriptive values are obtained from FND_LOOKUPS for line type and stream type meanings, and from the E-Business Tax views ZX_FC_CODES_DENORM_B, ZX_FC_PRODUCT_CATEGORIES_V, ZX_FC_USER_DEFINED_V, and ZX_FC_INTENDED_USE_V for the fiscal classification dimensions. The asset location column is not stored anywhere in these sources; it is computed at runtime through the package function OKL_LLA_UTIL_PVT.GET_ASSET_LOCATION. The documented dependency list also notes FND_GLOBAL, reflecting the standard EBS practice of resolving session context such as organization and user identifiers.

Key Columns

Common Use Cases and Queries

The most frequent use case is tax schedule reporting and reconciliation by legal entity, lease, or customer. Because the view exposes TRX_BUSINESS_CATEGORY alongside the ZX classification columns, it is also commonly used to analyze tax outcomes by fiscal classification.

A representative query filtering by the searched attribute is:

  • SELECT bill_to_customer, line_type, tax_date, tax_amount, total_tax, trx_business_category FROM okl_cs_taxsch_tax_sum_uv WHERE trx_business_category = :p_category AND org_id = :p_org_id;

Additional scenarios include aggregating total tax by legal entity over a date range, and listing asset locations for audit or jurisdictional review. Note that the view applies no ORG_ID or LEGAL_ENTITY_ID predicate internally, so callers must supply the appropriate operating unit or legal entity restriction. Performance depends on the underlying OKL_TAX_SOURCES indexes and on the cost of the GET_ASSET_LOCATION function call per row.