Search Results insert_inspection

Overview

The APPS.RCV_INSPECTION_GRP package is a Group-type PL/SQL API within Oracle E-Business Suite Receiving. It provides the programmatic entry point for creating inspection transactions — the record of receipt inspections, and in particular the accept or reject decisions that result from them. Its documented purpose is to insert an inspection transaction into the receiving transaction interface table, RCV_TRANSACTIONS_INTERFACE, from which the receiving transaction processor subsequently validates and processes the record into the receiving transaction tables. This enables inspection outcomes to be captured through a supported API rather than by direct table manipulation, preserving the integrity of the receiving transaction model.

The package is declared AUTHID CURRENT_USER and is owned by the APPS schema. Its current documented version is 1.1; version 1.1 added LPN context through the lpn_id and transfer_lpn_id parameters.

Key Procedures and Functions

The package exposes a single documented procedure:

• INSERT_INSPECTION — Inserts an inspection transaction into the PO interface table, thereby recording the inspection result for a received quantity. The procedure accepts a standard API control set (API version, initialization of the message list, commit flag, validation level, and audit columns such as created_by, last_updated_by, and last_update_login), together with the business context of the inspection. That business context includes the employee performing the inspection, the transaction group identifier, the parent transaction identifier, and the transaction type, which designates the result as either Reject or Accept. Processing behaviour is governed by the processing mode (ONLINE, IMMEDIATE, or BATCH). Quantities are expressed through the quantity and uom parameters.
• Optional attributes may be supplied to enrich the transaction, including the quality code, transaction date, comments, reason identifier, vendor lot, source LPN, and transfer LPN, along with the QA collection identifier.
• The procedure returns the standard concurrent-style API outputs: p_return_status (with S for success and U for unsuccess), p_msg_count, and p_msg_data, allowing callers to inspect errors without relying on exceptions alone.

Tables Accessed

The primary write target is RCV_TRANSACTIONS_INTERFACE, the staging table through which the receiving transaction processor creates and validates receiving activity. The package's broader reference footprint, established through APPS synonyms, includes RCV_TRANSACTIONS, RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES, and RCV_SUPPLY, which hold the shipment, receipt, and supply detail against which an inspection is validated. Purchase order context is resolved from PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, and PO_REQUISITION_HEADERS_ALL. Item validation uses MTL_SYSTEM_ITEMS and MTL_CUSTOMER_ITEMS. Order management context, where applicable, is drawn from OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL.

Usage Notes

This API is classified as a Group API and is referenced by three other packages, indicating that it is normally called indirectly — typically through the Oracle iProcurement or receiving inspection user interfaces, through related receiving APIs, or by custom extensions and concurrent programs that automate inspection decisions. Callers should execute it within the standard API framework, checking p_return_status and the message stack, and should only request commit when the calling process owns the transaction boundary. Because records are staged in RCV_TRANSACTIONS_INTERFACE, the receiving transaction processor must be run (or the appropriate processing mode selected) before the inspection is reflected in RCV_TRANSACTIONS. The same behaviour applies in both the 12.1.1 and 12.2.2 releases.