Search Results task_organization

Overview

PA_TASKS_ALL_EXPEND_V is a Projects (PA) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. As documented in the ETRM repository, it provides a view of the tasks for a given project to which expenditures can be charged. The view filters and formats the task hierarchy from PA_TASKS so that only tasks valid for expenditure entry are exposed, applying the proj ect implementation org context and the user's configured task-display preference.

The view is primarily referenced by expenditure entry and reporting components that need a chargeable task picklist restricted to a single operating unit or project. It is not a standalone data store; it is a read-only projection whose content depends on the profile option PA_TASKS_DISPLAYED (read through FND_PROFILE.VALUE) and on cross-charge setup between the implementation organization and the project organization.

Underlying Base Objects

• PA_TASKS (synonym to the base task table) — supplies TASK_ID, TASK_NUMBER, TASK_NAME, dates, flags, and hierarchy pointers.
• PA_PROJECTS_ALL — supplies PROJECT_ID and SEGMENT1 as PROJECT_NUMBER, and the owning ORG_ID.
• PA_IMPLEMENTATIONS_ALL — supplies IMP.ORG_ID, the implementation organization used for organization-based filtering.
• HR_ALL_ORGANIZATION_UNITS — outer-joined (HR.ORGANIZATION_ID (+) = IMP.ORG_ID) to resolve the organization unit.
• PA_LOOKUPS — the PA_TASKS_TO_DISPLAY lookup set drives the CHARGEABLE, ALL, and LOWEST filtering modes.
• PA_TASK_UTILS — package used in the select list (SORT_ORDER_TREE_WALK, CHECK_CHILD_EXISTS) to derive WBS_SORT_ORDER and lowest-level detection.
• FND_PROFILE — supplies the PA_TASKS_DISPLAYED profile value at query time.

The documented metadata also references PA_ALTERNATE_TASKS and PA_RBS_ELEMENTS as related synonyms used by the underlying task infrastructure. Because the view joins on ORG_ID and honors ALLOW_CROSS_CHARGE_FLAG, the same project can appear differently depending on the implementation org of the session.

Key Columns

• PROJECT_ID / PROJECT_NUMBER — project identifier and user-facing project number (P.SEGMENT1).
• TASK_ID / TASK_NUMBER / TASK_NAME — task identity and its display name.
• INDENTED_TASK_NAME — the DECODE expression that pads the task name by WBS level when the ALL display mode is active, producing a hierarchical label.
• WBS_SORT_ORDER — a 2000-character sort key generated by PA_TASK_UTILS.SORT_ORDER_TREE_WALK, enabling correct tree-ordered presentation.
• START_DATE / COMPLETION_DATE — task validity dates.
• CHARGEABLE_FLAG / BILLABLE_FLAG — indicate whether expenditure and billing are permitted.
• ALLOW_CROSS_CHARGE_FLAG — governs whether a task in another organization may be charged.
• LABOR_COST_MULTIPLIER_NAME, PROJECT_RATE_DATE, PROJECT_RATE_TYPE — costing and rate attributes.
• TASK_ORGANIZATION, EXPENDITURE_ORG_ID — organization context columns (the latter mapped from IMP.ORG_ID).
• TASK_DESCRIPTION (from T.DESCRIPTION) — free-form task description.

Common Use Cases and Queries

Typical uses include expenditure-entry task list of values, project cost reporting filtered to chargeable tasks, and integration extracts that must respect organization and cross-charge rules.

• Retrieve chargeable tasks for a project, ordered by WBS:

SELECT project_number, task_number, indented_task_name
FROM   pa_tasks_all_expend_v
WHERE  project_id = :p_project_id
ORDER  BY wbs_sort_order;

• List tasks with billing attributes:

SELECT task_name, chargeable_flag, billable_flag, allow_cross_charge_flag
FROM   pa_tasks_all_expend_v
WHERE  project_id = :p_project_id
AND    chargeable_flag = 'Y';

Because filtering depends on the PA_TASKS_DISPLAYED profile option and the session's implementation org, results are user- and responsibility-sensitive. Queries should therefore be validated under the same session context as the target application screen. The view should not be updated directly; changes are made through the underlying Projects task APIs.