Results for “audit_type_code”
18 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
PA_EXP_HISTORY_AR is an archive/purge companion table in the Oracle Projects (PA) schema, residing under the PA owner in Oracle E-Business Suite 12.1.1 and 12.2.2. As its name and ETRM description indicate, the table functions as a historical repository for expenditure records that have been moved out of the live transactional tables during an archive-and-purge cycle. The ETRM documentation explicitly states that "Pa_Expenditure_History_ar is a table for Archive/Purge. Refer to comments on the columns in the main table," confirming that its structure mirrors the primary expenditure history table and is populated only when the purge process relocates qualifying rows for retention or removal. Its 37 documented columns preserve the same attribute shape as the live expenditure data, allowing historical audit and reporting without burdening the operational tables.
From a Data Vault modeling perspective, the heuristic classification of this object is standalone, meaning the ETRM extraction did not identify a classic hub-and-satellite pattern in its foreign-key structure. In practice, the table behaves like a snapshot or archive satellite keyed to the originating expenditure, with PURGE_BATCH_ID recording which purge run captured the record.
Key Information Stored
The table is anchored by two documented foreign keys: EXPENDITURE_ID references PA_EXPENDITURES_ALL, and PURGE_BATCH_ID references PA_PURGE_BATCHES_ALL. Together these act as business-key candidates linking an archived row to both its source expenditure and its purge batch. PURGE_RELEASE and PURGE_PROJECT_ID refine the archive context.
- PURGE_BATCH_ID — identifies the purge batch that moved the record into the archive.
- EXPENDITURE_ID — the originating expenditure, joining back to PA_EXPENDITURES_ALL.
- PROJECT_ID, TASK_ID — project and task context for the expenditure.
- EXPENDITURE_CLASS_CODE, EXPENDITURE_SOURCE_CODE, EXPENDITURE_TYPE — classification of the expenditure.
- EXPENDITURE_ITEM_DATE — the accounting-relevant date of the item.
- INCURRED_BY_PERSON_ID — the person who incurred the cost.
- QUANTITY — the units associated with the expenditure.
- AUDIT_TYPE_CODE, LATE_ENTRY_CODE, AUDIT_ORDER — audit and sequence attributes carried over from the source.
- ADJUSTED_EXPENDITURE_ITEM_ID and DENORM_ID — adjustment and denormalized reference identifiers.
- ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE10 — the standard EBS descriptive flexfield columns.
- CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard WHO audit columns.
Common Use Cases and Queries
Typical use cases center on reconciliation and compliance reporting: confirming which expenditures a given purge run archived, reconstructing historical project cost detail, and validating that live expenditures were retired correctly. A join returning the source expenditure and batch is common:
SELECT h.EXPENDITURE_ID, h.PROJECT_ID, h.EXPENDITURE_TYPE,
h.EXPENDITURE_ITEM_DATE, b.PURGE_BATCH_ID
FROM PA.PA_EXP_HISTORY_AR h, PA.PA_PURGE_BATCHES_ALL b
WHERE h.PURGE_BATCH_ID = b.PURGE_BATCH_ID
AND h.PROJECT_ID = :project_id;
Reconciling archived against live expenditures uses the EXPENDITURE_ID relationship to PA_EXPENDITURES_ALL. Reporting on archived costs for a closed project is another frequent pattern, as is auditing adjustment history via AUDIT_TYPE_CODE and ADJUSTED_EXPENDITURE_ITEM_ID.
Related Objects
- PA_EXPENDITURES_ALL — referenced via EXPENDITURE_ID; the live counterpart to archived rows.
- PA_PURGE_BATCHES_ALL — referenced via PURGE_BATCH_ID; defines each purge run.
- PA_EXPENDITURE_ITEMS_ALL — associated detail items linked through expenditure identifiers.
- PA_PROJECTS_ALL — supplies PROJECT_ID project context.
- PA_TASKS — supplies TASK_ID context.
- PA_PURGE_PROJECTS — project-scope definitions relevant to PURGE_PROJECT_ID.
- PER_ALL_PEOPLE_F — resolves INCURRED_BY_PERSON_ID.
Because the table is populated only through the archive/purge process, report and integration logic should treat it as an appendix to the primary expenditure tables rather than an operational source of record.
-
Pa_Expenditure_History_ar is a table for Archive/Purge. Refer to comments on the columns in the main table
-
Audit records for self service time
-
Audit records for self service time
-
Pa_Expenditure_History_ar is a table for Archive/Purge. Refer to comments on the columns in the main table
-
VIEW: PA.PA_EXP_HISTORY_AR# 12.2.2
-
VIEW: PA.PA_EXP_HISTORY_AR# 12.2.2
-
TABLE: PA.PA_EXP_HISTORY_AR 12.1.1
-
TABLE: PA.PA_EXP_HISTORY_AR 12.2.2
-
eTRM - PA Tables and Views 12.1.1
-
eTRM - PA Tables and Views 12.2.2