Search Results set_name_psn_psup
Overview
APPS.HR_BPL_MESSAGE is a PL/SQL package in Oracle E-Business Suite (12.1.1 / 12.2.2) that provides language-aware message handling for Oracle HRMS business groups. It acts as a wrapper around the standard Oracle Application Object Library (FND) message infrastructure, extending the base FND_MESSAGE functionality so that message text can be resolved and set in the language associated with a specific business group, person, assignment, or supervisor. The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema rather than the owner, which is significant for a message package that must be invoked from a wide variety of HRMS contexts.
The design intent is that Oracle HRMS applications frequently need to present error, warning, or informational messages in the language of the relevant person or business group rather than the session language. HR_BPL_MESSAGE encapsulates that logic in one place, sparing individual callers from resolving language preferences manually.
Key Procedures and Functions
The package exposes twelve documented procedures and functions:
- GET_STRING_LNG_BG — returns a message string in the language of a specified business group. It is the packaged mechanism for business-group-specific language retrieval.
- GET — an updated version of the base retrieval function that supports setting the language, returning a message string.
- SET_NAME_PSN — sets the message using the language of the specified person_id.
- SET_NAME_SUP — sets the message using the language of the supervisor of the specified assignment.
- SET_NAME_PSUP — sets the message using the language of the primary supervisor of the specified assignment.
- SET_NAME_PSN_PSUP — sets the message using the language of the primary supervisor of a person.
- SET_NAME — the core setter, establishing the message name; also carries the business group context.
- FETCH_SQL_TOKEN, SET_TOKEN, SET_TOKEN_SQL — the token-handling routines that support the token substitution mechanism inherited from the FND message framework. These allow callers to bind values into message placeholders before retrieval.
- RETRIEVE — returns the fully assembled message after name, language, and tokens have been established.
- CLEAR — resets the package state so that a subsequent message can be built cleanly.
Tables Accessed
The package reads from FND_APPLICATION and FND_NEW_MESSAGES (via APPS synonyms). FND_APPLICATION is consulted to resolve the owning application referenced by the message name, while FND_NEW_MESSAGES holds the current message definitions and their translated variants. Access is primarily read-only, as the package queries message text rather than maintaining it.
Usage Notes
HR_BPL_MESSAGE is typically invoked from Oracle Forms, concurrent programs, and custom PL/SQL that must produce localized messages in an HRMS context. In particular, the SET_TOKEN_SQL routine is used where a token value must be derived dynamically — for example, resolving a value from a query at runtime rather than passing a static literal — before the message is retrieved. Callers generally follow the sequence SET_NAME (or the person/assignment-specific variant), SET_TOKEN / SET_TOKEN_SQL for each placeholder, then RETRIEVE, followed by CLEAR to reset state. Because the package relies on the underlying FND message store, any custom message must be defined and translated within the relevant application before it can be resolved by language at runtime. The package is referenced by at least one other documented package, indicating it functions as a shared utility rather than an end-user-facing component.