Results for “active_cwk”

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

Overview

APPS.PA_C_RESOURCE_V is a reporting and integration view in Oracle EBS 12.1.1 and 12.2.2 that presents a consolidated, current picture of project resources drawn from Oracle HRMS person and assignment data joined to Oracle Projects resource definitions. The view supplies one row per active primary assignment for employees and contingent workers, exposing person identifiers, names, resource type, employee or NPW number, and the owning HR organization. Because it resolves current-row conditions dynamically (using trunc(sysdate) against effective-dated person and assignment records), the view always returns the resource state as of the query run date rather than requiring callers to pass an effective date.

The view is commonly consumed by Oracle Projects resource management, cross-charging, and third-party integrations that need a lightweight resource lookup without navigating the full PER_PEOPLE_F and PER_ASSIGNMENTS_F date-effective model. The search term "active_cwk" refers directly to the filter predicate ast.per_system_status in ('ACTIVE_ASSIGN', 'ACTIVE_CWK'), which admits both active employee assignments (ACTIVE_ASSIGN) and active contingent worker assignments (ACTIVE_CWK). Note that the view text as documented does not correctly parenthesize this IN list, so PA_C_RESOURCE_V should be treated as a reference or lineage object rather than a substitute for a validated custom query.

Underlying Base Objects

The documented base objects and their roles are:

• PER_PEOPLE_F (view) — supplies person identity and name attributes, plus the current employee/NPW flags and numbers.
• PER_ASSIGNMENTS_F (view) — supplies the primary assignment, assignment type, job, and effective dates.
• PER_ASSIGNMENT_STATUS_TYPES (synonym) — supplies per_system_status, the column that carries the ACTIVE_ASSIGN and ACTIVE_CWK values.
• PA_RESOURCES (synonym) — supplies the Projects resource_id and resource_type_id linkage.
• PA_RESOURCE_TYPES (synonym) — supplies resource_type_code.
• PA_RESOURCE_TXN_ATTRIBUTES (synonym) — outer-joined on person_id and resource_id to attach transaction attributes.
• PA_RESOURCE_UTILS (package) — its get_organization_name function resolves the HR organization name for the assignment's organization_id.
• HR_GENERAL, HR_PERSON_NAME, HR_SECURITY (packages) — referenced by the person/assignment views for name formatting, date-track handling, and security.

Person, assignment, and transaction-attribute joins are outer joins (indicated by (+) on the Projects side), so a person lacking a matching PA_RESOURCES row still appears with null resource columns.

Key Columns

• RESOURCE_SOURCE_ID — the person_id of the resource.
• RESOURCE_ID — the PA_RESOURCES identifier for the person, used in project transaction tables.
• RESOURCE_NAME, RESOURCE_FIRST_NAME, RESOURCE_LAST_NAME, RESOURCE_MIDDLE_NAMES — full and component person names.
• RESOURCE_TYPE, RESOURCE_TYPE_ID — the resource type code and its surrogate key.
• RESOURCE_NUMBER — derived via DECODE: the employee number for current employees, otherwise the NPW number.
• RESOURCE_ORGANIZATION_ID, RESOURCE_ORGANIZATION_NAME — the assignment's organization and its resolved name.
• ASSIGNMENT_START_DATE, ASSIGNMENT_END_DATE — the effective start and end dates of the selected primary assignment.

Common Use Cases and Queries

Typical scenarios include populating resource LOVs for project expenditure or time entry, validating resources for integrations, and reconciling Projects resource records against HRMS assignments — particularly to isolate contingent workers.

List active contingent workers exposed by the view:

SELECT resource_id, resource_number, resource_name
FROM   apps.pa_c_resource_v
WHERE  resource_type IS NOT NULL
ORDER BY resource_name;

Join the view to project expenditure items to attribute costs to resources:

SELECT r.resource_name, x.expenditure_item_date, x.burdened_cost
FROM   apps.pa_c_resource_v r,
       apps.pa_expenditure_items_all x
WHERE  x.resource_id = r.resource_id
AND    x.expenditure_item_date >= TRUNC(SYSDATE) - 30;

Because the embedded IN-list predicate is documented without parentheses, production queries should not rely on this view's ACTIVE_CWK filtering as written. Instead, reuse the underlying join logic against PER_ASSIGNMENTS_F, PER_ASSIGNMENT_STATUS_TYPES, and PA_RESOURCES, applying per_system_status IN ('ACTIVE_ASSIGN','ACTIVE_CWK') explicitly and predicate-checking with EXPLAIN PLAN, since unparenthesized conditions can alter results and prevent index use.