Search Results generated_flag




Overview
Explore in AI Chat

Overview

PA_FIN_PLAN_TYPES_VL is a multilingual (VL) view owned by the APPS schema in Oracle E-Business Suite, belonging to the Projects (PA) product family. It presents the definition of financial plan types — the configurable planning structures used within Oracle Projects to classify, generate, and control cost and revenue plans associated with projects and project templates. Financial plan types determine whether a plan is entered manually or generated, whether generated amounts may be edited, whether the plan is used in billing, and which rate and date sources apply to cost and revenue calculations.

Because planning configuration drives downstream behavior in budgeting, forecasting, billing, and project performance reporting, this view serves as the primary read-only access point for financial plan type metadata. It exposes both the base attributes and the language-specific name and description, resolving the translation through the user's session language. In EBS 12.1.1 and 12.2.2 the object is delivered with STATUS VALID, and it is consumed by Oracle Projects forms, concurrent programs, and customer reporting/integration layers that must resolve a financial plan type's code, flags, and rate settings without querying the underlying base and translation tables directly.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through APPS synonyms:

  • PA_FIN_PLAN_TYPES_B — the base (non-translated) table holding the primary key FIN_PLAN_TYPE_ID and all operational attributes: flags, active dates, plan class, rate type and date-type columns, descriptive flexfield attributes, and standard WHO audit columns.
  • PA_FIN_PLAN_TYPES_TL — the translation table holding NAME and DESCRIPTION keyed by FIN_PLAN_TYPE_ID and LANGUAGE.

The view text joins these on FIN_PLAN_TYPE_ID and filters the translation by T.LANGUAGE = USERENV('LANG'), so that NAME and DESCRIPTION are returned in the current session language. This is the standard EBS VL pattern: a _B table providing language-independent data and a _TL table providing translated text, combined so that callers see a single row per financial plan type for the current language. The B.ROWID is exposed as ROW_ID.

Key Columns

The view returns the full set of base columns plus translated text. Significant columns include:

Common Use Cases and Queries

Typical scenarios include resolving a plan type code to its ID for integration payloads, listing available plan types for a planning setup, and reporting on billing-enabled or approved plan types.

  • Lookup by code: SELECT fin_plan_type_id, name, plan_class_code FROM pa_fin_plan_types_vl WHERE fin_plan_type_code = :code;
  • List active plan types: SELECT fin_plan_type_id, fin_plan_type_code, name FROM pa_fin_plan_types_vl WHERE SYSDATE BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE) AND plan_class_code = :class_code;
  • Billing-enabled types: SELECT fin_plan_type_code, name FROM pa_fin_plan_types_vl WHERE used_in_billing_flag = 'Y';
  • Approved cost/revenue types: SELECT name FROM pa_fin_plan_types_vl WHERE approved_cost_plan_type_flag = 'Y' OR approved_rev_plan_type_flag = 'Y';

As with all VL views, queries should respect the session language; joins to project- or plan-level tables should use FIN_PLAN_TYPE_ID. Reports and interfaces should treat the view as read-only and rely on seeded maintenance paths for changes.