123GER is installed into your SAP system as a standard transport. The engine runs as a background job, reads directly from your tables, and fires when a condition is met. There is no middleware, no external connection, and nothing to maintain outside SAP.
A scenario tells 123GER what to watch for. You do not need to know ABAP or touch any technical configuration. You describe the business situation in plain terms and we take care of the rest.
The library contains 50+ pre-built templates covering the most common SAP exception situations. Pick the ones that apply and we upload them into your engine. If your situation is not there, we build it as a custom scenario.
The 123GER engine runs inside your SAP system as a standard background job. At regular intervals it works through each active scenario, reads the relevant tables, and checks whether any conditions have been met. It does not call external systems and your data does not leave your landscape.
Direct table reads. No RFC calls to external systems.
Your SAP data stays in your landscape.
Scheduled and managed the same way as any other SAP batch process.
Compatible with all supported SAP releases and current status.
When a scenario fires, 123GER sends an email to the right person and writes a record to a dedicated table inside your SAP system. Both happen at the same time, without any manual step.
A clear message goes to the right inbox immediately, with the SAP object, the condition that was met, and the action that is expected.
Every occurrence is written to a 123GER table inside your system. The record includes the trigger name, exact timestamp, application server, user, client, and current status.
123GER includes a dedicated SAP Fiori application. You get a live view of your entire monitoring operation without needing transaction codes or custom reports.
A single tile shows whether the engine is running, when it last executed, and whether there are any errors. You can switch it on or off directly from Fiori.
Each scenario has its own tile showing its current state and today's trigger count. You can activate or pause a scenario without opening a transport or invoking IT.
123GER records time saved and cost avoided for each trigger. Over time you build a measurable record of what the monitoring has delivered.
A full run history of the engine. Useful for confirming expected behaviour and for investigating any discrepancies.
For an initial set of scenarios, implementation typically takes two to three weeks.
We map your SAP landscape, your modules, and the situations you most want to monitor.
We install the 123GER engine and your first set of scenarios via a standard SAP transport.
You test against your own conditions and manage templates together until everything behaves exactly as expected.
123GER goes into production. The background job is scheduled and alerts are active from day one.