Routing management - Implementation

Prerequisites

Activity codes

The following activity codes (sorted by type) can have an impact on the way the function operates:

Functional

  • CAP: Finite capacity
  • CCM: Change control management
  • CFG: Configurator
  • MWM: Weighing stations
  • NPI: Product design
  • RVM: Routing version management
  • SMI: Integrale migration

Sizing

  • MFO: Number of operations

General parameters

The following general parameters might change the way the function is working:

Manufacturing

  • ROUSTE (defined at level Folder): Operation sequence increment

Authorizations

This function is object managed. The creation, modification, and deletion operations can be activated or deactivated for a given user. Filters by roles can also be associated with this function.

As data is linked to a site, a filter per site can be activated.

A filter by access code is performed, based on the ACSCOD field. If an access code is given, inquiry and modification rights are granted according to the read and write permissions for the current user code. These are defined in their function profile.

Miscellaneous prerequisites

The routing code needs to be an existing product code.

Other prerequisites are as follows:

  • Standard operations
  • Work centers
  • Units
  • Technical sheets
  • Tools

Tables used

The following tables are implemented by the function:

Table

Table description

ATABZON [ATZ]

Field dictionary

ATEXTRA [AXX]

Texts to translate

ITMFACILIT [ITF]

Products-sites

ITMMASTER [ITM]

Products

MFGHEAD [MFG]

Work order - header

ROUOPE [ROO]

Routing - operations

ROUOPESTD [ROT]

Standard operations

ROUSCD [ROS]

Routing - scheduling operation

ROUTING [ROH]

Routings - header

TABROUALT [TRO]

BOM routings

TABWRKCTR [TWC]

Work center groups

WORKSTATIO [MWS]

Work centers