Routes
Use this template to extract routing data, that is, the sequence of operations and tools that are involved in producing or processing a particular product or assembly (bill of materials). You can use it to import routing data from any third party product into Sage X3 and to export from Sage X3.
Imported data is converted into the right format to populate the routing header information (function Routing management (GESROU)).
Operations used in the routing, scheduling details and fields associated with the operations such as subcontracted products on the following tabs are also populated:
- Header
- Routings
- Scheduling
Prerequisites
Activity codes
Other prerequisites
Tables to be completed
The following tables are used by the function. Their content must be updated if necessary :
| Table |
Table description |
|---|---|
|
WORKSTATIO [MWS] |
|
|
TABROUALT [TRO] |
|
|
TABWRKCTR [TWC] |
|
|
ROUOPESTD [ROT] |
|
|
ROUTING [ROH] |
Routings - header |
Operation
Template ROU - Routes must be active.
Data import
To import a new non-versioned routing at status 'Available to use' define a default routing code in the ROUTING table field *3 (Default ROU code). The import process initially creates a non-versioned routing as a new versioned-managed routing at status 'In development'. When it has validated the coherence of the routing operations is correct it then sets the new versioned routing to status 'Available to use'.
The default Routing code is mandatory the first time you import a versioned routing. Subsequent imports of the same routing will use the default routing code unless you select a different routing code.
Versioned routings must be imported in the correct sequence.
To import versioned routings that are older than today's date, type 'D' in the ROUTING table field *4 (Option).
Routing operations are detected and processed as follows:
- Search on the operation number and a replacement index
If the operation exists it is modified, otherwise it is created. - If an operation is imported with the number of resources equal to '0' (table ROUOPE, field WSTNBR) the operation is deleted.
Data export
All routing codes for a product are exported.
All versions (major, major/minor) of a routing are exported, not just the current version.
Mandatory fields in the template
The mandatory fields are as follows:
Table ROUTING – Routings - header
This is the main table. It is linked to the ROU OBJect.
- Routing (ITMREF)
- Routing code (ROUALT)
- Site (FCY)
Table ROUOPE – Routing - operations
- Operation number (OPENUM)
- Main work center (WST)
- Operation UOM (OPEUOM)
Limitations
Import of additional operations for an existing routing at status 'In development' creates new operations regardless of the status of the imported operations. For example, if an import includes an operation that has been excluded, a new operation is created and the status ignored.
Tables used
This template can be used in import and export modes. The data is updated in the following tables :
| Table |
Table description |
|---|---|
|
ATABZON [ATZ] |
Field dictionary |
|
ATEXTRA [AXX] |
Texts to translate |
|
ITMFACILIT [ITF] |
|
|
ITMMASTER [ITM] |
|
|
MFGHEAD [MFG] |
|
|
ROUOPE [ROO] |
Routing - operations |
|
ROUOPESTD [ROT] |
|
|
ROUSCD [ROS] |
Routing - scheduling operation |
|
ROUTING [ROH] |
Routings - header |
|
TABROUALT [TRO] |
|
|
TABWRKCTR [TWC] |
|
|
WORKSTATIO [MWS] |