Search Results track_as_labor_flag




Overview
Explore in AI Chat

Overview

PA_QUERY_RES_LIST_MEMBERS_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 ETRM, the view "displays all the Resource List Members which have been defined for a Resource List." Resource lists are the foundational containers that determine which people, organizations, jobs, and non-labor resources may be assigned to a project or used within project planning, budgeting, and costing. This view provides a flattened, query-friendly projection of those member definitions, joining member attributes to their parent resource lists, resource types, and transaction attributes.

The view is intended for reporting and integration rather than transactional maintenance. It surfaces the labor-tracking attribute TRACK_AS_LABOR_FLAG, which is the column users most frequently search for when interrogating this object. Because the view resolves resource names through PL/SQL (PA_RESOURCES_PKG.GET_RESOURCE_NAME) and filters on display and enabled flags, it presents a curated, human-readable roster of active list members suitable for extracts and dashboards.

Underlying Base Objects

The view is defined over several base and dependent objects in the APPS schema. The documented referenced objects include PA_RESOURCE_LISTS (VIEW), PA_RESOURCE_LIST_MEMBERS (SYNONYM), PA_RESOURCES (SYNONYM), PA_RESOURCE_TYPES (SYNONYM), PA_RESOURCE_TXN_ATTRIBUTES (SYNONYM), PA_EMPLOYEES (VIEW), PA_JOBS_V (VIEW), PA_ORGANIZATIONS_V (VIEW), and PO_VENDORS (VIEW). Supporting PL/SQL packages referenced include PA_RESOURCES_PKG, PA_UTILS, PA_CROSS_BUSINESS_GRP, FND_PROFILE, and HR security/name packages (HR_GENERAL, HR_PERSON_NAME, HR_SECURITY).

The view text is a UNION of two branches. The first branch covers non-labor resource types, excluding RESOURCE_TYPE_CODE values of 'EMPLOYEE', 'VENDOR', 'ORGANIZATION', and 'JOB'. The second branch covers employee resources, joining PA_EMPLOYEES to expose LAST_NAME and FIRST_NAME. Both branches join PA_RESOURCE_LIST_MEMBERS (aliased RLM2 for the member and RLM1 for the parent member), PA_RESOURCE_LISTS, PA_RESOURCES, PA_RESOURCE_TYPES, and an outer join to PA_RESOURCE_TXN_ATTRIBUTES. Members are restricted to DISPLAY_FLAG = 'Y' and ENABLED_FLAG = 'Y'.

Key Columns

  • RESOURCE_LIST_ID / NAME: Identifier and name of the parent resource list.
  • GET_RESOURCE_NAME(...): Resolved name of the member resource.
  • RESOURCE_TYPE_CODE / Resource Type NAME: Classifies the member (e.g., employee, organization, job, or non-labor type).
  • ALIAS: Member alias or parent member alias, with NVL to a space.
  • PARENT_MEMBER_ID: Self-referencing hierarchy pointer, defaulted to 0 when null.
  • LAST_NAME / FIRST_NAME: Populated only for employee members.
  • RESOURCE_LIST_MEMBER_ID / SORT_ORDER: Member identity and display ordering.
  • ENABLED_FLAG: Enabled state of the member.
  • UNIT_OF_MEASURE: Unit of measure for the resource.
  • TRACK_AS_LABOR_FLAG: Indicates whether the non-labor resource is tracked as labor.
  • EVENT_TYPE, EXPENDITURE_TYPE, EXPENDITURE_CATEGORY, REVENUE_CATEGORY: Default transaction attributes sourced from PA_RESOURCE_TXN_ATTRIBUTES.
  • MIGRATION_CODE: Migration reference for the member.

Common Use Cases and Queries

Typical uses include auditing which resources are enabled on a list, identifying non-labor resources flagged for labor tracking, and extracting list membership for integration. A representative query selecting the labor-tracking attribute is:

SELECT resource_list_id, name, resource_list_member_id, alias, resource_type_code, track_as_labor_flag
FROM apps.pa_query_res_list_members_v
WHERE resource_type_code = 'EXPENDITURE_TYPE';

To find all members tracking as labor on a specific list, filter on the flag:

SELECT name, alias, resource_list_member_id, track_as_labor_flag
FROM apps.pa_query_res_list_members_v
WHERE resource_list_id = :p_list_id
AND track_as_labor_flag = 'Y';

Because the view filters out disabled and hidden members, it returns only currently active roster entries, making it well suited to validation reports and downstream interfaces that must respect enabled definitions.