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.
- 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
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.
| Production site (MFGFCY) |
|
The production site. The production site defined on the user record is displayed by default but can be edited. |
| Replacement by date (REPLACEFLG) |
|
Indicates if resources in the selected routings are to be updated or reindexed (replaced).
|
| Application date (APPDAT) |
|
The current date is the default date. If the replacement operation is valid from a later date, enter the effective date. This field is only available for entry if the Replacement by date checkbox is selected. |
Tab Selection
You use this section to filter for routings at the production site.
Start - end range
| Code (ROUALTDEB / ROUALTFIN) |
|
Filter for results for routing codes at the selected production site. For a single routing code, select the same code in the from/start Code and to/end fields. Multiple routings can be defined for a single product. Each routing code can be assigned specific management features. These include restriction of the routing to a specific site and to specific areas of functionality, such as for use in a manufacturing environment, for costing, or for capacity planning. |
| Routing (ROUNUMDEB / ROUNUMFIN) |
|
Filter for results for routings at the selected production site. For a single routing, select the same code in the from/start Routing and to/end fields. The routing code describes the process involved in manufacturing (producing) or processing a product. It provides the sequence of operations and tools that are involved in producing or processing a particular product. |
| Operation (OPENUMDEB / OPENUMFIN) |
| Filter for results for operation sequence numbers. For a single operation sequence number, select the same number in the from/start Operation and to/end fields. |
| Work center (WSTDEB / WSTFIN) |
|
Filter for results for production resources used for an operation. This work center is the main or principal work center for the operation. The resource can be a machine, a labor, or a subcontract work center. Subcontracting type work centers are managed using the lead time defined in the subcontract product record. |
| Labor center (LABWSTDEB / LABWSTFIN) |
|
Filter for results for labor work centers. Labor work centers are considered secondary and always available, or available at the same time as the main work center. Their load is managed for information purposes only using the coefficients defined for the main work center. Note - informationIf the main work center is a Subcontracting type work center, there is no associated secondary work center.
|
| Subcontract type (SCOCODDEB / SCOCODFIN) |
|
Filter for results for operations carried out internally or sent to an external subcontract supplier.
|
| Subcontract work C (SCOWSTDEB / SCOWSTFIN) |
|
Filter for results for subcontract work centers. A subcontract work center can be used for the following:
A subcontract work center has the work center type set to Subcontracting. Routing operations are validated to ensure that the work center site of a subcontract work center matches the site for the routing code, if defined. |
| Subcon prod (SCOITMDEB / SCOITMFIN) |
| Filter for results for the service to be carried out by the subcontractor to execute the operations. The product needs to have a Service category. |
| Selection formula (FORMULE) |
|
Enter or build a calculation expression using the formula editor to further filter routing operations. Note - informationAn error message is displayed if you refer to tables that are not generally used by the configurator, or to unknown variables.
|
| Include the operations derived from std operations (EFFUPD) |
|
Indicates if operations assembled into routings from standard operations are included. Leave clear to exclude operations assembled into routings from standard operations or select the checkbox to include them. |
| Exclude unmodified operations (EFFUPD2) |
|
Indicates if operations that meet the entered selection criteria that will be changed or replaced by the values defined in the Parameters tab display. Leave the checkbox selected to only display operations that meet the entered selection criteria that will be changed or replaced or clear the checkbox to display all operations that meet the entered selection criteria. |
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.
Modification
| New work center (FWST) |
|
Identifies the production resource to use for the operations. This work center replaces the main or principal work center for the operations. The resource can be a machine, a labor, or a subcontract work center. Operation scheduling considers the availability of the work center. If you define a Subcontracting type work center, the Subcontract code (SCOCOD) is set to Normal and the operation is automatically subcontracted. The subcontract operations are managed using the lead time defined in the subcontract product record. Subcontract operation times are not used by the scheduling. To generate a temporary or ad hoc subcontract operation, enter an internal work center as the main work center and enter a temporary subcontracting code for the subcontract work center. Scheduling is carried out by priority on the main (workshop) work center when creating a work order. You can replace the work center with the subcontract work center if the operation is subsequently subcontracted. |
| New labor center (FLABWST) |
|
The labor work center to assign to the operations. The work center site needs to match the site for the routing code, if defined. Scheduling is not carried out for labor work centers. They’re considered secondary and always available, or available at the same time as the main work center. Their load is managed for information purposes only using the coefficients defined for the main work center. Note - informationIf the main work center is a Subcontracting type work center, there is no associated secondary work center.
|
| New sub-con w/center (FSCOWST) |
|
The replacement subcontract work center for the operations. A subcontract work center can be used for the following:
A subcontract work center has the work center type set to Subcontracting. Routing operations are validated to ensure that the work center site of a subcontract work center matches the site for the routing code, if defined. |
Subcontract
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.
| Production site (MFGFCY / FCYNAM) |
| The production site and production site name. |
Grid
| Routing (ITMREF) |
|
The routing code describes the process involved in manufacturing (producing) or processing a product. It provides the sequence of operations and tools that are involved in producing or processing a particular product. The routing code matches the product code. The product code can be a manufactured product, which is defined as a bill of material, or a generic reference to a parent routing, which is linked to several products. |
| Alternative (ROUALT) |
| Multiple routings can be defined for a single product. Each routing code can be assigned specific management features. These include restriction of the routing to a specific site and to specific areas of functionality, such as for use in a manufacturing environment, for costing, or for capacity planning. |
| No. (OPENUM) |
| The operation sequence number. |
| Index (RPLIND) |
| Indicates if the operation was edited. The value displayed concurs with the number of times the operation was edited. The operation with the highest index number is the new operation. |
| Start date (VALSTRDAT) |
|
The operation validity period start date. If the routing is version managed and you're editing an existing operation (the Index field is populated), the default start date is tomorrow. |
| End date (VALENDDAT) |
|
The operation validity period end date. If the routing is version managed and you're editing an existing operation, the previous operation (the Index field is blank or lower than the operation) defaults to the current date. |
| Std oper (STDOPENUM) |
|
The standard operation that was used to create the routing operation. Standard operations are simply template operations that provide default information to be assembled into routings for producing or processing a particular product. Note - information
If you confirm "recovery of the operation data":
Note - warningOperations based on a standard operation are not updated if the standard operation is changed.
|
| Work center (WST) |
|
Identifies the production resource to use for the operations. This work center replaces the main or principal work center for the operations. The resource can be a machine, a labor, or a subcontract work center. Operation scheduling considers the availability of the work center. If you define a Subcontracting type work center, the Subcontract code (SCOCOD) is set to Normal and the operation is automatically subcontracted. The subcontract operations are managed using the lead time defined in the subcontract product record. Subcontract operation times are not used by the scheduling. To generate a temporary or ad hoc subcontract operation, enter an internal work center as the main work center and enter a temporary subcontracting code for the subcontract work center. Scheduling is carried out by priority on the main (workshop) work center when creating a work order. You can replace the work center with the subcontract work center if the operation is subsequently subcontracted. |
| WSTTYP |
|
Identifies the type of operation that's performed on the work center. This might be a machine, a labor, or a subcontracted operation. Subcontracting type work centers are managed externally by subcontract suppliers. |
| Work center group (WCR) |
| Identifies the group of work centers that the work center belongs to. Work center groups are used to review workloads. |
| Operation description (ROODES) |
| The description defined for the routing operation. |
| Labor wk C (LABWST) |
|
The labor work center assigned to the operation. The work center site needs to match the site for the routing code, if defined. Scheduling is not carried out for labor work centers. They’re considered secondary and always available, or available at the same time as the main work center. Their load is managed for information purposes only using the coefficients defined for the main work center. Note - informationIf the main work center is a Subcontracting type work center, there is no associated secondary work center.
|
| Labor work center group (LABWCR) |
| The group of work centers that the work center belongs to. Work center groups are used to review workloads. |
| Setup time (SETTIM) |
|
Specifies a fixed amount of time needed to prepare a work center. It’s part of the work center load. It’s expressed in either the time unit specified in the routing header or in the standard operation, if a standard operation was applied for the operation. The time can be zero. |
| Time unit (TIMUOMCOD) |
|
Defines how time for the operations in the routing is expressed. The time unit can be hours or minutes. The time applies to the setup time, run time, and the rate of all operations in the routing. |
| Run time code (ROOTIMCOD) |
|
The operation time type applied to the production time entry.
|
| Management unit (TIMCOD) |
|
Depending on the resource being used, the number of decimals for the operation time can be insufficient to express the production time. The management unit makes it possible to express the operation time for 1, 100, 1,000, or a lot of units of parts to be produced. If the management unit is by lot, the lot size can be entered as the base quantity. |
| Base quantity (BASQTY) |
|
The base quantity depends on the management unit. In effect, if the time is expressed for 1 unit, for 100 units or for 1,000 units, the base quantity is forced, respectively to 1, 100 or 1,000 units. However, if the time is expressed for a lot, the base quantity can be entered. If the processed routing code is assigned to a site, it's initialized for the lot size of the product-routing for the site. The base quantity entry format depends on the operation unit. |
| Run time (OPETIM) |
|
The time needed to manufacture the product described in the routing. The operating time:
|
| Rate (CAD) |
|
The rate is a number of units produced by minute or by hour according to the time unit specified in the routing header (for an operation), or in the standard operation itself. The number of units is expressed according to the time unit. It can only be entered if the operation time type is Rate. |
| Number of resources (WSTNBR) |
| The number for this particular production resource that are needed for the operation. For example, if 3 people are needed to operate a specific labor work center, enter 3. |
| Number labor res. (LABNBR) |
| The number for this particular production resource that are needed for the operation. For example, if 3 people are needed to operate a specific labor work center, enter 3. |
| Efficiency (EFF) |
|
Efficiency is a way to measure compliance to the preset standards. It can be calculated over a given period by work center: Standard hours calculated for a given production divided by the actual hours worked. Efficiency makes it possible to correct the standard times of the routing (multiplying factor) according to the used resource. 2 efficiency rates are managed depending on the following:
If both factors are entered, they add up. The calculated operating time is corrected in the following way: work center efficiency * operation efficiency * time. The WSTEFFINH—Work center efficiency history parameter (GPA chapter, MIS group) is used to specify whether the efficiency defined at work center level should be used on the routing operation.
|
| Shrinkage in % (SHR) |
|
This percentage is used to balance the quantities on the production operations based on the released quantity. It’s possible to introduce a shrinkage percentage on the work center, which is used to weight the planned run times for an operation using the work center by a loss or gain on the quantity produced for the work center. |
| Lab set fact (SETLABCOE) |
| The coefficient applied to the planned setting time to obtain the setting time for the labor work center linked to the principal work center. This field is only available for entry if the labor work center is defined. |
| Lab R/T fac (OPELABCOE) |
|
The coefficient applied to the planned operation time to obtain the operation time for the labor work center linked to the principal work center. This field is only available for entry if the labor work center is defined. Operation times are subdivided as follows:
Proportional times are expressed for the production of an operation unit. They're not in the stock unit of the finished product using the routing. |
| Preparation time (PRPTIM) |
|
Preparation time is "waiting time" set at the start of an operation. Preparation time is not applied to the work center load. Note - informationPreparation time is always expressed in hours. It does not use the time unit defined in the routing header (Time unit field).
Although preparation time is waiting time, it can be used for the time it takes to prepare for an operation on a work center. This might be time for settling liquids or cleaning a machine. When preparation time is used for setting time at the start of an operation, the resource needs to be available. When scheduling preparation time, the calendar for the defined resource is applied. This means that if, for example, a machine or labor work center runs from 08:00 to 12:00 and from 13:00 to 17:00 with a 1 hour break from 12:00 to 13:00, preparation time will be interrupted by the 1 hour break. If the operation requires an "emergency release", a reduction coefficient can be assigned that makes it possible to completely remove any preparation time. |
| Waiting time (WAITIM) |
|
Waiting time is "delay time" that occurs after an operation. It’s non-productive time. Waiting time is not applied to the work center load. It's for periods such as drying time or cooling time that occurs after a process was completed on a machine and until the machine can next be used. Note - informationWaiting time is always expressed in hours. It does not use the time unit defined in the routing header (Time unit field).
If machine time is needed for an operation during the waiting time, you should add a new operation to the routing. A machine might be needed, for example, for drying or cooling components at a work center. The additional operation needs to be for the appropriate resource type, such as "cooler". When scheduling time for these resources if, for example, a machine or labor work center runs from 08:00 to 12:00 and from 13:00 to 17:00 with a 1 hour break from 12:00 to 13:00:
|
| Post op time (PSPTIM) |
|
Post operation, or post run time is a "deadline" that occurs after waiting time. It's non-productive time. Post run time is not applied to the work center load. It's typically "transfer time", or a transition period from one work center to the next work center that occurs after a process was completed on a machine and until the machine can next be used. Note - informationPost run time is always expressed in hours. It does not use the time unit defined in the routing header (Time unit field).
If operator time is needed for an operation during the post run time, you should add a new operation to the routing. An operator might be needed, for example, for the transportation or carriage, or the transition between 2 work centers. The additional operation needs to be for the appropriate resource type, such as "carrier". When scheduling time for these resources if, for example, a machine or labor work center runs from 08:00 to 12:00 and from 13:00 to 17:00 with a 1 hour break from 12:00 to 13:00:
If the operation requires an "emergency release", a reduction coefficient can be assigned that makes it possible to completely remove any post run time. Note - warningWhen scheduling time for these resources, if both waiting time and post run time was declared for the operation, only the largest of the 2 values is used.
|
| OP UOM (OPEUOM) |
|
Work order operation quantities are expressed in the operation unit. Use the operation unit to express the operating time in a different unit to that of the product being produced by the routing. Example
A product managed by unit is subject to 3 different operations, none of which produce intermediate stock:
There's no need to create semi-finished products for each production phase. The operation unit is associated with a conversion coefficient for the stock unit of the product being produced by the routing and the operation unit. |
| STK-OPE conversion (OPESTUCOE) |
|
The stock unit-operation unit conversion coefficient is used to convert the released quantity of the finished product into the quantity of the operation, according to its unit. It belongs to the coefficient table. |
| Subcontract (SCOCOD) |
|
Indicates if the operation is subcontracted to an outside company. Subcontract is the term used to describe the purchase of a service for carrying out an operation for a work order.
|
| Subcontracted prod. (SCOITMREF) |
| The service to be carried out by the subcontractor to execute the operations. The product needs to have a Service category. |
| Subcon w/c (SCOWST) |
|
A subcontract work center can be used for the following:
A subcontract work center has the work center type set to Subcontracting. Routing operations are validated to ensure that the work center site of a subcontract work center matches the site for the routing code, if defined. |
| Subcontract work center group (SCOWCR) |
| The group of work centers this subcontracted work center belongs to. Work center groups are used to review workloads. |
| BP (BPRNUM) |
| The subcontract supplier code to purchase the subcontracted product from. |
| Address (BPAADD) |
| The subcontract supplier address. |
| Reference price (REFPRI) |
| The generic price to apply to the subcontract service. This price will be applied (by operation unit) throughout the order process. |
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 rangeThe end value in the range is before the start value.
Work center: XXX. Work center does not exist on this siteAll 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 centeror
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 productThis 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/XThis is an information message. Operations are modified when the modifications are confirmed.
Creation of operation X/X/XThis is an information message. Replacement operations are created when the modifications are confirmed.
Log file
Operation X/X/X. A replacement operation already existsFor 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.