Results for “accounting_date”

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

Overview

PAY_XLA_EVENTS is a payroll subledger event table owned by the HR schema in Oracle E-Business Suite. It serves as the bridge between payroll processing activity and the Oracle Subledger Accounting (XLA) engine, capturing the accounting-relevant events generated when payroll runs, assignment actions, and related transactions are processed. In Release 12.1.1 and 12.2.2, this table is integral to the flow that produces payroll journal entries through Subledger Accounting, allowing payroll costs to be transferred to General Ledger with full drill-down capability.

From a Data Vault modeling perspective, the mined FK structure classifies PAY_XLA_EVENTS as a standalone table. This heuristic suggests treating it as a self-contained hub-like entity with no downstream foreign key dependencies within the documented schema, meaning its relationships are largely defined by how external processes consume it rather than by intrinsic link chains.

Key Information Stored

The table contains four documented columns in the ETRM 12.2.2 schema, each carrying significant functional meaning:

• EVENT_ID — The surrogate primary key, uniquely identifying each payroll subledger event. It is enforced by the unique index PAY_XLA_EVENTS_PK and is the business-key candidate for row-level identification.
• ASSIGNMENT_ACTION_ID — A foreign key referencing PAY_ASSIGNMENT_ACTIONS. This links the event to the specific assignment action (such as a payroll run action, reversal, or adjustment) that generated it, providing the operational context for the accounting entry.
• ACCOUNTING_DATE — The date on which the event is recognized for accounting purposes. This drives period assignment and cutoff logic in Subledger Accounting and General Ledger transfer.
• EVENT_STATUS — Indicates the processing state of the event within the XLA pipeline (for example, whether it has been accounted, transferred, or is pending). This governs the timing of journal creation and GL posting.

Because the documented column list is concise, the table functions as a compact event registry rather than a wide descriptive entity; the detailed accounting attributes are typically held in companion XLA tables keyed by EVENT_ID.

Common Use Cases and Queries

Typical uses include reconciling payroll costs to GL, auditing the accounting event lifecycle, and diagnosing why a payroll run failed to create journal entries. A representative query joins the event to its source assignment action:

• Identify unaccounted events: SELECT e.event_id, e.assignment_action_id, e.accounting_date, e.event_status FROM pay_xla_events e WHERE e.event_status = '<status>';
• Trace events to payroll actions: SELECT e.event_id, a.assignment_action_id, a.action_type FROM pay_xla_events e, pay_assignment_actions a WHERE e.assignment_action_id = a.assignment_action_id AND e.accounting_date BETWEEN :start_date AND :end_date;
• Period-end reconciliation: aggregate counts and accounting dates per period to verify that all payroll events for the period have been transferred.

Because the schema documentation is limited to four columns, reporting on additional attributes generally requires joining to the XLA event and accounting tables, where the event identifier is carried forward.

Related Objects

• PAY_ASSIGNMENT_ACTIONS — Referenced via ASSIGNMENT_ACTION_ID; the immediate parent of each payroll event.
• PAY_RUN_RESULTS — Holds the calculated payroll results that feed event creation.
• XLA_EVENTS — The generic Subledger Accounting event table where payroll events are propagated for accounting.
• XLA_AE_HEADERS / XLA_AE_LINES — Store the journal headers and lines created from these events.
• PAY_XLA_EVENTS_PK — The unique index on EVENT_ID guaranteeing event uniqueness.
• GL_JE_HEADERS / GL_JE_LINES — Final destination of payroll accounting after transfer from Subledger Accounting.