Search Results get_routing_step_id

Overview

RCV_RMA_TRANSACTIONS is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports Return Material Authorization (RMA) processing within the Receiving open interface. Its primary business function is to derive, default, and validate the attributes required to convert RMA return records into receiving transactions, ensuring that inbound RMA data supplied through the Receiving interface (RCV_HEADERS_INTERFACE) is reconciled against valid items, revisions, locations, reasons, and routing information before it is processed by the receiving transaction manager. In EBS 12.1.1 and 12.2.2 the package operates as a supporting component of the RMA/ROI inbound flow, working in conjunction with RCV_ROI_PREPROCESSOR and the RCV_SHIPMENT_OBJECT_SV and RCV_SHIPMENT_LINE_SV service packages. It is classified as an OTHER API, meaning it is not a published open interface in the traditional sense but is relied upon internally by the RMA receiving pipeline.

Key Procedures and Functions

The package exposes sixteen documented procedures and functions, reflecting a set of derivation, validation, and lookup utilities:

• DERIVE_RMA_LINE — Derives the RMA receiving line attributes from interface and shipment data.
• DERIVE_RMA_TRANS_DEL — Derives transaction-level detail for the RMA return.
• DERIVE_RMA_CORRECTION_LINE — Derives correction line information for adjusting an RMA receipt.
• DEFAULT_RMA_LINE — Populates default values on the RMA line when the interface record is incomplete.
• VALIDATE_RMA_LINE — Validates the derived and defaulted RMA line prior to processing.
• GET_LOCATION_ID — Resolves the party or customer location identifier.
• GET_LOCATOR_ID — Resolves the inventory locator (subinventory/locator combination) for the return.
• GET_ROUTING_HEADER_ID — Retrieves the routing header associated with the RMA.
• GET_ROUTING_STEP_ID — Retrieves the routing step associated with the RMA.
• GET_REASON_ID — Resolves the transaction reason identifier for the return.
• DEFAULT_ITEM_REVISION — Defaults the item revision when one is not supplied.
• VALIDATE_ITEM_REVISION — Validates that the supplied or defaulted revision is valid for the item.
• CHECK_DATE_TOLERANCE — Applies date tolerance checks against the RMA.
• CONVERT_INTO_CORRECT_QTY — Converts the entered quantity into the correct unit of measure quantity.
• GET_ITEM_ID — Resolves the inventory item identifier.
• GET_ORG_ID_FROM_HR_LOC_ID — Derives the inventory organization identifier from an HR location identifier.

Tables Accessed

Via APPS synonyms, the package reads and writes RCV_HEADERS_INTERFACE, the staging table holding inbound RMA and receipt header records. Item and revision validation relies on MTL_SYSTEM_ITEMS, MTL_SYSTEM_ITEMS_KFV, MTL_ITEM_REVISIONS, and MTL_ITEM_REVISIONS_B, while MTL_CUSTOMER_ITEMS supports customer item cross-references. Category defaulting uses MTL_CATEGORY_SETS_B, MTL_DEFAULT_CATEGORY_SETS, and MTL_ITEM_CATEGORIES. Reason resolution reads MTL_TRANSACTION_REASONS; transaction history and processing reference MTL_MATERIAL_TRANSACTIONS. Organization derivation uses HR_ALL_ORGANIZATION_UNITS, and customer and party lookups use HZ_CUST_ACCOUNTS and HZ_PARTIES. MTL_CLIENT_PARAMETERS supplies client-level setup values.

Usage Notes

RCV_RMA_TRANSACTIONS is invoked programmatically rather than directly by end users. It is referenced by RCV_ROI_PREPROCESSOR, which forms the RMA open interface preprocessing stage that transforms staged return data before the Receiving Transaction Processor executes. The package also references itself, indicating recursive or iterative line processing. Typical invocation points include the Receiving RMA concurrent programs and custom extensions that load records into RCV_HEADERS_INTERFACE and then call the ROI preprocessor. Because it is classified as OTHER and its procedures are supporting utilities, it should be treated as an internal package; customizations should follow Oracle's documented RMA receiving interface methodology and validate all derived values against the same item, revision, locator, and reason tables to avoid data integrity failures during receipt processing.