Search Results lot_num




Overview
Explore in AI Chat

Overview

RCV_LOTS_SUPPLY is a receiving transaction table owned by the PO schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the lot-level supply detail associated with receiving transactions, capturing quantities, expiration data, and reason information for lots processed during the receiving flow. Each row links a lot number and supply type code to either a shipment line or a receiving transaction, making the table a convergence point between the inbound shipment record and the accounting/inventory transaction record.

Within the ETRM metadata, the heuristic Data Vault classification for this object is link. This is a modeling suggestion derived from the foreign key structure: the table does not represent an independent business entity, but rather an association between RCV_SHIPMENT_LINES and RCV_TRANSACTIONS, qualified by lot-level attributes such as SUPPLY_TYPE_CODE and LOT_NUM. Treating it as a link highlights its role in resolving many-to-many or many-to-one relationships between receiving transactions and shipment lots.

Key Information Stored

The table contains 20 documented columns. The most operationally significant are listed below.

  • SUPPLY_TYPE_CODE — Classifies the supply context for the lot record. It participates in both unique keys, meaning supply type is a defining dimension of each row.
  • LOT_NUM — The lot number being received. Also present in both unique keys, making it a core business key component.
  • SHIPMENT_LINE_ID — Foreign key to RCV_SHIPMENT_LINES. Identifies the shipment line against which the lot supply was received. Part of unique key RCV_LOTS_SUPPLY_UK01.
  • TRANSACTION_ID — Foreign key to RCV_TRANSACTIONS. Identifies the receiving transaction that generated the lot supply record. Part of unique key RCV_LOTS_SUPPLY_UK02.
  • QUANTITY and PRIMARY_QUANTITY — The received quantity in the transaction unit of measure and in the primary inventory unit of measure, respectively.
  • SECONDARY_QUANTITY — The quantity expressed in the secondary unit of measure, used where dual UOM tracking is enabled.
  • EXPIRATION_DATE — Lot expiration date captured at receiving, relevant for shelf-life controlled items.
  • SUBLOT_NUM — Optional sublot identifier, allowing finer granularity than LOT_NUM alone.
  • REASON_CODE and REASON_ID — Reason identifiers associated with the lot supply record, typically used for returns, rejections, or adjustments.
  • LAST_UPDATE_DATE, CREATION_DATE, LAST_UPDATED_BY, CREATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns.
  • REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program context columns identifying the job that created or updated the row.

No single surrogate primary key is documented. Instead, two unique key constraints serve as business-key candidates: RCV_LOTS_SUPPLY_UK01 (SUPPLY_TYPE_CODE, SHIPMENT_LINE_ID, LOT_NUM) and RCV_LOTS_SUPPLY_UK02 (SUPPLY_TYPE_CODE, TRANSACTION_ID, LOT_NUM). These reflect the dual linkage of each row to shipment and transaction.

Common Use Cases and Queries

The table is commonly queried to reconcile received lot quantities against shipment lines, to trace which transaction generated a given lot supply record, and to report on expiring or expired lots. A typical reconciliation query joins RCV_LOTS_SUPPLY to RCV_SHIPMENT_LINES on SHIPMENT_LINE_ID to compare received lot quantities to the shipped quantity. A traceability query joins RCV_LOTS_SUPPLY to RCV_TRANSACTIONS on TRANSACTION_ID to retrieve transaction type, date, and source document context. Filtering by SUPPLY_TYPE_CODE isolates records for a particular supply scenario, which is useful when generating lot-level receiving reports or auditing returns and rejections via REASON_CODE.

Related Objects

  • RCV_SHIPMENT_LINES — Referenced by RCV_LOTS_SUPPLY.SHIPMENT_LINE_ID. Provides the expected shipment quantity and item context.
  • RCV_TRANSACTIONS — Referenced by RCV_LOTS_SUPPLY.TRANSACTION_ID. Provides the receiving transaction header information.
  • RCV_LOT_TRANSACTIONS and lot-level inventory tables — Related by lot number for downstream inventory lot tracking.
  • MTL_LOT_NUMBERS — Inventory lot master, joined on LOT_NUM for lot attribute validation.
  • Receiving open interface and correction APIs (RCV_HEADERS_INTERFACE, RCV_TRANSACTIONS_INTERFACE) — Consume similar structures when lots are created through interface processing.