Search Results plan_processing_code




Overview
Explore in AI Chat

Overview

APPS.PA_FCST_PROJ_DTL_V is a reporting view in the Oracle E-Business Suite Projects (PA) module, delivered as part of the Project Forecasting and Budgeting functionality. It exposes forecast detail data at the assignment and period level, formatted specifically for consumption by Oracle Business Intelligence (OBIEE) or similar graphical reporting engines that rely on a normalized pivot structure. The view does not merely select raw transactional rows; it reshapes forecast data into a layout in which derived sequence columns (Y1_SEQ and X1_SEQ) and formatted attribute columns are pre-calculated, allowing downstream tools to render matrix or chart-style output without additional transformation logic.

The plan_processing_code column, which the user searched for, is exposed in this view under the alias Y1_IMAGE. This aliasing reflects the view's designed role as a data source for image or icon-driven reporting, where the processing code drives a visual indicator identifying the plan type associated with each forecast record.

Underlying Base Objects

The view is defined over the following documented base objects:

  • PA_FCST_PROJ_PERIODIC_V (VIEW) — the primary source from which all columns are selected. It supplies the periodic forecast values, assignment identifiers, billing rates, discount percentages, and project totals.
  • FND_PROFILE (PACKAGE) — referenced indirectly, as is typical in Oracle EBS views, to honor profile option settings such as organizational or security context.
  • PA_FCST_GLOBAL (PACKAGE) — a global forecast utility package used within the forecasting framework.
  • PA_PERIOD_PROCESS_PKG (PACKAGE) — the period processing package, which governs how forecast periods are generated and processed.

Because PA_FCST_PROJ_DTL_V is itself defined over PA_FCST_PROJ_PERIODIC_V, it is a second-tier view. Any change to the underlying periodic view propagates upward, so administrators should validate impact whenever patching the forecasting schema. The view extracts its data by ordering on ASSIGNMENT_ID and applies window functions over the periodic view's result set.

Key Columns

  • ASSIGNMENT_ID — the assignment identifier linking the forecast row to a staffing assignment.
  • PERIOD_NAME (X1) — the forecast period name, aliased for the X-axis in reporting layouts.
  • Y1_SEQ — a dense rank generated over ASSIGNMENT_NAME and ASSIGNMENT_ID, providing the Y-axis sequence.
  • X1_SEQ — a dense rank partitioned by ASSIGNMENT_ID and ordered by PERIOD_START_DATE, providing the X-axis sequence.
  • PROJECT_ID — the project identifier.
  • ASSIGNMENT_NAME (Y1) — the display name of the assignment.
  • PLAN_PROCESSING_CODE (Y1_IMAGE) — the processing code used to select an image or icon that denotes the plan's processing state.
  • Y1_LEFTATTRIBUTE1–3 — formatted standard bill rate, average bill rate, and average discount percentage, each cast via TO_CHAR with numeric masks.
  • Y1_RIGHTATTRIBUTE1 — the formatted project total.
  • VALUE — the forecast value carried forward from the periodic view.

Common Use Cases and Queries

Typical use cases include forecast dashboards, assignment-level margin analysis, and graphical trend reporting where period, assignment, and rate data must appear on aligned axes. A representative query retrieving forecast details for a single project follows:

SELECT project_id, assignment_name, period_name, plan_processing_code,
  y1_leftattribute1, y1_rightattribute1, value
FROM apps.pa_fcst_proj_dtl_v
WHERE project_id = :p_project_id
ORDER BY y1_seq, x1_seq;

Because the view performs the ranking and formatting internally, reports can filter on PLAN_PROCESSING_CODE directly to isolate forecast rows by plan processing state, or join to PA_PROJECTS_ALL on PROJECT_ID for project descriptive attributes. Presented columns such as Y1_LEFTATTRIBUTE1 are already character-formatted, so consumers should not apply additional numeric functions to them.