Replenishment
Scenario I
Planning Forecast with Discrete PO, Version 1.0
Business Overview
The buyer generates a Planning / Delivery Schedule (net
rolling forecast) for information only and capacity or lead time
planning purposes, to convey anticipated demand or run rates; no
authorization to build or ship implied except per trading partner
agreement. To authorize build and ship, buyer calculates requirements
and places purchase orders, based upon agreed standard product and
pricing information from Price / Sales Catalog or upon Quote Request
/ Responses.
Click here to view a larger image.
Process Activity Diagram
Click here to view a larger image.
Narrative
| Step |
Description |
| 1. |
The buyer run Material Requirements
Planning (MRP) process. Buyer nets MRP data to generate a planning
forecast and determine whether replenishment is required during
the current planning cycle. |
| 2. |
If buyer determines that replenishment
is required during the current planning cycle, buyer sends Purchase
Order per Order Model 1. |
| 3. |
Buyer generates planning forecast
to send to supplier per Forecast/Planning Model 1.
Planning Forecast is typically regenerated weekly. Any changes/exceptions
from a previous run are factored into the new generation of
the planning forecast. The seller responds to the forecast
if needed. |
| 4. |
Prepare for the next MRP run. If
there are changes arising out of a supplier's response to a
forecast, they are dealt with during this activity, then the
next generation of the forecast starts again with 'Process MRP.' |
Implementation Options
- Order Models
- Forecast/Planning Models
Data Requirements for Replenishment Scenarios
- Data Requirements for Order Components
- Data Requirements for Release Components
- Data Requirements for Forecast (Schedule) Components
Business Documents Used in Replenishment Processes
- Business Documents for Order Components
- Business Documents for Release Components
- Discrete Releases
- Releases Embedded in Forecasts
- Business Documents for Forecast (Schedule) Components
|
contact
us 
