Search Results partially_impl_cos_exist

Overview

PA_FIN_PLAN_TYPES_UTILS is a utility package in the Oracle E-Business Suite Projects (PA) module that supports validation and referential-integrity logic for financial plan types. Financial plan types define the categories of financial plans (budgets, forecasts, and workplans) that can be created for a project, and they carry attributes governing whether the type is used in billing, whether it is generation-enabled, and how control items and cost implementation statuses behave. The package body provides reusable validation routines that are invoked by the financial plan type maintenance forms and by related APIs before rows are inserted or updated in the underlying base and translation tables. It also supplies query helpers used to determine whether a financial plan type has already been consumed by transaction data, thereby preventing the deletion or redefinition of types that are still in active use.

Key Procedures and Functions

The package contains eleven documented procedures and functions. NAME_VAL verifies that a non-null financial plan type name has been supplied and that it is unique across the multilingual view, raising the standard "unique name exists" and "mandatory information missing" messages through PA_UTILS. END_DATE_ACTIVE_VAL validates the end-date and active-flag combination so that an inactive or expired type cannot remain in an inconsistent state. GENERATED_FLAG_VAL and USED_IN_BILLING_FLAG_VAL validate the corresponding indicator columns on the financial plan type. DELETE_VAL performs the checks required before a financial plan type can be deleted, while VALIDATE acts as the umbrella routine that orchestrates the individual attribute validations. ISFPTYPEUSED reports whether a given financial plan type is already referenced by project data, and PARTIALLY_IMPL_COS_EXIST — the term behind the search that surfaced this package — determines whether any control items exist that are only partially implemented for cost, a condition that restricts which maintenance operations are permitted on the type. GET_CONCAT_STATUSES returns concatenated status information for display or downstream comparison, GET_WORKPLAN_PT_DETAILS retrieves workplan-related plan type details, and IS_REV_IMPL_PARTIALLY detects the analogous partially-implemented condition for revenue. All message-emitting procedures expect the caller to have invoked FND_MSG_PUB.initialize beforehand.

Tables Accessed

The package reads and writes PA_FIN_PLAN_TYPES_B and PA_FIN_PLAN_TYPES_TL, the base and translation tables that hold the financial plan type definition and its language-specific name and description. PA_PT_CO_IMPL_STATUSES stores the per-control-item implementation status used by PARTIALLY_IMPL_COS_EXIST and IS_REV_IMPL_PARTIALLY, while PA_CONTROL_ITEMS supplies the control item master. PA_BUDGET_VERSIONS and PA_BUDGET_TYPES are consulted to determine whether a plan type has been consumed by budget data, and PA_PROJ_FP_OPTIONS holds project-level financial plan configuration. FND_LANGUAGES is used for language-code resolution in the name uniqueness check, and DUAL supports scalar validations.

Usage Notes

The package is typically invoked from the Oracle Forms-based financial plan type setup screens, where each field-level validation delegates to the appropriate routine, and from concurrent or custom code that programmatically creates or retires financial plan types. Because NAME_VAL queries the multilingual view, language context must be set by the caller. Custom integrations should call VALIDATE for a consolidated check, and should test ISFPTYPEUSED, PARTIALLY_IMPL_COS_EXIST, or IS_REV_IMPL_PARTIALLY before attempting deletion or structural changes. Callers must initialize the message stack with FND_MSG_PUB.initialize and read messages afterwards via the standard FND_MSG_PUB APIs.