Results for “regime_item_class”

32 results




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

Overview

JAI_RCV_RGM_LINES is a transactional table owned by the JA schema within the Oracle E-Business Suite Asia/Pacific Localizations module. It stores line-level detail for receipt claims processed under the Regional Goods Management (RGM) claim framework used in Indian and other Asia/Pacific localization implementations. Each row captures the receipt, regime, tax term, vendor, and quantity information required to calculate a recoverable amount for a specific claim line, and it serves as the operative detail record beneath the claim header maintained in JAI_RCV_RGM_CLAIMS.

Based on the foreign key topology documented in the ETRM metadata, this object is best modeled as satellite-leaning. Its primary key, RCV_RGM_LINE_ID, is a surrogate identifier unique to the claim line itself, while the numerous outbound foreign keys to shipment, transaction, item, vendor, and term masters indicate a dependent structure rather than a hub. In a Data Vault design, JAI_RCV_RGM_LINES would map most naturally to a satellite hanging off the receipt transaction or shipment line hub, with descriptive claim attributes and amount measures attached at the claim-line grain.

Key Information Stored

The table contains 47 documented columns. The surrogate primary key is RCV_RGM_LINE_ID, enforced by the unique index JAI_RCV_RGM_LINES_PK. The metadata identifies no additional unique business-key indexes, so the surrogate key is the sole documented uniqueness constraint.

Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER) and fifteen descriptive ATTRIBUTE columns plus ATTRIBUTE_CATEGORY provide audit and extensibility support.

Common Use Cases and Queries

Typical usage centers on claim reconciliation reporting, recoverable amount tracking, and integration with purchasing and payables. A common query joins the claim line to its header and receipt transaction to report outstanding recoverables by vendor:

  • Retrieve claim lines by process status: SELECT rcv_rgm_line_id, receipt_num, recoverable_amount, recovered_amount FROM jai_rcv_rgm_lines WHERE process_status_flag = :status;
  • Reconcile claim amounts to receipt transactions by joining on TRANSACTION_ID to RCV_TRANSACTIONS and SHIPMENT_LINE_ID to RCV_SHIPMENT_LINES.
  • Analyze recoverability by regime: group by REGIME_CODE and REGIME_ITEM_CLASS, summing RECOVERABLE_AMOUNT minus RECOVERED_AMOUNT.
  • Vendor-facing reporting: join VENDOR_ID and VENDOR_SITE_ID to HZ_PARTIES and HZ_PARTY_SITES to present supplier details.
  • Audit queries filtering on CREATION_DATE and LAST_UPDATE_DATE windows for month-end close.

Related Objects

The following objects are the most significant dependencies, based on documented foreign key relationships:

  • JAI_RCV_RGM_CLAIMS — child claim records reference this table via JAI_RCV_RGM_CLAIMS.RCV_RGM_LINE_ID, tying each claim to its line detail.
  • RCV_SHIPMENT_HEADERS and RCV_SHIPMENT_LINES — joined on SHIPMENT_HEADER_ID and SHIPMENT_LINE_ID respectively for receipt context.
  • RCV_TRANSACTIONS — joined on TRANSACTION_ID to trace the originating receipt movement.
  • MTL_SYSTEM_ITEMS_B — joined on INVENTORY_ITEM_ID and ORGANIZATION_ID for item validation.
  • JAI_RGM_TERMS — joined on TERM_ID to resolve the calculation term applied to the claim line.
  • HZ_PARTIES and HZ_PARTY_SITES — joined on VENDOR_ID and VENDOR_SITE_ID for supplier details.
  • HR_LOCATIONS_ALL — joined on LOCATION_ID where location context is required.

These relationships make JAI_RCV_RGM_LINES a central detail table for receipt-based claim processing in the Asia/Pacific localization, and it should be treated as a dependent satellite of the receipt transaction domain in any downstream reporting or Data Vault model.