Search Results default_customer_site_info

Overview

APPS.RCV_RMA_HEADERS is a PL/SQL package that supports the processing of Return Material Authorization (RMA) receipt headers within Oracle E-Business Suite Release 12.1.1 and 12.2.2. It forms part of the Receiving (RCV) module's public and internal API infrastructure, providing the procedural logic required to derive, default, validate, and persist RMA header information during receipt creation. The package is declared with AUTHID CURRENT_USER, meaning its procedures execute with the privileges of the invoking user rather than the package owner, which is consistent with standard EBS API security conventions.

The package is classified in the ETRM repository with a classification of OTHER and a package header dated 2008, indicating a long-standing, stable component of the receiving stack that predates the 12.2 online-patching model but remains present in the 12.2.2 codebase. Its central data structure is the header record type defined by the RCV_ROI_PREPROCESSOR package, through which all header-level processing is passed.

Key Procedures and Functions

The package exposes a documented set of thirteen procedures. The core public interface consists of four procedures, each accepting an IN OUT NOCOPY parameter of type rcv_roi_preprocessor.header_rec_type:

• DERIVE_RMA_HEADER — populates header attributes that can be inferred from other data on the record, rather than being entered directly by the user.
• DEFAULT_RMA_HEADER — applies default values to the header record, including sourcing defaults from related customer, transaction, and shipment information.
• VALIDATE_RMA_HEADER — performs header-level validation, invoking the more granular validation routines described below.
• INSERT_RMA_HEADER — writes the completed and validated RMA header record to the underlying receiving tables.

The remaining documented procedures are private helper routines that support the four public entry points. DERIVE_CUSTOMER_INFO and DERIVE_CUSTOMER_SITE_INFO resolve customer and customer site attributes. DEFAULT_CUSTOMER_INFO, DEFAULT_CUSTOMER_SITE_INFO, DEFAULT_TRX_INFO, and DEFAULT_SHIPMENT_NUM apply defaults for the customer, customer site, transaction, and shipment number fields respectively. VALIDATE_RECEIPT_SOURCE_CODE, VALIDATE_CUSTOMER_INFO, and VALIDATE_CUSTOMER_SITE_INFO perform the corresponding validation checks. Together these helpers enforce consistency across the RMA header before insertion.

Tables Accessed

The package references three tables through APPS synonyms. HZ_CUST_ACCOUNTS and HZ_PARTIES are accessed by the customer-related derive, default, and validate procedures to resolve and verify the customer account and party associated with the return. RCV_SHIPMENT_HEADERS is referenced during header processing and, most notably, by the INSERT_RMA_HEADER procedure that persists the RMA header record. The use of HZ_ tables reflects the Trading Community Architecture (TCA) model that underpins customer data in Release 12.

Usage Notes

RCV_RMA_HEADERS is an internal code layer rather than a standalone concurrent program. It is typically invoked from the receiving forms and from the RCV_ROI_PREPROCESSOR interface, which drives header-level processing for RMA receipts. Custom code and extensions that need to create or manipulate RMA receipt headers should call the public procedures in the sequence derive, default, validate, then insert, passing the shared header record type. The package is referenced by one other documented package, confirming its role as a supporting component within the receiving preprocessor framework. Because the procedures are sensitive to the order of derivation, defaulting, and validation, callers should not invoke INSERT_RMA_HEADER without first completing the earlier stages.