Results for “jai_cmn_cess_trxs_v”

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

Overview

JAI_CMN_CESS_TRXS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the JA (Asia/Pacific Localizations) product family. Its purpose is to consolidate cess (a local indirect tax levied in certain Asia/Pacific jurisdictions, notably India) transaction details into a single, query-ready structure. The view is not a transactional entity; it is a read-only aggregation layer that presents cess amounts alongside the documents, parties, tax definitions, and accounting references from which they originated.

Because the view exposes a CESS_AMT column directly, it is the object users typically target when searching for the literal term "cess_amount". This makes it the standard entry point for cess reconciliation, statutory tax reporting, and downstream extracts feeding GST/cess returns. The view text is a UNION ALL of multiple source branches, normalising dissimilar transaction feeds into a common column set so that a single query can report cess across invoice, shipment, and receipt activity.

Underlying Base Objects

The view is defined over a broad set of documented base objects, reflecting its multi-source design:

• AR/manual invoice branch: JAI_AR_TRX_LINES and JAI_AR_TRX_TAX_LINES join to JAI_CMN_TAXES_ALL, RA_CUSTOMER_TRX_ALL, JAI_CMN_CUSTOMERS_V, and JAI_CMN_CUSTOMER_SITES_V.
• Shipment/order branch: JAI_OM_WSH_LINES_ALL and JAI_OM_WSH_LINE_TAXES join to JAI_CMN_TAXES_ALL, OE_ORDER_HEADERS_ALL, and the same customer/customer site views.
• Receiving branch: JAI_RCV_LINES and JAI_RCV_LINE_TAXES, together with RCV_TRANSACTIONS, PO_VENDORS, and PO_VENDOR_SITES_ALL, contribute vendor-side cess transactions.
• Registration and reference data: JAI_CMN_RG_PLA_TRXS supplies registration identifiers, while GL_JE_HEADERS and GL_JE_LINES provide accounting context and FND_GLOBAL supplies session/environment attributes.

The tax amount is always sourced from the corresponding localisation tax line table (for example JAI_AR_TRX_TAX_LINES.TAX_AMOUNT), while tax definition attributes such as rate, name, and cess type are drawn from JAI_CMN_TAXES_ALL. A DISTINCT is applied over the UNION ALL result to suppress duplicate rows.

Key Columns

• SOURCE — Identifies the originating feed, e.g. 'MANUAL AR INVOICES' or 'SHIPMENT DETAILS'.
• PARTY_NAME, PARTY_SITE — Customer or vendor and site associated with the transaction.
• SLNO — Document serial number; in the AR branch this is the transaction number (RAX.TRX_NUMBER), in the shipment branch the order number.
• REGISTER_ID — Excise/cess registration identifier, populated where the registration feed applies.
• TRANSACTION_DATE — Truncated creation date of the underlying transaction line.
• CODE_COMBINATION_ID — The tax accounting account (JTC.TAX_ACCOUNT_ID) used for posting.
• ITEM_ID, EX_INV_NO — Inventory item and the truncated excise invoice number.
• TAX_NAME, TAX_TYPE, CESS_TYPE — Tax definition, category, and the cess form/structure type.
• RATE — Tax rate as a percentage.
• CESS_AMT — The cess tax amount taken from the source tax line.
• TAXABLE_BASIS — Derived as CESS_AMT / (RATE/100), yielding the base value on which cess was computed.

Common Use Cases and Queries

The principal uses are cess reconciliation to the GL, statutory cess return preparation, and audit extracts by registration or period. A representative query filtering on the amount column:

• SELECT source, slno, party_name, transaction_date, tax_name, rate, cess_amt, taxable_basis FROM apps.jai_cmn_cess_trxs_v WHERE cess_amt > 0 AND transaction_date BETWEEN :p_from AND :p_to ORDER BY transaction_date, slno;
• Grouping by registration or account for reconciliation: SELECT register_id, code_combination_id, SUM(cess_amt) FROM apps.jai_cmn_cess_trxs_v GROUP BY register_id, code_combination_id;
• Isolating a feed: add WHERE source = 'MANUAL AR INVOICES' (or 'SHIPMENT DETAILS') to review one branch.

Because the view is a UNION ALL of distinct transaction families, queries should always constrain SOURCE and date range to avoid full scans across AR, order, and receiving data sets.