Search Results insert_rcv_txn_interface




Overview

POR_RCV_ORD_SV is an Oracle E-Business Suite PL/SQL specification package owned by the APPS schema. It provides the grouping and interface-population logic used during receiving of purchase order and internal requisition transactions. Specifically, the package accepts flat arrays of receipt attributes — purchase order header IDs, line location IDs, quantities, units of measure, items, organizations, distributions, comments, packing slips, and waybills — and applies grouping and splitting rules to convert them into discrete receiving transaction lines. Those grouped lines are then inserted into the receiving transaction interface for subsequent processing by the standard receiving transaction processor.

The package is classified as OTHER in the ETRM metadata, reflecting that it is an internal service component rather than a published public API. It is referenced by two other packages, indicating that the receiving forms and related processing logic depend on it to normalize incoming receipt data before submission.

Key Procedures and Functions

  • GROUP_PO_TRANSACTION — Function that applies grouping logic to purchase-order-based receipt lines. It accepts arrays of PO header, line location, quantity, UOM, item, organization, and distribution data along with a group ID, caller, and descriptive attributes, and splits the input into transaction lines suitable for the receiving transaction interface.
  • GROUP_INTERNAL_TRANSACTION — Function that performs equivalent grouping logic for internal requisition receipts, keyed on requisition line identifiers rather than PO attributes.
  • INSERT_RCV_TXN_INTERFACE_IR — Procedure that inserts internal requisition receipt records into the receiving transaction interface.
  • INSERT_RCV_TXN_INTERFACE — The procedure named in the user's search. It inserts grouped purchase order receipt lines into RCV_TRANSACTIONS_INTERFACE, making them available to the receiving transaction processor. This is the counterpart to the internal requisition variant.
  • PROCESS_TRANSACTIONS — Procedure that drives processing of the transactions staged by the insert routines.
  • CREATE_RCV_SHIPMENT_HEADERS — Procedure that creates shipment header records to which the interface transactions are associated.
  • CALL_TXN_PROCESSOR — Procedure that invokes the transaction processor for submitted groups.
  • CHECK_GROUP_ID — Procedure that validates a group identifier prior to processing.
  • CANCEL_PENDING_NOTIFS and NOTIF_IS_ACTIVE — Notification-handling routines used to manage pending and active workflow notifications tied to receipt processing.

Tables Accessed

The package reads and writes the core receiving and purchasing tables. RCV_TRANSACTIONS_INTERFACE and its sequence RCV_TRANSACTIONS_INTERFACE_S are the primary write targets, receiving the grouped lines. RCV_SHIPMENT_HEADERS and RCV_SHIPMENT_HEADERS_S support shipment header creation, while RCV_SHIPMENT_LINES holds associated line detail and RCV_TRANSACTIONS holds posted transaction history. PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, and PO_DISTRIBUTIONS_ALL provide the purchase order context required for grouping and validation. PO_INTERFACE_ERRORS captures errors during interface population. MTL_SYSTEM_ITEMS and MTL_UNITS_OF_MEASURE supply item and UOM reference data, RCV_PARAMETERS supplies receiving system options, and FND_USER is used for user context.

Usage Notes

POR_RCV_ORD_SV is typically invoked indirectly, by Oracle Receiving forms and related concurrent programs, rather than being called directly by end users. Custom code that needs to stage receipts programmatically should prefer the documented Receiving open interfaces and public APIs; direct calls into POR_RCV_ORD_SV require correct population of the array parameters, a valid group ID, and a caller string, and should be followed by the processor calls within the same package. Because the package is an internal service, signatures may change between releases, so code should be validated against the target EBS version (12.1.1 or 12.2.2) prior to deployment.