Objective
Default Routes
A default route defines the sequence of stops for a given source/destination location combination. Default routes can be used in place of transshipment chains with sales orders and deliveries, forwarding orders, and forwarding quotations. Default routes can be modified manually where the desired route is different to that proposed by the system.
To see information related to default routes, log into SAP Fiori, then choose Master Data folder→Define Default Routes.
_Scr.png "Sailing Schedule with Gateway (CFS).")
When shipping products via air or ocean, consider that your partners are typically renting space at a port facility. This facility is used by many parties, and so options for moving the product can be limited.
While the road-based scenario can make use of various transportation lanes due to the flexibility of the carriers, ocean and air carriers often face more competition and more regulation. This limits the flexibility for departures and arrivals. From a transportation planning perspective, the implication is that you may need a more structured and predictable plan for scheduling purposes. With SAP Transportation Management (SAP TM), your organization can take advantage of different types of schedules to model specific departure and arrival rules suited to air and ocean shipping.
Carrier schedules represent the actual transportation executed by the schedule vehicle. Be it by plane, vessel, train, or truck. Usually, these schedules involve stopping at locations such as ports and airports that are used commonly and shared by many different carriers. Flights for air transportation and vessel voyages for the ocean are examples of carrier schedules. Carrier schedules can also be truck schedules.
Location and time information are relevant to a schedule. For example, the planner asks the following questions:
When and from where does the plane depart?
When do you have to be there to board it?
When will it arrive?
Which carrier is responsible for the transportation?
What can be transported?
Carrier schedules do not just have a start and end destination; they can have multiple stops, which is common for air transportation. Carrier schedules can be executed by different carriers on different stages using a connection schedule. It is possible to use a multistop carrier schedule in any sequential location combination, so it is not required to start at the first and leave at the last location.
Schedules can be created manually in SAP TM and uploaded from an external source. You can also upload schedules from an external data source to SAP TM by calling function module /SCMTMS/BAPI_SCHEDULE_SAVEMULT. This function is available for the sea, air, and road transportation modes. Alternatively, you can upload schedules for the air transportation mode in a spreadsheet or CSV format to SAP TM by executing report /SCMTMS/SCH_UPLOAD. For more information, see the system documentation.
You can delete schedules created manually and uploaded by calling function module /SCMTMS/BAPI_SCHEDULE_DELMULTI or by executing report /SCMTMS/SCH_DELETION.
There are four ways to generate a schedule departure. A user can manually create a schedule departure for a specific date or generate schedule departures based on departure rules according to a specific pattern (for example, every Monday at noon). Furthermore, you can upload schedule departures either using the schedule upload report /SCMTMS/SCH_UPLOAD or by calling function module /SCMTMS/BAPI_SCHEDULE_SAVEMULT.
SAP TM allows businesses to create different schedule types to handle the multiple shipping scenarios they may encounter. Schedules can be maintained for each business partner or carrier, and can identify different loading and unloading points, such as ports and airports.
If you have reappearing transportation traffic in your transportation network scenario, you can use the schedules functionality. A combination of transportation mode, gateway customer fact sheets (CFS), direct, and reference fields define the type of schedule.
A gateway schedule includes two gateway locations. In ocean scenarios, the locations could be the CFS-locations. In air scenarios, they can be the gateway locations.
The following are the subcategories in the gateway schedules:
The schedule goes from A to B without changing the mode of transport. For example, GW Nurnberg to GW Hamburg via truck.
The schedule goes from A to B but the mode of transport changes. For example, GW Hamburg to GW Cape Town via truck and ocean.
The following are the subcategories in ocean and air scenarios:
Sailing schedules with vessel information
Master flight schedules with aircraft information
Carrier schedules describe a sequence of transportation stops where the start location and the target stop are not gateways. A gateway is a transportation hub where freight is consolidated and deconsolidated.
Use the ocean carrier schedule to define a standard sequence of transportation stops that are served by a ship. By specifying departure rules, you can generate voyages automatically.
Use the carrier flight schedule to define a standard sequence of transportation stops that are served by a plane. By specifying departure rules, you can generate flights automatically.
Use the road schedule to define a standard sequence of transportation stops that are served by a truck.
In the schedule type, you can define if the schedule has the following items assigned to it:
Limited capacities
Transportation costs