Search Results task_org_id

Overview

The PA_ALLOC_SOURCE_LINES_V view is an Oracle Applications (APPS) owned database view within the Projects (PA) product family, defined over the PA_ALLOC_SOURCE_LINES base synonym. Its purpose is to present allocation source line definitions in a fully denormalized, report-ready format by resolving internal identifiers into human-readable organization names, project numbers, task numbers, and lookup meanings. Allocation rules in Oracle Projects identify the sources of cost that are redistributed across tasks, projects, or organizations; the source lines define which expenditures are eligible. The view enriches those lines so that concurrent programs, Oracle Reports, OBIEE extracts, and Oracle BI Publisher layouts can display descriptive attributes without embedding complex joins and language-secure lookup logic in each consumer. Because the view already performs outer joins to HR organization tables and language-aware translation lookups, it acts as a stable integration surface for both seeded Projects allocation screens and customer-built reporting. The view is documented as VALID in the EBS 12.1.1 and 12.2.2 releases and carries standard WHO audit columns for change tracking.

Underlying Base Objects

The view is defined over several base objects, each joined to the allocation source line record:

• PA_ALLOC_SOURCE_LINES (SYNONYM) — the driving table holding rule lines, organization IDs, project/task references, classification, and service type.
• HR_ORG_UNITS_NO_JOIN (VIEW) — referenced twice as HOU1 and HOU2 to resolve PROJECT_ORG_ID and TASK_ORG_ID without invoking HR security or additional date-track joins. The "_NO_JOIN" suffix denotes a lightweight organization view that avoids the organization hierarchy joins present in HR_ORGANIZATION_UNITS.
• HR_ALL_ORGANIZATION_UNITS_TL (SYNONYM) — referenced as HRTL1 and HRTL2 to supply the translated organization NAME for each organization, filtered by USERENV('LANG') with a DECODE guard for null organizations.
• PA_PROJECTS_ALL (SYNONYM), PA_TASKS (SYNONYM) — provide project number, project name, task number, and task name.
• PA_LOOKUPS (VIEW) — resolves SERVICE_TYPE into a meaning using LOOKUP_TYPE = 'SERVICE TYPE'.
• HR_GENERAL and HR_SECURITY (PACKAGEs) — support HR organization security and language handling used by the underlying HR objects.

All joins to HR and Projects masters are outer joins (+) except the service type lookup, which tolerates missing codes via the LOOKUP_TYPE (+) predicate. This ensures allocation lines are never lost when an organization, project, task, or lookup value is absent.

Key Columns

The view exposes 24 columns. Principal among them are:

• ROW_ID — pseudo-column identifying the underlying PA_ALLOC_SOURCE_LINES row for update-safe processing.
• RULE_ID / LINE_NUM — identify the parent allocation rule and line sequence.
• PROJECT_ORG_ID / PROJECT_ORG_NAME and TASK_ORG_ID / TASK_ORG_NAME — the owning and task organizations, with translated names resolved through the HR tables.
• PROJECT_ID, PROJECT_NUMBER, PROJECT_NAME — the project context of the source line.
• TASK_ID, TASK_NUMBER, TASK_NAME — the task context.
• PROJECT_TYPE, CLASS_CATEGORY, CLASS_CODE — classification criteria that scope which expenditures are selected.
• SERVICE_TYPE, SERVICE_TYPE_MEANING — the expenditure service type and its decoded lookup meaning.
• EXCLUDE_FLAG — indicates whether matching expenditure is excluded from allocation.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical consumers include allocation rule inquiry screens, diagnostic reports verifying source line configuration, and integration extracts feeding costing or budgeting systems. A representative query for auditing allocation rule sources follows:

• SELECT rule_id, line_num, project_org_name, task_org_name, project_number, project_name, task_number, service_type_meaning, exclude_flag FROM pa_alloc_source_lines_v WHERE rule_id = :p_rule_id ORDER BY line_num;
• Reporting allocation coverage by organization: SELECT project_org_name, service_type_meaning, COUNT(*) FROM pa_alloc_source_lines_v GROUP BY project_org_name, service_type_meaning;
• Identifying lines missing project or task masters (outer-join gaps): SELECT rule_id, line_num FROM pa_alloc_source_lines_v WHERE project_id IS NOT NULL AND project_number IS NULL;

Because the view relies on USERENV('LANG') and HR organization security packages, querying through APPS with a correctly initialized session is required to obtain accurate translated names and security filtering.