Results for “authorized_by”

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

Overview

XTR_BATCH_EVENTS is a Treasury (XTR) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that records the individual events executed within a parent batch process. Where XTR_BATCHES captures the batch header and overall run context, XTR_BATCH_EVENTS captures the granular, per-event detail that makes up a single batch execution. This parent-child structure allows the Treasury batch framework to group many discrete actions under one logical run, while retaining event-level traceability for authorization, timing, and user accountability.

Based on the documented foreign key structure and the heuristic Data Vault classification supplied in the ETRM metadata, XTR_BATCH_EVENTS is best modeled as satellite-leaning. This is a modeling suggestion only: the table does not function as an independent hub, since its identity depends on an owning batch, but it does carry descriptive and status attributes (event code, authorization flags, audit columns) that more closely resemble a satellite than a pure link. The primary key XTR_BATCH_EVENTS_PK on BATCH_EVENT_ID provides the unique surrogate identity for each event row.

Key Information Stored

The table contains 11 documented columns. The most significant are:

• BATCH_EVENT_ID — the surrogate primary key (XTR_BATCH_EVENTS_PK) uniquely identifying each event.
• BATCH_ID — foreign key to XTR_BATCHES, tying each event to its parent batch.
• EVENT_CODE — the business code identifying the type of event recorded. Together with BATCH_ID, it forms the unique index XTR_BATCH_EVENTS_U1 (BATCH_ID, EVENT_CODE), making it a business-key candidate.
• AUTHORIZED — flag indicating whether the event has been authorized.
• AUTHORIZED_BY — the user who authorized the event.
• AUTHORIZED_ON — the date/time the event was authorized.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns tracking row creation and modification.

The distinction between the surrogate PK (BATCH_EVENT_ID) and the business-key candidate (BATCH_ID + EVENT_CODE) matters for deduplication logic and integration design.

Common Use Cases and Queries

Typical scenarios include reporting on batch execution detail, checking authorization status of events, and auditing who authorized a given event and when. A common query joins events to their parent batch:

• List all events for a batch: SELECT * FROM XTR.XTR_BATCH_EVENTS WHERE BATCH_ID = :batch_id;
• Find unauthorized events: SELECT BATCH_ID, EVENT_CODE FROM XTR.XTR_BATCH_EVENTS WHERE AUTHORIZED = 'N' OR AUTHORIZED IS NULL;
• Authorization audit: SELECT BATCH_ID, EVENT_CODE, AUTHORIZED_BY, AUTHORIZED_ON FROM XTR.XTR_BATCH_EVENTS WHERE AUTHORIZED_BY = :user_id;
• Batch summary by event: SELECT BATCH_ID, COUNT(*) FROM XTR.XTR_BATCH_EVENTS GROUP BY BATCH_ID;

These patterns support reconciliation, exception reporting, and compliance review of Treasury batch activity.

Related Objects

• XTR_BATCHES — the parent table; joined via XTR_BATCH_EVENTS.BATCH_ID = XTR_BATCHES.BATCH_ID. This is the only documented foreign key.
• XTR_BATCH_EVENTS_PK — the primary key constraint on BATCH_EVENT_ID.
• XTR_BATCH_EVENTS_U1 — the unique index on (BATCH_ID, EVENT_CODE).
• Standard EBS audit/concurrent objects (FND_USER via CREATED_BY/AUTHORIZED_BY) are commonly referenced in reporting joins.

Because the metadata documents a single foreign key, XTR_BATCHES is the principal dependency; other relationships are inferred from the audit and authorization columns.