Search Results task_start_date




Overview
Explore in AI Chat

Overview

The view PA_SST_VIEW_PROJECTS_TASKS_V is a Projects (PA) module reporting object that consolidates project and task header information into a single, flat result set. It supports the "View Projects and Tasks" function within SST (Self-Service Time), the Oracle EBS self-service timecard interface used by employees to record and review labor against projects and tasks. Rather than requiring the SST code to join project and task data separately, this view presents one denormalized row per task, carrying the parent project attributes alongside the task attributes.

The defining characteristic of the view is that it combines project-level and task-level date, identifier, and control flags. In this context, the column commonly searched as task_start_date corresponds to the view's TASK_START_DATE, while PROJECT_START_DATE and TASK_COMPLETION_DATE provide the related schedule boundaries. Because the view exposes both the project and task start dates under distinct column names, it is suitable for reporting that must reconcile project schedules with the individual tasks that employees charge time to.

Underlying Base Objects

According to the documented view text, PA_SST_VIEW_PROJECTS_TASKS_V is defined over two other Projects views rather than directly over base tables:

  • PA_ONLINE_PROJECTS_V — supplies the project-level columns (project number, name, ID, start and completion dates, and the carrying-out organization ID).
  • PA_ONLINE_TASKS_V — supplies the task-level columns (task number, name, ID, billable flag, task start and completion dates, and chargeable flag).

The two are joined on OP.PROJECT_ID = OT.PROJECT_ID, and the result set is qualified with SELECT DISTINCT, ensuring that duplicated project rows are eliminated when multiple tasks belong to the same project. The view therefore sits one layer above the online validation views, which in turn resolve against the underlying PA_PROJECTS and PA_TASKS tables. The ETRM metadata notes that no base objects are documented directly and that the view is not implemented in the reference database, meaning it is a shipped, seed-data-driven component whose exact column set is governed by the view text quoted above.

Key Columns

  • PROJECT_NUMBER / PROJECT_NAME / PROJECT_ID — the project identifier set, used to display and key the project on SST screens.
  • PROJECT_START_DATE / PROJECT_COMPLETION_DATE — the project schedule boundaries (from OP.START_DATE and OP.COMPLETION_DATE).
  • CARRYING_OUT_ORGANIZATION_ID — the organization responsible for executing the project, relevant to security and cross-charge processing.
  • TASK_NUMBER / TASK_NAME / TASK_ID — the task identifier set used to select a specific task when entering time.
  • TASK_START_DATE — the task start date (from OT.START_DATE); this is the columnmost users locate via the "task_start_date" search term.
  • TASK_COMPLETION_DATE — the task completion date, used to validate whether a timecard date falls within the task window.
  • BILLABLE_FLAG / CHARGEABLE_FLAG — flags indicating whether the task may be billed to a customer and whether it is chargeable for cost collection.

Common Use Cases and Queries

The primary use case is populating the list of values and validation logic behind self-service time entry, ensuring an employee can only select an active, chargeable project/task combination. A representative query retrieving task schedule information follows:

  • SELECT project_number, project_name, task_number, task_name, task_start_date, task_completion_date, chargeable_flag FROM pa_sst_view_projects_tasks_v WHERE project_id = :p_project_id ORDER BY task_number;

Additional scenarios include:

  • Identifying tasks whose start date falls within a given period: SELECT task_number, task_start_date FROM pa_sst_view_projects_tasks_v WHERE task_start_date BETWEEN :start_date AND :end_date;
  • Filtering to billable, chargeable tasks only: SELECT project_number, task_number FROM pa_sst_view_projects_tasks_v WHERE billable_flag = 'Y' AND chargeable_flag = 'Y';
  • Reconciling project and task dates to detect tasks scheduled outside the project window by comparing PROJECT_START_DATE with TASK_START_DATE.

Because the view is security-sensitive, queries should generally be combined with the same organization and project security predicates applied by the SST function to prevent exposure of unauthorized projects and tasks.