Results for “expected_ship_date”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

MRP_BIS_LATE_ORDERS_V is an Oracle E-Business Suite seeded view owned by the APPS schema within the MRP (Master Scheduling/MRP) product family. It exposes schedule-level detail for demand lines that the planning engine has flagged as late, expressed through the BIS (Business Intelligence System) reporting layer. The view consolidates gross requirements, schedule dates, pegging information, and order-line attributes so that planners and reporting tools can identify sales orders and forecast demand whose expected ship date has slipped beyond the scheduled ship date.

The view is defined as a UNION ALL of two branches. The first branch targets discrete sales order demand (ORIGINATION_TYPE = 6) and joins OE_ORDER_LINES_ALL, MTL_SYSTEM_ITEMS_KFV, and the customer/address hierarchy. The second branch covers forecast or non-sales-order requirements, using USING_REQUIREMENTS_QUANTITY and forecast designator columns. Both branches derive an expected ship date through the MRP_GET_BIS_VALUES.EXPECTED_SHIP_DATE function, added to the schedule ship date or pegging demand date.

Underlying Base Objects

The documented base objects are a mix of synonyms and packages. Transactional demand comes from OE_ORDER_LINES_ALL, joined to customer data through the HZ foundation tables (HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_LOCATIONS, HZ_PARTIES, HZ_PARTY_SITES). Item and organization context is provided by MTL_SYSTEM_ITEMS_KFV.

Planning data is sourced from MRP_GROSS_REQUIREMENTS, MRP_SCHEDULE_DATES, MRP_FULL_PEGGING, and MRP_EXCEPTION_DETAILS. Exception filtering is applied on MRP_EXCEPTION_DETAILS.EXCEPTION_TYPE IN (13, 15), restricting output to late-order exception categories. Three packages supply computed values: MRP_GET_BIS_VALUES for expected ship date, MRP_GET_ORDER to resolve the sales order from the disposition, and INV_SALESORDER to map the order header. Joins across GREQ, PEG, MED, and DATES are correlated on disposition, organization, item, and compile designator.

Key Columns

• COMPILE_DESIGNATOR — Identifies the plan or MPS/MRP compilation the requirement belongs to.
• ORGANIZATION_ID — Inventory organization for the demand.
• CONCATENATED_SEGMENTS — Flexible-formatted item identifier from MTL_SYSTEM_ITEMS_KFV.
• ORDERED_QUANTITY / ORDER_QUANTITY_UOM — Demand quantity and its unit of measure.
• SCHEDULE_SHIP_DATE — The scheduled ship date of the order line (branch one) or the pegging demand date (branch two).
• EXPECTED_SHIP_DATE — Computed as SCHEDULE_SHIP_DATE plus MRP_GET_BIS_VALUES.EXPECTED_SHIP_DATE(...), giving the date the requirement is expected to ship.
• SALES_ORDER — Resolved through INV_SALESORDER.GET_SALESORDER_FOR_OEHEADER and MRP_GET_ORDER.SALES_ORDER.
• LINE_ID / LINE_NUMBER — Order line identifiers for the sales order branch.
• SOLD_TO_ORG_ID / CUSTOMER_NAME — Sold-to party identifier and customer name.
• SHIP_TO_ORG_ID / ADDRESS1 — Ship-to site and address detail.

Common Use Cases and Queries

Planners use this view to produce late-order exception reports, to support BIS dashboards, and to reconcile expected versus scheduled ship dates for customer commitments. The expected_ship_date column is the primary output for scheduling analysis.

A representative query lists late sales order lines for a given plan and organization:

SELECT compile_designator,
       organization_id,
       concatenated_segments,
       sales_order,
       line_number,
       customer_name,
       schedule_ship_date,
       expected_ship_date,
       ordered_quantity,
       order_quantity_uom
FROM   apps.mrp_bis_late_orders_v
WHERE  compile_designator = :plan
AND    organization_id    = :org
ORDER BY expected_ship_date;

Because the expected ship date is derived from a function, filtering or sorting on it forces evaluation at runtime; restricting by plan, organization, or customer first improves performance. Reports typically aggregate by customer_name or concatenated_segments to quantify late demand exposure, while drill-down queries join back to OE_ORDER_LINES_ALL or MRP_GROSS_REQUIREMENTS through line_id and disposition references to obtain supporting detail. The view is read-only and intended for reporting and integration rather than transactional updates.