Results for “work_breakdown_structure_level”

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

Overview

PABV_TASKS is a read-only Oracle EBS view owned by the APPS schema and shipped as part of the PA (Projects) product family. It exists specifically to expose project task (WBS element) information alongside the security-relevant attributes of the parent project. According to the ETRM metadata, the view is marked "Retrofitted" and carries a status of VALID in both 12.1.1 and 12.2.2. Its implementation terminates with the WITH READ ONLY clause, reinforcing that it is intended for query and reporting purposes rather than as a maintenance interface. In the Oracle EBS reporting and integration stack, PABV_TASKS is most often encountered behind Oracle Business Intelligence (OBIEE) subject areas, Discoverer workbooks, custom concurrent program reports, and inbound/outbound interfaces that need task-level identity without granting direct access to the PA_TASKS base table.

Underlying Base Objects

The view is defined over two documented base synonyms: PA_TASKS (aliased PT) and PA_PROJECTS_ALL (aliased PPA), both resolved in the APPS schema. The join is a straightforward inner join on PT.PROJECT_ID = PPA.PROJECT_ID. Critically, the WHERE clause includes the security predicate '_SEC:PPA.ORG_ID' IS NOT NULL, which is the Oracle-deployed row-level security construct that ensures the view respects the operating unit (ORG_ID) access of the querying responsibility. Because of this predicate, the view participates in the Multi-Org Access Control (MOAC) model — any user running it through a responsibility that lacks ORG_ID context, or whose responsibility excludes the owning operating unit, will either see no rows or receive an error. This places PABV_TASKS firmly in the "secured reporting view" category rather than as a generic passthrough.

Key Columns

The projection list contains the standard task identity columns plus several delayed-resolution ("_LA:") and descriptive-flexfield ("_DF:") placeholders that Oracle Fusion middle-tier tooling resolves at runtime:

• TASK_ID, TASK_NUMBER, TASK_NAME, DESCRIPTION — core task identity attributes carried straight from PA_TASKS.
• WORK_BREAKDOWN_STRUCTURE_LEVEL — maps to PT.WBS_LEVEL, indicating the task's depth in the WBS tree.
• "_LA:SERVICE_TYPE" — resolves PT.SERVICE_TYPE_CODE against the PA_LOOKUPS SERVICE TYPE meaning.
• "_DF" — the PA_TASKS_DESC_FLEX descriptive flexfield descriptor.
• START_DATE, COMPLETION_DATE — task scheduling dates.
• "_LA:PM_PRODUCT" and PM_TASK_REFERENCE — project-manufacturing cross reference.
• PARENT_TASK_ID, TOP_TASK_ID — hierarchical pointers enabling parent/child roll-ups and top-task grouping.
• PROJECT_ID — the foreign key to PA_PROJECTS_ALL that also drives the security join.
• CARRYING_OUT_ORGANIZATION_ID — the performing organization.
• TASK_MANAGER_PERSON_ID — the person responsible for the task, and the column users most frequently search for against this view.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard audit trail columns.

Common Use Cases and Queries

Because the user searched for "task_manager_person_id," the most immediate use case is resolving which employee owns a given WBS task. A typical form is:

SELECT task_number, task_name, project_id, task_manager_person_id
FROM apps.pabv_tasks
WHERE project_id = :p_project_id
AND task_manager_person_id IS NOT NULL;

Other frequent scenarios include WBS hierarchy reporting (using PARENT_TASK_ID and TOP_TASK_ID), status and service-type listing via the _LA placeholders, and joining back to PER_PERSON_NAMES_F on TASK_MANAGER_PERSON_ID to display the manager's full name. The read-only nature of the view makes it safe for ad hoc queries and OBIEE extractions, while the ORG_ID security predicate guarantees results remain bound to the responsibility's operating unit in both EBS 12.1.1 and 12.2.2.