Search Results pay_trigger_components_pk




Overview
Explore in AI Chat

Overview

PAY_TRIGGER_COMPONENTS 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 the stored procedures that are executed from dynamic triggers within the Oracle Payroll application. Dynamic triggers allow payroll processing to invoke custom or seeded business logic at specific points in the payroll run lifecycle, and this table acts as the registry that binds each executable component to a triggering event. The table is documented as VALID and contains 13 physical columns in the 12.2.2 ETRM schema.

From a Data Vault modeling perspective, the heuristic classification for PAY_TRIGGER_COMPONENTS is satellite-leaning. This classification is inferred from its foreign key dependency on PAY_TRIGGER_EVENTS and its descriptive attribute set (legislation, business group, module name, enabled flag). It suggests the table behaves primarily as a descriptive satellite hanging off an event-based parent rather than as an independent hub or a pure link. This is offered as a modeling suggestion, not a definitive architectural mandate.

Key Information Stored

The primary key is PAY_TRIGGER_COMPONENTS_PK, defined on COMPONENT_ID. In the documented 12.2.2 physical schema, the unique index also includes ZD_EDITION_NAME, reflecting the multi-tenant editioning column introduced for online patching. The most significant columns are:

  • COMPONENT_ID — Surrogate primary key uniquely identifying each trigger component row.
  • EVENT_ID — Foreign key to PAY_TRIGGER_EVENTS, tying the component to its parent triggering event; this is the central relationship of the table.
  • LEGISLATION_CODE — Restricts the component to a specific legislative jurisdiction.
  • BUSINESS_GROUP_ID — Scopes the component to a particular business group/enterprise.
  • PAYROLL_ID — Associates the component with a specific payroll definition.
  • MODULE_NAME — Identifies the calling module context for the component.
  • ENABLED_FLAG — Controls whether the component is active and eligible for execution.
  • ZD_EDITION_NAME — Editioning column supporting online patching in 12.2.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — Standard EBS audit columns tracking creation and modification.

The business-key candidate is COMPONENT_ID combined with ZD_EDITION_NAME, as reflected in the unique index.

Common Use Cases and Queries

Typical use cases include auditing which procedures fire during payroll processing, diagnosing why a custom payroll hook failed to execute, and reviewing component configuration per legislation or business group. A common query resolves the parent event for each component:

  • SELECT c.COMPONENT_ID, c.EVENT_ID, c.MODULE_NAME, c.ENABLED_FLAG FROM PAY_TRIGGER_COMPONENTS c WHERE c.ENABLED_FLAG = 'Y';
  • Join to the parent event: SELECT c.COMPONENT_ID, e.* FROM PAY_TRIGGER_COMPONENTS c JOIN PAY_TRIGGER_EVENTS e ON c.EVENT_ID = e.EVENT_ID;
  • Filter by business group and legislation: ... WHERE c.BUSINESS_GROUP_ID = :bg AND c.LEGISLATION_CODE = :leg;

Reporting scenarios center on enabled-versus-disabled component inventories, patch impact analysis (via ZD_EDITION_NAME), and troubleshooting dynamic trigger failures by correlating components with events.

Related Objects

The most significant related objects are:

  • PAY_TRIGGER_EVENTS — Parent table referenced by PAY_TRIGGER_COMPONENTS.EVENT_ID; join key is EVENT_ID.
  • PAY_TRIGGER_COMPONENTS_PK — Primary key constraint/index on COMPONENT_ID (with ZD_EDITION_NAME in 12.2.2).
  • PAYROLL_ID references (PER_PAYROLLS / PAY_PAYROLLS_F) — Payroll definition referenced by PAYROLL_ID.
  • BUSINESS_GROUP_ID references (HR_OPERATING_UNITS / PER_BUSINESS_GROUPS) — Enterprise scoping.
  • FND_ application/user tables — Resolve CREATED_BY and LAST_UPDATED_BY audit references.

These relationships position PAY_TRIGGER_COMPONENTS as the executable-logic registry beneath PAY_TRIGGER_EVENTS within the Oracle Payroll dynamic trigger framework.