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

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.