
SAP SD Route Determination – Zones, Conditions & Groups
Say a customer in Mumbai orders 500 units of a product that is in your Pune plant. The business has a few things it wants to know before anything is shipped out of the warehouse. What route will the truck travel? How long will the journey take? What delivery date can the sales team promise the customer? In SAP Sales and Distribution, SAP SD route determination delivers the answers.
This guide covers a worked example, best practices and the errors that trip up most consultants. What is route determination in SAP? What master data drives route determination? How does delivery scheduling in SAP SD use route determination? How to do route determination configuration in SAP? It is useful for SAP SD beginners, functional consultants, support teams and SAP SD interview candidates.
What Is Route Determination in SAP SD?
Routing is a SAP SD function that automatically suggests a transportation route for a sales order item. It reads master data and a configuration table that you configure once, so that sales users never have to manually choose a route.
A route is the path a good travels from the point of shipment to the customer’s location. It could be by road, rail, air or sea and each route has details such as:
- Transit time, time from loading to arrival time
- Travel time means the actual time spent traveling
- Distance and distance unit
- Shipping type (e.g. truck, train, flight or ship)
- Carrier or service agent, as applicable
- Factory calendar, to account for weekends and holidays
Route determination is important because it:
- Saves time, as transportation details are not decided by order entry personnel
- Uniformity of logistics rules across all orders
- Scheduling of feeds delivery so that confirmed dates are realistic
- Supports different levels of service for different customers
- Cuts down on delivery delays and customer complaints
- Flexible, because the proposed route can still be manually changed in the sales order
The system suggests the route on item level in the sales order and copies it to the schedule lines and the outbound delivery. In the delivery it can be determined again if data like ship-to party or delivery weight has changed.
Primary Elements for the Choice of Routes
The system will not try to guess the path. It finds a configuration table using a fixed set of values. If it finds one it likes it suggests the route. If not, it displays an error.
Input is:
| Input | Meaning | Where it comes from |
|---|---|---|
| Departure zone | Where goods are withdrawn from the shipping point | Shipping point |
| Transportation zone | The receiving zone for the goods | Ship-to party |
| Shipping condition | The level of service expected by the customer | Customer master or sales document type |
| Transportation group | How material must be handled when transporting | Material master |
| Weight group (optional) | A class based on the weight of the consignment | Delivery weight |
Think of it as a look up table. You give it four or five values and it will give you one route. That is why full master data and a full configuration matrix are important. If one value is missing the lookup will fail.
Transport Areas
Transportation zones are geographic areas that aggregate origin and destination points. They are the foundation of route selection in SAP.
- Departure area: Assigned to shipping point. It tells the system where the journey starts.
- Receiving transportation zone: stored in the ship-to customer’s general data in the address section. This tells the system where to end the trip.
- Level of detail: a zone could be an entire state, a city or a set of postal codes. Choose the level that reflects how your carriers actually price and route.
- Naming: use a clean pattern like a state code and a number. Consistent names make maintenance and troubleshooting much easier.
- Coverage: must have a zone for each ship-to party. Missing zones are typical for customers created by bulk or migrated from legacy systems.
- Country link: transport zones are defined per country, so the same code can appear in different countries.
Pro tip: Before go-live, export your customer list, map all addresses to a zone, then bulk load the zone values. This stops hundreds of errors in the first week.
Transport Groups and Shipping Conditions
These two fields are about customer expectations and product handling requirements. Together they allow two orders to the same city to take different roads.
Shipping condition
- Is maintained in the customer master in the sales area shipping data.
- Typical values are standard, express and customer pickup.
- Also can be proposed from the sales document type. This will overwrite the customer master value if set there.
- You can give faster service to premium customers without any manual work.
Transportation group
- It is stored in the material master under the sales and general plant data.
- Typical values are standard goods, fragile goods, refrigerated goods and dangerous goods.
- It guarantees that special products are shipped by the right routes and in the right vehicles. A refrigerated truck is required for frozen items, but a normal truck is enough for regular items.
A frequent source of confusion is that route determination is done by the transportation group, not the loading group. Loading group is used when the system finds the shipping point and also for some loading related processing. Classic SAP SD interview mistake: mixing the two up.
Configuration of Route Determination
Route determination configuration is done in the SAP implementation guide (SPRO), under Logistics Execution, Shipping, Basic Shipping Functions, Routes, Route Determination. The normal order of work is:
- Define the transport areas.
- Assign shipping points for the outbound area.
- Assign ship-to customers to the receiving transport zone.
- Define shipping conditions and transport groups.
- Route definition with calendars and travel times.
- Define weight groups if needed.
- Keep the route determination entries.
- Check customer master and material master data.
Expert Guidance
Learn from industry experts
Trusted & Recognized
Top-rated by learners
Flexible Learning
Online options
Placement Support
Career support & more
Route master data is stored in table TVRO (behind the scenes) and route determination entries are stored in table TROLZ. They are not needed for setting up the system but are very handy for troubleshooting an error with a technical colleague.
Best practice for any SAP project: Build and test in the development and quality systems first, capture all changes in a transport request, and move to production only after the business has signed off the test results.
Locate Transport Zones and Routes
This step lays down the building blocks of SAP route determination.
Transport zones
- Create each zone with a clear code and description.
- Assign the departure zone to the right shipping points.
- Update each ship-to customer with the correct receiving zone.
Routes
- Each route should have a unique key and a description that the business understands. For example, Pune to Mumbai road route.
- Keep the travel duration and transit duration.
- Keep the distance and shipping type.
- Assign a factory calendar to skip non-working days when scheduling.
- Add the service agent or carrier if applicable.
- For long journeys with multiple legs you can specify route stages, e.g. a truck leg to a port and a sea leg after that.
Good names and complete data prevent most of the problems showing up later.
Definition of Route Determination Logic
Now tell the system which route to suggest for each combination.
- Specify for each entry the departure zone, receiving zone, shipping condition and transportation group.
- Assign the proposed route for that combination.
- Create entries for all combinations that your business actually uses. Standard goods with standard shipping take the regular road route. Standard goods with express shipping take the express route.
- See the full matrix at the end. Any generally used combination should not be left empty.
- Test typical orders in the quality system with real customers and materials.
It is a useful habit to have a simple sheet with each combination and its route. Easy for business users to review, and it helps new consultants understand the design within minutes.
Weight Groups to Determine Routes
Weight groups allow the system to choose a different route based on the weight of the delivery. These are optional but very handy when your vehicle or carrier changes with load size.
- Define the categories, for example, deliveries under 1000 kg and deliveries over 1000 kg.
- Add them to the entries. Add the weight group where the route depends on weight.
- Match the vehicle: a light delivery can be done in a small truck, a heavy one will require a larger truck or a different carrier.
- The delivery level: weight is known only when the delivery is created, so the route can be determined again there.
Keep it simple. If weight does not change your routing, skip this feature. A simple system is easier to maintain.
Route Determination Example (Mumbai to Pune)
Let's trace a single order from start to finish.
| Field | Value in the example |
|---|---|
| Plant and shipping point | Pune, set as the departure zone |
| Ship-to party | Customer in Mumbai, receiving zone set to Mumbai |
| Shipping condition | Standard, set in the customer master |
| Transportation group | Standard goods, set in the material master |
| Determined route | Pune to Mumbai road route with a transit time of two days |
There is a configuration entry that maps these four values to the Pune to Mumbai road route.
What does the system do
- The user creates a sales order and enters information on customers and material.
- The system reads the shipping point as the departure zone.
- It reads the shipping condition and receiving zone from the customer information.
- It reads the transportation group from the material master.
- It looks for the corresponding combination in the route determination entries.
- It finds the entry and suggests the Pune to Mumbai road route.
- Dates are based on route transit time for delivery scheduling.
How route is used in delivery scheduling
Delivery scheduling in SAP SD involves many dates: the date the material is available, the date the transportation is scheduled, the loading date, the goods issue date, and the delivery date. Transit time for the route is between the goods issue date and delivery date. Backward scheduling works by starting with the date the customer wants and subtracting the transit time, loading time and pick and pack time to figure out when the goods need to be ready. Forward scheduling starts with the material being available and adds the same times to calculate the earliest delivery date.
What if the customer wants express delivery?
- The shipping condition is changed to express by the customer master or the order type.
- The system finds another entry and suggests the express route.
- The express route has a shorter transit time so the confirmed date is earlier.
A change in master data changes the route and delivery date without manual calculation. That’s the real power of this feature.
Common Error “No Route Could Be Determined”
This is the most common route determination error in SAP SD and almost always means data is missing. Check these points in sequence:
- Is there a departure area at the shipping point?
- Does the ship-to party have a receiving transport zone?
- Is the shipping condition maintained in the customer master or order type?
- Is the transport group in the material master?
- Is there an exact route determination entry for this combination?
- If weight groups are used, is there an entry for the correct weight group?
- Has master data been changed since the creation of the order?
- Is the route itself fully specified with a valid transit time and a calendar?
Other issues to look out for
| Issue | What to check |
|---|---|
| Wrong route suggested | Usually caused by a wrong default shipping condition in the order type. |
| Delivery date seems too early or too late | Check transit time of the route, factory calendar and loading, pick and pack times of the shipping point. |
| Delivery route changes | If weight or ship-to data changed, it is normal to recalculate the route in the delivery. |
Best Practice Checklist
- Work with the logistics team for zone structure design prior to touching configuration.
- Use clear and consistent names for zones, routes, and groups.
- Bulk load customer zones during data migration.
- Document a matrix of all combinations.
- Test express, standard, and pickup scenarios separately.
- Recheck the setup every time you add a new plant, shipping point or a major customer region.
- Train your sales and logistics users to know why a route was proposed.
Summary
Route determination in SAP SD makes your master data drive smart logistics decisions. When the departure zone, receiving transportation zone, shipping condition, transportation group and optional weight group are all in place the system automatically suggests the right route and a realistic delivery date.
For the best results, carefully plan your zones, maintain complete master data for customers and materials, review the complete combination matrix, and test each relevant scenario before go-live. Fewer errors, faster order processing and happier customers come with a clean setup.
Like this tutorial, want more SAP SD tutorials, configuration guides and interview questions? Join our WhatsApp channel and get every post at once.