Results for “service_type_code”

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

Overview

PA_ALLOC_SRC_TASKS_V is a Projects (PA) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the set of project tasks that are eligible to act as allocation source tasks in the Oracle Projects allocation engine. The view is not a physical table; it is a stored query that filters the PA_TASKS table down to a curated list of "leaf-level or top-level" tasks, governed by a predicate implemented in the PA_TASK_UTILS package.

The view's purpose is to present task records that are valid starting points for allocating costs, burdens, or revenue across a project structure. Because allocation source tasks must be well-defined endpoints (either the top task itself or a task with no living children), the view hides intermediate parent tasks that would otherwise produce ambiguous allocation results. In reporting and integration contexts, PA_ALLOC_SRC_TASKS_V serves as a stable, pre-filtered source for LOVs, allocation setup screens, concurrent program inputs, and custom extracts that must not present non-allocatable tasks to end users.

Underlying Base Objects

The view is defined exclusively over two documented referenced objects:

• PA_TASKS (SYNONYM) — the base table holding project task definitions, including hierarchy relationships via TOP_TASK_ID and the task attribute columns surfaced by the view. PA_TASKS stores one row per task per project, with the top task of a structure carrying TASK_ID equal to TOP_TASK_ID.
• PA_TASK_UTILS (PACKAGE) — a PL/SQL utility package that exposes the function CHECK_CHILD_EXISTS, which returns zero when a given task has no child tasks in the hierarchy. This function supplies the second half of the view's filter predicate.

The defining query is:

SELECT PROJECT_ID, TASK_ID, TASK_NUMBER, TASK_NAME, SERVICE_TYPE_CODE, CARRYING_OUT_ORGANIZATION_ID FROM PA_TASKS WHERE (TASK_ID = TOP_TASK_ID OR PA_TASK_UTILS.CHECK_CHILD_EXISTS(TASK_ID) = 0)

Because the predicate invokes a PL/SQL function on each candidate row, the view is non-mergeable and cannot be tuned by simple index range scans alone; performance depends on the selectivity of the underlying PA_TASKS access path and the cost of evaluating CHECK_CHILD_EXISTS.

Key Columns

• PROJECT_ID — the owning project identifier, used to join to PA_PROJECTS and related project-level entities.
• TASK_ID — the unique task identifier; the primary join key back to PA_TASKS and to transaction tables such as PA_COST_DISTRIBUTION_LINES_ALL.
• TASK_NUMBER — the user-visible task number, commonly the value shown in allocation setup and LOV fields.
• TASK_NAME — the descriptive task name, presented alongside the number in inquiry and reporting output.
• SERVICE_TYPE_CODE — the service type classification of the task (for example, a billable or non-billable service designation). Users searching on this column typically wish to constrain, group, or filter tasks by their service type when configuring or reporting allocations.
• CARRYING_OUT_ORGANIZATION_ID — the identifier of the organization responsible for carrying out the task, supporting organization-based filtering and cross-charging analysis.

Common Use Cases and Queries

Typical scenarios include populating allocation source-task selection lists, validating that a chosen task is a legitimate allocation endpoint, and extracting service-type distributions for allocation analysis. The following sample retrieves all allocatable tasks for a project, constrained by service type:

SELECT task_number, task_name, service_type_code, carrying_out_organization_id
FROM pa_alloc_src_tasks_v
WHERE project_id = :p_project_id
AND service_type_code = :p_service_type_code;

To count allocatable source tasks per service type across projects:

SELECT service_type_code, COUNT(*)
FROM pa_alloc_src_tasks_v
GROUP BY service_type_code;

The view is frequently joined to PA_PROJECTS on PROJECT_ID and to HR organization tables on CARRYING_OUT_ORGANIZATION_ID to render readable allocation setup reports. Because PA_TASK_UTILS.CHECK_CHILD_EXISTS is evaluated per row, queries that return large task sets should be filtered by PROJECT_ID or TASK_ID to keep response times acceptable.