Topic Covered

1. Transportation Management Training Session
2. Logistics Payment Process Explanation
3. Transportation Event Tracking Systems
4. Business Warehouse and SAP Analytics
5. Global Trade System Impact Discussion
6. SAP Platform Migration Discussion
7. TM and ECC Integration Approaches
8. TM-EWM Integration Process Discussion
9. Freight Orders in TM Process
10. ECC 6.0 and TM Integration
11. SAP TM Integration Approaches

Summary

Transportation Management Training Session

Rohan J led a training session on transportation management (TM) processes, building on previous discussions about basic terms and TM evolution. He explained the six core TM pillars, focusing on the first four processes: order management, planning, execution/subcontracting, and settlement. The session detailed how orders are generated either manually or via EDI systems, followed by planning the movement method, executing shipments through carriers, and finally settling payments to carriers and customers.

Logistics Payment Process Explanation

Rohan explained the payment process for logistics operations, clarifying that DHL acts as a facilitator between Tata Steel and carriers, with two separate payment streams: customer payments and carrier payments. He described how payment terms can vary between entities and may involve delays, similar to services like Ola or Uber where payments are processed on a weekly or monthly basis rather than immediately. The discussion also covered how booking processes work differently for air and ocean transport compared to road and rail, as air and ocean require advance planning due to limited service providers, while road and rail operations can be more flexible.

Transportation Event Tracking Systems

Arun and Rohan J discussed event tracking in transportation management systems, explaining how it works similarly to e-commerce order tracking where various status updates are provided throughout the delivery process. They clarified that while transportation management handles order execution, event management systems are needed for tracking and tracing functionality. The discussion also covered carrier integration through carrier portals or SAP's Collaboration Portal/LBN, explaining that these simplified interfaces are necessary because carriers cannot use complex TM systems directly.

Business Warehouse and SAP Analytics

Rohan explained the purpose and functionality of Business Warehouse (BW) as a reporting tool that provides historical data for forecasting and generating dashboards, noting that it will likely be replaced by SAP Analytics Cloud (SAC) for real-time data analytics. He outlined the four segments of master data in TM: generic master data, transportation network, resource definition (vehicles), and charge management. The discussion included clarifications about SAP's carrier applications, with Rohan explaining that Collaboration Portal, LBN, and BN4L are all available carrier applications with cosmetic updates, though BN4L is the latest version.

Global Trade System Impact Discussion

Rohan J explained how Global Trade System (GTS) impacts international transportation, including customs clearances, compliance requirements, and tariff impacts on transportation costs. He discussed the business justification for why e-commerce platforms like Amazon don't implement live tracking maps, contrasting this with food delivery apps where real-time location tracking is essential for customer satisfaction. Rohan also explained the technical evolution from NetWeaver to Fiori platforms in SAP TM systems, noting that while the technical implementation changed, the functional experience remained similar for users.

SAP Platform Migration Discussion

Rohan explained that while SAP NetWeaver still exists, Fiori is now the recommended platform for accessing S4 applications, as it provides a unified interface for multiple modules rather than separate windows for different functions. He clarified that both NetWeaver and Fiori applications remain available, with Fiori offering more flexibility and integration with mobile devices. The discussion then shifted to explaining shipper scenarios, where transportation management is handled in-house rather than by third-party logistics providers, and how ECC and TM systems are integrated within a company's own ecosystem.

TM and ECC Integration Approaches

Rohan J explained two approaches for integrating TM and ECC systems: TM-driven and ECC-driven approaches. In the TM-driven approach, when a sales order is created in ECC, it triggers an OTR document in TM, which builds freight units for transportation planning and creates a delivery proposal before confirming with a DTR document. In the ECC-driven approach, the process skips the OTR and proposal steps, directly creating a delivery in ECC and then instructing TM to proceed with transportation using the DTR object. The team discussed how freight units can contain multiple items and how the PGI process confirms the actual number of units to be transported, validating the transportation planning.

TM-EWM Integration Process Discussion

Rohan explained the integration between TM and EWM systems, focusing on how outbound delivery orders (ODO) work as a cross-validation mechanism between the systems. He clarified that while TM uses freight orders and DTR for deliveries, EWM uses TUs as the main interaction object, with ODO serving as the document to validate and confirm details between the systems. The team discussed that both sales order-based and delivery order-based approaches are possible, with the choice depending on the solution architect's technical design decisions rather than being inherently better or worse. Nitin asked about the role of delivery proposals in the process, and Rohan confirmed they are used for transportation planning rather than actual planning execution.

Freight Orders in TM Process

Rohan explained the process of creating freight orders in TM, emphasizing that the solution design and architecture would determine whether to use ECC-driven or EWM-driven approaches. He clarified that when ECC and TM systems are integrated in the same environment, sales orders can directly create freight units without needing intermediary documents like OTR or DTR, making certain process slides irrelevant in S4 environments. The discussion focused on how solution architects should consider the overall system landscape during the product selection phase to determine the most appropriate integration approach.

ECC 6.0 and TM Integration

Rohan explained the integration between ECC 6.0 and TM systems, clarifying that in S4HANA environment, systems communicate via Data Replication Framework (DRF) rather than requiring separate interfaces or additional integration. Rakesh confirmed that SAP no longer releases separate TM versions, making the integrated S4HANA approach the future direction. The team discussed how sales orders trigger freight unit creation in TM, with ECC handling delivery processes separately, and agreed to continue the discussion in the next session where they will review system terms and proceed with system demonstrations.

SAP TM Integration Approaches

The team discussed SAP TM integration approaches and pricing structures. Rohan explained that SAP does not reveal pricing upfront as it varies based on customer needs and net worth, offering different subscription and user-based models instead. The group clarified two TM integration approaches: ECC-driven (using OTR/DTR) and TM-driven (directly from delivery), with technical architecture determining which approach to use. Shantanu sought clarification on the distinction between ECC and S4HANA, and Rohan explained that ECC in S4HANA refers to having ECC systems placed within the S4 HANA environment rather than being separate systems.