Results for “expenditure_group_status_code”

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

Overview

PA_EXPENDITURE_GROUPS_ALL is an Oracle Projects (PA) table that stores groups of pre-approved expenditures. Each row defines an expenditure group header, identified by the combination of EXPENDITURE_GROUP and ORG_ID. Expenditure groups are used throughout Oracle Projects to batch, control, and approve transaction expenditures before they are imported, distributed, or interfaced into other applications such as General Ledger, Payables, or Grants Accounting. The table is an _ALL table, meaning it is partitioned by operating unit through the ORG_ID column and is filtered by Multi-Org security in EBS 12.1.1 and 12.2.2.

From a Data Vault modeling perspective, the heuristic classification provided in the metadata is satellite-leaning. The table primarily holds descriptive and status-bearing attributes of a business entity (the expenditure group), rather than acting as a pure hub or link. It references lookup and control entities (PA_SYSTEM_LINKAGES, PA_TRANSACTION_SOURCES), which reinforces its role as a descriptive satellite attached to candidate hubs such as operating unit and transaction source.

Key Information Stored

The documented physical schema contains 19 columns. The most significant include:

• EXPENDITURE_GROUP — business name/identifier of the group; part of the primary key and unique index.
• ORG_ID — operating unit identifier; part of the primary key and unique index, enforcing Multi-Org partitioning.
• EXPENDITURE_GROUP_STATUS_CODE — lifecycle state of the group (e.g., unapproved, approved, processed).
• EXPENDITURE_ENDING_DATE — cutoff date for expenditures eligible to be included in the group.
• SYSTEM_LINKAGE_FUNCTION — foreign key to PA_SYSTEM_LINKAGES, defining the downstream system/flexfield linkage used at processing time.
• TRANSACTION_SOURCE — foreign key to PA_TRANSACTION_SOURCES, indicating the origin of expenditures in the group.
• CONTROL_COUNT — number of transactions controlled by the group.
• CONTROL_TOTAL_AMOUNT — monetary total controlled by the group.
• DESCRIPTION — free text describing the group.
• PERIOD_ACCRUAL_FLAG — controls whether period-end accrual is applied.
• LAST_UPDATE_DATE / LAST_UPDATED_BY / CREATION_DATE / CREATED_BY — standard WHO audit columns.
• REQUEST_ID / PROGRAM_ID / PROGRAM_APPLICATION_ID / PROGRAM_UPDATE_DATE — concurrent program audit context.

The surrogate primary key is PA_EXPENDITURE_GROUPS_PK (EXPENDITURE_GROUP, ORG_ID). A unique business-key index, PA_EXPENDITURE_GROUPS_U1, mirrors the same column pair. The table is referenced by PA_EXPENDITURES_ALL via EXPENDITURE_GROUP and ORG_ID.

Common Use Cases and Queries

Typical usage covers approval workflows, interface processing, and reconciliation reporting. Analysts frequently need to list approved expenditure groups still holding unprocessed transactions, or to reconcile group control totals against actual expenditures.

Illustrative query joining header to detail:

• SELECT g.expenditure_group, g.org_id, g.expenditure_group_status_code, g.control_count, g.control_total_amount
• FROM pa_expenditure_groups_all g
• WHERE g.org_id = :p_org_id AND g.expenditure_group_status_code = 'APPROVED'
• ORDER BY g.expenditure_group;

Reconciliation against detail expenditures:

• SELECT g.expenditure_group, g.control_total_amount, SUM(e.expenditure_amount) actual
• FROM pa_expenditure_groups_all g, pa_expenditures_all e
• WHERE g.expenditure_group = e.expenditure_group AND g.org_id = e.org_id
• GROUP BY g.expenditure_group, g.control_total_amount;

Other uses include driving concurrent programs that import, distribute, or interface expenditures, and auditing who created or modified groups via the WHO columns.

Related Objects

• PA_EXPENDITURES_ALL — child table holding individual expenditures; joins on EXPENDITURE_GROUP and ORG_ID.
• PA_SYSTEM_LINKAGES — referenced via SYSTEM_LINKAGE_FUNCTION; defines downstream system linkage.
• PA_TRANSACTION_SOURCES — referenced via TRANSACTION_SOURCE; defines expenditure origin.
• PA_EXPENDITURE_GROUPS_PK / U1 — primary key and unique index enforcing the group/org uniqueness.
• Oracle Projects Expenditure Group APIs — PL/SQL packages (e.g., PA_EXPENDITURE_GROUP_PKG-style utilities) used to create, approve, and process groups.