Search Results chk_approved_folder

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.PQH_BDGT_REALLOC_UTILITY is a PL/SQL package body within the Oracle E-Business Suite Public Sector / Human Resources budget reallocation framework. Its header signature (pqbreutl.pkb, version 120.2) indicates it is an integral utility layer that supports the budget pool reallocation process, in which budget amounts are donated or received between budget units and entities under an approval workflow. The package provides the computational, validation, and notification services required by the reallocation transaction engine.

The package performs two broad categories of work. First, it supplies functions that resolve entity identifiers to display names and that calculate reserved or reserved-remaining amounts at the period, transaction, folder, and detail levels. Second, it drives the approval lifecycle through transaction application and rejection, notification routing, and next-approver determination. The package is classified as OTHER in the ETRM API registry, indicating it is a supporting utility rather than a formal public API, and it is referenced by three other packages, confirming its role as a shared internal service.

Key Procedures and Functions

• GET_ENTITY_NAME — returns the display name of a budget entity, decoupling the caller from entity-type-specific decode logic for positions, jobs, organizations, and grades.
• GET_PRD_REALLOC_RESERVED_AMT — returns the already-donated or unapproved donated amount (or the received amount) for a budget period, parameterised by transaction type (e.g. donor details, receiver details), approval status, and amount type.
• GET_TRNX_LEVEL_TRANS_AMT and GET_FOLDER_LEVEL_TRANS_AMT — compute transaction amounts aggregated at the transaction and folder levels respectively.
• GET_DTL_REALLOC_RESERVED_AMT and GET_TRNX_LEVEL_RESERVED_AMT — return reserved reallocation amounts at the detail and transaction levels.
• GET_TRNX_DNR_REVR_COUNT — counts donor/receiver reversals associated with a transaction.
• CHK_RECV_EXISTS and CHK_APPROVED_FOLDER — validate that a receiver exists and that a folder has reached approved status.
• GET_LOCATION_CODE — resolves a location code used in routing and notification processing.
• APP_NEXT_USER, GET_NEXT_USER, FND_NEXT_USER, and ENTITY_ID — determine the next approver or routing recipient and the associated entity identifier.
• APPLY_TRANSACTION and REJECT_TRANSACTION — perform the core state transitions that apply or reject a reallocation transaction.
• RESPOND_NOTIFICATION, WARNING_NOTIFICATION, REJECT_NOTIFICATION, and APPLY_NOTIFICATION — generate the workflow notifications issued in response to approval, warning, rejection, and application events.

Tables Accessed

The package reads and writes the core reallocation and workflow tables through APPS synonyms. PQH_BDGT_POOL_REALLOCTIONS stores the reallocation transactions; PQH_BUDGET_POOLS, PQH_BUDGETS, PQH_BUDGET_DETAILS, and PQH_BUDGET_PERIODS supply the budget hierarchy and period context used in amount calculations. PQH_POSITION_TRANSACTIONS and PER_POS_STRUCTURE_ELEMENTS support position-level entity and transaction resolution. PQH_ROUTING_LISTS, PQH_ROUTING_LIST_MEMBERS, PQH_ROUTING_CATEGORIES, and PQH_ROUTING_HISTORY drive approval routing and history. PQH_ROLES, PQH_TRANSACTION_CATEGORIES, and PER_SHARED_TYPES provide role and lookup data, while FND_USER is used to resolve approvers for notifications.

Usage Notes

PQH_BDGT_REALLOC_UTILITY is invoked indirectly rather than by end users. Its callers are the budget reallocation forms and concurrent programs that submit, approve, and apply reallocations, together with the three dependent packages that reference it. The notification and apply/reject routines are typically triggered from Oracle Workflow or from form-level button handlers as a transaction moves through its approval chain. Customisations should treat the package as an internal implementation detail: because it is classified as OTHER, its interfaces are not guaranteed stable across patch levels, and direct calls should be avoided in favour of the supported reallocation APIs. The hard-coded donor/receiver transaction types and approval-status codes embedded in its amount functions should be respected when interpreting returned values.