Figure 8: SAP Solutions for Transportation & Logistics – SAP Supply Chain Execution Architecture Outlook
An full SAP solution architecture for the transportation and logistics Industries as well as SCM execution would consist of the solutions above. SRM and CRM provide relationship management capabilities for partnering suppliers and customers. The solutions in this full SAP solution landscape are in general connected with these systems via SAP ERP. In some scenarios, SAP customers would like to integrate processes between the different solutions without using SAP ERP as a process step or system in between. In some cases, there are standard interfaces available, and in other cases, these integrated processes can be created on a project basis by using business process management (BPM) and service-oriented architecture (SOA) solutions in the SAP solution portfolio. TM in particular is designed with SOA and BPM in mind, to integrate flexibly with other SAP solutions, third-party systems,and legacy systems
Figure 9: Architecture Overview – for Full, End-to-End, Process Integration
Ortec is the recommended vendor for load optimization
The SAP solution architecture for most of the end-to-end scenarios available at the moment for SAP TM is shown in the graphic above. For many SAP customers who already have an SAP ERP system, SAP TM in combination with SAP Event Management and GIS integration provides a solid foundation to support transportation processes already integrated in existing ERP processes. SAP GTS and mobile solutions extend the transportation solution landscape by providing additional capabilities for compliance and mobility. In the solution architecture above, SAP Business Objects is not included, but transportation-specific content is available and ready for use.
Figure 10: SAP TM 8.0: Overview System Landscape
The graphic above shows the standard TM 8.0 landscape. TM 8.0 has to be installed and executed in its own instance. This instance includes the standard SAP NetWeaver components Process Integration (PI), TM Optimizer 8.0, Internet Graphics Service (IGS), and SAP Event Management 7.01.
The PI 7.0 interface provides the ability to exchange transportation data with SAP or non-SAP systems.
The IGS constitutes the infrastructure that enables an application such as the geographical information system (GIS) to display graphics in an Internet browser with a minimum of effort. IGS runs as part of the Application Server in SAP NetWeaver 7.0. The integrated IGS exists on every SAP Web AS machine and is started and stopped with SAP Web AS.
TM 8.0 can, optionally, interface with an SAP ERP system, an SAP Global Trade Services (GTS) system, and an external geographical information system (GIS).
The Core Interface (CIF) is used for master data replication between ERP/ECC and TM. PI is used for transactional data integration between ERP/ECC and TM, and the external GIS system can provide geographical mapping data for transportation routes. The IGS uses this data to show the image on the screen.
The SAP Event Management system can be deployed on either the TM 8.0 system, the SAP ERP system, or its own system.
TM 8.0 can also interface with Adobe Document Services to provide additional output functions such as Adobe Forms and printing.
There is also an interface between TM 8.0 and the SAP BW environment.
In the graphic above, the TM 8.0 system is shown with possible integration points with SCM applications. Some integration points are not yet available. For example, integration with the Extended Warehouse Management system is not available at this time.
Figure 11: SAP TM 8.0: Software Component Architecture
When installing a TM server, some components are prerequisites, also for upgrades and Support Package installations. You can find the available stack(s) for installation, upgrades, and Support Package installation on SAP Service Marketplace. SAP NetWeaver (NW), SAP Business Suite Foundation (BS_FND), and SCM Basis are required for every installation of an SCM application. When this is installed, certain deployment options are possible. For SAP TM, this means it can be deployed together with SAP Event Management (SCEMSRV) on one server, although this is not absolutely necessary. During post-installations steps, it is however mandatory to activate business functions for activating TM-specific capabilities on the SCM server. In SAP Event Management it is also mandatory to activate the business function “SCM_EM_TMCONTENT01”, otherwise transportation visibility scenarios are not available in the event manager. The SCM Basis component provides many functions in the area of master data and master data integration with SAP ERP via the Core Interface (CIF). This is also used for other SCM applications like APO and EWM, but there is a specific TM flavor to this master data. Most of the APO transactions will have TM specific Transaction code, with additional data for TM or APO specific data is removed.
For example, the products are not available in the transportation lanes of TM.
Figure 12: TM Business Functions in ECC
This screen shot shows the business functions that need to be activated for TM 8.0. In ECC there are three business functions that can be activated to trigger integration with TM. The business functions are:
• LOG_TM_ORD_INT (Order Integration – New: Ehp 605) – This business function allows your business to integrate purchase orders, stock transport orders, and sales orders with the TM system. This functionality allows new features to the various order types.
• LOG_TM_ORD_INT_TRQ (Invoice Integration – New: Ehp 604) – This business function allows your business to integrate purchase orders, stock transport orders, and sales orders with the TM system.
• LOG_TM_IV_INT (Basic Order Integration – New – Ehp 604) –This business function allows your business to create, enter, process, or display invoices that refer to documents in TM.
In addition to ECC, there are Business functions that need to be activated in the TM system as well. These enterprise business functions are:
• SCM_EHS_DG_CI_1 (EH&S Services: Dangerous goods Ehp 801)
• Most of the APO transactions will have TM specific Transaction code. These transacations will have additional data for TM or APO specific data has been removed.SCM_EM_HIGHVOL (EM Archiving and Web Interface Improvements Ehp 801) – Your business can use this feature in high volume processing and archiving.
• SCM_EM_TMCONTENT01 (EM, Visibility process for external TM systems Ehp 801) You can monitor different event handler types, for example, freight units and freight orders.
• SCM_SCMB_TM_FND1 (Foundation of External TM system Ehp 801) – This business function to transfer specific attributes of a customer and or vendor from ECC to a business partner in SCM Basis using the CIF.
• SCM_SCMB_TR_NETWORK (Enhanced Services for Transportation Network Ehp 801) – With this function you can improve the geographical services used in the Transportation network.