Meister introduces the concept of predictive caching where the traversal of condition control tables and respective catalog materials is done using its own proprietary algorithms to provide a disruptive solution to the performance challenge of populating external applications with complex, yet dynamic data (like materials pricing and ATP) in realtime upon the start of external transactional process of creating new transaction that involves a consumption of such data (like sales order). Meister also introduces a disruptive approach that includes a preemptive caching engine using “Do Ahead” method where ML-based processes detect first what the usage pattern is of that specific user that just logged into the system. That user has a pattern of creating SAP documents with specific permutations. Based on that discovery the engine will “bucket” preconstructed SAP documents with all relations and related temp tables in place, saving up to 80% of the time to create such documents with ANY volume of line items.

Way more than “just a connector,” the Meister platform is the foundation for the development of many state-of-the-art applications and 3^rd party integrations for SAP users. It easily bolts on to other software offerings and is the only technology that directly connects to the SAP backend. Core to this is a sophisticated and comprehensive real-time cross compiler that compiles REST JSON data to ABAP internal data structures (and vice versa!) for high volume, high-speed data transactions, allowing direct connectivity into your world of web-based applications.

Workflow enablement is accomplished via Meister’s Workflow Foundation support. Meister provides the toolkit for the enablement of an existing SAP workflow as an endpoint accessible by any UX via the SDK website. Meister provides a class to be added as part of the header of the workflow definition at SAP. Once injected into the header of the workflow, all the events fired by SAP to the runtime instance of the workflow definition are trapped by Meister and provided as part of the development effort for specific needs. By default, six discrete events are trapped by Meister and made available as BADI extensions that are easily enhanced by the ABAP resources. Meister also exposes an endpoint named Meister.MWF.Decider to execute any decision task of workflows whether Meister was injected or not to the workflow definition file.