Business Process Monitoring for SAP (Configure)

⚙️ Configure Business-Process Monitoring for SAP

Configure GermainUX to measure the execution, duration, completion, abandonment, and efficiency of SAP business processes.

Business processes are constructed from events collected through RUM JS, the GermainUX Engine, synthetic scenarios, or custom integrations. GermainUX can analyze only the workflow steps represented by the available telemetry.

📋 Prerequisites

Before configuring a business process:

📡 Event sources

GermainUX does not automatically observe undocumented SAP internals. Backend process steps require an accessible and configured source.

🔍 Select the process

Start with a process that has clear business value and observable steps.

💡 SAP business-process examples

Potential processes include:

🛒 SAP Commerce Cloud examples

For SAP Commerce Cloud, formerly SAP Hybris, potential processes include:

The exact process must reflect the application’s actual event flow.

🔧 Define the business process

Go to:

Germain Workspace > Analytics > Business Processes

Create or select the SAP business process.

Configure:

Use a clear name such as:

SAP Purchase Requisition
SAP Invoice Approval
SAP Sales Order Entry
SAP Commerce Checkout

✅ Define the start and completion

▶️ Start condition

The start condition identifies when a process instance begins.

Examples include:

Avoid starting the process on a generic login or page view unless it reliably represents process intent.

🏁 Completion condition

The completion condition identifies successful business completion.

Examples include:

A successful click or HTTP status does not necessarily prove that the business process completed. Use the strongest available business-success evidence.

📝 Configure the process steps

Define every observable step required for analysis.

Example:

For each step, configure:

Use business-oriented names rather than raw URLs, element IDs, or API paths.

🔍 Configure correlation

Correlation determines which events belong to the same process instance.

Potential identifiers include:

Session-based correlation

Use session correlation when the complete process occurs within one browser session.

This is suitable for processes derived primarily from RUM events.

Identifier-based correlation

Use an approved transaction or document identifier when the process:

Do not collect sensitive identifiers unless necessary and approved. Mask or hash them when the original value is not required.

Time-based correlation

Time proximity can support analysis but is not reliable proof that two events belong to the same process.

Use time-based correlation only when stronger identifiers are unavailable, and document its limitations.

🔁 Configure alternative paths

SAP processes frequently contain valid variations.

Configure:

Do not classify every deviation from one ideal sequence as a failure.

Example:

Submit
  ├─ Approved
  ├─ Additional Approval Required
  ├─ Returned for Correction
  └─ Rejected

Each outcome can have a different completion or failure meaning.

⌛ Configure abandonment

A process is abandoned when it starts but does not reach an accepted completion condition within the configured period.

Define abandonment according to the process.

Examples:

Do not mark an event sequence as abandoned merely because GermainUX lost monitoring coverage or could not correlate later events.

Keep these outcomes separate:

⏱️ Configure performance objectives

Define expected durations for:

A process can complete successfully and still be inefficient.

Use representative baseline data before setting warning and critical thresholds.

📊 Analyze productivity

GermainUX can analyze productivity using observed process and interaction data.

Potential measures include:

Lost productivity

Lost productivity can be estimated by comparing actual duration with an approved baseline.

For one process instance:

Across multiple instances:

This is an estimate based on the configured baseline and observed events. It should not automatically be treated as employee performance measurement.

👥 Distinguish user time from system time

Where the necessary browser events are available, separate:

The available breakdown depends on what RUM JS captures and how process steps are defined.

Do not attribute the complete elapsed duration to application slowness or user inefficiency without supporting evidence.

☠️ Configure errors within the process

Associate relevant errors with the affected process and step.

Use these classifications:

Keep user validation separate from application errors.

🧭 Analyze process segments

Use pivots and filters to compare process performance by:

Collect only approved user and business attributes.

🔎 Configure outlier detection

Outlier detection can identify unusual process or step durations after sufficient data has been collected.

Potential use cases include:

Outlier detection operates on collected process data. It does not expose steps that GermainUX cannot observe.

🎯 Configure KPIs

Recommended business-process KPIs include:

Custom processes and steps can generate additional KPIs.

🖥️ Configure dashboards

Go to:

Germain Workspace > Dashboards > All

Search for SAP or business-process dashboards, or create a dashboard using the configured process KPIs.

Recommended views include:

🔔 Configure alerts and reports

Create alerts for actionable conditions such as:

Schedule reports for:

✅ Validate the configuration

Test each supported path before production use.

Confirm that:

🚫 Important limitations

GermainUX business-process monitoring depends on the available telemetry.

It does not automatically:

Additional SAP events may require custom RUM instrumentation, API access, log parsing, database queries, or another approved integration.

🔗 Related documentation

ℹ️ Get More Information

GermainUX can help determine which monitoring, analytics and automation capabilities are appropriate for your SAP environment.

Contact GermainUX Support.