Results for “pay_template_core_objects_uk1”

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

Overview

PAY_TEMPLATE_CORE_OBJECTS is a Payroll (PAY) module table owned by the HR schema. It serves as the metadata registry that tracks the core database schema objects generated whenever an element template is instantiated into a payroll element. In Oracle EBS, element templates define the reusable definition of a payroll element — its input values, calculation rules, and associated processing — and when a template is applied, the payroll engine physically creates supporting database objects (tables, views, indexes, or similar artifacts) to store and process element data. PAY_TEMPLATE_CORE_OBJECTS records the linkage between each template and the underlying core objects it spawned, providing the traceability needed for element maintenance, upgrades, and template reapplication.

From a Data Vault modeling perspective, the table exhibits satellite-leaning characteristics. Its structure is anchored by a surrogate primary key and a foreign key to a parent template entity, with no downstream tables referencing it as a hub or link. This suggests the table functions primarily as a descriptive, history-bearing extension to the element template definition rather than as a central business key repository. Modelers should treat it as an attribute satellite attached to PAY_ELEMENT_TEMPLATES, with effective-dating handled through the EFFECTIVE_DATE and audit columns.

Key Information Stored

The table contains twelve documented columns. The most significant include:

• TEMPLATE_CORE_OBJECT_ID — Surrogate primary key (PAY_TEMPLATE_CORE_OBJECTS_PK) uniquely identifying each row.
• TEMPLATE_ID — Foreign key to PAY_ELEMENT_TEMPLATES, identifying the source element template that produced the core object.
• CORE_OBJECT_TYPE — Classification of the generated schema object (e.g., table, view, synonym). Combines with CORE_OBJECT_ID to form the unique business key PAY_TEMPLATE_CORE_OBJECTS_UK1.
• CORE_OBJECT_ID — Identifier of the generated core object within its type category.
• SHADOW_OBJECT_ID — Reference to a shadow (staging or mirror) counterpart object, used during template reapplication and upgrade processing.
• EFFECTIVE_DATE — Date from which the object registration is effective, supporting date-tracked history.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Applications framework for concurrent update control.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE provide standard who-column tracking.

The surrogate key (TEMPLATE_CORE_OBJECT_ID) is distinct from the business-key candidate exposed by PAY_TEMPLATE_CORE_OBJECTS_UK1 (CORE_OBJECT_TYPE, CORE_OBJECT_ID), which enforces uniqueness of the generated object identity.

Common Use Cases and Queries

Typical scenarios include diagnosing element template failures, auditing which core objects exist for a given template, and validating template reapplication or upgrade scripts.

• Identify all core objects generated by a specific template:

  SELECT core_object_type, core_object_id, effective_date
  FROM   pay_template_core_objects
  WHERE  template_id = :template_id;

• Locate the template responsible for a registered object:

  SELECT template_id, shadow_object_id
  FROM   pay_template_core_objects
  WHERE  core_object_type = :type
  AND    core_object_id  = :object_id;

• Audit recent changes to template-generated objects:

  SELECT template_core_object_id, last_updated_by, last_update_date
  FROM   pay_template_core_objects
  WHERE  last_update_date > SYSDATE - 30;

These queries support payroll administrators investigating orphaned schema objects, migration teams reconciling templates between instances, and DBAs validating post-patch integrity of payroll element definitions.

Related Objects

• PAY_ELEMENT_TEMPLATES — Parent table joined via PAY_TEMPLATE_CORE_OBJECTS.TEMPLATE_ID = PAY_ELEMENT_TEMPLATES.TEMPLATE_ID; defines the template that generated the core objects.
• PAY_ELEMENT_TEMPLATE_INPUTS — Sibling definition of input values for the same template, useful when jointly analyzing element structure.
• PAY_ELEMENTS — Elements instantiated from templates; references the template lineage tracked here.
• PAY_ELEMENT_TYPES — Classifies the element type to which generated objects belong.
• FND_TABLES / FND_OBJECTS — Oracle Applications metadata registries that describe named schema objects referenced by CORE_OBJECT_ID.
• HR_API hooks and PAY_ELEMENT_TEMPLATE APIs — Public APIs (e.g., PAY_ELEMENT_TEMPLATE_API) that create and maintain the records in this table during template processing.