Show TOC

Background documentationPrerequisites for Transit Warehousing

 

You must make the following settings if you are working in Transit Warehousing:

Communication

You have set up the SAP Process Integration communication between SAP Transportation Management (SAP TM) and SAP Extended Warehouse Management (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)

  • /SCWM/SRVG_TM_TRA_URI (SAP EWM)

    This service group is used for navigating from SAP EWM user interfaces to SAP TM user interfaces.

For more information, see SAP Note 1978857Information published on SAP site and TM-EWM Integration.

Customizing Activities

  • You have made the prerequisite settings for Transit Warehousing in SAP TM.

    For more information, see SAP Library for SAP TM on SAP Help Portal at http://help.sap.com/tmInformation published on SAP site. In SAP Library, choose Start of the navigation path Integration Next navigation step Integration with SAP Extended Warehouse Management Next navigation step Transit Warehousing End of the navigation path.

  • You have defined new document types and item types for inbound deliveries in Customizing for Extended Warehouse Management under Start of the navigation path Goods Receipt Process Next navigation step Inbound Delivery Next navigation step Manual Settings Next navigation step Define Document Types for Inbound Delivery Process End of the navigation path and Start of the navigation path Define Item Types for Inbound Delivery Process End of the navigation path.

    The item category of the item type must be CGO (Transit Item). The profiles assigned to the document types and item types must be specific to transit warehousing. For example, the process profile assigned to the document type must have Communication to ERP set to No ERP Involved and the action profile must contain action /SCWM/PDI_NOTIFY_TM_DEL.

  • You have defined new document types and item types for outbound delivery orders and outbound deliveries in Customizing for Extended Warehouse Management under Start of the navigation path Goods Issue Process Next navigation step Outbound Delivery Next navigation step Manual Settings Next navigation step Define Document Types for Outbound Delivery Process End of the navigation path and Start of the navigation path Define Item Types for Outbound Delivery Process End of the navigation path.

    The item category of the item type must be CGO (Transit Item). The profiles assigned to the document types and item types must be specific to transit warehousing. For example, the process profile assigned to the document type must have Communication to ERP set to No ERP Involved.

  • You have made the prerequisite settings for destination bin determination in transit warehouses (see Destination Storage Bin Determination in Transit Warehousing).

  • You have made the following settings in Customizing for Extended Warehouse Management under Start of the navigation path Master Data Next navigation step Define Warehouse Number Control End of the navigation path:

    • You have assigned a transit handling unit (HU) procedure and a HU container procedure to your warehouse.

    • You have assigned a warehouse process type to your warehouse in the WPT to HUC Load (Warehouse Process Type to Move Transit HU to Loading Area) field.

    • You have defined a default discrepancy code so that SAP EWM can communicate to SAP TM about HUs to be clarified in an inbound process.

  • You have mapped the freight order settings from SAP Transportation Management (SAP TM) to the document types for the warehouse request in Customizing for Extended Warehouse Managementunder Start of the navigation path Interfaces Next navigation step TM Integration Next navigation step Map Freight Order to Delivery Document Type for Transit Warehouse End of the navigation path.

  • You have mapped the freight order settings from SAP TM to the item types for the warehouse request in Customizing for Extended Warehouse Management under Start of the navigation path Interfaces Next navigation step TM Integration Next navigation step Map Freight Order to Delivery Item Type for Transit Warehouse End of the navigation path.

  • You have activated actions /SCWM/SR_SEND_TU_LDAP_NOTI, /SCWM/SR_TU_CREATE_STAGING_WT, and /SCWM/SR_TU_PRINT_HU_LABEL in the action profile used for transportation units (TUs) in Customizing for Extended Warehouse Management under Start of the navigation path Cross-Process Settings Next navigation step Shipping and Receiving Next navigation step Message Processing Next navigation step Define Action Profiles for Transportation Units End of the navigation path.

  • You have activated action /SCWM/SR_SEND_VEH_LDAP_NOTI in the action profile used for vehicles in Customizing for Extended Warehouse Management under Start of the navigation path Cross-Process Settings Next navigation step Shipping and Receiving Next navigation step Message Processing Next navigation step Define Action Profiles for Vehicles End of the navigation path.

  • You have activated actions /SCWM/HU_TW_NOTIFY_TM_IN and /SCWM/HU_TW_NOTIFY_TM_OUT in action profile /SCWM/HU_TW used for HUs in Customizing for Extended Warehouse Management under Start of the navigation path Cross-Process Settings Next navigation step Handling Units Next navigation step Basics Next navigation step Print Next navigation step Define PPF Action Profiles End of the navigation path.

Note Note

This is a list of just the main Customizing settings that must be made as a prerequisite to using Transit Warehousing. For information about more settings, see SAP Note 2159320Information published on SAP site.

End of the note.
Business Add-Ins (BAdIs)

The following BAdIs are available in Customizing for Extended Warehouse Management under Start of the navigation path Business Add-Ins (BAdIs) for Extended Warehouse Management End of the navigation path:

  • If you want to determine a consolidation group for transit HUs that are to be moved, you must use BAdI: Determination of Consolidation Group for Transit Handling Units under Start of the navigation path Goods Receipt Process Next navigation step Strategies Next navigation step Putaway Strategies for Transit Warehouse End of the navigation path.

  • If you want to replace the search sequence determination for the destination bin, which is based on condition technique, by a different logic without calling the standard logic, you must use BAdI: Determination of Destination for Transit Warehouse under Start of the navigation path Goods Receipt Process Next navigation step Strategies Next navigation step Putaway Strategies for Transit Warehouse End of the navigation path.

  • If you want to change and enrich values of the communication structure that is used when determining a destination storage bin, you must use BAdI: Enrichment of Request Data for Transit Warehouse under Start of the navigation path Goods Receipt Process Next navigation step Strategies Next navigation step Putaway Strategies for Transit Warehouse End of the navigation path.

  • If you want to determine the condition schema for the destination storage bin determination, you must use BAdI: Adjustment of Condition Determination Procedure under Start of the navigation path Goods Receipt Process Next navigation step Strategies Next navigation step Putaway Strategies for Transit Warehouse End of the navigation path.

  • If you want to transfer customer-specific attributes from customer-specific fields into customer-specific fields of a TU, you must use BAdI: TransportationOrderLoadingAppointmentRequest_IN under Start of the navigation path Interfaces Next navigation step Enterprise Services Next navigation step TM-EWM Integration Next navigation step Enhancements to TM-EWM Integration End of the navigation path.

  • If you want to transfer customer-specific attributes from TUs, you must use BAdI: Delivery Creation - TransportationOrderLoadingAppointmentRequest_IN under Start of the navigation path Interfaces Next navigation step Enterprise Services Next navigation step TM-EWM Integration Next navigation step Enhancements to TM-EWM Integration End of the navigation path.

  • If you want to overwrite the result of the standard document type and item type determination for inbound deliveries and outbound delivery orders created from request message TransportationOrderLoadingAppointmentRequest, you must use BAdI: Delivery Creation - TransportationOrderLoadingAppointmentRequest_IN under Start of the navigation path Interfaces Next navigation step Enterprise Services Next navigation step TM-EWM Integration Next navigation step Enhancements to TM-EWM Integration End of the navigation path.

  • If you want to invoke the synchronous web service GetTransportationDocumentURI before requesting a Uniform Resource Identifier (URI) for an SAP TM document from the connected SAP TM system, you must use BAdI: Get URI of Transportation Document under Start of the navigation path Interfaces Next navigation step Enterprise Services Next navigation step TM-EWM Integration Next navigation step Enhancements to TM-EWM Integration End of the navigation path.

  • If you want to connect a physical device for weighing and measuring HUs to SAP Extended Warehouse Management (SAP EWM) and access these values from the device, you must use BAdI: Automatic Weighing and Measuring under Start of the navigation path Mobile Data Entry End of the navigation path.

  • If you want to change the way the system checks the weight, volume, and measures of HUs in the radio frequency transaction Receiving by TU/Door in the inbound process, you must use BAdI: RF: HU Checks for Receiving of HUs in Transit Warehousing under Start of the navigation path Mobile Data Entry End of the navigation path.

  • If you want to change the way dangerous goods data is displayed and used in certain user interfaces and processes, you must use BAdI: Aggregation and Prioritization of Dangerous Goods Data under Start of the navigation path Cross-Process Settings Next navigation step Delivery - Warehouse Request End of the navigation path.

Master Data
Master Data for Standard Warehousing

You have set up the master data required for standard warehousing that is also relevant for transit warehousing, for example:

  • Storage bins (see Storage Bin)

  • Resources (see Resource)

  • Work centers (see Work Center)

  • Vehicles (see Vehicle)

  • TUs (see Transportation Unit)

  • Packaging material

    Packaging materials are required for the following items in SAP EWM:

    • Transit HUs

    • HU containers

    • TU containers

    • TUs

    • Planned vehicles (outbound only)

    For more information, see Integration of Transit Warehousing with SAP TM.

    Note that you can create packaging materials in SAP ERP and replicate them to SAP EWM using Core Interface (CIF).

    Note Note

    Transit Warehousing does not use product master data, except for packaging materials, because the content of the HUs is not relevant in a transit warehouse.

    End of the note.

    Recommendation Recommendation

    If the packaging materials are also relevant for SAP TM, create them in SAP ERP and replicate them to SAP EWM and SAP TM. If the packaging materials are not relevant for SAP TM, create them in SAP EWM only.

    End of the recommendation.

  • Business partners and locations

    • Shippers, consignees, and carriers

      In SAP ERP, you have created vendors to represent carriers and customers to represent shippers and consignees, and replicated vendors and customers to SAP EWM as business partners and locations using CIF. Note that in a standard warehouse, a shipper is a business partner with the business partner role Vendor. However, in a transit warehouse, a shipper is a business partner with the business partner role Ship-To Party.

    • Transportation network

      In SAP TM, you have created locations to represent transit warehouses or other locations in the transportation network. You have then replicated the locations to SAP EWM using the report Send Business Partner and Locations for Transition Warehousing Process (/SCMTMS/BUPA_SEND_TRANS_WH). If the locations are assigned to business partners, the report also creates the business partners in SAP EWM.

More Information

Transit Warehousing