Search Results primary_uom

Overview

JAI_RCV_RG_QUANTITY_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 excise register quantities arising from receiving transactions so that they can be reported against the Indian excise register structures (RG23A, RG23C, RG23D and RG-I). The view is defined with status VALID in ETRM 12.2.2 and is also present in 12.1.1. It is not an operational entity; it is a read-only projection intended for statutory excise reporting, reconciliation of receipted quantities, and downstream integration where receipt-level register information is required. The view filters strictly on TRANSACTION_SOURCE_NUM = 18, that is, only receipt-driven register entries are surfaced.

Underlying Base Objects

The view is a UNION ALL / UNION construct over three underlying register transaction tables, referenced through synonyms in the APPS schema:

• JAI_CMN_RG_23AC_I_TRXS — source of RG23A and RG23C Part I register lines (REGISTER_TYPE 'A' or 'C').
• JAI_CMN_RG_I_TRXS — source of RG-I register lines, exposing MANUFACTURED_QTY as the quantity.
• JAI_CMN_RG_23D_TRXS — source of RG23D register lines, exposing COMM_INVOICE_NO and COMM_INVOICE_DATE for invoice detail.

Each branch is restricted to TRANSACTION_SOURCE_NUM = 18 and contributes the same thirteen columns, so the view presents a single homogeneous result set regardless of the register family. Because the branches use UNION ALL (with the final two combined by UNION), duplicate elimination behaviour differs slightly between registers, but this does not affect the reported quantity semantics.

Key Columns

• TRANSACTION_ID — RECEIPT_REF from the RG23A/C table, REF_DOC_NO from RG-I, or RECEIPT_REF cast to character from RG23D.
• REGISTER — derived literal identifying the register: 'RG23A - PARTI', 'RG23C - PARTI', 'RG-I' or 'RG23D'.
• ORGANIZATION_ID, LOCATION_ID, FIN_YEAR, SLNO, REGISTER_ID — registration attributes identifying the organisation, location, financial year and the specific register line.
• EXCISE_INVOICE_NUMBER and EXCISE_INVOICE_DATE — invoice references (mapped from EXCISE_INVOICE_NO, or COMM_INVOICE_NO/DATE for RG23D). Date values are TRUNC'd.
• CREATION_DATE — truncated creation timestamp of the register line.
• PRIMARY_UOM and TRANSACTION_UOM — primary and transactional unit of measure codes.
• QUANTITY_RECEIVED — the received quantity (QUANTITY_RECEIVED for RG23A/C and RG23D, MANUFACTURED_QTY for RG-I).

Common Use Cases and Queries

Typical uses include excise register reporting, quantity reconciliation between receipts and registers, and data extraction for statutory returns. A representative query lists all receipt-driven register quantities for an organisation, period and register:

SELECT register, transaction_id, fin_year,
       excise_invoice_number, excise_invoice_date,
       quantity_received, primary_uom
FROM   apps.jai_rcv_rg_quantity_v
WHERE  organization_id = :org_id
AND    fin_year = :fin_year
AND    register IN ('RG23A - PARTI','RG-I');

A second scenario aggregates received quantities by register for period-end reconciliation: SELECT register, SUM(quantity_received) FROM apps.jai_rcv_rg_quantity_v GROUP BY register. Because the view is defined in APPS and joins no other objects, it can be queried directly by reporting tools and custom concurrent programs without additional joins, provided the caller supplies ORGANIZATION_ID and FIN_YEAR to constrain the UNION result set.