Search Results cess_debit

Overview

APPS.JAI_RCV_RG_AMOUNT_V is a reporting view in Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2 that consolidates receipt-related excise register transactions maintained by the India Localization (JAI) module. India Localization tracks excise duty movements through statutory registers, principally the RG23A and RG23C Part II registers and the PLA (Personal Ledger Account). This view presents a unified, amount-oriented projection of those register entries so that downstream reports, reconciliations, and integration programs can consume credit and debit values without navigating the individual transaction tables directly.

The view is defined by a UNION ALL of two SELECT statements, each drawing from a separate register transaction table and filtering on a fixed transaction source. It exposes the register identity, organization and location context, financial year, serial number, and excise invoice data, alongside aggregated credit and debit amounts. Because both halves of the union share the same column list and data types, consumers see a single, uniform result set spanning both excise register families.

Underlying Base Objects

The documented base objects referenced by APPS.JAI_RCV_RG_AMOUNT_V are two synonyms:

• JAI_CMN_RG_23AC_II_TRXS — the RG23A/RG23C Part II transaction table. The view filters this source with the predicate WHERE TRANSACTION_SOURCE_NUM = 18 and derives the REGISTER label through DECODE(REGISTER_TYPE, 'A', 'RG23A - PartII', 'RG23C - PartII').
• JAI_CMN_RG_PLA_TRXS — the PLA transaction table. The second union branch filters this source with WHERE TRANSACTION_SOURCE_NUM = 19 and hard-codes the REGISTER literal as 'PLA'.

Both underlying objects are synonyms, resolving to the corresponding JAI accounting and excise register tables in the APPS schema. The view is therefore a read-only, non-materialized definition: no independent storage exists, and every query executes the union against the base tables in real time.

Key Columns

• TRANSACTION_ID — For RG23 entries, the character form of RECEIPT_REF; for PLA entries, the character form of REF_DOCUMENT_ID. It links the register row back to the originating receipt or reference document.
• REGISTER — Identifies the statutory register: 'RG23A - PartII', 'RG23C - PartII', or 'PLA'.
• ORGANIZATION_ID, LOCATION_ID — Inventory organization and location context for the transaction.
• FIN_YEAR, SLNO, REGISTER_ID — Financial year, serial number, and register identifier supporting sequential and statutory reporting.
• EXCISE_INVOICE_NUMBER, EXCISE_INVOICE_DATE — Excise invoice reference and its truncated date; sourced from EXCISE_INVOICE_NO/DR_INVOICE_NO and EXCISE_INVOICE_DATE/DR_INVOICE_DATE depending on the union branch.
• CREDIT — Sum of NVL-protected CR_BASIC_ED, CR_ADDITIONAL_ED, CR_ADDITIONAL_CVD (RG23 branch only), and CR_OTHER_ED.
• DEBIT — Sum of NVL-protected DR_BASIC_ED, DR_ADDITIONAL_ED, DR_ADDITIONAL_CVD (RG23 branch only), and DR_OTHER_ED.
• OTHER_CREDIT / OTHER_DEBIT — Standalone NVL-protected values from OTHER_TAX_CREDIT and OTHER_TAX_DEBIT. The user's search term "other_debit" maps directly to the OTHER_DEBIT column.

Common Use Cases and Queries

Typical uses include excise register reconciliation, CENVAT credit tracking, and feeds into statutory returns. To isolate debit-side activity, including the OTHER_DEBIT component:

• SELECT transaction_id, register, fin_year, debit, other_debit FROM apps.jai_rcv_rg_amount_v WHERE other_debit > 0;
• SELECT register, fin_year, SUM(debit) total_debit, SUM(other_debit) total_other_debit FROM apps.jai_rcv_rg_amount_v GROUP BY register, fin_year;
• SELECT * FROM apps.jai_rcv_rg_amount_v WHERE organization_id = :org AND fin_year = :fy;

Because the view performs union and arithmetic at runtime, restrictive predicates on ORGANIZATION_ID, FIN_YEAR, or REGISTER improve performance. Access is governed by the APPS schema and standard JAI responsibilities.