Results for “task_mgr”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKE_TASKS_V is a valid, read-only database view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the OKE product family, Project Contracts, and is documented in ETRM as a "valid task listing." In practice the view exposes project task records drawn from Oracle Projects (PA) alongside the name of the person assigned as task manager, resolved through Oracle HRMS person information. Because it surfaces only tasks that carry a valid project and task identifier, it serves as a convenient, join-ready source for reporting and integration logic that requires task-level detail without navigating the full PA_TASKS structure directly.

The view plays a supporting role in the Project Contracts data model. Contract lines, deliverables, and billing constructs frequently reference project tasks, and OKE_TASKS_V supplies the descriptive attributes — number, name, dates, and manager — needed to render those references in reports, concurrent programs, and interface extracts.

Underlying Base Objects

The documented 12.2.2 metadata lists the following referenced base objects: HR_GENERAL (package), HR_PERSON_NAME (package), HR_SECURITY (package), PA_TASKS (synonym), and PER_PEOPLE_F (view). The view text confirms a two-object primary join: PA_TASKS supplies the project and task attributes, while PER_PEOPLE_F supplies the task manager's full name. The person join is outer (PEOP.PERSON_ID (+) = PTK.TASK_MANAGER_PERSON_ID), so tasks with no assigned manager are still returned, with null manager information.

The HR packages are referenced because PER_PEOPLE_F is a date-tracked, secured view. HR_SECURITY enforces person-level security so that users see only employees within their authorized business group and security profile, HR_PERSON_NAME resolves the formatted name, and HR_GENERAL provides supporting person utilities. Because the view queries secured HRMS objects, its effective row set is subject to the calling user's HR security configuration.

Key Columns

• PROJECT_ID — Identifier of the owning project; the primary join key back to Oracle Projects.
• TASK_ID — Unique identifier of the task within the project.
• TASK_NUMBER — User-visible task number, commonly used for display and cross-referencing.
• TASK_NAME — Descriptive name of the task.
• START_DATE — Planned or actual start date of the task.
• END_DATE / COMPLETION_DATE — Task completion or end date; the documented view text selects COMPLETION_DATE and the column listing shows END_DATE, which are equivalent references to the task completion date.
• TASK_MGR_ID / TASK_MANAGER_PERSON_ID — Person identifier of the assigned task manager.
• TASK_MGR — Full name of the task manager, resolved from PER_PEOPLE_F; null when no manager is assigned.

Common Use Cases and Queries

Typical uses include task listings by project, manager-based summaries, and populating contract or billing reports that need task names and dates. A straightforward listing follows:

• SELECT task_number, task_name, start_date, end_date, task_mgr FROM apps.oke_tasks_v WHERE project_id = :p_project_id ORDER BY task_number;
• SELECT project_id, COUNT(*) FROM apps.oke_tasks_v GROUP BY project_id; — task counts per project.
• SELECT * FROM apps.oke_tasks_v WHERE task_mgr IS NULL; — tasks without an assigned manager.

Because the view is not date-effective in its own right, callers requiring as-of reporting should filter or join against PA_TASKS directly. All queries must run against the APPS schema or a synonym, and results remain constrained by HRMS security for the task manager name.