Search Results rcv_rma_headers




Overview
Explore in AI Chat

Overview

APPS.RCV_RMA_HEADERS is a PL/SQL package body that supports Return Material Authorization (RMA) receipt processing within Oracle E-Business Suite Release 12.1.1 and 12.2.2. Its primary business function is to derive, default, validate, and persist RMA receipt header information received through the Receiving Open Interface (ROI). The package operates against the ROI preprocessor header record structure (rcv_roi_preprocessor.header_rec_type), which is passed by reference to each procedure using the IN OUT NOCOPY convention for efficiency.

The package is classified as OTHER in the ETRM documentation and contains thirteen documented procedures and functions. It forms part of the broader ASN (Advanced Shipment Notice) and RMA inbound processing flow, and it is referenced by one other package. The $Header tag confirms the source file RCVRMAHB.pls, version 120.3.12010000.2, last updated in 2010. The package supports a debug mode controlled by the ASN_DEBUG profile option through the asn_debug utility, emitting trace messages when debugging is enabled.

Key Procedures and Functions

  • DERIVE_RMA_HEADER — Central orchestrator for header derivation. It delegates to common ROI routines for ship-to organization, from organization, location, payment terms, and receiver information, then calls derive_customer_info and derive_customer_site_info for RMA-specific customer data.
  • DEFAULT_RMA_HEADER — Applies default values to the header record when sourced data is incomplete. This is the procedure associated with the search term "default_rma_header" and invokes default_cust and related defaults.
  • VALIDATE_RMA_HEADER — Performs header-level validation before the record is persisted.
  • INSERT_RMA_HEADER — Writes the fully derived, defaulted, and validated header record into the receiving tables.
  • DERIVE_CUSTOMER_INFO — Resolves customer identity for the RMA header.
  • DERIVE_CUSTOMER_SITE_INFO — Resolves customer site information associated with the return.
  • DEFAULT_CUSTOMER_INFO — Supplies default customer values when not provided in the source transaction.
  • DEFAULT_CUSTOMER_SITE_INFO — Supplies default customer site values.
  • DEFAULT_TRX_INFO — Defaults transaction-level metadata onto the header.
  • DEFAULT_SHIPMENT_NUM — Assigns or derives the shipment number.
  • VALIDATE_RECEIPT_SOURCE_CODE — Confirms the receipt source code is valid for RMA processing.
  • VALIDATE_CUSTOMER_INFO — Validates derived or defaulted customer data.
  • VALIDATE_CUSTOMER_SITE_INFO — Validates customer site data prior to insertion.

Tables Accessed

  • HZ_CUST_ACCOUNTS — Read to resolve the customer account associated with the RMA and to validate customer identity.
  • HZ_PARTIES — Read to resolve and validate party-level (customer) information used in derivation and defaulting logic.
  • RCV_SHIPMENT_HEADERS — Accessed to default shipment header attributes and derive shipment numbering during RMA header processing.

All three tables are referenced through APPS synonyms, consistent with standard EBS coding practices.

Usage Notes

RCV_RMA_HEADERS is invoked internally during Receiving Open Interface processing when inbound RMA data is preprocessed. It is not an end-user-facing form package; instead it is called by the ROI preprocessor framework and by one other package. Custom integrations that load RMA receipts via the Receiving Open Interface should not call these procedures directly. Developers extending or troubleshooting RMA receipt flows may enable the ASN_DEBUG profile option to capture trace output from derive_rma_header and default_rma_header. Because the package operates on the shared header_rec_type structure, any custom logic should respect the documented derive-default-validate-insert sequence.