Search Results available_24_hrs_flag




Overview
Explore in AI Chat

Overview

WIP_RES_INST_EMPLOYEES_V is a Work in Process (WIP) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. As its ETRM description states, it presents "employee resource instances" — that is, the intersection of manufacturing resources that are of the employee type (BOM_RESOURCES.RESOURCE_TYPE = 2) with the specific employees who staff those resources inside a department and organization. The view consolidates department, resource, and person attributes into a single denormalized result set so that shop-floor scheduling, capacity planning, and resource-utilization reporting can join resource data directly to employee identity without navigating the full BOM and HR table hierarchy.

Because it exposes a resolved FULL_NAME and EMPLOYEE_ID alongside resource-level planning attributes, the view is frequently used in custom reports, concurrent program queries, and integration extracts that need to answer "which named employees are available to work a given resource?" It is a read-only view; no DML is permitted against it.

Underlying Base Objects

The view is defined over six documented base objects, all referenced through the APPS schema:

Joins are performed on RESOURCE_ID, DEPARTMENT_ID, and ORGANIZATION_ID, with effective-date alignment enforced between PER_ALL_PEOPLE_F and BOM_RESOURCE_EMPLOYEES.

Key Columns

  • ORGANIZATION_ID, DEPARTMENT_ID, DEPARTMENT_CODE — organizational context of the resource instance.
  • RESOURCE_ID, RESOURCE_CODE — the underlying BOM resource.
  • INSTANCE_ID, EMPLOYEE_ID, FULL_NAME — the specific person assigned to the resource instance.
  • AVAILABLE_24_HRS_FLAG (ML2.MEANING) — decoded from SYS_YES_NO; this is the column most commonly searched by users, indicating whether the resource is available around the clock.
  • CAPACITY_UNITS, RESOURCE_GROUP_NAME, CTP_FLAG, ATP_RULE_ID, EXCEPTION_SET_NAME — planning and scheduling attributes.
  • RESOURCE_TYPE, BASIS_TYPE — decoded lookup meanings for resource classification and cost basis.
  • SHARE_FROM_DEPARTMENT — derived with NVL, defaulting to the department code.
  • Costing columns — COST_ELEMENT_ID, PURCHASE_ITEM_ID, STANDARD_RATE_FLAG, ABSORPTION_ACCOUNT, RATE_VARIANCE_ACCOUNT, EXPENDITURE_TYPE, AUTOCHARGE_TYPE, and ALLOW_COSTS_FLAG.

Common Use Cases and Queries

Typical uses include listing named employees per resource for capacity studies, filtering resources that are available 24 hours, and feeding resource-employee mappings into custom integrations.

List employees staffed to 24-hour resources in an organization:

SELECT resource_code, full_name, employee_id, available_24_hrs_flag
FROM   apps.wip_res_inst_employees_v
WHERE  organization_id = :org_id
AND    available_24_hrs_flag = 'Yes';

Capacity summary by department and resource group:

SELECT department_code, resource_group_name, resource_code,
       SUM(capacity_units) total_capacity
FROM   apps.wip_res_inst_employees_v
WHERE  organization_id = :org_id
GROUP  BY department_code, resource_group_name, resource_code;

Search by employee name across departments:

SELECT department_code, resource_code, full_name
FROM   apps.wip_res_inst_employees_v
WHERE  full_name LIKE :name_pattern;

Because the view decrypts lookup meanings, report authors can present the AVAILABLE_24_HRS_FLAG and RESOURCE_TYPE values directly to end users without additional lookup joins.