Processing Customer Schedules
Once scheduled orders are set up in your system, you can receive printed or electronic schedule releases from your customers. The most recently received release normally supersedes all previous releases. An exception is raw and fabrication authorizations. The longest authorizations, calculated by end date, are the valid ones.
How a schedule is loaded also depends on the EDI purpose code specified in the header of the imported file. Based on the purpose code, schedules can be added, deleted, or simply loaded as a test without making any updates.
Two types of schedules are received: planning and shipping. The two schedule types may or may not match in quantity or due dates for any date or period. The ship schedule is usually more accurate, but this depends on your customer.
The selection of which schedule takes precedence in the short term is managed through the Netting Logic setting on the order header. Because shipping schedules typically dictate shorter ship days than the planning schedule, set the Netting Logic field to specify how the system holds or nets the planning quantities against the shipping quantities.
There are four basic steps to processing a schedule:
1 Receive the schedule, usually using EDI eCommerce.
2 Enter the release into the system or verify the schedule received through EDI eCommerce.
3 Run the schedule update to create the required ship schedule.
4 Run MRP to explode demand and schedule component orders.