Expert Knowledge on Digitalization & Automation of Business Processes
Topic: AP Automation | S/4HANA | Cloud
For years, many SAP user companies have relied on add-on solutions to enhance and extend standard SAP functionality. When selecting these solutions, particularly for invoice processing, two key criteria were traditionally considered essential:
These two factors were standard requirements in nearly every RFP (Request for Proposal) for selecting a workflow system. However, the rise of Clean Core and cloud computing has led to a paradigm shift, which is clearly reflected in this area. Deep SAP integration contradicts the Clean Core approach. Additionally, due to the cloud’s rapid innovation cycles, certifications now have a much shorter validity period. SAP users must now reconsider their criteria when selecting a workflow solution for S/4HANA.
SAP’s Clean Core approach advocates keeping the system core untouched. Deep integration, on the other hand, involves direct modifications to the core, which contradicts this principle. However, there are ways to address—or at least mitigate—this contradiction. If an add-on solution is developed according to SAP’s specifications and utilizes approved technologies (e.g., ABAP Cloud instead of classic ABAP), SAP can issue a certification confirming its compatibility with S/4HANA. As a result, such integrated solutions remain viable and supported.
A more elegant approach recommended by SAP is to opt for “side-by-side” solutions instead. These solutions are not embedded within the SAP system but are connected via SAP Business Technology Platform (SAP BTP). This ensures that the system core remains clean while still enabling extensions and customizations of the SAP standard. However, there is a caveat: The availability of solutions supporting this approach is still somewhat limited. Consequently, SAP user companies must assess their needs on a case-by-case basis—some areas may still require an SAP-integrated solution, while others are better suited for an SAP BTP-connected approach.
SAP certifications have traditionally been valid for three years, and this remains unchanged with S/4HANA. However, what has changed is the accelerated pace of cloud-driven updates. New versions of S/4HANA Cloud Private Edition are released annually, while updates in the public cloud occur even more frequently. As a result, certifications for specific versions of S/4HANA can quickly become outdated.
Moreover, there is no single certification that applies universally across all (cloud) models of S/4HANA. Instead, separate certifications exist for RISE with SAP, GROW with SAP, Clean Core, S/4HANA, S/4HANA Cloud, and more. This fragmentation makes it challenging for SAP users to determine which certification is truly relevant to their specific scenario. Simply checking the “SAP-certified” box is no longer a sufficient selection criterion.
If you are evaluating workflow solutions for SAP, consider these key questions to ask vendors:
With the shift to Clean Core and cloud-based architectures, SAP users must take a more nuanced approach when selecting invoice workflow solutions. Understanding the implications of integration models and certifications is now more important than ever to ensure long-term compatibility and sustainability.