Results for “vat_batch_num”

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

Overview

JAI_RCV_RTV_BATCH_TRXS is a transaction detail table owned by the JA (Asia/Pacific Localizations) schema in Oracle E-Business Suite. It stores Return-to-Vendor (RTV) batch transaction information captured for excise and VAT localization requirements, primarily associated with the India and broader Asia/Pacific localizations that track statutory batch-level tax details during goods returns. Each row captures the batch numbers, rates, and basis amounts applicable to a specific RTV movement against an inbound shipment and its underlying receiving transaction.

From a dimensional modeling perspective, the metadata's heuristic Data Vault classification identifies this object as a link. This is consistent with its structure: the table contains a surrogate primary key and a set of foreign keys that connect shipment headers, shipment lines, parent receiving transactions, and excise/VAT batch groups. It functions as an associative entity recording the intersection of these business entities rather than a pure hub of unique business keys or a satellite holding descriptive attributes alone.

Key Information Stored

The primary key is documented as JAI_RCV_RTV_BATCH_TRXS_PK, defined on the TRANSACTION_ID column. This is the surrogate identifier for each RTV batch transaction record; the documented metadata lists no separate unique business-key index in addition to this primary key, so TRANSACTION_ID serves as the unique business-key candidate as well.

• TRANSACTION_ID — Surrogate primary key uniquely identifying each RTV batch transaction row.
• SHIPMENT_HEADER_ID — Foreign key to RCV_SHIPMENT_HEADERS, tying the record to the receiving shipment header.
• SHIPMENT_LINE_ID — Foreign key to RCV_SHIPMENT_LINES, identifying the specific shipment line being returned.
• PARENT_TRANSACTION_ID — Foreign key to RCV_TRANSACTIONS, linking to the originating receiving transaction.
• EXCISE_BATCH_GROUP_ID and VAT_BATCH_GROUP_ID — Foreign keys to JAI_RCV_RTV_BATCH_GRPS, associating the transaction with the excise and VAT batch groupings.
• EXCISE_BATCH_NUM and VAT_BATCH_NUM — Statutory batch numbers recorded for excise and VAT reporting.
• RECEIPT_EXCISE_RATE and RTV_EXCISE_RATE — Excise rates applicable at receipt and at return respectively, enabling rate comparison.
• EXCISE_BASIS_AMT — The excise basis amount against which excise is computed for the RTV batch.
• VENDOR_ID and VENDOR_SITE_ID — The supplier and supplier site associated with the return.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the EBS framework for concurrent update control.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard who-columns providing audit lineage.

Common Use Cases and Queries

Typical usage centers on excise and VAT reconciliation for returned goods, batch traceability from receipt through return, and statutory reporting for India localization. A common pattern joins the table to shipment headers and lines to reconstruct the full return context:

• Retrieving all RTV batch transactions for a shipment: SELECT t.* FROM ja.jai_rcv_rtv_batch_trxs t WHERE t.shipment_header_id = :p_header_id;
• Reconciling excise rates between receipt and return by comparing RECEIPT_EXCISE_RATE and RTV_EXCISE_RATE.
• Aggregating EXCISE_BASIS_AMT by batch group for period-end excise reporting.
• Tracing a return back to its originating receiving transaction via PARENT_TRANSACTION_ID.
• Reporting VAT batch detail by vendor for localization compliance extracts.

Related Objects

• JAI_RCV_RTV_BATCH_GRPS — Referenced twice via EXCISE_BATCH_GROUP_ID and VAT_BATCH_GROUP_ID; the master batch group definition table.
• RCV_SHIPMENT_HEADERS — Joined on SHIPMENT_HEADER_ID for shipment-level context.
• RCV_SHIPMENT_LINES — Joined on SHIPMENT_LINE_ID for line-level return detail.
• RCV_TRANSACTIONS — Joined on PARENT_TRANSACTION_ID to reach the originating receiving transaction.
• PO_VENDORS / PO_VENDOR_SITES_ALL — Reference tables resolved through VENDOR_ID and VENDOR_SITE_ID.