Search Results create_elemnt_tmplt_usages




Overview
Explore in AI Chat

Overview

PAY_CREATE_ELEMNT_TMPLT_RECORD is an Oracle Payroll (PAY) package owned by the APPS schema and defined with AUTHID CURRENT_USER. Its purpose is to create and maintain the element template records—earnings and deductions templates—that Oracle EBS uses as preconfigured blueprints for generating element definitions. Element templates standardize how payroll elements such as flat-amount earnings, percentage earnings, and flat-amount deductions are constructed for a given legislation and currency. The package header (paycreatetemplte.pkh, version 120.1, dated 13-JUN-2005) shows an initial creation in May 2005 for the 115.0 version, with a subsequent revision in 115.1 that added the p_currency_code parameter to the earnings template routines. In Oracle EBS 12.1.1 and 12.2.2 this object remains a server-side PL/SQL package rather than a user-facing API, and it is classified as OTHER in the ETRM documentation. A user searching for "create_earn_pct_amt_templ" has located the specific procedure within this package that builds the percentage-of-amount earnings element template.

Key Procedures and Functions

The package exposes seven documented procedures. Parameter lists follow the source header declarations; no additional parameters are assumed.

  • CREATE_ELEMNT_TMPLT_USAGES — Creates the classification usages for an element template, accepting the template identifier, classification type, and legislation code.
  • CREATE_DEDN_FLAT_AMT_TEMPL — Creates the flat-amount deduction element template for a given legislation code and currency code.
  • CREATE_DEDN_PCT_AMT_TEMPL — Creates the percentage-of-amount deduction element template for a given legislation code and currency code.
  • CREATE_EARN_FLAT_AMT_TEMPL — Creates the flat-amount earnings element template for a given legislation code and currency code.
  • CREATE_EARN_HXR_AMT_TEMPL — Creates the hours-times-rate earnings element template for a given legislation code and currency code.
  • CREATE_EARN_PCT_AMT_TEMPL — Creates the percentage-of-amount earnings element template for a given legislation code and currency code. This is the procedure the user's search term targeted.
  • CREATE_ALL_TEMPLATES — A convenience wrapper that drives creation of the complete set of earning and deduction templates for a given legislation code and currency code.

Tables Accessed

The package operates against the following tables, reached through APPS synonyms:

  • PAY_ELEMENT_TEMPLATES — Stores the element template definitions created and maintained by the package.
  • PAY_ELE_TMPLT_CLASS_USAGES and PAY_ELE_TMPLT_CLASS_USG_S — Hold the template-to-classification usage mappings inserted by CREATE_ELEMNT_TMPLT_USAGES and its dependents.
  • PAY_ELEMENT_CLASSIFICATIONS — Provides classification information used when constructing template usages.
  • PAY_BALANCE_DIMENSIONS — Supplies balance dimension context for the templates being generated.
  • DUAL — Used for single-row PL/SQL constructs.
  • PLITBLM — The PL/SQL table-of-Boolean or index-by-table construct referenced in the package body.

Usage Notes

PAY_CREATE_ELEMNT_TMPLT_RECORD is not intended for direct end-user invocation. It is typically called from concurrent programs or setup routines that seed element templates for a legislation during implementation or localization of Oracle Payroll. The CREATE_ALL_TEMPLATES procedure provides the bulk-loading entry point, while the individual create_earn_* and create_dedn_* procedures allow selective generation of a single template type. The package is referenced by one other package in the APPS schema, indicating it is normally consumed as a dependency rather than called from a form. Custom code should call the procedures with a valid legislation code and a valid currency code supported by that legislation; the currency parameter was introduced in version 115.1 specifically to scope earnings templates correctly. Because the package is AUTHID CURRENT_USER, executing it under a schema other than APPS requires appropriate synonyms and privileges. Direct DML against the template tables should be avoided; changes flow through the procedures so that usage records and template definitions remain consistent.