Search Results all_resource_assignment_id

Overview

PA_FP_VP_TXNCURRENCY_V is a view owned by the APPS schema in Oracle E-Business Suite, part of the Projects (PA) product family. It is a reporting and display object used specifically by the View Plans page, where it retrieves user-entered budget lines and presents them in a hierarchical, currency-aware layout. User-entered budget data is captured during the budget entry process in forms such as the Budget Lines window and the View Plans page. The view consolidates transaction-level plan lines across task, resource group, resource, and transaction currency dimensions, then applies analytic first-value logic to determine which rows should display the parent hierarchy labels (task name, resource group name, resource name) versus which rows should remain as detail lines.

In Oracle EBS 12.1.1 and 12.2.2, this object carries a VALID status and is defined entirely in the APPS schema. It is not a table and holds no data of its own; it is a derived view. Because it is consumed by the View Plans user interface flow, it is most relevant to functional and technical consultants who need to understand how budget plan data is structured for display, or who are building custom reports that mirror the View Plans presentation.

The search term “resource_id” is a central column in the view. It forms part of the composite keys used in the DECODE and FIRST_VALUE analytic expressions that produce the hierarchical labels. When a problem arises in the View Plans page — such as duplicated or missing resource lines — queries against this view filtered by resource_id, task_id, project_id, or txn_currency_code are a common diagnostic path.

Underlying Base Objects

The documented base objects referenced by PA_FP_VP_TXNCURRENCY_V are:

• PA_FP_TXN_LINES_TMP (synonym) — the transactional budget line source that supplies the project, task, resource group, resource, transaction currency, unit of measure, quantity, and financial measures.
• PA_FP_VIEW_PLANS_TXN_PUB (package) — provides the public functions GET_TASK_NAME and GET_TASK_NUMBER called in the outer SELECT to resolve task identifiers into display names and numbers.
• PA_PROJ_ELEMENTS_UTILS (package) — a Projects utilities package used in the plan/budget element resolution logic.
• PA_RESOURCE_LIST_MEMBERS (synonym) — supplies resource list membership information that underpins resource group and resource naming.

The inner inline view selects from PA_FP_TXN_LINES_TMP and applies four FIRST_VALUE window functions partitioned by project, task, resource group, and resource. These compute LEVEL1 through LEVEL4 anchor keys. The outer query compares each row’s composite key against those anchors and emits task name, resource group name, and resource name only on the anchor row; all other rows receive NULL for those columns, producing the grouping effect seen on the View Plans page.

Key Columns

• TASK_NAME — populated for the anchor row of each task group; formatted as task name followed by task number in parentheses, resolved through PA_FP_VIEW_PLANS_TXN_PUB.
• RESOURCE_GROUP_NAME — displayed only on the anchor row for each resource group within a task.
• RESOURCE_NAME — displayed only on the anchor row for each resource within a resource group.
• TASK_ID, RESOURCE_ID, RESOURCE_GROUP_ID, PROJECT_ID — identifiers used to build the hierarchy keys and to join to other Projects objects; resource_id is frequently used as a filter predicate.
• TXN_CURRENCY_CODE — the transaction currency for the budget line and part of the LEVEL4 key.
• COST_RESOURCE_ASSIGNMENT_ID, REV_RESOURCE_ASSIGNMENT_ID, ALL_RESOURCE_ASSIGNMENT_ID — assignment identifiers linking the line to cost, revenue, and all-resource assignment records.
• UNIT_OF_MEASURE, QUANTITY — the unit of measure and quantity for the plan line.
• BURDENED_COST, RAW_COST, REVENUE, MARGIN, MARGIN_PERCENT — financial measures displayed for each budget line.

Common Use Cases and Queries

Typical uses include validating that user-entered budget lines appear correctly on the View Plans page, reconciling plan amounts by resource and currency, and building custom extracts that reproduce the page’s hierarchy. A common diagnostic query locates all rows for a given resource and currency:

SELECT project_id, task_id, resource_id, resource_group_id, txn_currency_code, task_name, resource_name, quantity, raw_cost, burdened_cost, revenue, margin, margin_percent
FROM apps.pa_fp_vp_txcurrency_v
WHERE resource_id = :resource_id;

To reconcile total plan cost by task and resource group for one project:

SELECT task_id, resource_group_name, resource_name, txn_currency_code, SUM(burdened_cost) total_burdened_cost
FROM apps.pa_fp_vp_txcurrency_v
WHERE project_id = :project_id
GROUP BY task_id, resource_group_name, resource_name, txn_currency_code;

Because the view is built on temporary plan-line storage, results reflect the plan lines as they exist at query time; ad hoc SQL should be executed under the APPS schema or with appropriate MO: Operating Unit and Projects security context to return the correct rows for the operating unit and project.