Search Results project_start_date

Overview

AP_WEB_PA_PROJECTS_TASKS_V is a view owned by the APPS schema within the Oracle Payables (AP) product family. In Oracle Internet Expenses, both the Projects and Tasks function and the Task Number list of values are based on this view, making it the primary data source through which expense-line project and task validation is performed. The view joins project, task, organization, and grant-award data into a single denormalized result set, exposing the identifiers, descriptive attributes, and date ranges that Internet Expenses requires when an employee charges an expense to a project and task combination.

The object carries a VALID status in ETRM and is documented for Oracle EBS 12.1.1 and 12.2.2. Because it filters tasks on CHARGEABLE_FLAG = 'Y', the view returns only those project/task combinations that are eligible to receive charges, which is the behavioral foundation of both the Projects and Tasks function and the Task Number list of values in Internet Expenses.

Underlying Base Objects

The view text selects from four primary sources: PA_TASKS_EXPEND_V (aliased T), PA_PROJECTS_EXPEND_V (aliased P), HR_ORGANIZATION_UNITS (aliased O), and GMS_SSA_AWARDS_V (aliased GMS). The joins are defined as T.PROJECT_ID = P.PROJECT_ID, P.CARRYING_OUT_ORGANIZATION_ID = O.ORGANIZATION_ID, and GMS.PROJECT_ID(+) = P.PROJECT_ID. The task filter T.CHARGEABLE_FLAG = 'Y' restricts output, and the DISTINCT operator eliminates duplicate combinations.

Documented referenced objects include the packages AP_WEB_FND_LOOKUPS_PKG, FND_PROFILE, HR_GENERAL, HR_SECURITY, PA_CROSS_BUSINESS_GRP, PA_PROJECT_UTILS, PA_TASK_UTILS, and PA_UTILS4, in addition to the views GMS_SSA_AWARDS_V, HR_ORGANIZATION_UNITS, PA_PROJECTS_EXPEND_V, and PA_TASKS_EXPEND_V. The security packages (HR_SECURITY, PA_CROSS_BUSINESS_GRP) are significant because the underlying expend views enforce operating-unit and cross-business-group access rules, so results are inherently filtered by the responsibility's security profile. AP_WEB_FND_LOOKUPS_PKG.GETYESNOMEANING supplies the decoded ALLOW_CHARGES value.

Key Columns

• PROJECT_ID, PROJECT_NAME, PROJECT_NUMBER, PROJECT_DESCRIPTION, PROJECT_TYPE — project identifiers and descriptive attributes.
• PROJECT_START_DATE, PROJECT_COMPLETION_DATE — the project date range; PROJECT_COMPLETION_DATE is the alias of P.COMPLETION_DATE.
• PROJECT_ORGANIZATION_ID, PROJECT_ORGANIZATION_NAME — the carrying-out organization of the project.
• TASK_ID, TASK_NUMBER, TASK_NAME — task identifiers and descriptive attributes.
• TASK_START_DATE, TASK_COMPLETION_DATE — the task date range; TASK_COMPLETION_DATE is the alias of T.COMPLETION_DATE and is the column users typically search for when reconciling task end dates. The completion date may be null for open-ended tasks and is stored as a date, so it may carry a time component.
• CHARGEABLE_FLAG, ALLOW_CHARGES — CHARGEABLE_FLAG is always 'Y' in the output; ALLOW_CHARGES renders the corresponding Yes/No lookup meaning.
• AWARD_NUMBER, AWARD_SHORT_NAME, AWARD_START_DATE, AWARD_CLOSE_DATE, AWARD_END_DATE, AWARD_ORGANIZATION_NAME — grant-management award attributes sourced through the outer join to GMS_SSA_AWARDS_V, null for non-award projects.

Common Use Cases and Queries

The principal use case is supplying the Projects and Tasks function and the Task Number list of values in Internet Expenses. Reporting queries commonly join the view to expense distributions, or filter by task completion date to identify tasks approaching or past their end date.

SELECT project_number,
       project_name,
       task_number,
       task_name,
       task_start_date,
       task_completion_date
  FROM apps.ap_web_pa_projects_tasks_v
 WHERE task_completion_date IS NOT NULL
   AND task_completion_date < SYSDATE
 ORDER BY task_completion_date;

To retrieve the valid charge combinations for a given project:

SELECT t.task_number,
       t.task_name,
       t.allow_charges,
       t.project_organization_name,
       t.award_number
  FROM apps.ap_web_pa_projects_tasks_v t
 WHERE t.project_number = :project_number
 ORDER BY t.task_number;

Because HR_SECURITY and cross-business-group logic are applied within the underlying expend views, query results depend on the operating unit and security profile of the session, and direct SQL against the view should account for that filtering. Regardless of the query pattern, CHARGEABLE_FLAG = 'Y' means only chargeable tasks are ever returned.