Search Results out_op_info

Overview

APPS.RCV_CORE_S is a core receiving services package body within the Oracle E-Business Suite Receiving (RCV) module. It provides the foundational validation and derivation logic shared across receiving transactions, including the determination of valid destinations, receiving controls, and work-in-process referencing data. The package is classified as OTHER in the ETRM metadata, indicating it is not a public API surface in the conventional sense but an internal service layer consumed by higher-level receiving APIs and forms. Its principal responsibilities include validating ship-to locations, deliver-to locations, destination subinventories, destination organizations, and deliver-to persons against the transaction date, nulling defaults that are no longer active, and resolving default locators for inventory destinations. The header comment reflects the package lineage spanning multiple EBS releases, with the file version corresponding to RCVCOCOB.pls.

Key Procedures and Functions

The ETRM metadata documents fifteen procedures and functions, of which four are named in the excerpt:

• val_destination_info — Validates whether the ship-to location, deliver-to location, destination subinventory, destination organization, and deliver-to person specified as defaults on the purchase order remain active as of the transaction date. Inactive values are nulled out, and when an item's destination is inventory, the procedure looks up the default locator for the associated subinventory. It returns resolved IDs and codes through OUT NOCOPY parameters.
• OUT_OP_INFO — The procedure the user searched for; it returns operation-related output information used in receiving contexts, typically associated with WIP-referenced receipts where a receiving line must be tied back to a work order operation.
• GET_RECEIVING_CONTROLS — Retrieves receiving control settings that govern how receipt transactions are processed, drawing on the RCV_PARAMETERS configuration.
• NAME — A utility or naming function within the package.
• WIP_LINE_INFO — Returns work-in-process line information, supporting receipt transactions sourced against discrete or repetitive work orders.

Detailed parameter lists are not reproduced here; the documented behavior above reflects the package's role in destination validation and WIP reference resolution.

Tables Accessed

The package references fifteen tables via APPS synonyms, spanning master data and transaction data:

• BOM_DEPARTMENTS, WIP_ENTITIES, WIP_LINES, WIP_OPERATIONS — support WIP-referenced receiving, resolving work order lines and operations for receipt matching.
• MTL_ITEM_SUB_INVENTORIES, MTL_SECONDARY_INVENTORIES, MTL_SYSTEM_ITEMS, MTL_PARAMETERS — supply item, subinventory, and organization-level defaults and validation attributes.
• PO_DISTRIBUTIONS, PO_LINE_LOCATIONS, PO_LINE_LOCATIONS_ALL, PO_HISTORY_RECEIPTS — provide the purchasing context, including destination and deliver-to defaults and historical receipt references.
• RCV_PARAMETERS, RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES — hold receiving controls and the shipment line structures being validated.

Usage Notes

RCV_CORE_S is invoked indirectly by receiving forms, the Receiving Transactions and Receiving Open Interface concurrent programs, and higher-level receiving APIs such as RCV_HEADERS_INTERFACE and receiving transaction processors. Because it is referenced by fourteen other packages, modifications carry broad impact. The package honors the RCV_DEBUG_MODE profile option, writing debug output prefixed with 'po.plsql.RCV_CORE_S.' to the FND log when enabled. Customizations should avoid direct calls to internal procedures such as OUT_OP_INFO and instead use documented public receiving APIs, since parameter signatures and internal behavior may change between patch levels.