Search Results rcv_824_sv




Overview

RCV_824_SV is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite. It supports the Receiving Open Interface (ROI) by constructing outbound 824 application advice messages that report processing errors encountered during receipt and receiving transaction processing. In EDI-enabled supply chain flows, the 824 transaction set communicates to a trading partner that a previously transmitted document — typically an 856 advance ship notice or a receipt — failed validation or could not be processed. This package assembles the header and line level error detail required to generate those advice transactions. The package header declares it as PACKAGE BODY RCV_824_SV AS, and the embedded source carries a header revision of 120.0.12000000.2, consistent with the 12.1.1 and 12.2.2 release code lines. Its API classification in the ETRM repository is OTHER, indicating it is an internal utility invoked by the receiving error notification framework rather than a publicly documented extension API.

Key Procedures and Functions

The ETRM metadata documents a single procedure, RCV_824_INSERT. This procedure is responsible for creating the line rows of the 824 application advice. Its signature receives a header record typed as RCV_ROI_PREPROCESSOR.header_rec_type alongside a type indicator, allowing the procedure to resolve the correct interface header context before writing error output. Internally, the procedure opens cursors that collect header-level and line-level errors and correlates them to the originating receipt data. A specific cursor gathers error rows where the interface line identifier is null, capturing conditions that apply to the entire interface header. A second cursor retrieves line-level errors joined from RCV_TRANSACTIONS_INTERFACE and PO_INTERFACE_ERRORS, returning item number, document number, document line number, barcode label, and both the error message and its translatable name. A third cursor, added in the original development cycle, joins RCV_SHIPMENT_LINES to purchasing document tables to enrich the advice with concatenated item segments, PO number, PO line number, and barcode label. Parameter lists are intentionally omitted here because the ETRM listing documents only the header record and type arguments.

Tables Accessed

The package reads and processes data from six documented tables, all accessed through APPS synonyms. PO_INTERFACE_ERRORS is the central error repository, supplying error messages and message names for both header and line conditions; the source notes that an NVL on the interface header identifier previously caused a full table scan and was removed for performance. RCV_TRANSACTIONS_INTERFACE provides the pending receiving transaction rows and their interface transaction identifiers used to join line errors. RCV_SHIPMENT_LINES supplies bar code label data and links to the purchase order line through PO_LINE_ID. PO_HEADERS and PO_LINES contribute the document number and line number attributes for the advice. MTL_SYSTEM_ITEMS_KFV, the key flexfield view over inventory items, provides concatenated item segments for readable item identification on the outbound message.

Usage Notes

RCV_824_SV is invoked as part of the Receiving Open Interface error handling path, not through a standalone concurrent program or form. When ROI processing detects errors, the receiving framework calls this package to build the detail rows that are subsequently emitted as an 824 application advice to the trading partner. The metadata indicates the package is referenced by two other packages, confirming it functions as a subordinate utility within the receiving integration stack. Customizations should avoid modifying this package directly; Oracle-supplied receiving code is patched during upgrades and the 824 generation logic is tightly coupled to the ROI preprocessor record structures. Because the source header includes a bug fix reference, sites on earlier code levels should verify they are on revision 120.0.12000000.2 or later to benefit from the corrected error cursor query plan.