We have received lots of customer inquiries regarding SAP’s clean core strategy in recent years. One of the most frequently asked questions is, how we, from S/4HANA Cloud for EWM private edition team, see it. We have decided to write down this blog so that hopefully you can get a clearer picture on what clean core means in the context of EWM on Private Cloud/OP.

In short, we, EWM PCE, would like to stay as clean core as possible, because the clean core concept ensures future upgrade stability for our customers. Still there are special considerations that we want to take into account, before we make our decisions. It will be a multi-year journey for us, as well as for you, our valuable customers and partners, to completely transform to the new clean core concept. We also want to give you the intermediate, or let’s say, pragmatic options, to stay clean core.

Learn how SAP Cloud ALM can be used to monitor the End to End Master data replication

The looming threat of tariffs is the most talked about topic in boardrooms all over the world as they become “the hammer” in many geopolitical conversations.

SAP TM ERP Document Flow Navigation Through Fiori

SAP Transportation Management (TM) allow users to navigate form the ERP documents direct to the Freights Documents.

In the previous version of SAP TM, the navigation through the Freight Documents was in NWBC, which was the Front End for the Key User, now with S/4HANA Key User use the Fiori Launchpad.

Through the navigation from the ERP documents Key Users can see many data and follow up the process of Planning and execution for the Sales Order, Delivery, etc.

For example, from a Sales Order user goes to TM Status Tab and see a lot of information from the Freight Documents.

TM Document Flow.

Every Use who has access to navigate through the TM Document flow jus clicks on the Freight Document, and it open a new session in the browser to visualize the Freight Document.

If you notice in the Browser once you open i.e. a Freight Unit the section is based on NWBC, this means you can still do any action if need in the Freight Unit but you’re not able to navigation through the Fiori Launchpad.

From a Key Users perspective this session of the Freight Unit is exclusive and can’t get back to the Fiori Launchpad

From a technical point of view if you want to allow the Key Users navigate to the Fiori Launchpad and not NWBC, you can add the User parameter WEBGUI_IS_IN_FLP = Y, in Transaction SU3 this will allow the Key Users open the Freights Documents from the ERP direct in the the Fiori Launchpad mode.

After adding this parameter, you can see the difference for the Fiori Launchpad mode.

Note: Login in the Fiori Launchpad might be request.

Refer to;

3577612 - How to navigate to the Fiori Launchpad to open TM documents from ERP document flow. - SAP for Me

3199167 - TM: Create fully-qualified FLP-based document URLs - SAP for Me

2708480 - SAP TM embedded in S/4HANA - PFCG role concept - SAP for Me

Hope this help you!

Thank you and regards.

Rogerio Lima.

🚀SAP FSM 2502 is here! This release brings AI-driven planning simulations, deeper scheduling insights, seamless SAP PM order integration, and enhanced Smartform management. Plus, expanded multilingual AI support, enhanced routing, and localization improvements. Discover the latest innovations now!

In today’s business landscape, sustainability isn’t just a buzzword—it’s a competitive necessity. Companies must track and reduce their carbon footprint, particularly Scope 3 emissions, which often make up the largest share of their environmental impact. The challenge? Reliable and standardized data exchange between business partners.

We have recently released the latest updates for SAP EWM with the SAP S/4HANA 2023 Feature Pack 3 update. The enhancements of this release further improve our Advanced Shipping & Receiving integration and functionalities, complementing the features we delivered in the SAP S/4HANA 2023 Feature Pack 2 release. Furthermore, with this release we introduced a new Machine Learning based feature, called “Predictive Labor Demand Planning”, empowering shift managers at the warehouse to more accurately and efficiently plan out the tasks for the day. And to start today’s deep dive, we will begin with it.

As announced in SAP S/4HANA PcE 2023 FPS03 (https://community.sap.com/t5/supply-chain-management-blogs-by-sap/what-s-new-in-fp03-of-transportation-management-in-s-4hana-cloud-private/ba-p/13950181), it is now possible to determine the carrier in the Freight Order, Freight Unit, and Consignment Order at the time of document creation.

This functionality is particularly beneficial in cases where not all advanced TM planning features are utilized. Additionally, it allows users to allocate their time to more critical aspects of the process.

Below I describe a little about it:

• General Activations and/or Checks
• Configuration Steps for Functionality Execution
• Extension
• New fields in cockpit
• Carrier propagation

General Activations and/or Checks

1. Freight Unit Stage List, FU/PU Stage List - Field Catalog

2. Freight Unit Stage Hierarchy, FU/PU Stage Hierarchy, Consignment Order List, Consignment Order Hierarchy - Field Catalog

3. Freight Order List, Freight Order Hierarchy, Freight Order / Freight Booking List - Field Catalog

4. Activation of the "Document Mass Change" button - Page layout

5. New Grouping Rule

Configuration Steps for Functionality Execution

1. Create Carrier Determination Profile

2. Assign Carrier Determination

Profile in Freight Unit

Freight Order

Consignment Order

If using the Transportation Cockpit and intending to group all demand by "Carrier from Carrier Determination

Create Requirement Grouping Profile

Extension

BADI /SCMTMS/EX_TSPD

This BAdI offers three key intervention possibilities:

• Adjust the carrier determination profile applied to a given business document.
• Modify the decision on whether redetermination is necessary.
• Adjust the determined carrier.

New Fields in Transportation Cockpit

Carrier Propagation

1. Classic Planning: When the Freight Unit (FU) is assigned to a Freight Order (FO), the carrier information is propagated between FU and FO.

2. Multiple Carriers: If two FUs with different carriers exist, the FO will inherit the carrier from the first FU.

3. Post-Planning Adjustments: If an FO is already planned and FUs are removed, the system will retain the carrier from the first FU after modifications.

4. Manual Carrier Assignment: If a carrier is manually populated in the FO, the system will not override it with the FU's carrier information.