Replace work-centers

Use this function to replace machine, labor, or subcontracted work centers assigned to operations in one or a range of routings at a single production site.

You can set a validity start date for replacement operations. The default is the current date. Replacement operations are given the same sequence number in the routings as the operations being replaced. Their index number is incremented and the validity start date set. The operation with the highest index number is the new operation.

Note - informationThis function marks operations as "not valid" by setting their validity end date to the validity start date for the replacement operation minus 1 day (n-1). It does not delete any operations.
Note - tipA routing displays operations that are valid on a specific date. A new operation is only displayed in a routing after it becomes valid (Application date (APPDAT) / Start date (VALSTRDAT) fields).
Note - warning
  • You cannot use this function to change operation details. Use the Routing operations function (FUNTDUPDR5) instead.
  • You cannot use this function to modify operations in version-managed routings.

Prerequisites

Note - informationRefer to the documentation on Implementation.

Screen management

Home

You use the home section to select the production site.

To replace work centers, select the Replacement by date checkbox and the effective application date. This is used as the validity start date for reindexed operations.

Then select the routings to include in the run. You can include subcontract work centers and operations assembled into routings from standard operations. Only routings that are not version managed are updated.

Tab Selection

You use this section to filter for routings at the production site.

Tab Parameters

Use this section to change work centers on the operations that are used in the routings included in the filtered results and operations to which a subcontract work center has been assigned.

Select the field to change then enter the new value.

Replacing work centers

Use the table to confirm the details of all or individual routings included in the filtered results to update. You can change selected details if you need to.

A log file displays the results of the run. Where appropriate it includes information that should be noted or acted upon. Any excluded version-managed routings are listed on the log file.

Error messages

In addition to the generic error messages, the following messages can appear during the entry

The end range is less than the start range

The end value in the range is before the start value.

Work center: XXX. Work center does not exist on this site

All work centers are linked to a specific site. The site defined for the selected work center needs to be identical to the selected Production site (MFGFCY).

XXX: is not a Subcontract work center
or
XXX: is not a Labor work center"

These messages are displayed if the work center defined is the wrong type. A labor work center needs to be defined as a Labor type and a subcontract work center needs to be defined as a Subcontracting type.

Entry of a mandatory product

This message is displayed if a modification has been requested for a subcontract work center and the subcontract product is missing.

Version-managed routings included in the selection criteria are not processed. Update them manually.

Amendments to the operations in a versioned routing are tightly controlled to minimize the impact on work orders. The selected operation is in one or more version-managed routings. The list of routings displayed will not include version-managed routings because these are excluded from the replacement process.

Modification of operation X/X/X

This is an information message. Operations are modified when the modifications are confirmed.

Creation of operation X/X/X

This is an information message. Replacement operations are created when the modifications are confirmed.

Log file

Operation X/X/X. A replacement operation already exists

For the defined operation, there's already a replacement operation in the routing. The initial and replacement operations have the same operation number, but they have been given different indices to distinguish them.

Tables used

Note - informationRefer to the documentation on Implementation.