Search Results mps_date_required

Overview

APPS.PJM_PROJECT_WIP_COMP_V is a Project Manufacturing (PJM) inquiry view that exposes Work in Process (WIP) job component information for the Oracle E-Business Suite Web Inquiry. It is a reporting and integration object rather than a transactional table: it consolidates component-level detail for discrete and repetitive WIP jobs so that project manufacturing users can review material requirements, supply, and issue status through the standard self-service inquiry screens.

Because the view is defined in the APPS schema and joins the WIP requirement operations view to item location data, it presents a denormalized, presentation-ready result set. It abstracts the complexity of locating components within WIP entities and returns human-readable attributes, including concatenated item and locator flexfield segments, decoded Yes/No flags, and derived serial number information. Within Oracle EBS 12.1.1 and 12.2.2, the object remains valid and retains the same fundamental purpose, providing a stable interface for the Project Manufacturing Web Inquiry.

Underlying Base Objects

The documented base objects referenced by the view are:

• WIP_REQUIREMENT_OPERATIONS_V (VIEW) — the primary driver, supplying WIP entity, operation, component, quantity, and date-required information aliased as WRO.
• MTL_ITEM_LOCATIONS_KFV (VIEW) — the key flexfield locator view, joined with outer joins to resolve supply locator descriptions via MIL.CONCATENATED_SEGMENTS.
• PJM_INQUIRY (PACKAGE) — supplies scalar functions used in the SELECT list, including LOCATOR_CONTROL, SYS_YES_NO, and COMPONENT_SERIAL.
• INV_PROJECT (PACKAGE) — a supporting package in the Inventory application associated with the view's dependencies.
• MTL_PARAMETERS (SYNONYM) — an organizational parameter reference underlying the locator and inventory logic.

The join condition MIL.INVENTORY_LOCATION_ID (+) = WRO.SUPPLY_LOCATOR_ID AND MIL.ORGANIZATION_ID (+) = WRO.ORGANIZATION_ID makes the locator lookup optional, ensuring that components with no supply locator still appear in the result set.

Key Columns

The view exposes identifiers and descriptive attributes necessary for component inquiry. ROW_ID provides a unique row identifier, while WIP_ENTITY_ID, OPERATION_SEQ_NUM, REPETITIVE_SCHEDULE_ID, and LINE_ID identify the WIP job and operation context. INVENTORY_ITEM_ID, CONCATENATED_SEGMENTS, ITEM_DESCRIPTION, and ITEM_PRIMARY_UOM_CODE describe the component item.

ITEM_PRIMARY_UOM_CODE — the column the user searched for — returns the primary unit of measure for the component item, which is essential for interpreting REQUIRED_QUANTITY, QUANTITY_ISSUED, QUANTITY_OPEN, QUANTITY_PER_ASSEMBLY, and MPS_REQUIRED_QUANTITY. Quantity columns are converted with TO_NUMBER, while flag columns such as INVENTORY_ASSET_FLAG, RESTRICT_SUBINVENTORIES_CODE, RESTRICT_LOCATORS_CODE, MRP_NET_FLAG, and ROUTING_EXISTS_FLAG are decoded through PJM_INQUIRY.SYS_YES_NO. Supply details are provided by SUPPLY_SUBINVENTORY, SUPPLY_LOCATOR_ID, and MIL.CONCATENATED_SEGMENTS. Scheduling attributes include DATE_REQUIRED, MPS_DATE_REQUIRED, FIRST_UNIT_START_DATE, FIRST_UNIT_COMPLETION_DATE, and LAST_UNIT_COMPLETION_DATE. Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, REQUEST_ID, PROGRAM_ID) are also present.

Common Use Cases and Queries

Typical scenarios include reviewing open component requirements for a project WIP job, validating supply subinventory and locator assignments, and extracting component data for project costing or material shortage reporting. A representative query follows:

• Query all components for a specific WIP entity, showing item, UOM, and quantities:

SELECT WIP_ENTITY_ID, OPERATION_SEQ_NUM, CONCATENATED_SEGMENTS, ITEM_DESCRIPTION, ITEM_PRIMARY_UOM_CODE, REQUIRED_QUANTITY, QUANTITY_ISSUED, QUANTITY_OPEN FROM APPS.PJM_PROJECT_WIP_COMP_V WHERE WIP_ENTITY_ID = :p_wip_entity_id ORDER BY OPERATION_SEQ_NUM;

• Identify components with open quantities and their supply locations:

SELECT WIP_ENTITY_ID, CONCATENATED_SEGMENTS, ITEM_PRIMARY_UOM_CODE, QUANTITY_OPEN, SUPPLY_SUBINVENTORY, SUPPLY_LOCATOR_ID FROM APPS.PJM_PROJECT_WIP_COMP_V WHERE QUANTITY_OPEN > 0 AND ORGANIZATION_ID = :p_org_id;

These queries illustrate how ITEM_PRIMARY_UOM_CODE contextualizes quantity values and supports downstream reporting and integration requirements.