Check a Delivery Schedule for Deviations

This document explains how you perform a deviation check of a delivery schedule (DS). You do this when the delivery schedule has been activated.

By performing a deviation check you will make sure that there are no unacceptable deviations within the delivery schedule before the creation of the net schedule, which is the next step in the processing of the delivery schedule.

A deviation check is based on a deviation model for which you choose the delivery schedule fields you want to check.

Outcome

If the deviation check results in deviations, a deviation report is created connected to the DS item line.

If required, the DS item line is stopped for further automatic processing according to the settings in 'Delivery Schedule Deviation Model. Open' (RSS020) or in 'Deviation Model. Connect Period Types' (RSS021).

The DS item status of the checked item is 30 = Deviation model run, if all defined check fields are OK. If any field is found not to be OK and stopped processing is requested, the DS item status is set to 25 = Deviation error.

If the deviation check ended unsuccessfully, an application message is sent to inform the responsible user that the DS item line deviation check was unsuccessful.

You use the deviation check result to take suitable actions in order to fulfill the DS processing.

If DS processing has been stopped because of a deviation, use option 19 = Deviation text in 'Delivery Schedule. Connect Items' (RSS101) to view the deviation report.

If the deviation model is set to create an application message, you can also view the deviation report in 'Application Message. Open' (CRS420).

The text files (OSYTXH) and (OSYTXL) are updated with text that builds the deviation report.

The DS item status in the DS item line file (ORSITM) is set to 25 = Deviation error or 30 = Deviation model run, depending on the outcome of the deviation check.

The DS header file (ORSHED) is updated with the highest and lowest DS item status based on the outcome of the deviation check.

If defined in the deviation model, the application message file (CMAILB) is updated with application messages that indicate that a deviation error has occurred.

Before you start

You must Activate a Delivery Schedule.
Starting conditions regarding deviation check described in Delivery Schedule Deviation Check must be met.

Follow these steps

Choose one of these alternatives:

Check a single DS item line for deviations

Start 'Delivery Schedule. Connect Items' (RSS101).

You start (RSS101) by selecting a DS in 'Delivery Schedule. Open' (RSS100/B) and choosing option 11 = Items.
Select option 23 = Deviation model for the DS item line that you are going to check.
Choose the deviation model you want to use for the deviation check on the (RSS101/N) panel. Confirm your choice by pressing Next. For more information about the deviation check activities, see Delivery Schedule Deviation Check.

Note that you are free to use any of the existing deviation models.

Check the entire DS for deviations

Start 'Delivery Schedule. Open' (RSS100).
Select option 23 = Deviation model for the DS that you are going to check.
Choose the deviation model you want to use for the deviation check on the (RSS100/N) panel. Confirm your choice by pressing Next. For more information about the deviation check activities, see Delivery Schedule Deviation Check.

Note that you are free to use any of the existing deviation models.

When you check the entire DS for deviations, all item lines within the selected DS will be checked. The processing, however, is the same as if the check was performed per DS item line.

Check the entire DS for deviations automatically

If you have chosen automatic deviation check of the DS, see Delivery Schedule Deviation Check for more information about the activities performed within the deviation check.

You choose automatic deviation check of the DS in the '055 Next Manual Function' field in 'Delivery Schedule Type. Open' (RSS010).