Search Results derive_shipment_header_id

Overview

APPS.RCV_ROI_HEADER is a VALID PL/SQL package in the Oracle E-Business Suite Receiving (RCV) module. Its name follows the "ROI" (Receiving Open Interface) naming convention, and it functions as the header-level processing engine for inbound receiving transactions submitted through the Receiving Open Interface. The package is responsible for deriving, defaulting, and validating header information for the various receiving flows supported by Oracle EBS: vendor (purchasing), customer (RMA/return), internal (inter-org and intransit), and internal order headers. Once header attributes are established, the package records the corresponding rows in the receiving interface tables for downstream validation and processing by the receiving transaction processor. This package is available in both Oracle EBS 12.1.1 and 12.2.2, and is classified as an OTHER API — that is, it is an internal implementation package rather than a formally published public API for custom development.

Key Procedures and Functions

The ETRM metadata documents 36 procedures and functions. The principal entry points follow a consistent header-processing pattern for each transaction class:

• PROCESS_HEADER — the top-level driver that orchestrates header processing across the supported flows.
• PROCESS_VENDOR_HEADER, PROCESS_CUSTOMER_HEADER, PROCESS_INTERNAL_HEADER, PROCESS_INTERNAL_ORDER_HEADER — flow-specific entry points for supplier receipt, customer return, inter-org, and internal order transactions, respectively.
• DERIVE_VENDOR_HEADER, DERIVE_CUSTOMER_HEADER, DERIVE_INTERNAL_HEADER, DERIVE_INTERNAL_ORDER_HEADER — derive header values from source documents and defaults.
• DEFAULT_VENDOR_HEADER, DEFAULT_CUSTOMER_HEADER, DEFAULT_INTERNAL_HEADER, DEFAULT_INTERNAL_ORDER_HEADER — populate default column values on the header interface records.
• VALIDATE_VENDOR_HEADER, VALIDATE_CUSTOMER_HEADER, VALIDATE_INTERNAL_HEADER, VALIDATE_INTERNAL_ORDER_HEADER — validate derived/defaulted header attributes against reference data.
• DERIVE_VENDOR_INFO — derives supplier-related header details.
• PROCESS_CANCELLATION and INSERT_CANCELLED_ASN_LINES — handle cancellation flows, including insertion of cancelled ASN lines.

All procedures are header-scoped; line-level work is delegated to companion packages such as RCV_ROI_TRANSACTION.

Tables Accessed

The package reads and writes the interface and base receiving tables via APPS synonyms:

• RCV_HEADERS_INTERFACE — the primary staging table where derived header records are inserted and updated.
• RCV_TRANSACTIONS_INTERFACE and RCV_TRANSACTIONS_INTERFACE_S — transaction-level interface staging, written as part of header processing and cancellation handling.
• RCV_SHIPMENT_HEADERS and RCV_SHIPMENT_LINES — used to resolve existing receipt/ASN shipment data.
• PO_HEADERS and PO_HEADERS_ALL — read for supplier and purchase order header validation and derivation.

Usage Notes

RCV_ROI_HEADER is invoked internally by the Receiving Open Interface processor — typically the Receiving Transaction Processor concurrent program or the ROI preprocessor — rather than being called directly by users. It is referenced by RCV_ROI_PREPROCESSOR, RCV_ROI_TRANSACTION, RCV_ROI_HEADER_COMMON, and itself, and it depends on RCV_ROI_PREPROCESSOR. Because the package is classified as an OTHER API rather than a public API, direct invocation from custom code is not supported. Custom integrations should insert rows into RCV_HEADERS_INTERFACE and RCV_TRANSACTIONS_INTERFACE and submit the standard Receiving Transaction Processor; this package then executes the derive, default, and validate logic automatically. Any troubleshooting of stuck or errored interface records should therefore examine the RCV_HEADERS_INTERFACE error columns produced by this package and its dependents.