Show TOC

Function documentationIntegration of Freight Orders (TM) in Shipping and Receiving

 

Shipping and Receiving offers features that integrate SAP Extended Warehouse Management (SAP EWM) with the Freight Order Management component of SAP Transportation Management (SAP TM). With this integration, you can control and monitor the entire transportation process from the planning stage to the goods receipt at the customer location or your own plant.

Freight order data in transportation management and vehicle or transportation unit (TU) data in SAP EWM can be transferred between SAP TM and SAP EWM using enterprise services. This communication can be realized either via SAP NetWeaver Process Integration or using point-to-point communication (Web Services Reliable Messaging).

If the transportation planning in SAP TM is based on orders and deliveries that are created in an SAP ERP system, the delivery execution information is communicated from SAP EWM to SAP TM via SAP ERP to update the corresponding transportation requirements in SAP TM. The execution information in the freight orders, however, is based solely on the data communicated directly by SAP EWM.

Note Note

For information about the integration of Transit Warehousing in SAP EWM with SAP TM, see, Integration of Transit Warehousing with SAP TM.

End of the note.

Prerequisites

  • You have set up the XI communication between SAP TM and SAP EWM for integration scenario TM_EWMLoadingAppointmentIntegration.

    As an alternative, you have set up an integration scenario in transaction SOAMANAGER for the point-to-point communication between SAP TM and SAP EWM for the following service groups:

    • /SCWM/SRVG_TM_SR (SAP EWM)

    • /SCMTMS/TOR_LDG_APPT_RQ (SAP TM)

    For more information, see SAP Note 1978857Information published on SAP site

  • You have configured the Document Creation Relevance of the freight order type in SAP TM as relevant for SAP EWM. In Customizing for Transportation Management, choose Start of the navigation path Freight Order Management Next navigation step Freight Order Next navigation step Define Freight Order Types End of the navigation path.

  • You have assigned a packaging material to the vehicle resources used in EWM-relevant freight orders in SAP TM. From the SAP TM application in NetWeaver Business Client, choose Start of the navigation path Master Data Next navigation step Resources Next navigation step Define Resource End of the navigation path.

  • You have assigned a packaging material to the equipment types used in EWM-relevant freight orders in SAP TM. In Customizing for Transportation Management, choose Start of the navigation path Master Data Next navigation step Resources Next navigation step Define Equipment Groups and Equipment Types End of the navigation path.

  • You have maintained the packaging material types used for shipping handling units (HUs) in SAP EWM as package type code in SAP TM. This is also true for the packaging material types of sub-HUs.

  • You have created a link in SAP EWM between the means of transport of the SAP TM freight order and the packaging material derived from the SAP TM vehicle resource or equipment type. On the SAP Easy Access screen, choose Start of the navigation path Extended Warehouse Management Next navigation step Settings Next navigation step Shipping and Receiving Next navigation step Link Between Packaging Material (TU) and Means of Transport End of the navigation path.

  • The PPF actions /SCWM/SR_SEND_TU_LDAP_NOTI (for TUs) and /SCWM/SR_SEND_VEH_LDAP_NOTI (for vehicles) are active in the action profile assigned to the TU, to the vehicle, or to both in SAP EWM.

  • If you enter seals information in SAP TM or in SAP EWM, you have maintained party role codes in Customizing for Extended Warehouse Management under Start of the navigation path Interfaces Next navigation step TM Integration Next navigation step Define Party Role Codes End of the navigation path.

Features

The Shipping and Receiving part of SAP EWM offers you the following features:

  • Staging area and door determination contains the following transportation-relevant attributes:

    • For inbound processing:

      • Carrier

      • Means of transport

      • HU type of packaging material

    • For outbound processing:

      • Carrier

      • Ship-to party

      • Means of transport

      • HU type of packaging material

  • The system displays the following data:

    • Transportation planning type, for example, for TUs, vehicles, and deliveries, indicating which transportation planning process you use

    • Transportation planning system in the case of transportation planning in SAP TM

    • Corresponding SAP TM freight order number, for example, for TUs, vehicles, and deliveries

    • Origin of route schedule for TUs, allowing a distinction between regular transports and ad hoc transports

  • The transportation planning takes place in SAP TM, where freight orders are created. Once the item status of a freight order is set to Cargo Ready for Loading, a TransportationOrderLoadingAppointmentRequest message is automatically sent to SAP EWM. Based on the freight order information contained in the TransportationOrderLoadingAppointmentRequest message, the SAP EWM application automatically creates TU activities and vehicle activities and assigns deliveries or delivery items to them. Based on the freight order item structure in SAP TM, the system creates TU activities and vehicle activities in SAP EWM in the following way:

    • An active vehicle resource is created as a vehicle in SAP EWM

    • Active vehicle resources and passive vehicle resources are created as transportation units in SAP EWM if they directly contain cargo.

    • Containers are created as TU containers in SAP EWM

      Caution Caution

      Handling of containers or other TU resources from SAP TM is not supported in SAP EWM in standard warehousing. It is only supported in transit warehousing.

      End of the caution.
  • SAP TM uses request message TransportationOrderLoadingAppointmentRequest to transfer updates to freight orders automatically to SAP EWM, as follows:

    • In inbound processes, freight documents can be updated until the TU arrives at the checkpoint.

      Freight documents cannot be automatically updated once the TU arrives at the checkpoint to avoid overwriting manual updates entered in SAP EWM.

    • In outbound processes, updates are allowed even after the TU arrives at the checkpoint, to allow the last-minute loading of cargo. New delivery items can be added until the loading of the TU is completed. Delivery items can be updated until the loading of the TU has begun. TUs and vehicles can be updated until the TU or vehicle arrives at the checkpoint.

    • The deletion of a freight document in SAP TM can be transferred to SAP EWM until the TU arrives at the checkpoint.

  • When a vehicle arrives, SAP EWM notifies SAP TM of the arrival at checkpoint by sending a TransportationOrderLoadingAppointmentNotification message to SAP TM.

  • In outbound processes, the system notifies SAP TM about the execution of the plan in SAP EWM by sending a TransportationOrderLoadingAppointmentNotification message to SAP TM after the system has set the Departure from Checkpoint status of the TU. The message contains delivery information and handling unit information. Delivery information is used by the system to update the product items, HU information to create packaging items in the freight order automatically.

    Caution Caution

    A reversal of the Departure from Checkpoint status is not supported in outbound processes.

    End of the caution.
  • In inbound processes, the system notifies SAP TM about the execution of the plan in SAP EWM by sending a TransportationOrderLoadingAppointmentNotification message to SAP TM after the system has set the Departure from Checkpoint status of the TU. The message does not include delivery information and handling unit information, as you can post or correct the goods receipt quantities at a later point in time.

  • When you delete a TU in SAP EWM that has been created as a replica of an SAP TM freight order, the deletion is communicated to SAP TM with a TransportationOrderLoadingAppointmentNotification message.

  • You can use the SAP TM freight order number as external TU number or external vehicle number.

The following restrictions apply:

  • Cross-delivery handling units are not supported in an SAP TM freight order. To prevent the creation of such handling units in SAP EWM, you can either use the Order Combination indicator in the SAP ERP customer master record or implement BAdI /SCWM/EX_CORE_CONS in SAP EWM (an example implementation is provided by SAP to mitigate this restriction).

  • Transportation Management in SAP EWM cannot be used in combination with SAP TM.

  • Direct communication between SAP TM and SAP EWM is not supported for transportation planning in SAP EWM (TUs and vehicles created manually in SAP EWM). For this purpose, you must use the transportation integration via SAP ERP shipments.

  • If you assign delivery items of the same SAP ERP delivery to different freight orders in SAP TM, the DBT status Blocked (Transp. Plan) of SAP EWM deliveries cannot be used. Make sure that the DBT status is inactive in the status profile assigned to the SAP EWM delivery.

  • Delivery items assigned to a freight order stop must be known in the SAP EWM warehouse receiving the loading appointment request.

  • Once the Departure from Checkpoint status is set for a vehicle or TU relevant for the SAP TM freight order integration, it cannot be reversed in an outbound process in standard warehousing. It is therefore recommended to post the goods issue and set the Departure from Checkpoint status as separate steps in SAP EWM, in order to be able to reverse the goods issue before departure from checkpoint.

  • Handling of containers or other transportation unit resources from SAP TM is not supported in SAP EWM in standard warehousing.