Results for “pay_xla_events_pk”

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

Overview

HR.PAY_XLA_EVENTS is a transactional table in the Oracle E-Business Suite 12.1.1 and 12.2.2 data model that stores payroll subledger accounting events. As documented in the ETRM metadata, its functional purpose is "Payroll support for sub ledger accounting." In the Oracle Payroll architecture, this table acts as the bridge between payroll run processing and the Subledger Accounting (SLA) engine, capturing the discrete accounting events that arise from assignment-level payroll actions and feeding them into the accounting and posting pipeline. The object is owned by the HR schema, is registered under FND Design Data as PAY.PAY_XLA_EVENTS, holds VALID status, and resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10.

From a dimensional modeling perspective, the mined foreign key structure classifies this object as a heuristic Data Vault hub candidate. Its single foreign key relationship to PAY_ASSIGNMENT_ACTIONS, combined with the absence of incoming foreign key references documented in the dependency data, suggests the table functions as a standalone event anchor rather than a pure link or satellite. This classification is offered strictly as a modeling suggestion; the operational reality is that the table behaves as a transactional event ledger.

Key Information Stored

The documented physical schema contains four columns, centering on the event identity and its association to a payroll action:

• EVENT_ID — NUMBER(15). The surrogate primary key and unique identifier for the table, enforced by the unique index PAY_XLA_EVENTS_PK. This is the single documented business-key candidate per the ETRM metadata.
• ASSIGNMENT_ACTION_ID — NUMBER(15). Foreign key to the PAY_ASSIGNMENT_ACTIONS table, linking each accounting event to the specific assignment-level payroll action that generated it. Indexed non-uniquely via PAY_XLA_EVENTS_FK1.
• ACCOUNTING_DATE — DATE. The accounting date associated with the event, used for period and General Ledger date determination. Indexed through PAY_XLA_EVENTS_FK1.
• EVENT_STATUS — VARCHAR2. The processing status of the event within the subledger accounting lifecycle.

The primary key is the surrogate identifier EVENT_ID; the ASSIGNMENT_ACTION_ID and ACCOUNTING_DATE pair serves as the principal access path for reporting and joins.

Common Use Cases and Queries

Typical scenarios include reconciling payroll results to subledger accounting entries, tracing assignment actions to their generated accounting events, and auditing event status across accounting periods. A foundational query pattern follows the documented query text:

• Retrieve all events for a given assignment action: SELECT EVENT_ID, ASSIGNMENT_ACTION_ID, ACCOUNTING_DATE, EVENT_STATUS FROM HR.PAY_XLA_EVENTS WHERE ASSIGNMENT_ACTION_ID = :action_id;
• Report events by accounting period: SELECT EVENT_STATUS, COUNT(*) FROM HR.PAY_XLA_EVENTS WHERE ACCOUNTING_DATE BETWEEN :start_date AND :end_date GROUP BY EVENT_STATUS;
• Join to assignment actions for detail enrichment: SELECT e.EVENT_ID, e.ACCOUNTING_DATE, a.* FROM HR.PAY_XLA_EVENTS e, HR.PAY_ASSIGNMENT_ACTIONS a WHERE e.ASSIGNMENT_ACTION_ID = a.ASSIGNMENT_ACTION_ID;

Related Objects

The significant related objects, grounded in the documented dependency and relationship data, include:

• HR.PAY_ASSIGNMENT_ACTIONS — the parent object referenced by the ASSIGNMENT_ACTION_ID foreign key; the primary join partner.
• HR.PAY_XLA_EVENTS# — documented as a dependent object referenced by this table.
• PAY_XLA_EVENTS_PK — the unique index on EVENT_ID.
• PAY_XLA_EVENTS_FK1 — the non-unique index on ASSIGNMENT_ACTION_ID and ACCOUNTING_DATE, the dominant query path.

These objects, together with the Subledger Accounting and payroll run interfaces that consume the events, constitute the immediate dependency neighborhood for this table.