The SAP Talent Gap: Finding the Right Team of Experienced Consultants

The SAP talent gap has come to the forefront in industry conversations around digital transformation and mandatory upgrades forecasted for the next several years. This recent Forbes article shines a spotlight on the growing talent gap in the SAP ecosystem, particularly in relation to the migration of existing ERP systems to the S/4HANA platform. SAP has set a 2027 deadline for migrating legacy ERP systems to S/4HANA–and most of SAP’s 425,000 clients worldwide have not started their migrations yet. 

While SAP S/4HANA can be used both on premise and in the cloud, the benefits of utilizing cloud technology are continually growing, convincing more and more organizations to make its adoption a priority. Organizations that wait too long to make the transition to the cloud may face difficulties due to outdated infrastructure. For an increasing number of organizations, it just makes sense when migrating to S/4HANA to simultaneously manage a move to the cloud. 

With just 3 years remaining until the SAP deadline, it’s clear that there will be a surge in migration projects, leading to an unprecedented demand for qualified talent and a growing concern over the SAP talent gap. Many organizations will face challenges when recruiting top talent for their own teams and in finding partners with experienced consultants who are available.

Working with experienced SAP consultants is crucial for any organization looking to maximize the potential of SAP software and to reduce risk when executing SAP projects. SAP is a complex and constantly evolving platform; working with consultants who bring varied and robust experience to the table is essential to ensure successful implementation and ongoing support of the system. 

Statistics about SAP talent gap concerns for 2027

In the early 2000s, the push to offshore SAP project delivery work exposed challenges when working with less experienced resources. Many projects were delivered behind schedule, incurred cost overruns, and resulted in functional and technical issues post-delivery. It was not unusual to have to invest significant capital to re-implement and clean up the issues. This experience led to the onshoring of many roles and to changes in how companies engage offshore resources. Moreover, it highlighted the importance of finding experienced SAP consultants and employees with SAP skills.

Senior SAP consultants provide the following benefits: in-depth knowledge and expertise, business acumen and familiarity with industry-specific processes, the ability to handle different SAP modules and integrations, an understanding of system upgrades and changes, efficient problem-solving skills, deep industry contacts and network, exposure to different project types and sizes, and an understanding of best practices. Those advanced skills lead to faster deployment and implementation, cost and time savings, and overall lower project risk.

Vortex SAP consultants have 23 years of experience

The number of years of SAP experience is just one part of the equation when it comes to delivering a high-quality solution. At Vortex it is as much about understanding your corporate dynamic as knowing the SAP system. We take pride in forming true partnerships and working with our clients to find the best teams for their needs.     

In summary, it is expected to become more and more difficult to find the right resources given the growing SAP talent gap and the surge in demand to migrate to the cloud. Experienced consultants bring a wealth of knowledge and expertise, helping organizations to streamline processes, increase efficiency, and achieve their business goals with SAP. In this competitive business landscape, partnering with experienced SAP consultants can give businesses a competitive edge and ensure they are making the most of their SAP investment. At Vortex, we are confident that we bring the best teams in the industry to help our clients be successful. Send us an email to get a conversation started with a member of our senior leadership team today. 

SAP Global Template Demystified: Process Design

We’ve talked about the fact that an SAP Global Template is so much more than process design. At the same time, you can say that it is nothing without a solid and sound process design at its core! This is where consulting expertise, business knowledge, and SAP software product experience intersect, where these different components must merge to form a beautiful piece of art. (For a refresher on this topic, please refer back to our earlier blog post, “Why Experience Matters on Your Road to S/4HANA.”)

Advice on SAP Global Template Process Design

When it comes to process design in the context of an SAP Global Template, I want to talk about some of the main concepts that come to mind:

  • Organizational Model – It is imperative to not only align the organizational model with the available structures in SAP (company codes, profit centers, etc.) but, also, to shape it in a way that creates templates. These structures need to be at the core of the building blocks to describe what an operating company vs. a holding company looks like, to distinguish the difference between a complex operation vs. a site business. They allow you to categorize the elements of your business fleet to identify the right starting point once the next acquisition or greenfield operation comes along.
  • Business Functionality – SAP has an extremely large portfolio of business functionalities. You need to be able to identify what is important for your company! Once you’ve established the core components of your business design, group them around the building blocks of your organizational model to establish the go-to pieces of your Lego puzzle! That allows you to start from a pre-built structure instead of starting from a single brick. As I’ve frequently said in previous blog posts, you need to avoid reinventing the wheel!
  • Level of Standardization – Part of the concept of the SAP Global Template is moving from having continued design discussions (“Business Blueprint”) to focusing on rolling out a pre-designed solution that needs to be adopted (“Fit-Gap”). It represents the shift from rehashing the basics to simply stating the obvious–if you are a business in the fleet, you need to comply with the direction that the overall enterprise takes. This will be the biggest factor for saving money in your SAP deployments, and, with it, the best guard against the useless over-customization of your SAP system that to this day plagues many companies out there.
  • Solid Documentation – We need to talk about the complexity of business design in relation to the short span of the human memory. If you do not document what you agreed upon, you have already lost the battle! Coming to conclusions in those endless blueprint sessions is a thing that you do not want to jeopardize afterwards! Simply write down what you agree on, put it in swim lane diagrams, freeze if in business design templates, lock it into configuration documents. In other words, put it in writing to save yourself from the hassle of doubting your memory as time passes! I agree, this is not the most enticing topic, but–by far–it is one of the most important, as many executives have had to learn the hard way! 

Allow me to come back to the question of standardization of the business design in your SAP Global Template. You need to talk about and agree on the rigidity of that design when it comes to systems configuration. Which parts would you allow to be changed by a given local business and where would you draw the line to defend the given corporate design? I find it very helpful to partition your functionality and master data into different categories that are aligned with said level of rigidity:

  • Mandatory, not changeable – These settings and functions are not up for debate. All parts of your business fleet have to adopt them as they are laid out, without any changes. You need to defend these elements with tooth and nail, as they are the pillars of the overall SAP design. Examples are foreign currency handling, supply chain handling, or production process elements that must follow a corporate design.
  • Mandatory, but expandable – You may allow the local business to extend certain pieces of your design in a way in which the result still fits within the corporate vision. Think, for example, about an organizational model where the local business wants to establish a more granular cost center structure than the one given by the template. Adding another marketing cost center or a more detailed work center structure in the production does, in its nature, not deviate from the overall design. It still complies with the spirit of the business design. I would caution you to still look out for Trojan design horses. When appropriate, be lenient in granting these requests.
  • Local – You will never be able to standardize everything. There will be local tax requirements, cultural “need to have’s” related to doing business in a certain country, the one-off odd (but hugely profitable) business in the portfolio–all legitimate reasons why design may need to deviate in a region, country, or line of business. Where advisable, don’t fight it, rather support it. Just make sure that the local deviation stays as the exception, not as the mainstream practice!

This brings us to the conclusion of today’s post about Business Process Design. In our next chapter of the Global Template series, we will talk about technical SAP Systems Environments. As always, thanks for your valuable time today! If you have questions about Global Template that you’d like to see addressed in future posts, we invite you to reach out via Twitter.

SAP Global Template Demystified: Rallying the Troops

Its people are the biggest asset of any company. The same is true when it comes to an SAP Global Template–it is only as good as those who establish and manage the platform. This requires that you keep those key people informed, educated, and involved. Only then can you ensure that they understand the direction, are working toward a common goal, and are ultimately willing to defend the system that has been built.

Quite often the change management impact in an effort as big as rolling out an SAP Global Template is profoundly underestimated. And even if change is generally embraced, that may not be enough to bring people on board. The message has to be clearly spelled out: Change is not the enemy but rather an opportunity, ready to be seized!

SAP Global Template Consultants

Let’s define some meaningful categories of key contributors to get closer to their needs:

People Impacting the Global Template
From executive sponsors who oversee teams implementing the Global Template, to the business people designated to support the implementations, you have to enable them with educated buy-in, access to the right tools, and recognition. And when it comes to recognition, go beyond the handshake! A well-structured incentive program may get your internal resources truly invested in the projects, allowing you to avoid much more expensive external help. In reality, the difference between a lousy and an excellent team meal could be significant motivation to go the extra (hundred) miles!

People Impacted by the Global Template
Try to walk in their shoes instead of telling them how brilliant you are. There is no success without acceptance! Make a distinction between people who accept the new world and the ones who don’t–and treat them all with dignity. Someone may just want to ride the existing state into the sunset, while others are eager to embrace change. You need them all. Don’t alienate them for no good reason! You can accept that someone does not want to go on the SAP trip and may rather choose a different position or retirement. They can still be of great help if you treat them right. Support the willingness to change as much as you can as it will contribute to a smoother, more successful process overall.

People Preserving the Impact of the Global Template
You need to defend what you built, and you cannot leave it to chance. The support team that you install needs to monitor across the board, ensuring the many elements of the Global Template are preserved and truly alive! You need to give them purpose and respect; they are NOT an appendix to the operations, but an essential and critical part of it. It starts with your Center of Excellence, includes the various Business Governance functions, like Master Data Management, and also something that is often forgotten–the harvesting of brilliant ideas to ensure continuous improvement from people in the field who really know what works and what doesn’t within the system.

SAP Global Template Team

When we talk about giving people the tools, it starts with governance of the Global Template project–the do’s and don’ts, and, also, the maybe’s that you need to foster creativity. I have found over the years that it is of utmost importance to define and communicate the boundaries around which people will interact with the Global Template. Consider these categories:

  • Global Must-Have’s – Mandatory and therefore not debatable
  • Global Can-be’s – Extendable, used as add-ons to mandatory settings
  • Local Needs – Elements that are better left to the locals

This ties back to executive messaging reinforcing that these rules are there for a reason. This clarity will help tame the “too-free spirits” in the field and also functions as guardrails, helping people walk by themselves.

In our next chapter we will talk about the Governance tools that should support the effort of creating and deploying your coveted Global Template. As always, thanks for your valuable time today! If you have questions about Global Template that you’d like to see addressed in future posts, we invite you to reach out via Twitter.

SAP Global Template Demystified

Welcome to the first in a new series on the Vortex Consulting blog. Join us over the next few months as we explore the ins and outs of SAP Global Template.

It isn’t about configuration. It isn’t the business process. Nor is it about documentation. It is about all of that and much more. An SAP Global Template (“GT”) is a blueprint to success, a holistic view of all elements of your SAP journey!

To achieve the promise of cost savings, rapid deployment, efficient support, and a solid return on investment, the breadth of standardization must cross the enterprise as a whole, including people, process, and systems.

The challenge is that many consultants, and firms, attempt to give guidance about SAP Global Templates, but only a few truly understand it. When embarking on the exercise, many people quickly realize the complexity and either give up or go only part way. To avoid this frustration and expenditure, you need to plan a GT like a major project, then embed it into your business strategy and long-term deployment plan(s). Finally, it has to be supported with expertise and experience, either in-house or through external advisors.

Vortex Consulting SAP Global Template Guide

Today’s post is the first in a new blog series we are launching. In the coming weeks, we will explore the underpinnings of an SAP Global Template and touch on the topics that need to be considered for standardization. And yes, it’s all about streamlining and standardizing to avoid reinventing the wheel in endless blueprinting sessions. With the concepts we will explore, your team can develop the software fabric that will allow for rapid, agile deployments. This strategic activity will generate acceptance in the organization with a right-sized overall SAP environment that supports the business vision and strategy.

Elements of an SAP Global Template that we will explore in upcoming blog posts:

SAP Global Template Elements

All these elements need to be considered in the context of already existing enterprise IT and business structures. None of them can be seen as a stand-alone effort. Each is a critical part of the foundation that can support the weight of future SAP deployments. When done right, an SAP Global Template can turn a possible burden into an IT strength, leading to a deep acceptance throughout the organization as it generates a “common language” for the deployments of the SAP package across the entire fleet.

Before we end this post, let me take a moment to drill deeper into the idea of a “common language.” This is not a question of whether English is your worldwide project language. It is one of the single most important success factors of your SAP journey. You need to create a dictionary of SAP Global Template business terms and take the utmost care to teach it, reiterate it, and defend it! Yes, you need to defend it until it becomes ingrained into the business DNA! Why? It is difficult enough to bridge a potential gap of languages, cultures, and countless other variables when rolling out an SAP road map across the enterprise. You should not add the unnecessary complications of debating if you refer to a division as a “group” or a “business line.” Clarity minimizes confusion and could literally save millions in wasted dollars.

It is the clarity of thinking strategically, speaking with the vocabulary of convergence, and the holistic inclusion of all aspects that makes an SAP Global Template successful. And you can be the designer of this thriving system, with the help of your trusted advisors. 

Check back next week for the second post in this series, and be sure to follow us on Twitter to stay up to date on all the latest news from the Vortex Consulting team.