Results for “change_code”

6 results




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

Overview

PA_EXPENDITURE_HISTORY_V is an APPS-schema database view in the Oracle E-Business Suite Projects (PA) module. Its documented purpose is to support the Online Expenditure Entry Form, where it provides the historical audit trail of changes made to expenditure items. Every time a user adjusts, reverses, or otherwise modifies an expenditure item through the online entry form, a corresponding history row is captured and exposed through this view for display and review.

Functionally, the view presents a denormalized, presentation-ready record of expenditure change history: it joins the raw history table to project, task, employee, and lookup information so that a form or report can render meaningful descriptions (project name, task name, employee name, and a translated change reason) rather than internal numeric identifiers. As a view rather than a table, it stores no data of its own; it is a read-only query layer over the PA_EXPENDITURE_HISTORY base object. Because it is owned by APPS and relies on PA security-aware underlying views, it participates in the standard Oracle EBS multi-organization and project security model. In 12.1.1 and 12.2.2 the object remains VALID and its definition is unchanged between the two releases for the documented columns.

Underlying Base Objects

The view text selects from five primary database objects joined together:

The documented metadata further lists supporting packages invoked by the underlying security views: FND_PROFILE, HR_GENERAL, HR_PERSON_NAME, HR_SECURITY, PA_CROSS_BUSINESS_GRP, PA_PROJECT_UTILS, PA_TASK_UTILS, and PA_UTILS4. These provide profile-option resolution, person-name formatting, and cross-business-group security filtering that govern which projects, tasks, and employees a given user may see.

Key Columns

The view exposes the full set of history and descriptive attributes. Notable columns include:

Common Use Cases and Queries

Typical uses include reviewing the change history of a specific expenditure item in a custom form or concurrent report, auditing who adjusted which expenditures and why, and reconciling adjustments for a project or date range. Because the view is already joined and security-filtered, it is convenient for ad hoc reporting in Oracle Projects.

Example: retrieve the change history for a given expenditure item.

  • SELECT expenditure_id, adjusted_expenditure_item_id, change_meaning, employee_name, expenditure_item_date, quantity, expenditure_item_comment, creation_date FROM apps.pa_expenditure_history_v WHERE expenditure_id = :p_expenditure_id ORDER BY creation_date DESC;

Example: list changes by project and date range for audit purposes.

  • SELECT project_number, project_name, task_number, employee_name, change_meaning, expenditure_item_date, creation_date FROM apps.pa_expenditure_history_v WHERE project_id = :p_project_id AND creation_date BETWEEN :p_from AND :p_to ORDER BY project_number, creation_date;

Because row visibility is governed by PA project and HR security plus FND profile options, results automatically respect the querying user's access. Analysts should note that use of TRUNC(SYSDATE) in the employee join means name data reflects only currently effective employee records, and that CHANGE_MEANING depends on the ONLINE_EXP_CHANGE_REASON lookup being populated.