Results for “batch_date”

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

Overview

PA_EXPENDITURE_BATCHES_ALL is a Projects (PA) module table in Oracle E-Business Suite, owned by the PA schema and valid in both 12.1.1 and 12.2.2. It stores groups of expense reports that are processed together during the same run of the Distribute Expense Reports program. Each row represents an expenditure batch — a logical grouping used to control and audit the cost distribution process that pushes expense report costs from Oracle Payables into Oracle Projects. The _ALL suffix indicates the table is partitioned by operating unit through the ORG_ID column, enforcing multi-org security at the row level.

From a Data Vault modeling perspective, the mined FK structure classifies this object as satellite-leaning. The table describes attributes and lifecycle status of a batch rather than acting as a pure hub or a pure link, making it a candidate for a satellite constructed around a batch business key.

Key Information Stored

The table documents ten columns. The primary key is PA_EXPENDITURE_BATCHES_PK, defined over (BATCH_NAME, ORG_ID). A unique index, PA_EXPENDITURE_BATCHES_U1, is defined over the same two columns, confirming BATCH_NAME as the business-key candidate scoped to operating unit.

• BATCH_NAME — Surrogate and business identifier of the batch; the value used by downstream cost distribution lines to reference the batch.
• ORG_ID — Operating unit that owns the batch; combined with BATCH_NAME it forms the primary key.
• BATCH_STATUS_CODE — Lifecycle status of the batch run (for example, whether it is open, processed, or closed), governing whether further distribution is permitted.
• BATCH_DATE — Effective date of the batch, typically used for reporting and reconciliation against the distribution run.
• BATCH_SOURCE — Source classification of the batch, referencing PA_BATCH_SOURCES; identifies the origin system or process that created the batch.
• CREATED_BY, CREATION_DATE — Audit stamp of the user and time of batch creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns tracking the most recent modification.

Common Use Cases and Queries

Typical usage centers on reconciliation and audit of the Distribute Expense Reports concurrent program. Analysts list batches by operating unit and status, trace all cost distribution lines produced by a batch, or reconcile batch volume against the interface into Oracle Projects.

A representative query joins batches to their distribution lines:

• SELECT b.batch_name, b.org_id, b.batch_status_code, b.batch_date, b.batch_source
• FROM pa_expenditure_batches_all b
• WHERE b.org_id = :p_org_id
• ORDER BY b.batch_date DESC;

To audit the lines belonging to a batch:

• SELECT l.batch_name, l.org_id, COUNT(*)
• FROM pa_cost_distribution_lines_all l
• WHERE l.batch_name = :p_batch_name AND l.org_id = :p_org_id
• GROUP BY l.batch_name, l.org_id;

Reporting frequently filters on BATCH_SOURCE to separate batches created by different feeders, and on BATCH_STATUS_CODE to isolate batches pending processing.

Related Objects

The documented foreign-key relationships tie this table to the following objects:

• PA_BATCH_SOURCES — Referenced by PA_EXPENDITURE_BATCHES_ALL.BATCH_SOURCE; defines the valid batch source codes.
• PA_COST_DISTRIBUTION_LINES_ALL — References this table through BATCH_NAME and ORG_ID; holds the individual cost distribution lines generated per batch.
• PA_EXPENDITURE_BATCHES_PK — Primary key constraint over (BATCH_NAME, ORG_ID).
• PA_EXPENDITURE_BATCHES_U1 — Unique index over (BATCH_NAME, ORG_ID) supporting the business key.
• Distribute Expense Reports concurrent program — The core PA process that creates and consumes these batches.

These relationships establish the batch as the parent grouping for cost distribution activity, with ORG_ID propagating multi-org context across all dependent records.