Results for “tax_assessment_amount”

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

Overview

OKL_PROPERTY_TAX_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the OKL – Lease and Finance Management product family. Its documented purpose is to expose property tax information for assets against which a lease contract has been signed. In practice the view presents a denormalized, ready-to-query projection of property tax records, joining the transactional property tax base table with its translation (TL) table so that descriptive attributes such as asset description and language are available alongside the numeric tax data.

Because the view is a database object rather than a form-backed entity, it is intended primarily for reporting, data extraction, and integration scenarios. It surfaces jurisdiction, mill rate, assessment, and invoice-level tax amounts together with asset and contract identifiers, allowing operational and financial users to reconcile property tax obligations against leased assets without navigating the underlying normalized model. For a user searching on asset_units, this view is relevant because it exposes an ASSET_UNITS column alongside the asset identifier, making it a convenient single source for asset quantity and tax details in one row.

Underlying Base Objects

The documented view metadata identifies two referenced base objects, both accessed through APPS synonyms:

• OKL_PROPERTY_TAX_B – the base (transactional) property tax table, aliased as PTC in the view definition.
• OKL_PROPERTY_TAX_TL – the translation table, aliased as PTCT, supplying language-dependent descriptive columns.

The view text selects most columns from PTC and takes ASSET_DESCRIPTION, LANGUAGE, SOURCE_LANG, and SFWT_FLAG from PTCT. The join key between the two tables is the property tax record identifier (ID). This mirrors the standard EBS _B/_TL pattern, in which the base table holds language-independent transactional data and the TL table holds translatable descriptions keyed by language. A ROW_ID pseudo-column derived from PTC.ROWID is also exposed for row-level addressing.

Key Columns

The view exposes a broad set of columns spanning identity, asset, jurisdiction, and financial measures. Principal columns include:

• ID / ROW_ID – unique identifier and row address of the property tax record.
• ASSET_ID, ASSET_NUMBER, ASSET_UNITS, ASSET_DESCRIPTION – asset identification and the unit quantity associated with the leased asset.
• KHR_ID, KLE_ID, CONTRACT_NUMBER – linkage to the lease contract and related entities.
• JURSDCTN_TYPE, JURSDCTN_NAME, SEQUENCE_NUMBER – jurisdiction classification for the tax record.
• MLRT_TAX, MILRATE – mill rate tax values used in assessment calculations.
• TAX_ASSESSMENT_AMOUNT, TAX_ASSESSMENT_DATE, PROPERTY_TAX_AMOUNT – assessed value, assessment date, and resulting property tax amount.
• TAX_JURISDICTION_CITY/COUNTY/STATE/SCHOOL/COUNTRY and their corresponding _RATE columns – component jurisdiction rates.
• TAX_VENDOR_ID, TAX_VENDOR_NAME, TAX_VENDOR_SITE_ID, TAX_VENDOR_SITE_NAME, INVOICE_DATE, AMOUNT – supplier and invoice detail for the tax charge.
• ASSET_ADDRESS_1..4, ASSET_CITY, ASSET_STATE – address attributes of the taxed asset.
• ORG_ID – operating unit, enabling multi-org security filtering.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE – standard audit columns.

Common Use Cases and Queries

Typical scenarios include property tax reconciliation by lease or asset, jurisdiction-level rate analysis, and invoice-to-assessment tie-outs. Because ASSET_UNITS and ASSET_NUMBER are exposed, users frequently query this view to relate tax amounts to the quantity of leased units. A representative query follows:

• Property tax by asset: SELECT asset_number, asset_units, jurisdctn_name, property_tax_amount, invoice_date FROM okl_property_tax_v WHERE org_id = :p_org_id ORDER BY asset_number;
• Jurisdiction rate summary: SELECT jurisdctn_name, milrate, SUM(property_tax_amount) FROM okl_property_tax_v GROUP BY jurisdctn_name, milrate;
• Asset-specific lookup: SELECT asset_id, asset_number, asset_units, tax_assessment_amount, tax_assessment_date FROM okl_property_tax_v WHERE asset_number = :p_asset;
• Vendor/invoice detail: SELECT tax_vendor_name, tax_vendor_site_name, invoice_date, amount FROM okl_property_tax_v WHERE contract_number = :p_contract;

Queries should generally filter on ORG_ID to respect operating unit security, and on LANGUAGE/SOURCE_LANG when language-specific descriptions are required from the TL source. As a view over documented OKL base and translation tables, OKL_PROPERTY_TAX_V provides a stable, read-only interface suitable for reporting and outbound integration without direct dependency on the underlying table structures.