Search Results check_unique_task_ref_pvt

Overview

The APPS.PA_PROJECT_CHECK_PVT package is a private validation utility within the Oracle E-Business Suite Projects (PA) module. In the Oracle EBS API architecture, packages suffixed with _PVT are classified as private APIs: they encapsulate business rule validations and are invoked exclusively by the public APIs and other internal packages that compose the supported interface surface. As its name implies, PA_PROJECT_CHECK_PVT centralizes the integrity checks applied to project and task data before records are committed. Its dependency list confirms this role — it consumes services from FND_API (marshalling error messages through the standard API error stack), PA_INTERFACE_UTILS_PUB, PA_PROJECT_PUB, and PA_PROJECT_UTILS, while being referenced by PA_PROJECT_PUB, PA_PROJECT_PVT, PA_PROJECT_PARTIES_PUB, and itself. The package carries no public API classification and should never be called directly from supported custom code.

Key Procedures and Functions

The ETRM metadata documents fifteen procedures and functions, which fall into three functional groups:

• Project-level checks: CHECK_UNIQUE_PROJECT_REF_PVT validates that a project reference is not duplicated; CHECK_DELETE_PROJECT_OK_PVT determines whether a project may be deleted without violating referential or business constraints; CHECK_CHANGE_PROJ_ORG_OK_PVT verifies that an organizational reassignment is permissible; and CHECK_START_END_DATE_PVT confirms that project start and end dates form a valid range.
• Task-level checks: CHECK_ADD_SUBTASK_OK_PVT validates the parent task for a proposed subtask; CHECK_DELETE_TASK_OK_PVT confirms that a task is deletable; CHECK_UNIQUE_TASK_REF_PVT and CHECK_UNIQUE_TASK_NUMBER_PVT enforce uniqueness of task reference and task number respectively; CHECK_CHANGE_PARENT_OK_PVT and CHECK_PARENT_CHILD_TK_DTS_PVT verify that parent/child relationships and their date spans remain consistent; CHECK_TASK_NUMB_CHANGE_OK_PVT evaluates whether a task number may be changed; and HANDLE_TASK_NUMBER_CHANGE_PVT performs the associated processing when that change is permitted.
• Billing and management checks: VALIDATE_BILLING_INFO_PVT verifies billing information against the applicable bill rate schedule; CHECK_FOR_ONE_MANAGER_PVT and CHECK_MANAGER_DATE_RANGE ensure that a project has exactly one manager and that the manager's effective date range is valid.

Tables Accessed

The package queries and validates against the core Projects tables through APPS synonyms:

• PA_PROJECTS / PA_PROJECTS_ALL — the base and organization-enabled project definition tables, used for uniqueness, deletion, date, and organization-change validation.
• PA_PROJECT_TYPES_ALL — supplies project type attributes that govern date and organizational rules.
• PA_TASKS — the task hierarchy table, used for task number/reference uniqueness, parent/child and date-span checks, and structural task changes.
• PA_STD_BILL_RATE_SCHEDULES / PA_STD_BILL_RATE_SCHEDULES_ALL — standard bill rate schedules referenced by VALIDATE_BILLING_INFO_PVT.
• DUAL and PLITBLM — used for single-row selection and PL/SQL table (index-by table) operations within the package's internal logic.

Access is read-oriented for validation, with writes limited to actions such as the task number change handler.

Usage Notes

PA_PROJECT_CHECK_PVT is invoked indirectly. The primary entry point is PA_PROJECT_PUB — the public project API — which calls these private checks before performing inserts, updates, and deletes on projects and tasks. PA_PROJECT_PVT and PA_PROJECT_PARTIES_PUB also reference it. In practice, the package executes whenever users maintain projects through the Projects form, when concurrent programs such as project and task interface importers process inbound data, or when custom integrations call the supported PA_PROJECT_PUB APIs. Because the package is classified as _PVT and is not part of Oracle's public API set, customers should not call it directly; doing so bypasses supported error-handling conventions and may be broken by patching. Custom code should route through PA_PROJECT_PUB and rely on the FND_API error stack for validation feedback. The presence of PA_PROJECT_CHECK_PVT in an environment is expected in Oracle EBS 12.1.1 and 12.2.2, where its metadata status is VALID.