Technical Overview

How 123GER works

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.

You define the scenario

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.

Which object to monitor: a delivery, a material, an invoice, a production order, a freight order, or any other SAP object
What condition triggers an alert: overdue by a number of days, a quantity below a threshold, a status that has not changed when it should have
Who gets notified: a specific user, a distribution list, or a role-based group
How often it fires: once when the condition is first met, again each time it persists, or as a daily digest
Minimum volume to trigger: define the number of relevant items required before an alert becomes active.

Browse the Scenario Library →

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 engine monitors your data

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.

No middlewareDirect table reads. No RFC calls to external systems.

No data exportYour SAP data stays in your landscape.

Standard background jobScheduled and managed the same way as any other SAP batch process.

ECC and S/4HANACompatible with all supported SAP releases.

Alerts go out by email and are recorded in SAP

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.

Email notificationA clear message goes to the right inbox immediately, with the SAP object, the condition that was met, and the action that is expected.

Alert recorded in SAPEvery 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.

Assignable: any recorded alert can be assigned to a specific team member directly from the Fiori view
Full history: every past alert is retained and searchable, so your team can trace any situation back to when it was first detected
Recipients are set per scenario and can include individuals, distribution lists, or role-based groups

Manage everything from the Fiori dashboard

123GER includes a dedicated SAP Fiori application. You get a live view of your entire monitoring operation without needing transaction codes or custom reports.

Engine statusA 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.

Scenario tilesEach scenario has its own tile showing its current state and today's trigger count. You can activate or pause a scenario without raising a transport or involving IT.

Business impact123GER records time saved and cost avoided for each trigger. Over time you build a measurable record of what the monitoring has delivered.

Execution logA full run history of the engine. Useful for confirming expected behaviour and for investigating any discrepancies.

From first call to go-live

For an initial set of scenarios, implementation typically takes two to three weeks.

Discovery call

We map your SAP modules, your landscape, and the situations you most want to monitor.

Installation

We install the 123GER engine and your first set of scenarios via a standard SAP transport.

Test in QA

You test against your own data. We fine-tune conditions and message templates together until everything behaves exactly as expected.

Go live

123GER goes into production. The background job is scheduled and alerts are active from day one.