Show TOC

 Dependencies Locate this document in the navigation structure

Before routings are archived and deleted, the system checks for the following usages:

  1. Usage in a production version

  2. The routing is stored in the material master record as a part of a production version.

  3. Usage in an inspection lot

  4. This criterion is only relevant if the Quality Management System (QM) is active in your system. You can only archive a routing if it is no longer used in an inspection lot.

  5. For reference operation sets/reference rate routings: References in routings or rate routings

  6. You can only archive reference operation sets or reference rate routings if references to other task lists no longer exist.

  7. Usage in a run schedule header

  8. A run schedule header always requires information from its routing, for example for confirmation. You can only archive this type of routing if the run schedule header is complete and archived.

  9. Other usages which you can define using the SAP Enhancement CPRE0001

Therefore, the archiving functionality for routings is dependent on the following objects:

  • material master records with production versions

  • run schedule headers

  • inspection lots (archiving object QM_CONTROL)

What Happens If a Routing Is Still Used

If during the usage check the system finds a routing which is still being used or which meets the checking criteria you specified (with SAP Enhancement CPRE0001), the system responds in one of the following ways:

  • The archiving run is terminated. You receive an information message with the routing which is still being used. Do not set the Log indicator in variant maintenance for this result.

  • The archiving run is completed and then you receive a log with a list of all routings which could not be archived or deleted because of the usage check.

    Set the Log indicator in variant maintenance for this result.