Search Results cess_amt




Overview
Explore in AI Chat

Overview

APPS.JAI_CMN_CESS_TRXS_V is a consolidated reporting view within the Oracle E-Business Suite India Localization (JAI) module. Its purpose is to present a unified register of cess transactions drawn from multiple transactional flows, principally manual AR invoices and shipment (delivery) details. The view normalizes dissimilar source records into a common column layout so that cess amounts, tax rates, taxable basis, and associated party information can be reported through a single query surface. Because cess is an India-specific indirect tax construct tied to excise and customs processing, this view is typically consumed by tax reporting, statutory filing extracts, and reconciliation reports rather than by transactional forms.

The presence of PARTY_SITE and PARTY_NAME columns, sourced from the JAI_CMN_CUSTOMER_SITES_V and JAI_CMN_CUSTOMERS_V views, indicates the view resolves the transacting party and their site code for each cess line. This supports reporting at the party/site grain, which is frequently required for excise and cess documentation.

Underlying Base Objects

The view is defined as a UNION ALL over at least two sub-queries. The first covers manual AR invoices, joining JAI_AR_TRX_LINES, JAI_AR_TRX_TAX_LINES, JAI_CMN_TAXES_ALL, RA_CUSTOMER_TRX_ALL, JAI_CMN_CUSTOMER_SITES_V, and JAI_CMN_CUSTOMERS_V. The second covers shipment details, joining JAI_OM_WSH_LINES_ALL, JAI_OM_WSH_LINE_TAXES, JAI_CMN_TAXES_ALL, OE_ORDER_HEADERS_ALL, and the same customer and site views. The documented base object list also references GL_JE_HEADERS, GL_JE_LINES, JAI_CMN_RG_PLA_TRXS, JAI_RCV_LINES, JAI_RCV_LINE_TAXES, RCV_TRANSACTIONS, PO_VENDORS, PO_VENDOR_SITES_ALL, and FND_GLOBAL, indicating the view text (or its dependencies) spans additional receipt, vendor, and general ledger flows. JAI_CMN_TAXES_ALL supplies the tax definition, including STFORM_TYPE used to filter cess records.

Key Columns

  • SOURCE — Identifies the originating flow, e.g. 'MANUAL AR INVOICES' or 'SHIPMENT DETAILS'.
  • PARTY_NAME / PARTY_SITE — Customer or party name and the associated party site code.
  • SLNO — Transaction number (AR trx number or order number) cast to character.
  • TRANSACTION_DATE — Truncated creation date of the transaction line.
  • CODE_COMBINATION_ID — The tax account identifier from JAI_CMN_TAXES_ALL.
  • ITEM_ID, EX_INV_NO — Inventory item and the excise invoice number (truncated to 30 characters).
  • TAX_NAME, TAX_TYPE, CESS_TYPE, RATE — Tax attributes; CESS_TYPE maps to STFORM_TYPE.
  • CESS_AMT, TAXABLE_BASIS — The cess amount and the derived taxable basis (cess amount divided by rate/100).

Common Use Cases and Queries

Typical usage includes cess reconciliation, statutory extract preparation, and cross-flow analysis of cess by party site or item. A representative query filtering by party site code is:

  • SELECT source, party_name, party_site, slno, transaction_date, tax_name, rate, cess_amt, taxable_basis FROM apps.jai_cmn_cess_trxs_v WHERE party_site = :p_site ORDER BY transaction_date;
  • SELECT cess_type, SUM(cess_amt) FROM apps.jai_cmn_cess_trxs_v WHERE transaction_date BETWEEN :from_date AND :to_date GROUP BY cess_type;

Because the view unions multiple sources and applies DISTINCT, aggregation and date-range filtering are recommended to bound result sets. The view should be treated as read-only reference data for reporting purposes.