Search Results claim_ref_status_change_sub




Overview
Explore in AI Chat

Overview

PV_BENFT_STATUS_CHANGE is an Oracle EBS Application Object Library PL/SQL package owned by the APPS schema. It belongs to the Oracle Partner Management / Channel Revenue Management family of modules, operating on benefit, referral, and lead entities managed through partner programs (the PV and AS product prefixes). Its primary business function is to orchestrate status-transition processing for benefits and referral records, including notification of interested parties, workflow-based subscription handling, audit logging of status changes, and lookup retrieval for decline reasons and product associations.

The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling user rather than as definer. This design is significant: it relies on the caller's access to the underlying APPS synonyms and Workflow objects, which supports flexible invocation from concurrent managers, Forms, and OAF pages where the effective user may vary.

Although the header dates to 2003 (version 115.3), the package remains documented in ETRM for both 12.1.1 and 12.2.2, indicating continued relevance in the current release architecture.

Key Procedures and Functions

The package exposes nine documented procedures and functions that collectively manage the status-change lifecycle:

  • STATUS_CHANGE_NOTIFICATION — The primary driver procedure that raises a status-change notification for a given benefit. It accepts the benefit identifier, the new status, an entity identifier, a partner identifier, and message and user callback API names, returning standard API return status, message count, and message data.
  • STATUS_CHANGE_LOGGING — Records the status change for audit and traceability purposes, capturing the same benefit, status, entity, and partner context as the notification path.
  • STATUS_CHANGE_RAISE — Raises the underlying Workflow business event that triggers downstream subscriptions for the status change.
  • STATUS_CHANGE_SUB — A Workflow event subscription function that handles the generic status-change event, receiving the subscription GUID and event payload.
  • CLAIM_REF_STATUS_CHANGE_SUB — A specialized Workflow subscription function that handles status changes specific to claim and referral records.
  • REFERRAL_SET_MSG_ATTRS — Populates message attributes for referral notifications, based on item type, item key, entity, user type, and status.
  • REFERRAL_RETURN_USERLIST — Returns a delimited list of users eligible to receive referral notification, filtered by benefit type, entity, user role, and status.
  • GET_DECLINE_REASON — Retrieves the configured decline reason associated with a benefit status transition.
  • GET_PRODUCTS — Returns the product associations relevant to the benefit or referral record, supporting the "get_products" search that surfaced this package.

Tables Accessed

The package reads and writes against APPS synonyms spanning several schema domains:

Usage Notes

PV_BENFT_STATUS_CHANGE is typically invoked indirectly rather than called directly by end users. Standard invocation paths are: Workflow event subscriptions (STATUS_CHANGE_SUB and CLAIM_REF_STATUS_CHANGE_SUB are registered subscription handlers on the Oracle Workflow event system), benefit status-change Forms or OAF pages that call STATUS_CHANGE_NOTIFICATION when a user transitions a benefit, and concurrent or batch programs that process referral and claim status updates. Three other packages reference PV_BENFT_STATUS_CHANGE, indicating that it is a shared service layer within the Partner Management stack.

Custom code integrating with this package should follow the standard EBS API conventions: initialize the message list, supply a meaningful API version number, set the commit flag appropriately, and always inspect x_return_status. Because the package relies on the caller's privileges, custom callers must have EXECUTE on the package and SELECT privileges on the referenced APPS synonyms. The GET_PRODUCTS function is the entry point most commonly queried when integrating product-level detail into benefit or referral processing.