Search Results org_info




Overview
Explore in AI Chat

Overview

PA_ALLOC_TXN_ACCUM_V is an Oracle E-Business Suite view owned by the APPS schema in the Projects (PA) product family. It presents a consolidated, allocation-oriented picture of project transaction accumulations, and it serves as a reporting and integration bridge between native Oracle Projects accumulation data and accumulation data sourced from an external project integration feed — specifically the "PJI" flow represented by the PJI_FP_XBS_ACCUM_F table. The view is defined as a UNION ALL of two branches, distinguished by a derived RECORD_SOURCE column that carries the value 'PA' for the native Oracle Projects branch and 'PJI' for the external integration branch.

The view is available in both Oracle EBS 12.1.1 and 12.2.2; the documented metadata in ETRM 12.2.2 confirms it remains VALID with the structure described here. Its principal role is to provide a single queryable surface through which both native and externally sourced transaction accumulation figures can be reported side by side using a consistent set of column names and semantic meanings. The user search term "pji_fp_xbs_accum_f" corresponds directly to one of the view's underlying base objects, indicating that this view is the standard entry point for reporting against that integration table.

Underlying Base Objects

The view is defined over the following documented objects, all resolved through APPS synonyms or views:

  • PA_TXN_ACCUM (SYNONYM) — the native Oracle Projects transaction accumulation table, providing the 'PA' branch of the union.
  • PJI_FP_XBS_ACCUM_F (SYNONYM) — the external project integration accumulation fact table, providing the source rows for the 'PJI' branch through an inline aggregation subquery.
  • PA_PROJECTS_ALL (SYNONYM) — joined to both branches to restrict or relate the accumulation rows to valid project definitions. The 'PA' branch explicitly filters on PJI_SOURCE_FLAG IS NULL.
  • PJI_ORG_EXTR_INFO (SYNONYM) — participation in the PJI branch, supplying organizational extraction context.
  • PJI_TIME_CAL_PERIOD_V (VIEW) — used in the PJI branch to resolve the PA_PERIOD value from the external calendar period information.

The union therefore merges per-project, per-task, per-period accumulation rows from the native PA model with aggregated rows derived from the PJI fact table.

Key Columns

Common Use Cases and Queries

Typical uses include reconciliation between native PA accumulations and external PJI-sourced accumulations, cross-source reporting of cost and revenue by project and period, and integration validation. Example:

  • Filter by source: SELECT RECORD_SOURCE, PROJECT_ID, PA_PERIOD, TOT_RAW_COST, TOT_BURDENED_COST FROM PA_ALLOC_TXN_ACCUM_V WHERE RECORD_SOURCE = 'PJI';
  • Reconcile by project and period: aggregate TOT_RAW_COST from both sources and compare to detect variances between the PA and PJI feeds.
  • Period reporting: constrain PA_PERIOD and sum TOT_REVENUE and billable totals for a given project.

Because the PJI branch aggregates to project element and period with TOT_QUANTITY drawn from LABOR_HRS, consumers should be aware that quantity and labor hours coincide on that branch and that interfaced totals are zeroed.