Search Results pay_run_balances_s

Overview

PAY_CORE_UTILS is a foundation utility package body in the Oracle Payroll (PAY) schema of Oracle E-Business Suite, owned by APPS and validated as of release 12.1.1 and 12.2.2. It performs the low-level plumbing work on which most payroll processing, element entry, assignment action, and payroll run logic depends. Rather than exposing a single business transaction, the package centralizes reusable services: cursor management for dynamic SQL, cached lookup of business group and legislation context, date and time period derivation, proration date calculation, identifier resolution for run results, and message/token emission for logging and user feedback.

The dependency footprint confirms its foundational role. ETRM documentation records that PAY_CORE_UTILS is referenced by 257 other packages, indicating it is called throughout payroll processing, costing, and legislative extensions. It is itself dependent on core payroll and HR tables plus DBMS_SQL, PLITBLM, FF_CONTEXTS, and HR_UTILITY. Its API classification is recorded as OTHER, reflecting that it is an internal utility rather than a public business API.

Key Procedures and Functions

Documented procedures number 44, including public and overloaded variants. The principal groups are:

• Dynamic SQL cursor handling — GET_SQL_CURSOR, CLOSE_SQL_CURSOR, and CLOSE_ALL_SQL_CURSORS open, track, and release dynamic cursors, and RESET_CACHED_VALUES clears the package's cached session values.
• Parameter management — GET_PARAMETER and REMOVE_PARAMETER read and remove entries in the package's internal parameter cache.
• Context and business group resolution — GET_BUSINESS_GROUP, GET_BUSINESS_GROUP_WITHBIND, and GET_DYT_BUSINESS_GROUP return business group identifiers (including a bind-variable and a "date you're thinking" variant), while GET_LEGISLATION_CODE derives the applicable legislation for the current context.
• Date and time derivation — GET_TIME_DEFINITION and GET_TIME_PERIOD_START resolve payroll time definitions and period start dates, and GET_ENTRY_END_DATE determines the closing date for an element entry.
• Proration — GET_PRORATED_DATES and SET_PRORATE_DATES compute and store proration boundaries used when entries are split across periods.
• Identifier lookup — GET_RR_ID, GET_AA_ID, and GET_RB_ID return run result, assignment action, and run balance identifiers respectively.
• Messaging — PUSH_MESSAGE and PUSH_TOKEN add lines and substitution tokens to the payroll message buffer for later retrieval by calling programs.

Tables Accessed

The package reads and writes the core payroll tables through APPS synonyms. Assignment action tables (PAY_ASSIGNMENT_ACTIONS, PAY_ASSIGNMENT_ACTIONS_S, PAY_ACTION_INTERLOCKS, PAY_ACTION_PARAMETERS) support action tracking and interlock checks. Element structures (PAY_ELEMENT_TYPES_F, PAY_ELEMENT_CLASSIFICATIONS, PAY_ELEMENT_CLASS_USAGES_F, PAY_ELEMENT_TYPE_USAGES_F, PAY_INPUT_VALUES_F, PAY_ELEMENT_ENTRIES_F, PAY_ELEMENT_ENTRY_VALUES_F) supply entry and classification data used in date and proration logic. Payroll and run objects (PAY_PAYROLLS_F, PAY_RUN_TYPES and _F, PAY_RUN_RESULTS and _S, PAY_RUN_BALANCES_S) support identifier resolution. Legislative and context tables (PAY_LEGISLATION_CONTEXTS, PAY_LEGISLATION_RULES, FF_CONTEXTS, PER_BUSINESS_GROUPS, PER_TIME_PERIODS, PER_ALL_ASSIGNMENTS_F) drive business group, legislation, and time period determination. Message output is staged in PAY_MESSAGE_LINES and PAY_MESSAGE_LINES_S. Additional references include PAY_COSTS, PAY_INTERPRETER_PKG, PAY_PROC_LOGGING, PAY_UPGRADE_* tables, and PAY_REPORT_FORMAT_* objects.

Usage Notes

Typical invocation occurs from payroll concurrent programs, element entry forms, assignment action processing, and legislative or customer extension code that needs cached context, consistent date calculation, or message output. Because the package maintains internal caches and open cursors, callers should invoke CLOSE_ALL_SQL_CURSORS and RESET_CACHED_VALUES at appropriate transaction boundaries to avoid stale values within a session. Customizations should favor the documented procedures over direct table access to preserve upgrade compatibility across 12.1.1 and 12.2.2.