Network routingsA 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:
Note 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:
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:
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 Routing Operations (tirou1102m000) session. To define parallel operations in a routing, complete the following steps:
After you complete the routing, validate the routing and correct any errors. To validate the routing, on the appropriate menu, click Validate Sequence. Note When a production order is created, LN validates the routing and stops the process if the routing is incorrect. 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. Caution! If you specified an operation in the Next Operation field, and that operation is skipped for a particular product variant, LN does not automatically replace that operation with the correct operation. Instead of the operation that follows the skipped operation, LN selects the operation with next higher operation number. After LN generated the routing for the product variant, correct the operation sequence for the customized item or configured standard item in the Routing Operations (tirou1102m000) session.
| |||