Results for “base_processing_priority”

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

Overview

PAY_ELEMENT_TEMPLATES is a Payroll (PAY) module table owned by the HR schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores Element Templates, the metadata definitions that drive the configuration of payroll elements across a business group. An element template acts as a reusable blueprint: it defines a template type, a base element name, default processing priority, preference and configuration attributes, and the set of shadow balance types, shadow element types, core objects, exclusion rules, and fast formula usages that should be created or inherited whenever a new element is instantiated from that template. In this sense the table is a configuration hub for payroll element generation rather than a transactional payroll table.

The documented physical schema for 12.2.2 lists 78 columns, with the primary key defined by the PAY_ELEMENT_TEMPLATES_PK unique index over TEMPLATE_ID and ZD_EDITION_NAME. Because the table is referenced by five dependent tables through TEMPLATE_ID and contains the surrogate key plus descriptive attributes, the heuristic Data Vault classification is hub-leaning. Under that modeling suggestion, PAY_ELEMENT_TEMPLATES would be treated as a hub keyed on TEMPLATE_ID, with dependent tables acting as links or satellites that carry the template's related definitions.

Key Information Stored

The most significant columns in PAY_ELEMENT_TEMPLATES include:

• TEMPLATE_ID — surrogate primary key (PAY_ELEMENT_TEMPLATES_PK); unique identifier for each element template.
• ZD_EDITION_NAME — editioning column; combined with TEMPLATE_ID it forms the documented unique business-key candidate.
• TEMPLATE_TYPE — classifies the template (for example, element template vs. balance template), controlling how the template is applied.
• TEMPLATE_NAME — user-visible name of the template.
• BASE_NAME and MAX_BASE_NAME_LENGTH — control the naming convention and length limit applied when elements are generated from the template.
• BASE_PROCESSING_PRIORITY — default processing priority assigned to generated elements.
• BUSINESS_GROUP_ID — the business group to which the template belongs, establishing the payroll configuration context.
• LEGISLATION_CODE — identifies the legislation (country) for which the template is valid.
• VERSION_NUMBER — tracks the template definition version.
• PREFERENCE_INFO_CATEGORY, PREFERENCE_INFORMATION1..30 — category and thirty generic preference attributes used to hold template-specific configuration values.
• CONFIGURATION_INFO_CATEGORY, CONFIGURATION_INFORMATION1..30 — category and thirty generic configuration attributes that parameterize the generated element behavior.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle framework.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard WHO audit columns.

Common Use Cases and Queries

Payroll administrators and implementation consultants query PAY_ELEMENT_TEMPLATES when diagnosing element generation, comparing template configurations across business groups, or reporting which templates are available for a given legislation. A typical lookup retrieves all templates for a business group and legislation:

• SELECT template_id, template_name, template_type, legislation_code FROM pay_element_templates WHERE business_group_id = :p_bg_id AND legislation_code = :p_leg_code;

Because the generic PREFERENCE_INFORMATION and CONFIGURATION_INFORMATION columns are unlabelled, reporting frequently joins to the dependent definition tables to resolve semantics. A common pattern is to identify templates that include fast formula usage by joining to PAY_TEMPLATE_FF_USAGES on TEMPLATE_ID, or to enumerate which shadow balance types a template will provision by joining to PAY_SHADOW_BALANCE_TYPES. Typical reports include template inventory by legislation, template-to-formula impact analysis, and validation queries that compare a template's base processing priority against the priority actually applied to generated elements.

Because TEMPLATE_ID is the hub key, most diagnostic queries start from this table and fan outward to the five dependent tables, making it the natural anchor for a template lineage report.

Related Objects

Five dependent tables reference PAY_ELEMENT_TEMPLATES through the TEMPLATE_ID foreign key column:

• PAY_SHADOW_BALANCE_TYPES — joins on PAY_SHADOW_BALANCE_TYPES.TEMPLATE_ID = PAY_ELEMENT_TEMPLATES.TEMPLATE_ID; defines shadow balance types created by the template.
• PAY_SHADOW_ELEMENT_TYPES — joins on TEMPLATE_ID; defines the shadow element types associated with the template.
• PAY_TEMPLATE_CORE_OBJECTS — joins on TEMPLATE_ID; lists the core payroll objects included in the template.
• PAY_TEMPLATE_EXCLUSION_RULES — joins on TEMPLATE_ID; captures rules that exclude elements or objects from template application.
• PAY_TEMPLATE_FF_USAGES — joins on TEMPLATE_ID; records which fast formulas the template uses.

Together these objects form the template definition cluster, with PAY_ELEMENT_TEMPLATES serving as the central hub against which each dependent table is joined by TEMPLATE_ID.