Results for “instance_id”

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

Overview

The APPS.WIP_PCB_RES_INST_EQUIPMENTS_V view is a Work in Process (WIP) object that serves as a base view for the Production Control Board (PCB) in Oracle E-Business Suite releases 12.1.1 and 12.2.2. Its purpose is to expose the relationship between manufacturing resources, the departments that own those resources, and the specific equipment instances assigned to them. In Oracle EBS, a resource such as a machine, tool, or workstation can be associated with one or more equipment instances, each identified by an inventory item and a serial number. This view flattens that association into a single, query-friendly row set.

Because it is a view rather than a table, it stores no data of its own; it presents a live, read-only projection of the underlying resource and equipment configuration. It is typically consumed by the Production Control Board and related shop-floor scheduling or resource-loading features, and it is equally useful for custom reporting and integration where a denormalized list of resource-to-equipment mappings is required.

Underlying Base Objects

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

• BOM_RESOURCES — the master list of resources, filtered to RESOURCE_TYPE = 1 (equipment resources).
• BOM_DEPARTMENTS — the departments that own the resources.
• BOM_DEPARTMENT_RESOURCES — the intersection table linking departments and resources.
• BOM_RESOURCE_EQUIPMENTS — the association between a resource and its installed equipment (inventory item plus serial).
• MTL_SYSTEM_ITEMS_KFV — the key-flexfield view of items, used to resolve the equipment's concatenated item segments.
• MTL_SERIAL_NUMBERS — the serial number master, supplying the instance serial number.

Joins are made on RESOURCE_ID between BOM_RESOURCES, BOM_DEPARTMENT_RESOURCES, and BOM_RESOURCE_EQUIPMENTS; on DEPARTMENT_ID between BOM_DEPARTMENTS and BOM_DEPARTMENT_RESOURCES; and on INVENTORY_ITEM_ID plus ORGANIZATION_ID linking the equipment association to both the item key-flexfield view and the serial number table. The view is defined WITH READ ONLY, confirming its reporting-only intent.

Key Columns

• ORGANIZATION_ID — the inventory organization in which the equipment item is defined.
• DEPARTMENT_ID — the department owning the resource.
• RESOURCE_ID — the unique identifier of the resource.
• RESOURCE_CODE — the user-facing resource name/code from BOM_RESOURCES.
• INSTANCE_ID — the equipment instance identifier carried from BOM_RESOURCE_EQUIPMENTS.
• INSTANCE_NAME — the concatenated item flexfield segments (MSIK.CONCATENATED_SEGMENTS), identifying the equipment item.
• SERIAL_NUMBER — the serial number of the specific equipment unit.
• NODE_LABEL — a derived display value combining the instance name and serial number (INSTANCE_NAME || ':' || SERIAL_NUMBER), used as a readable identifier on the Production Control Board.

Common Use Cases and Queries

Typical uses include listing all equipment assigned to a department's resources, resolving which physical machine a resource represents, and driving PCB displays or custom shop-floor dashboards. A representative query to list equipment by department is:

• SELECT department_id, resource_code, instance_name, serial_number, node_label FROM apps.wip_pcb_res_inst_equipments_v WHERE organization_id = :org_id ORDER BY resource_code;
• SELECT resource_id, node_label FROM apps.wip_pcb_res_inst_equipments_v WHERE department_id = :dept_id;
• Join to BOM_DEPARTMENTS on DEPARTMENT_ID to obtain department names for reporting, since the view itself exposes only the numeric department identifier.

All queries should be scoped by organization and department where applicable, and because the view is read-only, it must never be targeted by DML.