Search Results add_task_round_two

Overview

PA_PROJECT_PVT is the private implementation package for the Oracle Projects (PA) project foundation APIs in Oracle E-Business Suite 12.1.1 and 12.2.2. While the public package PA_PROJECT_PUB exposes the supported, customer-facing API surface for creating and maintaining projects and tasks, PA_PROJECT_PVT contains the internal logic that performs validation, reference resolution, structure assembly, and data persistence. It is declared with AUTHID DEFINER, meaning it executes with the privileges of its owner (APPS), and it carries an API version constant (G_API_VERSION_NUMBER := 1.0) that reflects the maturity of the underlying interface contract.

The package supports the core business process of project creation and maintenance: resolving user-supplied project references into internal identifiers, validating user input against setup and reference data, creating project and task structures in multiple rounds, and managing key members and class categories. Because it is classified as a PVT (private) API, Oracle does not guarantee backward compatibility of its signatures, and direct calls from custom code are discouraged in favor of PA_PROJECT_PUB.

Key Procedures and Functions

The documented interface includes 34 procedures and functions. The most relevant include:

• ADD_KEY_MEMBERS — Populates project key member records, typically when instantiating a project from a source template.
• ADD_CLASS_CATEGORIES — Creates class category assignments on a project, mirroring the source template where applicable.
• ADD_TASK_ROUND_ONE / ADD_TASK_ROUND_TWO — Two-phase task creation. Round one inserts the task shell and derives its identifiers; round two resolves parent/child relationships, project structures, and the task version identifier.
• FETCH_PROJECT_ID / FETCH_TASK_ID — Resolve internal project and task identifiers from supplied references.
• CONVERT_PM_PROJREF_TO_ID / CONVERT_PM_TASKREF_TO_ID / CONVERT_PM_TASKREF_TO_ID_ALL — Translate Project Manager-style references into numeric IDs, including the "ALL" variant that handles bulk task references.
• CHECK_VALID_* family — CHECK_VALID_MESSAGE, CHECK_VALID_ORG, CHECK_VALID_PROJECT_STATUS, CHECK_VALID_DIST_RULE, and CHECK_VALID_EMPLOYEE perform targeted validation of message text, operating unit, project status, distribution rule, and employee values.
• CHECK_CLASS_CODE_VALID — Validates that a supplied class code exists and is valid for the associated class category. This is the procedure returned by the user's search term check_class_code_valid.
• DELETE_ONE_TASK — Removes a single task record along with its dependent data.
• VALIDATE_BILLING_INFO — Confirms billing configuration before persistence.
• CHECK_FOR_ONE_MANAGER — Ensures only one manager is assigned where the business rule requires a single manager.
• HANDLE_TASK_NUMBER_CHANGE — Manages the special logic required when a task number is changed, using the G_task_num_updated_index_tbl collection to track updated tasks.
• CHECK_PARENT_CHILD_TASK_DATES — Verifies that parent and child task date ranges are consistent.

The package also defines the ROW_ALREADY_LOCKED exception (ORA-00054) for locking conflicts during updates, and the task_number_upd_rec_type / task_number_upd_tbl_type record and table types used by the task renumbering logic.

Tables Accessed

The package reads and writes a range of PA and shared reference tables via APPS synonyms:

• PA_PROJECTS — Primary project record; the package operates on PA_PROJECTS%ROWTYPE throughout its add/update routines.
• PA_PROJECT_TYPES — Supplies project_type_class_code and service_type_code used to drive task creation behavior.
• PA_CLASS_CATEGORIES, PA_CLASS_CODES — Back the class code and category validation procedures.
• PA_IMPLEMENTATIONS — Confirms the Projects installation and configuration context.
• PA_BILLING_ASSIGNMENTS — Consulted by VALIDATE_BILLING_INFO.
• PA_COMPILED_MULTIPLIERS, PA_EMP_BILL_RATE_OVERRIDES, PA_JOB_BILL_RATE_OVERRIDES, PA_JOB_ASSIGNMENT_OVERRIDES, PA_IND_COMPILED_SETS, PA_IND_RATE_SCH_REVISIONS — Rate and multiplier sources for billing validations.
• FND_LOOKUP_VALUES — Provides lookup-driven validation for statuses, distribution rules, and other descriptive flexfields.
• HZ_CUST_ACCT_SITES_ALL, HZ_PARTIES — Customer and party data used to validate billing and customer context.

Usage Notes

PA_PROJECT_PVT is invoked indirectly through PA_PROJECT_PUB, which is the supported entry point for project and task creation and update. In practice, calls originate from Oracle Projects forms (such as the Project, Task, and Template windows), from concurrent programs that mass-maintain projects, and from other internal PA packages — the ETRM metadata notes the package is referenced by 18 other packages. Because the API is private, its signatures carry no compatibility guarantee across releases; custom extensions should call PA_PROJECT_PUB rather than PA_PROJECT_PVT directly. The presence of G_API_VERSION_NUMBER and the ROW_ALREADY_LOCKED handler indicates callers should be prepared for locking conflicts and should version-check the API before invoking it.