Skip to end of metadata
Go to start of metadata

Purpose

The purpose of this page is to give a rough guide real-life illustrative example of how the route schedule functionality works. It is intended to be an illustrative aide to SAP note 146829 .

Overview

A route is typically characterized by 2 entities: i) a shipping point from which the goods are issued and ii) a ship-to party to which the goods are sent. A route may consist of multiple ship-to parties before the final ship-to party of the route is reached. The route schedule functionality will allow you to calculate accurate delivery dates / times for the various ship-to parties along the route.

Example: Why use Route Schedules?

In this example, a shipping point exists in Nice, France. A route exists between Nice & Paris. A ship-to party in Paris represents the final ship-to party of the route. The process of transporting our goods from our shipping point in Nice to our ship-to party in Paris is defined in route ZNCEUR. However, there are a number of other ship-to parties in our system on the route from Nice to Paris (See illustration). Therefore, we want to set up the route schedule functionality to calculate accurate delivery times for these customers.


Example: How to create Route Schedules

The route schedule is created in transaction VL51. Transaction VL51 is reached by following this menu path from the easy access menu:

> Logistics - Logistics Execution - Master Data - Transportation - Routes - Route Schedule
The relevant shipping point is entered and an appropriate name assigned to the route schedule.


 
A description for the route schedule must be entered. Additionally, the relevant route (in this case, ZNCEUR), the GI day of the route schedule (the day of the week that this route schedule is valid) and the GI time (the time that the goods are issued from the shipping point) must be maintained. The relevant ship-to parties along the route must also be entered into the route schedule:

In this example, the shipping point issues goods along the ZNCEUR route at 9am every Monday.

The next step is to maintain an itinerary.

Itinerary

The potential of the route schedule functionality is best realized by using an itinerary. The specific transit times between each ship-to party on the route are maintained in the itinerary. Creating an accurate itinerary will allow the system to calculate accurate delivery dates / times. If the transit times maintained in the itinerary are incorrect, the system will calculate inaccurate delivery dates / times.

In this example, we have a ship-to party located at Marseille (Customer 96), Toulouse (Customer 97), Bordeaux (Customer 98), Nantes (Customer 99) & the last ship-to point is in Paris (Customer 101).

Nice – Marseille = 6 hours transit time

Marseille – Toulouse = 16 Hours transit time

Toulouse – Bordeaux = 5 hours transit time

Bordeaux – Nantes = 5 hours transit time

Nantes – Paris = 22 hours transit time

Total Transit Time = 54 hours

To implement the above on the ECC system, you must maintain an itinerary in transaction VL51 / VL52:


The above specifies a route schedule where goods are issued from shipping point ZNCEUR every Monday. However, a business may want to issue goods from their shipping point on other days (and times) too. To realize this, more route schedules must be created in the same way as illustrated above.
 

The Effect of a Route Schedule on the scheduling result in a Sales Order

After a SD scheduling is executed, the system determines the route schedule. The system will add the specific transit time to the goods issue time to calculate the expected arrival time at the ship-to party. For example, a sales order is created for customer 101 with a requested delivery date = Monday 10th September, 2012. The system searches for the appropriate route schedule for that week and determines that the goods can be issued on Monday 10th September at 09:00 according to route schedule ZNC-PARMON. Monday 10th September (09:00) + 54 hours = Wednesday 12th September. Instead of confirming on the requested delivery date, the system confirms for this date /time:

Similarly, if a sales order was created for ship-to party 98 with a required delivery date = 10th September, the system determines route schedule ZNC-PARMON and calculates an arrival date / time = 11th September, 12:00. The Goods issue date / time is 10th September (09:00) + 6 hours to get to ship-to party 96 = 10th September (15:00) + 16 hours to get to ship-to party 97 = 11th September (07:00) + 5 hours to get to ship-to party 98 = 11th September (12:00):


Related Content

Related Documents

http://help.sap.com/saphelp_47x200/helpdata/EN/dd/560dee545a11d1a7020000e829fd11/frameset.htm

Related Notes

SAP Note 146829  : Process flow of route schedule


 



 

1 Comment

  1. Former Member

    Great article.. very well written. I have a question though - Route ZNCEUR, were the stages also maintained in this route?