Results for “active_cwk”

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

Overview

PA_C_RESOURCE_V is an Oracle EBS Projects (PA) view owned by the APPS schema. It is documented as identifying all resources available for use at this time or in the future, making it the primary published interface for resource lookup and validation within Oracle Projects. In Oracle EBS 12.1.1 and 12.2.2, the object retains VALID status and exists as a read-only view that consolidates person, assignment, and resource setup data into a single consumable result set.

Functionally, the view answers the question "which people can be assigned as project resources right now?" It joins Oracle HRMS person and assignment records against the Projects resource tables, applying date and status filters so that only currently active, primary, non-terminated employees and contingent workers are returned. This makes it central to resource management, assignment, and cost/effort planning workflows, and it is referenced by Oracle Projects forms, concurrent programs, and customer-built reporting. It is also commonly used as a validation source in integrations loading project resource assignments or requirements.

Underlying Base Objects

The view is defined over a combination of Projects synonyms and HRMS views. The documented base objects are:

• PER_PEOPLE_F and PER_ASSIGNMENTS_F — date-tracked HRMS views supplying person identity and assignment details.
• PER_ASSIGNMENT_STATUS_TYPES — used to restrict results to active assignments (PER_SYSTEM_STATUS in 'ACTIVE_ASSIGN', 'ACTIVE_CWK').
• PA_RESOURCES, PA_RESOURCE_TYPES, and PA_RESOURCE_TXN_ATTRIBUTES — Projects resource definitions and person-to-resource mappings, outer-joined via TXN.PERSON_ID(+) and RES.RESOURCE_TYPE_ID(+).
• PA_RESOURCE_UTILS — package supplying the GET_ORGANIZATION_NAME function used to resolve organization names.
• HRMS support packages HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY — typically referenced through the underlying HRMS views and for security/name resolution.

The joins require a single primary assignment (PRIMARY_FLAG = 'Y'), an assignment type of 'E' (employee) or 'C' (contingent worker), a non-null JOB_ID, that today's date falls within the person's effective dates, and that today is on or before the assignment end date. Only the earliest qualifying primary assignment start date is retained via a correlated MIN subquery.

Key Columns

• RESOURCE_SOURCE_ID — the PERSON_ID, the source identifier for the resource.
• RESOURCE_ID — the PA_RESOURCES identifier, linking to project resource records.
• RESOURCE_NAME, RESOURCE_FIRST_NAME, RESOURCE_LAST_NAME, RESOURCE_MIDDLE_NAMES — decomposed name attributes for display and matching.
• RESOURCE_TYPE / RESOURCE_TYPE_ID — the resource type code and its surrogate identifier from PA_RESOURCE_TYPES.
• RESOURCE_NUMBER — employee number for current employees; NPW number otherwise.
• RESOURCE_ORGANIZATION_ID / RESOURCE_ORGANIZATION_NAME — the assignment organization and its resolved name.
• ASSIGNMENT_START_DATE / ASSIGNMENT_END_DATE — the effective range of the selected primary assignment.

Common Use Cases and Queries

Typical uses include resource availability listings, LOV population, validation of resources before assignment creation, and reconciliation of Projects resources against HRMS assignments.

SELECT resource_source_id,
       resource_name,
       resource_number,
       resource_type,
       resource_organization_name
FROM   apps.pa_c_resource_v
WHERE  resource_name LIKE :p_name
ORDER  BY resource_name;

A second pattern counts available resources by organization and type:

SELECT resource_organization_name,
       resource_type,
       COUNT(*) available_resources
FROM   apps.pa_c_resource_v
GROUP  BY resource_organization_name, resource_type
ORDER  BY resource_organization_name;

Because the view embeds SYSDATE-based filters and HR security behavior, results are effective-dated at query time; no bind parameters are required, and the view is safe for read-only reporting. Performance is best when queries constrain RESOURCE_NUMBER or RESOURCE_NAME to limit the HRMS base tables.