Search Results rcv_824_insert

Overview

APPS.RCV_824_SV is a server-side PL/SQL package in Oracle E-Business Suite that supports outbound Electronic Data Interchange (EDI) processing for receiving transactions. The package is part of the Receiving (RCV) application module and is closely associated with the generation of the EDI 824 transaction set, the "Application Advice" message used to report the acceptance, rejection, or acknowledgement of previously transmitted EDI documents. Within the Oracle EBS integration architecture, RCV_824_SV acts as a thin wrapper layer that invokes the underlying EDI application programming interfaces required to build and stage 824 transaction data.

The package is classified under the OTHER API category in the ETRM repository, indicating that it is not a public, fully documented open interface but rather an internal utility used by Oracle's seeded integration flows. Its header revision (120.2, dated 2005) reflects long-standing stability across releases, and the object is present in both 12.1.1 and 12.2.2 environments. As the name suggests, its primary responsibility is to assemble an 824 acknowledgement record set from interface data supplied by the caller and hand it to the EDI subsystem.

Key Procedures and Functions

ETRM documents two procedures on this package, both named RCV_824_INSERT. They are overloads distinguished by the data type of their interface header parameter.

• RCV_824_INSERT (X_Interface_Header IN RCV_ROI_PREPROCESSOR.header_rec_type, X_Type IN VARCHAR2) — Accepts a header record typed against the RCV_ROI_PREPROCESSOR record structure. RCV_ROI_PREPROCESSOR is the receiving open interface preprocessor package, so this overload is designed to be called from within the inbound receiving preprocessing pipeline where acknowledgement data is derived directly from open interface staging rows. The X_Type parameter carries the transaction or message type context that governs how the acknowledgement is constructed.
• RCV_824_INSERT (X_Interface_Header IN RCV_SHIPMENT_HEADER_SV.headerrectype, X_Type IN VARCHAR2) — The second overload accepts a header record defined by RCV_SHIPMENT_HEADER_SV, the shipment header server-side view/API record type. This variant is invoked when calling code already operates on shipment header data structures, allowing receipt and shipment processing logic to raise an 824 acknowledgement without reshaping the header record.

Both procedures share the same purpose: to evaluate incoming interface data and call the appropriate EDI APIs so that an outbound 824 application advice record is created. They do not return a value; success or failure is communicated through the standard EBS exception and message conventions.

Tables Accessed

The package operates against the following documented tables, referenced through APPS synonyms:

• MTL_SYSTEM_ITEMS_KFV — The key flexfield view over inventory items, used to resolve item identifiers and descriptive attributes for the transaction lines being acknowledged.
• PO_HEADERS and PO_LINES — Purchasing document headers and lines, providing the source document context (purchase order number, line, and revision) against which the 824 acknowledgement is reported.
• RCV_SHIPMENT_LINES — Receiving shipment line detail, supplying receipt, quantity, and shipment information that populates the acknowledgement payload.
• RCV_TRANSACTIONS_INTERFACE — The receiving transactions open interface table, which stages receipt and delivery transactions awaiting validation and processing.
• PO_INTERFACE_ERRORS — The purchasing interface error table, used to record and retrieve validation failures associated with the interface rows being processed.

Collectively these tables supply the document reference data, item details, and error context needed to build an accurate 824 message.

Usage Notes

RCV_824_SV is not exposed through an end-user form. It is invoked programmatically by other server-side packages; ETRM records two dependent packages that reference it, reflecting its role as a shared integration utility. Typical invocation occurs during receiving open interface processing, where RCV_ROI_PREPROCESSOR validates inbound receipt data and, upon detecting conditions requiring an outbound acknowledgement, calls RCV_824_INSERT to generate the 824. The RCV_SHIPMENT_HEADER_SV overload supports the same outcome when processing is driven from shipment header structures.

Because both overloads are confined to the package specification with no separate public API documentation, customizations that need to trigger 824 acknowledgements should call these procedures only through the seeded integration flows rather than directly. Developers extending receiving integrations should be aware that the package writes through standard EDI and receiving interface tables, so any direct invocation must respect the same commit and error-handling boundaries observed by the standard concurrent programs that drive receiving open interface processing.