Results for “activity_date”

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

Overview

The PA_EXPEND_ITEM_ADJ_ACTIVITIES table is a Projects module audit and tracking table that records information about cost and/or revenue adjustments applied to expenditure items through Oracle Projects forms. This table captures the activity history surrounding adjustment processing, including the nature of each adjustment activity, the module from which it originated, and any exception or rejection conditions encountered during processing. Its documented description in ETRM is: "Information about cost and/or revenue adjustments made to expenditure items through the Oracle Projects forms."

From a Data Vault modeling perspective, the metadata's heuristic classification identifies this table as a link. This is consistent with its role as an association between an expenditure item and an adjustment activity event, carrying descriptive attributes that describe the activity itself. The link classification reflects the pairing of EXPENDITURE_ITEM_ID and ACTIVITY_DATE as the composite primary key (EXPEND_ITEM_ADJ_ACTIVITIES_PK), which binds the expenditure item to a point-in-time adjustment activity.

Key Information Stored

The table contains 15 documented columns in Oracle EBS 12.2.2. The most significant are:

• EXPENDITURE_ITEM_ID — Foreign key to PA_EXPENDITURE_ITEMS_ALL; identifies the expenditure item to which the adjustment activity pertains. Part of the composite primary key.
• ACTIVITY_DATE — The date of the adjustment activity; the second component of the composite primary key (EXPEND_ITEM_ADJ_ACTIVITIES_PK). Together with EXPENDITURE_ITEM_ID, it forms the business-key candidate for a unique record.
• EXCEPTION_ACTIVITY_CODE — Code describing any exception condition encountered during adjustment processing.
• MODULE_CODE — Identifies the Oracle Projects module or process that generated the adjustment activity.
• REJECTION_CODE — Code indicating why an adjustment activity was rejected, if applicable.
• DESCRIPTION — Free-text description of the adjustment activity.
• REQUEST_ID — Concurrent request identifier associated with the activity, useful for tracing to a specific batch run.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Standard concurrent program context identifying the program that last updated the row.
• CREATED_BY — Foreign key to FND_USER; the user who created the record.
• CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns tracking creation and modification.

The composite primary key uses natural business columns (EXPENDITURE_ITEM_ID, ACTIVITY_DATE) rather than a surrogate identifier, so there is no single surrogate key in the documented schema.

Common Use Cases and Queries

Typical scenarios include auditing adjustment activity per expenditure item, diagnosing rejected or exception adjustments, and reconciling concurrent program runs that touched expenditure adjustments. A representative query joins the table to the expenditure item and user masters:

• Retrieving all adjustment activities for an item: SELECT * FROM pa.pa_expend_item_adj_activities WHERE expenditure_item_id = :id ORDER BY activity_date;
• Identifying rejected adjustments: SELECT expenditure_item_id, activity_date, rejection_code, exception_activity_code FROM pa.pa_expend_item_adj_activities WHERE rejection_code IS NOT NULL;
• Joining to the item master for project context: SELECT a.expenditure_item_id, a.activity_date, a.module_code, i.project_id FROM pa.pa_expend_item_adj_activities a, pa.pa_expenditure_items_all i WHERE a.expenditure_item_id = i.expenditure_item_id;
• Joining to FND_USER to identify the creating user: SELECT a.expenditure_item_id, u.user_name FROM pa.pa_expend_item_adj_activities a, applsys.fnd_user u WHERE a.created_by = u.user_id;
• Tracing activities to a concurrent request: SELECT * FROM pa.pa_expend_item_adj_activities WHERE request_id = :request_id;

These patterns support audit reporting, exception monitoring, and troubleshooting of adjustment processing within Oracle Projects.

Related Objects

• PA_EXPENDITURE_ITEMS_ALL — Referenced via PA_EXPEND_ITEM_ADJ_ACTIVITIES.EXPENDITURE_ITEM_ID; the parent expenditure item master. All adjustment activities relate to an expenditure item in this table.
• FND_USER — Referenced via PA_EXPEND_ITEM_ADJ_ACTIVITIES.CREATED_BY; identifies the user who created the adjustment activity record.
• PA_EXPEND_ITEM_ADJUSTMENTS — Closely related expenditure adjustment table, typically joined on EXPENDITURE_ITEM_ID to correlate adjustment amounts with adjustment activities.
• PA_EXPENDITURE_ITEMS — Synonym/view aliasing the expenditure items master for read access.
• FND_CONCURRENT_REQUESTS — Joins on REQUEST_ID to trace the concurrent program execution that produced the activity.
• FND_APPLICATION and FND_CONCURRENT_PROGRAMS — Join on PROGRAM_APPLICATION_ID and PROGRAM_ID to identify the program context.

The primary relationship structure centers on PA_EXPENDITURE_ITEMS_ALL and FND_USER, as documented in the foreign key metadata.