Results for “jai_rcv_lines”

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

Overview

JAI_RCV_LINES is a table owned by the JA (Asia/Pacific Localizations) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores localization-related information for receipt lines processed through the Oracle Receiving application. The table extends the standard receiving data model to accommodate statutory and tax requirements specific to Asia/Pacific geographies, including excise invoicing, bill of entry (BOE) tracking, and tax modification flags. Records in this table correspond one-to-one with the JD Edwards-independent receiving transaction lines that require localization treatment, most notably in the Indian localization (JA_IN) context where excise, VAT, and GST compliance drive additional data capture.

Mined from its foreign key structure, a heuristic Data Vault classification of this object suggests it functions as a link table. It connects the shipment header, shipment line, receiving transaction, inventory organization, inventory item, and purchase order line location dimensions into a single normalized relationship. This modeling suggestion is consistent with the table's 50 documented columns, of which the majority are flags and attributes supporting receiving-related localization workflows.

Key Information Stored

The surrogate primary key of JAI_RCV_LINES is SHIPMENT_LINE_ID, enforced through the JAI_RCV_LINES_PK constraint. A separate unique index, JAI_RCV_LINES_UK1, exists on TRANSACTION_ID, which serves as a business-key candidate and confirms that each receiving transaction maps to at most one localization row. SHIPMENT_HEADER_ID provides the parent shipment reference, while RECEIPT_NUM and QTY_RECEIVED carry the human-readable receipt identity and received quantity respectively.

• SHIPMENT_LINE_ID — surrogate primary key linking to the originating shipment line.
• TRANSACTION_ID — business-key candidate; identifies the receiving transaction and is uniquely enforced by JAI_RCV_LINES_UK1.
• SHIPMENT_HEADER_ID — parent shipment header reference.
• LINE_LOCATION_ID — purchase order line location being received against.
• ORGANIZATION_ID — inventory organization where the receipt is recorded.
• INVENTORY_ITEM_ID — item received.
• RECEIPT_NUM and QTY_RECEIVED — receipt number and quantity received.
• BOE_NUMBER and BOE_APPLIED_FLAG — bill of entry number and application status for customs/localization processing.
• EXCISE_INVOICE_NO and EXCISE_INVOICE_DATE — excise invoice reference and date.
• GST_INVOICE_NO and GST_INVOICE_DATE — GST invoice reference and date.
• TAX_AMOUNT, TAX_MODIFIED_FLAG, CLAIM_MODVAT_FLAG — tax amount and modification/claim indicators.
• Process flags — PROCESS_RECEIVING, PROCESS_DELIVERY, PROCESS_MODVAT, PROCESS_RG, PROCESS_RTR, PROCESS_RTV, PROCESS_THIRD_PARTY_INV, PROCESS_POPULATE_CENVAT — govern which localization routines have executed against the line.

Common Use Cases and Queries

Operations and reporting teams query JAI_RCV_LINES to reconcile excise, VAT, and GST documentation against physical receipts. A typical join retrieves receipt details alongside item and organization context:

SELECT j.receipt_num, j.qty_received, j.boe_number,
       j.excise_invoice_no, j.tax_amount
FROM   ja.jai_rcv_lines j
WHERE  j.organization_id = :org_id
AND    j.process_modvat = 'Y';

Common scenarios include tracking pending bill of entry applications (BOE_APPLIED_FLAG), auditing tax-modified receipt lines (TAX_MODIFIED_FLAG), and validating that excise and GST invoice data align with receiving transactions. Because TRANSACTION_ID is uniquely indexed, lookup by transaction is a preferred filtering path for point queries and concurrent program joins.

Related Objects

The table's foreign keys tie it firmly into the Oracle Receiving and Procurement data model:

• RCV_SHIPMENT_HEADERS via SHIPMENT_HEADER_ID.
• RCV_SHIPMENT_LINES via SHIPMENT_LINE_ID.
• RCV_TRANSACTIONS via TRANSACTION_ID — the transaction-level anchor.
• HR_ALL_ORGANIZATION_UNITS via ORGANIZATION_ID.
• MTL_SYSTEM_ITEMS_B via INVENTORY_ITEM_ID and ORGANIZATION_ID.
• PO_LINE_LOCATIONS_ALL via LINE_LOCATION_ID.