Creating a Required Ship Schedule

At any point during schedule processing, you can use Required Ship Schedule Maintenance (7.5.3) to edit the active or any other required ship schedule release. To call up the active schedule release, select the correct order and click Next. In the Release ID field, click Next again to open the active release.

You can create the RSS based on both the manufacturing and customer calendars, or to better accommodate your customer-shipping requirements, you can create the RSS based on:

To run the schedule update, use either Required Ship Schedule Update (7.5.5) or Selective Req Ship Sched Update (7.5.6). The system records the source of the requirement—either a shipping or planning schedule. This information displays in the output of the update functions.

The update creates a required ship schedule from either or both the planning and ship schedules. Which schedule is used depends on the Netting Logic setting in the order header.

If the order is using netting logic 3, the value of Use Ship/Plan PCR in Customer Schedules Control affects the schedule calculation.

If you selected netting logic 5, the system looks at the last week on the schedule where the planning and shipping schedule overlap. If your planning schedule quantity for the last overlap week exceeds the shipping schedule quantity, the system determines the days over which to spread the excess quantity by examining both the shop and customer calendars. The system uses the calendar with the shortest days to determine open days. When you run the update, the system indicates from which schedule the requirement originates as follows:

When the system reconciles shipping and planning requirements as it creates the RSS, it also differentiates the excess planning requirements from shipping requirements on the RSS.

The system keeps track of the shipping and planning requirements by assigning and storing different internal values for the two requirement types. The following programs can set this internal value when the system creates schedule records:

The update first selects the most recent release for each schedule type. It then uses the order data you specify (Week Offset, Cumulative, Transport Days, Req Sched Days, Weeks and Months, Standard Pack, Netting Logic, and SDP Codes), your calendar, and your customer’s calendar to adjust, if necessary, any dates or quantities. Adjustments are required when a customer does not schedule their requirements with reference to your open days, ship schedule, or shipment multiples. All date adjustments are back-scheduled.

If you are using noncumulative accounting procedures, the system manages requirement detail based on the settings you define in the Non-Cumulative Quantity Accounting Data frame of Customer Scheduled Order Maintenance.

If requirement detail exists, the system verifies that authorization numbers are unique, based on the AUTHNBR Unique Days setting for the scheduled order. Then requirement detail is copied to the RSS and a schedule detail record is created for each requirement detail record. In addition, open requirements from the previous active RSS can be carried to the new RSS if Merge RSS is Yes.

Planning data is excluded from the merge based on the setting of Exclude Planning Data. In some environment, authorization numbers are only supplied with scheduled requirements, not planned ones.

When you import a schedule using EDI eCommerce, the system uses information from the customer’s EDI file to determine whether the incoming schedule should be merged with an existing one or replace it.

While updating the RSS also performs this function when Merge RSS is Yes in Customer Scheduled Order Maintenance (7.3.13), it is sometimes impractical to merge the schedules manually if changes are being imported several times a day.

The value of the schedule_merge variable in the implementation definition associated with the imported document controls whether the schedule is merged with the previous one.

• When the variable is No, the system replaces the current schedule with the corresponding new schedule from the EDI file.

Example: A schedule arrives at 10:00 a.m. with October 2 forecast for a quantity of 10. At 11:00 a.m., another schedule arrives with a new release ID for an October 3 forecast for a quantity of 2. The schedule_merge variable file is Yes. The system makes the second schedule the active schedule, then copies the requirements from the first schedule into it. The resulting schedule includes the requirements for both October 2 and October 3. If the second schedule had the schedule_merge variable set to No, the second schedule would replace the first—leaving only one requirement for a quantity of 2 on October 3.

Another variable, detail_purpose, can be used to provide more control over how imported forecasts are used when schedule_merge is Yes. Effects of Detail_Purpose Variable shows the effects of each value of the detail_purpose variable.


Value of detail_purpose	Effect
A	For forecasts matching type, order number, line, release, date, time, firm/plan setting, and reference, the incoming amount is added to the current value.
R	The matching forecast replaces the current value.
D	The current value is set to 0 (zero).
Other value or blank	The matching forecast replaces the current value.

When Report Detail/Summary is set to Detail in Required Ship Schedule Update, the entire calculation prints an audit trail. The update function can be run in preview mode first by setting Update to No.

When Update is Yes, a required ship schedule is created and the release ID incremented. You can rerun a schedule update by specifying the release ID of the order.