Results for “constraint_type_code”

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

Overview

PA_TASK_DET_SCH_OPT_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Projects (PA) product family. It exposes scheduling detail and options information for project tasks at the element-version level. Specifically, the view denormalizes rows from PA_PROJ_ELEM_VER_SCHEDULE, the table that stores per-task scheduling attributes for a given project element version, and decorates selected code columns with their corresponding Oracle FND lookup meanings.

In the context of ETRM 12.1.1 and 12.2.2, the view serves as a read-only presentation layer. It is typically consumed by scheduling, progress, and project-status reporting, by extracts feeding external scheduling tools such as Primavera or Microsoft Project, and by integration programs that need decoded scheduling metadata rather than raw code values. Because it is a view over a versioned scheduling table, it reflects scheduling state as of the element version selected by the calling application or report.

Underlying Base Objects

The view is defined over two documented objects:

• PA_PROJ_ELEM_VER_SCHEDULE (SYNONYM) — the primary source, aliased SCH in the view definition. It supplies project, element, and version identifiers along with scheduling task type, constraint type, constraint date, slack values, flags, record version, and the three duration columns.
• PA_PROJ_ELEMENTS_UTILS (PACKAGE) — a PL/SQL utility package invoked in the SELECT list through GET_FND_LOOKUP_MEANING. It resolves PA_SCHEDULE_TASK_TYPE and PA_SCHEDULE_CONSTRAINT_TYPE lookup codes into their display meanings.

Because the package function is called per row, the view carries a PL/SQL context switch for every row returned; this is relevant when the view is queried at high volume.

Key Columns

The view projects the following significant columns:

• PROJECT_ID, PROJ_ELEMENT_ID, ELEMENT_VERSION_ID — the composite key linking the scheduling record to a specific project, task (proj element), and element version.
• DEF_SCH_TOOL_TSK_TYPE_CODE / DEF_SCH_TOOL_TSK_TYPE_M — the code and decoded meaning of the default scheduling task type, based on the PA_SCHEDULE_TASK_TYPE lookup.
• CONSTRAINT_TYPE_CODE / CONSTRAINT_TYPE_M — the scheduling constraint code and its decoded meaning from the PA_SCHEDULE_CONSTRAINT_TYPE lookup.
• CONSTRAINT_DATE — the date associated with the scheduling constraint.
• FREE_SLACK and TOTAL_SLACK — float values describing scheduling flexibility for the task, as used in critical-path analysis.
• EFFORT_DRIVEN_FLAG and LEVEL_ASSIGNMENTS_FLAG — flags governing how durations respond to resource assignment changes and whether assignments are leveling-controlled.
• PEVS_RECORD_VERSION_NUMBER — the record version number from the underlying scheduling row.
• ACTUAL_DURATION, REMAINING_DURATION, SCHEDULED_DURATION — duration measures. These are surfaced from the base columns EXT_ACT_DURATION, EXT_REMAIN_DURATION, and EXT_SCH_DURATION respectively. The view therefore answers the common search term "actual_duration" by presenting ACTUAL_DURATION to callers.

Common Use Cases and Queries

Typical uses are project scheduling analysis, progress versus plan reporting, and extraction to external schedulers. Sample queries follow.

Task durations and decoding for a project:

• SELECT project_id, proj_element_id, element_version_id, def_sch_tool_tsk_type_m, actual_duration, remaining_duration, scheduled_duration, total_slack FROM pa_task_det_sch_opt_v WHERE project_id = :p_project_id;

Constraint analysis across current element versions:

• SELECT proj_element_id, constraint_type_m, constraint_date, free_slack, total_slack FROM pa_task_det_sch_opt_v WHERE constraint_type_code IS NOT NULL ORDER BY constraint_date;

Actual versus scheduled duration variance:

• SELECT project_id, proj_element_id, actual_duration, scheduled_duration, (actual_duration - scheduled_duration) variance FROM pa_task_det_sch_opt_v WHERE project_id = :p_project_id;

Because the view joins no data itself, joins to PA_PROJECTS or PA_TASKS are performed by the calling report when project names or task descriptions are required. Callers should also be aware that scheduling rows are version-scoped, so queries should filter ELEMENT_VERSION_ID or join to the appropriate current-version source to avoid returning superseded records.