Search Results vendor_lot_num




Overview
Explore in AI Chat

Overview

The RCV_SERIAL_CORRECTION_V view is an Oracle E-Business Suite database object owned by the APPS schema and classified under the PO – Purchasing product family. It is shipped with a status of VALID and is described in the data dictionary as "Retrofitted," indicating that its definition was migrated or preserved during an upgrade to the 12.1.1 / 12.2.2 code levels rather than being newly introduced. Functionally, the view exposes serial number correction data captured within the receiving and inventory transaction stream. It presents a flattened, read-only projection over the serial transaction records maintained by Oracle Receiving, allowing correction activity—such as adjustments, reassignments, or reversals of previously recorded serial numbers—to be reported on without requiring consumers to understand the full internal structure of the base transaction table.

Because the view is defined as a simple projection (a SELECT … FROM RCV_SERIAL_TRANSACTIONS with a column alias), it carries no additional filtering, joins, or aggregation logic. This makes it behave as a lightweight reporting surface: queries against it are effectively direct reads of the base serial transaction table, and the view acts purely as an abstraction layer that presents recognizable column names such as SERIAL_NUMBER in place of the underlying SERIAL_NUM.

Underlying Base Objects

The view is defined over a single documented base object: RCV_SERIAL_TRANSACTIONS, referenced through a synonym in the APPS schema. There are no joins to shipment headers, lots, or item masters within the view text itself. Consequently, all transactional attributes—including serial numbers, lot numbers, transaction dates, and correction references—must be resolved from RCV_SERIAL_TRANSACTIONS alone. Where additional context is required (for example, item information, shipment line details, or receipt numbers), the view must be joined to the relevant parent tables such as RCV_SHIPMENT_LINES or the corresponding receipt and transaction entities.

Key Columns

Common Use Cases and Queries

Typical scenarios include reconciling serial number corrections against original receipt transactions, auditing which correction transactions were generated for a given source transaction, and extracting serial correction activity for a specific shipment line. A representative query filtering by the searched attribute is:

SELECT serial_transaction_type, serial_number, usage_status_code,
       transaction_date, source_transaction_id, correction_transaction_id
 FROM apps.rcv_serial_correction_v
 WHERE serial_transaction_type = :p_type;

To trace a correction back to its originating transaction and forward to the correction produced, join SOURCE_TRANSACTION_ID and CORRECTION_TRANSACTION_ID against the base transaction table. For shipment-level reporting, join SHIPMENT_LINE_ID to RCV_SHIPMENT_LINES. Because the view performs no filtering, date-range and status predicates should be applied explicitly by the calling report or concurrent program.