Search Results pa_fin_plan_utils2




Overview
Explore in AI Chat

Overview

The view APPS.PA_FP_BUDGET_LINE_REJECTIONS_V is a reporting and integration construct within the Oracle EBS Projects (PA) module, owned by the APPS schema. Its purpose is to expose budget line records that carry either cost or burden rejection codes, presenting both the rejection code itself and its translated message text in the user's session language. It is defined over the financial planning budget line and budget version tables, and it enriches each rejected budget line with derived indicator flags that signal whether the rejection is localized to a specific line or applies across a resource assignment or budget period. The view is a read-only, presentation-layer object intended for diagnostics, reconciliation, and notification workflows rather than for transactional processing.

Underlying Base Objects

The documented metadata lists the following referenced base objects:

  • PA_BUDGET_VERSIONS (synonym) — source of budget_version_id and project_id.
  • PA_BUDGET_LINES (synonym) — the primary driver supplying line-level attributes and rejection codes.
  • PA_RESOURCE_ASSIGNMENTS (synonym) — provides the assignment context joined through resource_assignment_id.
  • PA_RESOURCE_LIST_MEMBERS (synonym) — supplied via ram.task_id.
  • FND_NEW_MESSAGES (synonym) — resolves rejection codes to readable message text using APPLICATION_ID = 275 and USERENV('LANG').
  • PA_FIN_PLAN_UTILS2 (package) — referenced as pa_fin_plan_utils2.get_bdgt_start_date and pa_fin_plan_utils2.get_bdgt_end_date to bound period-level checks.
  • DUAL (synonym) — used within correlated EXISTS subqueries that compute the "Y"/"N" flags.

This dependency on PA_FIN_PLAN_UTILS2 is precisely why a search for "pa_fin_plan_utils2" surfaces this view; the package functions act as session-context accessors for the budget start and end dates used in the period-level rejection test.

Key Columns

  • budget_version_id, project_id, task_id, budget_line_id, resource_assignment_id — the identifying and relational keys.
  • start_date, end_date, period_name — the budgeting period context.
  • txn_currency_code, project_currency_code, projfunc_currency_code — the transactional, project, and project functional currency codes.
  • cost_rejection_code / burden_rejection_code — the stored rejection reason codes.
  • cost_rejection_msg_data / burden_rejection_msg_data — human-readable message text resolved from FND_NEW_MESSAGES.
  • cost_rejection_flag / burden_rejection_flag — 'Y' when any line for the same budget version, currency, and resource assignment carries a rejection of that type.
  • period_cost_rejection_flag — 'Y' when a rejection exists for the same budget version, currency, and resource assignment where both start and end dates fall between get_bdgt_start_date and get_bdgt_end_date.

Common Use Cases and Queries

Typical usage includes identifying lines that failed cost or burden validation during budget upload, and surfacing translated explanations to end users.

  • List all currently rejected lines with messages:
    SELECT project_id, budget_line_id, cost_rejection_msg_data FROM pa_fp_budget_line_rejections_v WHERE cost_rejection_code IS NOT NULL;
  • Identify assignment-wide burden issues:
    SELECT budget_version_id, resource_assignment_id FROM pa_fp_budget_line_rejections_v WHERE burden_rejection_flag = 'Y';
  • Filter by period-level cost rejections:
    SELECT * FROM pa_fp_budget_line_rejections_v WHERE period_cost_rejection_flag = 'Y';

Because the view resolves message text dynamically through USERENV('LANG'), results are automatically localized to the querying user's language.