Multi-level routings
Use this function to view details of a routing for a specific date and the operations in the routing that apply on that date. The details include the time that it takes to set up and run each operation. Information is indented to show the different levels.
Prerequisites
Screen management
The Multi-level routings function displays a single screen into which you enter details of the routing and the date you want the routing details to be displayed for.
Entry screen
You use this screen to enter details of the routing and your reference date.
Routing
| Routing (ROUNUM) |
|
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. |
| Routing code (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. |
| Site (FCY) |
| The site at which the shop floor processes in the routing were prepared. The In development and Available to use sites need to be identical. |
| Major version (ROUECCMAJ) |
|
Indicates if this is a major version of the routing. Major versions might be used where there have been increased or significant changes in functionality. The "form, fit, or function" has changed. Note - informationThe Major version and Minor version fields, and the Reference date field are directly linked. The "version" fields default to the version of the routing that applies on the Reference date. You can change the displayed major or minor version, if needed. The Reference date changes to the start date of the validity period for the selected version.
|
| Minor version (ROUECCMIN) |
| Indicates if this is a minor version of the routing. Minor versions might be used where there have been minor features or changes in functionality, or significant fixes applied to a specific major version. |
| Version start date (ROUECCSTR) |
| The major and minor version validity period start date. |
| Version end date (ROUECCEND) |
| The major and minor version validity period end date, or blank if the version is the current or active version. |
| BOM code (BOMALT) |
|
The numeric code associated with a production BOM. Multiple bills of material (BOM) can be defined for a single product. Each BOM code can be assigned specific management features. For manufactured or subcontracted products, this includes restriction of the BOM to a specific site and to specific areas of functionality such as for costing or for capacity planning. |
| Major version (BOMECCMAJ) |
|
Indicates if this is a major version of the production BOM. Major versions might be used where there have been increased or significant changes in functionality. The "form, fit, or function" has changed. Note - informationThe Major version and Minor version fields, and the Reference date field are directly linked. The "version" fields default to the version of the BOM that applies on the Reference date. You can change the displayed major or minor version, if needed. The Reference date changes to the start date of the validity period for the selected version.
|
| Minor version (BOMECCMIN) |
| Indicates if this is a minor version of the production BOM. Minor versions might be used where there have been minor features or changes in functionality, or significant fixes applied to a specific major version. |
| Version start date (BOMECCSTR) |
| The major and minor version validity period start date. |
| Version end date (BOMECCEND) |
| The major and minor version validity period end date, or blank if the version is the current or active version. |
| Reference date (DATREF) |
|
Selects the routing and BOM versions with a validity period that include the date you enter.
Note - informationThe routing and production BOM Major version and Minor version fields, and the Reference date field are directly linked. The "version" fields default to the version of the routing and BOM code that applies on the Reference date. |
Header
| Description (ROUDES) |
| The routing description. |
| Technical lot (MFGLOTQTY) |
|
Lot size. The lot size is used in the MRP (Material Requirements Planning) calculation. According to the reorder policy, you can perform the following actions:
Example
Production suggestion of 500 units, to be divided into 5 suggestions of 100 units. Purchasing suggestion of 52 units with a lot size of 12, 60 units need to be ordered. |
| Validity dates (ROUSTRDAT / ROUENDDAT) |
| The major and minor routing version validity period start and end dates. |
| USESTA |
|
The status on the shop floor of the preparation of the operations and tools in the routing. In development: The routing is not yet complete. Available to use: The routing is complete and the coherence of the routing operations was validated. Note - tipA routing can only be assigned to manufacturing processes such as work orders and cost calculations if the status is Available to use.
|
Routing detail
You use this section to view the details of the routing hierarchy. You can expand and collapse the levels, and select any level to view the details.
Grid: Routing detail
| Level (LEV) |
| The production operations and operation resources at each level in the routing. |
| Component (GRPITMREF) |
| The component needed for the production operations and operation resources. |
| Description (ITMDES1) |
| The description from the product record. |
| Routing (OPEROUNUM) |
|
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. |
| Operation (OPENUM) |
| The operation sequence number. |
| Alternate 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. |
| Product (ITMREF) |
| The product code. |
| Valid from (BODSTRDAT) |
| The validity period start date or blank if the BOM is valid until the defined end date. |
| Valid to (BODENDDAT) |
| The validity period end date, or blank if the BOM does not have a validity period. |
| Sequence (BOMSEQ) |
| Identifies the sequence number of the component in the BOM (bill of material). |
| Work center (WST) |
|
Identifies the production resource to use for the 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. Operation scheduling considers the availability of the work center. You can specify the number of operators to allocate to it however you cannot allocate more resources than that defined on the work center record. |
| Work center type (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. |
| Tools (EQUNUM) |
| The product reference for the tool. |
| Subcontracted prod. (ITMSST) |
| The service to be carried out by the subcontractor to execute the operations. |
| BP (BPRNUM2) |
| The subcontract supplier code to purchase the subcontracted product from. |
| 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. |
| Run time (OPETIM) |
|
The time needed to manufacture the product described in the routing. The operating time:
|
| Post-run 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.
|
| 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:
|
| 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. |
| Time unit (TIMUOM2) |
|
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. |
| Operation 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. |
| 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. |
| Number of resources (LWSTNBR) |
| The number for this particular production resource that are needed for the operation. |
| Component (CPNITMREF) |
| A component that's needed to produce the product. |
| Component type (CPNTYP) |
|
Indicates if the component is stored in stock. Physical: This is a physical component. Quantities are stored in stock. Active: This is an active component such as nails or staples. Quantities are not stored in stock. Note - tipActive components have a "potency" percentage defined on the stock record.
|
| Parent (PARKEY) |
| Key (KEYC) |
| Screentip (LIBSH) |
| Icon (ICO) |
| Expand (EXPFLG) |
| Weight (POIDS) |
| Text (ROUTEX) |
| Text associated with the routing. |
Current element
The field values in this section display after you select a line in the Routing detail table.
Operation
| Operation (XOPENUM) |
| The operation sequence number. |
| XRPLIND |
| 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. |
| Validity dates (XVALSTRDAT / XVALENDDAT) |
| The operation validity period start and end dates. |
| Setup time (XSETTIM) |
|
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. |
| Preparation time (XPRPTIM) |
|
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. |
| Run time (XOPETIM) |
|
The time needed to manufacture the product described in the routing. The operating time:
|
| Waiting time (XWAITIM) |
|
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:
|
| Quantity (XBASQTY / XOPEUOM) |
|
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. |
| Post op time (XPSPTIM) |
|
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.
|
| Run time cd (XROOTIMCOD) |
|
The operation time type applied to the production time entry.
|
| XTIMCOD |
|
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. |
Work center
| Work center group (XWCR) |
| Identifies the group of work centers that the work center belongs to. Work center groups are used to review workloads. |
| Work center (XWST) |
| Identifies the production resource to use for the operation. The resource can be a machine, a labor, or a subcontract work center. |
| XWSTTYP |
|
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. |
| Number of resources (XWSTNBR) |
| The number for this particular production resource that are needed for the operation. |
Text
| TEXTE |
| Text associated with the operation. For example, information describing how to use the workstation, how to merge colors, how to use tools, the torsional movement to fix a screw. |
Image
| Image (IMG) |
| An image of the product at the level you select in the routing hierarchy. |
Subcontract
| 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. |
| BP (BPRNUM) |
| The business partner code. |
| Product |
| Select Product from the Actions icon to view or amend the details of the selected product. |
| Routing |
| Select Routing from the Actions icon to view or amend the routing details. |
| Stock by site |
| Select Stock by site from the Actions icon to view the inventory levels for the selected product, by site. |
Action panel
| First level | Select the First level action to display the operations in the selected routing. |
| Multilevel | Select the Multilevel action to display the operation details. |
| Graph | Select the Graph action to view the scheduling details. You can switch between displaying the details in a graphical or tabular format. |
| Where-used | Select the Where used action to view the list of products that can be manufactured (produced) using the routing. |
| Printing | Select the Printing action to print the routing details. |
Error messages
The only error messages are the generic ones.