Search Results get_gl_periods

Overview

PA_FUNDS_CONTROL_UTILS is a foundational utility package within the Oracle Projects (PA) module of Oracle E-Business Suite. Its principal responsibility is to support funds control and budgetary control processing by centralizing the derivation of budget, encumbrance, and commitment related values needed during transaction validation. The package implements a one-level cache through a series of package global variables (g_project_id, g_bdgt_version_id, g_task_id, g_exp_type, g_exp_item_date, g_budget_ccid, g_period_name, and others). These globals retain the most recent lookup context so that repeated calls within the same session avoid redundant queries against the base tables, yielding a significant performance improvement during high-volume funds checking.

In the 12.1.1 and 12.2.2 releases the package remains a core dependency for budgetary control. Bugs such as 5373272 are reflected in additional globals (g_event_type_code, g_document_distribution_id, g_document_distribution_type, g_parent_distribution_id) that support Subledger Accounting (SLA) integration with XLA_EVENTS. The search term derive_po_req_amt_side relates to the encumbrance derivation logic this package underpins when requisitions and purchase orders are subjected to funds checking.

Key Procedures and Functions

The package exposes 27 documented procedures and functions. INIT_UTIL_VARIABLES resets the cached global variables, typically called at the start of a processing cycle. GET_FC_COMPILED_MULTIPLIER and GET_FC_COMPILED_SET_ID retrieve compiled burden multipliers and set identifiers for a given task, expenditure organization, and expenditure item date. GET_FC_PROJ_BURDN_COST derives burdened project cost, while GET_GL_PERIODS obtains GL period information. GET_FND_REQD_FLAG indicates whether funds checking is required, and GET_ENCUM_TYPE_ID and GET_BDGT_LINK return the encumbrance type and budget link identifiers.

GET_BDGT_VERSION_ID and GET_BASELINED_BUDGET_VERSION resolve the applicable budget version, and GET_BUDGET_CCID returns the budget code combination. GET_TIME_PHASED_TYPE_CODE returns the time-phased budgeting indicator. GET_ACCT_LINE_BALANCE retrieves account line balances, and IS_BUDGET_BASELINED_BEFORE evaluates the baseline status for a given date. RUNSWEEPER and PRINT_MESSAGE provide housekeeping and diagnostic output. IS_ACCOUNT_CHANGE_ALLOWED and IS_ACCOUNT_CHANGE_ALLOWED2 control whether account modifications are permitted under funds control rules. GET_SLA_NOTUPGRADED_FLAG checks SLA upgrade status, and UPDATE_BVID_BLID_ON_CDL_BCCOM propagates budget version and budget link identifiers across the commitment and budgetary control tables.

Tables Accessed

The package reads and writes PA_BC_PACKETS, PA_BC_BALANCES, PA_BC_COMMITMENTS, and PA_BC_COMMITMENTS_ALL to maintain budgetary control balances and commitment records. PA_BUDGET_VERSIONS, PA_BUDGET_ACCT_LINES, PA_BUDGET_ENTRY_METHODS, and PA_BUDGETARY_CONTROL_OPTIONS supply budget definitions and funds control configuration. GL_PERIOD_STATUSES and GL_ENCUMBRANCE_TYPES provide GL period and encumbrance type data. AP_INVOICES_ALL, AP_INVOICE_DISTRIBUTIONS_ALL, AP_PREPAY_APP_DISTS, and AP_PREPAY_HISTORY_ALL support encumbrance derivation for invoices and prepayments. XLA_EVENTS connects funds control to subledger accounting events.

Usage Notes

PA_FUNDS_CONTROL_UTILS is referenced by 32 other packages, confirming its role as a shared services layer rather than a user-facing entry point. It is invoked indirectly from the Funds Check and Budgetary Control flows triggered by Oracle Purchasing (requisitions and purchase orders), Payables (invoices and prepayments), and Projects transaction entry. Concurrent programs that perform funds checking and budgetary control sweeps call RUNSWEEPER and the master validation APIs that depend on this utility. Custom extensions integrating with funds control should call these utility APIs rather than querying PA_BC_PACKETS directly, ensuring that the global caching and derivation logic remain consistent across the session. Because the globals are not protected for concurrent use within a session, custom code should re-invoke INIT_UTIL_VARIABLES when switching processing context.