Multi-level routings

• 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 the same 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:

• MRP calculation,
• Sales order entry
• Manufacturing/production

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.

• 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:

• 'In development', if the routing is not yet complete.
• 'Available to use', if the routing is complete and the coherence of the routing operations have been validated.

 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'.

 The 'In development' and 'Available to use' sites must be identical.

• 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.

• 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)

• Work center group (field XWCR)

• Work center (field XWST)

• field XWSTTYP

• Number of resources (field XWSTNBR)

• 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

• field TEXTE

• Image (field IMG)

• 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:

• No: the operation is never sub-contracted. The sub-contracting product and the sub-contracting work center cannot be assigned,
• Structural: the operation is systematically sub-contracted. The factory does not have the required skills or toolings. The sub-contracting product is mandatory and the sub-contracting work center cannot be assigned. it is loaded with the principal work center, which, in this case, must be of the sub-contracting type.
• Temporary (conjuncture related): the operation is carried out internally in priority, but in case of overload or temporary problem, it can be sub-contracted. The sub-contracting product and the sub-contracting work center can be assigned and are mandatory.

• Subcontracted prod. (field SCOITMREF)

• BP (field BPRNUM)