Comprehending Process House Scores

Objective

After completing this lesson, you will be able to explain the three main metrics in Process House.

Process House Scores

Now that you have looked at the solution provisioning, you will learn how to interpret and navigate plug and gain.

In this lesson, you will learn about the scores provided within the process house. You will explore three key metrics: the Best Run Score, the Transaction Score and the Completion Score. You will also learn where and how to access the metrics and how to interpret the numbers correctly.

Let's get started with the Best Run Score - one of the major deliverable of the plug and gain approach.

Best Run Score

The Best Run Score is a metric that shows us to what extent an organization is running an effective process in the SAP system. Please keep in mind, that effective does not necessarily mean "automated" or "extremely fast".

Instead, let’s take into account the multiple ways that exist to accomplish a process step. Some of these ways are more favorable than others; the favorable process steps are the ones highlighted in green. The more green boxes the cases pass through, the higher the Best Run Score is. Conversely, the more red boxes the cases pass through, the lower the Best Run Score is.

The figure illustrates the concept of a Best Run Score.

This figure explains the concept of a Best Run Score, demonstrating how it measures the effectiveness of an organization's process in the SAP system by evaluating completed cases against best-run criteria through a visual process diagram.

You can see the best run score when you enter the process house: each end to end process and also its sub-processes are provided with Best Run Score. The Best Run Score can also be broken down by company code or region.

The Best Run Score is a super helpful metric when you consider to harmonize your processes and look out for a very well performing example.

Transaction Usage

Apart from the Best Run Score, additional scores were recently published.

One is the so-called "Transaction Usage" Scoring, that shows the average number of transaction codes used per process step. This analysis can be broken down even further - you can distinguish between standard transactions and custom transactions.

This figure presents the transaction usage within the Collaboration Hub, highlighting the average number of transaction codes used in each process step across different business functions such as Plan to Optimize Financials, Record to Report, Invoice to Pay, and Invoice to Cash.

To keep a process as simple as possible, it is recommended to keep the number of transaction codes as little as possible - this scoring can be a good indicator.

Now, if you are interested in throughput and completion of cases, you might want to check out our so-called completion score.

Completion Score

Completion Score detects number of cases collected within a specified timeframe, encompassing all cases irrespective of their completion status.

To determine how many cases have reached the final stage, refer to the percentage value.

This figure provides an overview of throughput and completion of cases, showcasing the completion scores across various processes including Plan to Optimize Financials, Record to Report, Invoice to Pay, and Invoice to Cash, with a percentage scoring revealing cases that have reached the final process step within a specific timeframe

Reaching a 100% score is desirable, but reality shows that this is often not possible. Therefore, a higher score is always better.

Watch the video to understand the metrics provided by the Process House.

Now that you have reviewed the three process house metrics, let's summarize their key points.

The following table summarizes the 3 metrics.

Best Run ScoreTransaction UsageCompletion Score
  • Shows to what extent an organization is running an effective process in the SAP system.​
  • If multiple ways exist to accomplish a process step, some options are more favorable ("best-run") than others, such as automated process steps.
  • is calculated based on the number of completed cases through steps that are considered best-run versus not best-run.
  • Shows the average number of transaction codes used for each process step.​
  • To promote a streamlined way of working, it is recommended to keep the amount of transaction codes used per process step at a minimum.
  • Can be further broken down into whether standard or custom transaction codes are used.
  • Provides an overview on throughput and completion of cases ​.
  • Detect how many cases have been collected within the respective timeframe - regardless of whether they have been completed or not.
  • Additionally, a percentage scoring is provided: This reveals cases that have reached the final process step within a given timeframe.

Summary

  • The process house is our central point entry into the analysis content.
  • Three main scores available:
    • Best Run Score
    • Transaction Usage
    • Completion Score