How Are Forwarding Orders Created in SAP TM, and How Does It Handle Order-Based and Delivery-Based Requirements?

Introduction :

 SAP TM Online Training Every transportation process begins with one component: a request to transport goods from one location to any other. In SAP Transportation Management (TM), that request takes a specific form, depending on who you are and where the request comes from.

If you are a logistics service company (LSP), a freight forwarder, or a provider who moves items for customers, the request usually arrives as a forwarding order. If you’re a shipper, a producer, or a retailer who moves its very own items, the request comes out of your own commercial enterprise documents, which include purchase orders, buy orders, and deliveries. In SAP TM, those emerge as order-based transportation necessities (OTRs) and transport-based transportation necessities (DTRs).

Learners often mix those up, and interviewers love to check the difference. This guide explains how forwarding orders are created, how SAP TM handles order-primarily based and shipping-based transportation necessities, how they vary, and where each fits within the system.

A brief note: SAP TM has changed throughout releases and licensing fashions. Screens, app names, and customizing paths vary by version. Treat this guide as a conceptual foundation and confirm information in the SAP Help Portal for your release.

The Big Picture: What Is a Transportation Requirement?

In SAP TM, a transportation requirement is a document that tells the system what is to be transported. It is the place to begin for planning. The 3 principal sorts are:

Transportation requirementTypical sourceTypical userForwarding orderCustomer’s transport request to an LSP Logistics provider providerOrder-based transportation requirement Sales order, buy order, or stock delivery orderShipperDelivery-based transportation requirement Outbound or inbound delivery Shipper.

All of them serve one purpose: to feed the planning process. After they are stored and checked, the system converts them into freight documents, the smallest units that TM plans and executes. Freight devices are then grouped into freight orders or freight bookings assigned to companies, and in the end settled and invoiced.

The glide looks like this:

• A transportation requirement is created (forwarding order, OTR, or DTR)

• Freight gadgets are built from it

• Freight devices are delivered into freight orders or bookings

• Carriers are selected and tendered

• Transportation is carried out and tracked

• Charges are calculated and settled

Keeping this chain in mind makes every topic below less complicated.

Part 1: What Is a Forwarding Order?

A forwarding order is the document an LSP uses to capture a client’s request for transportation offerings. It states what is being moved, where it is going, under which terms, and at what rate.

A forwarding order commonly holds:

• Business companions: the ordering party, shipper, consignee, and other parties involved

• Locations: supply and delivery locations, and sometimes pickup and delivery addresses

• Dates and times: requested pickup and shipping windows

• Items: the products, programs, bins, or products being moved, with portions, weights, and volumes

• Transportation info: mode of shipping, transport kind, movement type, service degree, and Incoterms

• Stages: pre-carriage, primary carriage, and on-carriage legs, where relevant

• Charges: calculated freight and provider prices; the LSP payments to the customer

• Statuses and documents: processing reports, output files, and connected files

Because the LSP sells transportation as a carrier, the forwarding order works like a sales order for freight. It captures the industrial agreement with the customer, and it also drives the operational making plans behind the curtain.

Forwarding Orders vs. Forwarding Quotations

Some LSPs first send a forwarding citation with a price and terms. When the customer accepts, the quotation may be converted into a forwarding order, which avoids re-entering data and maintains the quoted phrases regularly.

Part 2: How Are Forwarding Orders Created in SAP TM?

Forwarding orders can enter the system in numerous ways. The proper method depends on how your customers communicate with you.

Method 1: Manual Creation

A customer service agent or order supervisor creates the order directly in SAP TM, typically through the Fiori launchpad or the SAP GUI-based totally interface, depending on your launch. This is common when customers name or email their requests.

Typical steps:

• Choose the forwarding order type. The kind controls the conduct and defaults of the order, along with which item types are allowed, how freight devices are constructed, and how the order is processed. Types are configured in customizing.

• Enter enterprise companions. Add the ordering celebration, shipper, and consignee. Master statistics for those come from the commercial enterprise association setup.

• Enter source and destination. Locations are picked from location master records or entered as addresses.

• Set dates. Enter pickup and shipping dates or time home windows.

• Add objects. Choose the item kind, which includes a product object, a package, or a container, and enter portions, weights, and volumes. Dangerous goods records and handling requirements may be brought in as needed.

• Set transportation terms. Define the transportation mode, transport kind, carrier stage, movement type, and Incoterms.

• Review ranges and defaults. The machine may derive levels, mode, or other values robotically from configuration.

• Calculate prices. SAP TM determines the applicable settlement and price tables, then calculates the charge to the customer.

• Check and keep. The device runs consistency checks. If the order is complete and valid, it’s then stored and can be released for planning.

Method 2: Creating from a Forwarding Quotation

If the purchaser approved a quotation, the planner creates the order with the aid of copying from it. This carries over the agreed events, places, gadgets, and expenses, reducing errors and saving time.

Method 3: Creating from a Template or via Copying

For clients who ship the same lanes repeatedly, users can replicate a current order or use a template. Only the converting information, along with dates and portions, needs updating.

Method 4: Electronic Creation via Integration

Larger customers frequently send shipping requests electronically, for example through EDI messages, internet services, or a patron portal. SAP TM can get hold of these and create forwarding orders routinely, using mappings that convert incoming facts into the order structure. Any errors are located in a queue for the order crew to correct, so nothing is misplaced.

What Happens Behind the Scenes When You Save

Saving a forwarding order sets numerous processes in motion:

• Determination and defaulting. The system fills in values together with transportation mode, transport type, and levels based entirely on configuration.

• Consistency tests. It validates that required information is provided and that the order makes sense.

• Charge calculation. The system retrieves the relevant freight settlement and charge tables and computes the rate.

• Freight unit building. Using freight unit constructing guidelines (FUBRs), the machine creates freight units from the order items. The regulations determine how items are grouped and cut up.

• Status updates. The order’s processing and planning statuses are updated as work moves forward.

The freight unit step deserves attention. If the FUBR is installed poorly, planning becomes messy. For instance, programs that ought to ship together may be cut up, or unrelated objects may be grouped collectively.

Part 3: The Configuration That Makes Forwarding Orders Work

A forwarding order can not behave effectively without supporting setup. Learners should be familiar with those regions.

Forwarding order kinds. These outline commercial enterprise conduct: variety tiers, allowed object sorts, default values, and processing steps.

Item sorts. These define what sort of thing is being moved, such as a product, container, package deal, or provider.

Freight unit constructing guidelines. They manage how freight items are built from order objects.

Incoterms, delivery sorts, movement types, and carrier degrees. These affect tiers, mode dedication, and pricing.

Organizational units. Sales and planning organizations determine who is responsible for the order and which agreements and prices apply.

Master facts. Business partners, locations, transportation lanes, zones, and products need to exist and be correct.

Charge control setup. Forwarding agreements, charge tables, calculation profiles, and rate sorts decide pricing.

Output management. Documents, together with order confirmations and shipping files, are composed of configured output profiles.

Strong education covers each of the front-end order access and this configuration, due to the fact that actual tasks spend most of their effort on the setup.

Part 4: How Does SAP TM Handle Order-Based Requirements?

Now to the shipper facet of the story. In many S/4HANA initiatives, the organisation isn’t always an LSP. It sells and buys physical goods and wishes to move them. Here, the shipping request comes from documents that already exist inside the ERP side of the machine.

An order-based transportation requirement (OTR) is made out of an order file:

• A sales order, for outbound consumer shipments

• A purchase order, for inbound dealer shipments

• An inventory shipping order, for transfers among flora

Why Use the Order-Based Approach?

The essential gain is early visibility and early planning. Transportation can be planned before deliveries are created. A logistics group can see that a big order is coming, plan potential issues, and even e-book carriers earlier. This fits corporations with lengthy lead times, which include ocean freight, wherein carrier space ought to be reserved well before the goods are ready.

How the Order-Based Flow Works

• A sales or purchase order is created in the S/4HANA logistics software.

• The order is checked for transportation relevance. In customizing, document sorts and item categories are flagged as relevant for transportation planning. Only applicable documents pass on to TM.

• An OTR is created. In an embedded S/4HANA TM setup, this takes place on the same device, using integration good judgment as opposed to a separate machine connection. In older setups with a standalone TM device, the switch was passed off across systems.

• The OTR is stored, and freight gadgets are built. The FUBR corporations the gadgets into freight units for making plans.

• Planning proceeds. Planners use the freight units to create freight orders, pick out carriers, and schedule shipping.

• Deliveries are created later. The transport items are then matched to the existing freight units so that the transportation plan is carried through to execution, in preference to being redone.

• Changes drift through. If the order amount, date, or vicinity is adjusted, the OTR and freight units are replaced, and the gadget might also flag affected plans.

Points to Watch with OTRs

• Order adjustments can trigger replanning, so teams need clear policies for what occurs whilst plans are already tendered or in execution.

• The shipping must be connected effectively to present freight devices, or planning can emerge as duplicated.

• Not every order has to visit TM, so relevance settings count.

Part 5: How Does SAP TM Handle Delivery-Based Requirements?

A shipping-primarily based transportation requirement (DTR) is made from a transport file:

• An outbound transport for purchaser shipments

• An inbound shipping for supplier shipments

Why Use the Delivery-Based Approach?

Deliveries are in the direction of the bodily truth. By the time a delivery exists, quantities, weights, dates, and frequently packing are more accurate. This makes planning more accurate and reduces later modifications. It fits agencies with quick lead times and strong shipping approaches, in which transportation planning needs to begin while items are nearly ready to ship.

How the Delivery-Based Flow Works

• A transport is created from a sales order or purchase order, or immediately in some cases.

• The delivery is checked for transportation relevance, again through customizing.

• A DTR is created in TM, and the transport records are copied in: gadgets, quantities, weights, volumes, locations, and dates.

• Freight units are constructed from the DTR using freight unit building guidelines.

• Planning and execution are observed. Freight orders are created, providers are assigned, and shipments are processed.

• Execution feeds back to transport. Updates, including loading, departure, and delivery confirmation, are fed back so the logistics documents stay aligned. Goods trouble and other execution steps continue within the ERP side.

• Invoicing and agreement follow. Freight costs may be settled with the provider and, where applicable, tied back to the logistics documents.

Points to Watch with DTRs

• Planning starts evolved later, so there may be much less time to optimize or book scarce potential.

• Delivery changes, which include splits or modifications, want to replace the requirement and freight units cleanly.

• Delivery relevance ought to be configured cautiously, or deliveries won’t attain TM at all.

  Part 6: Order-Based vs. Delivery-Based Requirements

  Choosing between the two approaches is a design decision, and projects discuss it early. Here is a side-by-side view

Part 7: Forwarding Orders vs. OTRs and DTRs

Now we will answer the query in the title. Are forwarding orders, OTRs, and DTRs options for each other? Not exactly. They serve distinct enterprise roles.

Forwarding order: created via an LSP to capture a client’s transport request. It consists of business statistics and costs to be billed to the consumer. Its source is the consumer, not an ERP order.

OTR and DTR: comprised of the shipper’s very own ERP files. They deliver the logistics wishes of a business enterprise moving its very own goods, and the price side is commonly about freight paid to carriers.

Some points of similarity:

• All 3 build freight units and then plan.

• All three rely upon top master information.

• All three hyperlink to freight orders, execution, and settlement.

Some points of difference:

• Forwarding orders help patrons deal with rate calculation and billing (forwarding settlement), while OTRs and DTRs specifically guide provider-facing fees (freight settlement).

• Forwarding orders are created directly in TM, at the same time as OTRs and DTRs originate in ERP documents.

• Forwarding orders are principal to LSP tactics, even as OTRs and DTRs are significant to shipper tactics.

In interviews, being capable of providing an explanation for this truly is a strong sign that you understand SAP TM beyond display navigation.

Part 8: What Happens After the Requirement Is Created?

Whichever requirement type you begin with, the subsequent steps appear similar.

Freight Unit Building

The gadget creates freight units from the requirement. A freight unit represents an amount of goods that should be transported collectively on the same route and time frame. The FUBR decides how objects are grouped, primarily based on standards including source, destination, dates, mode, and product characteristics.

Planning

Planners use the transportation cockpit or automated planning to assign freight devices to freight orders. They don’t forget about capacity, value, schedules, and constraints. Optimization may be implemented, and planning can be guided, automatic, or a mixture.

Carrier Selection and Tendering

The gadget can select vendors based entirely on rules, charges, and priorities, and may send tenders electronically. Carrier responses feed back into the plan.

Execution and Tracking

Freight orders are performed with steps including loading, departure, arrival, and unloading. Events may be tracked and compared to the plan, and exceptions may be flagged.

Charge Calculation and Settlement

For forwarding orders, the device calculates patron prices and supports forwarding settlement to invoice the patron. For all situations, it calculates carrier charges on freight orders and helps the freight agreement pay for the service. Documents are passed to finance for accounting.

Part 9: Common Challenges and How to Handle Them

Real tasks hit predictable issues. Knowing them makes you more valuable.

Missing or wrong master data. Locations, business partners, or lanes may be incomplete, causing errors throughout creation or planning. Fix the statistics promptly.

Wrong transportation relevance settings. If record types are not flagged effectively, orders or deliveries never reach TM, or the incorrect ones do.

Poor freight unit constructing rules. Badly designed rules result in unrealistic or fragmented planning. Test with sensible eventualities.

Frequent order changes. In an order-primarily based technique, modifications cascade into replanning. Define clean trade dealing with policies.

Duplicate planning. If order-based freight units aren’t matched nicely with deliveries, the same items may be planned two times.

Charge calculation mistakes. Missing agreements, fee tables, or wrong calculation profiles can produce incorrect or zero expenses.

Integration failures. Electronic order intake can fail because of mapping or record errors. Monitoring and blunder queues are critical.

Unclear ownership. Teams want clear responsibility for order creation, planning, execution, and settlement.

Part 10: Skills You Need to Learn

If you are preparing for a function in SAP TM, focus on those areas.

• Transportation basics: modes, Incoterms, degrees, and shipping standards

• TM grasp statistics: business companions, locations, zones, lanes, sources, and calendars

• Forwarding order management: types, item types, creation methods, and statuses

• Order-based and transport-based integration: relevance, switching, matching, and alternative handling

• Freight unit construction regulations: design and testing

• Planning: the transportation cockpit, optimization principles, and constraints

• Charge management: agreements, charge tables, calculation, and agreement

• Execution and event monitoring

• Integration with S/4HANA SD, MM, and logistics execution, and with EWM or Event Management where relevant

• Fiori apps and analytics for planners and order managers

A solid online direction should give you hands-on right of entry to a device wherein you may create forwarding orders, trigger OTRs and DTRs from sales and shipping files, and watch how freight units are constructed.

Part 11: Practice Exercises

Try those on a training machine to reinforce the concepts.

• Create a forwarding order for a simple avenue cargo and look at the tiers, items, and calculated fees.

• Create a forwarding quotation, be given it, and convert it into an order.

• Change the freight unit building rule and observe how freight units alternate for the identical order.

• Create an income order flagged as transportation-applicable and verify that an OTR is created.

• Create the shipping for that income order and look at how the shipping relates to present freight devices.

• Repeat the procedure using a delivery-based total setup and evaluate while planning becomes feasible.

• Change the amount or date on an order and be aware of how the requirement and freight devices are replaced.

• Plan the freight devices right into a freight order, pick a service, and observe the system to settlement.

After each exercise, ask: Which record was created? Which statistics got here from where? What could go wrong if these statistics were missing?

Part 12: How Online Training Helps

SAP TM has many moving components, and self-learning from documentation can feel overwhelming. Good online schooling helps in several ways.

• Structure: a logical course from transportation fundamentals to advanced planning and settlement

• Live demonstrations: seeing the identical method from forwarding order to settlement clarifies how the pieces connect

• System get right of entry to: hands-on practice is important

• Real eventualities: LSP and shipper case research make the differences concrete

• Doubt explanation: live periods permit you to ask why, no longer simply how

• Recordings: beneficial for revision

• Interview guidance: usually requested questions, together with forwarding order vs. OTR/DTR, are worth training

When evaluating providers, test for a current syllabus, running shoes with implementation experience, actual device access, and honest claims. No institute can assure a process.

13.Why ProExcellency Is the No.1 

Here’s why ProExcellency Solutions is continuously in :

• Certified Trainers with 10+ years of experience in

• one hundred % Practical-Oriented Learning

• Flexible Online & Weekend Batches

• Training Projects and Case Studies

• Affordable Fee Structure

• Placement & Resume Support

• High Success Rate in Certification Exam

14. Frequently Asked Questions

Is a forwarding order similar to an income order?

No. A forwarding order captures a transport carrier request in an LSP situation. A sales order sells items. In a shipper scenario, a sales order can create an order-based transportation requirement; however, it isn’t itself a forwarding order.

Can a shipper use forwarding orders?

Some companies with internal logistics carrier organizations or intercompany models use forwarding-order-style procedures; however, the normal shipper state of affairs uses OTRs and DTRs. The proper approach depends on the commercial enterprise version and licensing, so confirm this on your challenge.

Do I have to select between order-based planning and transport-based planning?

Not necessarily. Many corporations use each, depending on the transportation mode, lead time, or business unit.

What is a freight unit?

It is the planning unit in SAP TM, constituted of a transportation requirement. Freight devices are assigned to freight orders or bookings.

Which is higher, order-primarily based or shipping-primarily based?

Neither is universally better. Order-based totally fits early planning and potential bookings. Delivery-based fits stable strategies with more positive data.

How are expenses calculated on a forwarding order?

The machine finds the applicable forwarding settlement and price tables, applies calculation logic, and produces fees that may be settled through forwarding settlement.

Do freshers need SAP SD or MM understanding to analyze TM?

It facilitates this, considering that order-based and delivery-based integration makes use of sales, purchasing, and shipping documents. Freshers can learn the fundamentals through schooling.

Is SAP TM in S/4HANA different from standalone SAP TM?

Yes, in structure and packaging. Embedded TM in S/4HANA runs inside the same system as the ERP logistics, whereas older setups used a separate system. Features and licensing fluctuate via release, so verify with SAP documentation.

Final Thoughts

So, how are forwarding orders created in SAP TM, and how does the system take care of order-primarily and transport-primarily necessities?

Forwarding orders are created by using logistics carrier vendors to capture consumer transport requests. They can be entered manually, copied from quotations or templates, or obtained electronically. On saving, the system applies defaults, runs assessments, calculates charges, and builds freight gadgets through freight unit constructing policies.

Order-based and shipping-based requirements serve shippers moving their own goods. OTRs come from income, buy, and stock transport orders and enable early planning. DTRs come from deliveries and offer more positive statistics toward shipment. Both feed the same freight unit and planning method, and many groups use them collectively.

The key insight is that these are exclusive factors in the same transportation technique. If you can explain who uses each one, where the facts come from, when planning starts, and how the whole thing flows via freight devices, planning, execution, and settlement, you grasp the coronary heart of SAP TM.

Blog Written By C.Rojarani