Search Results task_display_sequence




Overview

APPS.PA_FP_WEBADI_NP_CUSTOM_V is a custom reporting view within the Oracle E-Business Suite Projects (PA) module, associated with the Web ADI (Web Applications Desktop Integrator) financial planning feature set. It exposes non-periodic financial plan data — budget and forecast lines that are defined without being tied to specific accounting periods — in a flattened, denormalized form suitable for extraction, spreadsheet integration, and downstream reporting. The view derives its data by selecting from PA_FP_WEBADI_NON_PERIODIC_V and re-ordering the result set by task display sequence, resource name, unit of measure, and currency. This ordering is significant: the view is commonly referenced when consumers need deterministic, task-sequenced presentation of financial plan rows, which explains the frequent association with the "task_display_sequence" search term.

The view is owned by the APPS schema and is intended for use in EBS 12.1.1 and 12.2.2 environments where Web ADI financial plans (budgets, forecasts, and related plan types) are maintained. It is not a base application table but a presentation layer over the underlying non-periodic view.

Underlying Base Objects

According to the documented ETRM metadata, PA_FP_WEBADI_NP_CUSTOM_V is defined over the following objects:

  • PA_FP_WEBADI_NON_PERIODIC_V (VIEW) — the immediate source from which all projected columns are drawn.
  • PA_FIN_PLAN_UTILS, PA_FIN_PLAN_UTILS2, PA_FP_WEBADI_UTILS, PA_PLANNING_ELEMENT_UTILS (PACKAGES) — PL/SQL utilities invoked within the financial planning and Web ADI framework that supply derived values, list of values logic, and plan element resolution.
  • PA_CROSS_BUSINESS_GRP (PACKAGE) — provides cross-business-group security and organization context.
  • FND_PROFILE (PACKAGE) — supplies profile option values that govern Web ADI behavior, security, and planning defaults.

The view therefore sits at the top of a layered stack: base planning tables feed PA_FP_WEBADI_NON_PERIODIC_V, which is wrapped and re-sorted by this custom view, while the referenced packages provide the surrounding security and utility logic used during Web ADI upload and download operations.

Key Columns

The projected column list is extensive. Notable columns include:

  • budget_version_id, fin_plan_preference_code, plan_class_code — identify the plan version, the financial plan preference, and the plan class (for example, budget versus forecast).
  • project_id, project_name, project_number — project identification attributes.
  • resource_assignment_id, resource_name, resource_list_member_id — the assigned resource and its list membership.
  • task_number, task_name, task_display_sequence — task identification, with the display sequence driving the view's ORDER BY and frequently used in search and sort filters.
  • start_date, end_date, currency, uom, description, change_reason — plan line attributes and units of measure.
  • quantity, actual_quantity, etc_quantity, current_quantity, original_quantity, prior_forecast_quantity — the quantity measures across the standard plan quantity families.
  • raw_cost, burdened_cost, revenue and their corresponding actual, ETC, current, original, and prior forecast variants — the core financial amount measures.
  • raw_cost_rate, burdened_cost_rate, bill_rate and ETC rates — rate columns supporting rate-based analysis.
  • Projfunc_/Project_ cost and revenue rate types, dates, and rates — the project functional and project currency rate attributes.
  • physical_percent_complete, etc_source, record_version_number, cost_code, cost_code_name — completion percentage, estimate-to-complete source, concurrency version, and cost code details.

Common Use Cases and Queries

Typical uses include Web ADI download templates, project budget and forecast reporting, and integration extracts. The view's inherent ordering by task_display_sequence makes it convenient for reports that must honor task ordering.

A representative query retrieving budget lines for a specific project, ordered by task sequence, is:

  • SELECT project_number, task_number, task_name, task_display_sequence, resource_name, currency, uom, quantity, raw_cost, burdened_cost, revenue FROM apps.pa_fp_webadi_np_custom_v WHERE project_id = :p_project_id AND budget_version_id = :p_version_id ORDER BY task_display_sequence, resource_name;
  • SELECT plan_class_code, task_number, resource_name, SUM(burdened_cost) total_burdened_cost FROM apps.pa_fp_webadi_np_custom_v WHERE project_id = :p_project_id GROUP BY plan_class_code, task_number, resource_name ORDER BY task_display_sequence;

Because the view inherits the security and profile logic of the referenced packages, users must connect with appropriate project and cross-business-group privileges to see all expected rows.