How Rajashiva Ramalingam Helped Deploy SAP's Embedded Transportation Platform at Maersk

When A.P. Moller-Maersk needed to extend its SAP embedded transportation platform into new European markets, the implementation required a specialized SAP configuration that goes beyond conventional shipper-mode deployments. Ramalingam was brought in because of his experience with exactly that configuration.

A.P. Moller-Maersk is one of the world's largest integrated logistics companies, operating in more than 130 countries and managing freight flows across container shipping, port operations, air freight, and land-based logistics. By 2021, the company was in the middle of a publicly announced strategic transformation, moving from a pure container shipping business toward a fully integrated logistics provider capable of managing cargo end-to-end across modes and geographies. That transformation required, among other things, a logistics technology platform that could support a fundamentally different operating model: not a shipper moving its own goods, but a logistics service provider managing transportation on behalf of clients.

Rajashiva Ramalingam joined Maersk's Global Service Center in October 2021 as a Senior SAP Transportation Management and Event Management engineer, assigned to a multi-country implementation of SAP Embedded Transportation Management on HANA 1909 in Logistics Service Provider scenario mode. His first responsibility was a live rollout for Italy. His second was contributing to the blueprinting and proof-of-concept work for the United Kingdom and Ireland.

The LSP Distinction: Why This Implementation Was Different

Ramalingam had built his SAP TM expertise across Shipper scenario implementations at organizations including Microsoft, Merck, and Apple during his Cognizant tenure. In Shipper mode, the system serves a company managing transportation for its own goods. The Logistics Service Provider scenario operates differently: the platform handles freight orders, carrier tendering, planning, and settlement for multiple external clients, each with distinct service agreements, charge structures, and reporting requirements. The data model, planning logic, and settlement flows all require different configuration approaches than a Shipper implementation, and practitioners whose experience is limited to Shipper mode cannot simply transfer that configuration approach to an LSP environment.

Ramalingam's assignment to the Maersk program also required working with SAP Embedded Transportation Management within S/4HANA, a platform variant with a different architecture than the standalone SAP TM he had worked with at earlier clients. Embedded TM shares the S/4HANA data model and process layer, which affects how integrations are structured and where configuration constraints apply. Understanding those differences, and applying them correctly in an LSP environment, was a specific technical requirement of the engagement that Ramalingam was responsible for navigating.

"The LSP scenario changes almost every assumption you bring in from a Shipper implementation," Ramalingam told this publication. "The charge calculation logic, the way orders are structured, the planning constraints, the settlement flows, they all work differently when you are managing freight on behalf of clients rather than for your own business. You cannot transfer your Shipper configuration experience directly. You have to re-examine everything from the data model up."

The Italy Rollout: From Blueprint to Live Operations

Ramalingam's primary delivery responsibility at Maersk GSC was the SAP Embedded TM implementation and go-live rollout for Italy. He configured the LSP scenario to handle freight flows and client requirements specific to that market, including charge calculation structures for multiple external clients, carrier tendering logic, and settlement flows that Maersk's Italy operations depended on. He then led configuration validation through structured testing phases and supported the transition into production.

For the Italy rollout, Ramalingam made configuration decisions that shaped the LSP charge model and how the platform's multi-client operating model represented client-specific requirements. These decisions became part of the production configuration used by the Italian operation. His responsibility therefore extended beyond technical development: he was accountable for translating business requirements into configuration that could operate reliably in a live logistics environment.

Ramalingam delivered an implementation that supported logistics operations across 27 client accounts and 84 freight lanes within Maersk's Italy network, establishing the SAP Embedded TM platform as the operational backbone for transportation planning and execution in that market.

UK and Ireland: Blueprinting for Scale

Alongside the Italy rollout, Ramalingam contributed to the blueprinting phase of the SAP Embedded TM implementation for the United Kingdom and Ireland. Blueprinting is the phase of an SAP implementation program where business requirements are translated into system design decisions: which processes will run in which configuration, how integrations will be structured, where standard platform capabilities will be used, and where custom development is required. The quality of the blueprinting phase can materially influence the stability and fitness of the implementation that follows.

His contribution to the UK and Ireland blueprinting included active participation in business workshops, where operational requirements were gathered and validated, and in proof-of-concept activities, where specific configuration approaches were tested against real business scenarios before being committed to the implementation design. Proof-of-concept work in an LSP SAP TM environment is particularly important because the LSP scenario configuration space is less standardized than the Shipper scenario, and incorrect design assumptions at the blueprinting stage are harder and more costly to correct once development and testing are underway.

The Professional Contribution of the Maersk Engagement

Ramalingam's work at Maersk GSC covered two distinct phases of an enterprise SAP TM program: a live country rollout in Italy, where his configuration decisions went into production and governed real client freight operations, and the blueprinting and proof-of-concept phase for the United Kingdom and Ireland, where his design decisions would shape the architecture of the implementation that followed. Contributing to both phases within the same program, and doing so in LSP mode on SAP Embedded TM, gave him direct experience across the full project lifecycle in a technically specialized configuration.

The Maersk engagement extended Ramalingam's implementation record in a direction his earlier Shipper-mode work at Microsoft, Merck, and Apple had not covered. An SAP TM practitioner experienced only in Shipper mode has a limited view of how the platform behaves when the operating model changes: when the company using the system is not moving its own goods but managing transportation as a service for external clients. Ramalingam's work at Maersk added that dimension to his record, establishing experience across two materially different operating scenarios within SAP Transportation Management. His experience across Maersk, ACCO Brands, Microsoft, Merck, and Apple demonstrates an implementation record spanning different transportation operating models, SAP platform environments, and stages of enterprise transformation.