Search Results pa_fin_plan_types_utils




Overview
Explore in AI Chat

Overview

The APPS.PA_FIN_PLAN_TYPES_UTILS package is a utility package in the Oracle E-Business Suite Projects (PA) module that supports the definition, validation, and lifecycle management of financial plan types. Financial plan types are the configuration entities that define which planning structures (budgets, forecasts, resource plans, and cost/revenue plans) may be created against a project, and which rules govern their usage across budgeting, billing, and workplan generation. In Oracle EBS 12.1.1 and 12.2.2, this package serves as the validation and dependency-checking layer beneath the public API PA_FIN_PLAN_TYPES_PUB. It enforces business rules on financial plan type records, determines whether a given type is in use, and evaluates the implementation status of control items and revenue or cost plan associations. Its status is VALID in the APPS schema, and ETRM documentation identifies it as an API of classification OTHER, meaning it is intended primarily for internal use by Oracle code rather than as a formally published integration interface.

Key Procedures and Functions

The documented package exposes eleven procedures and functions, each targeting a specific validation or query requirement:

  • NAME_VAL — validates the name attribute of a financial plan type record.
  • END_DATE_ACTIVE_VAL — validates the end date and active status combination for a plan type.
  • GENERATED_FLAG_VAL — validates the generated flag indicator.
  • USED_IN_BILLING_FLAG_VAL — validates the flag controlling whether the plan type participates in billing.
  • DELETE_VAL — verifies whether a financial plan type may be safely deleted, checking associated dependencies.
  • VALIDATE — the master validation routine that orchestrates attribute-level checks for a plan type record.
  • ISFPTYPEUSED — determines whether a specific financial plan type is referenced or in use, guarding modification and deletion.
  • PARTIALLY_IMPL_COS_EXIST — checks for the existence of partially implemented control items linked to a plan type.
  • GET_CONCAT_STATUSES — returns concatenated implementation status values, typically for control item or plan type state display.
  • GET_WORKPLAN_PT_DETAILS — retrieves workplan-related plan type detail information.
  • IS_REV_IMPL_PARTIALLY — evaluates whether revenue plan implementation is partially complete for a given configuration.

Tables Accessed

The package reads and writes the following base tables through APPS synonyms:

  • PA_FIN_PLAN_TYPES_B and PA_FIN_PLAN_TYPES_TL — the base and translated tables holding financial plan type definitions, the primary objects validated and queried.
  • PA_PT_CO_IMPL_STATUSES — stores plan type / control item implementation statuses, used by the implementation-status routines.
  • PA_CONTROL_ITEMS — defines control items whose partial implementation is checked.
  • PA_BUDGET_VERSIONS and PA_BUDGET_TYPES — used to detect whether plan type instances exist against budget versions, supporting usage and deletion checks.
  • PA_PROJ_FP_OPTIONS — project-level financial plan options that influence validation outcomes.
  • FND_LANGUAGES — supports language-related validation for translated names.
  • DUAL — used for scalar queries and constant evaluation.

Usage Notes

PA_FIN_PLAN_TYPES_UTILS is invoked primarily by Oracle's own setup forms for financial plan types, by the public API PA_FIN_PLAN_TYPES_PUB, and internally within the package itself. ETRM records that it references PA_FIN_PLAN_TYPES_PUB and is referenced by that package and by itself, confirming a tightly coupled, internal-facing role. Administrators and technical consultants generally encounter it indirectly during configuration of financial plan types, and it is not recommended as a direct integration point. Custom code should favor the documented public API rather than calling these utility routines directly.