Results for “projfunc_revenue_amount”

50+ results




Overview
Explore in AI Chat

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

Overview

PA_DRAFT_REV_ITEMS_AR is an Oracle E-Business Suite table owned by the PA (Projects) schema. Its name and structure identify it as the archive/purge companion of the transactional draft revenue items table. Oracle EBS implements archive and purge operations by copying qualifying rows into an _AR shadow table before the source rows are deleted, so the data survives for audit, retention, and regulatory purposes while the live table remains lean. As the ETRM documentation states, Pa_Draft_Revenue_Items_ar is a table for Archive/Purge, and its column comments mirror those of the main table.

The table holds 26 documented columns in release 12.2.2. Its Data Vault classification, derived heuristically from its foreign key structure, is standalone. The only documented foreign key is PURGE_BATCH_ID referencing PA_PURGE_BATCHES_ALL. This is a modeling suggestion rather than a definitive tag: functionally the table behaves as a satellite of the draft revenue item it archives, with the purge batch acting as the parent context. Because archived rows are frozen at the point of purge, referential integrity to live transactional tables is not enforced.

Key Information Stored

The most important columns fall into three groups: purge control, project/revenue identity, and multi-currency amounts.

Common Use Cases and Queries

Typical usage is investigative or reconciliation-based rather than transactional. Analysts query archived rows when a draft revenue line has been purged from the live table but must still be traced. A representative pattern joins the archive back to its purge batch:

  • Retrieve all archived lines for one purge run: SELECT * FROM pa.pa_draft_rev_items_ar WHERE purge_batch_id = :batch_id;
  • Trace a specific project's archived revenue: SELECT project_id, draft_revenue_num, line_num, amount FROM pa.pa_draft_rev_items_ar WHERE purge_project_id = :project_id ORDER BY draft_revenue_num, line_num;
  • Reconcile purged releases: SELECT purge_release, COUNT(*) FROM pa.pa_draft_rev_items_ar GROUP BY purge_release;
  • Audit currency amounts: compare PROJFUNC_REVENUE_AMOUNT against PROJECT_REVENUE_AMOUNT for archived lines.

Because there is no documented unique key, queries should not assume row uniqueness; filtering by PURGE_BATCH_ID is the most reliable scoping predicate.

Related Objects

The following objects are the most significant to consider alongside this table:

  • PA_PURGE_BATCHES_ALL — parent of the documented FK via PURGE_BATCH_ID; defines each archive/purge run.
  • PA_DRAFT_REV_ITEMS — the live source table from which rows are archived; shares the same column semantics.
  • PA_DRAFT_REVENUES_ALL — header table referenced by DRAFT_REVENUE_NUM and PROJECT_ID.
  • PA_PROJECTS_ALL — supplies PROJECT_ID / PURGE_PROJECT_ID context.
  • PA_TASKS — resolves TASK_ID to a project task.
  • PA_PURGE_PROJECTS — associates projects with purge batches.
  • Archive/purge concurrent programs and the PA purge APIs that populate these rows.

Together these objects allow a complete audit trail from purge batch, through project and task, to the archived multi-currency revenue line.