Search Results firm_date




Overview
Explore in AI Chat

Overview

The view MRP_RHX_FIRM_PLANNED_ORDERS_V is an Oracle E-Business Suite Integration Toolkit object belonging to the MRP – Master Scheduling/MRP product. It is designed to expose firm planned orders generated by the MRP planning engine so that external systems and downstream integration processes can consume them in a stable, denormalized form. Firm planned orders are discrete planned supply recommendations that the planner has "firmed," meaning the planning engine will not automatically reschedule or modify them during subsequent regenerations. Within EBS 12.1.1 and 12.2.2, this view serves as a reporting and integration access point into the recommendation data stored in the MRP schema, joining planner recommendations against item master information and lookup values.

Because it is an Integration Toolkit view, it is intended primarily for programmatic consumption — interfaces, extracts, and custom reports — rather than as an interactive inquiry screen. The view returns only open firm planned orders, that is, those whose remaining firm quantity is still greater than zero after subtracting any already-implemented quantity.

Underlying Base Objects

The view text references the following base objects:

  • MRP_RECOMMENDATIONS (alias RECOM) — the primary source table holding planner recommendations, including order type, firm flags, dates, and quantities.
  • MRP_RHX_PLANNED_ITEMS_V (alias ITEM) — another Integration Toolkit view supplying the item number, inventory item identifier, and organization context.
  • MFG_LOOKUPS (alias LUP) — the standard lookup table used to translate the order type code into a meaningful value.

The join conditions apply several filters. RECOM.ORDER_TYPE = 5 restricts results to a specific recommendation category, while RECOM.FIRM_PLANNED_TYPE = 1 isolates the firm planned order type. The lookup join constrains LUP.LOOKUP_CODE = 5 and UPPER(LUP.LOOKUP_TYPE) = 'MRP_ORDER_TYPE', yielding the descriptive job-type meaning. The item join matches on both INVENTORY_ITEM_ID and ORGANIZATION_ID, and a final predicate RECOM.FIRM_QUANTITY - NVL(RECOM.IMPLEMENTED_QUANTITY, 0) > 0 eliminates fully implemented or zero-balance records.

Key Columns

  • TRANSACTION_ID — unique identifier of the recommendation record.
  • ITEM_NUMBER and INVENTORY_ITEM_ID — the item's user-facing name and internal identifier.
  • ORGANIZATION_ID — the inventory organization context for the order.
  • NEW_WIP_START_DATE — the proposed work-in-process start date for the planned order.
  • FIRM_DATE — the date on which the order was firmed, and the field most directly associated with the "firm_date" search term.
  • FIRM_QUANTITY — the firm quantity recommended; note this reflects the unfiltered value as selected, while the predicate ensures the remaining balance is positive.
  • ALTERNATE_BOM_DESIGNATOR, ALTERNATE_ROUTING_DESIGNATOR, COMPILE_DESIGNATOR — manufacturing designators associated with the planned order.
  • JOB_TYPE_MEANING — the decoded lookup meaning for the order type.

Common Use Cases and Queries

Typical usage includes extracting firm planned orders for external planning systems, building custom dashboards for planners, or reconciling MRP recommendations against executed work orders. A representative query:

  • SELECT TRANSACTION_ID, ITEM_NUMBER, ORGANIZATION_ID, FIRM_DATE, NEW_WIP_START_DATE, FIRM_QUANTITY, JOB_TYPE_MEANING FROM MRP_RHX_FIRM_PLANNED_ORDERS_V WHERE FIRM_DATE BETWEEN :start_date AND :end_date ORDER BY FIRM_DATE;
  • Filtering by ORGANIZATION_ID to isolate a plant, or by INVENTORY_ITEM_ID for a specific item.
  • Joining to MTL_SYSTEM_ITEMS_B using INVENTORY_ITEM_ID and ORGANIZATION_ID to enrich extracts with item attributes.

Because the view already restricts to firm, open recommendations, consumers need not reapply the firming or balance logic.