Great news ! If you need help implementing SAP EWM, you can get help with this free customizing(configuration) course from SAP. 

This blog post is part of a series on SAP Digital Manufacturing new POD 2.0 framework, the new generation of SAP Digital Manufacturing worker UIs.

SAP Digital Manufacturing is taking a major step forward with POD 2.0. This is not a cosmetic upgrade. It is a full redesign of how worker-facing applications are built, configured, and executed on the shop floor.

If you work with Production Operator Dashboards (PODs) today, you already know their importance. They are the primary interface between operators and manufacturing execution. POD 2.0 fundamentally changes how these UIs are built, behave, how fast they respond, and how easily they can be adapted to real-world processes.

This blog post shows you how to build a event-driven extensions in SAP S/4HANA Public Cloud using a practical example, that updates freight order header data automatically after creation.

This blog post shows possibilities to simplify the Transportation Cockpit layout to focus on the data and actions most relevant to daily planning. 

This article describes how you can you can configure delivery-based Freight Unit (FU) creation to simplify your Freight Order process in SAP S/4HANA Public Cloud Transportation Management.

The post explains how to configure and maintain Processing Variants in SAP Logistics Management using the Configure Shipping Processes Fiori app. It describes the app as the central place to view SAP-delivered variants and create customer-specific variants, with list features like filtering by shipping process, searching by ID/description, and identifying SAP-managed vs. custom entries. It notes that SAP provides standard, read-only baseline variants (e.g., Parcel, LTL, Direct LTL, and No Shipping) that cannot be changed. For custom variants, the workflow includes creating a draft, selecting a base shipping process, defining a clear Display ID and description, configuring available options (currently mainly Consolidation Cutoff for LTL/Direct LTL), and then activating the variant. After activation, process-controlling configuration becomes immutable to avoid disrupting active Transportation Requests and Consignments, while descriptions and default status can still be updated. The post outlines governance rules: SAP-managed variants are fully read-only, only one default variant is allowed, and deletion is not supported (with deprecation suggested via naming/description). It closes by emphasizing that business rules determine when a variant is used, while variants define what the process behavior is, enabling changes in rules without changing variant logic.

This blog post is part of a series on SAP Digital Manufacturing new POD 2.0 framework, the new generation of SAP Digital Manufacturing worker UIs.

SAP Digital Manufacturing is taking a major step forward with POD 2.0. This is not a cosmetic upgrade. It is a full redesign of how worker-facing applications are built, configured, and executed on the shop floor.

If you work with Production Operator Dashboards (PODs) today, you already know their importance. They are the primary interface between operators and manufacturing execution. POD 2.0 fundamentally changes how these UIs are built, behave, how fast they respond, and how easily they can be adapted to real-world processes.

If your logistics are lightweight, full-scale Transportation Management can feel heavy. With SAP S/4HANA Public Cloud Transportation Management, you can automate most steps so planning, execution, and settlement take only a few clicks. 
This series highlights practical automations across the freight order lifecycle. In the overview illustration, steps marked in blue can be fully automated.