Search Results csr_attribute




Overview
Explore in AI Chat

Overview

PAY_ELEMENT_TEMPLATE_GEN is an internal Oracle Payroll (Oracle HRMS) PL/SQL package that supports the generation of payroll element templates from defined balance and element classification metadata. Its scope centers on the configuration objects that govern how earnings, deductions, and other payroll elements are constructed — balance types, balance attributes, balance dimensions, classifications, and formula associations. The package resides in the APPS schema and is classified as an "OTHER" API, indicating that it is not intended as a public, supported integration interface. Instead, it functions as a backend engine invoked by Oracle's own setup and template-generation facilities, most notably when the system creates or refreshes element templates that ultimately drive element, input value, and balance record creation. The header comment references the source file pyetmgen.pkb, and the package declares shared package variables and PL/SQL collection types (g_rowid_id_rec, t_rowid_id_recs, g_id_ovn_rec, t_id_ovn_recs) used to cache primary keys, ROWIDs, object version numbers, and effective dates for iterative DML operations. The package also defines constant lookup types for CORE_OBJECT_TYPE values, including balance feeds and balance type identifiers, reflecting its role in navigating the Payroll balance model.

Key Procedures and Functions

  • GENERATE_PART1 — The first phase of the template generation process. It initiates the creation of template artifacts by resolving the source element classifications, balance definitions, and related metadata, persisting primary keys and ROWIDs into the package's collection structures for use in subsequent processing.
  • GENERATE_PART2 — The second phase, which completes template generation. It consumes the identifiers cached by GENERATE_PART1 and performs the remaining object creation and update logic, using row handler and object version number tracking to manage the iterative tables described in the package header.
  • ZAP_CORE_OBJECTS — A cleanup routine that removes the core objects created during template generation. The name reflects the package's convention of managing CORE_OBJECT_TYPE lookups, and it is used to undo or reset generated configuration when a template is regenerated or discarded.

No parameter lists are documented for these procedures; they should be treated as internal entry points rather than published APIs.

Tables Accessed

The package reads and writes against a substantial set of Payroll configuration tables via APPS synonyms. Balance-related tables include PAY_DEFINED_BALANCES, PAY_BALANCE_TYPES, PAY_BALANCE_CATEGORIES_F, PAY_BALANCE_CLASSIFICATIONS, PAY_BALANCE_ATTRIBUTES, PAY_BAL_ATTRIBUTE_DEFINITIONS, PAY_BALANCE_DIMENSIONS, and PAY_BALANCE_FEEDS_F; these supply the balance model from which element templates are derived. Element configuration is represented by PAY_ELEMENT_TYPES_F and PAY_ELEMENT_CLASSIFICATIONS. Formula associations are handled through FF_FORMULAS_F, FF_FORMULA_TYPES, FF_FDI_USAGES_F, and FF_COMPILED_INFO_F, which link templates to their calculation logic. BEN_BENEFIT_CLASSIFICATIONS is referenced to accommodate benefit-plan classification data. Collectively these objects allow the package to translate balance and classification metadata into fully formed element template records.

Usage Notes

PAY_ELEMENT_TEMPLATE_GEN is referenced by one other package, confirming its role as a subordinate component in a larger generation flow rather than a standalone utility. It is typically invoked indirectly — through Oracle's element template setup forms, related concurrent programs, or higher-level payroll configuration packages — when templates are created, refreshed, or removed. Because the package uses direct row handler DML and ROWID-based iteration rather than formal business APIs (a fact acknowledged in the package's own header comments), custom code should not call it directly. Developers investigating or extending template generation should inspect the calling context and treat these procedures as implementation details of the Payroll configuration framework.