EBS Reference
Planning
Supply chainMRP/ASCP plan output — planned orders, recommendations, and the supply/demand entities behind them
8 tables
Verified September 2026
In the business-problem map Demand Planning & Forecasting
Tables
Transaction · 4
- MRP_FORECAST_DATESThe forecast fact — one row per forecast entry per item, org, forecast name, and date, carrying both the entered quantity and the post-consumption remainderSchema: MRPtransaction
- MRP_SCHEDULE_DATESMDS/MPS schedule entries — one row per entry per item, org, schedule name, and date, spanning discrete quantities and repetitive rates, demand rows and supply rowsSchema: MRPtransaction
- MSC_DEMANDSEvery demand row a plan considered — sales orders, forecasts, and the dependent demand exploded from supplies, each with its due date, quantity, and originSchema: MSCtransaction
- MSC_SUPPLIESEvery supply row in a plan — existing purchase orders, jobs, on-hand, and in-transit alongside the planner's recommended planned orders; the supply side of ASCP plan outputSchema: MSCtransaction
Control · 3
- MRP_FORECAST_DESIGNATORSThe forecast name and forecast set master per organization — consumption behavior (consume flag, forward/backward time fences, outlier cap) lives at this levelSchema: MRPcontrol
- MRP_SCHEDULE_DESIGNATORSThe MDS/MPS schedule name master per organization — schedule type, relief behavior, and whether the schedule supplies ATPSchema: MRPcontrol
- MSC_PLANSThe ASCP plan registry — one row per plan with its user-visible name, owning org, type, planning horizon, and run timestamps; every plan-output query starts by picking a row hereSchema: MSCcontrol