Search Results source_document_code

Overview

The JAI_RCV_RECEIVE_LINES_V view resides in the APPS schema and belongs to the JA (Asia/Pacific Localizations) product family. It presents receiving transaction lines together with the corresponding Asia/Pacific localization attributes stored in JAI_RCV_LINES. The view is a real-time reporting and integration object: it joins standard Oracle Purchasing receiving entities (RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES, and RCV_TRANSACTIONS) with locally defined excise and claim data, producing a flat, denormalized result set that reporting tools, interfaces, and customizations can consume directly.

The view is especially relevant to users investigating the SOURCE_DOCUMENT_CODE column, which indicates the originating document type for a receiving line and is central to distinguishing receipt sources such as purchase orders versus internal requisitions and other transfer documents.

Underlying Base Objects

The documented referenced base objects are synonyms (typically pointing to the owning product tables) for JAI_RCV_LINES, RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES, and RCV_TRANSACTIONS. The join relationships in the view definition are:

• JAI_RCV_LINES joins to RCV_SHIPMENT_LINES on both SHIPMENT_HEADER_ID and SHIPMENT_LINE_ID.
• RCV_SHIPMENT_LINES joins to RCV_SHIPMENT_HEADERS on SHIPMENT_HEADER_ID.
• RCV_TRANSACTIONS joins to RCV_SHIPMENT_LINES on SHIPMENT_HEADER_ID and SHIPMENT_LINE_ID.

Transaction types are restricted so that only receiving activities are returned: RECEIVE, UNORDERED (where PO_HEADER_ID is null), and MATCH (where PO_HEADER_ID is not null). This restriction keeps the view focused on actual receipt events.

Key Columns

• SOURCE_DOCUMENT_CODE — code identifying the source document type (for example PO receipt, requisition, or transfer order) for the line; the primary search target for this article.
• SHIPMENT_HEADER_ID, SHIPMENT_LINE_ID — receiving identifiers linking header, line, and transactions.
• RECEIPT_NUM, SHIPMENT_NUM, SHIPPED_DATE, RECEIPT_DATE, TRANSACTION_ID — receipt and transaction-level identifiers and dates.
• PO_HEADER_ID, PO_LINE_ID, PO_LINE_LOCATION_ID, REQUISITION_LINE_ID — sourcing document references.
• ORGANIZATION_ID (from TO_ORGANIZATION_ID), FROM_ORGANIZATION_ID, LOCATION_ID, TO_SUBINVENTORY, DESTINATION_TYPE_CODE — destination and warehouse context.
• ITEM_ID, LINE_NUM, QUANTITY (as QUANTITY_RECEIVED), UOM, PRIMARY_UNIT_OF_MEASURE, SHIPMENT_UNIT_PRICE — item and quantity metrics.
• Localization attributes from JAI_RCV_LINES: EXCISE_INVOICE_NO, EXCISE_INVOICE_DATE, ONLINE_CLAIM_FLAG, RMA_TYPE.

Common Use Cases and Queries

Typical scenarios include receipt reconciliation by source document, excise invoice reporting, and feeding downstream AP or tax processes. To filter on the searched column:

SELECT RECEIPT_NUM, LINE_NUM, SOURCE_DOCUMENT_CODE,
       ITEM_ID, QUANTITY_RECEIVED, RECEIPT_DATE
FROM   APPS.JAI_RCV_RECEIVE_LINES_V
WHERE  SOURCE_DOCUMENT_CODE = :p_source_code
AND    RECEIPT_DATE BETWEEN :p_from AND :p_to;

To return localization excise detail for a specific receipt:

SELECT SHIPMENT_HEADER_ID, SHIPMENT_LINE_ID, EXCISE_INVOICE_NO,
       EXCISE_INVOICE_DATE, ONLINE_CLAIM_FLAG, RMA_TYPE
FROM   APPS.JAI_RCV_RECEIVE_LINES_V
WHERE  RECEIPT_NUM = :p_receipt_num;

Because columns such as QUANTITY and UOM are aliased in the column list (to QUANTITY_RECEIVED and UOM), queries should reference the documented interface column names rather than the underlying RCV_TRANSACTIONS attributes.