Search Results get_next_user

Overview

PQH_BDGT_REALLOC_UTILITY is an APPS-owned PL/SQL package within the Oracle E-Business Suite Public Sector / Human Resources budget module. It provides the core utility logic that supports budget reallocation processing for positions and position hierarchies. In the Oracle EBS 12.1.1 and 12.2.2 releases, the package is registered with a status of VALID and is classified as an OTHER API. Its primary business function is to compute, validate, and apply budget reallocation transactions that move budget amounts between budget pools, budget periods, and position-level budget details, while routing those transactions through the appropriate approval workflow and maintaining a complete audit trail.

The package is tightly coupled with the Oracle Approval Management (AME) and routing framework, as evidenced by its references to routing lists, routing categories, routing history, and transaction categories. It therefore acts as both a calculation engine and a workflow integration point for budget reallocation.

Key Procedures and Functions

The package exposes approximately thirty documented procedures and functions. Significant members include:

• GET_ENTITY_NAME – resolves the descriptive name of the entity associated with a reallocation transaction.
• GET_PRD_REALLOC_RESERVED_AMT – returns the reserved reallocation amount at the budget period level.
• GET_TRNX_LEVEL_TRANS_AMT and GET_TRNX_LEVEL_RESERVED_AMT – return transaction-level transferred and reserved amounts respectively.
• GET_FOLDER_LEVEL_TRANS_AMT – returns the transferred amount aggregated at the folder (position hierarchy) level.
• GET_DTL_REALLOC_RESERVED_AMT – returns the reserved reallocation amount at the budget detail level.
• GET_TRNX_DNR_REVR_COUNT – counts do-not-reallocate or reversal occurrences on a transaction.
• CHK_RECV_EXISTS and CHK_APPROVED_FOLDER – validation functions confirming that a receiver record exists and that a folder has been approved.
• GET_LOCATION_CODE – derives the location code associated with a transaction.
• APP_NEXT_USER, GET_NEXT_USER, and FND_NEXT_USER – determine the next approver in the routing chain, drawing on FND_USER.
• APPLY_TRANSACTION and REJECT_TRANSACTION – commit or reject a reallocation transaction, updating the underlying budget records.
• ENTITY_ID – returns the identifier of the entity being processed.
• RESPOND_NOTIFICATION, WARNING_NOTIFICATION, REJECT_NOTIFICATION, and APPLY_NOTIFICATION – handle the workflow notification responses raised during the reallocation approval cycle.

Tables Accessed

The package reads and writes a defined set of budget, routing, and HR tables through APPS synonyms:

• PQH_BUDGETS, PQH_BUDGET_DETAILS, PQH_BUDGET_PERIODS, and PQH_BUDGET_POOLS – the core budget structures whose amounts are reallocated.
• PQH_BDGT_POOL_REALLOCTIONS – records the reallocation transactions themselves.
• PQH_POSITION_TRANSACTIONS – links reallocations to position-level transactions.
• PQH_ROUTING_LISTS, PQH_ROUTING_LIST_MEMBERS, PQH_ROUTING_CATEGORIES, PQH_ROUTING_HISTORY, and PQH_TRANSACTION_CATEGORIES – support approval routing and audit history.
• PQH_ROLES – resolves the role of the participant in the approval chain.
• FND_USER, PER_ASSIGNMENTS_F, PER_POS_STRUCTURE_ELEMENTS, HR_ORGANIZATION_UNITS_V, and PER_SHARED_TYPES – provide user, assignment, hierarchy, and organization context.

Usage Notes

PQH_BDGT_REALLOC_UTILITY is not intended for direct end-user invocation. It is called by the budget reallocation forms and concurrent programs, and it is referenced by the sibling packages PQH_BDGT_REALLOC_LOG_PKG, PQH_CBR_ENGINE, and PQH_WF, which together drive the workflow and logging lifecycle. The presence of notification-handling procedures indicates the package is invoked from Oracle Workflow notification response processing. Customizations should avoid modifying this package and should instead call its documented APIs, since the package body is proprietary and changes occur across patch levels.