Search Results rcv_core_s




Overview
Explore in AI Chat

Overview

RCV_CORE_S is a core PL/SQL package in the APPS schema that centralizes fundamental receiving logic within Oracle E-Business Suite. It is classified as an "OTHER" API in the ETRM repository, meaning it is an internal utility rather than a publicly supported integration interface. The package provides shared services for receiving transactions, shipment header handling, receiving control retrieval, and the coordination of inbound material against both purchasing and work-in-process (WIP) activities. Because of its central role, RCV_CORE_S sits beneath a large family of receiving and purchasing packages, acting as a reusable foundation that higher-level transaction programs call rather than duplicate. The package is VALID across EBS 12.1.1 and 12.2.2, and it is referenced by fourteen other packages, indicating its broad internal footprint in the receiving and procurement flow.

Key Procedures and Functions

The documented interface includes fifteen procedures and functions. The notable entries are:

  • NAME — A utility function returning the package name, a common convention used for error logging and diagnostic trace messages.
  • GET_RECEIVING_CONTROLS — Retrieves receiving control settings from the receiving parameters, giving callers the business rules that govern receipt processing, such as control levels and enforcement options.
  • OUT_OP_INFO — Returns information about outside processing operations, supporting the linkage of purchased items to routing operations, particularly for WIP and job-related receipts.
  • WIP_LINE_INFO — Supplies work-in-process line details, enabling receiving logic to associate receipts with the appropriate WIP entities, lines, and operations.

These procedures operate together to supply the transactional context that upstream receiving programs require before validating and posting a receipt.

Tables Accessed

RCV_CORE_S accesses a defined set of base tables through APPS synonyms. Receiving-specific tables include RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES, and RCV_PARAMETERS, which hold shipment data and the receiving control configuration. Purchasing tables such as PO_LINE_LOCATIONS, PO_LINE_LOCATIONS_ALL, PO_DISTRIBUTIONS, PO_HISTORY_RECEIPTS, and PO_HISTORY_RECEIPTS support the link between receipts and their originating purchase orders. Inventory and item tables, including MTL_SYSTEM_ITEMS, MTL_PARAMETERS, MTL_SECONDARY_INVENTORIES, and MTL_ITEM_SUB_INVENTORIES, provide item and subinventory definitions used during receipt validation. Work-in-process tables such as WIP_ENTITIES, WIP_LINES, WIP_OPERATIONS, and BOM_DEPARTMENTS supply the manufacturing context for outside-processing and job-related receipts.

Usage Notes

RCV_CORE_S is not intended for direct customer invocation. It is invoked by higher-level receiving and purchasing packages including RCV_TRANSACTIONS_SV, RCV_TRANSACTION_SV, RCV_RECEIPTS_QUERY_SV, RCV_HEADERS_INTERFACE_SV, RCV_RMA_TRANSACTIONS, RCV_ROI_HEADER, and the PO_PDOI family of packages. These callers rely on RCV_CORE_S for control lookups, WIP and outside-processing detail, and shared shipment-header handling. Within the EBS form and concurrent program layer, its functionality is reached indirectly, for example through the Receiving form and receipt-processing concurrent programs. Custom code that performs receiving should call the supported receiving APIs rather than RCV_CORE_S directly, since the package is internal, unsupported, and its internal interfaces may change without notice.