Search Results transaction_source_num




Overview
Explore in AI Chat

Overview

APPS.JAI_RCV_RG_QUANTITY_V is a reporting view in Oracle E-Business Suite that consolidates receipt-based quantity information captured in the Indian excise registers maintained by the JAI (India Localization) module. It presents a unified, read-only projection of goods received quantities drawn from three separate statutory register tables, exposing them through a single consistent column set. In Oracle EBS 12.1.1 and 12.2.2, this view is primarily used to support excise and VAT reporting, reconciliation of receipt quantities against register balances, and downstream reporting or integration queries that require a normalized quantity figure regardless of which register originally held the transaction.

A defining characteristic of the view is the TRANSACTION_SOURCE_NUM = 18 filter applied to every branch of the underlying UNION, which restricts the result set to receipt-based movements. This aligns the view with Receiving (RCV) activity, consistent with its JAI_RCV naming prefix.

Underlying Base Objects

The view is defined over three documented base objects, all accessed through public synonyms owned by APPS:

The three branches are combined with UNION ALL for the first two and UNION for the third, yielding a de-duplicated, register-agnostic result set. All three branches apply the same source-number filter.

Key Columns

Common Use Cases and Queries

Typical scenarios include tracing the register context of a received quantity, reconciling excise register totals against receipt data, and generating quantity-based audit extracts.

SELECT register, transaction_id, quantity_received
FROM   apps.jai_rcv_rg_quantity_v
WHERE  organization_id = :org_id
AND    fin_year = :fin_year;

Aggregation by register is common for statutory summaries:

SELECT register, SUM(quantity_received) total_qty
FROM   apps.jai_rcv_rg_quantity_v
GROUP  BY register;

Because the view is a UNION, queries filtering on EXCISE_INVOICE_NUMBER or TRANSACTION_ID are effective for locating a specific movement across registers. As with all such views, no DML is permitted; it is intended strictly for query and reporting purposes.