Show TOC

Function documentationCreation of Delivery Proposals Locate this document in the navigation structure

 

SAP Transportation Management (SAP TM) can propose inbound deliveries and outbound deliveries and send these proposals to SAP ERP to trigger the creation of deliveries.

Prerequisites

  • An order-based transportation requirement exists.

  • Freight units exist for the order-based transportation requirement.

  • The order-based transportation requirement is not blocked for delivery.

  • A delivery is expected for the order in the ERP system. This can be determined, for example, by the order type or shipping conditions.

  • If you want to use a selection profile to select the relevant input for the delivery proposal, you have defined a selection profile (see Selection Profile).

  • If you want to use a delivery profile during delivery creation, you have defined a delivery profile (see Delivery Profile).

  • If you want to send delivery proposals to SAP ERP from the freight order UI, you have assigned a delivery profile to the relevant freight order types. You do this in Customizing for Transportation Management under   Freight Order Management   Freight Order   Define Freight Order Types  .

When using the background report, a delivery proposal must not have already been made for the freight units. This includes freight units for which a delivery failed to be created.

Features

Background Report

The user can create delivery proposals for order-based transportation requirements by using a background function (program /SCMTMS/DLV_BATCH). The user can enter selection criteria or use selection profiles. In both cases, the user can also enter a delivery profile. The system selects the documents, creates the delivery proposals, and sends them automatically to SAP ERP.

If a freight unit has previously been used for a delivery proposal, but no delivery-based transportation requirement was ultimately created, the user cannot use the function to create a new delivery proposal for that freight unit. Instead, the user has to create the delivery proposal interactively in SAP NetWeaver Business Client.

For more information about the background function, see Creation of Deliveries in SAP ERP.

Interactive Delivery Creation

The user can create deliveries interactively as follows:

  • From the delivery creation UI in SAP NetWeaver Business Client under   ERP Logistics Integration   Delivery Creation   Create Deliveries in ERP  .

    The user specifies one or more profiles according to which the system selects and displays a list of business documents. The user then selects the relevant documents in the list and triggers delivery proposal creation. The user can review the delivery proposals before sending them to SAP ERP

  • From the following overviews:

    • Overview of freight orders or freight bookings in SAP NetWeaver Business Client under Freight Order Management.

    • Overview of order-based transportation requirements or order-based freight units in SAP NetWeaver Business Client under   ERP Logistics Integration   Worklist   Overview Transportation Requirements  .

    • Overview of order-based freight orders or order-based freight bookings in SAP NetWeaver Business Client under   ERP Logistics Integration   Worklist   Overview Freight Orders and Freight Bookings  .

    The user selects the relevant business documents in the overview and chooses the Create Deliveries in ERP pushbutton. The system displays a list of freight units related to the selected business documents. The user selects the relevant freight units and triggers delivery proposal creation. The user can review the delivery proposals before sending them to SAP ERP

  • From the Transportation Cockpit

    The user triggers delivery proposal creation for specific business documents after carrying out planning in the Transportation Cockpit. The user selects the business documents in the Transportation Cockpit and chooses the Create Delivery Proposals pushbutton. The system automatically creates and displays the delivery proposals. The user can review the delivery proposals before sending them to SAP ERP.

The user can also trigger the creation and sending of delivery proposals for a specific freight order by choosing   Follow Up   Send Delivery Proposals to ERP   in the freight order UI. The system automatically creates the delivery proposals and sends them to SAP ERP. In this case, the user cannot review the delivery proposals before they are sent to SAP ERP. Note that the system creates the delivery proposals according to the delivery profile assigned to the freight order type.

Source of Data

SAP TM collects data from the relevant documents as follows:

  • Dates

    SAP TM uses dates from the freight order or freight booking. If the order-based transportation requirement is not planned, that is no freight order or freight booking exists, then SAP TM uses dates from the freight units.

  • Quantities

    SAP TM uses quantities from the freight units.

  • ERP document references

    SAP TM retrieves document references (such as order document number) from the order-based transportation requirement.

Consolidation

If order-based transportation requirements have been planned, and freight orders or freight bookings exist for the transportation requirements, SAP TM uses only one freight order or one freight booking for each delivery proposal. That is, only freight units that belong to the same freight order or freight booking can be consolidated into a single delivery proposal. In this way, freight units from various order-based transportation requirements can be consolidated into a single delivery proposal if they belong to the same freight order or freight booking. If, however, freight units from a single order-based transportation requirement were distributed across multiple freight orders or freight bookings, then multiple deliveries are proposed for the freight units of this one order-based transportation requirement.

If order combination is not allowed for an order-based transportation requirement, SAP TM does not group freight units from this transportation requirement together with freight units from other order-based transportation requirements. If freight units for such order-based transportation requirements have been consolidated into the same freight order or freight booking during planning, SAP TM does not include them in the same delivery proposal, but instead creates multiple delivery proposals.

In addition, freight units can only be consolidated into the same delivery proposal if the following data is the same:

  • SAP ERP system from which the order was received

  • Source location

  • Destination location

  • Incoterms

  • Shipping conditions

  • SAP ERP document type, such as purchase order or sales order

  • Start stop (if planning has already been done)

  • Destination stop (if planning has already been done)

If an order-based transportation requirement has not been planned in SAP TM, and no freight order or freight booking exists, SAP TM can also create delivery proposals for the corresponding freight units. In this case, SAP TM creates delivery proposals according to the settings in the delivery profile. For more information about the delivery profile, see Delivery Profile.

Bill of Materials (BOMs)

Either a BOM header or BOM items can be goods-movement-relevant. If a BOM header is goods-movement relevant, SAP TM can, if necessary, distribute the quantity across multiple delivery proposals. If BOM items are delivery relevant, SAP TM expects a common delivery group for all items and does not distribute the items or their quantities across multiple delivery proposals.

Consumption of Schedule Lines in SAP ERP

The delivery proposal in SAP TM takes into account that SAP ERP consumes order schedule lines in chronological order. Therefore, SAP TM does not propose a delivery for a schedule line before another schedule line of the same order item that has an earlier delivery date has been used for a delivery proposal. If freight unit selection results in this situation, SAP TM excludes the affected freight units from the selection.

If an error occurs in SAP ERP when creating a delivery, then SAP ERP does not create deliveries that correspond to later schedule lines of the same order item, or the delivery is created but excludes the later schedule lines of that item.

Execution and Planning Blocks in SAP ERP

You can use the delivery profile to determine how, during delivery creation, the SAP TM system deals with objects that are blocked for planning or execution. You can choose either or both of the following options:

  • Exclude freight units or freight orders that are blocked for planning

  • Exclude freight units or freight orders that are blocked for execution

Note Note

Previously the system excluded all objects with the status “Blocked for Execution”, from delivery creation. The option to exclude objects with the status “Blocked for Planning” was not previously available.

End of the note.

The system considers freight units and freight orders to check whether they are blocked for planning or blocked for execution. If a freight order or its assigned freight units are blocked, the system – depending on the settings you have chosen in the delivery profile and depending on how you start delivery creation – prevents the user from creating a delivery. The system runs the check based only on the object (freight orders, bookings, transportation units, freight units) that you have selected as the starting point for creation of delivery proposals.

Example Example

A freight unit is assigned to a pre-carriage and a main-carriage freight order. The main-carriage freight order is blocked for execution, but the freight unit has no blocks. The delivery profile has been configured to exclude freight units or freight orders that are blocked for execution.

If you start creation of delivery proposals with the pre-carriage freight order, the system allows creation of deliveries.

If you start creation of delivery proposals with the main-carriage freight order, which is blocked for execution, the system prevents you from creating a delivery.

End of the example.

The system checks for blocks in freight orders only when you start delivery creation in a freight order context, for example, from the freight order POWL or the freight order UI or by using a freight order selection profile in the report “Create Deliveries in ERP”. Otherwise only the blocks in freight units are considered.

Delivery Proposals with Handover Locations

When the TM system receives handover locations from an ERP order, the TM system decides whether to build one or two stages and whether to designate one of them as “statistical”. If two stages are built and neither is designated “statistical”, then the logic of delivery creation is the same as that for a scenario without handover location. That means the original source and destination locations from the SAP ERP order are relevant for transportation planning and for the date-time fields in the delivery proposal. If two stages are built and one is designated as “statistical”, or only one stage is built, then the handover location becomes relevant for transportation planning and delivery proposal.

Example Example

For the OTRs of several purchase orders only the second stage has been built or two stages have been built and the first one is statistical. Then only the stage from handover location to the goods receiving plant is relevant for transportation planning and delivery proposal. If there are now several FUs originating from different locations but with the same handover location and destination location, and a FOR has been built for all these FUs, then a common delivery proposal may result for all these FUs.

End of the example.
Delivery Proposals with Freight Document Hierarchies

With transportation units, SAP TM provides a new three-tier hierarchy of freight documents. This can comprise a freight order on the highest level, transportation units on the middle level, and freight units on the lowest level. For two-tier hierarchies, the highest level can include freight orders, freight bookings and transportation units. On the lowest level, you can have freight units and automatically generated transportation units. In addition, automatically generated transportation units and automatically generated freight orders can represent a one level hierarchy.

You can create delivery proposals for each of these hierarchy types. If not explicitly stated, the term freight unit can also mean automatically generated freight order or automatically generated transportation unit, in order to represent objects on the lowest hierarchy level. In the same way the term freight order can also mean freight booking or transportation unit in order to represent objects on the highest hierarchy level.

More Information

For information about monitoring the delivery creation process, see Monitoring of Delivery Creation.