Search Results phantom_flag

Overview

The WIP_SUB_OPERATION_RESOURCES_V view is an APPS-owned, valid database object within the Work in Process (WIP) module of Oracle E-Business Suite, applicable to releases 12.1.1 and 12.2.2. It is documented as providing foreign-key data for WIP_OPERATION_RESOURCES, exposing the resource requirements assigned to operations within discrete jobs and repetitive schedules. The view is a denormalized read-only construct that joins the underlying operation resource table to descriptive master data such as resource codes, unit-of-measure classes, activity names, and lookup meanings. Administrators and developers consult this view when building reports, interfaces, or custom inquiries that must present resource assignment details without performing multiple manual joins.

Because it supplies resolved descriptive columns alongside numeric rate and quantity attributes, the view is particularly useful for reporting resource loading, scheduled versus applied consumption, and remaining open quantities. The user query "scheduled_units" maps directly to the derived SCHEDULED_UNITS column computed inside this view.

Underlying Base Objects

The view is defined over the following documented base objects and synonyms:

• WIP_SUB_OPERATION_RESOURCES — the primary driving table, aliased WOR, holding resource assignments per WIP entity, operation sequence, and resource sequence.
• BOM_RESOURCES — supplies RESOURCE_CODE and PURCHASE_ITEM_ID.
• BOM_DEPARTMENTS — referenced for department-level resource context.
• CST_ACTIVITIES — supplies the ACTIVITY description.
• MFG_LOOKUPS — resolves AUTOCHARGE_TYPE into the AUT OCHARGE_CODE meaning.
• MTL_UOM_CONVERSIONS — supplies the UOM_CLASS for the resource unit of measure.
• WIP_DISCRETE_JOBS — provides START_QUANTITY for discrete job scheduling.
• WIP_REPETITIVE_SCHEDULES — provides DAILY_PRODUCTION_RATE and PROCESSING_WORK_DAYS for repetitive scheduling.

The relationship is driven from WOR (WIP_SUB_OPERATION_RESOURCES), enriched through outer joins to resource, activity, and unit-of-measure definitions, and conditionally to discrete job or repetitive schedule data depending on the BASIS_TYPE and REPETITIVE_SCHEDULE_ID.

Key Columns

• WIP_ENTITY_ID, OPERATION_SEQ_NUM, RESOURCE_SEQ_NUM — composite identifiers of the resource assignment.
• RESOURCE_CODE, RESOURCE_ID — human-readable and surrogate resource identifiers.
• USAGE_RATE_OR_AMOUNT — the resource usage rate; the view also exposes the rounded value and an "INVERSE" (1/rate).
• SCHEDULED_UNITS — derived as USAGE_RATE_OR_AMOUNT multiplied by a basis factor (job START_QUANTITY for discrete jobs, or DAILY_PRODUCTION_RATE × PROCESSING_WORK_DAYS for repetitive schedules when BASIS_TYPE = 1), returned as NULL when the result rounds to zero.
• APPLIED_RESOURCE_UNITS and QUANTITY_OPEN — actual applied units and the derived remaining quantity.
• BASIS_TYPE, SCHEDULED_FLAG, STANDARD_RATE_FLAG, AUTOCHARGE_CODE — scheduling and costing attributes.
• UOM_CODE, UOM_CLASS, ACTIVITY, START_DATE, COMPLETION_DATE, and audit columns.

Common Use Cases and Queries

Typical scenarios include resource-loading reports for a discrete job or repetitive schedule, and reconciliation of scheduled versus applied resource quantities.

SELECT wip_entity_id, operation_seq_num, resource_code,
       usage_rate_or_amount, scheduled_units, quantity_open
FROM   apps.wip_sub_operation_resources_v
WHERE  wip_entity_id = :p_wip_entity_id
ORDER  BY operation_seq_num, resource_seq_num;

To isolate resources with remaining open quantities:

SELECT wip_entity_id, operation_seq_num, resource_code, quantity_open
FROM   apps.wip_sub_operation_resources_v
WHERE  quantity_open IS NOT NULL;

To summarize scheduled units by resource across jobs using the SCHEDULED_UNITS column the user searched for, analysts aggregate on RESOURCE_CODE. All queries should respect the APPS schema and adhere to standard EBS security and read-only access conventions.