Results for “jai_rcv_rtv_batch_grps”

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

Overview

The JAI_RCV_RTV_BATCH_GRPS table resides in the JA schema and belongs to the Asia/Pacific Localizations product family within Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to store invoice lines created as part of Third Party Receipt Taxes (TPRT) processing, specifically the return-to-vendor (RTV) batch group header information required for excise and VAT batch reporting in APAC localization flows.

Each row represents a batch group header that consolidates return-to-vendor transactions for a specific vendor, vendor site, operating unit organization, and location within a tax regime. The table acts as a parent grouping record, with the actual tax transaction detail lines maintained in the companion table JAI_RCV_RTV_BATCH_TRXS.

From a Data Vault modeling perspective, the FK topology suggests this table is satellite-leaning. It carries descriptive business attributes (batch number, invoice number, invoice date, regime) tied to a defined business key, rather than behaving as a pure hub or a many-to-many link. Analysts reconstructing a dimensional or Data Vault model should treat BATCH_GROUP_ID as the surrogate anchor and the descriptive columns as satellite attributes.

Key Information Stored

The table contains 15 documented columns. The most operationally significant are:

• BATCH_GROUP_ID — Surrogate primary key defined by the unique index JAI_RCV_RTV_BATCH_GRPS_PK. This is the identifier most users search for when tracing a batch group back to its originating transactions.
• BATCH_NUM — Business-facing batch number assigned to the batch group; the primary human-readable reference used in reconciliation and audit reports.
• REGIME_CODE — Tax regime under which the batch is generated (e.g., excise or VAT regime applicable to the localization).
• ORGANIZATION_ID — Operating unit / organization that owns the batch, resolving to HR_ALL_ORGANIZATION_UNITS.
• LOCATION_ID — Physical or legal location associated with the batch, resolving to HR_LOCATIONS_ALL.
• VENDOR_ID — Supplier party for whom the return-to-vendor transaction was recorded, resolving to HZ_PARTIES.
• VENDOR_SITE_ID — Specific supplier site, resolving to HZ_PARTY_SITES.
• INVOICE_NO and INVOICE_DATE — Invoice reference and date captured for the third-party receipt tax documentation.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER — Standard EBS WHO columns and optimistic locking column, used for auditing and concurrency control.

The unique index confirms BATCH_GROUP_ID as the sole documented business-key candidate; no composite alternate key is exposed in the metadata.

Common Use Cases and Queries

Typical scenarios include extracting batch group headers for a given vendor to reconcile return-to-vendor tax postings, reporting excise or VAT batches by regime and period, and drilling from a batch group into its detail transactions. A common join pattern is:

• Batch-to-detail drill-down — join JAI_RCV_RTV_BATCH_GRPS to JAI_RCV_RTV_BATCH_TRXS on EXCISE_BATCH_GROUP_ID or VAT_BATCH_GROUP_ID to retrieve all transaction lines belonging to a group.
• Vendor-level reconciliation — filter by VENDOR_ID and VENDOR_SITE_ID to list all batches associated with a supplier.
• Regime and organization reporting — group by REGIME_CODE and ORGANIZATION_ID to summarize batch volumes and invoice values by operating unit.
• Invoice tracing — search by INVOICE_NO to locate the batch group that captured a specific invoice's third-party receipt tax line.

A representative query pattern selects BATCH_GROUP_ID, BATCH_NUM, REGIME_CODE, INVOICE_NO, and INVOICE_DATE from this table, filtered by VENDOR_ID and ORGANIZATION_ID, then joins outward to JAI_RCV_RTV_BATCH_TRXS for line-level tax detail. Reporting should always filter on REGIME_CODE when both excise and VAT batches coexist in the same period.

Related Objects

• JAI_RCV_RTV_BATCH_TRXS — Child transaction detail table; references this table via both EXCISE_BATCH_GROUP_ID and VAT_BATCH_GROUP_ID, confirming the group header role.
• HR_ALL_ORGANIZATION_UNITS — Joined on ORGANIZATION_ID to resolve the operating unit.
• HR_LOCATIONS_ALL — Joined on LOCATION_ID to resolve the location.
• HZ_PARTIES — Joined on VENDOR_ID to resolve the supplier name.
• HZ_PARTY_SITES — Joined on VENDOR_SITE_ID to resolve the supplier site.

These five relationships constitute the documented dependency graph for JAI_RCV_RTV_BATCH_GRPS in the ETRM 12.2.2 physical schema, with JAI_RCV_RTV_BATCH_TRXS forming the principal downstream consumer of the batch group key.