Search Results jai_rcv_headers




Overview
Explore in AI Chat

Overview

JAI_RCV_HEADERS is the India Localization receipts header table, owned by the JA schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It mirrors the structure and semantics of the standard Oracle Receiving table RCV_SHIPMENT_HEADERS, extending it with India-specific excise and tax attributes required for statutory compliance. The table is classified as VALID within the ETRM repository and forms part of the JA – Asia/Pacific Localizations product family.

Functionally, the table stores receipt header information for inbound shipments, including vendor and customer references, excise invoice details, and RMA processing indicators. It serves as the localization anchor point that integrates with Oracle Purchasing and Oracle Receiving flows when the India Localization (JA) module is installed. Based on its foreign key structure, the heuristic Data Vault classification for this object is link: it bridges party master data (vendors and customers), party sites, and organization units, connecting these reference hubs to transactional receipt activity.

Key Information Stored

The primary key JAI_RCV_HEADERS_PK is defined on SHIPMENT_HEADER_ID, a surrogate identifier that aligns the localization record with the corresponding standard shipment header. The most significant columns include:

No unique business-key index other than the primary key is documented; RECEIPT_NUM and SHIPMENT_NUM are therefore business identifiers rather than enforced unique keys.

Common Use Cases and Queries

Typical use cases center on India excise reporting and receipts reconciliation. A common query joins the localization header to the standard receiving tables to reconcile excise invoices against shipments:

  • Extracting excise invoice registers for a given period using EXCISE_INVOICE_DATE and EXCISE_INVOICE_NO.
  • Reconciling localization receipts to standard RCV_SHIPMENT_HEADERS on SHIPMENT_HEADER_ID.
  • Reporting vendor-wise and organization-wise inbound receipt volumes using VENDOR_ID and ORGANIZATION_ID.
  • Identifying return transactions through RMA_TYPE and CUSTOMER_ID for credit and claim processing.
  • Auditing third-party and online claim scenarios via THIRD_PARTY_FLAG and ONLINE_CLAIM_FLAG.

A representative pattern: SELECT h.RECEIPT_NUM, h.EXCISE_INVOICE_NO, p.PARTY_NAME FROM JA.JAI_RCV_HEADERS h, HZ_PARTIES p WHERE h.VENDOR_ID = p.PARTY_ID AND h.EXCISE_INVOICE_DATE BETWEEN :start_date AND :end_date;

Related Objects

  • RCV_SHIPMENT_HEADERS – Standard receiving header; joined on SHIPMENT_HEADER_ID, the localization counterpart structure.
  • HZ_PARTIES – Referenced by VENDOR_ID and CUSTOMER_ID for supplier and customer identity.
  • HZ_PARTY_SITES – Referenced by VENDOR_SITE_ID and CUSTOMER_SITE_ID for site-level address and tax details.
  • HR_ALL_ORGANIZATION_UNITS – Referenced by ORGANIZATION_ID to resolve the receiving inventory organization.
  • JAI_RCV_LINES – The corresponding India localization receipt line table, linked through the shipment header.
  • JAI_AP_TDS_INVOICES / JAI_CMN_* – India localization tax and common tables that consume receipt header data for excise reporting.
  • RCV_SHIPMENT_LINES – Standard line detail that pairs with this header for full receipt documents.
  • PO_HEADERS_ALL / PO_LINES_ALL – Purchase order references underlying the receipt for procurement traceability.