Results for “wipbv_wip_operation_resources”

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

Overview

WIPBV_WIP_OPERATION_RESOURCES is a read-only Oracle EBS view owned by the APPS schema and catalogued under the WIP (Work in Process) product. It presents operation resource requirements and consumption details for both discrete jobs and repetitive schedules, joining resource-level transactions against their parent work orders, operations, and standard operation definitions. The view is flagged WITH READ ONLY, confirming it is intended strictly for reporting, not transactional update. Report authors and integrators commonly search for the column resource_sequence_number, which exposes the ordered position of a resource within its operation and is essential for sequencing and reconciliation queries. Because the view resolves foreign keys to descriptive values via message lookups (the "_LA:" columns), it is well suited for BI Publisher reports, OBIEE/OTBI extracts, and custom SQL used by shop-floor dashboards.

Underlying Base Objects

The view text selects from six synonyms joined together:

• WIP_OPERATION_RESOURCES (OPRE) — the driving table containing the actual resource assignments.
• WIP_ENTITIES (EN) — supplies the work order name (WIP_ENTITY_NAME).
• WIP_OPERATIONS (OP) — the parent operation on the work order, outer-joined on WIP_ENTITY_ID, REPETITIVE_SCHEDULE_ID, OPERATION_SEQ_NUM, and ORGANIZATION_ID.
• BOM_STANDARD_OPERATIONS (ST) — the standard operation definition yielding OPERATION_CODE.
• BOM_DEPARTMENTS (DE) — the department header.
• WIP_DISCRETE_JOBS (DI) and WIP_REPETITIVE_SCHEDULES (RE) — outer-joined to cover both discrete and repetitive manufacturing contexts.

The join logic uses NVL on REPETITIVE_SCHEDULE_ID (-1 for discrete jobs) to accommodate disjoint and repetitive work orders within one result set. An outer join to WIP_OPERATIONS allows resource rows for operations not yet fully defined. The multi-organization security predicate '_SEC:OPRE.ORGANIZATION_ID' enforces operating unit and inventory organization access control at runtime.

Key Columns

• RESOURCE_SEQUENCE_NUMBER — maps to OPRE.RESOURCE_SEQ_NUM; the ordered sequence of the resource on the operation, used for sorting resources within a department/operation.
• RESOURCE_REQUIRED_AMOUNT — OPRE.USAGE_RATE_OR_AMOUNT, the resource units required per assembly or rate basis.
• ASSIGNED_UNITS, APPLIED_RESOURCE_UNITS — quantities assigned versus those actually applied/charged.
• "_LA:SCHEDULE_METHOD" and "_LA:AUTO_CHARGE_TYPE" — lookup-decoded MEANING values from MFG_LOOKUPS (BOM_RESOURCE_SCHEDULE_TYPE, BOM_AUTOCHARGE_TYPE).
• "_LA:PHANTOM_FLAG" — SYS_YES_NO lookup translation.
• START_DATE / COMPLETION_DATE — resource scheduling window.
• MFG_ORDER_NAME, OPERATION_CODE, WIP_ENTITY_ID, REPETITIVE_SCHEDULE_ID, OPERATION_SEQUENCE_NUMBER, ORGANIZATION_ID, RESOURCE_ID, ACTIVITY_ID, DEPARTMENT_ID — the full set of keys needed for drill-down and integration joins.
• Audit columns CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY.

Common Use Cases and Queries

Typical scenarios include resource load reporting by operation, phantom resource analysis, and variance between assigned and applied resource units.

Resource sequencing report for a discrete job:

SELECT wip_entity_name, operation_sequence_number,
       resource_sequence_number, resource_id,
       resource_required_amount, assigned_units,
       applied_resource_units
FROM   apps.wipbv_wip_operation_resources
WHERE  wip_entity_id = :p_wip_entity_id
ORDER  BY operation_sequence_number, resource_sequence_number;

Resource consumption by organization and department:

SELECT organization_id, department_id, operation_code,
       resource_id, SUM(applied_resource_units) applied_units
FROM   apps.wipbv_wip_operation_resources
GROUP  BY organization_id, department_id, operation_code, resource_id;

Because resource_sequence_number holds the resource's position on the operation, ordering by it is required when rebuilding resource detail in downstream integrations or when verifying resource renumbering after a routed operation change.