Search Results tm_out

Overview

PA_TASK_MANAGER is an Oracle Applications (APPS) PL/SQL package body that supports task-level management within Oracle Projects. Its primary business function is to enforce and maintain the integrity of project membership records that underpin task ownership, in particular the assignment of a task manager as a project member. The package combines utility routines—profile option retrieval and diagnostic logging—with validation logic that verifies whether a designated task manager exists as a valid member of the associated project for the relevant project role.

The header comment ($Header: PATMUPGB.pls 120.1 2005/08/08 04:25:58 avaithia noship $) indicates the package was maintained as a non-shipped ("noship") upgrade component, positioned around the task manager upgrade path. It is registered in ETRM as having an API classification of OTHER and is referenced by no other packages, meaning it is invoked directly rather than as a shared dependency.

Key Procedures and Functions

• GET_PROFILE_VALUE — A helper function that retrieves the value of a named profile option using FND_PROFILE.GET. Because a profile option can never legitimately hold a NULL value, a returned NULL signals that the profile does not exist; the routine applies NVL to default the result to 'N'.
• VALIDATE_MEMBER_EXISTS — The core validation procedure. It determines whether the task manager is already established as a project member and evaluates break periods across the member's active date range. Internal cursors query open-ended membership rows (where end_date_active IS NULL) and enumerate membership records ordered by start_date_active, which the source comment explicitly flags as essential to ordered processing.
• UPGRADE_TASK_MANAGER — The upgrade entry point that applies task manager membership changes, coordinating validation and persistence of the project member records.
• TM_LOG — A diagnostic logging routine corresponding to the "tm_log" search context; it captures task manager processing messages for review and troubleshooting.
• TM_OUT — An output routine that emits task manager processing details, typically to the concurrently generated log or output file.
• PRINT_OUTPUT — Writes the accumulated output buffer, supporting the delivery of upgrade or validation results to the caller or log file.

Tables Accessed

• PA_PROJECT_PARTIES — The primary read target, queried to confirm membership existence, project role, and active date ranges for the task manager.
• PA_PROJECTS_ALL — Supplies project context, including the project end date used to bound membership validation.
• PA_TASKS — Provides task-level records associated with the task manager assignment.
• PA_IMPLEMENTATIONS — Used to confirm the Oracle Projects installation and operating context.
• FND_PROFILE_OPTION_VALUES — The underlying source for profile option lookup in GET_PROFILE_VALUE.
• FND_NEW_MESSAGES — Supports the messaging and message-count retrieval pattern used for output handling.
• DUAL — Used for scalar evaluations and simple control queries.

Usage Notes

PA_TASK_MANAGER is typically invoked during Oracle Projects upgrades or data-maintenance activities where task manager assignments must be reconciled with project membership records, and it may be executed from concurrent programs or direct catalog calls. The presence of TM_LOG, TM_OUT, and PRINT_OUTPUT indicates the package is designed for batch execution with captured output, making the request log the first reference point when diagnosing "tm_log" behavior. Because no other packages reference it, custom code that calls it should account for its standalone nature and the ordered start-date processing required by VALIDATE_MEMBER_EXISTS.