Search Results jai_rcv_transactions_pk

Overview

JAI_RCV_TRANSACTIONS is a transaction-level table owned by the JA schema, the schema that carries the Oracle E-Business Suite Asia/Pacific localizations. In the documentation metadata it is classified under Product/Module JA - Asia/Pacific Localizations, and its stated purpose is to hold receiving transaction records information. Operationally, the table functions as the localization extension for standard Oracle Receiving, storing the excise, CENVAT, VAT, and latterly GST attributes that Indian and other Asia/Pacific statutory regimes require when goods are received against a shipment. The table is documented as VALID in ETRM for both 12.1.1 and 12.2.2, and the physical schema listing records 79 columns in the JA schema.

Modelling the object heuristically from its foreign key structure yields a Data Vault classification of link. This classification is a modelling suggestion rather than a documented attribute: the table carries its own surrogate primary key, TRANSACTION_ID, yet almost every meaningful column is a foreign reference, notably to RCV_TRANSACTIONS, RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES, HR_ALL_ORGANIZATION_UNITS, HR_LOCATIONS_ALL, and MTL_SYSTEM_ITEMS_B, and also to three self-referencing roles on RCV_TRANSACTIONS. That pattern is characteristic of an associative structure that ties a receiving event to the organizational, item, and location context in which the localized tax treatment is computed.

Key Information Stored

The primary key is TRANSACTION_ID, enforced by the unique index JAI_RCV_TRANSACTIONS_PK. Because there is only one documented unique index, TRANSACTION_ID is also the sole business-key candidate identified in the source metadata; it is simultaneously a foreign key to RCV_TRANSACTIONS, meaning the localized row is keyed to the same transaction identifier used by the core receiving tables.

• Transaction identification: TRANSACTION_ID, TRANSACTION_TYPE, TRANSACTION_DATE, and RECEIPT_NUM describe the receipt event itself.
• Context keys: SHIPMENT_HEADER_ID, SHIPMENT_LINE_ID, ORGANIZATION_ID, LOCATION_ID, and INVENTORY_ITEM_ID identify the shipment, line, organization, location, and item involved.
• Hierarchy references: PARENT_TRANSACTION_ID, PARENT_TRANSACTION_TYPE, and TAX_TRANSACTION_ID allow a transaction to be linked to its originating or tax counterpart record.
• Quantity and UOM: QUANTITY and UOM_CODE capture the received amount.
• Statutory tax values: TAX_AMOUNT, ASSESSABLE_VALUE, CENVAT_AMOUNT, CENVAT_CLAIMED_PTG, EXCISE_INVOICE_NO, EXCISE_INVOICE_DATE, VAT_INVOICE_NO, VAT_INVOICE_DATE, and the more recent GST_INVOICE_NO and GST_INVOICE_DATE hold the excise, CENVAT, VAT, and GST data used for compliance reporting.
• Classification flags: ITEM_CLASS, ITEM_CENVATABLE, ITEM_EXCISABLE, INV_ITEM_FLAG, INV_ASSET_FLAG, and COSTING_METHOD drive how the localized tax logic treats each receipt. PROCESS_STATUS, PROCESS_MESSAGE, CENVAT_RG_STATUS, and PROCESS_VAT_STATUS record the outcome of that processing.
• Audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and ATTRIBUTE1 through ATTRIBUTE15 are the standard EBS audit and descriptive-flexfield columns, supported here by OBJECT_VERSION_NUMBER for optimistic locking.

Common Use Cases and Queries

Reporting and reconciliation are the dominant uses. A typical query joins the localized row back to core receiving to reconcile quantities and tax amounts:

• Excise and VAT register reporting: filter on EXCISE_INVOICE_DATE or VAT_INVOICE_DATE to produce period returns.
• CENVAT credit tracking: aggregate CENVAT_AMOUNT where CENVAT_CLAIMED_PTG is set.
• Receipt reconciliation: join TRANSACTION_ID to RCV_TRANSACTIONS and RCV_SHIPMENT_LINES to compare localized tax data with the underlying shipment.
• Error handling: query rows where PROCESS_STATUS is not complete or PROCESS_MESSAGE is populated to identify failed localized processing.

Related Objects

• RCV_TRANSACTIONS — joined on TRANSACTION_ID, PARENT_TRANSACTION_ID, and TAX_TRANSACTION_ID.
• RCV_SHIPMENT_HEADERS — joined on SHIPMENT_HEADER_ID.
• RCV_SHIPMENT_LINES — joined on SHIPMENT_LINE_ID.
• MTL_SYSTEM_ITEMS_B — joined on INVENTORY_ITEM_ID and ORGANIZATION_ID.
• HR_ALL_ORGANIZATION_UNITS — joined on ORGANIZATION_ID.
• HR_LOCATIONS_ALL — joined on LOCATION_ID.