Search Results delete_plan_type_from_project

Overview

PA_FIN_PLAN_TYPE_GLOBAL is an Oracle Projects API package owned by the APPS schema and classified by ETRM as an "OTHER" API. Its documented purpose is to provide the underlying API layer for the Org Forecast "PLANS" page within Oracle E-Business Suite. The package centralizes logic used to resolve the relationship between financial plan types and plan classes, and to identify the appropriate budget or forecast version records associated with a given project and plan type. It also maintains a package-level global variable (G_PROJECT_ID) so that dependent logic can retrieve the currently active project context via GET_PROJECT_ID.

The package is significant in Oracle EBS 12.1.1 and 12.2.2 because financial plan types are a configurable, extensible construct in Oracle Projects; the mapping between a plan type and its underlying plan class (the internal classification that drives budget versus forecast processing) is a recurring requirement in both the standard Org Forecast forms and in custom extensions. The presence of PLANTYPE_TO_PLANCLASS and PLANVERSION_TO_PLANCLASS in the documented procedure list suggests this package is the authoritative resolution point for that mapping.

Key Procedures and Functions

• GET_PROJECT_ID — Returns the value of the package global G_PROJECT_ID, exposing the project identifier established for the current session context.
• SET_GLOBAL_VARIABLES — Initializes the package globals, notably the project identifier, and returns the factor_by_code option value along with standard return status, message count, and message data out parameters.
• PA_FP_GET_ORGFCST_VERSION_ID — Retrieves the Org Forecast version identifier for a given project, plan type, and plan status code. It is intended specifically for Org Forecast plan types.
• PA_FP_GET_FINPLAN_VERSION_ID — Serves a parallel purpose for non-Org Forecast plan types, returning the cost version and revenue version identifiers that correspond to the current working or current baselined status.
• DELETE_PLAN_TYPE_FROM_PROJECT — Removes an association between a plan type and a project, supporting cleanup when a plan type is no longer applicable.
• PLANTYPE_TO_PLANCLASS — Resolves the plan class code associated with a given plan type identifier. This is the object users search for using the term "plantype_to_planclass."
• PLANVERSION_TO_PLANCLASS — Resolves the plan class from a plan version, complementing the plan-type-based lookup.

Each procedure follows Oracle Projects conventions, returning x_return_status, x_msg_count, and x_msg_data, and using NOCOPY for OUT parameters.

Tables Accessed

• PA_FIN_PLAN_TYPES_B — Defines financial plan types and their plan class codes; primary source for plan type to plan class resolution.
• PA_BUDGET_VERSIONS — Stores budget and plan version records used to resolve version identifiers by status.
• PA_PROJ_FP_OPTIONS — Provides financial plan options, including the factor_by_code setting returned by SET_GLOBAL_VARIABLES.
• PA_FP_ELEMENTS and PA_FP_EXCLUDED_ELEMENTS — Define the elements included in or excluded from a financial plan structure.
• PA_FP_TXN_CURRENCIES — Holds transaction currency definitions relevant to plan processing.
• PA_RBS_HEADERS_B, PA_RBS_PRJ_ASSIGNMENTS, PA_RBS_VERSIONS_B — Support resource breakdown structure context used when interpreting plan versions.
• PLITBLM — A Projects message table referenced for message resolution.

Usage Notes

This package is primarily invoked by the Oracle Projects Org Forecast PLANS page and by other Oracle Projects forms that must resolve plan types and versions. ETRM documents that it is referenced by seven other packages, confirming it is a dependency within the Projects API stack rather than an entry-point API. Custom code should call PLANTYPE_TO_PLANCLASS and PLANVERSION_TO_PLANCLASS to obtain plan class codes rather than querying PA_FIN_PLAN_TYPES_B directly, and should call SET_GLOBAL_VARIABLES before invoking version-resolution routines so that G_PROJECT_ID and related globals are populated. Because the package uses AUTHID CURRENT_USER and relies on APPS synonyms, callers must be granted execute privileges appropriately. Its 2005 header version (120.1) indicates it has remained stable across 12.1.1 and 12.2.2.