Search Results margin_percent




Overview
Explore in AI Chat

Overview

APPS.PA_FP_VP_TXNCURRENCY_V is a reporting view in the Oracle E-Business Suite Projects (PA) module, belonging to the Forecast and Planning (FP) schema family. It presents transaction-level forecast or plan data aggregated by task, resource group, resource, and transaction currency, and it is intended primarily to drive the "View Plans" (VP) user interface and related reporting within Project Management. The view's defining characteristic is its hierarchical, report-style output: rather than returning every underlying transactional row, it selectively populates grouping columns (task name, resource group name, resource name) only at the first occurrence of each grouping level, using DECODE against window-function "first_value" markers (level1 through level4). This produces a denormalized, break-grouped result set suitable for direct display in Oracle Forms or OAF-based plan review pages, where repetition of parent labels would be visually undesirable. Because it exposes columns such as quantity, burdened cost, raw cost, revenue, margin, and margin percent alongside their currency and unit-of-measure context, it also functions as a convenient data source for financial plan extracts and custom reporting.

Underlying Base Objects

The documented base objects referenced by this view are:

  • PA_FP_TXN_LINES_TMP (SYNONYM) — the forecast/plan transaction lines table that supplies the core transactional rows (project, task, resource assignments, currency, quantity, cost, revenue figures).
  • PA_RESOURCE_LIST_MEMBERS (SYNONYM) — provides resource list membership and hierarchy information (resource groups and resources).
  • PA_PROJ_ELEMENTS_UTILS (PACKAGE) — supplies the function GET_DISPLAY_SEQUENCE, used to derive task_sequence_id from the task, giving the deterministic ordering of tasks within a project.
  • PA_FP_VIEW_PLANS_TXN_PUB (PACKAGE) — provides display functions get_task_name and get_task_number, used to render the task label and task number.

The view is defined over an inline subquery that joins these sources, and the supplied text confirms that task_sequence_id originates from PA_PROJ_ELEMENTS_UTILS.GET_DISPLAY_SEQUENCE(task_id). The four window functions partition by project and progressively finer keys, producing the level1–level4 markers that drive the DECODE-based suppression of repeated group labels.

Key Columns

  • task_sequence_id — a derived sequence value (via GET_DISPLAY_SEQUENCE) used to order and identify tasks consistently within a project; it is not a stored persistent attribute but a computed display sequence.
  • task_name — the concatenated task name and task number, shown only on the first row of a task group.
  • resource_group_name and resource_name — displayed only at their first occurrence within each grouping level.
  • task_id, cost_resource_assignment_id, rev_resource_assignment_id, all_resource_assignment_id — identifiers linking the row back to the underlying forecast/plan assignments.
  • txn_currency_code, unit_of_measure — currency and UOM context for the amounts.
  • quantity, burdened_cost, raw_cost, revenue, margin, margin_percent — the quantitative and financial measures presented per task/resource/currency combination.

Common Use Cases and Queries

The view supports plan review, forecast reporting, and extract-style integrations. A typical query might filter a project and order by task sequence, for example: SELECT task_sequence_id, task_name, resource_group_name, resource_name, txn_currency_code, quantity, burdened_cost, revenue FROM apps.pa_fp_vp_txncurency_v WHERE project_id = :p_project ORDER BY task_sequence_id; (note: the view exposes project_id only through the inline query's derived columns; the outer select lists task-level columns). A search for "task_sequence_id" will resolve here because the column is central to the ordering semantics. Analysts use the view to inspect margin and revenue by currency, to feed plan-versus-actual comparisons, or to build custom BI reports without reimplementing the grouping logic. It is also valuable in integrations requiring a pre-grouped, human-readable forecast snapshot.