Network routings
A simple routing contains only sequentially ordered operations. A network routing can contain sequentially ordered operations and parallel operations.
LN offers three methods to define parallel operations:
- Manually, in the Operation Relationships by Order (tisfc1102m000) session.
- By inserting phantom components that have a routing.
- By defining parallel operations in the Job Shop Routing Operations (tirou4101m000) or Generic Routing (tipcf3120m000) session.
-
If the Sites and Job Shop by Site parameters in the Concept Activation (tcemm4600m000) are In Preparation or Active routings are maintained on site level.
-
Only converging network routings are supported: two operations can a common succeeding operation, but they cannot have a common preceding operation. Every network routing has one final operation.
To manually define parallel operations
To manually define parallel operations in the production order planning, complete the following steps:
- Create a production order with a sequentially-ordered routing.
- Start the Operation Relationships by Order (tisfc1102m000) session.
- For each operation, enter the number of the next operation in the Next Operation. Enter 0 in the production order's final operation.
To define parallel operations using phantom components
To define a routing that has a secondary branch that joins the main routing halfway, complete the following steps:
- Define a phantom item that represents the subassembly created in the secondary routing branch.
- Define the phantom item's routing, which is the secondary branch.
- Add the phantom to the job shop bill of material of the main item.
-
In the Job Shop Bills of Material (tibom3100m000) session, link the phantom to the operation that follows the secondary branch of the routing.
Alternatively, you can link the phantom to a specific operation for each routing in the BOM Line - Material-Routing Relationships (tibom0140m000) session.
LN connects the routing of the phantom item to the main item routing immediately before the main item operation that is linked to the phantom. For more information, see Example network routing.
To link an operation to phantom for a specific production order, in the Estimated Materials (ticst0101m000) session, specify that operation in the Operation field. For an example, see Example network routing.
To define parallel operations in a routing
If the Allow Parallel Operations in Routing check box in the Job Shop Master Data Parameters (tirou0100m000) session is selected, you can define parallel routings in the Job Shop Routing Operations (tirou4101m000) session.
To define parallel operations in a routing, complete the following steps:
- Before you enter the operations, roughly order the operations from first to last. Ensure no operation is followed by an operation that must be performed earlier.
- Start the Job Shop Routing Operations (tirou4101m000) session.
- Define all routing operations. At first, leave the Next Operation field at the default value, 0 (zero).
-
For each operation, in the Next Operation field, enter the operation that is performed next.
The operation number of the next operation must be greater than the number of the current operation. For example, operation 40 cannot follow operation 50.
For the final operation, enter 0 (zero) in the Next Operation field.
After you complete the routing, validate the routing and correct any errors. To validate the routing, on the appropriate menu, click .
To define parallel operations in a generic routing
The procedure to define parallel operations in a generic routing is almost the same as that for regular routings. Instead of the Routing Operations (tirou1102m000) session, you must use the Generic Routing (tipcf3120m000) session.