Why Years of SAP ERP Experience Makes Me Question if You Really Need That Custom Code

There is a joke that those of us with a few years of SAP ERP experience tell:

“If you believe you need to create custom SAP ABAP code to meet the business requirement, chances are you don’t understand the business requirement. And if, after further consideration, you still think you need custom SAP ABAP code to meet your requirement, you still don’t understand the requirement.”

Now that might sound harsh, but the reality is that if, after 30+ years, the number one ERP software provider doesn’t have embedded in their current S/4HANA solution the ability to meet a requirement without custom code, that’s a sign to reconsider what’s really needed. On one hand, maybe you don’t have a complete understanding of what SAP S/4HANA is capable of. On the other hand, maybe your business requirement needs a good revisit by a seasoned pro with some major SAP ERP experience.

With SAP’s GROW and RISE initiatives, which prescribe the installation of the S/4HANA ERP system outside of your own data center, there is minimal opportunity (if any at all) to just “cut code.”

Some have implied that SAP’s attempts to limit code cutting is a mean act. Image shows computer code It’s worth briefly calling out why this is better described as “giving us bitter medicine” as opposed to being an act of bullying.

S/4HANA and its predecessors are business applications mostly written in SAP’s development language ABAP. ABAP was initially described and truly was, similar to COBOL (Common Business Oriented Language) in that it was intended to be used for authoring business applications with minimal development experience. Given that SAP themselves were enhancing their ERP application and supporting new technologies (e.g. web browsers), the ABAP language evolved from its roots, with enhancements supporting object orientation constructs and much more.

Simultaneously, SAP was very unique among software vendors where the source code of their business applications were not just readable by their customers, but permitted them to not only build new reports and transactions but also author ABAP code to run within SAP’s own developed applications. This allowed SAP, along with their implementation partners and clients, to enhance SAP to meet essentially all possible business requirements. This access to nearly limitless customization undoubtedly contributed to the rapid adoption of SAP and the emergence of an ERP implementation industry where everyone could get what they wanted.

But then, two things happened.

First, SAP kept building. Through acquisitions and internal development, SAP has built extensive capabilities into their core ERP solution as well as applications such as SAP TMS, eWM, etc. SAP has also developed the ability to build applications outside of core S/4 ERP solutions through environments such as SAP BTP, or through very robust APIs (Application Programming Interfaces). The sheer list of capabilities is exhausting to review.

Second–and this one might be hard for some SAP experts to admit–integrators got lazy. Through implementation after implementation, many integrators with SAP ERP experience simply ”threw code” at requirements. In many scenarios, those requirements would have been completely satisfied by standard functionality if there was awareness. The remainder of the scenarios would have been addressed by changing how the business requirement is addressed.

A lot of that custom code stemming from so-called “‘lazy” implementations has stranded many existing SAP ERP systems in the past. The custom code often doesn’t work with the latest enhancement packs or S/4HANA, and justification to unwind custom code can be hard to make. The ironic part is that the custom code might not have been required in the first place if the business requirement was properly addressed with out-of-the-box functionality from SAP.

Sentence on how SAP ERP experts recommend meeting business requirements

An SAP project should have never been, but now is no longer reliant on an army of ABAP developers. Its success depends on having knowledgeable resources who deeply understand the S/4HANA module and other available SAP and non-SAP solutions and who are extremely comfortable in working with business requirements.

Reviewing and redesigning business processes to align them to standard SAP S/4 functionality is a core competency of the Vortex Consulting team. With over 25 years of SAP ERP experience under our belt, we’ve monitored passing trends and strengthened our approach to long-lasting ERP performance that is made to evolve and adapt as our clients’ needs change, too. Send us a message to learn more about how we can support your business.

 

About the Author: Matthew Montano is a Vortex Consulting SAP architect with more than 25 years of experienceSAP Architect Matthew Montano in Electronic Data Interchange, Supply Chain Integration, and Third-Party Logistics. His passion for good documentation and streamlined work process has yielded measurable results for clients in the consumer packaged goods, life sciences, manufacturing, and transportation industries across both the United States and Canada. Keep checking in for his “Musings with Uncle Matthew” series on the Vortex Consulting blog.

SAP GRC: Digital Transformation Series, Part III

Today we continue our blog series on digital transformation. (For an overview on the topic, be sure to check out the first post in the series.) In our most recent post, we walked through 2 of 4 key areas to consider when it comes to digital transformation: Network security and SAP capabilities. Now, let’s take a look at the remaining key areas: Governance, risk management, and compliance–collectively known as GRC–and physical security. 

Consider these 3 main components to GRC: SAP Security, SAP Early Watch (pattern recognition), and Audit. Another way to think about GRC is establishing logical boundaries around roles and responsibilities and each employee’s related system access. In other words, no single person can complete all steps in the process. Here’s an example: If you cut the purchase order, you cannot be the one who approves the payment.

GRC can be difficult to design, implement, SAP GRC Best Practices for Business Securityand maintain successfully. It requires someone–or a team–with experience. You need to ensure that the right people have the right access to be able to do their jobs. At the same time, it is vital that the “slice of the pie” each employee sees is necessary to their role, defined, and secured. Also, this is not a “one and done” scenario. As the business evolves and changes, so do the roles and the unique access that each of the roles has within the organization. Strategic role design and maintenance is an ongoing process which is critical to the security of your organization.

Uniquely, the concern around establishing best practices in GRC is not about “getting hacked,” as it is for many aspects of digital business management. The focus is on limiting scenarios where someone may see a vulnerability and use it to defraud you. Controlling employee access is critical to limit opportunities for fraudulent behavior– but that access control is not limited to only employees.

In today’s interconnected environment, your vendors, suppliers, and customers may all have access points into your system. These access points all need security roles assigned to them to limit the view to only the appropriate and relevant information for the actor’s role. As an example, an external actor could see proprietary information and sell it to a competitor. Each partner or vendor should only see what is most relevant to and required for their specific role in the larger process.

Within your organization’s SAP framework, BPML–Business Process Mapping List–establishes employee and vendor access. GRC creates profiles in such a way that it encircles all relevant functionality before linking that role to a person. The truth of the matter is that many companies give people way too much access by accident!

GRC SAP Digital and Physical SecurityStandard SAP GRC risk detection and auditing settings compile reports and grant access to internal and external audits. This allows pattern recognition functionality to detect where key elements of your security infrastructure may have changed unexpectedly or where other gaps in the system may exist.

That brings us to Number 4: physical security. Identification procedures fall into this category–being sure that someone cannot get in, pretending to be someone they are not. Along those lines, when a consultant’s contract ends, it’s crucial to lock out their access immediately so that they can no longer access the premises, or the sensitive systems inside the premises. Whether you are building from the ground up, undergoing an expansion, or moving to a “new to you” space, make physical security a part of the discussion upfront.

As explored through our 3-part series, digital transformation and security is a broad-reaching topic that weaves into all aspects of your business. A successful digital ERP implementation or upgrade is based on a holistic view of security structure including external partners, project teams, and internal resources. Invest in bringing together these moving pieces to ensure a secure digital and physical environment for your organization’s assets. If you have questions about digital upgrades in SAP and Oracle, want to talk about staffing support options, or even need to fill a role immediately, be sure to contact us today. We look forward to helping you optimize your business operations as the digital world continues to grow and evolve.

Network Security & SAP Capabilities: Digital Transformation Series, Part II

Welcome to the second post in our blog series on digital transformation. As mentioned in our series kickoff, digital transformation security can be divided into four key areas: network security, SAP capabilities, SAP GRC (roles and access), and physical security. Let’s dive right into what those categories include, beginning with network security.

If you were to bring up the topic of technological security with a group of colleagues, chances are it’s network security that would first come up in discussion. Intrusion and phishing are a few of the main areas that fall into this category. In the case of intrusion, we’re talking about the detection of network entry without proper authorization. And, unfortunately, we’ve all seen phishing in action–fraudulent messages that seek to obtain personal, valuable information, and designed to look as though they were from a reputable organization. In order to maintain a truly secure system, all access points into your network, such as VPNs, need to be secured. The Vortex team is very aware of these threats and makes network security an integral part of every project, whether that’s including our own security experts in a full staffing scenario or collaborating with your on-staff security team during an SAP setup or upgrade.

This brings us to the second key area of digital security–SAP capabilities, our sweet spot. A core feature of SAP is that it helps to establish baseline security patterns, then detects when there are variations from those base guidelines. SAP is loaded with inherent process-based security capabilities that work toward detecting and preventing fraud and architecture issues:

  • Optical Scanning Tools, used in tandem with AI for managing and securing invoicing practices
  • Dispute Management tools for detecting irregularities in disputes or payments
  • Quality Management and audits for dealing with claims that there is an issue with your product quality
  • Accounts Receivable and Incoming Payments tools for analyzing who you owe and who owes you
  • Tools for detecting Internal Issues, such as identifying “bad apples” who may be trying to defraud the company
  • Tools for detecting Money Routing Irregularities by visualizing patterns where company money is moving

Machines and systems can recognize patterns in a way that humans cannot. Humans have the ingenuity, once these critical pieces of information are identified, to see things from different angles and make sense of situational information based on experience and expertise. It’s the experience of our senior leadership team and vast network of consultants that allows Vortex to recognize capabilities and apply them in unique ways for the benefit of our clients.

Network security and SAP capabilities are 2 of the 4 critical areas SAP Cloud symbol for network securitycomprising your holistic security architecture, and when discussing these, there’s another topic that cannot be excluded from the conversation–understanding security of cloud vs. on-premise. Simply said, the more you go on-premise with your SAP investment, the more SAP performance ability you give up. The powerful SAP cloud platform has stronger capabilities and is a sound, secure choice for your business in the long term.

What questions do you have about network security for SAP? Drop us a line or reach out on social media: LinkedIn and Twitter. Tune in for the next in our series on digital transformation security, where we’ll discuss GRC and physical security, coming soon here on the Vortex Consulting blog. 

Digital Transformation Security Goes Beyond Network Security

Digital transformation is a hot topic these days–but in reality it’s not a new one. Professionals in the ERP technology space have been moving businesses from old technology platforms to cutting edge software for over 30 years. Here at Vortex Consulting, we’ve been in business for 25 years, working in digital transformation–as seen in products like Oracle Cloud and SAP S/4HANA. Continue reading this first blog post in our new series and follow along for others in the upcoming months.

So why has research and development surrounding digital transformation been deemed so critical for over 3 decades? A key reason: efficiency. Digitizing workflow, storage, and processes in general means eliminating time-consuming, repetitive, inefficient tasks. It brings meaningful and successful automation to standard business processes, all while integrating data efficiently. As an example, let’s look at the process of invoicing. Long gone are the days of needing to manually scan an invoice, organize paper files, collect and match up payments, etc. All of this can be done digitally–it’s streamlined, takes less time and energy, and frees up employees to do more valuable work. Product orders are even transferred to third party logistics providers who automatically determine the most efficient delivery routes, can combine loads, and automatically select the lowest cost delivery options. 

Business owner with SAP compares low cost delivery options

There are newer technologies coming into play that add to the discussion of what is possible in digital transformation. The Internet of things (IoT), artificial intelligence (AI), data lakes, and improved pattern detection capabilities are each transformative in their own right. At the time of publishing this post, discussions about AI are dominating social spaces as its uses are tested in education, healthcare, information management, and beyond. 

Female business owner monitors SAP digital transformation

As application specialists, Vortex works in the realm of these digital technologies on every project. The SAP platform is at the core of the system, with SAP and third party satellites communicating as a network, enabling automation and digital flows of information–all of which must be secured. (Our work with Oracle-based clients functions in a similar way.) Adding to the complexity of the situation, there are always evolving technologies which require the integration of handheld devices, sensors, and portals that extend the network and must be integrated into SAP. With the introduction of more middleware tools to the SAP setup, those assets must be secured as well.

When it comes to digital transformation security, we’ve learned there are really 4 buckets: network security, SAP capabilities, SAP GRC (roles and access), and physical security. Throughout this blog post series, we’ll take a deep dive into each of those key areas. If you have questions you’d like us to address, reach out on Twitter or send an email to let us know. Watch for the next in our digital transformation security series soon.

How to Start your S/4 HANA Journey: Operations First

From guest author Sven Wierzbicki. The fourth in our blog series on “How to Start your SAP S/4HANA Journey.”

You confront your challenges head on. You do not shy away from open heart surgery. You trust your ability to initiate and manage fundamental change. Welcome to the S/4HANA implementation option of “Operations First.

Most companies, even the ones that had a rough SAP R/3 implementation, will finally get to the happy place where they have a stabilized ERP platform that meets the needs of their business operations. Can you call them out for trying to stay in their perceived “ROI zone?” 

These companies may feel much more at home with options to implement BW/4HANA or S/4HANA Central Finance before turning their operations upside down. 

There is, however, a different school of thought that exists. It subscribes to the idea to go after supporting the fundamentals of the business in the most advanced way possible. In the end, it does not matter how they arrive at the conclusion. What matters is that they right-size the effort to implement S/4HANA, by one of two options:

  • Shorten the period of parallel operations: When a company is centralized in its nature, it may make sense to strive for a shorter period of overlap between the R/3 sunset horizon and rise of the new S/4HANA star. If palatable, the idea of a big bang, or a small series of big bangs, should be the centerpiece of the digital transformation road map.
  • Or, extend the period of parallel operations: When the diversity of operations, the geography, or the limited appetite/funds dictate to refrain from doing “big bites,” an S/4HANA seed approach may be better. Acknowledge that you cannot do it all at once, and pick the right representative/business to be the seed for the future business template in S/4. Implement in reasonable chunks–with bigger steps–once experience gains traction.

Regardless of which way you go, never bite off more than you can chew. Doing so only sets you up for disappointment. Embracing the new functionality should be exciting for your business–especially those seen in Finance. Success should be experienced all along the journey!

So, which steps can you take to right-size your “Operations First” effort to implement S/4HANA? Let’s explore some key elements to avoid diving into an abyss:

  • Deployment Strategy – Build a road map that is custom fit to your company’s means and capabilities. Don’t shy away from tackling the S/4HANA journey; do, however, avoid overstretching your IT and business organization. Find a suitable seed business that fits your needs and go to the starting block. Do not wait too long, as there is still the R/3 sunset looming; you do not want to be pressured into a decision that may force your hand!
  • There is No Upgrade – We all like good news. That’s why it’s tempting to listen to relentless ‘experts’ claiming to have the tools “to make the upgrade easy.” The thing is, there is no true upgrade for the Business Suite. Yes, the technical HANA DB can be upgraded, but the functionality must be implemented anew. You may not need to reinvent the wheel–but see this upgrade as an opportunity to shed some of the snakeskin that is too tight, that you have outgrown!
  • Change is Inevitable – While it is undeniable that the knowledge of the S/4HANA product and its application to your business plays a big role, the Change Management aspect is even more important. You need to create a readiness for the project, within the C-suite, business, and IT organization, and choose a partner that you can trust. You will find that a well-prepared organization is, in the end, more important than a technical approach to the journey!

In closing, I want to reiterate that Vortex can be the trusted partner on your S/4HANA journey. Why? Because of the experts who can address the points raised above: 

  • Strategic Advisors who work with your senior management and help to build the S/4HANA roadmap and your Global Template based on real-life experience
  • Operations Experts in warehousing, manufacturing, supply chain finance, and more; who have worked in these key industries before becoming SAP consultants
  • IT Experts who translate business needs into programming of interfaces or add-ons, create BI applications, and much more

This concludes our blog series on choosing an approach to your organization’s SAP S/4HANA upgrade. Click through the links below to read the other blog posts in the series. We hope you find these insights helpful as you consider your best step forward. To learn more about how Vortex can be your main resource in this vital investment, contact us at 1.888.627.3640 or sales@vortexconsulting.net. 

#1: How to Start Your SAP S/4HANA Journey: Three Unique Approaches

#2: How to Start Your SAP S/4HANA Journey: Insight First

#3: How to Start Your SAP S/4HANA Journey: Central Finance First

How to Start your S/4 HANA Journey: Central Finance First

From guest author Sven Wierzbicki. The third in our blog series on “How to Start your SAP S/4HANA Journey.”

Let’s say you live on the banks of the powerful river of doubts. You know there is a new world on the other side of the river–and one way to get there is by building a bridge! This bridge needs to be strong, architected to last. It has to be founded in modern technology to carry the road to the new world. Well, SAP Central Finance can be your bridge to S/4HANA! Today’s post will focus on bridging the gap between seamless operations and painless innovations …

It is completely understandable that organizations want to embrace stability of their R/3 systems as long as they can. There are many factors playing into this notion, from limited budgets over avoiding the bleeding edge to simply the fear of making the wrong decision. The list of deterrents is lengthy. Also, the road map to S/4HANA needs to put a construct in place that lasts for 15-20 years to come. 

That’s where SAP Central Finance comes into the picture:

SAP S/4HANA Central Finance Options

Photo credit: SAP

 

Implementing something that supplements, rather than disrupts, operations can be a good option to “dip the toe,” so to speak, instead of making a big splash. Central Finance can be that sidecar solution that exposes the IT organization to the new technology. The benefits are certainly worth mentioning: it provides an excellent learning opportunity, contributes to the building up of an experienced resource, and creates a strong new foundation, while at the same time delivering new capabilities to the business.

Consider the following tangible benefits of SAP Central Finance:

  1. Systems Harmonization & Data Intake – Assuming that you have a systems environment that contains both SAP and non-SAP systems, SAP Central Finance offers a place to harmonize and centralize your financial data across the entire organization, with simplified and standardized interfaces and a robust platform for data transformation. It gives you the ability to elevate the level of systems integration after the fact, providing a cleaner set of data for central planning, processing, reporting, and financial consolidations.
  1. Reporting Capabilities – Regardless of the limited or diverse capabilities of the operational ERP systems, you can create homogeneous financial reporting by utilizing the strength of the new unified journal, enabling centralized profitability and profit center reporting right out of the box. Beyond that, the now harmonized data set can serve as input to the more sophisticated Business Intelligence tool sets like BW or BPC.
  1. Operational Centralization – While not yet perfect, the Central Finance system already has multiple functions available that play right into the concepts of shared services and business optimization. Noteworthy are the central payment option and certain tax features like tax withholding for centralized payments. 

Allow Vortex Consulting to assist you in implementing your SAP Central Finance system. We can help you start your S/4HANA journey without breaking the bank, focusing on these key actions:

  • Building a bridge to the new world of the S/4HANA technology
  • Educating your IT staff on the new capabilities and functionality
  • Delivering meaningful business features to your finance department & C-suite

In our next post, we’ll address the “Operations First” option for an SAP S/4HANA implementation, talking about a head-on approach that uses operations as the starting point. Click here to catch up on our first post in the series, “How to Start Your SAP S/4HANA Journey: Three Unique Approaches.” And be sure to get involved in the conversation on Twitter–you’ll find us here: https://twitter.com/VortexConsultng.

How to Start your SAP S/4HANA Journey: Three Unique Approaches

From guest authors Sven Wierzbicki and John Louw

If you’ve had the great fortune to travel around Maui, you know that the road to Hana is unique indeed. It is a winding stretch of astonishing beauty that rewards you all along the way. And with the right approach, your road to SAP S/4HANA could be a beautiful journey as well. See it as a rewarding experience from the start, and you will begin to harvest the benefits well before reaching the end point. It all comes down to planning your road map the right way…

Road to Hana Blog Post

Let’s face it–even with the recent pushback of the SAP R/3 ERP sunset, companies need to start planning a cost-efficient road map that has an individualized return of investment in mind. Today’s CIOs are held much more accountable for the way they stretch their budget–especially during the current health crisis, which has created additional budget strains.

When implementing SAP S/4HANA, you will be required to make sizable decisions. These decisions, and a chain of related movements and consequences, are much more significant to the current IT environment than simply selecting a new software that delivers additional capabilities. Initially, you’ll need to choose the organization’s approach to SAP S/4HANA implementation. Strategy comes into play big time as the approach you establish from day one touches the very underpinnings of the systems, their databases, and the hardware. It needs to touch on information security, cloud deployment, license acquisition, and systems selection, to name just some of the key aspects of the larger road map.

It’s easy to get lost in a topic as big as “SAP S/4HANA Implementation.” Today we focus on 3 potential options to embark on an S/4HANA deployment that make sense, are digestible for the organization, and can be achieved with relative speed and agility.

Let us explore these three potential choices to start your S/4HANA journey:

  1. Insight First – With an “Insight First” approach, you start with planning and consolidations. Either upgrade the existing BW and BPC environment, or start deploying an SAP-centric solution, choosing the most desirable way to get to better enterprise insight. It could be an existing on-premise BW solution that runs on S/4HANA, a BW/4HANA solution, the inclusion of SAP Analytics Cloud, or any hybrid of these tolls. Business Intelligence is the main driver to S/4HANA on this path.
  1. Central Finance First – Some take this approach as a way to dip their toe in, gain confidence, and build a solid backbone in preparation for future acquisitions. The “Central Finance First” method establishes the opportunity for data collection that combines SAP and non-SAP systems. This approach enables your IT department to become experts in the S/4HANA world before remodeling the operations, establishing a strategic approach to embarking on the journey that avoids overburdening the enterprise. 
  1. Operations First – There are a number of approaches out there with colorful names, from greenfield, to brownfield, to bluefield. Detailed information on each can easily be found online. In our upcoming “Operations First” blog post, we will focus on rightsizing the effort to make it part of a road map that can be sustained in parallel to an existing ERP R/3–pacing it right is a centerpiece of the approach.

Today’s blog post is the first in our series on selecting an approach to the SAP S/4HANA journey. Over the next several weeks we’ll outline the three options listed above in greater detail. You can also check out our recent blog post on why experience matters on the road to S/4HANA. Stay tuned for the next chapter in our SAP S/4HANA series. We thank you for your valuable time!

Why Experience Matters on Your Road to S/4HANA

I get it. We cannot indulge in yesterday’s ideas. We need fresh thinking to embrace the challenges of the new world we are living in. Machine learning, artificial intelligence, blockchain, and cloud–all things that did not matter that much when R/3 was introduced. Now they do matter–a whole lot–and they’ll play a big role in your road map to S/4HANA.

Let’s take a moment to recall the transition from R/2 to R/3 and all the hype that drew tidal waves of new consultants into the workforce. As I recall, it was an undeniable benefit to know the table names, the transaction codes, the base concepts that were at the core of the SAP package. The experienced consultants had a substantial edge over the newcomers–the status of the veteran SAP road warriors becoming immortalized by the coining of the “Platinum” distinction. 

SAP S4 HANA Consultant with Upgrade Experience

What does that mean in today’s terms? Does it still have meaning when talking about the road to S/4HANA? Yes, I am convinced it does! Consider this:

  1. Strategy – The journey you are about to embark on will stretch over the next two decades. S/4HANA will be around for about 20 years to come, and the tracks you lay and the switches you build will define your path substantially for the short- and medium-term future. You want to avoid costly dead-end streets, redos, and endless construction sites by putting a solid road map in place, based on a mix of strategy that is rooted in experience paired with new, fresh thinking that can lead you into the future. 
  1. Experience – As exciting as it may appear, not every wheel needs to be reinvented. Some of the new functionality in S/4HANA needs to be questioned for usefulness. Take the banking configuration that forced you to go into Fiori for no good reason–SAP got the feedback from experience in the market and brought the good old transaction code back.
  1. Insight – You had to be there before to truly understand things. To appreciate the deeper sense of the very thing in front of your eyes, you might want to have seen it before! Not everything entertains the idea of love at first sight, and not everything that is blissfully charming at first sight is the right thing for your business in the long run. Insight comes with experience.
  1. Results – You may enjoy teaching and training new resources, but it should be your resources and not the ones of your systems integration partner. When working with seasoned resources that made the transition to the S/4 world you will find a willingness to see things through, paired with experience–and success stories–from having done it before.  
SAP Consultants with S/4 HANA Upgrade Experience

In my opinion, it makes good sense to consider an SAP provider like Vortex that can be a partner on your journey to S/4HANA. We bring pre-screened, experienced resources to the table who understand the strategic aspects of your business and the hands-on elements of the S/4HANA package, and who have demonstrated knowledge out in the field. All of our people have 10+ years of experience in SAP, many of them with even 20 or more years.

Neither old nor new is good or bad by itself. But think about the effort that the experienced consultants have put in to reinvent themselves as new S/4HANA implementers. You want this determination on your side when the weather turns bad and the sea gets rough! You are the captain, and you need an advisor at your side who knows the cliffs by heart. Give us a call and we’ll help you navigate whatever challenges lie ahead.

Comparing SAP BPC and S/4HANA Implementation Options

There are many variables when it comes to understanding SAP BPC and S/4HANA implementation options. Today’s blog post is from guest author Johannes Le Roux, an SAP HANA Architect at Infogility. Join us as he walks through the basics:

In 2015, SAP launched its latest data management solution, SAP Business Planning and Consolidation (BPC). It was designed to operate seamlessly on SAP’s latest ERP platform, S/4HANA.

Before we delve into the options for SAP BPC and S/4HANA implementation, let’s quickly recap a few of the main benefits to this groundbreaking approach to data management: 

  • Real-time data access
  • Fast data load time and overall processing
  • Changes are implemented to core data, ensuring all sourcing comes from a single, centralized data pool

Option 1: New Implementation

Whether your organization is running on SAP or another ERP, implementing a new instance on SAP S/4HANA is an enticing option. Making the move to SAP’s most modern platform allows you the opportunity to realign and optimize existing business processes. If you have highly complex customizations that were built in years past, it’s likely that we can streamline and simplify those setups in a modern platform. Creation of a new SAP environment provides an opportunity to purge outdated data and establish a clean and well-structured data foundation for forward movement and growth. This environment can be developed either on-premise or in the cloud, depending on the unique resources and needs of your business. 

SAP BPC and S/4HANA Implementation Option 1: New implementation on-premise or cloud

Option 2: Landscape Transformation

Landscape transformation is ideal for those organizations with an existing SAP landscape, or even multiple systems–whether distributed regionally or in one central location. Alternatively, it enables large organizations to extract specific entities or business processes from the larger environment and establish them in a standalone SAP S/4HANA setup. Outdated or overly complex business processes benefit from the simplification and development of a “clean slate.”

SAP BPC and S/4HANA Implementation Option 2: Landscape transformation on-premise or cloud

Option 3: System Conversion / Migration

Some customers seeking an SAP BPC and S/4 HANA implementation simply want to convert an existing SAP ERP system to SAP’s most modern platform. A system conversion, which establishes a new on-premise or cloud-based S/4HANA environment, is the ideal option for organizations in this position. Using SAP’s migration tools, business data and configuration are managed to ensure a seamless transition.

SAP BPC and S/4HANA Implementation Option 3: System conversion or migration from an existing ERP system

Option 4: Migration to New General Ledger (G/L)

Finally, there are businesses operating with a classic General Ledger that are ready to take advantage of the benefits offered by SAP S/4HANA Finance. This process may take place through the use of SAP’s General Ledger Migration Service or through the activation of a parallel ledger and document splitting strategy. A customized approach will ensure data streams and financial management functions remain in order throughout.

Initiating an SAP BPC and S/4HANA Implementation

Choosing to move forward with an SAP BPC and S/4HANA implementation is a strategic decision that will benefit your business. As technology and the business landscape continues to change, your ERP environment will be set up to outperform outdated systems. SAP has been a leader for decades, and with its latest launch of cutting edge ERP solutions, it has once again demonstrated that it will continue to be an industry leader for years to come.

Contact us today to learn more about your options for an SAP BPC and S/4HANA implementation and other SAP solutions.