Show TOC

  Deviation Analysis for Work Orders

Use

Work order collaboration uses deviation analysis from consensus finding to determine deviations between the following data:

  • Confirmation PIOs of the supplier and request PIOs of the customer

    If the confirmation PIOs of the supplier do not deviate from the request PIOs of the customer within the customer-defined quantity tolerances and time tolerances, the system accepts the confirmation PIOs automatically.

  • Projected deliveries and planned deliveries

    If the projected deliveries deviate from the planned deliveries more than the customer-defined quantity tolerances and time tolerances allow, the system creates alerts, required actions, and statuses for deviating projected deliveries for the planned deliveries.

  • Actual PIOs and planned PIOs

    If the actual PIOs deviate from the planned PIOs more than the customer-defined quantity tolerances and time tolerances allow, the system creates alerts, required actions, and statuses for deviating actual data for the planned PIOs.

Features

Definition of the Tolerances

You can configure the quantity tolerances or time tolerances depending on the following characteristics:

  • Customer

  • Supplier

  • Product

  • Phase type

  • Phase ID

  • Phase input, phase output

  • Phase structure

If you do not make any settings, the system does not allow any deviations (quantity tolerance = time tolerance = 0).

Assignment Algorithm

In deviation analysis, the system views the phase inputs and phase outputs separately. (In particular, you can configure different quantity tolerances and date/time tolerances for phase inputs and phase outputs.) This also applies to deliveries: Here the system likewise views the transportation phase inputs and transportation outputs separately. The assignment algorithm for phase inputs and phase outputs is the same, so the superordinate term "PIO" is used in the following description.

In deviation analysis, the system assigns PIOs to the reference PIOs and compares the assigned PIOs to the reference PIOs. For automatic approval, the request PIOs of the customer are the reference PIOs. To determine deviating actual data or deviating projected deliveries, the plan PIOs are the reference PIOs.

The system assigns the PIOs to the reference PIOs depending on certain criteria (time tolerances) and in a particular sequence. In a first assignment step, the system assigns PIOs that are as punctual as possible and do not violate the time tolerance of the reference PIO. In a second step, the system also considers PIOs that are outside of the time tolerances.

For more information about the assignment algorithm, explained with an example of deviation analysis for projected deliveries, see Deviation Analysis for Projected Deliveries (DA_QTY_TIME_02) .

Determination of Deviations Between Planned Deliveries and Projected Deliveries

The system compares the projected transportation PIOs with the planned transportation PIOs. To do this, the system assigns projected transportation PIOs to the planned transportation PIOs. It then compares the total quantity and the dates/times of the projected transportation PIOs assigned to a planned transportation PIO, with the quantity and date/time of the planned transportation PIO. In the case of deviations outside of the quantity tolerances and date/time tolerances, the system creates the appropriate alerts and statusees for the planned transportation PIOs. For more information, see Alerts, Actions, and Statuses for Deviating Projected Delivereies and Deviation Analysis for Projected Deliveries (DA_QTY_TIME_02) .

Determination of Deviations Between Plan PIOs and Actual PIOs

The system compares the actual PIOs that the supplier reports for the input and output components of a phase, with the planned phase inputs and phase outputs. To do this, the system assigns actual PIOs to the planned PIOs. It then compares the total quantity and the dates/times of the actual PIOs assigned to a planned PIO, with the quantity and date/time of the planned PIO. In the case of deviations outside of the quantity tolerances and date/time tolerances, the system creates the appropriate alerts and statuses for the plan PIOs. For more information, see Alerts, Actions, and Statuses for Deviating Actual Data .

Determination of Deviations Between Request PIOs and Confirmation PIOs

The system compares the confirmation PIOs of the supplier with the request PIOs of the customer. To do this, the system assigns confirmation PIOs to the request PIOs. It then compares the total quantity and the dates/times of the confirmation PIOs assigned to a request PIO, with the quantity and date/time of the request PIO. The system accepts the confirmation PIOs that are assigned to a request PIO, if these meet the following conditions:

  • The dates/times of all assigned confirmation PIOs match the date/time of the request PIO within the time tolerance.

  • The total quantity of the confirmation PIOs lies between the allowed minimum quantity (request quantity minus underdelivery tolerance) and the allowed maximum quantity (request quantity plus overdelivery tolerance) for the request PIO.

Activities

To configure tolerances, proceed as follows:

  1. Make the following settings in Customizing for Supply Network Collaboration under Basic Settings → Consensus Finding :

    • Under Consensus Profiles , define a quantity profile and a time profile for every quantity tolerance value and time tolerance value. The quantity profile DA_QTY_2 and the time profile DA_TIME_2 are available in the standard system.

    • Under Maintain Consensus Rules , create a consensus rule for each required combination of quantity and tolerance profile. The consensus rule DA_QTY_TIME_02 is available in the standard system. For the comparison algorithm, use the permissible class DA_QTY_TIME_02.

  2. To assign consensus rules to the relevant parameter combinations (see above), you must create condition records. To do this, on the SAP Easy Access screen, choose Supply Network Collaboration → Basic Settings → Consensus Finding → Condition Records → Maintain Condition Records.

    Use the following settings for work orders:

    • Application: CF

    • Maintenance group: CF

    • Condition type: 1000

    • Data to be compared

      Choose the value depending on the data that the system is to compare:

      • Compare confirmation data of the supplier to the request data: 1

      • Compare actual data to planned data: 2

      • Compare actual data to projected data: 3

    • Order document type REWO