Search Results csd_receive_util




Overview
Explore in AI Chat

Overview

CSD_RECEIVE_UTIL is a utility package owned by APPS in Oracle E-Business Suite, classified by ETRM as a UTIL (utility) API rather than a business-flow API. Its principal role is to support the Receiving Open Interface by validating input and populating the RCV interface tables, most notably RCV_TRANSACTIONS_INTERFACE and RCV_HEADERS_INTERFACE. It exposes a structured, strongly typed contract for callers that need to submit receiving transactions programmatically — internal orders, service or depot transactions, and custom integrations — without hand-coding the low-level column mappings required by the receiving API.

The package's most recognisable construct is the rcv_tbl_type associative array, indexed by BINARY_INTEGER and composed of elements of the record type rcv_rec_type. rcv_rec_type encapsulates the complete attribute set of a receiving transaction line: sourcing and destination identifiers (customer, customer site, employee, inventory item, item revision, from and to organization), quantity and unit of measure, destination type code, subinventory and locator, requisition and order references, transaction and expected receipt dates, shipping attributes, lot and serial numbers, and internal order shipment attributes. This record/table pair is the mechanism through which callers hand data to the package, which then validates it and drives the receiving interface.

Key Procedures and Functions

  • IS_AUTO_RCV_AVAILABLE — Determines whether automatic receiving is enabled for the given context, allowing callers to decide between automatic and manual/interface-driven receipt creation.
  • VALIDATE_RCV_INPUT — Performs validation over the supplied receiving input, checking the record and table content for the consistency and completeness required before the data is written to the RCV interface tables.
  • CHECK_RCV_ERRORS — Retrieves and evaluates errors raised during processing of the receiving interface data, typically by inspecting PO_INTERFACE_ERRORS and the RCV interface error columns, so that callers can report failures and take corrective action.
  • GET_EMPLOYEE_ID — Resolves the employee identifier associated with the receiving transaction, derived from the supplied or session context, for population of the interface record.
  • GET_RCV_ITEM_PARAMS — Returns the item-related receiving parameters required for a valid transaction, resolving control codes and item attributes from the item master and related setup tables.

Tables Accessed

The package reads and writes the Receiving Open Interface tables RCV_TRANSACTIONS_INTERFACE and RCV_HEADERS_INTERFACE, and reads RCV_PARAMETERS for receiving system parameters. Error handling draws on PO_INTERFACE_ERRORS. Item and inventory validation references MTL_SYSTEM_ITEMS, MTL_SYSTEM_ITEMS_B, MTL_ITEM_CATEGORIES, MTL_SECONDARY_INVENTORIES and MTL_SERIAL_NUMBERS. Interorganization and internal order processing references MTL_INTERORG_PARAMETERS and OE_ORDER_LINES_ALL. FND_USER provides the session user context used in the WHO columns and, indirectly, employee resolution.

Usage Notes

CSD_RECEIVE_UTIL is an internal utility, not an end-user API. It is invoked from forms and concurrent programs in the service, depot repair and internal order flows, and it is referenced by three other packages within the EBS codebase; custom code should therefore model its call patterns on those existing callers rather than treating the package as a published, supported interface. Because the package ultimately stages data in RCV_TRANSACTIONS_INTERFACE, its output is only fully applied when the Receiving Open Interface concurrent program or Receiving Transaction Processor runs. Callers must consequently follow up with CHECK_RCV_ERRORS to confirm that the staged records have processed successfully, and must not assume that a clean VALIDATE_RCV_INPUT result alone guarantees a completed receipt. The package is present and functionally consistent in both 12.1.1 and 12.2.2, with the header comment carrying an older file revision and the rcv_rec_type definition including a noted fix for lot number length, reflecting the package's long-established, stable role in the receiving interface toolchain.