A routing method is a list of destinations describing the journey material will travel on its way from the supplier to the construction site. Supplier shipments can take any number of different routes to their final destination at the job site. Each route requires a routing method to be identified for accurate calculation of ETA (Estimated Time of Arrival) times. A routing method is made up of one or more destinations and the number of days required to arrive at the current destination from the previous one.
In this function, the destinations defined on P.10.52 as well as the amount of time material spends at a destination and needs to arrive at the next destination are maintained.
Routing methods are used to calculate expediting dates.
Routing methods with their destinations and transit days are defined on the P.10.53 Routing Methods screen.
First, select the delivery type and delivery designation of the new routing method in the first (Delivery Designations) block. The delivery types and designations are defined on the A.10.39 Delivery Designations screen. For more information see Delivery Designations.
To define a routing method in the second (Routing Methods) block, enter the name in the Routing Method field and the descriptions in the Short Desc and Description fields.
When you create a new routing method by duplicating an existing one using the F4
(duplicate record above) key, all details (destination, transit days) will also be
copied. Then you can create new details, or delete or update existing ones.
The Transit Days field shows the total of transit days of the associated routing method schedules. If you are working with extended expediting (project default ZP_NEW_EXP set to Y), only the transit days of those destinations with an order sequence equal to or higher than that of the destination marked as the delivery date are taken into account for this calculation .
In the third (Routing Method Schedules) block, you define the destinations of the selected routing method with their transit days. Enter a unique sequence number in the Seq field. This sequence number is used to order the material destinations. Then select a destination from the LOV in the Destination field. Double-click in this field to open P.10.52 where the destinations are defined. If you enter an unknown destination, it will be created automatically if you acknowledge the message "You have entered an unknown destination. Do you wish to continue?" with Yes.
You cannot create routing methods without marking exactly one destination as the
delivery date because all calculations in the extended expediting module are based
on this destination.
Enter the number of days that are required to deliver the material from the previous to the current destination in the Transit Days field. We recommend that you enter 0 (zero) in the Transit Days field for the last destination in the supply chain to avoid any confusion. As you have reached your final destination, another value for the transit days is not really needed, but it must be entered because it is a mandatory field.
When item shipments are created and a routing method is assigned, the transit days
of the routing method are used to calculate some of the dates on item shipments.
In the Date Type field, you specify the type of date this destination represents. This information is necessary for saving the data in case of an update of the routing method in the extended expediting module. Each type of date except the NULL value and Shipping can only be assigned to one destination within a routing method. Moreover, this type of date is needed if you work with basic expediting (project default ZP_NEW_EXP set to N) and the project default ZP_POP_ETA is set to POP_MOC. In this case, several date values are populated to the associated item shipments:
-
ETD Date -> predicted ship date
-
ATA Date -> actual ship date
-
ETA Date -> predicted traffic arrival date
-
ATA Date -> actual traffic arrival date
Also, the predicted on site date is recalculated if in the routing method schedule, one destination is set to date type Traffic Arrival and another destination with a higher order sequence is set to type Arrival On Site. The new value then depends on the sum of the transit days between these two destinations:
Predicted on site date = ATA date + sum of transit days
If the ATA date is not set, but the ETA date is set, this date value is used instead. If both the ETA date and ATA date are not set, the predicted on site date is calculated as:
Predicted on site date = curr/rev prom ship + sum of all transit days of the routing method.
If curr/rev prom ship is not filled, prom ship date is used for the calculation.
The Delivery Date check box is an indicator for whether this destination represents the contractual delivery date. You must select this indicator for exactly one destination for each routing method if you work with the extended expediting module (project default ZP_NEW_EXP is set to Y). This check box is evaluated when doing the automatic calculation of planned dates in the extended expediting module. This calculation starts at the destination marked as Delivery Date, which is the contractual delivery date of the item shipment.
To avoid any conflicts later on in expediting, we recommend NOT setting this check
box for destinations that have been marked as type Inspection or type IRC.
The Main Destination check box is an indicator for whether this destination is regarded as the main destination. Main destination means that the main transport of a routing method starts at this point and ends at the next destination (for example shipment, flight, transportation by train). This indicator is evaluated in the extended traffic module and used for populating the traffic tree (PT.20.01). Please see the description of module PT.20.01 for more information. You must check this indicator for exactly one destination for each routing method if you work with extended expediting (project default ZP_NEW_EXP is set to Y).
If you are working with the extended expediting module (project default ZP_NEW_EXP
is set to Y) and you modify the schedule of a routing method, these changes are automatically
populated to the expediting dates within the extended expediting module. Depending
on the number of related item shipments, this may take some time. Therefore, we strongly
recommend that you set up all routing methods within a new project prior to creating
orders and item shipments.
-
Any changes are only applied to item shipments that cannot be found on approved release notes. If approved release notes exist, a second window appears to show you the affected release notes. Then it is up to you to decide for which release notes you also want the updates to be passed on.
-
You cannot delete a destination on the schedule if the routing method can be found on an approved release note. In this case, you can only either unapprove the affected release notes or set the number of transit days to 0.