Search Results t_sql_stm_tab

Overview

PAY_CORE_UTILS is a foundational Oracle Payroll utility package within the APPS schema, providing shared low-level services consumed broadly across the Oracle E-Business Suite payroll and HRMS module family. Its API classification is OTHER, indicating it is an internal infrastructure package rather than a business-facing API. In EBS 12.1.1 and 12.2.2, the package supplies cross-cutting helpers for dynamic SQL cursor management, business group and legislation resolution, parameter-list parsing, proration date derivation, time definition lookups, and message/token emission. The package header defines several PL/SQL collection types, including DATE_ARRAY, CHAR_ARRAY, T_CONTEXTS_REC/T_CONTEXTS_TAB for dynamic context details, and T_SQL_STM_REC/T_SQL_STM_TAB for caching dynamic SQL statements, alongside a global cache of business group identifiers. With 257 dependent packages, PAY_CORE_UTILS is effectively a shared kernel routine; most payroll processing, element entry, and payroll action logic transitively relies on its utility functions. The user search term "assert_condition" reflects a common expectation that utility packages expose assertion helpers; the documented interface does not include a procedure of that name, and PAY_CORE_UTILS instead supports validity checking through its structural helpers.

Key Procedures and Functions

• GET_SQL_CURSOR — Opens or retrieves a cached dynamic SQL cursor from the global statement table, returning success status.
• CLOSE_SQL_CURSOR / CLOSE_ALL_SQL_CURSORS — Release a single cached cursor or all outstanding cached cursors maintained in G_SQL_CURSORS.
• GET_PARAMETER / REMOVE_PARAMETER — Parse, read, and strip named parameters from a delimited parameter-list string, supporting dynamic context evaluation.
• GET_BUSINESS_GROUP / GET_BUSINESS_GROUP_WITHBIND / GET_DYT_BUSINESS_GROUP — Derive the current business group identifier from a SQL statement, optionally with bind variables or Dynamic Year Table logic.
• GET_LEGISLATION_CODE — Return the legislation code for a given business group identifier.
• RESET_CACHED_VALUES — Clear cached business group and related session-level values.
• GET_TIME_DEFINITION — Determine the time definition applicable to an element entry and assignment action combination.
• GET_TIME_PERIOD_START, GET_ENTRY_END_DATE, GET_PRORATED_DATES, SET_PRORATE_DATES — Compute and manipulate payroll time period boundaries and proration date arrays.
• GET_RR_ID, GET_AA_ID, GET_RB_ID — Resolve run result, assignment action, and related identifiers used by payroll processing.
• PUSH_MESSAGE, PUSH_TOKEN — Emit message lines and formatting tokens to the payroll message stack.

Tables Accessed

The package reads and writes a defined set of payroll and FastFormula metadata tables through APPS synonyms. FF_CONTEXTS supplies the dynamic context definitions used to build the T_CONTEXTS_TAB structures. PAY_INPUT_VALUES_F and PAY_ELEMENT_TYPES_F provide element and input value metadata referenced during context resolution. PAY_LEGISLATION_CONTEXTS and PAY_LEGISLATION_RULES support legislation-specific rule evaluation. PAY_ASSIGNMENT_ACTIONS and PAY_ASSIGNMENT_ACTIONS_S are used for assignment action resolution and identifier lookups. PAY_ELEMENT_ENTRIES_F and PAY_ELEMENT_ENTRY_VALUES_F supply element entry data for time definition and proration logic, while PAY_ELEMENT_CLASSIFICATIONS, PAY_ELEMENT_CLASS_USAGES_F, and PAY_ELEMENT_TYPE_USAGES_F drive element classification and usage checks. PAY_COSTS and PAY_ACTION_INTERLOCKS support payroll action and costing context. PAY_MESSAGE_LINES receives output from the message and token push routines.

Usage Notes

PAY_CORE_UTILS is invoked indirectly by Oracle Payroll forms, concurrent programs, and payroll action processing rather than being exposed as an end-user API. Custom extensions, particularly FastFormula user-defined functions and custom payroll routines, may call its parameter parsing, business group, and legislation helper functions to resolve execution context. Because the package maintains session-level globals such as G_SQL_CURSORS and cached business group values, callers should invoke RESET_CACHED_VALUES when switching business group context within a session and ensure cursors are closed to avoid resource accumulation. There is no ASSERT_CONDITION routine in the documented interface; code requiring assertion behavior must implement conditional checks using standard PL/SQL constructs or the validation helpers this package provides.