SAP Transportation Management Clean Core Evolution

Introduction

SAP Transportation Management (TM) is undergoing a transformative evolution through the Clean Core (What is a clean core? | SAP) initiative, fundamentally changing how organizations approach transportation order processing and data management. This comprehensive analysis examines five critical SAP Notes that collectively establish the foundation for modern, Clean Core-compliant TOR (Transportation Order) processing in S/4HANA 2025.

These interconnected notes represent a strategic shift from traditional transportation processing to a standardized, API-first architecture that leverages Virtual Data Model (VDM) CDS views, RESTful Application Programming (RAP) objects, and enhanced cross-module integration capabilities. Organizations implementing or upgrading SAP TM will benefit significantly from understanding how these notes work together to create a robust, future-ready transportation management platform.

Find out about the purpose and key ingredients of a clean core in SAP S/4HANA Cloud, private edition. Explore how you can get and stay “clean core compliant,” and discover the advantages you gain by following the clean core principles, with the focus on clean core extensibility.

Clean Core: What It Is, Why to Do It, and How to Get There

SAP Notes Overview

SAP Note 3619960 - Clean Core TOR Transportation Processing VDM CDS View + RAP Objects

Purpose

This note delivers new Transportation Processing (TP) layer VDM CDS views along with comprehensive RAP objects specifically designed for transportation order management. It establishes the core processing layer that enables modern, API-first transportation order handling while maintaining strict Clean Core compliance.

Key Components

The note introduces several critical TP views including R_TransportationOrderTP_2, R_TransportationOrderItemTP_2, R_TransportationOrderStopTP_2, R_TransportationOrderEventTP_2, R_TransportationOrderStageTP_2, R_TranspOrdDocRefTP_2, and R_TranspOrdItemDocRefTP_2. Additionally, it delivers BDEF R_TRANSPORTATIONORDERTP_2 with comprehensive RAP objects including behavior implementation pools (BP_R_TRANSPORD*TP_2), behavior handler classes, and entity handler classes.

Prerequisites

This note requires Clean Core TOR Foundation layer VDM CDS views available from S/4HANA 2025 FPS0, establishing a clear dependency hierarchy that must be followed during implementation.

SAP Note 3620011 - BDC/Data Produtores/4 2025 FPS1

Purpose

This note enhances the Business Data Catalog (BDC) framework and introduces advanced data product capabilities specifically for Transportation Order processing in S/4HANA 2025 FPS1, enabling standardized data exchange and improved integration patterns.

Key Features

The implementation focuses on enhanced data product framework for TOR objects, improved integration capabilities with external systems, standardized data exchange mechanisms, and performance optimizations for large-scale transportation operations. This creates a foundation for seamless data consumption across hybrid landscapes.

SAP Note 3546383 - Clean Core TOR_CDS View Foundation_OP25FSP0

Purpose

This foundational note contains new Clean Core Transportation Order Management foundation layer CDS views delivered in S/4HANA 2025 FPS0. It establishes the base data model structure upon which all subsequent transportation processing enhancements are built.

Core Components

The note delivers fundamental CDS views that provide base transportation order data structures, standardized field definitions and relationships, authorization framework integration, and performance-optimized data access patterns. As the foundation layer, this note serves as a prerequisite for other transportation processing enhancements.

SAP Note 3675099 - Downport Location VDM to EWE (2025/FPS1)

Purpose

This note addresses the downporting of Location VDM capabilities to Extended Warehouse Environment (EWE) for S/4HANA 2025 FPS1, ensuring consistent location data management across transportation and warehouse management modules.

EWE Integration

The note delivers new CDS views for Location and Transportation Location including I_LocationBasic_2, I_LocationText_2, I_LocationType, I_TransportationLocation_2, and I_TranspLocationType_2. These views become available when the corresponding Support Package is installed, providing seamless integration between TM and EWM location master data.

SAP Note 3677186 - Clean Core Location CDS View Foundation - OP2025 FPS1

Purpose

This note provides enhanced Clean Core Location CDS view foundation for S/4HANA 2025 FPS1, delivering corrections and enhancements to the location data model established in the previous note.

Foundation Components

The note delivers the same core location CDS views as Note 3675099 but includes corrections and enhancements. This ensures robust location master data management with improved data consistency and enhanced integration capabilities across transportation and warehouse management modules.

Comparative Analysis

Implementation Roadmap

Phase 1: Foundation Setup

1. Apply SAP Note 3546383 to establish Clean Core TOR Foundation layer CDS views
2. Validate base transportation order data structures through transaction SE11
3. Configure authorization framework and verify data access permissions
4. Perform initial testing of foundation layer functionality
5. Document baseline system configuration for future reference

Phase 2: Core Processing Enhancement

1. Implement SAP Note 3619960 for Transportation Processing layer
2. Deploy VDM CDS views and validate data consistency across all transportation objects
3. Configure RAP objects including behavior definitions and handler classes
4. Test CRUD operations through RAP framework with comprehensive error handling
5. Validate business logic implementation and integration points

Phase 3: Data Product Integration

1. Apply SAP Note 3620011 for BDC/Data Product capabilities
2. Configure data product framework for TOR objects with appropriate governance controls
3. Test integration scenarios with external systems and validate data quality
4. Implement monitoring and alerting for data product consumption
5. Establish data governance policies and procedures

Phase 4: Location Management Integration

1. Implement SAP Note 3675099 for Location VDM downport
2. Apply SAP Note 3677186 for enhanced location foundation
3. Configure EWE integration points and validate location data synchronization
4. Test cross-module consistency between TM and EWM
5. Validate location master data harmonization across all modules

Phase 5: Complete System Validation

1. Perform comprehensive end-to-end testing across all implemented components
2. Conduct performance validation under realistic load conditions
3. Execute user acceptance testing with business stakeholders
4. Prepare go-live procedures and rollback plans
5. Establish ongoing monitoring and maintenance procedures

Technical Architecture Impact

VDM Layer Evolution

The progression from foundation (Note 3546383) to processing layer (Note 3619960) creates a robust, layered architecture that separates concerns while maintaining data consistency. This evolution enables better performance through optimized data access patterns and provides clear extension points for custom requirements while adhering to Clean Core principles.

RAP Framework Integration

The introduction of RAP objects in Note 3619960 enables modern service exposure capabilities, encapsulates business logic effectively, and provides standardized API access patterns. This framework supports both OData and REST protocols, making transportation data accessible to various client technologies while maintaining upgrade stability.

Cross-Module Integration

The location VDM implementation (Notes 3675099 and 3677186) ensures data consistency between Transportation Management and Extended Warehouse Management, creating a unified location master data approach that reduces data redundancy and improves data quality across modules.

Benefits and Value Proposition

Clean Core Compliance

• Reduced customization complexity through standardized extension points and approved APIs
• Improved upgrade compatibility by eliminating core modifications and technical debt
• Standardized data models that align with SAP's strategic technology direction
• Future-ready architecture supporting seamless cloud migration scenarios

Performance Improvements

• Optimized data access patterns through VD
• Support documentation for this topic

 CDS Views for Fixed Domain | SAP Help Portal For SAP Transportation Management

3662211 - Clean core enhancement capabilities and MTr consideration for TRS and NPD - SAP for Me

3675099 - Downport Location VDM to EWE (2025/FPS1) - SAP for Me

3619960 - Clean Core TOR Transportation Processing VDM CDS View + RAP objects - SAP for Me

3546383 - Clean Core TOR_CDS View Foundation_OP25FSP0 - SAP for Me

3677186 - Clean Core Location CDS view foundation - OP2025 FPS1 - SAP for Me

Hope this support you.

Kind regards

Rogerio Lima.

With SAP Business Network for Logistics release 2511, SAP harmonizes freight execution tracking across SAP Business Network Freight Collaboration (FC) and SAP Business Network Global Track and Trace (GTT). This article outlines the new, harmonized tracking experience and the role of the shared Web UI for manual event reporting—the ‘Manage Freight Execution’ app —which provides a consistent look for role-appropriate views by shippers and carriers, and ties events to a central tracking table accessible from both Freight Collaboration (FC) and Global Track and Trace (GTT).

This unification consolidates information shared across FC, Dock Appointment Scheduling, and GTT. As part of the product roadmap, the legacy apps ‘Track Freight Movement’ for FC shippers and ‘Freight Orders for Reporting’ for FC carriers are planned for deprecation in May 2026. GTT solution owners gain an additional reporting channel, enabling data contributors to report events via the Web UI.

Alongside the shared event-reporting application, we refined the tracking scenarios in FC and GTT.

This blog is structured as follows:

• Introducing the ‘Manage Freight Execution’ app
• Use-case differentiation for event tracking in FC and GTT
• Next steps for shippers / solution owners
• FC shippers using basic tracking
• GTT solution owners receiving tracking information through B2B connectivity with data contributors
• GTT solution owners planning to request event reporting via Web UI from some data contributors and C shippers wanting to leverage
• Next steps for carriers / data contributors
• Carriers using the legacy ‘Freight Orders for Reporting’ app
• Carriers or data contributors connecting via API or EDI
• Carriers newly requested by their shipper customers to report events via the Web UI
• Where to find more information

 Please note, there is also a dedicated webinar on tracking harmonization scheduled for November 26th. 

Register here

Introducing the ‘Manage Freight Execution’ app

The ‘Manage Freight Execution’ app has been introduced for both shippers and carriers.

It supports shippers in gaining visibility into shipment execution and in managing freight activities with flexible event intake options, while enabling carriers to report events via Web UI, while still leveraging the existing API or EDI options for automated reporting. The app also allows shippers to report events on behalf of their carrier. All events are displayed in a unified view, independent of the submission channel.

Shippers can view carrier milestones (regardless of how the event was received), report planned and unplanned events, provide estimates or delays, view event history, and access attachments.  This allows all of the stakeholders associated with the shipper to stay informed, when a tracking update is made by the shipper themselves. 

Carriers can report milestones and events (planned or unplanned), provide estimates or delays, and view event history, independent of reporter or channel.  Manual reporting through the new app gives carriers an option, in addition to automated reporting through the existing API and EDI, to report events and stay n sync with shipment execution. 

The following screens illustrate the carrier view.

Figure 1: Main view, filter section and worklist

 Figure 2: Detail view, header and tabs

Figure 3: Report planned event from header

Figure 4: Report unplanned event

 Figure 5: View event history

Figure 6: Detailed event overview

This carrier how-to video describes the app in detail.

The shipper view and use of the app differ only in minor aspects; more details are available here.

Shippers currently operating with the ‘Track Freight Movement’ app and carriers operating with the ‘Freight Orders for Reporting’ app are encouraged to commence adoption of the new ‘Manage Freight Execution’ app, with ample time to adopt prior to conclusion of the legacy apps in May 2026.

Use-case differentiation for event tracking in FC and GTT

As noted earlier, we have introduced a shared application for event reporting, while maintaining the existing API and EDI options for automated reporting. While supporting these options for  tracking data reporting, we can clarify the use-cases and tracking scenarios between FC and GTT.

Going forward, FC will continue to support collaboration between shipper and carrier for contracting, settlement, and dock appointment scheduling. For tracking, FC provides basic milestone event tracking, document attachments, and ETA updates.

GTT supports the same basic tracking as FC, along with more advanced shipment and order-fulfillment tracking scenarios, including geolocation updates, map view, and emissions data, for shipments in the context of the purchase order, sales order, or stock transfer order to which the shipment pertains.  

The graphic below illustrates the differentiation of use cases when using the “Manage Freight Execution” app.

In FC, carriers or visibility providers can report milestones and ETAs for road and ocean transports via the web UI or API. Events reported by warehouse or gate operators are included in the ’Manage Freight Execution‘ app. FC shippers can view the events in the event history.

In GTT, data contributors—visibility providers and carriers—can directly report milestones, ETAs, and geolocation updates via API, for shipper’s information and use in the existing ’Track Shipments‘ app. Carriers can now also report events via the new ‘Manage Freight Execution’ web UI, sharing specifically milestones, ETAs and documents. Reporting stays in sync between the ‘Manage Freight Execution’ and ‘Track Shipments’ apps.

Synchronization with the S/4HANA remains unchanged for both FC and GTT.

Next steps for shippers / solution owners

FC shippers using basic tracking

With this release, we deliver enhanced consistency to improve data reliability and alignment across the landscape. Carriers and shippers can report milestones, ETA, as well as unplanned events via the ‘Manage Freight Execution’ app in the web UI, ensuring timely and comprehensive event reporting. In addition, ocean freight tracking is now available, extending visibility to sea shipments and enabling end-to-end tracking.

Please consider the following enablement steps

1. Notify business users about the new application and update role collections. Admins should either create a new role collection or add the role templates 'ManualReportingDisplayTemplate' and 'ManualReportingProcessTemplate' to an existing role collection. If added to an existing collection, all users in that collection will gain access to the app; if a new collection is created, assign the relevant users to it.

Note: SAP will enhance carriers’ role collections on productive carrier tenants. On test tenants, shippers must update their test carriers’ roles.

2. Start using the new 'Manage Freight Execution' application as soon as possible. The legacy application 'Track Freight Movement' remains available until deprecation.

3. Encourage your carriers to adopt and use the new 'Manage Freight Execution' application.

GTT solution owners receiving tracking information through B2B connectivity with data contributors

Functional enhancement from this release does not impact their current use case – no changes or next steps required.

GTT solution owners planning to request event reporting via Web UI from some data contributors and FC shippers wanting to leveraging advanced tracking

GTT solution owners who want carriers to report events via the web UI can now use the ‘Manage Freight Execution’ app. Events submitted through the web UI are visible in the existing  ‘Track Shipments’ app.

Going forward, the map view, geolocation reporting, are no longer available in FC. GTT is SAP’s solution for advanced tracking and order-fulfillment monitoring across sales, purchase, and stock transfer orders, inbound advance ship notices (ASNs), and outbound deliveries. In addition to road and ocean tracking, it supports air and parcel tracking; impact analysis for late or delayed shipments; emissions tracking; and provides a flexible UI and event-to-action scripting for automated alerts and notifications. Further, GTT tracking is not only based on freight order and freight booking level. GTT  can also generate tracking units based on freight orders or freight bookings, based on freight units or containers. GTT is both tightly integrated with SAP S/4HANA and able to be connected to non-SAP applications.

Please consider the following enablement steps (for GTT solution owners only steps 5 and 6):

1. Subscribe to SAP Business Network Global Track and Trace and onboard.
2. Decide how you want your freight documents to be tracked in GTTOption 1: Standard IDOC (recommend; Advantage: support advanced tracking, including FU, multiple tracking units (e.g. containers), events reported from S/4, customized events reporting, but requires additional configuration). For more details, see using standard extractor codesOption 2: SOAP message (TransportationOrderGenericTrackedProcessRequest_Out) for TM freight order/booking in GTT (routing request can be entered via customer ticket, component SBN-LBN-INT). Less effort if you are already using this SOAP message for Track Freight Movement app, but limited scope, e.g. only FO and FB with one tracked object (e.g. 1 container per shipment).  
3. Replicate location from S/4HANA to Location master of BN4L
4. Maintain system ID and logical system ID in ‘System Connection’ app (see screenshot) 

      5. (Visibility Provider integration – no GTT configuration required, but double check on tracking information in each      shipment e.g. carrier reference, carrier identifier, tracked object, …     

     6. Setup carrier manual reporting via WebUI

• Invite carriers to onboard via Carrier Onboarding Guide (Note: Please contact your SAP network services lead to guide with aligning the carrier LBN ID and carrier identifier, e.g. SCAC code to leverage Visibility Provider service. Or Maintain Alternate ID in Custom Header of ‘Configure Partner Connection’ app by entering “LBN_CUSTOM_CARRIER_ALT_ID” as Key and “SCAC#1234” as value)
• Maintain carrier’s LBN ID in business partner master, e.g. update Business' Partner LBN ID in S/4HANA
• Maintain carrier LBN IDs in carrierListForManageFreightExecution value in Event-to-Action Script in gttft1 model

• To process events in the same way as in the ‘Manage Freight Execution’ app, you must set event status to be triggered by actual technical timestamp in the ‘Manage Models’ app - see Edit the Tracked Process

•  Adjust entries in ‘Configure Partner Connections’ app e.g, previously maintained “SCAC#1234” should be replaced by the LBN ID - see 'Create Partner Connection’

     7. Get shipper ready to work with ‘Manage Freight Execution app’

• The admin users need to either create new role collection or add the new roles templates ‘ManualReportingDisplayTemplate’ and ‘ManualReportingProcessTemplate’ to existing role collections. If added to existing role collection, then the users in that role collection will have access to the app. If a new role collection is created, then the users should be added to that role collection.

Next steps for carriers / data contributors

Carriers using the legacy Freight Orders for Reporting app

Carriers currently using the ‘Freight Orders for Reporting’ app should start using the new ‘Manage Freight Execution’ app as soon as possible, leaving ample time for adoption before deprecation in May 2026.

Detailed how-to video for carriers on how to use the app can be found here.

Carriers or data contributors connecting via API or EDI

For carriers and data contributors currently reporting via API or EDI, there are no changes.

Carriers newly requested by their shipper customers to report events via the Web UI

Carriers without an active account in SAP Business Network for Logistics will receive an invitation from their shipper or solution owner to join the network. A detailed guide to activating the account after receiving an invitation is available here.

Further, shippers or solution owners need to notify their carriers if they want them to report via the new ‘Manage Freight Execution’ app. The carrier’s administrator must assign the necessary roles in the ‘User Management’ app and inform the relevant business users.

A step-by-step tutorial video for carriers on using the ‘Manage Freight Execution’ app is available here.

Where to find more information

Below, please find a collection of useful links related to the tracking harmonization enhancements from this release.

In addition, I would like to point you to our upcoming webcast on November 26th, 10 am CET where you can hear directly from our experts and ask questions – register here

SAP Help Portal – What’s New

Feature detail deck on tracking harmonization

Carrier how-to video on ‘Manage Freight Execution’ app

SAP Business Network Freight Execution L2

SAP Business Network Global Track and Trace L2

Getting started with SAP Business Network for Logistics

---------------------------------------------------------------------------------------------------

The above summarizes tracking harmonization as part of the 2511 release. Thanks for reading the blog post and stay tuned! 

A full overview of the 2511 release can be found under the following link.

To learn more about SAP Business Network for Logistics visit SAP - Business Network for Logistics.

For further questions and feedback related to the blog, please check the Q&A area and feel free to post your questions in the link with the tag SAP Business Network for Logistics.

Special Operation Activity Routings are a tool in SAP Digital Manufacturing (DM) that are useful for a number of use cases.   This article describes the configuration and use of Special Operation Activities and Routings (SOA) within SAP DM. A Special Operation Activity and Special Operation Activity Routings that provides a controlled method for removing an SFC from its standard production flow to handle rework, inspection, or other nonstandard processes, ensuring traceability and process integrity.

Many SAP customers use SAP Ariba Supplier Lifecycle and Performance (SLP) to onboard suppliers and then integrate the supplier master data into SAP Master Data Governance (MDG) or directly into SAP ERP/S/4HANA Business Partner. However, the standard integration provided through SAP Integration Suite, Managed Gateway for Spend and Business Network (CIG) does not support the transfer of supplier attachments (e.g., compliance documents, certificates, tax forms) from Ariba SLP into MDG Change Requests or directly into the Business Partner record.

To address this gap, the SAP MaxAttention Center of Expertise (CoE), Procurement team (North America) has developed an integration package on the SAP BTP Integration Suite. This custom content enables customers to automatically bring attachments uploaded in Ariba SLP into:

• SAP MDG Change Requests, or

• SAP S/4HANA Business Partner attachments (bypassing MDG if desired)

This solution helps customers complete supplier onboarding with all required documentation synchronized across systems, reducing manual effort and compliance risk.

In this blog post, you can find the latest collection of new capabilities in SAP Field Service Management. 

In the fast-paced world of cloud native solutions like SAP Field Service Management, staying up-to-date with the latest information and resources is crucial. This blog post serves as your centralized hub, providing direct access to essential documentation, strategic roadmaps, influential channels, upcoming and recorded webinars, and insightful blogs. Bookmark this page and revisit often to ensure you're always informed.

Supply Chain 2035: How Data, AI, and Agents are Changing Supply Chain Planning

In the discussion about the future of supply chain management, one area is increasingly at the center: planning. Supply chain planning not only affects operational efficiency, but directly influences a company’s service quality, fixed capital and responsiveness. Our joint study from SAP Business Consulting and Kühne Logistics University clearly shows that companies that are already planning proactively today can avoid bottlenecks, optimize costs, and exploit potential in a targeted manner.

Supply chain planning is the central lever for anticipating problems before they arise. Companies that anticipate bottlenecks and proactively manage capacity, inventory and resources avoid hectic “fire fighting” in day-to-day operations. Planning thus acts as an early warning system that not only enables stable service, but also more efficient use of resources and proactive action. Effective planning also requires seamless integration and evaluation of a variety of internal and external data sources – from granular sales data to basic economic data, to production, procurement, and distribution plans. Different planning levels and horizons need to be connected, and this is where there are huge opportunities for artificial intelligence that can process data volumes, identify patterns, and improve predictions. Advanced planning processes will become a matter of course over the next ten years. If you do not achieve at least a modern, integrated planning level by 2035, you risk not only a competitive disadvantage, but also the loss of operational control capability.

Our survey of supply chain decision-makers (see figure) provides a clear picture of the future. Many expect planning to be much simpler and more intuitive in 2035 than today. More than half expect generative AI and GPT models to have a significant impact on planning processes, and much of it sees data quality as a critical factor in planning decisions. In addition, many expect the breakthrough of new AI-powered forecasting tools that incorporate additional data sources and significantly improve demand planning. Around a quarter expect advanced risk analysis to provide the ability to proactively detect and mitigate disruptions.

However, the status quo shows how big the gap between aspirations and reality is. Only a small number of companies rated their planning as mature in our survey. Similarly, few are actively experimenting with GenAI or GPT applications in the planning environment. Only a minority has very accurate planning data harmonized from different sources. Highly automated demand planning with minimal human intervention is the exception, as are planning systems that provide clear recommendations for action in the event of disruptions. This discrepancy shows that the path to truly modern, intelligent planning is still long and requires targeted investment, clear priorities and structured action.

In order to close this gap, different approaches must be pursued. Companies where planning is a strategic core process or requires very individual processes can realize enormous potential with agent-based AI. With the advent of new agency tools, most repetitive, error-prone work is automated, allowing planners to focus on value-added analytics and decisions. Companies with standardized processes and a low strategic relevance of planning will be able to procure their planning function more as a service in the future. Technology and platform models could enable true end-to-end planning across company boundaries for the first time. Simulations and digital twins will also play a growing role. Although these often fail today due to complexity, modeling effort, and scalability, AI-powered modeling agents could significantly accelerate and improve the accuracy of simulation creation and updates in the future, making their use more practical in larger networks.

Regardless of the individual target image, there are measures that every company should tackle immediately (“no-regret moves”). This includes building robust data governance and harmonizing master data as the foundation for any data-driven planning. Unfortunately, the principle of “garbage in, garbage out” also applies with AI: without high-quality data, even the best AI system cannot deliver meaningful value. A consistent, company-wide IBP system enabling a S&OP process provides the basis for a common planning goal. Initial pilot projects with agent-based sales forecasting help gather experience with AI-powered planning approaches. Finally, it is important to actively link existing planning platforms, such as SAP IBP, with AI services to unlock integration potential early on.

Supply chain planning is now more important than ever and will become a key differentiator between successful companies and those left behind by 2035. The technologies to make planning smarter, faster, and more resilient already exist – but they must be combined with clear goals, a resilient data foundation, and organizational readiness for change. Those who lay the foundations today will not only be able to plan faster and more precisely tomorrow but can also act strategically before others can even react.

Figure: Results of an online survey of 119 SC managers with people responsibility, conducted on 01/2025 as part of a joint SAP KLU study

This article was written in collaboration with Prof. Kai Hoberg (Kühne Logistics University) in the context of the SAP-KLU study "The Supply Chain of the Future”.

Improve your APIs as part of your own sustainability journey!

SAP TM Transaction SICF Configuration Details

Sometimes when Users try to open a Fiori in SAP TM got the error "403 Forbidden". The reason for this error will explain in this blog how to fix it.

Overview

• In SAP Transportation Management (SAP TM), the SICF (SAP Internet Communication Framework) configuration enables all web-based user interfaces, APIs, and system integrations.
  It ensures that transportation planners, carriers, and connected systems can access TM functionalities through secure web services and Fiori applications.

Prerequisites

• Required authorizations: SM34, SICF, SM30, SPRO, SU01, STRUST, SE38
• System requirements: SAP TM 9.1 and subsequent releases, or SAP S/4HANA 1709 and later versions
• User access levels needed: Administrative privileges for service activation and configuration

Accessing SICF Transaction

1. Navigate to transaction code SICF in your SAP TM system
2. Execute the transaction to query the service hierarchy
3. The initial screen displays the virtual hosts and services tree structure

SICF Configuration for SAP TM

Service Activation Steps

1. Select the default host or virtual host under which you want to create/activate services
2. Navigate through the hierarchy tree to locate TM-specific services (/default_host/sap/bc/webdynpro/scmtms)
3. Right-click on services and choose "Activate Service" to enable them

After activated it you also can execute a Test to ensure the error is not appearing.

A popup will appear to open the Fiori:

Key TM Services in SICF

Service Configuration Parameters

HTTP Settings

• Configure virtual hosts based on your system landscape requirements
• Set appropriate port settings for HTTP/HTTPS communication
• Enable SSL configuration for secure data transmission

Authentication Settings

• Configure client number in the Logon Data tab for TM-specific services
• Set up handler classes (e.g., /TRP/CL_REST_APP for REST services)
• Assign appropriate user credentials for service access

Testing and Validation

1. After service activation, clear cache globally and locally through transaction SMICM
2. Navigate to Menu → Goto → Http Plugin → Server cache → Invalidate locally and globally
3. Test service accessibility through web browser or integration testing tools
4. Verify proper authentication and data exchange

Support documentation for this topic

2614758 - Important SICF services in SAP Transportation Management - SAP for Me

2807334 - Web Dynpro SICF nodes for Transportation Management - SAP for Me

Creating and Activating ICF Service | SAP Help Portal

Configuration of SAP Transportation Management | SAP Help Portal

3660702 - 403 forbidden error when accessing "Create Transportation Duration Determination Profile" in SAP S/4HANA 2023 - SAP for Me

2834523 - Troubleshooting 500 Internal Server Error when opening any SAP TM UI screen - SAP for Me

Hope this support you.!

Kind regards

Rogerio Lima.