Results for “mps_date_required”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
WIP_REQUIREMENT_OPS_INQ_V is an APPS-owned view within the Oracle E-Business Suite Work in Process (WIP) module. It is defined as an inquiry view that supplies additional descriptive and denormalized data for the base transaction table WIP_REQUIREMENT_OPERATIONS, which stores the component requirements and supply/issue records associated with discrete jobs and repetitive schedules. Because the base table holds only surrogate identifiers and coded values, the view joins those identifiers to master and lookup tables to expose human-readable descriptions and derived quantities, making it suitable for reporting, inquiry forms, and integration extracts.
The view is significant for users searching on wip_job_status, since it exposes a decoded WIP_JOB_STATUS column through a join to the MFG_LOOKUPS view. This allows the job status for repetitive schedule rows to be reported directly rather than resolved from the STATUS_TYPE code. The view is valid in both Oracle EBS 12.1.1 and 12.2.2 and is treated as a read-only inquiry object.
Underlying Base Objects
The documented metadata lists nine referenced base objects. WIP_REQUIREMENT_OPERATIONS (WRO) is the driving table and supplies the requirement rows, quantity columns, and operation sequence. WIP_ENTITIES (WE) supplies the entity type and primary item, distinguishing discrete jobs from repetitive schedules. WIP_DISCRETE_JOBS (WDJ) and WIP_REPETITIVE_SCHEDULES (WRS) provide schedule-level attributes such as start quantities, production rates, processing days, status type, and scheduled dates. WIP_OPERATIONS (WOP) is used to determine whether routing exists and to obtain operation start and completion dates. WIP_LINES (WL), BOM_DEPARTMENTS (BD), and MTL_SYSTEM_ITEMS_KFV (MSIK) provide the line code, department code, and item concatenated segments, description, and primary unit of measure respectively. MFG_LOOKUPS appears twice conceptually via aliases (ML1 and ML2) to decode the supply type and the WIP job status.
Key Columns
- WIP_JOB_STATUS — the decoded meaning of WRS.STATUS_TYPE from MFG_LOOKUPS, the column most commonly queried for job state reporting.
- CONCATENATED_SEGMENTS / ITEM_DESCRIPTION / ITEM_PRIMARY_UOM_CODE — item identification and unit of measure from MTL_SYSTEM_ITEMS_KFV.
- SCHEDULED_QUANTITY — derived from the repetitive daily production rate multiplied by processing work days, or from the discrete job start quantity.
- REQUIRED_QUANTITY, QUANTITY_ISSUED, QUANTITY_OPEN, QUANTITY_PER_ASSEMBLY — component demand and issue quantities, with QUANTITY_OPEN computed through nested DECODE logic.
- WIP_SUPPLY_MEANING — decoded from ML1 for the requirement supply type.
- SCHEDULED_START_DATE / SCHEDULED_COMPLETION_DATE — first unit start and last unit completion dates.
- ROUTING_EXISTS_FLAG — 1 when a matching operation sequence exists, otherwise 0.
- OPERATION_SEQ_NUM, DEPARTMENT_CODE, LINE_CODE — routing, department, and line context.
Common Use Cases and Queries
Typical scenarios include component shortage and open-quantity reporting, job status dashboards keyed on WIP_JOB_STATUS, and extracts feeding shop-floor or planning systems.
SELECT wip_entity_id,
concatenated_segments,
wip_job_status,
required_quantity,
quantity_issued,
quantity_open
FROM apps.wip_requirement_ops_inq_v
WHERE organization_id = :org_id
AND wip_job_status = 'Released';
The view is also used to reconcile requirements against routing existence, for example filtering on ROUTING_EXISTS_FLAG = 0 to locate requirements with no associated operation, or grouping by DEPARTMENT_CODE to report open component demand by department. Because it joins multiple WIP and inventory objects, queries should always be constrained by ORGANIZATION_ID and, where possible, WIP_ENTITY_ID to limit the result set.
-
Additional data for WIP_REQUIREMENT_OPERATIONS
APPS.WIP_REQUIREMENT_OPS_INQ_V·↳ BOM_DEPARTMENTS·↳ MFG_LOOKUPS·↳ MTL_SYSTEM_ITEMS_KFV·Explore WIP module →
-
This view provides all materials for a work order
APPS.WIP_EAM_REQUIREMENTS_ALL_V·↳ BOM_DEPARTMENTS·↳ EAM_DIRECT_ITEM_RECS_V·↳ EAM_MATERIAL_ALLOCQTY_PKG·Explore WIP module →
-
View: EAM_CFR_MATERIALS_V 12.2.2
This view displays information on materials for work orders.
APPS.EAM_CFR_MATERIALS_V·↳ BOM_DEPARTMENTS·↳ EAM_MATERIAL_ALLOCQTY_PKG·↳ MFG_LOOKUPS·Explore EAM module →
-
This table stores the material requirements of forecasted work orders for eaM maintenance budgeting and forecasting.
-
Material Import Table
-
Material Import Table
-
View on top of wip_requirement_operations. It has the extra columns needed for the support of one-off items.
APPS.EAM_REQUIREMENT_OPERATIONS_V·↳ EAM_MATERIAL_ALLOCQTY_PKG·↳ MTL_SYSTEM_ITEMS·↳ WIP_REQUIREMENT_OPERATIONS·Explore EAM module →
-
Foreign-key data for WIP_REQUIREMENT_OPERATIONS
APPS.WIP_REQUIREMENT_OPERATIONS_V·↳ BOM_DEPARTMENTS·↳ MFG_LOOKUPS·↳ MTL_SYSTEM_ITEMS_VL·Explore WIP module →
-
Requests to add/delete/ modify material/resource requirements for jobs and schedules
-
This table stores the material requirements of forecasted work orders for eaM maintenance budgeting and forecasting.
-
Components required by jobs and schedules
-
Requests to add/delete/ modify material/resource requirements for jobs and schedules
-
Requests to add/delete/ modify material/resource requirements for jobs and schedules
-
This view provides all materials for a work order
APPS.WIP_EAM_REQUIREMENTS_ALL_V·↳ BOM_DEPARTMENTS·↳ EAM_DIRECT_ITEM_RECS_V·↳ EAM_MATERIAL_ALLOCQTY_PKG·Explore WIP module →
-
View: PJM_PROJECT_WIP_COMP_V 12.2.2
WIP job component information for the Web Inquiry.
APPS.PJM_PROJECT_WIP_COMP_V·↳ INV_PROJECT·↳ MTL_ITEM_LOCATIONS_KFV·↳ MTL_PARAMETERS·Explore PJM module →
-
View: PJM_PROJECT_WIP_COMP_V 12.1.1
WIP job component information for the Web Inquiry.
APPS.PJM_PROJECT_WIP_COMP_V·↳ INV_PROJECT·↳ MTL_ITEM_LOCATIONS_KFV·↳ MTL_PARAMETERS·Explore PJM module →
-
The staging table used by the collection program to validate and process data for table MSC_DEMANDS.
-
The staging table used by the collection program to validate and process data for table MSC_DEMANDS.
-
Foreign-key data for WIP_REQUIREMENT_OPERATIONS
APPS.WIP_REQUIREMENT_OPERATIONS_V·↳ BOM_DEPARTMENTS·↳ MFG_LOOKUPS·↳ MTL_SYSTEM_ITEMS_VL·Explore WIP module →
-
Additional data for WIP_REQUIREMENT_OPERATIONS
APPS.WIP_REQUIREMENT_OPS_INQ_V·↳ BOM_DEPARTMENTS·↳ MFG_LOOKUPS·↳ MTL_SYSTEM_ITEMS_KFV·Explore WIP module →
-
Components required by jobs and schedules
-
Requests to add/delete/ modify material/resource requirements for jobs and schedules
-
VIEW: EAM.EAM_FORECAST_WRO# 12.2.2
-
VIEW: MSC.MSC_ST_DEMANDS# 12.2.2
-
VIEW: EAM.EAM_FORECAST_WRO# 12.2.2
-
Not implemented in this database·Explore MRP module →
-
Not implemented in this database·Explore MRP module →
-
Not implemented in this database·Explore MRP module →
-
VIEW: MSC.MSC_ST_DEMANDS# 12.2.2