Show TOC

 Consistency Check Locate this document in the navigation structure

The system does not automatically check consistency between operations and sequences when you create or change a routing. Therefore, when you are creating a routing, you can create several operations with the same operation number if the exact order is not known and then delete the unnecessary operations or change the operation numbers at a later time.

Automatic Consistency Check

In Customizing for routing, you can specify, depending on the status of the routing, that a consistency check is automatically carried out before saving the routing. (see Activating the Automatic Consistency Check ) The system checks the following object relationships:

Scope of Consistency Check

Checked objects

Possible inconsistencies

Standard Sequence

The validity period of the standard sequence does not agree with the validity period of the header.

Operation and sub-operation numbers

The same number has been assigned more than once.

Branch and return operations

The branch operation is greater than the return operation.

The branch or return operation of a sequence was deleted.

The smallest operation number of an alternative sequence is smaller than the branch operation in the standard sequence. The largest operation number of an alternative sequence is larger than the return operation in the standard sequence.

Units of measure

The unit of measure for the routing does not agree with the unit of measure of the referenced operation set.

Lot size ranges

The lot size range of an alternative sequence exceeds the lot size range of the header.

The lot size range of the header or alternative sequence exceeds the lot size range of the referenced operation set.

In addition, the system checks the consistency of an operation’s inspection characteristics when you exit the characteristic overview. For additional information about this, refer to the SAP Library Quality Management .

Consistency Check During Task List Maintenance

During task list maintenance you can carry out a consistency check independently of the task list status When the system carries out the check it writes a check log where system messages are displayed. You can use these system messages to decide whether you should save despite the inconsistencies or whether any errors must be corrected online.

Note Note

When a consistency check is carried out in the background, the routing is always saved. If errors occur, the consistency log is also saved on the database.

End of the note.
Consistency Check for Material Assignments

In addition to checking the consistency of operations and sequences, you can also check the consistency of the material component assignments to your routing.

Checking Material Component Assignments

Consistency Check at Order Creation

Once a routing is checked and saved without inconsistencies, the system sets an internal indicator in the header so that no further check is carried out at order creation.

In the following cases, the system checks consistency again when an order is created:

  • If you have saved a routing despite inconsistencies.

  • If the valid from date of the change number (see also Working with History ) for a checked routing has changed.

  • If a configurable material is assigned to the routing.

For additional information about the consistency check at order creation, refer to the SAP Library Production Orders (PP-SFC) .