Real -time insights into material availability with MRP cockpit

• One single harmonized MRP process for all materials, both unconstrained and those
requiring advanced constraint -based planning

• Personalized and dynamic planning of replenishment with demand-driven MRP, fully

integrated into the existing ERP concept

• Material ledger as a default option; inventory valuation data existing in material ledger,
removing redundancies and aggregates

• Single platform with basic and advanced shipping, with the SAP Transportation
Management application embedded in SAP S/4HANA

• Multichannel allocation management using demand characteristics to allocate and

reserve short supply

• Real -time order confirmation considering allocation constraints

DATA
Resolving data issues is the No. 1 challenge for S/4HANA migration. As an example, the current master
data switch from the existing Customer Master model to S/4HANA’s Business Partner approach. This
and a number of other similar changes in various data elements will have to be thought through from both
the data model and overall business process perspective.

SCOPE

It’s important to understand your critical business process needs, and then limit the scope of the
S/4HANA migration to those, while also making sure that you’re aware of the mandatory changes that
SAP S/4HANA imposes. You don’t want to create a scope larger than what it Needs to be.

FEATURES
Your migration needs to take account of areas in S/4HANA where functionality has either been moved,
eliminated, or replaced with new innovations. Some common examples are the replacement of Foreign
Trade with Global Trade Services, or with the shift of Credit Check to the Finance area. All the new
features need to be looked at from both lenses, Scope and Business criticality.

CODE
With many SAP customers now having considerable custom code within their environment, any
migration will need to take account of best coding practice revisions, as well as any limitations in terms of
what they can do with their code. The balance between replacing the code with new Functionality,
business process criticality, and overall project scope is the key.

UI, UPDATE AND INFRASTRUCTURE

Despite user enthusiasm for Fiori applications, it’s important not to overload the initial migration.
Organizations also need to be aware of the challenges of frequent S/4HANA updates (quarterly on the
cloud), as well as managing the multiple aspects of cloud scalability, performance, and reduced overall
infrastructure size.