Multi-level routings
Use the Multi-level routings function to view details of a selected routing on a specific date and the operations in the routing that apply on that date. The details include the time it takes to set up and run each operation. Information is indented to show the different levels.
Prerequisites
Refer to documentation Implementation
Screen management
The Multi-level routings function displays an initial 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.
XSL
Routing
Routing (field ROUNUM) |
This routing code describes the process involved in manufacturing (producing) or processing a product. That is, 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 (a bill of materials), or a generic reference to a parent routing which is linked to several products. |
Routing code (field 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 (for use in a manufacturing environment, for costing or for capacity planning). |
Site (field FCY) |
The production site associated with the user is proposed by default. It can be modified by another site authorized for the operator, depending on its authorizations. |
Major version (field ROUECCMAJ) |
The Major version and Minor version fields and the Reference date field are directly linked. The 'version' fields default to the version of this routing that applies on the defined Reference date. You can change the displayed version (major or minor), if required. The Reference date is changed to the start date of the validity period for the selected version. |
Minor version (field ROUECCMIN) |
Version start date (field ROUECCSTR) |
This field displays the start date of the displayed version's (major and minor) validity period. |
Version end date (field ROUECCEND) |
This field displays the final date of the displayed version’s validity period. This field is blank if the displayed version is the current, or active version. |
BOM code (field BOMALT) |
Several BOMs can be defined for a single product reference. They can be distinguished via the code, entered on two numbers. The various BOM codes can be used to manage different product structures according to their use context such as:
This field can be left empty (value = 0) to enable manual entry of the components. In this case, only the component is loaded. |
Major version (field BOMECCMAJ) |
The Major version and Minor version fields and the Reference date field are directly linked. The 'version' fields default to the version of the bill of materials (BOM) that applies on the defined Reference date. You can change the displayed version (major or minor), if required. The Reference date is changed to the start date of the validity period for the selected version. |
Minor version (field BOMECCMIN) |
Version start date (field BOMECCSTR) |
This field displays the start date of the displayed version's (major and minor) validity period. |
Version end date (field BOMECCEND) |
This field displays the final date of the displayed version’s validity period. This field is blank if the displayed version is the current, or active version. |
Reference date (field DATREF) |
Use this field to automatically select the routing and bill of materials (BOM) versions for which the validity period matches the defined Reference date. |
Header
Description (field ROUDES) |
Technical lot (field MFGLOTQTY) |
Validity dates (field ROUSTRDAT) |
field ROUENDDAT |
field W1 |
field USESTA |
This field indicates the status on the shop floor of the preparation of the operations and tools in this routing. This field will be set to one of the following values:
A routing can only be assigned to the various manufacturing processes (such as work orders and cost calculations) when its status is 'Available to use'.
|
Grid Routing detail
Level (field LEV) |
Level (field NIVEAU) |
Line number (field NOLIG) |
Component (field GRPITMREF) |
Description (field ITMDES1) |
Routing (field OPEROUNUM) |
Operation (field OPENUM) |
Alternate index (field RPLIND) |
Product (field ITMREF) |
Valid from (field BODSTRDAT) |
Valid to (field BODENDDAT) |
Sequence (field BOMSEQ) |
Work center (field WST) |
Work center type (field WSTTYP) |
Work center group (field WCR) |
Tools (field EQUNUM) |
Subcontracted prod. (field ITMSST) |
BP (field BPRNUM2) |
Setup time (field SETTIM) |
Run time (field OPETIM) |
Post-run time (field PSPTIM) |
Waiting time (field WAITIM) |
Preparation time (field PRPTIM) |
Time unit (field TIMUOM2) |
Operation UOM (field OPEUOM) |
Run time code (field ROOTIMCOD) |
Management unit (field TIMCOD) |
Number of resources (field LWSTNBR) |
Component (field CPNITMREF) |
Component type (field CPNTYP) |
Parent (field PARKEY) |
Key (field KEYC) |
Screentip (field LIBSH) |
Icon (field ICO) |
Expand (field EXPFLG) |
Weight (field POIDS) |
Text (field ROUTEX) |
Current element
field XLIB |
field XLIBL1 |
field XLIBL2 |
Major version (field XBOHECCMAJ) |
This field indicates which major version of this component applies. Major versions might be used where there have been increased or significant changes to the original or previous version, that is the 'form, fit or function' has changed. |
Minor version (field XBOHECCMIN) |
This field indicates which minor version of this component applies. Minor versions might be used where there have been minor features or changes in functionality, or significant fixes applied to a specific major version. |
Work center
Work center group (field XWCR) |
Work center (field XWST) |
field XWSTTYP |
Number of resources (field XWSTNBR) |
Operation
Operation (field XOPENUM) |
field XRPLIND |
Validity dates (field XVALSTRDAT) |
field XVALENDDAT |
Setup time (field XSETTIM) |
field XTIMUOM1 |
Preparation time (field XPRPTIM) |
field XTIMUOM2 |
Run time (field XOPETIM) |
field XTIMUOM3 |
Waiting time (field XWAITIM) |
field XTIMUOM4 |
Quantity (field XBASQTY) |
field XOPEUOM |
Post op time (field XPSPTIM) |
field XTIMUOM5 |
Run time cd (field XROOTIMCOD) |
field XTIMCOD |
Text
field TEXTE |
Image
Image (field IMG) |
Subcontract
Subcontract (field SCOCOD) |
The sub-contracting code is used to determine whether the operation is carried out internally or if it is sent outside to a sub-contracting supplier. It can take the following values:
|
Subcontracted prod. (field SCOITMREF) |
BP (field BPRNUM) |
Product |
Click Product from the Actions icon to view or amend the details of the selected product. |
Routing |
Click Routing from the Actions icon to view or amend the routing details. |
Stock by site |
Click Stock by site from the Actions icon to view the inventory levels for the selected product, by site. |
Specific Buttons
First level |
Click the First level action to display the operations in the selected routing. |
Multilevel |
Click the Multilevel action to display the operation details. |
Graph |
Click the Graph action to view the scheduling details. You can switch between displaying the details in a graphical or tabular format. |
Where-used |
Click the Where used action to view the list of products that can be manufactured (produced) using this routing. |
Printing |
Click the Printing action to print the details of this routing. |
Error messages
The only error messages are the generic ones.
Tables used
Refer to documentation Implementation