Search Results jai_rcv_rg_amount_v




Overview
Explore in AI Chat

Overview

The view APPS.JAI_RCV_RG_AMOUNT_V is a reporting object within the JA (Asia/Pacific Localizations) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It consolidates Indian excise register transaction amounts into a single, query-friendly structure. Specifically, it presents debit and credit amounts accumulated against statutory registers maintained for excise purposes: the RG23A Part II and RG23C Part II registers, and the PLA (Personal Ledger Account). These registers are central to Indian Central Excise compliance, tracking the utilization and accumulation of CENVAT credit for inputs and capital goods, as well as deposits and withdrawals from the PLA.

The view's principal role is to expose register transactions with independently totalled credit and debit components, enabling reporting, reconciliation, and downstream integration without each consumer having to reconstruct the amount logic. By deriving a single CREDIT and DEBIT figure from multiple duty heads (basic excise duty, additional excise duty, additional CVD, and other excise duty), it simplifies the presentation of excise balances.

The user search term "dr_basic_ed" maps directly to the debit-side basic excise duty column in the base transaction tables. This column is one of four summed components in the view's DEBIT expression, which is why this view is commonly retrieved when investigating basic excise duty debits.

Underlying Base Objects

The view is defined over two documented base objects, both exposed to APPS as synonyms:

  • JAI_CMN_RG_23AC_II_TRXS — the RG23A / RG23C Part II transaction table. The view filters this source to rows where TRANSACTION_SOURCE_NUM = 18, representing receipt-driven (RCV) register activity.
  • JAI_CMN_RG_PLA_TRXS — the PLA transaction table. The view filters this source to rows where TRANSACTION_SOURCE_NUM = 19.

The two sources are combined with UNION ALL, producing a unified transaction stream. The REGISTER column distinguishes the origin: rows from the RG23 source are labelled 'RG23A - PARTII' or 'RG23C - PARTII' via a DECODE on REGISTER_TYPE ('A' maps to RG23A), while PLA rows are labelled 'PLA'. The transaction identifier is also derived per source: RG23 rows use RECEIPT_REF (cast to character), whereas PLA rows use REF_DOCUMENT_ID.

Key Columns

Common Use Cases and Queries

Typical applications include excise register reconciliation, CENVAT credit utilization reporting, and period-end statutory returns preparation. The view is well suited to balance calculations because each row carries its own credit and debit totals.

To examine basic excise duty debits by register and financial year:

  • SELECT register, fin_year, SUM(debit) FROM jai_rcv_rg_amount_v GROUP BY register, fin_year;

To isolate PLA versus RG23 activity for a given organization:

  • SELECT transaction_id, register, excise_invoice_number, credit, debit FROM jai_rcv_rg_amount_v WHERE organization_id = :org AND register = 'PLA';

To compute net movement per register definition:

  • SELECT register_id, SUM(credit) - SUM(debit) net_movement FROM jai_rcv_rg_amount_v GROUP BY register_id;

Because the view already aggregates the individual duty heads, consumers investigating a specific component such as dr_basic_ed should query the base table JAI_CMN_RG_23AC_II_TRXS directly when that granularity is required; the view is intended for consolidated reporting.