Results for “pa_schedule_constraint_type”

28 results




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

Overview

APPS.PA_TASK_DET_SCH_OPT_V is a view in the Oracle E-Business Suite (EBS) Applications schema, registered under FND Design Data as PA.PA_TASK_DET_SCH_OPT_V. It is documented as an Oracle Internal Use Only object within the Projects (PA) module. The view presents detailed scheduling options for project tasks, specifically project elements that participate in scheduling calculations. Its columns expose the scheduling constraint type, task type defined in the scheduling tool, slack values, effort-driven and assignment-levelling indicators, and duration metrics (actual, remaining, and scheduled).

In Oracle EBS 12.1.1 and 12.2.2, this view functions primarily as an internal implementation artifact consumed by standard Oracle Projects programs, particularly those related to Project Management and the integration with Oracle Projects scheduling (including primavera-style scheduling data). Because it is flagged Internal Use Only, Oracle Corporation does not support direct access to this data except from standard Oracle Applications programs; nevertheless, it is frequently discovered by technical consultants and reported in reporting/ETRM contexts.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, PA_TASK_DET_SCH_OPT_V references the following base objects:

The view is not referenced by any other database object, meaning it is a leaf-level view. Its dependence on a package (PA_PROJ_ELEMENTS_UTILS) is notable: such views often wrap complex package-driven logic (for example functions returning task type or effort-driven defaults) rather than a simple join of tables, which is consistent with an "Internal" view type. The primary persistence of task scheduling detail resides in PA_PROJ_ELEM_VER_SCHEDULE, keyed by project element and element version.

Key Columns

Common Use Cases and Queries

Typical usage is diagnostic: confirming the effort-driven setting, levelling behaviour, and constraint configuration of project tasks in a schedule. A representative query is:

SELECT project_id, proj_element_id, element_version_id, def_sch_tool_tsk_type_m, constraint_type_m, constraint_date, effort_driven_flag, level_assignments_flag, free_slack, total_slack, actual_duration, remaining_duration, scheduled_duration FROM apps.pa_task_det_sch_opt_v WHERE project_id = :p_project_id AND effort_driven_flag = 'Y';

Because the view is unsupported for direct access, production reporting should preferably use supported APIs or documented Project Management views; the query above is appropriate for troubleshooting and data verification.