When SAP Intake Spills Outside the System
CIOREVIEW >> SAP >> NEWS

When SAP Intake Spills Outside the System

CIO Review

The SAP system can stay the transactional core, but the trigger for its actions comes from elsewhere. Purchase professionals receive requests via e-mail or instant messaging services and recreate context within the SAP system, where decisions have already been made. Spreadsheets can serve as yet another medium. The issue is not in the lack of functionality but rather in the difference between the official business process and the actual channels used by employees. A truly native SAP-based intake and orchestration tool will help to bridge that gap without requiring users to keep yet another system of records and abandon the controls that were built within SAP.

It is important to analyze native integration because "integrated" can imply different architectural models. It is possible to have a separate portal communicating with SAP periodically and thus create duplicates of data, additional middleware, or even a time delay between the request and its execution. The buyer needs to understand where the data of the request is located and how soon the updates in statuses become visible in SAP. Moreover, one needs to know how a change in the approval step, master data rule, routing criteria or other exceptions is implemented. The more integrated the orchestration layer with the SAP context remains, the less work the IT department will have to synchronize process logic. Design of deployment is critical for the S/4HANA upgrade as well. Extensions allowing for maintaining the integrity of the ERP system and minimizing replication will decrease the number of technologies to be revalidated.

“ConvergentIS keeps Rio connected to SAP while extending intake across email and chat, reducing the need for another front-end portal.”

Configurability is also critical for another reason. Organizations do not have just one intake pattern, but developing a custom solution for each procurement or supply chain issue will undo all the progress made through the use of such a platform. What would make more sense is to have a scalable foundation for the organization that allows changing the workflow behavior without creating another set of one-offs. In other words, executives need to evaluate the ability to change form and routing configurations without compromising the governance that should remain consistent across all use cases.

User adoption is also practical. Employees are going to keep communicating by email and chat when another path for request submission complicates their workflows. What is supposed to help is a solution that gets close to the point of submitting a request and then takes the request into managed enterprise processes. While artificial intelligence could help with the classification of a request or decision on what to do next, there are limits to the usage of AI solutions. There should be an audit trail, business rules should be transparent, and IT should control all actions of the system.

ConvergentIS creates the platform called Rio, which is configurable and designed to be natively integrated with SAP to address repetitive gaps within the process rather than building an additional customized solution every time. ConvergentIS will keep Rio integrated with SAP, but extend the intake capabilities to emails and chats. In this way, another front-end portal is not required. At the same time, its architecture enables reuse within different processes while SAP is still coordinated with the whole range of information used in the workflow. Therefore, this option solves the problems discussed above and still ensures user adoption via familiar interfaces. If companies need intake and orchestration to stay in SAP but broaden the ways in which it can be accomplished, they should pay attention to ConvergentIS.