Results for “cache_elements”

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

Overview

PSB_WS_POS1 is a server-side PL/SQL package owned by APPS within the Oracle E-Business Suite HRMS/Public Sector Budgeting (PSB) module. Its core business function is to execute position and salary worksheet calculations used by the PSB budgeting engine. The package encapsulates the computational logic required to translate budget positions, pay elements, HRMS factors, and set relations into allocated cost lines distributed across budget periods, budget accounts, and budget groups. It is classified as an OTHER API, indicating that it is an internal engine package rather than a published integration interface intended for external callers.

The package defines two significant PL/SQL collection types that reveal its internal design. The g_poscalc_rec_type record structures a calculated position cost, holding a pay element identifier, element type and set identifier, an element cost, a budget year identifier, and up to sixty period amount columns. The companion table type g_poscalc_tbl_type, indexed by BINARY_INTEGER and instantiated as the package global g_pc_costs with counter g_num_pc_costs, caches these records for the duration of a calculation. A second record type, g_posdist_rec_type, begins the structure used for position distribution, holding a chart of accounts combination identifier (CCID) and element data.

Key Procedures and Functions

The documented 21 procedures group into several functional areas. Initialization routines — INITIALIZE_CALC, INITIALIZE_DIST, INITIALIZE_SALARY_DIST, INITIALIZE_ELEMENT_DIST, and INITIALIZE_PERIOD_DIST — reset and prepare the package globals and distribution structures prior to a calculation or distribution pass. Caching routines — CACHE_ELEMENTS, CACHE_NAMED_ATTRIBUTES, CACHE_NAMED_ATTRIBUTE_VALUES, and CACHE_SALARY_DIST — pre-load reference and setup data to avoid repeated queries during heavy worksheet processing.

The calculation and distribution routines form the heart of the package. CREATE_POSITION_LINES, CREATE_POSITION_MATRIX, CREATE_FTE_LINES, and CREATE_ELEMENT_LINES generate the respective position, matrix, full-time-equivalent, and element cost rows for a worksheet. DISTRIBUTE_FOLLOWING_ELEMENTS and DISTRIBUTE_PERIODS spread element costs across distribution targets and budget periods. UPDATE_ANNUAL_FTE, the procedure surfaced by the search term, is responsible for maintaining the annualized full-time-equivalent value associated with a budget position after position, FTE, or element lines have been created or recalculated. HRMS_FACTOR resolves the applicable HRMS factor values used in salary and benefit computation, while CHECK_ALLOWED validates whether a requested operation is permitted, and GET_DEBUG returns the package debug flag.

Tables Accessed

The package reads and writes a broad set of PSB tables through APPS synonyms. Setup and reference tables include PSB_ATTRIBUTES, PSB_ATTRIBUTE_VALUES, PSB_SET_RELATIONS, PSB_HRMS_FACTORS, PSB_PAY_ELEMENTS, PSB_ELEMENT_POS_SET_GROUPS, PSB_SERVICE_PACKAGES, PSB_BUDGET_GROUPS, and PSB_BUDGET_STAGES. Positional data is drawn from PSB_BUDGET_POSITIONS and PSB_POSITION_ASSIGNMENTS. Financial and distribution results are read from and written to PSB_BUDGET_ACCOUNTS, PSB_PAY_ELEMENT_DISTRIBUTIONS, PSB_POSITION_PAY_DISTRIBUTIONS, and the principal worksheet table PSB_WORKSHEETS.

Usage Notes

PSB_WS_POS1 is invoked internally by the Public Sector Budgeting worksheet engine rather than by end users directly. It is typically triggered when a budget analyst opens or recalculates a position or salary worksheet in the PSB forms, or when PSB concurrent processes rebuild worksheet lines. The metadata records that the package is referenced by 10 other packages, confirming its role as a shared utility within the PSB engine. Custom code should not call these procedures without validating the expected initialization sequence, since the cached globals (g_pc_costs, g_num_pc_costs) carry state across calls. The package header carries a 2005 identifier, consistent with long-term stability in 12.1.1 and 12.2.2.