Search Results derive_from_org_info

Overview

APPS.RCV_ROI_HEADER_COMMON is a Receiving Open Interface (ROI) utility package in Oracle E-Business Suite. It encapsulates the header-level defaulting, derivation, and validation logic required to process inbound receiving transactions submitted through the Receiving Open Interface. The package operates against the RCV_HEADERS_INTERFACE staging table and its related interface structures, transforming a partially populated header record into a complete, validated record suitable for downstream processing by the ROI preprocessor and the receiving transaction processor.

The package is classified under the OTHER API category, indicating it is an internal implementation component rather than a formally published public API. It works in close coordination with RCV_ROI_PREPROCESSOR, whose header_rec_type record structure is passed by reference (IN OUT NOCOPY) between the documented procedures. The package is referenced by eight other packages, reflecting its role as a shared header-processing engine.

Key Procedures and Functions

The documented procedures fall into three functional groups: derivation, defaulting, and validation.

• Derivation procedures — DERIVE_SHIP_TO_ORG_INFO, DERIVE_FROM_ORG_INFO, DERIVE_LOCATION_INFO, DERIVE_PAYMENT_TERMS_INFO, DERIVE_RECEIVER_INFO, DERIVE_SHIPMENT_HEADER_ID, and DERIVE_UOM_INFO populate header attributes from related reference data. DERIVE_UOM_INFO additionally operates on the cascaded transaction table type used by the preprocessor.
• Defaulting procedures — DEFAULT_LAST_UPDATE_INFO, DEFAULT_CREATION_INFO, DEFAULT_ASN_TYPE, DEFAULT_SHIPMENT_HEADER_ID, DEFAULT_RECEIPT_INFO, DEFAULT_SHIP_TO_LOCATION_INFO, and DEFAULT_SHIP_FROM_LOC_INFO apply system defaults and audit columns to the header record.
• Validation procedures — VALIDATE_TRX_TYPE, VALIDATE_SHIPMENT_DATE, VALIDATE_EXPECTED_RECEIPT_DATE, VALIDATE_RECEIPT_NUM, VALIDATE_SHIP_TO_ORG_INFO, and VALIDATE_FROM_ORG_INFO confirm that header values are consistent with receiving setup and transactional rules before the record is passed to the transaction processor. VALIDATE_SHIP_TO_ORG_INFO and VALIDATE_FROM_ORG_INFO are the logical counterpart to the corresponding derivation procedures.

A record type, common_default_record_type, is declared in the package specification and mirrors key columns of RCV_TRANSACTIONS_INTERFACE such as destination_type_code, transaction_type, and processing_mode_code.

Tables Accessed

The package reads reference and setup data from a broad set of APPS synonyms. Receiving and purchasing tables — RCV_PARAMETERS, PO_HEADERS, PO_LINES, PO_LINES_ALL, PO_LINE_LOCATIONS, and PO_SYSTEM_PARAMETERS — supply shipment, receipt, and sourcing context. MTL_SYSTEM_ITEMS, MTL_ITEM_REVISIONS, MTL_RELATED_ITEMS, and MTL_UNITS_OF_MEASURE provide item, revision, and unit-of-measure validation data, which is directly relevant to item revision validation during header processing. MTL_PARAMETERS and HR_LOCATIONS_ALL supply organization and location defaults. OE_DROP_SHIP_SOURCES supports drop-ship derivation logic. RCV_HEADERS_INTERFACE and RCV_TRANSACTIONS_INTERFACE are the interface tables whose records are ultimately populated and validated.

Usage Notes

RCV_ROI_HEADER_COMMON is not intended for direct invocation by end users. It is called internally by the Receiving Open Interface preprocessor during header-level preprocessing, for example when the Receiving Transaction Manager or the Receiving Open Interface concurrent program processes staged interface records. Custom integrations that stage records directly into RCV_HEADERS_INTERFACE typically rely on the standard ROI submission path rather than calling this package directly, because its procedures expect the preprocessor's header_rec_type and cascaded transaction table types. Developers extending ROI logic should replicate its validation semantics rather than bypassing them, since downstream receipt creation assumes that header attributes such as ship-to organization, from-organization, receipt number, and dates have already been derived and validated. In the context of revision validation, item revision checks referenced through MTL_ITEM_REVISIONS should be regarded as part of the broader header validation flow governed by this package.