Search Results notify_rma_request_action




Overview
Explore in AI Chat

Overview

IBE_OM_INTEGRATION_GRP is a PL/SQL package owned by APPS and classified as a GRP (group) API within Oracle E-Business Suite. It provides the integration bridge between Oracle iStore (IBE) and Oracle Order Management (OM) for the return merchandise authorization (RMA) approval workflow. Specifically, the package delivers notification to the iStore end user when an Order Management administrator acts on a return order the user previously submitted.

The package declares two global constants that identify the notification context passed by OM when the API is called: G_RETURN_APPROVAL (value '1') and G_RETURN_REJECT (value '2'). The user search term "g_return_reject" therefore maps directly to the documented constant used as the P_notif_context value for rejection notifications. The header comment records this package at version 115.1, dated 2003/09/02, and compiled with AUTHID CURRENT_USER.

Key Procedures and Functions

Only one procedure is documented in the ETRM metadata for this package:

  • NOTIFY_RMA_REQUEST_ACTION — Notifies iStore end users of the OM administrator's action (approval or rejection) on a return order they submitted. The caller supplies the notification context through a parameter whose valid values are the two global constants, G_RETURN_APPROVAL and G_RETURN_REJECT. An additional parameter carries the comments entered by the OM administrator, and another carries the rejection reason code when the context is G_RETURN_REJECT. When the return is approved, the notification may contain the address of the location to which the goods must be returned. The procedure also exposes output parameters for return status and message count, consistent with standard EBS API error-handling conventions.

Per the package header commentary, the API is designed to be extensible: additional notification context values can be defined in the future so the same entry point can retrieve notification party lists for other OM events.

Tables Accessed

The package references the following tables through APPS synonyms, as recorded in the ETRM metadata:

  • OE_ORDER_HEADERS_ALL — The order header for the return order is read to determine the user, order identity, and other attributes needed to build the notification payload.
  • FND_USER — Resolves the iStore end user (notification recipient) associated with the return order.
  • WF_ITEMS — Supplies the Oracle Workflow item context used to identify the workflow process and item key for the return notification.
  • WF_MESSAGES — Provides the workflow message definition used to render the approval or rejection notification text delivered to the user.

Usage Notes

The API is primarily invoked by Oracle Order Management when the RMA approval process is active. OM calls the procedure with P_notif_context set to G_RETURN_APPROVAL for approval notifications and to G_RETURN_REJECT for rejection notifications. If the approval process has not been configured in OM, the API is not called at all; instead, the return order is booked directly upon user submission.

The procedure is not designed for direct invocation by end users or standard forms. Custom extensions that need to reuse the notification logic should pass the appropriate context constant and the corresponding optional parameters (comments and, for rejections, the reason code) to align with the workflow message expected by the recipient. Because the package is compiled with AUTHID CURRENT_USER, it executes with the privileges of the calling schema, so any custom caller must have the necessary grants on the underlying objects.