Download as pdf or txt
Download as pdf or txt
You are on page 1of 208

12/19/2022

Reference Guide for Performance


Indicators
Generated on: 2022-12-19 00:20:54 GMT+0000

SAP Signavio Process Insights | Cloud

PUBLIC

Original content: https://help.sap.com/docs/BPI/ac0c8ce412284734b40a43e432b47172?locale=en-


US&state=PRODUCTION&version=CLOUD

Warning

This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not re ect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.

For more information, please visit the https://help.sap.com/docs/disclaimer.

This is custom documentation. For more information, please visit the SAP Help Portal 1
12/19/2022

Reference Guide for Performance Indicators


This reference guide gives you an overview of the process performance indicators implemented in SAP Signavio Process
Insights.

This guide is intended for process owners or experts using the SAP Signavio Process Insights solution who want to get more
information about what process performance indicators are implemented for process ows, as standard performance
indicators, and for correction recommendations.

The information provided for process ows helps you understand the following for each process ow:

What the process ow measures

How frequently data is collected and what reference period is used

What data records are extracted

Whether your administrator needs to speci cally activate data collection for the process ow (if it's not activated by
default)

What criteria must be met for business object instances to transition to different stages

What criteria must be met for business object instances to be included in the boxes for blockers or other context
information

The information provided for standard performance indicators helps you understand the following for each performance
indicator:

What the performance indicator measures

How frequently data is collected and what reference period or status applies

What data records are extracted

Whether your administrator needs to speci cally activate data collection for the performance indicator (if it's not
activated by default)

Performance Indicator Categories


Understand the different types of performance indicators and what the categories de ned in the KPI catalog mean.

 Tip
When examining the data and metrics for performance indicators, keep in mind that performance indicators can be based on
different timeframes and different logic, and have different underlying conditions that need to be met. This holds true even if
labels for performance indicators or various stages in process ows, for example, look the same.

Feature Category Description

This is custom documentation. For more information, please visit the SAP Help Portal 2
12/19/2022

Feature Category Description

Process Flows Process Progress Progress of documents or items in typical


processes in given timeframe

These performance indicators convey for a


baseline set of documents or items the
progression of business object instances
through typical business processes and
their phases. They provide transparency
into the overall process.

They can help you assess where you face


bottlenecks, lack efficiency, and need to
improve.

Example: Purchase order item creation to


invoice receipt creation

Standard Performance Indicators Throughput Number of documents or items posted in


given timeframe

These performance indicators measure how


many documents, line items, or schedule
lines were created in a given timeframe.

They can help you assess during a go-live


situation whether a new location or business
process is achieving the desired
throughput, for example.

Example: Purchase order items created

Backlog Number of documents or items not fully


processed by the expected date

These performance indicators check for


documents, line items, or schedule lines
that don't yet have a nal processing status
or haven't reached a key process milestone.
They can be identi ed based on planned
processing dates that lie in the past.

They're important performance indicators


to help you identify weaknesses and
potential for improvement. They typically
hint at a systematic issue within a process.

Example: Purchase order items open and


overdue

This is custom documentation. For more information, please visit the SAP Help Portal 3
12/19/2022

Feature Category Description

Exception Number of error messages raised in given


timeframe

These performance indicators collect error


messages from different technical error
logs and associate them with business
context data. They typically indicate the
actual root cause of a problem based on the
speci c error message.

They help you to identify weaknesses and


potential for improvement.

Example: Errors during manufacturing order


actual settlement

Automation Rate Number of documents processed


automatically

These performance indicators indicate what


percentage of documents processed in a
given timeframe were processed
automatically. This lets you determine the
ratio of documents that have been
processed manually instead of
automatically.

They complement the backlog and


exception performance indicators and are
typically of interest at later stages of efforts
to improve process excellence. They're
used to increase process efficiency and
drive process harmonization processes.

Example: Automation rate: Customer


invoice clearing

Changes Changes made to master data or business


document in dialog mode in given
timeframe

These performance indicators indicate how


many changes were made to master data or
a document by a user in dialog mode in a
given timeframe.

They help you assess where there's


potential for improving efficiency and
reducing the complexity of user tasks that
involve manual changes.

Example: Changes in purchase orders

This is custom documentation. For more information, please visit the SAP Help Portal 4
12/19/2022

Feature Category Description

Customizing Con guration Incorrect con guration typically leading to


performance issues

These performance indicators highlight


where con guration checks identify that
settings are con gured incorrectly and are
potentially resulting in performance issues
that prevent smooth and efficient operation.

Example: Con guration check: Suggest


'delivery completed'

Master Data Number of master data or con guration


entries and their usage in given timeframe

These performance indicators indicate what


master data or con guration entries are
being used. They can help you identify
entries that are no longer used and could
potentially be removed or archived from a
system, for example. Or they can help you
identify if there are entries that should be
used that aren't being used, for example.

Example: Order type usage in production


orders (cross-plant)

Related Information
KPI Catalog

Personal Data in Performance Indicators


Understand what personal data can be stored and processed in performance indicators.

The SAP Signavio Process Insights solution can potentially store and process personal data, such as customer, supplier, and
user identi ers collected for some performance indicators that it receives from your ERP system. SAP therefore acts as the
data processor. The solution displays the data in detail lists to allow users to analyze and lter performance data based on
customers and suppliers.

If a performance indicator contains elds that can potentially contain supplier, customer, or user identi ers, this is indicated on
the Technical tab in the KPI Catalog. You can nd the elds for these identi ers by searching for the following entries in the
Semantic ID column:

Semantic ID Personal Information Potentially Contained in Fields

ERP_LIFNR Supplier identi ers

ERP_KUNNR Customer identi ers

ISU_INVOICING_PARTY

BC_USER User identi ers

CRM_PARTNER

This is custom documentation. For more information, please visit the SAP Help Portal 5
12/19/2022

Related Information
Data Protection and Privacy

Available Process Flows


Get an overview of the process performance indicators that are currently available for process ows in SAP Signavio Process
Insights.

Legend for Additional Information column:

BRIM : Relevant for data from SAP Billing and Revenue Innovation Management.

Utilities : Relevant for data from SAP for Utilities (IS-U).

 Tip
Selecting the value driver Reduce Meter Reading to Invoice Cycle Time in the application lets you focus speci cally
on performance indicators relevant for SAP for Utilities.

Performance Name End-to-End Line of Business Category Additional


Indicator ID Process Information

KFFI000960 Supplier invoice Finance Finance Process Progress


issuing (without
Sourcing &
purchase order) to
Procurement
FI-AP clearing

KFFI001060 Customer invoice Finance Finance Process Progress


issuing (without
sales) to FI-AR
clearing

KFFI002660 Provider contract Finance Finance Process Progress BRIM


creation to rst
Lead to Cash
invoicing

KIISU00160 Utilities contract Lead to Cash Finance Process Progress Utilities


creation to rst
open item clearing

KIISU00161 Utilities billing order Lead to Cash Finance Process Progress Utilities
creation (non-
ST-A/PI 01V_731* Sales
billable) to
scheduled billing
date

KIISU00162 Utilities billing order Lead to Cash Finance Process Progress Utilities
creation (billable) to
ST-A/PI 01V_731* Sales
scheduled billing
date

KIISU00260 Utilities billing Lead to Cash Finance Process Progress Utilities


document creation
ST-A/PI 01V_731* Sales
to print document
creation

This is custom documentation. For more information, please visit the SAP Help Portal 6
12/19/2022

Performance Name End-to-End Line of Business Category Additional


Indicator ID Process Information

KIISU00261 Outsorted utilities Lead to Cash Finance Process Progress Utilities


billing document
ST-A/PI 01V_731* Sales
creation to invoice
printout

KIISU00360 Utilities print Lead to Cash Finance Process Progress Utilities


document creation
ST-A/PI 01V_731* Sales
to open item
clearing

KIISU00361 Outsorted utilities Lead to Cash Finance Process Progress Utilities


print document
ST-A/PI 01V_731* Sales
creation to open
item clearing

KPIM000160 Stock level of Plan to Ful ll Supply Chain Process Progress


sellable materials
(not batch
managed)

KPIM000161 Stock level of Plan to Ful ll Supply Chain Process Progress


sellable materials
(batch managed)

KPLE000360 Outbound delivery Plan to Ful ll Finance Process Progress


item creation to
Sales
goods issue posting
Sourcing &
Procurement

KPLE000361 Outbound delivery Plan to Ful ll Finance Process Progress


item creation to
Sales
goods issue posting
(transfer order) Sourcing &
Procurement

KPLE000362 Inbound delivery Plan to Ful ll Finance Process Progress


item creation to
Source to Pay Sales
goods receipt
posting Sourcing &
Procurement

KPMRP00260 Materials touched Plan to Ful ll Supply Chain Process Progress


by MRP last week
Source to Pay

KPPP000160 Production order Plan to Ful ll Manufacturing Process Progress


Enhanced creation to technical
completion

KPPP000161 Production order Finance Finance Process Progress


creation to rst
Plan to Ful ll Manufacturing
settlement

KPPP000162 Production order Plan to Ful ll Manufacturing Process Progress


Enhanced component creation
Supply Chain
to goods issue
ST-A/PI 01V_731*
posting

This is custom documentation. For more information, please visit the SAP Help Portal 7
12/19/2022

Performance Name End-to-End Line of Business Category Additional


Indicator ID Process Information

KPPP000260 Process order Plan to Ful ll Manufacturing Process Progress


Enhanced creation to technical
completion

KPPP000261 Process order Finance Finance Process Progress


creation to rst
Plan to Ful ll Manufacturing
settlement

KPPP000262 Process order Plan to Ful ll Manufacturing Process Progress


Enhanced component creation
Supply Chain
to goods issue
ST-A/PI 01V_731*
posting

KPPROJ0360 WBS element Acquire to Asset Management Process Progress


creation (without Decommission
Finance
investment pro le)
Finance
to closure R&D/Engineering
Governance

KPPROJ0361 WBS element Acquire to Asset Management Process Progress


creation (with Decommission
Finance
investment pro le)
Finance
to closure
Governance

KPPURCH260 Purchase order item Finance Finance Process Progress


creation to GR/IR
Source to Pay Sourcing &
clearing
Procurement

KPPURCH261 Purchase order item Plan to Ful ll Sourcing & Process Progress
creation to invoice Procurement
Source to Pay
receipt creation

KPPURCH265 Purchase order item Finance Finance Process Progress


creation (without
Source to Pay Sourcing &
GR) to FI-AP clearing
Procurement

KPPURCH266 Purchase order item Plan to Ful ll Manufacturing Process Progress


creation
Source to Pay Sourcing &
(subcontracting) to
Procurement
invoice receipt
creation

KPPURCH360 Purchase requisition Plan to Ful ll Sourcing & Process Progress


item creation to Procurement
Source to Pay
purchase order item
Supply Chain
creation

KPPURCH362 Stock transport Plan to Ful ll Sourcing & Process Progress


requisition item Procurement
Source to Pay
creation to stock
Supply Chain
transport order item
creation

KPPURCH460 Supplier invoice Finance Finance Process Progress


Enhanced issuing to FI-AP
Source to Pay
clearing

This is custom documentation. For more information, please visit the SAP Help Portal 8
12/19/2022

Performance Name End-to-End Line of Business Category Additional


Indicator ID Process Information

KPPURCH560 Stock transport Plan to Ful ll Sourcing & Process Progress


order item creation Procurement
Source to Pay
(without delivery) to
GR

KPPURCH561 Stock transport Plan to Ful ll Sourcing & Process Progress


order item creation Procurement
Source to Pay
(with delivery) to GR

KPPURCH562 Intercompany stock Finance Finance Process Progress


transport order item
Source to Pay Sourcing &
creation to FI-AR
Procurement
clearing

KPPURCH660 Scheduling Source to Pay Sourcing & Process Progress


agreement item Procurement
creation to end of
validity

KPPURCH661 Purchase quantity Governance Sourcing & Process Progress


contract item Procurement
Source to Pay
creation to end of
validity

KPPURCH662 Purchase value Governance Sourcing & Process Progress


contract item Procurement
Source to Pay
creation to end of
validity

KPSD000260 Sales billing Finance Finance Process Progress


document creation
Lead to Cash Sales
to FI-AR clearing

KPSD000360 Sales order item Lead to Cash Sales Process Progress


creation to outbound
delivery item
creation

KPSD000361 Sales order item Lead to Cash Sales Process Progress


creation to sales
invoice item
creation

KPSD000362 Sales order item Finance Finance Process Progress


creation to FI-AR
Lead to Cash Sales
item clearing

KPSD000363 Third-party sales Lead to Cash Sales Process Progress


order item creation
Source to Pay
to sales invoice item
creation

KPSD000364 Sales order item Lead to Cash Sales Process Progress


(purchase to order)
Source to Pay
to sales invoice item

KPSD000365 Sales order item Lead to Cash Sales Process Progress


(make to order) to
Plan to Ful ll
sales invoice item

This is custom documentation. For more information, please visit the SAP Help Portal 9
12/19/2022

Performance Name End-to-End Line of Business Category Additional


Indicator ID Process Information

KPSD000366 Intercompany sales Lead to Cash Finance Process Progress


order item creation
Finance Sales
to FI-AP item
clearing

KPSD000367 Sales order item Finance Finance Process Progress


creation (order-
Lead to Cash Sales
related billing) to FI-
AR item clearing

KPSD000368 Quotation item Lead to Cash Sales Process Progress


creation to sales
order item creation

KPSD000369 Sales order item Lead to Cash Sales Process Progress


Enhanced creation (sell from
stock) to delivery
ST-A/PI 01V_731*
creation

KPSD000380 Returns order item Lead to Cash Sales Process Progress


creation to goods
receipt posting

KPSD000460 Debit memo request Finance Finance Process Progress


item creation to FI-
Lead to Cash Sales
AR item clearing

KPSD000462 Credit memo Finance Finance Process Progress


request item
Lead to Cash Sales
creation to FI-AR
item clearing

KWPM000160 Plant maintenance Acquire to Asset Management Process Progress


noti cation creation Decommission
to noti cation
completion

KWPM000161 Customer service Plan to Ful ll Service Process Progress


noti cation creation
to noti cation
completion

KWPM000260 Plant maintenance Acquire to Asset Management Process Progress


order creation to Decommission
order closure

KWPM000261 Plant maintenance Acquire to Asset Management Process Progress


order creation to Decommission
Finance
order settlement
Finance

KWPM000262 Customer service Plan to Ful ll Service Process Progress


order creation to
order closure

KWPM000263 Customer service Finance Finance Process Progress


Enhanced order creation to
Plan to Ful ll Service
order settlement

This is custom documentation. For more information, please visit the SAP Help Portal 10
12/19/2022

Performance Name End-to-End Line of Business Category Additional


Indicator ID Process Information

KWPM000264 Plant maintenance Acquire to Asset Management Process Progress


Enhanced order component Decommission
Supply Chain
creation to goods
ST-A/PI 01V_731*
issue posting

KWPM000265 Customer service Plan to Ful ll Service Process Progress


Enhanced order component
Supply Chain
creation to goods
ST-A/PI 01V_731*
issue posting

KWQM000161 Lot creation for Plan to Ful ll Manufacturing Process Progress


goods receipt
Source to Pay Sourcing &
inspection from
Procurement
purchasing to usage
decision

KWQM000162 Lot creation for Plan to Ful ll Manufacturing Process Progress


goods receipt
Sourcing &
inspection from
Procurement
manufacturing to
usage decision Supply Chain

*This process ow is only available as of ST-A/PI 01V_731. Upgrading to the latest version is always recommended.

Supplier invoice issuing (without purchase order) to FI-AP


clearing
Find out more about the process ow Supplier invoice issuing (without purchase order) to FI-AP clearing.

General Information

ID in KPI Catalog KFFI000960

What does this process ow measure? Measures the number of supplier invoice items created in the
reference period that don't result from MM invoices and where FI-
AP clearing is expected, and shows how many of them reached
prede ned stages of the process and how long on average this
progression took.

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -77 to -35 calendar days relative to the
date of data collection

What data records are extracted? All FI-AP items with the posting key for supplier invoices that
weren't initiated from purchasing and that were created in the
reference period.

What details are extracted? As outlined in the KPI catalog entry for KFFI000960 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

This is custom documentation. For more information, please visit the SAP Help Portal 11
12/19/2022

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Supplier invoices All supplier invoices that were issued – None – – None –
issued within the reference period based on the
document date of the supplier invoice.
The document date is the date on which
the original document was issued.

This is custom documentation. For more information, please visit the SAP Help Portal 12
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

This stage represents additional Supplier invoices Supplier invoices with the accounting
activities related to the previous stage. parked document status Parked document or
Parked document with change of
document ID.

Supplier invoices Supplier invoices that were previously


previously parked parked but have since been posted, as
indicated in the available change table
information, which might have
been deleted in a timely manner.

Supplier invoices All supplier invoices for which an Supplier invoices Supplier invoices created by a user that's
created and posted accounting document was also created created by dialog maintained as a dialog user in the system.
and has the status Posted. This is based user
Dialog users are users created for human
on the date on which the invoice
users who interact with a system. Supplier
document was entered in the system.
invoices created by dialog users are
therefore typically created manually.
However, it's also possible that some
invoices are created automatically through
interface calls and the dialog user is
recorded as the user who created these
invoices.

Supplier invoices Supplier invoices created in the system


created after posting after the actual posting date in the
date accounting document.

Supplier invoices Supplier invoices that have been reversed,


reversed as indicated when a reversal document
number exists.

Supplier invoices Supplier invoices that are related to a


created for internal supplier that's an internal trading partner.
trading partners

ST-A/PI 01V_731*

FI-AP items released All supplier invoices for which the FI-AP items Supplier invoices for which the
for payment accounting document is also not blocked currently blocked corresponding FI-AP item is currently
or no longer blocked for payment and for for payment blocked for payment, as indicated when a
which no reverse document has been payment block key is entered in the
created. If a document was never system.
blocked, the entry date of the document
is considered. If a document was blocked FI-AP items Supplier invoices for which the FI-AP item
for payment, the last release date is previously blocked was previously blocked for payment, as
considered. for payment indicated in the available change table
information, which might have been
deleted in a timely manner.

Open FI-AP items Supplier invoices for which the FI-AP item
with net due date in is still open, so hasn't been canceled or
the past cleared, and where the net due date is
already in the past.

Open FI-AP items Supplier invoices for which the FI-AP item
with possible is still open, so hasn't been canceled or
discount cleared, and where Cash Discount
Percentage 1 isn't zero.
ST-A/PI 01V_731*

This is custom documentation. For more information, please visit the SAP Help Portal 13
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

FI-AP clearing All supplier invoices for which an FI-AP FI-AP items not Supplier invoices for which the FI-AP item
documents created clearing document has also been created, cleared via payment wasn't cleared as part of a payment run
based on the entry date, and where the run triggered using transaction code F110
original invoice wasn't reversed. (Parameters for Automatic Payment).

FI-AP items cleared Supplier invoices for which the FI-AP item
more than 3 days was cleared 3 days or more before the
before net due date calculated net due date and for which no
and with no discount was applied, which means a
discount weekend in between isn't the sole reason
for the early payment.

FI-AP items cleared Supplier invoices that were cleared using


with account account maintenance transaction FB1K
maintenance (Clear Vendor).
transaction FB1K

FI-AP items cleared All supplier invoices with FI-AP clearing FI-AP items cleared Supplier invoices for which the FI-AP item
documents with a clearing date that were after clearing date was cleared after the clearing date, as
created to clear the supplier invoices and indicated by a clearing document entered
where the original invoice hasn't been in the system after the actual clearing
reversed. date.

FI-AP items cleared Supplier invoices for which the FI-AP item
after net due date was cleared after the calculated net due
date.

FI-AP items cleared Supplier invoices for which the FI-AP item
despite payment was cleared despite a payment block.
block

ST-A/PI 01V_731*

This stage represents additional FI-AP items cleared Supplier invoices for which the FI-AP item
activities related to the previous stage. with discount lost was cleared and a discount was offered
but wasn't applied and deducted.
ST-A/PI 01V_731*

FI-AP items cleared Supplier invoices for which the FI-AP item
with discount was cleared and an offered discount was
applied applied and deducted.

ST-A/PI 01V_731*

FI-AP items cleared Supplier invoices for which the FI-AP item
with discount was cleared and an offered discount was
applied but late applied and deducted although the
payment clearing date is later than the net due date.

ST-A/PI 01V_731*

* This data is only available as of ST-A/PI 01V_731. Upgrading to the latest version is always recommended. Also ensure you
implement the latest version of the relevant SAP Note for your ST-A/PI version as outlined under Technical Prerequisites in the
Administration Guide .

Customer invoice issuing (without sales) to FI-AR clearing

This is custom documentation. For more information, please visit the SAP Help Portal 14
12/19/2022
Find out more about the process ow Customer invoice issuing (without sales) to FI-AR clearing.

General Information

ID in KPI Catalog KFFI001060

What does this process ow measure? Measures the number of customer invoice items created in the
reference period that don't result from SD invoices and where FI-AR
clearing is expected, and shows how many of them reached
prede ned stages of the process and how long on average this
progression took.

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -77 to -35 calendar days relative to the
date of data collection

What data records are extracted? All customer invoice items entered directly in FI with the posting
key for customer invoices that have a document date in the
reference period.

What details are extracted? As outlined in the KPI catalog entry for KFFI001060 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

This is custom documentation. For more information, please visit the SAP Help Portal 15
12/19/2022

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Customer invoices All customer invoice items entered Customer invoices Customer invoices created by a user
issued directly in FI with the posting key for created by dialog that's maintained as a dialog user in the
customer invoices that have a document user system.
date in the reference period.
Dialog users are users created for human
users who interact with a system.
Customer invoices created by dialog users
are therefore typically created manually.
However, it's also possible that some
invoices are created automatically through
interface calls and the dialog user is
recorded as the user who created these
invoices.

Customer invoices Customer invoices that are currently


parked parked and not yet posted, as indicated
by an accounting document with the status
Parked document or Parked document
with change of document ID.

Customer invoices Customer invoices that have been


reversed reversed, as indicated when a reversal
document number exists.

Customer invoices Customer invoices that are related to a


created for internal customer that's an internal trading partner.
trading partners

ST-A/PI 01V_731*

This stage represents additional Customer invoice Customer invoices that have been created
activities related to the previous stage. created with with a document date before the creation
document date in date, which can indicate that invoices are
the past processed late.

This is custom documentation. For more information, please visit the SAP Help Portal 16
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Customer invoice Customer invoices that have been created


created with with a document date after the creation
document date in date, which can indicate cases where
the future customers are granted an unwanted or
unnecessary payment extension.

This stage represents additional Open FI-AR items Customer invoices that aren't cleared or
activities related to the previous stage. with dunning block paid and are blocked for dunning.

Open FI-AR items Customer invoices that aren't cleared or


already dunned paid and have been dunned at least once.

Open and overdue Customer invoices that aren't cleared or


FI-AR items paid and where the net due date is already
in the past.

Open and overdue Customer invoices that aren't cleared or


FI-AR items despite paid and where the net due date is already
offered discount in the past although a discount was offered
to the customer if they paid earlier.
ST-A/PI 01V_731*

FI-AR items cleared All customer invoice items for which a FI-AR items Customer invoices that are cleared or paid
clearing or payment has also taken place, previously dunned and have been dunned at least once.
which is determined based on the are cleared
clearing date.
FI-AR items cleared Customer invoices that are cleared or paid
with transaction and for which the clearing was processed
FBZ1 manually using transaction code FBZ1.

FI-AR items cleared Customer invoices that are cleared or paid


after net due date and for which the clearing was posted
after the net due date.

FI-AR items cleared Customer invoices that are cleared or paid


after net due date and for which the clearing was posted
but with discount after the net due date but where a
discount amount was still deducted.
ST-A/PI 01V_731*

This stage represents additional FI-AR items cleared Customer invoices that are cleared or paid
activities related to the previous stage. with clearing date in and for which the clearing date is after the
the future creation date of the clearing document,
which can indicate that a customer
payment is only anticipated in the future.

FI-AR items cleared Customer invoices that are cleared or paid


with clearing date and for which the clearing date is more
more than 3 days in than 3 days earlier than the creation date
the past of the clearing document, which can
indicate that the customer payment
couldn't be allocated on time.

FI-AR items cleared Customer invoices that are cleared or paid


with discount and where a discount amount was
applied deducted.

ST-A/PI 01V_731*

This is custom documentation. For more information, please visit the SAP Help Portal 17
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

FI-AR items cleared Customer invoices that are cleared or paid


without offered without a discount amount deducted,
discount although a discount was offered to the
customer if they paid earlier.
ST-A/PI 01V_731*

* This data is only available as of ST-A/PI 01V_731. Upgrading to the latest version is always recommended. Also ensure you
implement the latest version of the relevant SAP Note for your ST-A/PI version as outlined under Technical Prerequisites in the
Administration Guide .

Provider contract creation to rst invoicing


Find out more about the process ow Provider contract creation to rst invoicing.

General Information

ID in KPI Catalog KFFI002660

What does this process ow measure? Measures the number of provider contracts created in the
reference period where rst invoicing documents are expected and
shows how many of them reached prede ned stages of the process
and how long on average this progression took.

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -42 to -14 calendar days relative to the
date of data collection

What data records are extracted? All provider contracts representing the agreement between a
business partner and the entity offering the contract (the provider)
that were created in the reference period. This is determined based
on the date on which the provider contract was created.

What details are extracted? As outlined in the KPI catalog entry for KFFI002660 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

This is custom documentation. For more information, please visit the SAP Help Portal 18
12/19/2022

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Provider contract All provider contracts representing the – None – – None –


created agreement between a business partner
and the entity offering the contract (the
provider) that were created in
the reference period. This is determined
based on the date on which the provider
contract was created.

Contract has begun All provider contracts that have already Provider contracts Provider contracts that have a billing lock
begun. This is determined based on the locked for billing set together with lock reasons at
contract start date displayed in the contract level.
provider contract.
Provider contracts Provider contracts for which the contract
with contract accounts have a billing lock set
accounts locked for that in uences billing of the provider
billing contract.

This is custom documentation. For more information, please visit the SAP Help Portal 19
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

First billing document All provider contracts for which a Provider contracts Provider contracts for which a
created subsequent billing document was also without billing corresponding billing document hasn't yet
created. This is determined based on the document been subsequently created.
date on which the corresponding billing
document for the provider contract was Provider contracts Provider contracts that have a
created. with billing corresponding billing document that
documents created doesn't contain an internal number of a
without billing run billing run.

This stage represents additional Provider contracts Provider contracts that have an invoicing
activities related to the previous stage. locked for invoicing lock set together with lock reasons
for invoicing at contract level.

Provider contracts Provider contracts for which the contract


with contract accounts have an invoicing lock set
accounts locked for that in uences invoice creation for the
invoicing provider contract.

This stage represents additional Provider contracts Provider contracts for which the
activities related to the previous stage. with billing corresponding billing document is overdue
documents overdue for invoicing because the target date for
for invoicing invoicing in the invoicing request is
already in the past.

First invoicing All provider contracts for which the Provider contracts Provider contracts for which a
document created subsequent billing documents also have without invoicing corresponding invoicing document hasn't
a corresponding invoicing document. This documents yet been subsequently created.
is determined based on the creation date
of the corresponding invoicing document Provider contracts Provider contracts for which a
for the provider contract. with invoicing corresponding invoicing document has
documents created been created that doesn't contain an
without invoicing internal number of an invoicing run to
run re ect its source of creation.

Provider contracts Provider contracts for which a


with invoicing corresponding invoicing document has
documents created been created where the creation mode of
using individual the invoicing document is set to Invoicing
processing Individual Process or Invoicing Individual
Process in Expert Mode.

Utilities contract creation to rst open item clearing


Find out more about the process ow Utilities contract creation to rst open item clearing.

General Information

ID in KPI Catalog KIISU00160

What does this process ow measure? Measures the number of utilities contracts created in the reference
period and shows how many of them reached prede ned stages of
the process and how long on average this progression took.

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?

This is custom documentation. For more information, please visit the SAP Help Portal 20
12/19/2022
Reference period: -42 to -14 calendar days relative to the
date of data collection

What data records are extracted? All utilities contracts that were created in the reference period.

What details are extracted? As outlined in the KPI catalog entry for KIISU00160 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

This is custom documentation. For more information, please visit the SAP Help Portal 21
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Contracts created All utilities contracts that were created in Contracts locked for Utilities contracts that are locked for
the reference period. billing billing.

Contracts with Utilities contracts that can't be billed


installation blocked because installation for meter reading is
for meter reading blocked.

This stage represents additional Contracts with Utilities contracts for which billing orders
activities related to the previous stage. billing orders are overdue for billing but that can be
overdue for billing billed. The meter reading orders
and billing status were created and plausible meter reading
"billable" results were entered for all registers
allocated to the contract.

Contracts with Utilities contracts for which billing orders


billing orders are overdue for billing and that can't be
overdue for billing billed. The meter reading orders were
and billing status created and a plausible meter reading
"not billable" result hasn't yet been entered for at least
one of the meter reading orders.

Contracts without Utilities contracts for which billing orders


billing orders or or billing documents weren't created.
billing documents

First billing document All utilities contracts for which a rst Contracts with Utilities contracts for which billing
related to contract billing document was also created. outsorted and document are outsorted and not
created unreleased billing yet released.
documents

Contracts without Utilities contracts for which billing


any billing documents weren't created.
documents

Provider contracts Utilities contracts for which billing


with manual billing documents weren't created by the billing
document creation run but manually.

This stage represents additional Contracts with Utilities contracts for which billing
activities related to the previous stage. outsorted and documents were outsorted and released.
released billing
documents

Contracts with Utilities contracts for which billing


billing documents documents are overdue for invoicing.
overdue for
invoicing

Contracts with Utilities contracts for which billing


billing documents documents are open for invoicing.
open for invoicing

First print document All utilities contracts for which a rst Contracts with Utilities contracts for
related to contract print document was also created. outsorted and which invoicing documents are outsorted
created unreleased invoicing but not released.
documents

Contracts without Utilities contracts for which invoicing


invoicing documents documents weren't created.

This is custom documentation. For more information, please visit the SAP Help Portal 22
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Contracts with Utilities contracts with contract accounts


contract accounts that are locked for invoicing.
locked for invoicing

This stage represents additional Contracts with Utilities contracts for


activities related to the previous stage. outsorted and which invoicing documents are outsorted
released invoicing and released.
documents

Contracts with print Utilities contracts for which print


documents overdue documents are overdue for printing.
for printing

First contract All utilities contracts for which a rst Open contract Utilities contracts for which open contract
accounting document contract accounting document was also account items account items exist and are overdue for
related to contract created. overdue for clearing clearing.
created

First contract All utilities contracts for which a rst Contract account Utilities contracts for which contract
accounting item contract accounting item was also items cleared after account items were cleared after the net
related to contract cleared. net due date due date.
cleared

Utilities billing order creation (non-billable) to scheduled billing


date
Find out more about the process ow Utilities billing order creation (non-billable) to scheduled billing date.

 Note
This process ow is only available as of ST-A/PI 01V_731. Upgrading to the latest version is always recommended. Also
ensure you implement the latest version of the relevant SAP Note for your ST-A/PI version as outlined under Technical
Prerequisites in the Administration Guide .

General Information

ID in KPI Catalog KIISU00161

What does this process ow measure? Measures the number non-billable utilities billing orders that were
created in the reference period and shows how many of them
reached prede ned stages of the process and how long on average
this progression took.

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -35 to -1 calendar days relative to the
date of data collection

What data records are extracted? All utilities billing orders that were created in the reference period
for which the status of the billing order is Non-billable.

What details are extracted? As outlined in the KPI catalog entry for KIISU00161 on the
Technical tab in the Detail List column.

This is custom documentation. For more information, please visit the SAP Help Portal 23
12/19/2022

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.
This is custom documentation. For more information, please visit the SAP Help Portal 24
12/19/2022

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Billing orders created All utilities billing orders that were Billing orders for Billing orders created for periodic billing.
created in the reference period for which periodic billing
the status of billing order is Non-billable.
Billing orders for Billing orders created for interim billing.
interim billing

Billing orders for Billing orders created for nal billing for
move-out move-out.

This stage represents additional Billing orders Billing orders for which a meter reading
activities related to the previous stage. without meter order doesn't exist.
reading order

Billing orders with Billing orders for which meter reading was
meter reading automatically locked by the system.
locked automatically

Billing orders with Billing orders for which meter reading was
meter reading released by an agent.
released by agent

Billing orders with Billing orders for which meter reading was
scheduled meter scheduled by the utility company.
reading by utility
company

Billing orders with Billing orders for which meter reading was
scheduled meter scheduled by the customer.
reading by customer

Billing orders with Billing orders for which meter reading was
scheduled automatic scheduled by automatic estimation.
estimation

This stage represents additional Billing orders with Billing orders that can´t be billed because
activities related to the previous stage. contract currently of a billing block at contract level.
blocked for billing

Billing orders with Billing orders where a billing block in the


blocked contract contract was released.
released for billing

Billing orders with Billing orders with an invoicing party in the


invoicing party in contract that sends the bill for
contract the installation.

Billing orders with All utilities billing orders that have a Billing orders with Billing orders that have a scheduled billing
scheduled billing date scheduled billing date in the future. scheduled billing date in the past.
in the future date in the past

This is custom documentation. For more information, please visit the SAP Help Portal 25
12/19/2022

Utilities billing order creation (billable) to scheduled billing date


Find out more about the process ow Utilities billing order creation (billable) to scheduled billing date.

 Note
This process ow is only available as of ST-A/PI 01V_731. Upgrading to the latest version is always recommended. Also
ensure you implement the latest version of the relevant SAP Note for your ST-A/PI version as outlined under Technical
Prerequisites in the Administration Guide .

General Information

ID in KPI Catalog KIISU00162

What does this process ow measure? Measures the number billable utilities billing orders that were
created in the reference period and shows how many of them
reached prede ned stages of the process and how long on average
this progression took.

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -35 to -1 calendar days relative to the
date of data collection

What data records are extracted? All utilities billing orders that were created in the reference period
for which the status of the billing order is Billable.

What details are extracted? As outlined in the KPI catalog entry for KIISU00162 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

This is custom documentation. For more information, please visit the SAP Help Portal 26
12/19/2022

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

This is custom documentation. For more information, please visit the SAP Help Portal 27
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Billing orders created All utilities billing orders that were Billing orders for Billing orders created for periodic billing.
created in the reference period for which periodic billing
the status of the billing order is Billable.
Billing orders for Billing orders created for interim billing.
interim billing

Billing orders for Billing orders created for nal billing for
move-out move-out.

Meter reading result All utilities billing orders that also have an Billing orders Billing orders for which a meter reading
saved for billing actual meter reading result. without meter order doesn't exist.
orders reading order

Billing orders with Billing orders for which meter reading was
meter reading automatically locked by the system.
locked automatically

Billing orders with Billing orders for which meter reading was
meter reading released by an agent.
released by agent

Billing orders with Billing orders for which meter reading was
actual meter reading scheduled by the utility company.
by utility company

Billing orders with Billing orders for which meter reading was
actual meter reading scheduled by the customer.
by customer

Billing orders with Billing orders for which meter reading was
actual automatic scheduled by automatic estimation.
estimation

This stage represents additional Billing orders with Billing orders that can´t be billed because
activities related to the previous stage. contract currently of a billing block at contract level.
blocked for billing

Billing orders with Billing orders where a billing block in the


blocked contract contract was released.
released for billing

Billing orders with Billing orders with an invoicing party in the


invoicing party in contract that sends the bill for
contract the installation.

Billing orders with All utilities billing orders that have a Billing orders with Billing orders that have a scheduled billing
scheduled billing date scheduled billing date in the future. scheduled billing date in the past.
in the future date in the past

Utilities billing document creation to print document creation


Find out more about the process ow Utilities billing document creation to print document creation.

 Note
This process ow is only available as of ST-A/PI 01V_731. Upgrading to the latest version is always recommended. Also
ensure you implement the latest version of the relevant SAP Note for your ST-A/PI version as outlined under Technical

This is custom documentation. For more information, please visit the SAP Help Portal 28
12/19/2022
Prerequisites in the Administration Guide .

General Information

ID in KPI Catalog KIISU00260

What does this process ow measure? Measures the number of utilities billing documents that were
created in the reference period for which a print document is
expected, and shows how many of them reached prede ned stages
of the process and how long on average this progression took.

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -35 to -1 calendar days relative to the
date of data collection

What data records are extracted? All billing documents that were created in the reference period
without simulation, so that simulated documents are not generated
during invoicing.

What details are extracted? As outlined in the KPI catalog entry for KIISU00260 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

This is custom documentation. For more information, please visit the SAP Help Portal 29
12/19/2022

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Billing documents All billing documents that were created in Billing documents Billing documents that were created by a
created the reference period without simulation. created by dialog user that's maintained as a dialog user in
This is determined by the date on which user and without the system and for which the number that
the order was created. billing run uniquely identi es a billing run is empty.

This is custom documentation. For more information, please visit the SAP Help Portal 30
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Billing documents Billing documents that were created by a


created by dialog user that's maintained as a dialog user in
user in billing run the system and for which the number that
uniquely identi es a billing run is found in
the Bi.run no. eld of the billing
document.

Billing documents Billing documents with the creation


for periodic billing reason Periodic Billing (01).

Billing documents Billing documents with the creation


for interim billing reason Interim Billing (02).

Billing documents Billing documents with the creation


for move-out reason Final Billing for Move-Out (03).

This stage represents additional Billing documents Billing documents that don't yet have a
activities related to the previous stage. not invoiced subsequent print document created
although end of although the date on which the billing
billing period in the period ends is in the past (in relation to
past the date of data collection).

Billing documents Billing documents for which an entry also


outsorted but not exists in the outsorting table for billing
yet released data (ERCHO) and that still need to be
released for further processing to take
place.

Billing documents Billing documents for which an entry also


outsorted and exists in the outsorting table for billing
released data (ERCHO) and that were already
released for processing for further
processing to take place.

Billing documents Billing documents that have a reversal


reversed before date and for which a subsequent print
print documents document hasn’t yet been created.
were created

Print documents All billing documents for which a print Print documents Billing documents that still need to be
created and posted document has also been created and outsorted but not released for further processing to
posted, which is determined by the day yet released take place because the to-be-released
on which the accounting document was indicator isn't canceled until
entered and invoiced. all outsortings for the documents are
released.

Print documents Billing documents that have a reference to


reversed a reversal print document number.

Billing documents Billing documents with more than one


with more than one subsequent print document.
subsequent print
document

Billing documents Billing documents that have a reversal


reversed after print date and for which a subsequent
documents were print document has also already been
created created.

This is custom documentation. For more information, please visit the SAP Help Portal 31
12/19/2022

Outsorted utilities billing document creation to invoice printout


Find out more about the process ow Outsorted utilities billing document creation to invoice printout.

 Note
This process ow is only available as of ST-A/PI 01V_731. Upgrading to the latest version is always recommended. Also
ensure you implement the latest version of the relevant SAP Note for your ST-A/PI version as outlined under Technical
Prerequisites in the Administration Guide .

General Information

ID in KPI Catalog KIISU00261

What does this process ow measure? Measures the number of outsorted utilities billing documents that
were created in the reference period for which a print document is
expected after their release, and shows how many of them
reached prede ned stages of the process and how long on average
this progression took.

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -56 to -1 calendar days relative to the
date of data collection

What data records are extracted? All outsorted billing documents, that is, billing documents for which
an entry also exists in the outsorting table for billing data (ERCHO),
that were created in the reference period and are without
simulation, so that simulated documents are not generated
during invoicing.

What details are extracted? As outlined in the KPI catalog entry for KIISU00261 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

This is custom documentation. For more information, please visit the SAP Help Portal 32
12/19/2022

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Outsorted billing All outsorted billing documents that were Outsorted billing Outsorted billing documents that were
documents created created in the reference period without documents created created by a user that's maintained as a
simulation. This is determined by the by dialog user and dialog user in the system and for which
date on which the order was created. without billing run the number that uniquely identi es a
billing run is empty.

This is custom documentation. For more information, please visit the SAP Help Portal 33
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Outsorted billing Outsorted billing documents that were


documents created created by a user that's maintained as a
by dialog user in dialog user in the system and for which
billing run the number that uniquely identi es a
billing run is found in the Bi.run no.
eld of the billing document.

Outsorted billing Outsorted billing documents with the


documents for creation reason Periodic Billing (01).
periodic billing

Outsorted billing Outsorted with the creation reason Interim


documents for Billing (02).
interim billing

Outsorted billing Outsorted billing documents with the


documents for creation reason Final Billing for Move-Out
move-out (03).

Outsorted billing All outsorted billing documents that also Outsorted billing Outsorted billing documents that don't yet
documents released have a document release date. documents not have a subsequent print document
invoiced although created although the date on which the
end of billing period billing period ends is in the past (in
in the past relation to the date of data collection).

Outsorted billing Outsorted billing documents for which an


documents entry also exists in the outsorting table for
outsorted but not billing data (ERCHO) and that still need to
yet released be released for further processing to take
place.

Outsorted billing Outsorted billing documents for which a


documents with reason for manual outsorting in billing
manual outsorting exists.

Outsorted billing Outsorted billing documents that have a


documents reversed reversal date and for which a subsequent
before print print document hasn’t yet been created.
documents were
created

Print documents All outsorted billing documents that were Print documents Outsorted billing documents that still need
created and posted released and for which a subsequent outsorted but not to be released for further processing to
print document has also been created yet released take place because the to-be-released
and posted, which is determined by the indicator isn't canceled until
day on which the accounting document all outsortings for the documents are
was entered and invoiced. released.

Print documents Outsorted billing documents for which the


reversed subsequent print documents have
a reference to a reversal print document
number.

Billing documents Outsorted billing documents with more


with more than one than one subsequent print document.
subsequent print
document

This is custom documentation. For more information, please visit the SAP Help Portal 34
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Outsorted billing Outsorted billing documents that have a


documents reversed reversal date and for which a subsequent
after print print document has also already been
documents were created.
created

Utilities print document creation to open item clearing


Find out more about the process ow Utilities print document creation to open item clearing.

 Note
This process ow is only available as of ST-A/PI 01V_731. Upgrading to the latest version is always recommended. Also
ensure you implement the latest version of the relevant SAP Note for your ST-A/PI version as outlined under Technical
Prerequisites in the Administration Guide .

General Information

ID in KPI Catalog KIISU00360

What does this process ow measure? Measures the number of print documents that were created in the
reference period for which a corresponding accounting document
and customer payment are expected, and shows how many of them
reached prede ned stages of the process and how long on average
this progression took.

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -49 to -14 calendar days relative to the
date of data collection

What data records are extracted? All print documents that were created in the reference period.

What details are extracted? As outlined in the KPI catalog entry for KIISU00360 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

This is custom documentation. For more information, please visit the SAP Help Portal 35
12/19/2022

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

This is custom documentation. For more information, please visit the SAP Help Portal 36
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Print documents All print documents created in the Print documents Print documents created by a user that's
created reference period, based on the date the created by dialog maintained as a dialog user in the system.
document was created. user
Dialog users are users created for human
users who interact with a system.
Documents created by dialog users are
therefore typically created manually.
However, it's also possible that some
documents are created automatically
through interface calls and the dialog user
is recorded as the user who created these
documents.

Print documents Print documents created for Print


with creation reason consumption billing.
"Print consumption
billing"

Print documents Print documents created for Periodic


with billing billing.
transaction
"Periodic billing"

Print documents Print documents created for Interim


with billing billing.
transaction "Interim
billing"

Print documents Print documents created for Final billing


with billing for move-out.
transaction move-
out

This stage represents additional Print documents not Print documents that have not yet been
activities related to the previous stage. yet posted to posted to accounting at the time of data
accounting although collection and whose net due date (date on
net due date is in the which an item is due for payment without
past deduction of cash discount) is in the past.

Print documents Print documents that have


outsorted but not been outsorted and that have not yet been
yet released released at the time of data collection.

If the released indicator is set, the


document must be released before further
processing can take place, which means
bill printout is stopped. The indicator is
set either because at least one
outsorting check failed or because the
indicator for manual outsorting is set in a
contract.

Print documents Print documents that have


outsorted and been outsorted and that have been
released released at the time of data collection.
This means that further processing, such
as bill printout, can take place.

This is custom documentation. For more information, please visit the SAP Help Portal 37
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Print documents Print documents that have been reversed


reversed before before a Contract Accounts Receivable
accounting and Payable (FI-CA) document has
documents were been created.
created

Print documents Print documents that are blocked for


with print block printing.

Open items created in All print documents for which open items Open items overdue Print documents for which open items
accounting have also been created in accounting for clearing have been created in accounting that
based on the creation date of the item. have not yet been cleared, although the net
due date is in the past at the time of
data collection.

Print documents Print documents for which open items


with open items but have been created in accounting that
no print date have not yet been cleared, but for which a
print date hasn't been scheduled.

Print documents Print documents for which open items


reversed after have been created in accounting that
accounting have been reversed after being posted to
documents were accounting.
created

Open items cleared in All print documents for which open items Items cleared by a Print documents for which open items
accounting have also been cleared in accounting reversal have been created in accounting that
based on the clearing date. have been cleared by a reversal.

Items cleared by Print documents for which open items


account have been created in accounting that have
maintenance been cleared by account maintenance.

Items cleared by Print documents for which open items


incoming payment have been created in accounting that have
been cleared by an incoming payment.

Items cleared with Print documents for which open items


zero amount have been created in accounting that have
been cleared with zero amount.

Outsorted utilities print document creation to open item clearing


Find out more about the process ow Outsorted utilities print document creation to open item clearing.

 Note
This process ow is only available as of ST-A/PI 01V_731. Upgrading to the latest version is always recommended. Also
ensure you implement the latest version of the relevant SAP Note for your ST-A/PI version as outlined under Technical
Prerequisites in the Administration Guide .

General Information

This is custom documentation. For more information, please visit the SAP Help Portal 38
12/19/2022
ID in KPI Catalog KIISU00361

What does this process ow measure? Measures the outsorted utilities print documents that were created
in the reference period for which a corresponding accounting
document and customer payment are expected, and shows
how many of them reached prede ned stages of the process and
how long on average this progression took.

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -70 to -14 calendar days relative to the
date of data collection

What data records are extracted? All outsorted utilities print documents that were created in the
reference period.

What details are extracted? As outlined in the KPI catalog entry for KIISU00361 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

Process Flow Stages, Blockers, and Other Information


This is custom documentation. For more information, please visit the SAP Help Portal 39
12/19/2022

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Outsorted print All outsorted utilities print documents Outsorted print Outsorted utilities print documents
documents created that were created in the reference documents created created by a user that's maintained as a
period, based on date the document was by dialog user dialog user in the system.
created.
Dialog users are users created for human
users who interact with a system.
Documents created by dialog users are
therefore typically created manually.
However, it's also possible that some
documents are created automatically
through interface calls and the dialog user
is recorded as the user who created these
documents.

Outsorted print Outsorted utilities print documents


documents with created for Print consumption billing.
creation reason
"Print consumption
billing"

Outsorted print Outsorted utilities print documents


documents with created for Periodic billing.
billing transaction
"Periodic billing"

Outsorted print Outsorted utilities print documents


documents with created for Interim billing.
billing transaction
"Interim billing"

Outsorted print Outsorted utilities print documents


documents with created for Final billing for move-out.
billing transaction
move-out

Outsorted print All outsorted utilities print documents Outsorted print Outsorted utilities print documents that
documents released that have also been released, based on documents not yet have not yet been released at the time
the release date. released although of data collection and for which the
net due date in the net due date (date on which an item is due
past for payment without deduction of
cash discount) is in the past.

This is custom documentation. For more information, please visit the SAP Help Portal 40
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Outsorted print Outsorted utilities print documents that


documents with are marked to be
manual outsorting manually outsorted during invoicing.
during invoicing

Outsorted print Outsorted utilities print documents that


documents with are marked to be
manual outsorting manually outsorted during printing.
during printing

Outsorted print Outsorted utilities print documents that


documents reversed were reversed before an
before accounting accounting document was created.
documents were
created

This stage represents additional Outsorted print Outsorted utilities print documents that
activities related to the previous stage. documents with are blocked for printing.
print block

Open items created in All outsorted utilities print documents for Open items overdue Outsorted utilities print documents for
accounting which open items have also been created for clearing which open items have been created
in accounting, based on the creation date in accounting that have not yet been
of the items. cleared, although the net due date is in
the past at the time of data collection.

Print documents Outsorted utilities print documents for


with open items but which open items have been created
no print date in accounting that have not yet been
cleared, but for which a print date hasn't
been scheduled.

Print documents Outsorted utilities print documents for


reversed after which open items have been created
accounting in accounting that have been reversed
documents were after being posted to accounting.
created

Open items cleared in All outsorted utilities print documents for Items cleared by a Outsorted utilities print documents for
accounting which open items have also been cleared, reversal which open items have been created
based on the clearing date. in accounting that have been cleared by a
reversal.

Items cleared by Outsorted utilities print documents for


account which open items have been created
maintenance in accounting that have been cleared by
account maintenance.

Items cleared by Outsorted utilities print documents for


incoming payment which open items have been created
in accounting that have been cleared by an
incoming payment.

Items cleared with Outsorted utilities print documents for


zero amount which open items have been created in
accounting that have been cleared with
zero amount.

This is custom documentation. For more information, please visit the SAP Help Portal 41
12/19/2022

Stock level of sellable materials (not batch managed)


Find out more about the process ow Stock level of sellable materials (not batch managed).

General Information

ID in KPI Catalog KPIM000160

What does this process ow measure? Measures the stock level and last movement of sellable materials
that are not batch managed (on material/plant/storage location
combination level)

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: All data up to the date of data collection

What data records are extracted? The storage location data for those materials with reference
material types for trading goods and nished products that
aren't batch managed and where the valuated unrestricted-use
stock is greater than zero; the present posting period at the time of
data collection is considered the current period and is used as
the baseline for determining in which period the last movement of
the material stock took place.

What details are extracted? As outlined in the KPI catalog entry for KPIM000160 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

This is custom documentation. For more information, please visit the SAP Help Portal 42
12/19/2022

Process Flow Stages, Blockers, and Other Information

 Note
Non-Standard Process Flow

This is not a typical process ow and you need to interpret the data visualized in a different way to the visualizations for
most process ows. The rst stage in this process ow represents the baseline set of business object instances created up
to the date of data collection.

The concept of progression doesn't apply in this case. Instead, the stage boxes under Process Flow Performance are used as
a means of providing a visual breakdown of how the business object instances in the baseline set can be categorized. This
means that the sum of the metrics in all subsequent stages equals the metrics of the baseline set in the rst stage.

Since there's no concept of progression in this case, average time metrics aren't applicable and therefore aren't available
for the lead times between stages or the average days taken to reach each stage.

Stage Description Frequent Description


Blockers/Other
Information

Material/plant/storage All material/plant/storage location ST-A/PI 01V_731* All material/plant/storage location


location combinations combinations of sellable materials that combinations for which neither a
Combinations
with stock have a stock level greater than zero at corresponding open sales order (that is, a
without open sales
the time of data collection. sales order with missing delivery) nor an
orders or outbound
open delivery (that is, a delivery with
deliveries
missing goods issue posting) exists.

ST-A/PI 01V_731* All material/plant/storage location


combinations for which at least one
Combinations with
corresponding open sales order (that is, a
open sales orders
sales order with missing delivery) exists.

ST-A/PI 01V_731* All material/plant/storage location


combinations for which at least one
Combinations with
corresponding open delivery (that is, a
open outbound
delivery with missing goods issue posting)
deliveries
exists.

Combinations with last All material/plant/storage location Combinations Material/plant/storage location


goods moved over 1 combinations for which the last stock without plan-driven combinations of materials where planning
year ago movement took place over 1 year ago. MRP with last goods for the material is something other than
This is determined by the posting period moved over 1 year Material requirements planning and the
in which the goods of the combination ago last stock movement took place over 1
were last moved. year ago.

Combinations with Material/plant/storage location


trading-goods-like combinations of materials with the
materials last moved reference material type for trading goods
over 1 year ago for which the last stock movement
took place over 1 year ago.

Combinations with Material/plant/storage location


nished-product- combinations of materials with the
like materials last reference material type for nished goods
moved over 1 year for which the last stock movements
ago took place over 1 year ago.

This is custom documentation. For more information, please visit the SAP Help Portal 43
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Combinations with last All material/plant/storage location Combinations Material/plant/storage location


goods moved 7-12 combinations for which the last stock without plan-driven combinations of materials where planning
periods ago movement took place 7 to 12 periods MRP with last goods for the material is something other than
ago. This is determined by the posting moved 7-12 periods Material requirements planning and the
period in which the goods of the ago last stock movement took place 7 to 12
combination were last moved. periods ago.

Combinations with Material/plant/storage location


trading-goods-like combinations of materials with
materials last moved the reference material type for trading
7-12 periods ago goods for which the last stock movement
took place 7 to 12 periods ago.

Combinations with Material/plant/storage location


nished-product- combinations of materials with
like materials last the reference material type for nished
moved 7-12 periods goods for which the last stock movement
ago took place 7 to 12 periods ago.

Combinations with last All material/plant/storage location Combinations Material/plant/storage location


goods moved 4-6 combinations for which the last stock without plan-driven combinations of materials where planning
periods ago movement took place 4 to 6 periods ago. MRP with last goods for the material is something other than
This is determined by the posting period moved 4-6 periods Material requirements planning and the
in which the goods of the combination ago last stock movements took place 4 to 6
were last moved. periods ago.

Combinations with Material/plant/storage location


trading-goods-like combinations of materials with
materials last moved the reference material type for trading
4-6 periods ago goods for which the last stock movement
took place 4 to 6 periods ago.

Combinations with Material/plant/storage location


nished-product- combinations of materials with
like materials last the reference material type for nished
moved 4-6 periods goods for which the last stock movement
ago took place 4 to 6 periods ago.

Combinations with last All material/plant/storage location Combinations Material/plant/storage location


goods moved 2-3 combinations for which the last stock without plan-driven combinations of materials where planning
periods ago movement took place 2 to 3 periods ago. MRP with last goods for the material is something other than
This is determined by the posting period moved 2-3 periods Material requirements planning and the
in which the goods of the combination ago last stock movements took place 2 to 3
were last moved. periods ago.

Combinations with Material/plant/storage location


trading-goods-like combinations of materials with
materials last moved the reference material type for trading
2-3 periods ago goods for which the last stock movement
took place 2 to 3 periods ago.

Combinations with Material/plant/storage location


nished-product- combinations of materials with
like materials last the reference material type for nished
moved 2-3 periods goods for which the last stock movement
ago took place 2 to 3 periods ago.

This is custom documentation. For more information, please visit the SAP Help Portal 44
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Combinations with last All material/plant/storage location Combinations Material/plant/storage location


goods moved in combinations for which the last stock without plan-driven combinations of materials where planning
previous period movement took place one period ago. MRP with last goods for the material is something other than
This is determined by the posting period moved in previous Material requirements planning and the
in which the goods of the combination period last stock movement took place 1 period
were last moved. ago.

Combinations with Material/plant/storage location


trading-goods-like combinations of materials with
materials last moved the reference material type for trading
in previous period goods for which the last stock movement
took place 1 period ago.

Combinations with Material/plant/storage location


nished-product- combinations of materials with
like materials last the reference material type for nished
moved in previous goods for which the last stock movement
period took place 1 period ago.

Combinations with last All material/plant/storage location Combinations Material/plant/storage location


goods moved this combinations for which the last stock without plan-driven combinations of materials where planning
period movement took place during the current MRP with last goods for the material is something other than
period. This is determined by the moved this period Material requirements planning and the
posting period in which the goods of the last stock movement took place during the
combination were last moved. current period.

Combinations with Material/plant/storage location


trading-goods-like combinations of materials with
materials last moved the reference material type for trading
this period goods for which the last stock movement
took place during the current period.

Combinations with Material/plant/storage location


nished-product- combinations of materials with
like materials last the reference material type for nished
moved this period goods for which the last stock movement
took place during the current period.

* This data is only available as of ST-A/PI 01V_731. Upgrading to the latest version is always recommended. Also ensure you
implement the latest version of the relevant SAP Note for your ST-A/PI version as outlined under Technical Prerequisites in the
Administration Guide .

If you're using an older ST-A/PI version, lead times aren't available when there are additional stages supported by a higher ST-
A/PI version. Similarly, if there are additional boxes for frequent blockers and other information that are speci c to a newer ST-
A/PI version, metrics aren't available in these boxes and they appear to contain 0 business object instances.

Stock level of sellable materials (batch managed)


Find out more about the process ow Stock level of sellable materials (batch managed).

General Information

ID in KPI Catalog KPIM000161

This is custom documentation. For more information, please visit the SAP Help Portal 45
12/19/2022
What does this process ow measure? Measures the stock level and last movement of sellable materials
that are batch managed (on material/plant/storage location/batch
combination level)

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: All data up to the date of data collection

What data records are extracted? The storage location and batch data for materials types for trading
goods and nished products that are batch managed and where the
valuated unrestricted-use stock is greater than zero; the present
posting period at the time of data collection is considered the
current period and is used as the baseline for determining in which
period the last movement of the material stock took place

What details are extracted? As outlined in the KPI catalog entry for KPIM000161 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

Process Flow Stages, Blockers, and Other Information

 Note
Non-Standard Process Flow

This is not a typical process ow and you need to interpret the data visualized in a different way to the visualizations for
most process ows. The rst stage in this process ow represents the baseline set of business object instances created up
to the date of data collection.

This is custom documentation. For more information, please visit the SAP Help Portal 46
12/19/2022
The concept of progression doesn't apply in this case. Instead, the stage boxes under Process Flow Performance are used as
a means of providing a visual breakdown of how the business object instances in the baseline set can be categorized. This
means that the sum of the metrics in all subsequent stages equals the metrics of the baseline set in the rst stage.

Since there's no concept of progression in this case, average time metrics aren't applicable and therefore aren't available
for the lead times between stages or the average days taken to reach each stage.

Stage Description Frequent Description


Blockers/Other
Information

Material/plant/storage All material/plant/storage location ST-A/PI 01V_731* All material/plant/storage location


location combinations combinations of sellable materials that combinations for which neither a
Combinations
with stock have a stock level greater than zero at corresponding open sales order (that is, a
without open sales
the time of data collection. sales order with missing delivery) nor an
orders or outbound
open delivery (that is, a delivery with
deliveries
missing goods issue posting) exists.

ST-A/PI 01V_731* All material/plant/storage location


combinations for which at least one
Combinations with
corresponding open sales order (that is, a
open sales orders
sales order with missing delivery) exists.

ST-A/PI 01V_731* All material/plant/storage location


combinations for which at least one
Combinations with
corresponding open delivery (that is, a
open outbound
delivery with missing goods issue posting)
deliveries
exists.

Combinations with last All material/plant/storage location/batch Combinations Material/plant/storage location


goods moved over 1 combinations for which the last without plan-driven combinations of materials where planning
year ago stock movement took place over 1 year MRP with last goods for the material is something other than
ago. This is determined by the posting moved over 1 year Material requirements planning and the
period in which the goods of the ago last stock movement took place over 1
combination were last moved. year ago.

Combinations with Material/plant/storage location


trading-goods-like combinations of materials with the
materials last moved reference material type for trading goods
over 1 year ago for which the last stock movement
took place over 1 year ago.

Combinations with Material/plant/storage location


nished-product- combinations of materials with the
like materials last reference material type for nished goods
moved over 1 year for which the last stock movements
ago took place over 1 year ago.

Combinations with last All material/plant/storage Combinations Material/plant/storage location


goods moved 7-12 location/batch combinations for which without plan-driven combinations of materials where planning
periods ago the last stock movement took place 7 to MRP with last goods for the material is something other than
12 periods ago. This is determined by moved 7-12 periods Material requirements planning and the
the posting period in which the goods of ago last stock movement took place 7 to 12
the combination were last moved. periods ago.

Combinations with Material/plant/storage location


trading-goods-like combinations of materials with
materials last moved the reference material type for trading
7-12 periods ago goods for which the last stock movement
took place 7 to 12 periods ago.

This is custom documentation. For more information, please visit the SAP Help Portal 47
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Combinations with Material/plant/storage location


nished-product- combinations of materials with
like materials last the reference material type for nished
moved 7-12 periods goods for which the last stock movement
ago took place 7 to 12 periods ago.

Combinations with last All material/plant/storage Combinations Material/plant/storage location


goods moved 4-6 location/batch combinations for which without plan-driven combinations of materials where planning
periods ago the last stock movement took place 4 to MRP with last goods for the material is something other than
6 periods ago. This is determined by the moved 4-6 periods Material requirements planning and the
posting period in which the goods of the ago last stock movements took place 4 to 6
combination were last moved. periods ago.

Combinations with Material/plant/storage location


trading-goods-like combinations of materials with
materials last moved the reference material type for trading
4-6 periods ago goods for which the last stock movement
took place 4 to 6 periods ago.

Combinations with Material/plant/storage location


nished-product- combinations of materials with
like materials last the reference material type for nished
moved 4-6 periods goods for which the last stock movement
ago took place 4 to 6 periods ago.

Combinations with last All material/plant/storage Combinations Material/plant/storage location


goods moved 2-3 location/batch combinations for which without plan-driven combinations of materials where planning
periods ago the last stock movement took place 2 to MRP with last goods for the material is something other than
3 periods ago. This is determined by the moved 2-3 periods Material requirements planning and the
posting period in which the goods of the ago last stock movements took place 2 to 3
combination were last moved. periods ago.

Combinations with Material/plant/storage location


trading-goods-like combinations of materials with
materials last moved the reference material type for trading
2-3 periods ago goods for which the last stock movement
took place 2 to 3 periods ago.

Combinations with Material/plant/storage location


nished-product- combinations of materials with
like materials last the reference material type for nished
moved 2-3 periods goods for which the last stock movement
ago took place 2 to 3 periods ago.

Combinations with last All material/plant/storage Combinations Material/plant/storage location


goods moved in location/batch combinations for which without plan-driven combinations of materials where planning
previous period the last stock movement took place one MRP with last goods for the material is something other than
period ago. This is determined by the moved in previous Material requirements planning and the
posting period in which the goods of the period last stock movement took place 1 period
combination were last moved. ago.

Combinations with Material/plant/storage location


trading-goods-like combinations of materials with
materials last moved the reference material type for trading
in previous period goods for which the last stock movement
took place 1 period ago.

This is custom documentation. For more information, please visit the SAP Help Portal 48
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Combinations with Material/plant/storage location


nished-product- combinations of materials with
like materials last the reference material type for nished
moved in previous goods for which the last stock movement
period took place 1 period ago.

Combinations with last All material/plant/storage Combinations Material/plant/storage location


goods moved this location/batch combinations for which without plan-driven combinations of materials where planning
period the last stock movement took place MRP with last goods for the material is something other than
during the current period. This is moved this period Material requirements planning and the
determined by the posting period in last stock movement took place during the
which the goods of the combination were current period.
last moved.
Combinations with Material/plant/storage location
trading-goods-like combinations of materials with
materials last moved the reference material type for trading
this period goods for which the last stock movement
took place during the current period.

Combinations with Material/plant/storage location


nished-product- combinations of materials with
like materials last the reference material type for nished
moved this period goods for which the last stock movement
took place during the current period.

* This data is only available as of ST-A/PI 01V_731. Upgrading to the latest version is always recommended. Also ensure you
implement the latest version of the relevant SAP Note for your ST-A/PI version as outlined under Technical Prerequisites in the
Administration Guide .

If you're using an older ST-A/PI version, lead times aren't available when there are additional stages supported by a higher ST-
A/PI version. Similarly, if there are additional boxes for frequent blockers and other information that are speci c to a newer ST-
A/PI version, metrics aren't available in these boxes and they appear to contain 0 business object instances.

Outbound delivery item creation to goods issue posting


Find out more about the process ow Outbound delivery item creation to goods issue posting.

General Information

ID in KPI Catalog KPLE000360

What does this process ow measure? Measures the number of outbound delivery items created in the
reference period that are relevant for picking and for posting a
goods issue, and shows how many of them reached prede ned
stages of the process and how long on average this progression
took.

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -28 to -1 calendar days relative to the
date of data collection

What data records are extracted? All outbound delivery items of the sales document category for
delivery that were created in the reference period where the goods

This is custom documentation. For more information, please visit the SAP Help Portal 49
12/19/2022
movement status and the picking status of the delivery items is
either Not yet processed, Partially processed, or Completely
processed, and where the status of warehouse management
activities of the delivery items is Not relevant.

What details are extracted? As outlined in the KPI catalog entry for KPLE000360 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note

This is custom documentation. For more information, please visit the SAP Help Portal 50
12/19/2022
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Delivery items All outbound delivery items of the sales Delivery items with Delivery items classi ed with the sales
created document category for delivery that were reference to sales document category Sales order .
created in the reference period where the order item
goods movement status and the picking
status of the delivery items is either Not Delivery items with Delivery items classi ed with the sales
yet processed, Partially processed, or reference to stock document category Purchase order.
Completely processed, and where the transport order item
status of warehouse management
Delivery items Delivery items not classi ed with a sales
activities of the delivery items is Not
without reference document category, indicating that it's not
relevant.
clearly determined how the system stores
and keeps track of document data.

This stage represents additional Delivery items Delivery items that were created manually.
activities related to the previous stage. manually created A delivery item is considered manually
created if it was automatically created
from a sales order, or if it was created by a
batch user and therefore not created using
a transaction.

Delivery items Delivery items that were created with


created using transaction VL01N (Create Outbound
transaction VL01N Delivery with Order Reference), VL01
for single (Create Delivery), or VL01NO (Create
processing Outbound Delivery with Order
Reference). These transaction codes are
used to create a single document.

Delivery items Delivery items that were created with


created using transaction code VL10X, a program used
transaction VL10x to process documents collectively.
for mass processing

Delivery items Delivery items that have been


automatically automatically created from a sales order
created from sales using transaction code VA01 (Create
order Sales Documents), or VA02 (Change
Sales Documents).

Delivery items picked All outbound delivery items that also Delivery items with Delivery items where the picking request
have an actual picking date actual picking in the document ow is created after the
request after planned picking date.
planned picking date

This stage represents additional Delivery items Delivery items with a packing status Not
activities related to the previous stage. relevant for packing yet processed, Partially processed, or
Completely processed that are therefore
considered relevant for packing.

Delivery items where Delivery items with the packing status Not
packing has not yet yet processed.
started

Delivery items with Delivery items with the packing status


partial packing Partially processed.

This is custom documentation. For more information, please visit the SAP Help Portal 51
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Delivery items with Delivery items with the packing status


packing completed Completely processed.

This stage represents additional Delivery items Delivery items with a transportation
activities related to the previous stage. relevant for planning status Not yet processed,
transportation Partially processed, or Completely
planning processed, which indicates the extent
to which transportation planning has been
performed.

Delivery items not Delivery items with the transportation


yet assigned to any planning status Not yet processed.
shipment document

Delivery items Delivery items with the transportation


completely planned planning status Completely processed.
for transportation

Delivery items with All outbound delivery items that also Delivery items with Delivery items where the actual goods
goods issue posted have the goods movement status goods issue posting movement date is later than the
Completely processed and an actual later than planned planned goods movement date, which is
goods movement date at delivery header the date on which the goods must have
level, which is the date that lls the physically left the shipping point to reach
posting date of the material document the customer on time.

Delivery items Delivery items with the incompletion


incomplete for status Not yet processed for the goods
goods movement issue.

Delivery items Delivery items where an actual goods


overdue for goods movement date is not yet speci ed,
movement indicating that the goods haven't
physically left the shipping point, and the
planned goods movement date is overdue
because it's in the past.

Delivery items with Delivery items where the corresponding


header delivery header is blocked for delivery.
block

Outbound delivery item creation to goods issue posting (transfer


order)
Find out more about the process ow Outbound delivery item creation to goods issue posting (transfer order).

General Information

ID in KPI Catalog KPLE000361

What does this process ow measure? Measures the number of outbound delivery items created in the
reference period that are relevant for picking and for warehouse
management activities, and shows how many of them reached
prede ned stages of the process and how long on average this
progression took.

This is custom documentation. For more information, please visit the SAP Help Portal 52
12/19/2022
How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -28 to -1 calendar days relative to the
date of data collection

What data records are extracted? All outbound delivery items that were created in the reference
period that are relevant for picking and for warehouse management
activities and for which a goods issue is expected.

What details are extracted? As outlined in the KPI catalog entry for KPLE000361 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

This is custom documentation. For more information, please visit the SAP Help Portal 53
12/19/2022

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Delivery items All outbound delivery items that were Delivery items with Delivery items with the document category
created created in the reference period that reference to sales Sales order.
are relevant for picking and for order item
warehouse management activities and for
which a goods issue is expected. This is Delivery items with Delivery items with the document category
based on the creation date of the reference to stock Purchase order.
outbound delivery item. transport order item

Delivery items Delivery items for which a


without reference document category has not been entered

This stage represents additional Delivery items Delivery items that were created manually.
activities related to the previous stage. manually created A delivery item is considered manually
created if it was automatically created
from a sales order, or if it was created by a
batch user and therefore not created using
a transaction.

Delivery items Delivery items that were created with


created using transaction VL01N (Create Outbound
transaction VL01N Delivery with Order Reference), VL01
for single (Create Delivery), or VL01NO (Create
processing Outbound Delivery with Order
Reference). These transaction codes are
used to create a single document.

Delivery items Delivery items that were created with


created using transaction VL10X, a program used to
transaction VL10x process documents collectively.
for mass processing

Delivery items Delivery items that have been


automatically automatically created from a sales order
created from sales using transaction VA01 (Create Sales
order Documents), or VA02 (Change Sales
Documents).

Delivery items with All outbound delivery items for which Delivery items with Delivery items for which the status of
transfer order item subsequent transfer order items transfer order item warehouse management activities
created and have also been created and con rmed. created and not is Partially processed and the item has
con rmed Transfer order items with zero quantity con rmed been completely picked
aren't considered. This is based on the
transfer order creation date. Delivery items with Delivery items for which the status of
transfer order warehouse management activities is
con rmed with Completely processed and the item has
differences been partially picked

Delivery items with Delivery items for which the


transfer order transport order item creation date is after
created after the planned picking date
planned picking date

This is custom documentation. For more information, please visit the SAP Help Portal 54
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

This stage represents additional Delivery items Delivery items with the packing status Not
activities related to the previous stage. relevant for packing yet processed, Partially processed, or
Completely processed

Delivery items where Delivery items with the packing status Not
packing has not yet yet processed
started

Delivery items with Delivery items with the packing status


partial packing Partially processed

Delivery items with Delivery items with the packing status


packing completed Completely processed

This stage represents additional Delivery items Delivery items with the transportation
activities related to the previous stage. relevant for planning status Not yet planned, Partially
transportation planned, or Completely planned
planning

Delivery items not Delivery items for which the delivery is


yet assigned to any still to be processed in
shipment document transportation planning

Delivery items Delivery items for which the delivery has


completely planned been assigned to one or more shipment
for transportation documents in transportation planning

Delivery items with All outbound delivery items for which a Delivery items with Delivery items for which the actual goods
goods issue posted subsequent goods issue has also goods issue posting movement date is after the planned
been posted. This is based on the goods later than planned goods movement date
movement status Completely processed
and on the actual goods movement date. Delivery items Delivery items with the incompletion
incomplete for status Not yet processed
goods movement

Delivery items Delivery items for which an actual goods


overdue for goods movement date hasn't been entered
movement although the data collection date is after
the planned goods movement date

Delivery items with Delivery items that are entirely blocked for
header delivery delivery because the Delivery block
block (document header) indicator is set

Inbound delivery item creation to goods receipt posting


Find out more about the process ow Inbound delivery item creation to goods receipt posting.

General Information

ID in KPI Catalog KPLE000362

What does this process ow measure? Measures the number of inbound delivery items created in the
reference period that are relevant for posting a goods receipt, and
shows how many of them reached prede ned stages of the process
and how long on average this progression took.

This is custom documentation. For more information, please visit the SAP Help Portal 55
12/19/2022

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -28 to -1 calendar days relative to the
date of data collection

What data records are extracted? All inbound delivery items of the sales document category for
delivery/shipping noti cation that were created in the reference
period where the goods movement status of the delivery items is
either Not yet processed, Partially processed, or Completely
processed and where the actual delivered quantity is greater zero.

What details are extracted? As outlined in the KPI catalog entry for KPLE000362 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

This is custom documentation. For more information, please visit the SAP Help Portal 56
12/19/2022
Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Delivery items All inbound delivery items of the sales Delivery items with Delivery items that have the sales document
created document category for reference to category Purchase order and refer to items of
delivery/shipping noti cation that were purchase order purchase document category Purchase order.
created in the reference period where item
the goods movement status of the
delivery items is either Not yet Delivery items with Delivery items that have the sales document
processed, Partially reference to category Purchase order and refer to items of
processed, or Completely scheduling purchase document category Scheduling
processed and where the actual agreement item agreement.
delivered quantity is greater zero. This
is based on the creation date of the Delivery items Delivery items not classi ed with a document
inbound delivery item. without reference category.

This stage represents additional Delivery items Delivery items that were created by a dialog
activities related to the previous stage. manually created user or with a transaction code speci c
to dialog mode.

Delivery items Delivery items that were created with


created using transaction VL31N (Create Inbound Delivery).
transaction VL31N
for single
processing

This stage represents additional Delivery items with Delivery items where the date by which the
activities related to the previous stage. delivery date earlier item should be received according to the sales
than date in document is earlier than the date on which it is
purchase order to be delivered according to the purchase
item order.

Delivery items with Delivery items where the delivery date by


delivery date later which the item should be received according to
than date in the sales document is later than the date on
purchase order which it is to be delivered according to the
item purchase order.

Open delivery items Delivery items where the delivery date by


with delivery date in which the item should be received according to
the past the sales document is in the past, even though
the item is still considered open because the
goods movement status is not Completely
processed.

This is custom documentation. For more information, please visit the SAP Help Portal 57
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Open delivery items Delivery items that are still considered open
with closed because the goods movement status is
purchase order not Completely processed, even though the
items corresponding purchase order is considered
closed because either the nal delivery
indicator is set or a partial goods receipt has
been posted for a quantity that is equal to or
greater than the scheduled quantity.

This stage represents additional Delivery items Delivery items with the transportation planning
activities related to the previous stage. relevant for status of Not processed, Partially
transportation processed, or Completely processed.
planning

Delivery items not Delivery items with the transportation planning


yet assigned to any status Not processed.
shipment document

Delivery items Delivery items with the transportation planning


completely planned status Completely processed.
for transportation

This stage represents additional Delivery items Delivery items with the packing status Not
activities related to the previous stage. relevant for packing processed, Partially processed, or Completely
processed.

Delivery items Delivery items that have the packing status Not
where packing has processed.
not yet started

Delivery items with Delivery items that have the packing


partial packing status Partially processed.

Delivery items with Delivery items that have the packing


packing completed status Completely processed.

This stage represents additional Delivery items Delivery items with the warehouse management
activities related to the previous stage. relevant for activity status Not processed, Partially
warehouse processed, or Completely processed.
management

Delivery items with Delivery items with the warehouse management


transfer order item activity status Not processed.
created and not
con rmed

Delivery items with Delivery items with the warehouse management


con rmed transfer activity status Completely processed.
order

Delivery items with All inbound delivery items for which a Delivery items with Delivery items where the date on which the
goods receipt subsequent goods receipt has also goods receipt material document for the actual goods
posted been posted. This is based on the posting later than movement was posted is later than date by
goods movement status planned which the delivery should have been received
Completely processed and on the according to the sales document.
actual goods movement date.

This is custom documentation. For more information, please visit the SAP Help Portal 58
12/19/2022

Materials touched by MRP last week


Find out more about the process ow Materials touched by MRP last week.

General Information

ID in KPI Catalog KPMRP00260

What does this process ow measure? Analyzes materials affected by an MRP run in the last week

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: the six days up to the date of data
collection

What data records are extracted? All material/plant combinations affected by an MRP run in the six
days up to the date of data collection

What details are extracted? As outlined in the KPI catalog entry for KPMRP00260 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

This is custom documentation. For more information, please visit the SAP Help Portal 59
12/19/2022

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
Non-Standard Process Flow

In this process ow, the intention is to examine material/plant combinations involved in planning and not a transactional
document for which a logical progression occurs, as is the case in typical process ows. For this reason, and also because of
the high level of dependencies that exist for material/plant combinations in planning, average time metrics can't be
calculated meaningfully.

This process ow helps you to analyze data from MRP runs to identify where things are not running optimally, and where
there are issues that can result in problems in the supply chain. Of primary interest in this process ow is therefore to
examine the following:

Stages 2-5: The backlog items reported to identify where information in the system deviates from the actual status
quo of the supply and demand situation.

Stage 6: MRP lists that indicate where exceptions have occurred that have a direct impact on planning. These are
exceptions that an MRP planner should examine and resolve.

Stages 7-8: Where manufacturing orders and purchase orders are created without reference to planned orders or
purchase requisitions. This indicates that users aren't working with the results of the MRP run, and are making
planning decisions that deviate or don't respect system planning, which in turn, can have a negative follow-on impact
on future input for MRP planning.

Stage Description Frequent Description


Blockers/Other
Information

Material/plant combinations All material/plant combinations Combinations Material/plant combinations without


processed in last week affected by an MRP run in the six days without planning planning relevant change in the
by MRP up to the date of data collection. relevant change last week, based on the date of the last
in last week planning-relevant change

Combinations with Material/plant combinations where the


in-house procurement type of the material is In-
production house

Combinations with Material/plant combinations where the


external procurement type of the material is
procurement External procurement

Combinations with Material/plant combinations where the


both procurement procurement type of the material is
types Both procurement types

This is custom documentation. For more information, please visit the SAP Help Portal 60
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

ST-A/PI 01V_731* All material/plant combinations that Combinations used All material/plant combinations that
do not have a sales backlog. This in sales order item were used in a sales order in the last
Material/plant combinations
includes sales orders as well as the in last week week. This is the case if the sales order
without overdue sales
backlog for outbound deliveries. has been created in the last week.
backlog
Combinations with All material/plant combinations with an
overdue sales overdue sales order backlog. This is the
order item backlog case if the sales order is still open with
a material availability date in the past.

Combinations with All material/plant combinations with an


overdue delivery overdue delivery order backlog. This is
item backlog the case if the delivery is still open with
a material availability date in the past.

Material/plant combinations All material/plant combinations that Combinations with Material/plant combinations with an
without overdue planned don't have a planned order backlog. overdue planned overdue planned order backlog of
order backlog This includes the order types for stock order backlog of type Stock order or Individual
orders, standard purchase orders, type LA/KD customer order; a planned order is
individual customer orders and run overdue if it's open but the order nish
schedule quantities, and the backlog date is in the past
for dependent requirements
Combinations with Material/plant combinations with an
overdue planned overdue planned order backlog of
order backlog of type Standard purchase order; a
type NB planned order is overdue if it's open but
the order nish date is in the past

Combinations with Material/plant combinations with an


overdue planned overdue planned order backlog of
order backlog of type Run schedule quantity; a planned
type PE order is overdue if it's open but the
order nish date is in the past

Combinations with Material/plant combinations with an


overdue backlog of overdue planned order backlog of
dependent dependent requirement items; a
requirement items planned order is overdue if it's open but
the order nish date is in the past

Material/plant combinations All material/plant combinations that Combinations with Material/plant combinations with an
without overdue don't have a manufacturing backlog. overdue overdue production order backlog;
manufacturing backlog This includes production orders, production order a production order is overdue if
process orders, and the backlog for backlog it's open but the scheduled nish
order reservation. date is in the past

Combinations with Material/plant combinations with an


overdue process overdue process order backlog;
order backlog a process order is overdue if
it's open but the scheduled nish date
is in the past

Combinations with Material/plant combinations with an


overdue backlog of overdue backlog of order
order reservation reservation items; an order reservation
items item is overdue if the requirement date
is in the past

This is custom documentation. For more information, please visit the SAP Help Portal 61
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Material/plant combinations All material/plant combinations that Combinations with Material/plant combinations with an
without overdue purchasing don't have a purchasing backlog. overdue purchase overdue purchase requisition backlog;
backlog This includes purchase requisitions requisition item a purchase requisition is overdue if
and purchase orders. backlog it's open but the release date is in
the past

Combinations with Material/plant combinations with an


overdue purchase overdue purchase order backlog;
order item backlog a purchase order is overdue if
it's open but the delivery date is in the
past

Material/plant combinations All material/plant combinations that Combinations with Material/plant combinations where the
without MRP exception do not have the following MRP MRP list exceptions planning run created an exception
exceptions: due to opening date message because the opening date of
in the past the MRP element is in the past
MRP element rescheduled as
opening date, order start date, Combinations with Material/plant combinations where the
or order nish date that lies in MRP list exceptions planning run created an exception
the past due to start date in message because the start date of the
the past MRP element is in the past
General messages
Combinations with Material/plant combinations where the
BOM explosions
MRP list exceptions planning run created an exception
Availability check due to nish date in message because the nish date of the
the past MRP element is in the past
Rescheduling
Combinations with Material/plant combinations where the
Terminations
MRP terminations planning run created an exception
message because of MRP terminations

Combinations with Material/plant combinations where the


MRP list exceptions planning run created an exception
during message during the rescheduling
rescheduling

Combinations with Material/plant combinations where the


MRP list exceptions planning run created an
during availability exception message during the
check availability check

Combinations with Material/plant combinations where the


MRP list exceptions planning run created an exception
during BOM message during the BOM explosion
explosion

Material/plant combinations All material/plant combinations with a Combinations used Material/plant combinations that were
used in manufacturing production order that was created in but without used but, based on the number of the
order in last week the last week. planned order planned order, don't have a reference to
reference a planned order

Material/plant combinations All material/plant combinations with a Combinations used Material/plant combinations that were
used in purchase order item purchase order that was created in the but without used but, based on the number of the
in last week last week. purchase purchase requisition, don't have a
requisition reference to a purchase requisition
reference

* This data is only available as of ST-A/PI 01V_731. Upgrading to the latest version is always recommended. Also ensure you
implement the latest version of the relevant SAP Note for your ST-A/PI version as outlined under Technical Prerequisites in the
This is custom documentation. For more information, please visit the SAP Help Portal 62
12/19/2022
Administration Guide .

If you're using an older ST-A/PI version, lead times aren't available when there are additional stages supported by a higher ST-
A/PI version. Similarly, if there are additional boxes for frequent blockers and other information that are speci c to a newer ST-
A/PI version, metrics aren't available in these boxes and they appear to contain 0 business object instances.

Related Information
https://help.sap.com/docs/BPI/f5642e5272c1465986661c763b56213d/43e1400fffca47c5bca194199e479326.html

Production order creation to technical completion


Find out more about the process ow Production order creation to technical completion.

General Information

ID in KPI Catalog KPPP000160

What does this process ow measure? Measures the number of production orders created in the reference
period and shows how many of them reached prede ned stages of
the process and how long on average this progression took.

How frequently is data collected and what is the reference period Frequency: Weekly
for the data collected?
Reference period: -70 to -14 calendar days relative to the
date of data collection

What data records are extracted? All production orders that were created in the reference period.

What details are extracted? As outlined in the KPI catalog entry for KPPP000160 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

This is custom documentation. For more information, please visit the SAP Help Portal 63
12/19/2022

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Production orders All production orders that were created Production orders Production orders that were created with
created within the reference period. manually created the user type for dialog mode.

Production orders Production orders created that have a


created for sales special stock indicator for sales order
order stock.

This stage represents additional Production orders Production orders created that have a
activities related to the previous stage. without planned blank planned order number.
order reference

Production orders Production orders created that have a


created earlier than creation date that's before the planned
planned opening date of the planned order.

This is custom documentation. For more information, please visit the SAP Help Portal 64
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Production orders Production orders created that have a


created later than creation date that's after the planned
planned opening date of the planned order.

Production orders All production orders that also have an Production orders Production orders that have a scheduled
released actual release date up to the date of data released early release date that's after the actual release
collection. date.

Production orders Production orders that have a scheduled


released late release date that's before the actual
release date.

Production orders Production orders that have order item


with missing parts requirements contained in the missing
parts index.

Unreleased Production orders that aren't yet released


production orders (and aren't set to technically complete)
with overdue and where the scheduled release date is
scheduled release already in the past.

Production orders All production orders that also have an Production orders Production orders that have a scheduled
initially con rmed actual start date, which indicates when con rmed late nish date that's before the actual start
the order was considered initially date.
con rmed.
Production orders Production orders that have order items
with con rmation with entries in the index of goods
errors during goods movements with errors from
movement con rmations.

Production orders Production orders that have an actual start


not nally con rmed date but the con rmed order nish date is
blank.

Production orders All production orders that also have an Production orders Production orders that have a scheduled
delivered actual delivery or nish date, which delivered late nish date that's before the actual
indicates when the material was delivery or nish date of the order items.
produced or delivered to stock.
Production orders Production orders that have an expected
with expected scrap scrap quantity in the order items.

Delivered Production orders with goods receipt


production orders postings where the Delivery completed
without "Delivery indicator isn't set although the orders have
completed" set an actual delivery or nish date.

This stage represents additional Delivered Production orders where the goods receipt
activities related to the previous stage. production orders is posted into quality inspection stock.
with goods receipt
into quality
inspection

Delivered Production orders where the goods receipt


production orders is connected to an inspection lot in quality
with inspection lot management.
from goods receipt

This is custom documentation. For more information, please visit the SAP Help Portal 65
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Production orders Production orders where the goods receipt


with inspection lot is connected to an inspection lot in quality
with outstanding management and where the usage
stock posting decision is still outstanding such that
stock is still in quality inspection.

Delivered Production orders where the goods receipt


production orders is posted into unrestricted-use stock.
with goods receipt
into unrestricted-
use stock

Delivered production All production orders that also have a Production orders Production orders where either no goods
orders technically technical completion date, which not (fully) delivered receipt or only partial goods receipt is
completed indicates the date on which the order but technically posted and where the relevant production
status was changed to Technically completed order is set to technically completed.
completed. Also included are the
following production orders:

Production orders for which the


quantity of goods receipt for the
order items produced and posted Production orders Production orders that aren't yet set to
to stock is greater than or equal overdue for technically completed although the basic
to the total order quantity technical completion nish date is already more than 30 days in
(including scrap) that had to be by more than 30 the past.
produced in the order days

Production orders for which the


Delivery completed indicator
shows that items can be
considered closed

Production order creation to rst settlement


Find out more about the process ow Production order creation to rst settlement.

General Information

ID in KPI Catalog KPPP000161

What does this process ow measure? Measures the number of production orders relevant for settlement
that were created in the reference period and shows how many of
them reached prede ned stages of the process and how long on
average this progression took

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -70 to -14 calendar days relative to the
date of data collection

What data records are extracted? All production orders that were created in the reference period
where the actual costs or costs of sales of the orders are to be
settled in full

What details are extracted? As outlined in the KPI catalog entry for KPPP000161 on the

This is custom documentation. For more information, please visit the SAP Help Portal 66
12/19/2022
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

This is custom documentation. For more information, please visit the SAP Help Portal 67
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Production orders All production orders that are to be Production orders Production orders that have the indicator
created settled in full and that were created in the without automatic Do not calculate planned costs for
reference period. This is determined by preliminary costing order, which indicates that the planned
the date on which the order was created. costs in the order aren't calculated
automatically

Production orders Production orders that have the inactive


without preliminary individual object status Pre-costed
costing

Production orders Production orders that have the active


with errors in cost individual object status Error in
calculation cost calculation

Production orders Production orders that have the special


created for sales stock indicator for sales order stock
order

Production orders All production orders that also have an Production orders Production orders that have the inactive
released actual release date. This is determined without settlement individual object status Settlement rule
by the date on which the order was rule created
released.
Production orders Production orders that have the active
where costs are not individual object status Costs not current
current

Production orders All production orders that also have an Production orders Production orders where an entry or
initially con rmed actual start date, which speci es when with con rmation document can be found listed in the
the order was initially con rmed. errors during goods index of Goods movements with errors
movement from con rmations, which
identi es incorrect goods movement in a
con rmation corresponding to the order

Production orders Production orders where an entry or


with con rmation completion con rmation number for
errors during cost an operation corresponding to the order
posting can be found listed in the index
of Incorrect cost calculations from
con rmations

Production orders All production orders that also have an Production orders Production orders that have a technical
delivered actual delivery or nish date, which technically completion date
speci es when the material was completed
produced or delivered to stock.
Production orders Production orders that have the active
with work in individual object status Results
progress calculation analysis carried out

Delivered Production orders that have an actual


production orders delivery or nish date, which indicates
without variance that the material was produced or
calculation delivered to stock, and for which the
individual object status Variances
calculated is also inactive

Delivered production All production orders that also have a Production orders Production orders that have the active
orders rst settled settlement document that allocates the closed individual object status Closed
actual costs for the order to receiver cost
objects. This is determined by the date

This is custom documentation. For more information, please visit the SAP Help Portal 68
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

on which the settlement document was


Production orders Production orders that have more than one
created.
with more than one settlement document for the unique object
settlement number of the production order

Production order component creation to goods issue posting


Find out more about the process ow Production order component creation to goods issue posting.

 Note
This process ow is only available as of ST-A/PI 01V_731. Upgrading to the latest version is always recommended. Also
ensure you implement the latest version of the relevant SAP Note for your ST-A/PI version as outlined under Technical
Prerequisites in the Administration Guide .

General Information

ID in KPI Catalog KPPP000162

What does this process ow measure? Measures the number of stock-relevant components reserved in
the de ned timeframe and checks the lead time until when the
component was actually consumed for manufacturing. This process
ow also indicates whether problems related to insufficient stock or
supply chain planning might delay component consumption and
therefore manufacturing.

How frequently is data collected and what is the reference period Frequency: every 3 days
for the data collected?
Reference period: -14 to -1 calendar days relative to the
date of data collection

What data records are extracted? All production order components that are relevant for inventory
management for which goods movement is allowed and that have a
required quantity greater than zero

What details are extracted? As outlined in the KPI catalog entry for KPPP000162 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

This is custom documentation. For more information, please visit the SAP Help Portal 69
12/19/2022

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Production order All production order components created Production order Production order components with special
components created in the reference period. This is components created stock indicator set to Orders on hand.
determined by the date on which the for sales order
production order component was created.
Production order Production order components for which
components with the back ush indicator is set.
back ush indicator Each material component is assigned to
an operation in the production order. If
a material component is back ushed, the
system posts the withdrawal only when
the operation is con rmed. The withdrawal
is then posted automatically.

This is custom documentation. For more information, please visit the SAP Help Portal 70
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Production order Production order components from


components from different plants.
different plants

Production order Production order components for which


components marked the deletion indicator has been set.
for deletion

This stage represents additional Production order Production order components for which
activities related to the previous stage. components with the requested quantity of the material is
planned only required in over 4 weeks in the future.
requirements date
more than 4 weeks
in the future

Production order Production order components for which


components marked the Missing Part indicator is set.
as missing parts This means that an error message will be
issued in the event of negative availability.

Production order All production orders released for Open production Production order components that are
released for components. This is determined by the order components open because no deletion indicator has
components date on which the order was released. with partial been set and the nal issue information is
withdrawal blank and for which material has been
partially withdrawn, so the withdrawn
quantity is smaller than the required
quantity.

Open production Production order components that are


order components open because the deletion indicator and
with planned the nal issue indicator have not been set,
requirements date in the withdrawn quantity is smaller than the
the past required quantity, and the requirements
date is in the past compared to the date of
data collection.

Production order Production order components for which


components with the Failed Goods Movement indicator has
con rmation errors been set.
during goods
movement

This stage represents additional Open production Production order components that are
activities related to the previous stage. order components open because no deletion indicator has
with no been set, the nal issue information
unrestricted-use is blank, and the withdrawn quantity is
stock smaller than the required quantity without
unrestricted-use stock

Open production Production order components that are


order components open because no deletion indicator has
with less been set, the nal issue information
unrestricted-use is blank, and the withdrawn quantity is
stock than required smaller than the required quantity for
which the unrestricted-use stock is
smaller than the required quantity.

This is custom documentation. For more information, please visit the SAP Help Portal 71
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Open production Production order components that are


order components open because no deletion indicator has
with quality been set, the nal issue information
inspection stock is blank, and the withdrawn quantity is
smaller than the required quantity that has
a quality inspection stock greater zero.

This stage represents additional Production order Production order components for which
activities related to the previous stage. components with purchase order items exist (for the same
overdue purchase material and plant combination) with a
order items planned delivery date in the past and
outstanding quantities.

Open production Open production order components for


order components which purchase order items exist (for the
with open purchase same material and plant combination) with
order items a planned delivery date in the future and
outstanding quantities.

Production order Production order components for which


components with purchase order items exist (for the same
overdue purchase material and plant combination) with a
requisition items release date in the past and outstanding
quantities.

This stage represents additional Production order Production order components for which
activities related to the previous stage. components with manufacturing orders exist (for the same
other overdue material and plant combination) with a
production orders scheduled nish date in the past and
outstanding quantities.

Open production Open production order components for


order components which manufacturing orders exist (for the
with other open same material and plant combination) with
production orders a scheduled nish date in the future and
outstanding quantities.

Production order Production order components for which


components with planned orders exist (for the same
overdue planned material and plant combination) with an
orders order nish date in the past and
outstanding quantities.

First goods issue All production order components for Goods issue earlier Production order components for which
posted for which a rst goods issue has also been than planned the creation date of the goods issue is
components posted. This is determined by the date requirements date earlier than the planned requirements
on which the goods issue was entered in date.
the system.
Goods issue later Production order components for which
than planned the creation date of the goods issue is
requirements date later than the planned requirements date.

Components with Production order components for which


withdrawal quantity the quantity withdrawn is greater than the
greater than planned requirement quantity.

This is custom documentation. For more information, please visit the SAP Help Portal 72
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Components with Production order components with the


nal issue indicator nal issue indicator set for which
and withdrawal the quantity withdrawn is less than the
quantity less than requirement quantity.
planned

Process order creation to technical completion


Find out more about the process ow Process order creation to technical completion.

General Information

ID in KPI Catalog KPPP000260

What does this process ow measure? Measures the number of process orders created in the reference
period and shows how many of them reached prede ned stages of
the process and how long on average this progression took.

How frequently is data collected and what is the reference period Frequency: Weekly
for the data collected?
Reference period: -70 to -14 calendar days relative to the
date of data collection

What data records are extracted? All process orders that were created in the reference period.

What details are extracted? As outlined in the KPI catalog entry for KPPP000260 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

This is custom documentation. For more information, please visit the SAP Help Portal 73
12/19/2022

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Process orders All process orders that were created Process orders Process orders that were created with the
created within the reference period. manually created user type for dialog mode.

Process orders Process orders created that have a special


created for sales stock indicator for sales order stock.
order

This stage represents additional Process orders Process orders created that have a blank
activities related to the previous stage. without planned planned order number.
order reference

Process orders Process orders created that have a


created earlier than creation date that's before the planned
planned opening date of the planned order.

This is custom documentation. For more information, please visit the SAP Help Portal 74
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Process orders Process orders created that have a


created later than creation date that's after the planned
planned opening date of the planned order.

Process orders All process orders that also have an Process orders Process orders that have a scheduled
released actual release date up to the date of data released early release date that's after the actual release
collection. date.

Process orders Process orders that have a scheduled


released late release date that's before the actual
release date.

Process orders with Process orders that have order item


missing parts requirements contained in the missing
parts index.

Unreleased process Process orders that aren't yet released


orders with overdue (and aren't set to technically completed)
scheduled release and where the scheduled release date is
already in the past.

Process orders All process orders that also have an Process orders Process orders that have a scheduled
initially con rmed actual start date, which indicates when con rmed late nish date that's before the actual start
the order was considered initially date.
con rmed.
Process orders with Process orders that have order items with
con rmation errors entries in the index of goods movements
during goods with errors from con rmations.
movement

Process orders not Process orders that have an actual start


nally con rmed date but the con rmed order nish date is
blank.

Process orders All process orders that also have an Process orders Process orders that have a scheduled
delivered actual delivery or nish date, which delivered late nish date that's before the actual
indicates when the material was delivery or nish date of the order items.
produced or delivered to stock.
Process orders with Process orders that have an expected
expected scrap scrap quantity in the order items.

Delivered process Process orders with goods receipt


orders without postings where the Delivery completed
"Delivery indicator isn't set although the orders have
completed" set an actual delivery or nish date.

This stage represents additional Delivered process Process orders where the goods receipt is
activities related to the previous stage. orders with goods posted into quality inspection stock.
receipt into quality
inspection

Delivered process Process orders where the goods receipt is


orders with connected to an inspection lot in quality
inspection lot from management.
goods receipt

This is custom documentation. For more information, please visit the SAP Help Portal 75
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Process orders with Process orders where the goods receipt is


inspection lot with connected to an inspection lot in quality
outstanding stock management and where the usage
posting decision is still outstanding such that
stock is still in quality inspection.

Delivered process Process orders where the goods receipt is


orders with goods posted into unrestricted-use stock.
receipt into
unrestricted-use
stock

Delivered process All process orders that also have a Process orders not Process orders where either no goods
orders technically technical completion date, which (fully) delivered but receipt or only partial goods receipt is
completed indicates the date on which the order technically posted and where the relevant process
status was changed to 'Technically completed order is set to technically completed.
completed'. Also taken into account are
the following process orders:

Process orders for which the


quantity of goods receipt for the
order items produced and posted Process orders Process orders that aren't yet set to
to stock is greater than or equal overdue for technically completed although the basic
to the total order quantity technical completion nish date is already more than 30 days in
(including scrap) that had to be by more than 30 the past.
produced in the order days

Process orders for which the


Delivery completed indicator
shows that items can be
considered closed

Process order creation to rst settlement


Find out more about the process ow Process order creation to rst settlement.

General Information

ID in KPI Catalog KPPP000261

What does this process ow measure? Measures the number of process orders relevant for settlement
that were created in the reference period and shows how many of
them reached prede ned stages of the process and how long on
average this progression took

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -70 to -14 calendar days relative to the
date of data collection

What data records are extracted? All process orders that were created in the reference period where
the actual costs or costs of sales of the orders are to be settled in
full

What details are extracted? As outlined in the KPI catalog entry for KPPP000261 on the

This is custom documentation. For more information, please visit the SAP Help Portal 76
12/19/2022
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

This is custom documentation. For more information, please visit the SAP Help Portal 77
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Process orders All process orders that are to be settled Process orders Process orders that have the indicator Do
created in full and that were created in the without automatic not calculate planned costs for order,
reference period. This is determined by preliminary costing which speci es that the planned costs in
the date on which the order was created. the order aren't calculated automatically

Process orders Process orders that have the inactive


without preliminary individual object status Pre-costed
costing

Process orders with Process orders that have the active


errors in cost individual object status Error in
calculation cost calculation

Process orders Process orders that have the special stock


created for sales indicator for sales order stock
order

Process orders All process orders that also have an Process orders Process orders that have the inactive
released actual release date. This is determined without settlement individual object status Settlement rule
by the date on which the order was rule created
released.
Process orders Process orders that have an active
where costs are not individual object status Costs not current
current

Process orders All process orders that also have an Process orders with Process orders where an entry or
initially con rmed actual start date, which speci es when con rmation errors document can be found listed in the
the order was initially con rmed. during goods index of Goods movements with errors
movement from con rmations, which
identi es incorrect goods movement in a
con rmation corresponding to the order

Process orders with Process orders where an entry or


con rmation errors completion con rmation number for
during cost posting an operation corresponding to the order
can be found listed in the index
of Incorrect cost calculations from
con rmations

Process orders All process orders that also have an Process orders Process orders that have a technical
delivered actual delivery or nish date, which technically completion date
speci es when the material was completed
produced or delivered to stock.
Process orders with Process orders that have the active
work in progress individual object status Results
calculation analysis carried out

Process orders Process orders for which the individual


without variance object status Variances calculated is
calculation inactive

Delivered process All process orders that also have a Process orders Process orders that have the active
orders rst settled settlement document that allocates the closed individual object status Closed
actual costs for the order to receiver cost
objects. This is determined by the date Process orders with Process orders that have more than one
on which the settlement document was more than one settlement document for the unique object
created. settlement number of the process order

This is custom documentation. For more information, please visit the SAP Help Portal 78
12/19/2022

Process order component creation to goods issue posting


Find out more about the process ow Process order component creation to goods issue posting.

 Note
This process ow is only available as of ST-A/PI 01V_731. Upgrading to the latest version is always recommended. Also
ensure you implement the latest version of the relevant SAP Note for your ST-A/PI version as outlined under Technical
Prerequisites in the Administration Guide .

General Information

ID in KPI Catalog KPPP000262

What does this process ow measure? Measures the number of stock-relevant components reserved in
the de ned timeframe and checks the lead time until when the
component was actually consumed for manufacturing. This process
ow also indicates whether problems related to insufficient stock or
supply chain planning might delay component consumption and
therefore manufacturing.

How frequently is data collected and what is the reference period Frequency: every 3 days
for the data collected?
Reference period: -14 to -1 calendar days relative to the
date of data collection

What data records are extracted? Measures all process order components that are relevant for
inventory management, for which goods movement is allowed and
the required quantity is greater than zero.

What details are extracted? As outlined in the KPI catalog entry for KPPP000262 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

This is custom documentation. For more information, please visit the SAP Help Portal 79
12/19/2022

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Process order All process order components that were Process order Process order components with special
components created created in the reference period. This is components created stock indicator set as “Orders on hand”
determined by the date on which the for sales order
process order component was created.
Process order Process order components for which the
components with back ush indicator is set. Each
back ush indicator material component is assigned to an
operation in the process order. If
a material component is back ushed, the
system posts the withdrawal only when
the operation is con rmed. The withdrawal
is then posted automatically.

This is custom documentation. For more information, please visit the SAP Help Portal 80
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Process order Process order components from different


components from plants.
different plants

Process order Process order components for which the


components marked deletion indicator has been set.
for deletion

This stage represents additional Process order Production order components for which
activities related to the previous stage. components with the requested quantity of the material is
planned only required in over 4 weeks in the future.
requirements date
more than 4 weeks
in the future

Process order Process order components for which the


components marked Missing Part indicator is set. This means
as missing parts that an error message will be issued in the
event of negative availability.

Process order All process orders released for Open process order Process order components that are open
released for components. This is determined by the components with because no deletion indicator has been set
components date on which the order was released partial withdrawal and the nal issue information is blank
and for which material has been partially
withdrawn, so the withdrawn quantity is
smaller than the required quantity.

Open process order Process order components that are open


components with because the deletion indicator and the
planned nal issue indicator have not been set, the
requirements date in withdrawn quantity is smaller than the
the past required quantity, and the requirements
date is in the past compared to the date of
data collection.

Process order Process order components for which the


components with Failed Good Movement indicator has been
con rmation errors set.
during goods
movement

This stage represents additional Open process order Process order components that are open
activities related to the previous stage. components with no because no deletion indicator has
unrestricted-use been set, the nal issue information is
stock blank, and the withdrawn quantity is
smaller than the required quantity without
unrestricted-use stock.

Open process order Process order components that are open


components with because no deletion indicator has been
less unrestricted- set, the nal issue information
use stock than is blank, and the withdrawn quantity is
required smaller than the required quantity without
unrestricted-use stock.

This is custom documentation. For more information, please visit the SAP Help Portal 81
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Open process order Process order components that are open


components with because no deletion indicator has been
quality inspection set, the nal issue information
stock is blank, and the withdrawn quantity is
smaller than the required quantity that has
a quality inspection stock greater zero.

This stage represents additional Process order Process order components for which
activities related to the previous stage. components with purchase order items exist (for the same
overdue purchase material and plant combination) with a
order items planned delivery date in the past and
outstanding quantities.

Open process order Open process order components for which


components with purchase order items exist (for the same
open purchase material and plant combination) with a
order items planned delivery date in the future and
outstanding quantities.

Process order Process order components for which


components with purchase requisition items exist (for the
overdue purchase same material and plant combination) with
requisition items a release date in the past and outstanding
quantities.

This stage represents additional Process order Process order components for which
activities related to the previous stage. components with manufacturing orders exist (for the same
other overdue material and plant combination) with a
process orders scheduled nish date in the past and
outstanding quantities.

Open process order Open process order components for which


components with manufacturing orders exist (for the same
other open process material and plant combination) with a
orders scheduled nish date in the future and
outstanding quantities.

Process order Process order components for which


components with planned orders exist (for the same
overdue planned material and plant combination) with an
orders order nish date in the past and
outstanding quantities.

First goods issue All process order components for which Goods issue earlier Process order components for which the
posted for also a rst goods issue was posted. This than planned creation date of the goods issue is
components is based on the date the goods issue was requirements date earlier than the planned requirements
entered in the system. date.

Goods issue later Process order components for which the


than planned creation date of the goods issue is
requirements date later than the planned requirements date.

Components with Process order components for which the


withdrawal quantity quantity withdrawn is greater than
greater than planned the requirement quantity.

This is custom documentation. For more information, please visit the SAP Help Portal 82
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Components with Process order components with the nal


nal issue indicator issue indicator set for which the
and withdrawal quantity withdrawn is less than the
quantity less than requirement quantity.
planned

WBS element creation (without investment pro le) to closure


Find out more about the process ow WBS element creation (without investment pro le) to closure.

General Information

ID in KPI Catalog KPPROJ0360

What does this process ow measure? Measures the number of work breakdown structure (WBS)
elements created in the reference period and shows how many of
them reached prede ned stages of the process and how long on
average this progression took. Only WBS elements without an
investment pro le are considered.

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -550 to -180 calendar days relative to
the date of data collection

What data records are extracted? All WBS elements without an investment pro le that were created
in the reference period

What details are extracted? As outlined in the KPI catalog entry for KPPROJ0360 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

This is custom documentation. For more information, please visit the SAP Help Portal 83
12/19/2022

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Blockers/Other Description


Information

WBS elements created All WBS elements that were WBS elements where planning WBS elements with the status
created in the reference period. is locked Planning locked.

WBS elements where date WBS elements with the status


de nition is locked Date de nition locked.

WBS elements with locked WBS elements with the status


budget management Budget management locked.

WBS elements de ned as WBS elements that are de ned


billing elements as billing elements so that
billing can take place.

This stage represents WBS elements with locked WBS elements with the status
additional activities related to account assignments Account assignment locked.
the previous stage.

This is custom documentation. For more information, please visit the SAP Help Portal 84
12/19/2022

Stage Description Frequent Blockers/Other Description


Information

WBS elements with locked WBS elements with the status


master data Master data locked.

WBS elements completely WBS elements with the status


locked Locked.

Budgeted WBS elements WBS elements with the status


Budgeted.

WBS elements released All WBS elements that have Released WBS elements with WBS elements with the status
been released. open PR commitment item Released that have an open
assigned purchase request commitment
item assigned to them.

Released WBS elements with WBS elements with the status


open PO commitment item Released that have an open
assigned purchase order
commitment item assigned to
them.

Released WBS elements with WBS elements with the status


released PM/CS order Released that have a released
assigned PM/CS order assigned to them.

Released WBS elements with WBS elements with the status


released internal order Released that have a released
assigned internal order assigned to them

WBS elements rst settled All WBS elements that have WBS elements with existing WBS elements orders that have
been settled. For the lead time project stock the special stock indicator for
calculation, the rst settlement project stock.
of the WBS element is taken
into account. WBS elements last settled over WBS elements that were last
1 year ago settled more than 1 year ago,
which can indicate that the WBS
element is outdated and can be
closed.

WBS elements settled 2-12 WBS elements that were settled


times between 2 and 12 times.

WBS elements settled more WBS elements that were settled


than 12 times more than 12 times.

WBS elements closed All WBS elements that have Closed WBS elements with WBS elements with the status
been closed. released PM/CS order Closed that have a released
assigned PM/CS order assigned to them.

Closed WBS elements with WBS elements with the status


released internal order Closed that have a released
assigned internal order assigned to them.

WBS element creation (with investment pro le) to closure


Find out more about the process ow WBS element creation (with investment pro le) to closure.

General Information

This is custom documentation. For more information, please visit the SAP Help Portal 85
12/19/2022

ID in KPI Catalog KPPROJ0361

What does this process ow measure? Measures the number of work breakdown structure (WBS)
elements created in the reference period and shows how many of
them reached prede ned stages of the process and how long on
average this progression took. Only WBS elements with an
investment pro le are considered.

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -550 to -180 calendar days relative to
the date of data collection

What data records are extracted? All WBS elements with an investment pro le that were created in
the reference period.

What details are extracted? As outlined in the KPI catalog entry for KPPROJ0361 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

This is custom documentation. For more information, please visit the SAP Help Portal 86
12/19/2022
Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

WBS elements created All WBS elements that were created WBS elements WBS elements with the status Planning
in the reference period. where planning is locked.
locked

WBS elements WBS elements with the status Date


where date de nition locked.
de nition is locked

WBS elements with WBS elements with the status Budget


locked budget management locked.
management

WBS elements WBS elements that are de ned as billing


de ned as billing elements so that billing can take place.
elements

This stage represents additional WBS elements with WBS elements with the status Account
activities related to the previous locked account assignment locked.
stage. assignments

WBS elements with WBS elements with the status Master


locked master data data locked.

WBS elements WBS elements with the status Locked.


completely locked

Budgeted WBS WBS elements with the status Budgeted.


elements

WBS elements released All WBS elements that have been Released WBS WBS elements with the status Released
released. elements without that don't have an asset under
AuC assigned construction assigned to them.

Released WBS WBS elements with the status Released


elements with that have a capitalized asset under
capitalized AuC not construction that's not deactivated
deactivated assigned to them.

This stage represents additional Released WBS WBS elements with the status Released
activities related to the previous elements with open that have an open purchase request
stage. PR commitment commitment item assigned to them.
item assigned

Released WBS WBS elements with the status Released


elements with open that have an open purchase order
PO commitment commitment item assigned to them.
item assigned

This is custom documentation. For more information, please visit the SAP Help Portal 87
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Released WBS WBS elements with status Released that


elements with have a released PM/CS order assigned to
released PM/CS them
order assigned

Released WBS WBS elements with the status Released


elements with that have a released internal
released internal order assigned to them.
order assigned

WBS elements rst settled All WBS elements that have been WBS elements with WBS elements orders that have the
settled. For the lead time existing project special stock indicator for project stock.
calculation, the rst settlement of stock
the WBS element is taken into
account. WBS elements last WBS elements that were last settled more
settled over 1 year than 1 year ago, which can indicate that
ago the WBS element is outdated and can be
closed.

WBS elements WBS elements that were settled between


settled 2-12 times 2 and 12 times.

WBS elements WBS elements that were settled more


settled more than than 12 times.
12 times

WBS elements closed All WBS elements that have been Closed WBS WBS elements with the status Closed
closed. elements with AuC that have an asset under construction
not deactivated that's not deactivated assigned to them.

Closed WBS All WBS elements with the status Closed


elements with that have a released PM/CS
released PM/CS order assigned to them.
order assigned

Closed WBS All WBS elements with the status Closed


elements with that have a released internal
released internal order assigned to them.
order assigned

Purchase order item creation to GR/IR clearing


Find out more about the process ow Purchase order item creation to GR/IR clearing.

General Information

ID in KPI Catalog KPPURCH260

What does this process ow measure? Measures the number of purchase order items created in the
reference period for which a goods receipt as well as an invoice
receipt clearing are expected and shows how many of them
reached prede ned stages of the process and how long on average
this progression took

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
This is custom documentation. For more information, please visit the SAP Help Portal 88
12/19/2022
Reference period: -70 to -14 calendar days relative to the
date of data collection

What data records are extracted? All standard purchase order items for which both a goods receipt
and an invoice receipt are expected that were created in the
reference period. Deleted purchase order items or items of deleted
purchase orders aren't considered.

What details are extracted? As outlined in the KPI catalog entry for KPPURCH260 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note

This is custom documentation. For more information, please visit the SAP Help Portal 89
12/19/2022
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Purchase order items All standard purchase order items for Invoice receipt Purchase order items where the invoice
created which both a goods receipt and an invoice created before receipt was entered before the goods
receipt are expected that were created in goods receipt receipt
the reference period. Deleted purchase
order items or items of deleted purchase
orders aren't considered.

This stage represents additional Purchase order Purchase order items with a release group
activities related to the previous stage. items waiting for that have the purchasing document
Metrics aren't available for this stage but approval processing state In release
additional blockers and other
information are provided. Purchase order Purchase order items with a release group
items approved that have the purchasing document
processing state Release completed

Purchase order Purchase order items with a release group


items rejected that have the purchasing document
processing state Rejected

Goods receipts All purchase order items for which also a Goods receipt: Purchase order items where the goods
created goods receipt was created. This is GR/IR not cleared receipt has been posted but the
determined based on the date on which a corresponding invoice receipt isn't yet
goods receipt was entered. If more than assigned
one goods receipt was entered, the most
recent date is considered when
determining the average times.

Supplier invoices All purchase order items for which a Invoice receipt: Purchase order items where the invoice
created supplier invoice was also created. This is GR/IR not cleared receipt has been posted but the
determined based on the date on which corresponding goods receipt isn't
the invoice was issued by the supplier. If assigned yet
there's more than one invoice receipt
entered, the most recent date is
considered when determining the average
times.

FI-AP items cleared All purchase orders that also have a GR/IR clearing not Purchase order items where a clearing
cleared invoice up to the date of data okay took place between subsequent GR and IR
collection. accounting documents that aren't related
to each other, which therefore suggests
that clearing was forced

Purchase order item creation to invoice receipt creation


Find out more about the process ow Purchase order item creation to invoice receipt creation.

General Information

ID in KPI Catalog KPPURCH261

What does this process ow measure? Measures the number of purchase order items created in the

This is custom documentation. For more information, please visit the SAP Help Portal 90
12/19/2022
reference period for which a goods receipt as well as an invoice
receipt are expected and shows how many of them reached
prede ned stages of the process and how long on average this
progression took.

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -49 to -21 calendar days relative to the
date of data collection

What data records are extracted? All standard purchase order items for which both a goods receipt
and an invoice receipt are expected that were created in the
reference period.

What details are extracted? As outlined in the KPI catalog entry for KPPURCH261 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

This is custom documentation. For more information, please visit the SAP Help Portal 91
12/19/2022
Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Purchase order items All standard purchase order items for Purchase order Purchase orders items for which a
created which both a goods receipt and an invoice items without reference to a purchase requisition doesn't
receipt are expected that were created in purchase requisition exist.
the reference period. reference

Purchase order Purchase orders items created without a


items without reference to a material number (free-text
material number material).

Purchase order Purchase order items created without


items without reference to a purchasing information
agreement or record or to an existing outline agreement.
purchasing info
record

Purchase order Purchase order items created without


items without reference to any outline agreement, which
outline agreement indicates off-contract spend.

This stage represents additional Purchase order Purchase order items for which a block
activities related to the previous stage. items blocked indicator set.

Purchase order Purchase order items for which a deletion


items deleted indicator set.

Open purchase Purchase order items that are open


order items overdue (neither deletion nor nal delivery
for delivery indicator is set) and have either not been
delivered or only partially delivered
although the planned delivery date is
already in the past.

This stage represents additional Purchase order Purchase order items with a release group
activities related to the previous stage. items waiting for that have the purchasing document
approval processing status In release.

Purchase order Purchase order items with a release group


items approved that have the purchasing document
processing status Release completed.

Purchase order Purchase order items with a release group


items rejected that have the purchasing document
processing status Rejected

Goods receipts All purchase order items for which also a Purchase order Purchase order items for which the
created goods receipt was created. This is items with partial delivered quantity is less than the quantity
determined based on the date on which a goods receipt ordered.
goods receipt was entered. If more than
one goods receipt was entered, the most
This is custom documentation. For more information, please visit the SAP Help Portal 92
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

recent date is considered when


Purchase order Purchase order items for which at least
determining the average times.
items with canceled one goods receipt was canceled.
goods receipt

Purchase order Purchase order items for which a delivery


items with goods is still expected by the system although a
receipt but no goods receipt amount has already been
"Delivery posted.
completed" set

Goods receipt Purchase order items for which the


created later than delivery occurred later than the planned
planned delivery date in the scheduling agreement.

Goods receipt Purchase order items for which the goods


created earlier than receipt was posted earlier than the
planned calculated delivery date.

This stage represents additional Purchase order Purchase order items where the goods
activities related to the previous stage. items with goods receipt is posted into quality inspection
receipt into quality stock.
inspection

Purchase order Purchase order items where the goods


items with receipt is connected to an inspection lot in
inspection lot from quality management.
goods receipt

Purchase order Purchase order items where the goods


items with receipt is connected to an inspection lot in
inspection lot with quality management and the usage
outstanding stock decision is still outstanding such that
posting stock is still in quality inspection.

Supplier invoices All purchase order items for which a Invoice receipt Purchase order items for which either the
created supplier invoice was also created. This is created before invoice receipt was created before the
determined based on the date on which goods receipt goods receipt or the invoice receipt exists
the invoice was entered. If there's more without a corresponding goods receipt.
than one invoice receipt entered, the
most recent date is considered when Purchase order Purchase order items for which either no
determining the average times. items with partial further goods receipt is expected and the
invoice receipt delivered quantity is greater than the
invoiced quantity, or the goods receipt
doesn't exist and the ordered quantity is
greater than the invoiced quantity.

Purchase order Purchase order items for which the invoice


items with canceled receipt was canceled.
invoice receipt

Purchase order Purchase order items with open


items with open commitment items in Controlling.
commitment items

Purchase order item creation (without GR) to FI-AP clearing


Find out more about the process ow Purchase order item creation (without GR) to FI-AP clearing.

This is custom documentation. For more information, please visit the SAP Help Portal 93
12/19/2022

General Information

ID in KPI Catalog KPPURCH265

What does this process ow measure? Measures the number of standard purchase orders created in the
reference period for which invoice receipt clearing in FI-AP is
expected and shows how many of them reached prede ned stages
of the process and how long on average this progression took

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -84 to -28 calendar days relative to the
date of data collection

What data records are extracted? All purchase orders for which an invoice receipt is expected that
were created in the reference period

What details are extracted? As outlined in the KPI catalog entry for KPPURCH265 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

This is custom documentation. For more information, please visit the SAP Help Portal 94
12/19/2022
Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Purchase order items All purchase orders for which an invoice Purchase order Purchase orders items for which there's no
created receipt is expected that were created in items without reference to a purchase requisition, which
the reference period. purchase requisition is identi ed when the corresponding eld
reference is initial
 Note
Purchase order Purchase order items that were created
A goods receipt isn't a requirement
items manually with the user type for dialog mode
and stock transport orders aren't
created
considered.
Purchase order Purchase order items with a deletion
items blocked indicator (S) denoting they've been
blocked

Purchase order Purchase order items with a deletion


items deleted indicator (L) denoting they've been
deleted

This stage represents additional Purchase order Purchase order items with a release group
activities related to the previous stage. items waiting for that have the purchasing document
approval processing status In release

Purchase order Purchase order items with a release group


items approved that have the purchasing document
processing status Release completed.

Purchase order Purchase order items with a release group


items rejected that have the purchasing document
processing status Rejected

Supplied invoices All purchase order items for which a Invoice receipt Purchase order items for which the
created (partial) supplier invoice was also created earlier than corresponding invoice receipt document
created until the date of data collection. planned date is before the planned invoice receipt
This is determined based on the date on date
which the invoice receipt was entered. If
there's more than one invoice receipt Partial invoice Purchase order items for which only a
entered, the most recent date is receipt and nal partial invoice receipt (rather than the full
considered when determining the average invoice indicator not quantity) has been entered and a nal
times. set invoice indicator hasn’t been set (denoting
that more invoice receipts are pending)

Purchase order Purchase order items with commitment


items with open items related to the purchase order that
commitment item still contain a positive open quantity and
value

This is custom documentation. For more information, please visit the SAP Help Portal 95
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Open purchase Purchase order items where the full


order items with invoice quantity has yet been received
planned delivery although the planned delivery date is in
date in the past the past

FI-AP items created All purchase order items that are also FI-AP items Purchase order items for which an open
fully invoiced and for which an item was currently blocked item has been created in FI-AP for which a
created in FI-AP. This also includes partial for payment payment block is currently set
supplier invoices for which the nal
invoice indicator has been set. This is FI-AP items Purchase order items for which an open
determined based on the date on which previously blocked item has been created in FI-AP for which a
the nal invoice receipt was entered. for payment payment block has been removed

FI-AP clearing All purchase order items for which the FI-AP items not Purchase order items for which an open
documents created open items in FI-AP have also been cleared via payment item has been created in FI-AP that was
cleared (and clearing documents have run cleared manually rather than in a payment
been created) up to the date of data run (based on the transaction code of the
collection. This is determined based on clearing)
the date on which the clearing document
was entered. Payment terms Purchase orders with a clearing document
different in FI-AP where the payment terms in the purchase
and purchase order orders don't match those in the clearing
document

Purchase order item creation (subcontracting) to invoice receipt


creation
Find out more about the process ow Purchase order item creation (subcontracting) to invoice receipt creation.

General Information

ID in KPI Catalog KPPURCH266

What does this process ow measure? Measures the number of subcontracting purchase order
items created in the reference period for which a goods receipt and
an invoice receipt are expected and shows how many of them
reached prede ned stages of the process within this selected
timeframe and how long on average this progression took.

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -49 to -21 calendar days relative to the
date of data collection

What data records are extracted? All subcontracting purchase order items created in the reference
period for which both a goods receipt and an invoice receipt are
expected.

What details are extracted? As outlined in the KPI catalog entry for KPPURCH266 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

This is custom documentation. For more information, please visit the SAP Help Portal 96
12/19/2022

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Purchase order items All subcontracting purchase order items Purchase order Subcontracting purchase orders items for
created created in the reference period for which items without which a reference to a purchase requisition
both a goods receipt and an purchase requisition doesn't exist.
invoice receipt are expected. reference

Purchase order Subcontracting purchase order items for


items blocked which a block indicator is set.

This is custom documentation. For more information, please visit the SAP Help Portal 97
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Purchase order Subcontracting purchase order items for


items deleted which a deletion indicator is set.

This stage represents additional Purchase order Subcontracting purchase order items with
activities related to the previous stage. items waiting for a release group that have the purchasing
approval document processing status In release.

Purchase order Subcontracting purchase order items with


items approved a release group that have the purchasing
document processing status Release
completed.

Purchase order Subcontracting purchase order items with


items rejected a release group that have the purchasing
document processing status Rejected.

This stage represents additional Open purchase Open subcontracting purchase order items
activities related to the previous stage. order items where where the rst material from
rst required the component list shows a requirement
component quantity quantity greater than what was found in
exceeds the subcontracting stock for the same
subcontracting vendor/material/plant combination.
stock This indicates that a full goods issue
wasn't yet posted for the
relevant component.

Open purchase Open subcontracting purchase order items


order items with for which a material movement with
rst component not movement type Goods issue warehouse
issued according to to subcontracting stock wasn't found
plan with the same quantity as the requirement
quantity of the rst material from the
component list. This indicates that a full
goods issue wasn't yet posted for the
relevant component or that more quantity
was issued than planned.

Open purchase Open subcontracting purchase order items


order items overdue that weren't or were only
for delivery partially delivered although the planned
delivery date is already in the past.

Goods receipts All subcontracting purchase order items Purchase order Subcontracting purchase order items for
created for which a goods receipt was also items with partial which the delivered quantity is less than
created. This is determined based on the goods receipt the quantity ordered.
date on which a goods receipt was
entered. If more than one goods receipt Purchase order Subcontracting purchase order items for
was entered, the most recent date is items with canceled which at least one goods receipt was
considered when determining the average goods receipt canceled.
times.
Goods receipt Subcontracting purchase order items for
created later than which the delivery occurred later than the
planned planned delivery date in the scheduling
agreement.

This stage represents additional Purchase order Subcontracting purchase order items
activities related to the previous stage. items with goods where the goods receipt is posted into
receipt into quality quality inspection stock.
inspection

This is custom documentation. For more information, please visit the SAP Help Portal 98
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Purchase order Subcontracting purchase order items


items with where the goods receipt is connected to
inspection lot from an inspection lot in quality management.
goods receipt

Purchase order Subcontracting purchase order items


items with where the goods receipt is connected to
inspection lot with an inspection lot in quality management
outstanding stock and the usage decision is still outstanding
posting such that stock is still in quality
inspection.

Supplier invoices All subcontracting purchase order items Invoice receipt Subcontracting purchase order items for
created for which a supplier invoice was also created before which either the invoice receipt was
created. This is determined based on the goods receipt created before the goods receipt or the
date on which the invoice was entered. If invoice receipt exists without a
there's more than one invoice receipt corresponding goods receipt.
entered, the most recent date is
considered when determining the average Purchase order Subcontracting purchase order items for
times. items with partial which either no further goods receipt
invoice receipt is expected and the delivered quantity is
greater than the invoiced quantity, or the
goods receipt doesn't exist and the
ordered quantity is greater than the
invoiced quantity.

Purchase order Subcontracting purchase order items for


items with canceled which the invoice receipt was canceled.
invoice receipt

Purchase requisition item creation to purchase order item


creation
Find out more about the process ow Purchase requisition item creation to purchase order item creation.

General Information

ID in KPI Catalog KPPURCH360

What does this process ow measure? Measures the number of purchase requisition items created in the
reference period in which a purchase order item creation is
expected and shows how many of them reached prede ned stages
of the process and how long on average this progression took.

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -28 to -1 calendar days relative to the
date of data collection

What data records are extracted? All purchase requisitions items that were created in the reference
period. Stock transport requisitions (STR) aren't considered.

What details are extracted? As outlined in the KPI catalog entry for KPPURCH360 on the
Technical tab in the Detail List column.

This is custom documentation. For more information, please visit the SAP Help Portal 99
12/19/2022

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

This is custom documentation. For more information, please visit the SAP Help Portal 100
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Purchase requisition All purchase requisitions items that were Purchase requisition Purchase requisition items that were
items created created in the reference period. items manually created manually as indicated by
Stock transport requisitions (STR) aren't created the creation indicator with the user type
considered. for dialog mode.

Purchase requisition Purchase requisition items created without


items without reference to a material number.
material number

Purchase requisition Purchase requisition items created without


items without info reference to a purchasing info record or a
record or agreement purchase agreement.

Purchase requisition Purchase requisition items that were


items from created by an MRP run or the SAP
MRP/APO Advanced Planning and Optimization
(APO) component.

This stage represents additional Purchase requisition Purchase requisition items that can't be
activities related to the previous stage. items xed changed automatically by the materials
planning and control system.

Purchase requisition Purchase requisition items that can't be


items blocked converted to a purchase order due to a
block indicator.

Purchase requisition Purchase requisition items that are


items deleted already deleted, such as when changes
were made in a scenario with SAP
Advanced Planning and Optimization.

This stage represents additional Purchase requisition Purchase requisition items with the
activities related to the previous stage. items waiting for processing status In release.
approval

Purchase requisition Purchase requisition items with the


items approved processing status Release completed.

Purchase requisition Purchase requisition items with the


items rejected processing status Release completed.

This stage represents additional Open purchase Purchase requisition items for which the
activities related to the previous stage. requisition items desired source of supply isn't yet
with source of assigned.
supply not yet
assigned

Purchase requisition Purchase requisition items with reference


items without to a material number for which master
automatic purchase data doesn't allow purchase orders to be
order ag in material generated automatically when purchase
master requisitions are converted into
purchase orders due to the missing ag for
automatic PO.

Purchase requisition Purchase requisition items for which the


items with zero days planned delivery time in days is zero.
as planned delivery
time

This is custom documentation. For more information, please visit the SAP Help Portal 101
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Purchase requisition Purchase requisition items for which the


items with planned planned delivery time in days differs from
delivery time the planned delivery time speci ed in the
different from relevant material master.
material master

This stage represents additional Open purchase Open purchase requisition items that
activities related to the previous stage. requisition items aren't closed or deleted for which the
partially converted ordered quantity is less than the quantity
in the purchase requisition.

Open purchase Open purchase requisition items that


requisition items aren't closed or deleted where, based on
with delivery date in the comparison of the delivery date and
the past the date of data extraction, the delivery
date lies in the past; only those items are
considered for which the ordered quantity
is less than the quantity in the purchase
requisition.

Purchase order items All purchase requisitions items for which Purchase requisition Purchase requisition items that are
created a purchase order item was also created. items manually converted manually into a purchase order.
converted

Purchase order Purchase requisition items converted into


quantity greater a purchase order where the
than purchase ordered quantity is greater than
requisition quantity requested.

Purchase order Purchase requisition items converted into


quantity less than a purchase order where the
purchase requisition ordered quantity is less than requested
quantity and the purchase requisition isn't
agged as closed.

Quantity increased Purchase requisition items with the


after purchase processing status Release Completed
requisition that have been converted to a purchase
approved order and where the ordered quantity is
greater than the requested quantity.

This stage represents additional Purchase order Purchase requisition items for which the
activities related to the previous stage. created later than corresponding purchase order was
planned initiated later than the speci ed release
date.

Purchase order Purchase requisition items for which the


created earlier than corresponding purchase order
planned was initiated earlier than the speci ed
release date.

This stage represents additional Purchase order Purchase requisition items for which the
activities related to the previous stage. waiting for approval corresponding purchase order has the
processing status In release.

Purchase order Purchase requisition items for which the


approved corresponding purchase order has the
processing status Release completed.

This is custom documentation. For more information, please visit the SAP Help Portal 102
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Purchase order Purchase requisition items for which the


rejected corresponding purchase order has the
processing status Rejected.

Stock transport requisition item creation to stock transport


order item creation
Find out more about the process ow Stock transport requisition item creation to stock transport order item creation.

General Information

ID in KPI Catalog KPPURCH362

What does this process ow measure? Measures the number of stock transport requisition items created
in the reference period for which stock transport order item
creation is expected, and shows how many of them reached
prede ned stages of the process and how long on average this
progression took.

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -28 to -1 calendar days relative to the
date of data collection

What data records are extracted? All stock transport requisition items that were created in the
reference period.

What details are extracted? As outlined in the KPI catalog entry for KPPURCH362 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

This is custom documentation. For more information, please visit the SAP Help Portal 103
12/19/2022

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Stock transport All stock transport requisition items that Stock transport Stock transport requisition items that were
requisition items were created in the reference period. This requisition items created manually by a dialog user
created is based on the date on which the manually created
purchase requisition was created.
Stock transport Stock transport requisition items for which
requisition items a purchasing info record or a purchase
without info record agreement haven't been entered in the
or agreement system

Stock transport Stock transport requisition items that were


requisition items created from material requirements
from MRP/APO planning or SAP Advanced Planning and
Optimization

This is custom documentation. For more information, please visit the SAP Help Portal 104
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

This stage represents additional Stock transport Stock transport requisition items that
activities related to the previous stage. requisition items can't be changed automatically by the
xed materials planning and control system

Stock transport Stock transport requisition items that are


requisition items blocked and can't be converted, for
blocked example, into a purchase order

Stock transport Stock transport requisition items for which


requisition items the deletion indicator is set
deleted

This stage represents additional Stock transport Stock transport requisition items for which
activities related to the previous stage. requisition items the purchase requisition is currently
waiting for approval pending release

Stock transport Stock transport requisition items for which


requisition items the purchase requisition is completely
approved released

Stock transport Stock transport requisition items for which


requisition items release of the purchase requisition has
rejected been rejected

This stage represents additional Open stock Stock transport requisition items that,
activities related to the previous stage. transport based on the Assigned source of supply
requisition items indicator, don't yet have a source of
with source of supply assigned
supply not yet
assigned

Stock transport Stock transport requisition items for which


requisition items a material number hasn't been entered in
without automatic the purchase requisition, and for which the
PO ag in material indicator allowing purchase orders to
master be generated automatically when the
purchase requisition is converted isn't set

Stock transport Stock transport requisition items for which


requisition items the planned delivery time in days is zero.
with zero days as
planned delivery
time

Stock transport Stock transport requisition items for which


requisition items the planned delivery time in days differs
with planned from the planned delivery time speci ed
delivery time in the relevant material master.
different from
material master

This stage represents additional Open stock Open stock transport requisition items for
activities related to the previous stage. transport which the ordered quantity is less than the
requisition items quantity in the purchase requisition, and
partially converted that are not closed or deleted.

This is custom documentation. For more information, please visit the SAP Help Portal 105
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Open stock Open stock transport requisition items


transport where, based on the delivery date and
requisition items the date of data collection, the delivery
with delivery date in date is in the past; only those items are
the past considered where the ordered quantity is
less than the quantity in the purchase
requisition, and that are not closed
or deleted

Stock transport order All stock transport requisition items for Stock transport Open stock transport requisition items for
items created which a subsequent stock transport order requisition items which the automatic PO indicator is set to
was also created. This is based on the manually converted manual
date on which the order was created. Only
those items are considered where, Stock transport Stock transport orders where, based on
according to the purchase requisition, order quantity the values for Purchase requisition
either the ordered quantity is greater than greater than stock quantity and Quantity ordered against
or equal to the requested quantity, or transport this purchase requisition, the quantity
the ordered quantity is greater than zero requisition quantity is greater than in the requisition
and the purchase requisition is closed,
Stock transport Stock transport orders where, based on
which means that no further purchase
order quantity less the values for Purchase requisition
orders are to be created for this
than stock transport quantity and Quantity ordered against
purchase requisition.
requisition quantity this purchase requisition, the quantity is
less than in the requisition; only those
orders are considered that are closed,
which means that no further purchase
orders are to be created for this purchase
requisition

This stage represents additional Stock transport Stock transport orders for which the
activities related to the previous stage. order created later purchase order creation date is later than
than planned the purchase requisition release date

Stock transport Stock transport orders for which the


order created earlier purchase order creation date is earlier
than planned than the purchase requisition release date.

This stage represents additional Stock transport Stock transport orders with the purchasing
activities related to the previous stage. order waiting for document processing state In release
approval

Stock transport Stock transport orders with the purchasing


order approved document processing state Release
completed

Stock transport Stock transport orders with the


order rejected purchasing document processing state
Rejected

Supplier invoice issuing to FI-AP clearing


Find out more about the process ow Supplier invoice issuing to FI-AP clearing.

General Information

This is custom documentation. For more information, please visit the SAP Help Portal 106
12/19/2022
ID in KPI Catalog KPPURCH460

What does this process ow measure? Measures the number of supplier invoices created in reference to a
purchase order in the reference period and shows how many of
them reached prede ned stages of the process and how long on
average this progression took.

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -77 to -35 calendar days relative to the
date of data collection

What data records are extracted? All supplier invoices at document item level that were created in
the reference period that are marked as posted (the post invoice
indicator is set to Yes) and are considered logistics invoices based
on the internal document type. The document date is determined
by the date on which the original document was issued.

What details are extracted? As outlined in the KPI catalog entry for KPPURCH460 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

Process Flow Stages, Blockers, and Other Information

 Remember

This is custom documentation. For more information, please visit the SAP Help Portal 107
12/19/2022
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Supplier invoices All supplier invoices at document item Supplier invoices Supplier invoices for which the creation
issued level that were created in the reference issued before date of the invoice is before the creation
period that are marked as posted (the purchase order date of the purchase order.
post invoice indicator is set to Yes) and
are considered logistics invoices based Supplier invoices Supplier invoices for which a reverse
on the internal document type. The reversed document number exists.
document date is determined by the date
Supplier invoices Supplier invoices that have been deleted
on which the original document was
deleted as indicated by the invoice document
issued.
status.

Supplier invoices Supplier invoices created by a user that's


created by dialog maintained as a dialog user in the system.
user
Dialog users are users created for human
users who interact with a system. Supplier
invoices created by dialog users are
therefore typically created manually.
However, it's also possible that some
invoices are created automatically through
interface calls and the dialog user is
recorded as the user who created these
invoices.

This stage represents additional Supplier invoices Supplier invoices created for which the
activities related to the previous stage. created via BAPI origin of the invoice in Logistics Invoice
interface Veri cation is set to BAPI Invoice.

Supplier invoices Supplier invoices created for which the


created via EDI/IDoc origin of the invoice in Logistics Invoice
Veri cation is set to EDI.

Supplier invoices Supplier invoices created for which the


created using origin of the invoice in Logistics Invoice
evaluated receipt Veri cation is set to ERS.
settlement

Supplier invoices All supplier invoices that are related to an


created for internal invoicing party that is an internal trading
trading partners partner.

ST-A/PI 01V_731*

This is custom documentation. For more information, please visit the SAP Help Portal 108
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Supplier invoices All supplier invoices for which the Supplier invoices Supplier invoices for which the entry date
created and posted subsequent accounting document has created after posting of the invoice is after the date used to
also been created and that have the date enter the document in Financial Accounting
status indicating posted. This is based or Controlling.
on the date on which the invoice
document was entered in the system. Supplier invoices Supplier invoices for which the invoice
currently parked status is either Parked, Parked complete,
Held parked, Held entered, or Parked
released.

Supplier invoices Supplier invoices for which the invoice is


previously parked created from parking functions.

FI-AP items released All supplier invoices for which the FI-AP items Supplier invoices for which the
for payment accounting document has also been currently blocked subsequent FI-AP items have been
created, where this is not or no longer for payment created and a payment block key is
blocked for payment, and for which a entered in the system.
reverse document hasn't been created. If
the document was never blocked, the FI-AP items Supplier invoices for which the
creation date is based on the entry date previously blocked subsequent FI-AP items have been
of the document. If a document was for payment created and the Previously blocked
blocked for payment, the creation date is indicator is set in the system.
based on the last release date.
Supplier invoices Supplier invoices that are blocked for
blocked for payment payment in invoice veri cation, which is
in invoice indicated when the Blocked indicator is
veri cation set in the system.

Supplier invoices Supplier invoices that are blocked for


blocked for payment payment in invoice veri cation, which is
in invoice indicated when the Blocked indicator is
veri cation but set in the system, but that are released in
released in FI-AP FI-AP.

Supplier invoices Supplier invoices for which the indicator


with manual for previously blocked is set in the system
payment blocks set that were released by a transaction code
in FI-AP that indicates manual transaction use in
FI-AP.

FI-AP clearing All supplier invoices for which the Open FI-AP items Supplier invoices for which the FI-AP item
documents created subsequent FI-AP clearing document has with net due date in is still open, so hasn't been canceled or
also been created (based on the clearing the past cleared, and where the net due date is
date) and that haven´t been reversed already in the past.
(based on the reverse document).
Open FI-AP items Supplier invoices for which the FI-AP item
with possible is still open (that is, not canceled or
discount cleared yet) and where the cash discount
percentage 1 is not zero.
ST-A/PI 01V_731*

Supplier invoices Supplier invoices that have been canceled


reversed and FI-AP in Logistics Invoice Veri cation but for
items not cleared which the corresponding clearing in
Finance is not processed yet.

This is custom documentation. For more information, please visit the SAP Help Portal 109
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

FI-AP items cleared All supplier invoices for which the FI-AP items not Supplier invoices for which FI-AP items
subsequent FI-AP item has also been cleared via payment have been created but for which the
cleared (based on the clearing date) and run payment run wasn't created using
that haven´t been reversed (a reverse transaction F110 (Automatic Payment
document doesn't exist). Transactions) or another transaction was
used.

FI-AP items cleared Supplier invoices for which the FI-AP item
more than 3 days was cleared 3 days or more before the
before net due date calculated net due date and no discount
and no discount was deducted, which means a weekend in
between isn't the sole reason for the early
payment.

Payment terms Supplier invoices for which FI-AP items


different in FI-AP have been created, but the payment terms
and purchase order in the FI-AP items differ from the payment
terms in the related purchase order;
supplier invoices that have been reversed
aren't considered.

FI-AP items cleared Supplier invoices that were cleared using


with account account maintenance transaction FB1K
maintenance (Clear Vendor).
transaction FB1K

This stage represents additional FI-AP items cleared Supplier invoices for which the date of the
activities related to the previous stage. after clearing date accounting document in the system is
after the clearing date of the FI-AP item.

FI-AP items cleared Supplier invoices for which the FI-AP item
after net due date was cleared after the calculated net due
date.

Supplier invoice Supplier invoices for which a reversal


reversed and FI-AP document number is entered in the
items paid system and the FI-AP item was created
using the automatic payment program.

FI-AP items cleared Supplier invoices for which the FI-AP item
despite payment was cleared despite a payment block.
block

This stage represents additional FI-AP items cleared Supplier invoices for which the FI-AP item
activities related to the previous stage. with discount lost was cleared and a offered discount was
not applied.
ST-A/PI 01V_731*

FI-AP items cleared Supplier invoices for which the FI-AP item
with discount was cleared and an offered discount was
applied applied.

ST-A/PI 01V_731*

FI-AP items cleared Supplier invoices for which the FI-AP item
with discount was cleared and an offered discount was
applied but late applied although the clearing date is later
payment than the net due date.

ST-A/PI 01V_731*

This is custom documentation. For more information, please visit the SAP Help Portal 110
12/19/2022
* This data is only available as of ST-A/PI 01V_731. Upgrading to the latest version is always recommended. Also ensure you
implement the latest version of the relevant SAP Note for your ST-A/PI version as outlined under Technical Prerequisites in the
Administration Guide .

Stock transport order item creation (without delivery) to GR


Find out more about the process ow Stock transport order item creation (without delivery) to GR.

General Information

ID in KPI Catalog KPPURCH560

What does this process ow measure? Measures the number of intracompany stock transport order items
created in the reference period where a replenishment delivery isn't
expected and shows how many of them reached prede ned stages
of the process and how long on average this progression took

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -42 to -14 calendar days relative to the
date of data collection

What data records are extracted? All stock transport order items with the document category for
purchase order where no delivery is expected that were created in
the reference period.

What details are extracted? As outlined in the KPI catalog entry for KPPURCH560 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

This is custom documentation. For more information, please visit the SAP Help Portal 111
12/19/2022

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Stock transport order All stock transport order items with the Stock transport Stock transport items for which the
items created document category for purchase order order items not committed quantity within the same
where no delivery is expected that were committed schedule line is blank
created in the reference period.
Stock transport Stock transport order schedule lines for
order items without which a purchase requisition number
stock transport hasn't been entered
requisition
reference

Stock transport order All stock transport order items that were Overdue stock Stock transport order items that were
items issued created and also subsequently issued. transport order created but for which a goods issue hasn't
This is based on the date on which the items created but yet been posted although the planned
goods issue was entered. not issued delivery date is already in the past

This is custom documentation. For more information, please visit the SAP Help Portal 112
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Stock transport order All stock transport order items that were Stock transport Stock transport order items for which the
items received created and also subsequently received. order items with goods receipt document was created after
This is based on the date on which the goods receipt the planned delivery date
goods receipt was entered. created later than
planned

Overdue stock Stock transport order items that were


transport order issued in the supplying plant but for which
items issued but not a goods receipt hasn't yet been posted in
received the receiving plant although the planned
delivery date is already in the past; the
goods are considered to be in transit

Received stock Stock transport order schedule lines for


transport order which the Delivery completed indicator
items without isn't set but a goods receipt date has been
"Delivery entered
completed" set

Stock transport order item creation (with delivery) to GR


Find out more about the process ow Stock transport order item creation (with delivery) to GR.

General Information

ID in KPI Catalog KPPURCH561

What does this process ow measure? Measures the number of intracompany stock transport order items
created in the reference period where a replenishment delivery is
expected and shows how many of them reached prede ned stages
of the process and how long on average this progression took.

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -42 to -14 calendar days relative to the
date of data collection

What data records are extracted? All stock transport order items with the document category for
purchase order where a replenishment delivery is expected that
were created in the reference period.

What details are extracted? As outlined in the KPI catalog entry for KPPURCH561 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

This is custom documentation. For more information, please visit the SAP Help Portal 113
12/19/2022

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Stock transport items All intracompany stock transport order Stock transport Stock transport items where the
created items that were created in the reference order items not committed quantity, which speci es
period that are identi ed by a supplying committed what's available and can be delivered by
(or issuing) plant allocated to the order the con rmed date, isn't yet entered in the
that supplies the ordered material and system.
that expect a replenishment delivery
created as part of the process. This is

This is custom documentation. For more information, please visit the SAP Help Portal 114
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

determined based on the order date of


Stock transport Stock transport order items that don't
the stock transport order schedule line.
order items without have a reference to a purchase requisition
stock transport number.
requisition
reference

Stock transport order All intracompany stock transport order Overdue stock Stock transport order items that were
items delivered items that also either have a delivered transport order created but for which replenishment hasn't
quantity that is equal to or greater than items created but yet been fully delivered although the
the order quantity or have a smaller not (fully) delivered planned delivery date is already in the
quantity delivered and for which the Final past.
delivery indicator is set. This is
determined based on the date on which Stock transport Stock transport order items where the
the material document was entered for order items with quantity in the replenishment delivery is
the goods movement. overdelivery greater than the ordered quantity.

Partially delivered Stock transport order items that have


stock transport been partially delivered but for which the
order items without Final delivery indicator isn't set, which
"Final delivery" set indicates that further outbound deliveries
are to be generated for the item.

Stock transport order All intracompany stock transport order Overdue stock Stock transport order items with a
items issued items that also have an issued quantity transport order replenishment delivery for which a goods
that is equal to or greater than the order items delivered but issue hasn't yet been fully posted although
quantity. This is determined by the date not (fully) issued the planned delivery date is already in the
on which the material document was past.
entered for the goods issue.

Stock transport order All intracompany stock transport order Stock transport Stock transport order items for which the
items received items that also have a received quantity order items with goods receipt document was created after
that is equal to or greater than the order goods receipt the planned delivery date.
quantity. This is determined by the date created later than
on which the material document was planned
entered for the goods receipt.
Overdue stock Stock transport order items that were
transport order issued in the supplying plant but for which
items issued but not a full goods receipt hasn't yet been posted
(fully) received in the receiving plant although the planned
delivery date is already in the past. The
goods are considered to be in transit.

Received stock Stock transport order items that have


transport order been delivered based on the entry date of
items without the goods receipt but for which the
"Delivery Delivery completed indicator isn't set,
completed" set which indicates that the item is to be
regarded as closed, but the goods receipt
has already been posted.

Partially delivered Stock transport order items that have


stock transport been partially delivered based on the
order items with entry date for the goods receipt, and for
"Final delivery" set which the Final delivery indicator is set
but "Delivery but the Delivery completed indicator isn’t
completed" not set set.

This is custom documentation. For more information, please visit the SAP Help Portal 115
12/19/2022

Intercompany stock transport order item creation to FI-AR


clearing
Find out more about the process ow Intercompany stock transport order item creation to FI-AR clearing.

General Information

ID in KPI Catalog KPPURCH562

What does this process ow measure? Measures the number of intercompany stock transport order items,
created in the reference period, where a replenishment delivery is
expected as part of the process. It shows how many of them
reached prede ned stages of the process and how long on average
this progression took.

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -70 to -28 calendar days relative to the
date of data collection

What data records are extracted? All intercompany stock transport order items with the purchasing
category for purchase orders that are identi ed by a supplying (or
issuing) plant allocated to the order that supplies the ordered
material and where the purchasing document date as well as the
order date of the schedule lines were created in the reference
period. Also taken into account is that the stock transport order
items have the item category for standard items.

What details are extracted? As outlined in the KPI catalog entry for KPPURCH562 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

This is custom documentation. For more information, please visit the SAP Help Portal 116
12/19/2022

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Stock transport order All intercompany stock transport order Stock transport Stock transport order items that weren't
items created items that were created in the reference order items not committed within the same schedule line.
period. This is determined based on the committed
order date of the stock transport order
schedule line. Stock transport Stock transport order items that don't
order items without have a reference to a purchase requisition
stock transport number.
requisition
reference

This is custom documentation. For more information, please visit the SAP Help Portal 117
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Stock transport order All intercompany stock transport order Overdue stock Stock transport order items that were
items delivered items that also either have a delivered transport order created but for which replenishment hasn't
quantity that is equal to or greater than items created but yet been fully delivered although the
the ordered quantity or have a smaller (fully) not delivered planned delivery date is already in the
quantity delivered and for which the Final past.
delivery indicator is set. This is
determined based on the date on which Stock transport Stock transport order items where the
the material document was entered for order items with quantity in the replenishment delivery is
the goods movement (delivery). overdelivery greater than the ordered quantity.

Partially delivered Stock transport order items that have


stock transport been partially delivered but for which the
order items without Final delivery indicator isn't set, which
"Final delivery" set indicates that further outbound deliveries
are to be generated for the item.

Stock transport order All intercompany stock transport order Intercompany billing Stock transport order schedule lines for
items issued items that also have an issued quantity document created which a corresponding intercompany
that is equal to or greater than the order billing document has been created, which
quantity. This is determined by the date is indicated by the date on which the
on which the material document was record was created.
entered for the goods issue.
Overdue stock Stock transport order items with a
transport order replenishment delivery for which a goods
items delivered but issue hasn't yet been fully posted although
not (fully) issued the planned delivery date is already in the
past.

Stock transport order All intercompany stock transport order Supplier invoice Stock transport order schedule lines for
items received items that also have a received quantity received which a corresponding supplier invoice
that is equals to or greater than the order document has been received, which is
quantity. This is determined by the date indicated by the date on which the
on which the material document was accounting document was entered.
entered at goods receipt.
Stock transport Stock transport order items for which the
order items with goods receipt document was created after
goods receipt the planned delivery date.
created later than
planned

Overdue stock Stock transport order items that were


transport order issued in the supplying plant but for which
items issued but not a full goods receipt hasn't yet been posted
(fully) received in the receiving plant although the planned
delivery date is already in the past. The
goods are considered to be in transit.

Received stock Stock transport order items that were


transport order received, such that a goods receipt date is
items without entered in the system, but for which the
"Delivery Delivery completed indicator isn't set,
completed" set which indicates that the item is to be
considered closed, but the quantity of
goods received is assigned at schedule
line level.

This is custom documentation. For more information, please visit the SAP Help Portal 118
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Partially delivered Stock transport order items that have


stock transport been partially delivered based on the
order items with entry date for the goods receipt, and for
"Final delivery" set which the Final delivery indicator is set
but "Delivery but the Delivery completed indicator isn’t
completed" not set set.

FI-AR items created All stock transport order items where the – None – – None –
intercompany billing document led to an
FI-AR item in the supplying company
code.

FI-AP items created All stock transport order items where the – None – – None –
FI-AR item in the supplying company
code led to a corresponding FI-AP item in
the receiving company code.

FI-AP items cleared All intercompany stock transport order – None – – None –
items for which the corresponding FI-AP
items are also considered cleared or
paid. This is determined by the clearing
date of the payment document with which
the supplier invoice posting was cleared.

FI-AR items cleared All intercompany stock transport order – None – – None –
items for which the corresponding FI-AR
items are also considered cleared or
paid. This is determined by the clearing
date of the payment document with which
the customer invoice posting from
intercompany billing was cleared.

Scheduling agreement item creation to end of validity


Find out more about the process ow Scheduling agreement item creation to end of validity.

General Information

ID in KPI Catalog KPPURCH660

What does this process ow measure? Measures the number of scheduling agreement items created in the
reference period and shows details of the stipulated validity period
of these outline agreements

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -550 to -1 calendar days relative to the
date of data collection

What data records are extracted? All scheduling agreements that were created in the reference
period, except for stock transport scheduling agreements

What details are extracted? As outlined in the KPI catalog entry for KPPURCH660 on the
Technical tab in the Detail List column.

This is custom documentation. For more information, please visit the SAP Help Portal 119
12/19/2022

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

This is custom documentation. For more information, please visit the SAP Help Portal 120
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Scheduling All scheduling agreements that were Scheduling Scheduling agreement items created later
agreement items created in the reference period, except agreement items then the scheduling agreement.
created for stock transport scheduling created after
agreements. agreement creation

Scheduling Scheduling agreement items created


agreement items without an assigned purchasing info
created without info record.
record

Scheduling Scheduling agreement items created


agreement items where release documentation isn't logged.
without active
release
documentation

Scheduling Scheduling agreement items created


agreement items where the Evaluated receipt settlement
created with ERS (ERS) indicator is set.
indicator

This stage represents additional Scheduling Scheduling agreement items for which a
activities related to the previous stage. agreement items deletion indicator is set.
deleted

Scheduling Scheduling agreement items for which a


agreement items blocking indicator is set.
blocked

Scheduling Scheduling agreement items for which a


agreement items delivery is no longer expected.
with "Delivery
completed" set

This stage represents additional Scheduling Scheduling agreement items with the
activities related to the previous stage. agreement items approval processing status In release.
waiting for approval

Scheduling Scheduling agreement items with the


agreement items approval processing status Release
approved completed.

Scheduling Scheduling agreement items with the


agreement items approval processing status Rejected.
rejected

Validity start of All scheduling agreement items where the Scheduling Scheduling agreement items for which the
scheduling scheduling agreement also has a validity agreement items respective material has no source list
agreements start date. without source list entry in their validity period.
entry

Scheduling Scheduling agreement items for which the


agreement items respective material has a source list entry
without MRP- in their validity period but not with the
relevant source list correct value 2, which means the material
entry requirements planning (MRP)
doesn't create a delivery schedule line
with respect to a requirement.

This is custom documentation. For more information, please visit the SAP Help Portal 121
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

This stage represents additional Open scheduling Scheduling agreement items with a
activities related to the previous stage. agreement items validity end date in the future that aren't
without schedule blocked or deleted and for which schedule
lines lines haven't yet been created.

Scheduling Scheduling agreement items for which


agreement items corresponding open commitment items
with open exist.
commitment items

This stage represents additional Open scheduling Scheduling agreement items with a
activities related to the previous stage. agreement items validity end date in the future that aren't
without blocked or deleted and that haven't yet
transmission been transmitted to the supplier.

Open scheduling Scheduling agreement items with a


agreement items validity end date in the future that aren't
with last blocked or deleted and that were
transmission over 1 transmitted to the supplier more that 365
year ago days before the date on which the data
shown was collected.

Validity end of All scheduling agreement items where the Scheduling Scheduling agreement items for which the
scheduling scheduling agreement also has a validity agreement items target quantity is equal to the ordered
agreements in the end date that lies in the past. with full quantity in quantity.
past schedule lines

Scheduling Scheduling agreement items for which the


agreement items target quantity is less than the ordered
with overdelivery quantity.

Scheduling Scheduling agreement items without


agreement items schedule lines for which the validity end
without schedule date is in the past.
lines and validity
end date in the past

Purchase quantity contract item creation to end of validity


Find out more about the process ow Purchase quantity contract item creation to end of validity.

General Information

ID in KPI Catalog KPPURCH661

What does this process ow measure? Measures the number of purchase quantity contract items created
in the reference period and shows how many of them reached
prede ned stages of the process and how long on average this
progression took

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -550 to -1 calendar days relative to the
date of data collection

What data records are extracted? All purchase quantity contract items created in the reference

This is custom documentation. For more information, please visit the SAP Help Portal 122
12/19/2022
period, without considering stock transport orders

What details are extracted? As outlined in the KPI catalog entry for KPPURCH661 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

This is custom documentation. For more information, please visit the SAP Help Portal 123
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Quantity contract All purchase quantity contract items Quantity contract Quantity contract items that were created
items created created in the reference period. The items created after later than the contract.
stock transport orders aren't considered. contract creation

Quantity contract Quantity contract items that were created


items created without an assigned purchasing info
without info record record.

This stage represents additional Quantity contract Quantity contract items that were created
activities related to the previous stage. items for one for a dedicated combination of material
material and plant and plant.

Quantity contract Quantity contract items that were created


items for one for a combination of one material and all
material and all plants.
plants

Quantity contract Quantity contract items that were created


items for material for a combination of material group and
group and one plant one plant.

Quantity contract Quantity contract items that were created


items for material for a combination of material group and all
group and all plants plants.

This stage represents additional Quantity contract Quantity contract items for which a
activities related to the previous stage. items deleted deletion indicator is set.

Quantity contract Quantity contract items for which a


items blocked blocking indicator is set.

Validity start of All purchase quantity contracts items Quantity contract Quantity contract items that have the
quantity contracts where the quantity contract also has items waiting for approval processing status In release.
a validity start date. approval

Quantity contract Quantity contract items that have the


items approved approval processing status Release
completed.

Quantity contract Quantity contract items that have the


items rejected approval processing status Rejected.

First release order All purchase quantity contract items for Open quantity Quantity contract items with a validity end
created for contract which an initial release order has contract items date in the future that aren't blocked or
items also been created. without release deleted and for which a release order
order hasn't yet been issued.

Open quantity Quantity contract items with a validity end


contract items with date in the future that aren't blocked or
last release order deleted and for which the last release
over 1 year ago order was issued more than a year ago.

Validity end of All purchase quantity contracts items Quantity contract Quantity contract items for which the
quantity contracts in where the quantity contract also has items with full release order quantity is equal to
the past a validity end date that lies in the past. quantity released or greater than the quantity of the contract
item.

This is custom documentation. For more information, please visit the SAP Help Portal 124
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Quantity contract Quantity contract items for which a release


items without order hasn't yet been issued and the
release order and validity end date is in the past.
validity end in the
past

Purchase value contract item creation to end of validity


Find out more about the process ow Purchase value contract item creation to end of validity.

General Information

ID in KPI Catalog KPPURCH662

What does this process ow measure? Measures the number of purchase value contract items created in
the reference period and shows how many of them reached
prede ned stages of the process and how long on average this
progression took

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -550 to -1 calendar days relative to the
date of data collection

What data records are extracted? All purchase value contract items created in the reference period,
without considering stock transport orders

What details are extracted? As outlined in the KPI catalog entry for KPPURCH662 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

This is custom documentation. For more information, please visit the SAP Help Portal 125
12/19/2022

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Value contract items All purchase value contract items created Value contract items Value contract items that were created
created in the reference period. The created after later then the contract.
stock transport orders aren't considered. contract creation

Value contract items Value contract items that were created


created without info without an assigned purchasing info
record record.

This stage represents additional Value contract items Value contract items that were created for
activities related to the previous stage. for one material and a dedicated combination of material and
plant plant.

Value contract items Value contract items that were created for
for one material and a combination of one material and all
all plants plants.

This is custom documentation. For more information, please visit the SAP Help Portal 126
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Value contract items Value contract items that were created for
for material group a combination of material group and one
and one plant plant.

Value contract items Value contract items that were created for
for material group a combination of material group and all
and all plants plants.

This stage represents additional Value contract items Value contract items for which a deletion
activities related to the previous stage. deleted indicator is set.

Value contract items Value contract items for which a blocking


blocked indicator is set.

Validity start of value All purchase value contracts items where Value contract items Value contract items that have the
contracts the value contract also has a validity start waiting for approval approval processing status In release.
date.
Value contract items Value contract items that have the
approved approval processing status Release
completed.

Value contract items Value contract items that have the


rejected approval processing status Rejected.

First release order All purchase value contract items for Open value contract Value contract items with a validity end
created for contract which an initial release order has also items without date in the future that aren't blocked or
items been created. release order deleted and for which a release order
hasn't yet been issued.

Open value contract Value contract items with a validity end


items with last date in the future that aren't blocked or
release order over 1 deleted and for which the last release
year ago order was issued more than a year ago.

Validity end of value All purchase value contracts items where Value contract items Value contract items for which the
contracts in the past the value contract also has a validity with full value cumulated value of all release orders is
end date that lies in the past. released equal to or greater than the cumulated
planned value of the value contract.

Value contract items Value contract items for which a release


without release order hasn't yet been issued and their
order and validity validity end date is in the past.
end in the past

Sales billing document creation to FI-AR clearing


Find out more about the process ow Sales billing document creation to FI-AR clearing.

General Information

ID in KPI Catalog KPSD000260

What does this process ow measure? Measures the number of sales billing documents created in the
reference period for which a corresponding FI document and
customer payment are expected and shows how many of them

This is custom documentation. For more information, please visit the SAP Help Portal 127
12/19/2022
reached prede ned stages of the process and how long on average
this progression took

How frequently is data collected and what is the reference period Frequency: Weekly
for the data collected?
Reference period: -77 to -35 calendar days relative to the
date of data collection

What data records are extracted? All sales billing documents that were created within the reference
period that are related to invoices, debit memos, and intercompany
invoices that have a status that's relevant for transferring to
accounting

What details are extracted? As outlined in the KPI catalog entry for KPSD000260 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

This is custom documentation. For more information, please visit the SAP Help Portal 128
12/19/2022
Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Sales billing All sales billing documents that were Sales billing Sales billing documents that don't have
documents created created within the reference period that documents manually the indicator that speci es automatic
are related to invoices, debit memos, and created creation
intercompany invoices that have a status
that's relevant for transferring to Sales billing Sales billing documents that were created
accounting documents created for customers that are internal trading
for internal trading partners
partners

Sales billing Sales billing documents that were created


documents from with reference to an outbound delivery or
delivery-related intercompany replenishment delivery
billing

Sales billing Sales billing documents that were created


documents from with reference to a sales document
order-related billing

Sales billing Sales billing documents that were created


documents from with reference to a billing plan
periodic billing

This stage represents additional Sales billing Sales billing documents that have a
activities related to the previous stage. documents canceled cancelation indicator

Sales billing Sales billing documents that have a


documents canceled cancelation indicator and that haven't
and FI-AR item not been cleared by a corresponding clearing
cleared document

Sales billing Sales billing documents for which the


documents not yet status for transferring to accounting
transferred to FI indicates an error in the accounting
interface, a block for forwarding to FI, or
issues with master data consistency or
authorizations, with the result that the
posting or accounting document couldn't
be created

Sales billing Sales billing documents with zero net


documents with value for which the system therefore does
zero net value and not create any accounting document and
no accounting no clearing is expected. The process ow
document ends with the billing document.

This is custom documentation. For more information, please visit the SAP Help Portal 129
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

FI-AR items created All sales billing documents for which a Payment terms Sales billing documents for which the key
corresponding accounting document was different in billing for de ning payments terms is different
also created document and FI-AR from the key applied in the corresponding
accounting documents

FI-AR document FI-AR accounting documents that have a


reversed reverse document number

Sales billing FI-AR accounting documents that were


documents manually created by a transaction code that's
released to FI executed manually, such as VFX3

This stage represents additional Open FI-AR items FI-AR accounting documents that have a
activities related to the previous stage. with dunning block key re ecting the reason for a dunning
block and that don't show a number of
documents with which the line items were
cleared

Open FI-AR items FI-AR documents that have a dunning level


already dunned assigned that speci es how often an item
or account has been dunned

Open and overdue Customer invoices that aren't cleared or


FI-AR items paid and where the net due date is already
in the past

ST-A/PI 01V_731* Customer invoices that aren't cleared or


paid and where the net due date is already
Open and overdue
in the past although the customer was
FI-AR items despite
offered a discount for early payment.
offered discount

FI-AR items cleared All sales billing documents that also have FI-AR items cleared Customer invoices that are cleared or paid
a clearing date in their corresponding after net due date and for which the clearing was posted
accounting document after the net due date

FI-AR items Customer invoices that have a dunning


previously dunned level assigned that speci es how often an
are cleared item or account has been dunned and that
also shows a document number with which
the line items were cleared

FI-AR items cleared Customer invoices that were cleared or


with manual paid with transaction code FBZ1, which is
payment posting used for manual payment postings
transaction

FI-AR items cleared Customer invoices that were cleared or


with account paid with transaction code FB1D, which is
maintenance used for clearing a customer account
transaction

This stage represents additional FI-AR items cleared Customer invoices that were cleared or
activities related to the previous stage. with clearing date in paid for which the clearing date is after the
the future creation date of the clearing document;
this can indicate that a customer payment
is only expected in the future

This is custom documentation. For more information, please visit the SAP Help Portal 130
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

FI-AR items cleared Customer invoices that were cleared or


with clearing date paid for which the clearing date is more
more than 3 days in than 3 days before the creation date of the
the past clearing document; this can indicate that
the customer payment couldn't be
allocated on time

ST-A/PI 01V_731* Customer invoices that were cleared or


paid with a discount applied.
FI-AR items cleared
with discount
applied

ST-A/PI 01V_731* Customer invoices that were cleared or


paid without a discount applied, although
FI-AR items cleared
the customer was offered a discount for
without offered
early payment.
discount

ST-A/PI 01V_731* Customer invoices that were cleared or


paid and the clearing was posted after the
FI-AR items cleared
net due date, but a discount was still
after net due date
applied.
but with discount
applied

* This data is only available as of ST-A/PI 01V_731. Upgrading to the latest version is always recommended. Also ensure you
implement the latest version of the relevant SAP Note for your ST-A/PI version as outlined under Technical Prerequisites in the
Administration Guide .

If you're using an older ST-A/PI version, lead times aren't available when there are additional stages supported by a higher ST-
A/PI version. Similarly, if there are additional boxes for frequent blockers and other information that are speci c to a newer ST-
A/PI version, metrics aren't available in these boxes and they appear to contain 0 business object instances.

Sales order item creation to outbound delivery item creation


Find out more about the process ow Sales order item creation to outbound delivery item creation.

General Information

ID in KPI Catalog KPSD000360

What does this process ow measure? Measures the number of sales order items created in the reference
period where an outbound delivery is expected and shows how
many of them reached prede ned stages of the process and how
long on average this progression took

How frequently is data collected and what is the reference period Frequency: Weekly
for the data collected?
Reference period: -28 to -1 calendar days relative to the
date of data collection

What data records are extracted? All standard sales order items at schedule line level that were

This is custom documentation. For more information, please visit the SAP Help Portal 131
12/19/2022
created in the reference period and have the overall delivery status
Not yet processed, Partially processed, or Completely processed

What details are extracted? As outlined in the KPI catalog entry for KPSD000360 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

This is custom documentation. For more information, please visit the SAP Help Portal 132
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Sales order items All standard sales order items at Sales order items Sales order items that have a reason for
created schedule line level that were created in rejected rejection assigned to the item data in the
the reference period and have the overall sales document
delivery status Not yet processed,
Partially processed, or Completely Sales order items Sales order items that have a document
processed. with reference to reference to a sales contract item
contract

Sales order items Sales order items that have a document


with reference to reference to a sales quotation item
quotation

Sales order items Sales order items that have a document


with reference to reference to another sales order item
order

This stage represents additional Sales order items Sales order items that have the
activities related to the previous stage. not con rmed con rmation status Not yet processed

Sales order items Sales order items that have the overall
partially delivered delivery status Partially processed

Open sales order Sales order items that have the overall
items with planned delivery status Not yet processed (are not
material availability yet fully delivered) and where the planned
date in the past material availability date lies in the past

This stage represents additional Undelivered items Sales order items that have an overall
activities related to the previous stage. with credit block delivery status Not yet processed or
Partially processed (are not yet fully
delivered), as well as an overall header
credit check status assigned to the sales
order that indicate Credit check was
executed, document not OK, or Credit
check was executed, document not OK,
partial release

Items released by Sales order items that have the overall


credit representative credit check status Document released
by credit representative assigned at
sales document header level

Items with Sales order items that have the overall


successful credit credit check status Credit check was
check executed, document OK assigned at
sales document header level

This stage represents additional Undelivered items Sales order items that have the overall
activities related to the previous stage. with header delivery status Not yet processed or
incomplete Partially processed (are not yet fully
delivered) as well as the incompletion
status Not yet processed assigned to the
delivery-related header information of the
corresponding sales document

This is custom documentation. For more information, please visit the SAP Help Portal 133
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Sales order items Sales order items that have the overall
incomplete for delivery status Not yet processed or
delivery Partially processed (are not yet fully
delivered) as well as the incompletion
status Not yet processed, in relation to
the delivery

This stage represents additional Undelivered items Sales order items that have the overall
activities related to the previous stage. with header blocked delivery status Not yet processed or
for delivery Partially processed (are not yet fully
delivered) as well as the overall delivery
block status Partially processed or
Completely processed assigned at
header level

Sales order items Sales order items that have the overall
blocked for delivery delivery status Not yet processed or
Partially processed (are not yet fully
delivered) as well as an item delivery
block status Partially processed or
Completely processed assigned

Items where header Sales order items where the corresponding


was previously order header had a billing block reason
blocked for delivery that has since been removed

 Note
This information requires change logs
to be available that might already have
been deleted in the system

Sales order items Sales order items where at least one


previously blocked corresponding schedule line had a delivery
for delivery block reason that was since removed

 Note
This information requires change logs
to be available that might already have
been deleted in the system

Delivery items All sales order items for which a Delivery items Delivery documents that were created by
created subsequent delivery document was also manually created a user in dialog mode or with a transaction
created. This is determined based on the code speci cally for dialog mode
date on which a delivery document was
entered. If more than one delivery was Delivery created Delivery documents where the date on
entered for the sales order items, the after planned which the delivery items were created is
most recent delivery document date is material availability later than the date on which sufficient
considered when determining the average date quantities of the items are available so
times relating to progression. that picking can begin

Sales order item creation to sales invoice item creation


Find out more about the process ow Sales order item creation to sales invoice item creation.
This is custom documentation. For more information, please visit the SAP Help Portal 134
12/19/2022

General Information

ID in KPI Catalog KPSD000361

What does this process ow measure? Measures the number of sales order items created in the reference
period where an outbound delivery and a corresponding delivery-
related invoice are expected and shows how many of them reached
prede ned stages of the process and how long on average this
progression took

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -35 to -7 calendar days relative to the
date of data collection

What data records are extracted? All standard sales order items at schedule line level that were
created in the reference period that are relevant for delivery-related
billing and have the overall delivery status Not yet processed,
Partially processed, or Completely processed

What details are extracted? As outlined in the KPI catalog entry for KPSD000361 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances

This is custom documentation. For more information, please visit the SAP Help Portal 135
12/19/2022
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Sales order items All standard sales order items at Sales order items Sales order items that have a reason for
created schedule line level that were created in rejected rejection assigned to the item data in the
the reference period that are relevant for sales document
delivery-related billing and have the
overall delivery status Not yet
Sales order items Sales order items that have the
processed, Partially processed, or
not con rmed con rmation status Not yet processed
Completely processed

Delivery items All sales order items for which a Delivery created Delivery documents where the date on
created subsequent delivery document was also after planned which the delivery items were created is
created. This is determined based on the material availability later than the date on which sufficient
date on which a delivery document was quantities of the items are available so
entered. If more than one delivery was that picking can begin
entered for the sales order items, the
most recent delivery document date is Sales order items Sales order items that have delivery block
considered when determining the average blocked for delivery status Partially processed or Completely
times relating to progression. processed and are not completely
delivered

Sales order items Sales order items that have the


incomplete for incompletion status Not yet processed for
delivery the delivery and are not completely
delivered

Goods issue posted All sales order items for which the Sales order items Sales order items that have the
subsequent delivery documents also incomplete for incompletion status Not yet processed for
have a goods issue posting. This is goods movement the goods issue
determined based on the actual goods
movement date. If more than one goods Goods issue posted Sales order items where the actual goods
movement was entered, the most recent after planned goods movement date is later than the date on
date is considered when determining the issue date which the goods must physically leave the
average times relating to progression. shipping point to reach the customer on
time

Customer invoice All sales order items that also have Sales order items Sales order items with the billing block
items created subsequent customer invoice items blocked for billing status Completely processed
created. This is determined based on the
date on which the invoice was entered. If Sales order items Sales order items with the incompletion
more than one invoice was created for the incomplete for status Not yet processed for billing-
sales order items, the most recent billing related information
customer invoice creation date is
Unbilled sales order Sales order items where a goods issue
considered when determining the average
items with planned took place but where the corresponding
times relating to progression.
billing date in the billing document has not yet been created
past and the planned billing date is in the past

This is custom documentation. For more information, please visit the SAP Help Portal 136
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

This stage represents additional Invoice posted after Sales order items where the date on which
activities related to the previous stage. planned billing date the subsequent invoice document was
created is later than the date on which the
billing is planned for accounting purposes

Sales order items Sales order items where the corresponding


where header was order header had a billing block reason
previously blocked that has since been removed
for billing
 Note
This information requires change logs
to be available that might already have
been deleted in the system

Sales order items Sales order items that had a billing block
previously blocked reason that was since removed
for billing
 Note
This information requires change logs
to be available that might already have
been deleted in the system

Sales order item creation to FI-AR item clearing


Find out more about the process ow Sales order item creation to FI-AR item clearing.

General Information

ID in KPI Catalog KPSD000362

What does this process ow measure? Measures the number of sales order items created in the reference
period where an outbound delivery, a corresponding delivery-
related invoice, a corresponding FI document, and a customer
payment are expected and shows how many of them reached
prede ned stages of the process and how long on average this
progression took

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -63 to -35 calendar days relative to the
date of data collection

What data records are extracted? All standard sales order items at schedule line level that were
created in the reference period that are relevant for delivery-related
billing and have the overall delivery status Not yet processed,
Partially processed, or Completely processed

What details are extracted? As outlined in the KPI catalog entry for KPSD000362 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

This is custom documentation. For more information, please visit the SAP Help Portal 137
12/19/2022

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Sales order items All standard sales order items at Sales order items Sales order items that have the
created schedule line level that were created in not con rmed con rmation status Not yet processed
the reference period that are relevant for
delivery-related billing and have the
overall delivery status Not yet
processed, Partially processed, or
Completely processed
This is custom documentation. For more information, please visit the SAP Help Portal 138
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Sales order items Sales order items that have a reason for
rejected rejection assigned to the item data in the
sales document

Delivery items All sales order items for which a Sales order items Sales order items that have delivery block
created subsequent delivery document was also blocked for delivery status Partially processed or Completely
created. This is determined based on the processed and are not completely
date on which a delivery document was delivered
entered. If more than one delivery was
entered for the sales order items, the Sales order items Sales order items that have the
most recent delivery document date is incomplete for incompletion status Not yet processed for
considered when determining the average delivery the delivery and are not completely
times relating to progression. delivered

Delivery created Sales order items that were delivered and


after planned where the delivery document was created
material availability after the planned material availability date
date

Goods issue posted All sales order items for which the Sales order items Sales order items that have the
subsequent delivery documents also incomplete for incompletion status Not yet processed for
have a goods issue posting. This is goods movement the goods issue
determined based on the actual goods
movement date. If more than one goods Goods issue posted Sales order items where the actual goods
movement was entered, the most recent after planned goods movement date is later than the date on
date is considered when determining the issue date which the goods must physically leave the
average times relating to progression. shipping point to reach the customer on
time

Customer invoice All sales order items that also have Sales order items Sales order items with the billing block
items created subsequent customer invoice items blocked for billing status Completely processed
created. This is determined based on the
date on which the invoice was entered. If Sales order items Sales order items with the incompletion
more than one invoice was created for the incomplete for status Not yet processed for billing-
sales order items, the most recent billing related information
customer invoice creation date is
Invoice posted after Sales order items where the date on which
considered when determining the average
planned billing date the subsequent invoice document was
times relating to progression.
created is later than the date on which the
billing is planned for accounting purposes

FI-AR items created All sales order items for which the – None – – None –
subsequent customer invoice also has an
FI document posting. This is determined
based on the date on which the FI
document was created.

FI-AR items cleared All sales order items for which the – None – – None –
subsequent customer invoice was also
cleared. This is determined based on the
date on which the corresponding FI
document was cleared.

Third-party sales order item creation to sales invoice item


creation

This is custom documentation. For more information, please visit the SAP Help Portal 139
12/19/2022
Find out more about the process ow Third-party sales order item creation to sales invoice item creation.

General Information

ID in KPI Catalog KPSD000363

What does this process ow measure? Measures the number of sales order items created in the reference
period that are relevant for third-party delivery and shows how
many of them reached prede ned stages of the process and how
long on average this progression took

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -49 to -7 calendar days relative to the
date of data collection

What data records are extracted? All sales orders items created in the reference period that are
standard items relevant for delivery and are purchasing document
types marked as relevant for third-party delivery. An item is
considered as relevant for third-party delivery when its status is
Relevant for order-related billing, which is based on the invoice
receipt quantity.

What details are extracted? As outlined in the KPI catalog entry for KPSD000363 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

Process Flow Stages, Blockers, and Other Information


This is custom documentation. For more information, please visit the SAP Help Portal 140
12/19/2022

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Sales order items All sales orders items created in the Sales order items Sales order items for which a rejection
created reference period that are standard items rejected reason has been entered.
relevant for delivery and are purchasing
document types marked as relevant for Sales order items Sales order items where the Generally
third-party delivery. An item is incomplete incomplete status is Not yet processed.
considered as relevant for third-party Incompleteness means that not all item
delivery when its status is Relevant for information necessary for further
order-related billing, which is based on processing has been provided.
the invoice receipt quantity.
Sales order items Sales order items where a customer
with billing invoice can only be created based on the
according to quantity of a corresponding supplier
supplier invoice invoice.
quantity

Sales order items Sales order items where a customer


with billing invoice can be created based on the order
according to order quantity in the sales order item.
quantity

Purchase requisition All sales order items for which a Purchase requisition Sales order items where the purchase
items created subsequent purchase requisition has also items created later requisition wasn't created automatically
been created. This is determined based than sales order upon saving because the creation date of
on the date on which the purchase items the purchase requisition was at least one
requisition was created. day later than that of the sales order
items.

 Note
A belated purchase requisition might
be because of an incomplete sales
order item or a failed credit check.

This is custom documentation. For more information, please visit the SAP Help Portal 141
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Purchase order items All sales order items for which a Purchase order Sales order items where the corresponding
created subsequent purchase order has also been items deleted third-party purchase order item is marked
created. This is determined based on the for deletion, which is a prerequisite for
date on which the purchase order was rejecting the corresponding sales order
created. If more than one purchase order item.
was created for the sales order item, the
purchase order with the highest
referenced quantity per sales order is
considered. If multiple purchase orders
have the same referenced quantity, the
purchase order with the highest number
is considered.

Supplier invoice All sales order items for which a Supplier invoices Sales order items where a supplier invoice
created subsequent supplier invoice has also created but no was created, which typically indicates a
been created. This is based on the customer invoice yet proof of delivery to the end customer, but
invoice receipt document date. If more for which the corresponding customer
than one invoice was created for a sales invoice wasn't yet created.
order, the invoice with the highest number
is considered. If the quantity of the
purchasing document is greater than or
equal to the cumulative con rmed
quantity of the sales document, the full
quantity must have been delivered and
invoiced by the third party.

Customer invoice All sales order items for which a Customer invoice Sales order items where the customer
items created subsequent customer invoice has also items created more invoice is created at least 1 day after the
been created. This is based on the date than a day after corresponding supplier invoice was
on which the invoice was created. Only supplier invoice created.
invoices where the full customer invoice
quantity has been received are
considered.

Sales order item (purchase to order) to sales invoice item


Find out more about the process ow Sales order item (purchase to order) to sales invoice item.

General Information

ID in KPI Catalog KPSD000364

What does this process ow measure? Measures the number of sales order items created in the reference
period where an outbound delivery and a corresponding delivery-
related invoice are expected and a corresponding purchase-to-
order process is required to ful ll the customer demand; and
shows how many of them reached prede ned stages of the process
and how long on average this progression took

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -49 to -7 calendar days relative to the
date of data collection

What data records are extracted? All sales order items that were created within the reference period

This is custom documentation. For more information, please visit the SAP Help Portal 142
12/19/2022
that are relevant for delivery, are purchasing document types, are
de ned as sales-order stock, and for which a purchase requisition
is expected

What details are extracted? As outlined in the KPI catalog entry for KPSD000364 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

This is custom documentation. For more information, please visit the SAP Help Portal 143
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Sales order items All sales order items that were created Sales order items Sales order items for which a rejection
created within the reference period that are rejected reason has been entered.
relevant for delivery, are purchasing
document types, are de ned as sales- Sales order items Sales order items where the Generally
order stock, and for which a purchase incomplete incomplete status is Not yet processed.
requisition is expected. Incompleteness means that not all item
information necessary for further
processing has been provided.

Sales order items Sales order items for which the con rmed
with con rmation delivery date in the schedule line is later
date later than than the initially requested delivery date.
requested delivery
date

Purchase requisition All sales order items for which a Purchase requisition Sales order items for which the purchase
items created subsequent purchase requisition has also items created later requisition wasn't created automatically
been created. This is determined based than sales order upon saving but at a later point in time.
on the date on which the purchase items
requisition was created.  Note
A belated purchase requisition might
be because of an incomplete sales
order item or a failed credit check.

Purchase order items All sales order items for which a Open purchase Sales order items where the con rmed
created subsequent purchase order has also been order items with delivery date is already in the past but a
created. This is determined based on the con rmed delivery goods receipt hasn't yet been posted for
date on which the purchase order was date in sales order the corresponding purchase order item.
created. If more than one purchase order in the past
was created for the sales order item, the
purchase order with the highest
Purchase order Sales order items where the corresponding
referenced quantity per sales order is
items deleted purchase order item is marked for
considered. If multiple purchase orders
deletion, which is a prerequisite for
have the same referenced quantity, the
rejecting the corresponding sales order
purchase order with the highest number
item.
is considered.

Goods receipt posted All sales order items for which a Goods receipt Sales order items where the goods receipt
subsequent goods receipt has also been posted after for the corresponding purchase order item
posted. This is based on the creation con rmed delivery wasn't posted until after the con rmed
date of the goods receipt. Only the latest date in sales order delivery date from the sales order item.
goods receipt for a sales order is
considered. If there's more than one Sales order item Sales order items with unrestricted-use
goods receipt, the one with the highest stock exists stock reserved for the relevant sales order
number is considered. item.

Goods issue posted All sales order items for which a Delivery items Sales order items for which a subsequent
subsequent goods issue has also been created delivery item has been created, based on
posted. the creation date of the delivery item.

Goods issue posted Sales order items where the actual goods
after con rmed issue was posted after the con rmed
delivery date delivery date in the corresponding sales
schedule line.

This is custom documentation. For more information, please visit the SAP Help Portal 144
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Delivery items Sales order items for which a delivery item


created before has been created before the goods
goods receipt receipt, based on the delivery item and
goods receipt creation dates.

Customer invoice All sales order items for which a Supplier invoice Sales order items for which a subsequent
items created subsequent customer invoice has also created supplier invoice has been created, based
been created. This is based on the date on the creation date of the supplier
on which the invoice was created. invoice.

Supplier invoice Sales order items for which a subsequent


created before supplier invoice was created before goods
goods receipt receipt, based on the supplier invoice and
goods receipt creation dates.

Supplier invoice Sales order items for which a supplier


created but no invoice was created for the corresponding
customer invoice yet purchase order item, but for which the
corresponding customer invoice wasn't yet
created.

This stage represents additional Customer invoice Sales order items where the supplier
activities related to the previous stage. created later than invoice was created for the corresponding
supplier invoice purchase order item before a customer
invoice was created.

Sales order item (make to order) to sales invoice item


Find out more about the process ow Sales order item (make to order) to sales invoice item.

General Information

ID in KPI Catalog KPSD000365

What does this process ow measure? Measures the number of sales order items created in the reference
period where an outbound delivery and a corresponding delivery-
related invoice are expected and a corresponding make-to-order or
assembly-to-order process is required to ful ll the customer
demand; and shows how many of them reached prede ned stages
of the process and how long on average this progression took

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -49 to -7 calendar days relative to the
date of data collection

What data records are extracted? All sales orders that were created in the reference period that are
relevant for delivery, are purchasing document types, and are
de ned as sales-order stock. This is based on the creation date of
the document.

What details are extracted? As outlined in the KPI catalog entry for KPSD000365 on the
Technical tab in the Detail List column.

 Note

This is custom documentation. For more information, please visit the SAP Help Portal 145
12/19/2022
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

This is custom documentation. For more information, please visit the SAP Help Portal 146
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Sales order items All sales orders that were created in the Sales order items Sales order items for which a rejection
created reference period that are relevant for rejected reason has been entered.
delivery, are purchasing document types,
and are de ned as sales-order stock. Sales order items Sales order items where the Generally
This is based on the creation date of the incomplete incomplete status is Not yet processed.
document Incompleteness means that not all item
information necessary for further
processing has been provided.

Sales order items Sales order items for which the con rmed
with con rmation delivery date in the schedule line is later
date later than than the initially requested delivery date.
requested delivery
date

Manufacturing orders All sales order items for which a Manufacturing Sales order items for which a planned
created subsequent manufacturing order has also orders not related to order number isn't entered.
been created. This is based on the planned order
creation date of the manufacturing order.

Manufacturing orders All sales order items for which a Unreleased Manufacturing orders that aren't yet
released manufacturing order has also been manufacturing released (and aren't set to technically
subsequently released. This is based on orders with sales complete) for which the con rmed
the actual release date of the order con rmation delivery date in the corresponding sales
manufacturing order. date in the past order item is already in the past.

Manufacturing Manufacturing orders that were actually


orders released released before the scheduled released
early date.

Manufacturing Manufacturing orders that were actually


orders released late released after the scheduled released
date.

Unreleased Manufacturing orders that aren't yet


manufacturing released (and not set to technically
orders overdue for completed) and where the scheduled
release release date is already in the past.

Manufacturing orders All sales order items for which a Released but Released manufacturing orders for which a
initially con rmed subsequent manufacturing order has also undelivered goods receipt hasn't yet been posted
been initially con rmed. This is based on manufacturing although the con rmed delivery date in the
the actual start date of the manufacturing orders with sales corresponding sales order item is already
order. order con rmation in the past.
date in the past

Manufacturing Manufacturing orders for which the actual


orders con rmed nal con rmation was after the scheduled
later than scheduled nish date.

Undelivered Manufacturing orders for which a goods


manufacturing receipt was not yet posted although the
orders with scheduled nish date is already in the
scheduled nish past.
date in the past

This is custom documentation. For more information, please visit the SAP Help Portal 147
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Manufacturing orders All sales order items for which a Manufacturing Manufacturing orders for which the (last)
delivered subsequent manufacturing order has also orders delivered goods receipt was posted after the
been delivered and technically after sales order con rmed delivery date in the
completed. This is based on the actual con rmation date corresponding sales order item.
delivery date. If the delivered quantity is
greater than or equal to the target Manufacturing Manufacturing orders for which the last
quantity, or if the delivery completed orders delivered goods receipt was posted after the
indicator is set, the manufacturing order after scheduled scheduled nish date.
is technically completed. Delivery items nish date
with zero quantity are excluded.
Sales order item Sales order items with unrestricted-use
stock exists stock reserved for the relevant sales order
item.

Delivered Manufacturing orders with goods receipt


manufacturing postings where the delivery completed
orders without indicator isn't set.
"Delivery
completed" set

Con rmed Manufacturing orders with an initial


manufacturing con rmation (an actual start date) but
orders not nally aren't con rmed as nished because the
con rmed document doesn't have a con rmed order
nish date.

Sales order items All sales order items for which a Delivery items Sales order items that have a subsequent
with goods issue subsequent goods issue has also been created delivery item, which is indicated by the
posted created. This is based on the creation creation date of the delivery item.
date of the goods issue.
Goods issue posted Sales order items for which the actual
after planned goods goods issue was posted after the planned
issue date in sales goods issue date in the corresponding
order item sales schedule line.

Delivery items Sales order items for which the creation


created before date of the delivery item is before the
goods receipt actual delivery date.
posted

Customer invoice All sales order items for which a – None – – None –
items created subsequent customer invoice has also
been created. This is based on the
creation date of the invoice.

Intercompany sales order item creation to FI-AP item clearing


Find out more about the process ow Intercompany sales order item creation to FI-AP item clearing.

General Information

ID in KPI Catalog KPSD000366

What does this process ow measure? Measures the number of intercompany sales order items created in

This is custom documentation. For more information, please visit the SAP Help Portal 148
12/19/2022
the reference period where an outbound delivery and a
corresponding delivery-related invoice are expected and shows
how many of them reached prede ned stages of the process and
how long on average this progression took

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -63 to -35 calendar days relative to the
date of data collection

What data records are extracted? All standard sales order items at schedule line level that were
created in the reference period that meet the following criteria:

Are sales order or standard items relevant for delivery-


related billing and don't have zero quantities

Where the overall delivery status to the item is either Not


yet processed, Partially processed, or Completely
processed

Have a customer number representing an internal customer


for intercompany billing

Have a vendor number maintained for plants

Only the rst schedule line for a delivery date is considered.


Entries where the sales company code is equal to the shipping
company code are not considered

What details are extracted? As outlined in the KPI catalog entry for KPSD000366 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

This is custom documentation. For more information, please visit the SAP Help Portal 149
12/19/2022

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Sales order items All sales order items that were created Sales order items Sales order items for which a rejection
created within the reference period as indicated rejected reason has been entered.
in the table above for What data records
are extracted? Sales order items Sales order items for which the
incomplete completeness status for item data is
incomplete

Delivery items All sales order items for which a Sales order items Sales order items for which the delivery
created subsequent delivery item has also been blocked for delivery block status is either Partially processed
created. This is based on the creation or Completely processed and a delivery
date of the delivery item. If there is more document doesn't exist.
than 1 delivery item, only the latest
delivery item is considered. Sales order items Sales order items for which the delivery
incomplete for indicator is Not yet processed and a
delivery delivery document doesn't exist.

Delivery created Sales order items for which the creation


after planned date of the delivery is after the material
material availability staging/availability date.

Goods issue posted All sales order items for which a Sales order items Sales order items for which the
subsequent goods issue has also been incomplete for Incomplete for goods movement status
created for which goods movement is goods movement is set to Not yet processed.
completed. This is based on the creation
date of the goods issue. If there is more Goods issue posted Sales order items for which the
than 1 goods issue, only the latest goods after planned goods subsequent goods issue was created after
issue is considered. issue date the planned goods issue date.

Customer invoice All sales order items for which a Sales order items Sales order items for which the order-
items created subsequent customer invoice has also blocked for billing related billing status is set to Not yet
been created that is completely processed.
processed. This is based on the creation
date of the invoice. If there is more than 1 Sales order items Sales order items for which the
invoice, only the latest invoice is incomplete for incompletion status is set to Not yet
considered. billing processed.

This is custom documentation. For more information, please visit the SAP Help Portal 150
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Invoice posted after Sales order items for which the


planned billing date subsequent customer invoice was created
after the planned billing date of the sales
order.

Customer FI-AR items All sales order items for which a Customer FI-AR Sales order items for which a clearing date
created subsequent FI-AR item has also been items cleared has been entered for the subsequent
created. This is based on the entry date customer FI-AR item.
of the FI-AR item. FI-AR Items that have
been reversed aren't considered.

Intercompany All sales order items for which a – None – – None –


documents created subsequent intercompany document has
also been created that has been
completely processed and for which
goods movement has been completed.
This is based on the creation date of the
intercompany invoice. If there's more
than 1 invoice, only the latest invoice is
considered.

Intercompany FI-AR All sales order items for which a Intercompany FI-AR Sales order items for which a clearing date
items created subsequent intercompany FI-AR item has items cleared has been entered for the subsequent
also been created. This is based on the intercompany FI-AR item.
entry date of the FI-AR item.
Intercompany FI-AR items that have been
reversed are not considered.

Intercompany FI-AP All sales order items for which a Intercompany FI-AP Sales order items for which a clearing date
items created subsequent intercompany FI-AP item has items cleared has been entered for the subsequent
also been created. This is based on the intercompany FI-AP item.
entry date of the intercompany FI-AP
item.

Sales order item creation (order-related billing) to FI-AR item


clearing
Find out more about the process ow Sales order item creation (order-related billing) to FI-AR item clearing.

General Information

ID in KPI Catalog KPSD000367

What does this process ow measure? Measures the number of sales order items created in the reference
period where a corresponding order-related invoice and an FI
document are expected, and shows how many of them reached
prede ned stages of the process and how long on average this
progression took

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -77 to -35 calendar days relative to the
date of data collection

What data records are extracted? All standard sales order items that are relevant for order-related

This is custom documentation. For more information, please visit the SAP Help Portal 151
12/19/2022
billing (status according to order, target, or the delivery quantity),
where the order-related billing status is Not yet processed,
Partially processed or Completely processed, for which
subsequent documents created from the sales documents have the
document category Invoice, and that were created within the
reference period.

What details are extracted? As outlined in the KPI catalog entry for KPSD000367 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note

This is custom documentation. For more information, please visit the SAP Help Portal 152
12/19/2022
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Sales order items All standard sales order items that are Sales order items Sales order items that have a reason for
created relevant for order-related billing (status rejected rejection assigned to the item data in the
according to order, target, or the delivery sales document
quantity), where the order-related billing
status is Not yet processed, Partially Unbilled items with Sales order items that have the order-
processed or Completely processed, for billing block related billing status Not yet processed
which subsequent documents created and the billing block status Completely
from the sales documents have the processed
document category Invoice, and that
Unbilled items Sales order items that have the order-
were created within the reference period.
incomplete for related billing status Not yet processed
billing and for which the incompletion status for
billing-related information is also set to
Not yet processed

Customer invoices All sales order items that also have Customer invoices Sales order items where the subsequent
created subsequent customer invoices created. manually created customer invoices were created by a
This is determined based on the date on dialog user or with a transaction code for
which the invoice was created. If more dialog mode
than one invoice was created for the sales
order items, the most recent customer Customer invoices Sales order items where the subsequent
invoice creation date is considered when canceled customer invoices for which the Billing
determining the average times. document is canceled ag is set to Yes

Customer invoices Sales order items for which the


not yet transferred subsequent customer invoices couldn't be
to FI posted to accounting because the status
for transfer to accounting is Error in
accounting interface, Billing document
blocked for forwarding to FI, Posting
document not created, Accounting
document not created, or No posting
document due to fund management

Payment terms Sales order items with different keys for


different in sales de ning customer payment terms
order and invoice assigned in the sales order document and
subsequent customer billing document

FI-AR items created All sales order items for which the Payment terms Sales order items where the subsequently
subsequent customer invoice also has an different in invoice created customer billing document and
accounting document posted. This is and FI corresponding accounting document
determined based on the date on which posted to FI have different keys for
the FI document was created. de ning customer payment terms

FI document Sales order items for which the


reversed subsequently posted accounting
documents (for related customer invoices)
contain another accounting document
number with which the documents have
been reversed

This is custom documentation. For more information, please visit the SAP Help Portal 153
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Customer invoices Sales order items for which the


manually released to subsequently created customer invoices
FI were released for posting to accounting by
a transaction code for dialog mode, which
is recorded in the accounting document

FI-AR items cleared All sales order items for which the Open items with Sales order items for which the
subsequent customer invoice was also dunning block corresponding FI item postings have a
paid. This is determined based on the dunning block indicator following
date on which the corresponding allocation of a dunning block reason, which
accounting document was cleared. prevents the open items from being
dunned

Open items already Sales order items for which the


dunned corresponding open items in FI have a
dunning level assigned, which indicates
how often an item has been dunned

FI-AR items FI-AR accounting items that were cleared


manually cleared by a dialog user or with a transaction code
speci c to dialog mode

Quotation item creation to sales order item creation


Find out more about the process ow Quotation item creation to sales order item creation.

General Information

ID in KPI Catalog KPSD000368

What does this process ow measure? Measures the number of quotation items created in the reference
period and shows how many of them reached prede ned stages of
the process and how long on average this progression took

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -98 to -14 calendar days relative to the
date of data collection

What data records are extracted? All quotation items that were created in the reference period

What details are extracted? As outlined in the KPI catalog entry for KPSD000368 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

This is custom documentation. For more information, please visit the SAP Help Portal 154
12/19/2022

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Quotation items All quotation items that were Quotation items Quotation items that were created later than the
created created in the reference period. created after quotation.
quotation created

Quotation items Quotation items that were created with reference to


created with an inquiry.
reference to
inquiry

Quotation items Quotation items that were created with reference to a


created with quotation.
reference to
quotation

This is custom documentation. For more information, please visit the SAP Help Portal 155
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Quotation items Quotation items that were created with reference to


created with an order.
reference to order

This stage represents additional Quotation items Quotation items that are considered completely
activities related to the previous with completion processed after the rst subsequent sales order has
stage. rule " rst been created.
reference"

Quotation items Quotation items that are


with completion considered completely processed after their quantity
rule "full has been fully referenced by subsequent sales
reference" orders.

This stage represents additional Quotation items Quotation items for which no subsequent sales
activities related to the previous not referenced and orders are created and for which a rejection reason is
stage. not rejected not set.

Quotation items Quotation items for which no subsequent sales


fully rejected orders are created and for which a rejection reason is
set.

This stage represents additional Quotation items Quotation items that have the incompletion status
activities related to the previous with incomplete Not yet processed for the delivery.
stage. delivery data

Quotation items Quotation items that have the incompletion status


with incomplete Not yet processed for the billing.
billing data

First sales order All quotation items for which a rst Quotation items Quotation items that are partially processed and for
items created sales order was also subsequently with partial which a rejection reason isn't set.
referencing created. processing
quotation item
Open quotation Quotation items with valid-to date in the past.
items with validity
end in the past

Quotation items All quotation items for which a last Quotation items Quotation items that are completely processed.
fully processed sales order was also subsequently fully referenced
created.
Referenced Quotation items that are partially processed and for
quotation items which a rejection reason is set.
with rejection

Sales order item creation (sell from stock) to delivery creation


Find out more about the process ow Sales order item creation (sell from stock) to delivery creation.

 Note
This process ow is only available as of ST-A/PI 01V_731. Upgrading to the latest version is always recommended. Also
ensure you implement the latest version of the relevant SAP Note for your ST-A/PI version as outlined under Technical
Prerequisites in the Administration Guide .

This is custom documentation. For more information, please visit the SAP Help Portal 156
12/19/2022

General Information

ID in KPI Catalog KPSD000369

What does this process ow measure? Measures the number of sales order items that were served from
unrestricted-use stock (and not from special or separately
managed stock) and created in the reference period where an
outbound delivery is expected and shows how many of them
reached prede ned stages of the process and how long on average
this progression took.

How frequently is data collected and what is the reference period Frequency: every 3 days
for the data collected?
Reference period: -14 to -1 calendar days relative to the
date of data collection

What data records are extracted? All standard sales order items that do not have a speci c stock
type assigned, are delivery relevant, and were created in the
reference period.

What details are extracted? As outlined in the KPI catalog entry for KPSD000369 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

This is custom documentation. For more information, please visit the SAP Help Portal 157
12/19/2022

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Sales order items All standard sales order items that do not Sales order items Sales order items that have a rejection
created have a speci c stock type assigned, are rejected reason assigned.
delivery relevant, and were created in the
reference period. Sales order items Sales order items that have the
with unprocessed con rmation status “Not yet processed”.
con rmation status

Sales order items Sales order items that do not have a


with quantity not con rmed quantity at schedule-line level.
con rmed for
customer-requested
delivery date

This stage represents additional Sales order items Sales order items with the overall delivery
activities related to the previous stage. partially delivered status Partially processed.

Sales order items Sales order items with the overall delivery
blocked for delivery status Not yet processed or Partially
processed and the delivery block status
Partially processed or Completely
processed for the item.

Sales order items Sales order items that don’t have the
not delivered and overall delivery status Completely
planned material processed yet and the material
availability date in availability date for the item at schedule-
the past line level is already overdue (that is, older
than the last data collection date).

This stage represents additional Open sales order Sales order items that don’t have the
activities related to the previous stage. items with no zero overall delivery status Completely
unrestricted-use processed yet and the valuated
stock unrestricted-use stock in the storage
location of the material is zero.

This is custom documentation. For more information, please visit the SAP Help Portal 158
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Open sales order Sales order items that don’t have the
items with less overall delivery status Completely
unrestricted-use processed yet and the valuated
stock than unrestricted-use stock in the storage
con rmed quantity location of the material is less than the
con rmed quantity.

Open sales order Sales order items that don’t have the
items with stock in overall delivery status Completely
quality inspection processed yet and the stock in quality
inspection is greater than zero.

Open sales order Sales order items that don’t have the
items with overall delivery status Completely
insufficient stock processed yet and insufficient stock has
found during already been identi ed for the sales order
delivery due runs item in the latest collective processing of
last week the sales document header.

This stage represents additional Sales order items Sales order items that are associated with
activities related to the previous stage. with overdue outstanding purchase order items that
purchase order have not yet been received as expected.
items

Open sales order Open sales order items that are


items with open associated with open purchase order
purchase order items for which goods a receipt is
items expected.

Sales order items Sales order items that are associated with
with overdue overdue purchase requisition items that
purchase requisition have not yet been ordered as expected.
items

This stage represents additional Sales order items Sales order items that are associated with
activities related to the previous stage. with overdue outstanding manufacturing orders that
manufacturing have not yet been produced as expected.
orders

Open sales order Open sales order items that are


items with open associated with open manufacturing
manufacturing orders for which a goods movement is
orders expected.

Sales order items Sales order items that are associated with
with overdue overdue planned orders that have not yet
planned orders been converted as expected.

Delivery items All standard sales order items for which a Delivery items Delivery documents that were created by
created subsequent delivery document item was manually created a user in dialog mode or with a transaction
also created. code speci cally for dialog mode.

Delivery items Delivery documents where the date on


created after which the delivery items were created is
planned material later than the date on which sufficient
availability date quantities of the items are available so
that picking can begin.

This is custom documentation. For more information, please visit the SAP Help Portal 159
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Delivered sales Sales order items with the overall delivery


order items with status Completely processed although
insufficient stock insufficient stock has already been
found during identi ed for the sales order item in the
delivery due runs latest collective processing of the sales
last week document header.

Sales order items Sales order items that have an on-time


delivered by delivery date of schedule lines.
customer-requested
delivery date

Returns order item creation to goods receipt posting


Find out more about the process ow Returns order item creation to goods receipt posting.

General Information

ID in KPI Catalog KPSD000380

What does this process ow measure? Measures the number of returns order items that were created in
the reference period where a return delivery is expected, and
shows how many of these items reached prede ned stages of the
process and how long on average this progression took.

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -49 to -7 calendar days relative to the
date of data collection

What data records are extracted? All returns order items that were created in the reference period for
which a returns delivery is expected.

What details are extracted? As outlined in the KPI catalog entry for KPSD000380 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

This is custom documentation. For more information, please visit the SAP Help Portal 160
12/19/2022

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Returns order items All returns order items that were created Returns order items All returns order items that were created
created in the reference period and for which a created with invoice with a reference to a preceding sales
returns delivery is expected. This is reference invoice.
based on the creation date of the return
order items. Returns order items All returns order items that were created
created with order with a reference to a preceding sales
reference order.

Returns order items All returns order items that were created
created without without a reference to a
reference preceding document.

This is custom documentation. For more information, please visit the SAP Help Portal 161
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

This stage represents additional Open returns order All returns order items where a returns
activities related to the previous stage. items with delivery delivery hasn't yet been created and
block where either the entire order or
corresponding schedule lines are blocked
for delivery.

Open returns order All returns order items where a returns


items with material delivery hasn't yet been created although
availability date in the calculated material availability date is
the past already in the past.

Returns delivery All return order items for which a Open returns All returns order items where the
items created subsequent returns delivery item has delivery items with corresponding goods movement posting
also been created. This is based on the planned goods for the returns delivery hasn't yet been
date on which the delivery item was receipt date in the posted although the calculated
created. past planned goods movement date is already
in the past.

Goods receipt posted All return order items for which a Goods receipt All returns order items for which the goods
subsequent goods receipt has also been posted into returns receipt has been posted into returns
posted. This is based on the date on stock stock.
which the goods issue was entered in the
system. Goods receipt All returns order items for which the goods
posted into receipt has been posted into unrestricted-
unrestricted-use use stock.
stock

Goods receipt All returns order items for which the goods
posted into quality receipt has been posted into
inspection stock quality inspection stock.

Goods receipt All returns order items for which the goods
posted into blocked receipt has been posted into blocked
stock stock.

Goods receipt All returns order items that are related to


posted for customer consignment returns.
consignment return

Credit memo items All return order items for which a Returns order items All returns order items that aren't relevant
created subsequent credit memo item has also without billing for billing, which means that credit
been created. This is based on the date relevance memos aren't expected.
on which the credit memo item was
created.

Debit memo request item creation to FI-AR item clearing


Find out more about the process ow Debit memo request item creation to FI-AR item clearing.

General Information

ID in KPI Catalog KPSD000460

What does this process ow measure? Measures the number of debit memo request items created in the
reference period where a corresponding debit memo and an FI

This is custom documentation. For more information, please visit the SAP Help Portal 162
12/19/2022
document are expected, and shows how many of them reached
prede ned stages of the process and how long on average this
progression took

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -77 to -35 calendar days relative to the
date of data collection

What data records are extracted? All standard sales order items that are classi ed as items of a
debit memo request, that are relevant for order-related billing
(status according to order, target, or the delivery quantity), where
the order-related billing status is Not yet processed, Partially
processed, or Completely processed, and that were created within
the reference period

What details are extracted? As outlined in the KPI catalog entry for KPSD000460 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

This is custom documentation. For more information, please visit the SAP Help Portal 163
12/19/2022
Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Debit memo request All standard sales order items that are Debit memo request Debit memo request items that have a
items created classi ed as items of a debit memo items rejected reason for rejection assigned to the item
request, that are relevant for order- data in the sales document
related billing (status according to order,
target, or the delivery quantity), where the Unbilled items with Debit memo request items that have the
order-related billing status is Not yet billing block order-related billing status Not yet
processed, Partially processed, or processed and have a billing block value
Completely processed, and that were assigned indicating that the item is
created within the reference period. blocked for billing; the billing block can
also be assigned at header level to the
entire sales document

Unbilled items Debit memo request items that have the


incomplete for order-related billing status Not yet
billing processed and for which the item
incompletion status for billing-related
information is set to Not yet processed.

Debit memo items All debit memo request items that also Debit memo items Debit memo request items where the
created have subsequent documents of the manually created subsequent debit memo items were
category Debit memo' created for the created by a dialog user or with a
items. This is determined based on the transaction code for dialog mode
date on which the debit memo was
created. If more than one debit memo Debit memo items Debit memo request items where the
was created for the debit memo request canceled subsequent debit memos have the Billing
items, the most recent debit memo document is canceled ag set to Yes
creation date is considered when
Debit memos not yet Debit memo request items for which the
determining the average times.
transferred to FI subsequent debit memos couldn't be
posted to accounting because the status
for transfer to accounting is Error in
accounting interface, Billing document
blocked for forwarding to FI, Posting
document not created, Accounting
document not created, or No posting
document due to fund management

Payment terms Debit memo request items with different


different in request keys for de ning customer payment terms
and memo assigned in the debit memo request and in
the subsequent debit memo

FI-AR items created All debit memo request items for which Payment terms Debit memo request items where the
the subsequent debit memo items also different in debit subsequently created debit memo and the
have corresponding open items posted memo and FI corresponding accounting document
through an accounting document in FI-AR. posted to FI have different keys for
This is determined based on the date on de ning customer payment terms
which the FI document was created.

This is custom documentation. For more information, please visit the SAP Help Portal 164
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

FI document Debit memo request items for which the


reversed subsequently posted accounting
documents (for the interconnecting debit
memo) contain another accounting
document number with which these have
been reversed

Debit memos Debit memo request items for which the


manually released to subsequently created debit memos were
FI released for posting to accounting by a
transaction code for dialog mode, which is
recorded in the accounting document

FI-AR items cleared All debit memo request items for which Open items with Debit memo request items for which the
the subsequent debit memo items were dunning block corresponding FI item postings have a
settled and the open items were cleared. dunning block indicator following the
This is determined based on the date on allocation of a dunning block reason, which
which the corresponding accounting prevents the open items from being
document was cleared. dunned

Open items already Debit memo request items for which the
dunned corresponding open items in FI have a
dunning level assigned, which indicates
how often an item has been dunned

FI-AR items FI-AR accounting items that were cleared


manually cleared by a dialog user or with a transaction code
speci c to dialog mode

Credit memo request item creation to FI-AR item clearing


Find out more about the process ow Credit memo request item creation to FI-AR item clearing.

General Information

ID in KPI Catalog KPSD000462

What does this process ow measure? Measures the number of credit memo request items created in the
reference period where a corresponding credit memo and an FI
document are expected, and shows how many of them reached
prede ned stages of the process and how long on average this
progression took

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -77 to -35 calendar days relative to the
date of data collection

What data records are extracted? All standard sales order items that are classi ed as items of a
credit memo request, that are relevant for order-related billing
(status according to order, target, or the delivery quantity), where
the order-related billing status is Not yet processed, Partially
processed, or Completely processed, and that are created within
the reference period.

What details are extracted? As outlined in the KPI catalog entry for KPSD000462 on the
This is custom documentation. For more information, please visit the SAP Help Portal 165
12/19/2022
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

This is custom documentation. For more information, please visit the SAP Help Portal 166
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Credit memo request All standard sales order items that are Credit memo Credit memo request items that have a
items created classi ed as items of a credit memo request items reason for rejection assigned to the item
request, that are relevant for order- rejected data in the sales document
related billing (status according to order,
target, or the delivery quantity), where the Unbilled items with Credit memo request items that have a
order-related billing status is Not yet billing block billing block value assigned indicating that
processed, Partially processed, or the item is blocked for billing; the billing
Completely processed, and that are block can also be assigned at header level
created within the reference period. to the entire sales document

Unbilled items Credit memo request items that have the


incomplete for order-related billing status Not yet
billing processed and for which the item
incompletion status for billing-related
information is set to Not yet processed

Credit memo items All credit memo request items that also Credit memo items Credit memo request items where the
created have subsequent documents of the manually created subsequent credit memo items were
category Credit memo created for the created by a dialog user or with a
items. This is determined based on the transaction code for dialog mode
date on which the credit memo was
created. If more than one credit memo Credit memo items Credit memo request items where the
was created for the credit memo request canceled subsequent credit memos have the Billing
items, the most recent credit memo document is canceled ag set to Yes
creation date is considered when
Credit memos not Credit memo request items for which the
determining the average times.
yet transferred to FI subsequent credit memos couldn't be
posted to accounting because the status
for transfer to accounting is Error in
accounting interface, Billing document
blocked for forwarding to FI, Posting
document not created, Accounting
document not created, or No posting
document due to fund management

Payment terms Credit memo request items with different


different in request keys for de ning payment terms assigned
and memo in the credit memo request and in the
subsequent credit memo

FI-AR items created All credit memo request items for which Payment terms Credit memo request items where the
the subsequent credit memo items also different in credit subsequently created credit memo and
have corresponding open items posted memo and FI the corresponding accounting document
through an accounting document in FI-AR. was posted to FI have different keys for
This is determined based on the date on de ning payment terms
which the FI document was created.
FI document Credit memo request items for which the
reversed subsequently posted accounting
documents (for the interconnecting credit
memo) contain another accounting
document number with which these have
been reversed

Credit memos Credit memo request items for which the


manually released to subsequently created credit memos were
FI released for posting to accounting by a
transaction code for dialog mode, which is
recorded in the accounting document

This is custom documentation. For more information, please visit the SAP Help Portal 167
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

FI-AR items cleared All credit memo request items for which FI-AR items FI-AR accounting items that were cleared
the subsequent credit memo items have manually cleared by a dialog user or with a transaction code
been settled and the open items cleared. speci c to dialog mode
This is determined based on the date on
which the corresponding accounting
document was cleared.

Plant maintenance noti cation creation to noti cation


completion
Find out more about the process ow Plant maintenance noti cation creation to noti cation completion.

General Information

ID in KPI Catalog KWPM000160

What does this process ow measure? Measures the number of maintenance noti cations created in the
reference period and shows how many of them reached prede ned
stages of the process and how long on average this progression
took

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -70 to -14 calendar days relative to the
date of data collection

What data records are extracted? All maintenance noti cations that were created in the reference
period

What details are extracted? As outlined in the KPI catalog entry for KWPM000160 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

This is custom documentation. For more information, please visit the SAP Help Portal 168
12/19/2022

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Maintenance All maintenance noti cations that were Maintenance Maintenance noti cations that have a
noti cations created created in the reference period. noti cations created reference to an existing maintenance plan.
with maintenance
plan reference

Maintenance Maintenance noti cations that were


noti cations created created with a general noti cation as the
as general origin.
noti cations

Maintenance Maintenance noti cations that were


noti cations created created with a malfunction report as the
as malfunction origin.
reports

This is custom documentation. For more information, please visit the SAP Help Portal 169
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Maintenance Maintenance noti cations that were


noti cations created created with an activity report as the
as activity reports origin.

This stage represents additional Maintenance Maintenance noti cations for which a
activities related to the previous stage. noti cations with required end date maintained is
required end date maintained by which the noti cation is to
be processed.

Maintenance Maintenance noti cations for which the


noti cations for Breakdown indicator set.
breakdown

Maintenance Maintenance noti cations that have one or


noti cations with more documented items assigned to
recorded items them.

Maintenance All maintenance noti cations that also Open maintenance Maintenance noti cations that have a
noti cations have been set to In process. noti cations with required end date in the past but for which
processing started required end date in the noti cation isn't yet completed.
 Note the past

The average times related to this step


Maintenance Maintenance noti cations that have
can't currently be calculated. The date
noti cations with assigned tasks.
information needed for the calculation
tasks
is expected to be provided in an
upcoming version of ST-A/PI. Open maintenance Maintenance noti cations that have open
noti cations with tasks assigned to them.
open tasks

This stage represents additional Maintenance Maintenance noti cations that have a
activities related to the previous stage. noti cations with maintenance order assigned to them.
assigned order

Open maintenance Maintenance noti cations that aren't yet


noti cations with completed and for which the assigned
created order not maintenance order is created but not yet
released released.

Open maintenance Maintenance noti cations that aren't yet


noti cations with completed and for which the assigned
released order not maintenance order is released but isn't
closed technically completed or closed.

Open maintenance Maintenance noti cations that aren't yet


noti cations but completed although the assigned
order already closed maintenance order is set to completed.

Processed All maintenance noti cations that have Maintenance Maintenance noti cations that weren't
maintenance also been processed and completed. noti cations completed until after the required end
noti cations This is determined based on the date on completed after date.
completed which the noti cation was completed and required end date
is also considered when determining the
average times. Maintenance Maintenance noti cations that were set to
noti cations Completed but for which the assigned
completed but order maintenance order is still open.
still open

This is custom documentation. For more information, please visit the SAP Help Portal 170
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Completed Maintenance noti cations that were set to


maintenance Completed but never set to In process.
noti cations without
processing

Customer service noti cation creation to noti cation completion


Find out more about the process ow Customer service noti cation creation to noti cation completion.

General Information

ID in KPI Catalog KWPM000161

What does this process ow measure? Measures the number of customer service noti cations created in
the reference period and shows how many of them reached
prede ned stages of the process and how long on average this
progression took

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -70 to -14 calendar days relative to the
date of data collection

What data records are extracted? All customer service noti cations that were created in the reference
period

What details are extracted? As outlined in the KPI catalog entry for KWPM000161 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

This is custom documentation. For more information, please visit the SAP Help Portal 171
12/19/2022

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Service noti cations All service noti cations that were created Service noti cations Service noti cations that have a reference
created in the reference period. created with service to an existing service plan.
plan reference

Service noti cations Service noti cations that were created


created as problem with a problem noti cation as the origin.
noti cations

Service noti cations Service noti cations that were created


created as activity with an activity report as the origin.
reports

Service noti cations Service noti cations that were created


created as general with a general noti cation as the origin.
noti cations

This is custom documentation. For more information, please visit the SAP Help Portal 172
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

This stage represents additional Service noti cations Service noti cations for which a required
activities related to the previous stage. with required end end date is maintained by which the
date noti cation is to be processed.

Service noti cations Service noti cations for which the


for breakdown Breakdown indicator is set.

Service noti cations Service noti cations that have one or more
with recorded items documented items assigned to them.

Service noti cations All service noti cations that have been Open service Service noti cations that have a required
processing started set to In process. noti cations with end date in the past but for which the
required end date in noti cation isn't yet completed.
 Note the past

The average times related to this step


Service noti cations Service noti cations that have assigned
cannot currently be calculated. The
with tasks tasks.
date information needed for the
calculation is expected to be provided Open service Service noti cations that have open tasks
in an upcoming version of ST-A/PI. noti cations with assigned to them.
open tasks

This stage represents additional Service noti cations Service noti cations that have a service
activities related to the previous stage. with assigned order order assigned to them.

Open service Service noti cations that aren't yet


noti cations with completed and for which the assigned
created order not service order is created but not yet
released released.

Open service Service noti cations that aren't yet


noti cations with completed and for which the assigned
released order not service order is released but isn't
closed technically completed or closed.

Open service Service noti cations that aren't yet


noti cations but completed although the assigned service
order already closed order is set to completed.

This stage represents additional Service noti cations Service noti cations that have a sales
activities related to the previous stage. with assigned sales order assigned.
order

Processed service All service noti cations that have also Service noti cations Service noti cations that weren't
noti cations been processed and completed. This is completed after completed until after the required end
completed determined based on the date on which required end date date.
the noti cation was completed and is
also considered when determining the Service noti cations Service noti cations that were set to
average times. completed but order Completed but for which the assigned
still open service order is still open.

Completed service Service noti cations that were set to


noti cations without Completed but never set to In process.
processing

Plant maintenance order creation to order closure


Find out more about the process ow Plant maintenance order creation to order closure.
This is custom documentation. For more information, please visit the SAP Help Portal 173
12/19/2022

General Information

ID in KPI Catalog KWPM000260

What does this process ow measure? Measures the number of plant maintenance orders created in the
reference period and shows how many of them reached prede ned
stages of the process and how long on average this progression
took

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -70 to -14 calendar days relative to the
date of data collection

What data records are extracted? All maintenance orders that were created in the reference period

What details are extracted? As outlined in the KPI catalog entry for KWPM000260 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
This is custom documentation. For more information, please visit the SAP Help Portal 174
12/19/2022
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Maintenance orders All plant maintenance orders that were Maintenance orders Plant maintenance orders for which a
created created in the reference period. created with maintenance noti cation number is
noti cation assigned, either in reference to the
reference noti cation or that was subsequently
assigned to the order

Maintenance orders Plant maintenance orders for which a


created with maintenance plan number is assigned,
maintenance plan either as part of the maintenance plan
reference scheduling or that was subsequently
assigned to the order

Maintenance orders All plant maintenance orders that also Maintenance orders Plant maintenance orders with an actual
released have an actual release date. This is released after basic release date that's after the basic start
determined based on the date on which start date date of the order (planned earliest start
the order was released and is also date)
considered when determining the average
times. Unreleased Plant maintenance orders that were
maintenance orders created but haven't yet been released
with basic start date although the basic start date is already in
in the past the past

Maintenance orders All plant maintenance orders that also – None – – None –
initially con rmed have an actual start date. This is
determined based on the date on which
the rst operation of the order was
con rmed and is also considered when
determining the average times.

Maintenance orders All plant maintenance orders that also Released Plant maintenance orders that were
nally con rmed have a con rmed order nish date. This maintenance orders released but haven't yet been set to
is determined based on the date on which overdue for technically completed although the basic
the last operation was con rmed, the technical completion nish date is already in the past
order received the status Finally
con rmed, and is also considered when
determining the average times.

Maintenance orders All plant maintenance orders that also Maintenance orders Plant maintenance orders that have a
con rmed and have a technical completion date in technically technical completion date but that are not
technically completed addition to the con rmed order nish completed but not yet nally con rmed
date. This is determined based on the con rmed
date on which the order status was
changed to Technically complete and is Maintenance orders Plant maintenance orders that have a
also considered when determining the technically technical completion date that's after the
average times. completed after basic nish date (planned latest nish
basic nish date date)

This is custom documentation. For more information, please visit the SAP Help Portal 175
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Maintenance orders All plant maintenance orders that also Maintenance orders Plant maintenance orders that have a
con rmed and closed have a close date in addition to the closed but not close date indicating they were set to
con rmed order nish date. This is con rmed closed but that are yet not nally
determined based on the date on which con rmed
the order status was changed to Closed
and is also considered when determining
the average times.

Plant maintenance order creation to order settlement


Find out more about the process ow Plant maintenance order creation to order settlement.

General Information

ID in KPI Catalog KWPM000261

What does this process ow measure? Measures the number of plant maintenance orders created in the
reference period and shows how many of them reached prede ned
stages of the process and how long on average this progression
took

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -70 to -14 calendar days relative to the
date of data collection

What data records are extracted? All plant maintenance orders that were created in the reference
period

What details are extracted? As outlined in the KPI catalog entry for KWPM000261 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

This is custom documentation. For more information, please visit the SAP Help Portal 176
12/19/2022

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Maintenance orders All plant maintenance orders that Maintenance orders Plant maintenance orders with errors in
created were created in the reference period. with errors in cost cost calculation.
calculation

Maintenance orders Plant maintenance orders without


without preliminary preliminary costing.
costing

Maintenance orders Plant maintenance orders with estimated


with estimated costs costs.

This is custom documentation. For more information, please visit the SAP Help Portal 177
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Unreleased Plant maintenance orders not yet released


maintenance orders for which there is a settlement rule.
with settlement rule

Maintenance orders All plant maintenance orders that have Released Plant maintenance that have been
released also been released. maintenance orders released for which there isn't a settlement
without settlement rule.
rule

Maintenance orders All plant maintenance orders that have Maintenance orders Plant maintenance orders with
initially con rmed also been initially con rmed. with con rmation con rmation errors during goods
errors during goods movement posting.
movement posting

Maintenance orders Plant maintenance orders with


with con rmation con rmation errors during cost posting.
errors during cost
posting

Maintenance orders All plant maintenance orders that have Maintenance orders Plant maintenance orders with open
technically completed also been technically completed. with open purchase purchase order commitment items.
order commitment
item

Maintenance orders All plant maintenance orders that have Maintenance orders Plant maintenance orders with more than
rst settled also been settled. The rst settlement of with more than one one settlement.
plant maintenance orders is considered settlement
to calculate the lead time.

Customer service order creation to order closure


Find out more about the process ow Customer service order creation to order closure.

General Information

ID in KPI Catalog KWPM000262

What does this process ow measure? Measures the number of customer service orders in the reference
period and shows how many of them reached prede ned stages of
the process and how long on average this progression took

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -70 to -14 calendar days relative to the
date of data collection

What data records are extracted? All customer service orders that were created in the reference
period.

What details are extracted? As outlined in the KPI catalog entry for KWPM000262 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

This is custom documentation. For more information, please visit the SAP Help Portal 178
12/19/2022

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Service orders All service orders that were created in the Service orders Service orders with a noti cation reference
created reference period. created with assigned as a noti cation number
noti cation
reference

Service orders Service orders with a reference to the


created with maintenance plan assigned as a
maintenance plan maintenance plan number
reference

This is custom documentation. For more information, please visit the SAP Help Portal 179
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Service orders All service orders that were also released. Service orders Service orders released after the
released This is based on the actual release date. released after basic basic start date, indicated by an actual
start date release date that's later than the
basic start date

Service orders Service orders not yet released


overdue for release although the basic start date is already in
the past

Service orders All service orders that were also initially – None – – None –
initially con rmed con rmed. This is based on the actual
start date.

Service orders nally All service orders that were also nally Released service Service orders released but not yet set to
con rmed con rmed. This is based on the actual orders overdue for technically completed although the basic
nish date. technical completion nish date is already in the past

Service orders All service orders that were also Service orders Service orders that are technically
con rmed and con rmed and technically completed. technically completed based on the technical
technically completed This is indicated when an actual nish completed but not completion date but that are not yet nally
date and a technical completion date are con rmed con rmed
entered in the system.
Service orders Service orders that are technically
technically completed after the basic nish date,
completed after which is indicated by a technical
basic nish date completion date that's later than the basic
nish date

Service orders All service orders that were also Service orders Service orders that have a close date
con rmed and closed con rmed and closed. This is indicated closed but not indicating they were set to closed but that
when an actual nish date and a closing con rmed are yet not nally con rmed
date are entered in the system.

Customer service order creation to order settlement


Find out more about the process ow Customer service order creation to order settlement.

General Information

ID in KPI Catalog KWPM000263

What does this process ow measure? Measures the number of customer service orders created in the
reference period and shows how many of them reached prede ned
stages of the process and how long on average this progression
took

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -70 to -14 calendar days relative to the
date of data collection

What data records are extracted? All customer service orders that were created in the reference
period

What details are extracted? As outlined in the KPI catalog entry for KWPM000263 on the
Technical tab in the Detail List column.

This is custom documentation. For more information, please visit the SAP Help Portal 180
12/19/2022

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

Activated by default Yes

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

This is custom documentation. For more information, please visit the SAP Help Portal 181
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Service orders All customer service orders that were Service orders with Customer service orders created with
created created in the reference period. revenue revenue, which are those orders for which
costs are incurred on a value category
used in posting revenues and incoming
payments.

Service orders with Customer service orders with errors in


errors in cost cost calculation.
calculation

Service orders Customer service orders without


without preliminary preliminary costing.
costing

Service orders with Customer service orders with estimated


estimated costs costs.

Unreleased service Customer service maintenance orders not


orders with yet released for which there's a settlement
settlement rule rule.

Service orders with Customer service orders created for which


quotation created a quotation has been created but not yet
but not yet accepted accepted.

Service orders with Customer service orders created for which


quotation created a quotation has been both created and
and accepted accepted.

Service orders All customer service orders that have Released service Customer service orders that have been
released also been released. orders without released for which there's no settlement
settlement rule rule.

Service orders All customer service orders that have Service orders with Customer service orders with con rmation
initially con rmed also been initially con rmed. con rmation errors errors during goods movement posting.
during goods
movement posting

Service orders with Customer service orders with con rmation


con rmation errors errors during cost posting.
during cost posting

Service orders All customer service orders that have Service orders with Customer service orders with open
technically completed also been technically completed. open purchase purchase order commitment item.
order commitment
item

Service orders with Customer service orders that were created


billing request with a billing request, which means that a
debit memo request was created either
during the quotation acceptance phase or
after the order was technically completed,
which is standard.

Service orders rst All customer service orders that have Service orders with Customer service orders with more than
settled also been settled. The rst settlement of more than one one settlement.
customer service orders is considered to settlement
calculate the lead time.

This is custom documentation. For more information, please visit the SAP Help Portal 182
12/19/2022

Plant maintenance order component creation to goods issue


posting
Find out more about the process ow Plant maintenance order component creation to goods issue posting.

 Note
This process ow is only available as of ST-A/PI 01V_731. Upgrading to the latest version is always recommended. Also
ensure you implement the latest version of the relevant SAP Note for your ST-A/PI version as outlined under Technical
Prerequisites in the Administration Guide .

General Information

ID in KPI Catalog KWPM000264

What does this process ow measure? Measures the number of maintenance orders relevant for goods
issue posting created in the reference period and shows how many
of them reached prede ned stages of the process within this
selected timeframe and how long on average this progression took.

How frequently is data collected and what is the reference period Frequency: every 3 days
for the data collected?
Reference period: -14 to -1 calendar days relative to the
date of data collection

What data records are extracted? All maintenance orders that were created in the reference period
and that have a reservation.

What details are extracted? As outlined in the KPI catalog entry for KWPM000264 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

This is custom documentation. For more information, please visit the SAP Help Portal 183
12/19/2022

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Maintenance order All maintenance orders with a reservation Maintenance order Maintenance order components for which
components created created in the reference period. This is components with withdrawal is automatically posted when
determined by the date on which the back ush indicator the maintenance order operation time is
order was created. con rmed.

Maintenance order Maintenance order components reserved


components from from a plant that is not the plant executing
different plants the maintenance.

This is custom documentation. For more information, please visit the SAP Help Portal 184
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Maintenance order Maintenance order components marked


components marked for deletion.
for deletion

This stage represents additional Maintenance order Maintenance order components with a
activities related to the previous stage. components with requirements date at least 4 weeks in the
planned future relative to the order creation date. In
requirements date the case of preventive maintenance, this
more than 4 weeks identi es possible irregularities between
in the future the maintenance plan scheduling
parameters and deadline monitoring.

Maintenance order Maintenance order components that issue


components marked an error message in the event of negative
as missing parts availability.

Maintenance order All maintenance orders that also have an Open maintenance Open maintenance order components that
released for actual release date. This is determined order components have already been withdrawn and the
components by the date on which the order was with partial quantity withdrawn is less than the
released. withdrawal required quantity.

Open maintenance Open maintenance order components with


order components a planned requirements date in the past.
with planned This indicates that when the maintenance
requirements date in order operation time was con rmed, the
the past clear open reservation indicator wasn't
set, leaving the reservation document
open.

This stage represents additional Open maintenance Open maintenance order components with
activities related to the previous stage. order components no unrestricted-use stock.
with no
unrestricted-use
stock

Open maintenance Open maintenance order components for


order components which the current unrestricted-use stock is
with less less than that required in the reservation
unrestricted-use document.
stock than required

Open maintenance Open maintenance order components for


order components which there's an amount in the quality
with quality inspection stock being inspected.
inspection stock

This stage represents additional Maintenance order Procured maintenance order components
activities related to the previous stage. components with that have overdue purchase order items.
overdue purchase
order items

Open maintenance Open procured maintenance order


order components components that have open purchase
with open purchase order items.
order items

This is custom documentation. For more information, please visit the SAP Help Portal 185
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Maintenance order Procured maintenance order components


components with that have overdue purchase requisition
overdue purchase items.
requisition items

First goods issue All maintenance orders that also have a Goods issue earlier Maintenance order components where the
posted for material document that allocates all than planned goods issue happened before the
components materials issued for the order and their requirements date requirements date. This may impact the
quantities. This is determined by the maintenance budget if the component was
date on which the material document was withdrawn in a posting period before the
created. planned period.

Goods issue later Maintenance order components where the


than planned goods issue took place after the
requirements date requirements date. This may impact the
maintenance budget if the component was
withdrawn in a posting period after the
planned period.

Components with Maintenance order components where the


withdrawal quantity quantity withdrawn is greater than
greater than planned planned. This may impact the
maintenance budget.

Components with Maintenance order components where the


nal issue indicator quantity withdrawn is less than planned
and withdrawal and the nal issue indicator is set in the
quantity less than reservation document. In the case of
planned preventive maintenance, this may indicate
that the planned quantity in the task list
bill of material is wrong.

Customer service order component creation to goods issue


posting
Find out more about the process ow Customer service order component creation to goods issue posting.

 Note
This process ow is only available as of ST-A/PI 01V_731. Upgrading to the latest version is always recommended. Also
ensure you implement the latest version of the relevant SAP Note for your ST-A/PI version as outlined under Technical
Prerequisites in the Administration Guide .

General Information

ID in KPI Catalog KWPM000265

What does this process ow measure? Measures the number of service orders relevant for goods issue
posting created in the reference period and shows how many of
them reached prede ned stages of the process within this selected
timeframe and how long on average this progression took.

How frequently is data collected and what is the reference period Frequency: every 3 days

This is custom documentation. For more information, please visit the SAP Help Portal 186
12/19/2022
for the data collected? Reference period: -14 to -1 calendar days relative to the
date of data collection

What data records are extracted? All service orders that were created in the reference period and that
have a reservation

What details are extracted? As outlined in the KPI catalog entry for KWPM000265 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

This is custom documentation. For more information, please visit the SAP Help Portal 187
12/19/2022

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Service order All service orders with a reservation Service order Service order components for which
components created created in the reference period. This is components with withdrawal is automatically posted when
determined by the date on which the back ush indicator the maintenance order operation time is
order was created. con rmed.

Service order Service order components reserved from a


components from plant that is not the plant executing the
different plants maintenance.

Service order Service order components marked for


components marked deletion.
for deletion

This stage represents additional Service order Service order components with a
activities related to the previous stage. components with requirements date at least 4 weeks in the
planned future relative to the order creation date. In
requirements date the case of preventive maintenance, this
more than 4 weeks identi es possible irregularities between
in the future the maintenance plan scheduling
parameters and deadline monitoring.

Service order Service order components that issue an


components marked error message in the event of negative
as missing parts availability.

Service order All service orders that also have an actual Open service order Open service order components that have
released for release date. This is determined by the components with already been withdrawn and the quantity
components date on which the order was released. partial withdrawal withdrawn is less than the required
quantity.

Open service order Open service order components with a


components with planned requirements date in the past.
planned This indicates that when the service order
requirements date in operation time was con rmed, the clear
the past open reservation indicator wasn't set,
leaving the reservation document open.

This stage represents additional Open service order Open service order components with no
activities related to the previous stage. components with no unrestricted-use stock.
unrestricted-use
stock

Open service order Open service order components for which


components with the current unrestricted-use stock is less
less unrestricted- than that required in the reservation
use stock than document.
required

Open service order Open service order components for which


components with there's an amount in the quality inspection
quality inspection stock being inspected.
stock

This is custom documentation. For more information, please visit the SAP Help Portal 188
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

This stage represents additional Service order Procured service order components that
activities related to the previous stage. components with have overdue purchase order items.
overdue purchase
order items

Open service order Open procured service order components


components with that have open purchase order items.
open purchase
order items

Service order Procured service order components that


components with have overdue purchase requisition items.
overdue purchase
requisition items

First goods issue All service orders that also have a Goods issue earlier Service order components where the
posted for material document that allocates all than planned goods issue happened before the
components materials issued for the order and their requirements date requirements date. This may impact the
quantities. This is determined by the maintenance budget if the component was
date on which the material document was withdrawn in a posting period before the
created. planned period.

Goods issue later Service order components where the


than planned goods issue took place after the
requirements date requirements date. This may impact the
maintenance budget if the component was
withdrawn in a posting period after the
planned period.

Components with Service order components where the


withdrawal quantity withdrawal quantity is greater than
greater than planned planned. This may impact the
maintenance budget.

Components with Service order components where the


nal issue indicator withdrawal quantity is less than planned
and withdrawal and the nal issue indicator is set in the
quantity less than reservation document. In the case of
planned preventive maintenance, this may indicate
that the planned quantity is wrong.

Lot creation for goods receipt inspection from purchasing to


usage decision
Find out more about the process ow Lot creation for goods receipt inspection from purchasing to usage decision.

General Information

ID in KPI Catalog KWQM000161

What does this process ow measure? Measures the number of inspection lots for goods receipt
inspection from purchasing that were created in the reference
period and where a usage decision is expected, and shows how

This is custom documentation. For more information, please visit the SAP Help Portal 189
12/19/2022
many of them reached prede ned stages of the process and how
long on average this progression took.

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -56 to -1 calendar days relative to the
date of data collection

What data records are extracted? All inspection lots for goods receipt inspection from purchasing
that were created in the reference period.

What details are extracted? As outlined in the KPI catalog entry for KWQM000161 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

This is custom documentation. For more information, please visit the SAP Help Portal 190
12/19/2022

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Inspection lots All inspection lots for goods receipt Inspection lots Inspection lots that weren't created
created inspection from purchasing that were manually created automatically by the SAP system.
created in the reference period. The
creation date is the date on which Inspection lots for Inspection lots that refer to materials that
the inspection lot record was created. material with require detailed documentation. Only for
required these materials does the SAP system
documentation store additional change logs for status
or eld changes.

Inspection lots Inspection lots that were canceled after


canceled creation.

This stage represents additional Inspection lots Inspection lots that require a dedicated
activities related to the previous stage. without required inspection plan but for which the plan
inspection plan hasn't yet been assigned.

Inspection lots with Inspection lots with a dedicated


inspection plan inspection plan.

This stage represents additional Inspection lots Inspection lots where there are
activities related to the previous stage. without completed outstanding quantities that are to be
stock posting posted from quality inspection stock to
unrestricted-use stock.

Inspection lots with Inspection lots where the lot quantity was
inspection stock posted to inspection stock (and not
directly to unrestricted-use stock) when
the inspection lot was created.

This stage represents additional Inspection lots with Inspection lots where short-term
activities related to the previous stage. outstanding short- characteristics are outstanding
term characteristics for processing and completion.

Inspection lots with Inspection lots where all short-term


completed short- characteristics are completed so that a
term characteristics usage decision could be made.

This stage represents additional Inspection lots Inspection lots where the usage decision is
activities related to the previous stage. without usage missing although the inspection should be
decision and with nished according to plan.
planned inspection
end date in the past

Inspection lots Inspection lots where the usage decision is


without usage missing, but at least one characteristic
decision and with at had the result con rmed.
least one con rmed
result

Inspection lots with All inspection lots for which a usage Inspection lots with Inspection lots where the usage decision
usage decision taken decision is also processed. This is rejection as usage was rejection of the goods receipt.
determined based on the date of the decision
code used for the usage decision.

This is custom documentation. For more information, please visit the SAP Help Portal 191
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Inspection lots with Inspection lots where the SAP system can
planned automatic make an automatic usage decision if the
usage decision relevant prerequisites are met.

Lot creation for goods receipt inspection from manufacturing to


usage decision
Find out more about the process ow Lot creation for goods receipt inspection from manufacturing to usage decision.

General Information

ID in KPI Catalog KWQM000162

What does this process ow measure? Measures the number of inspection lots for goods receipt
inspection from manufacturing that were created in the reference
period and where a usage decision is expected, and shows how
many of them reached prede ned stages of the process and how
long on average this progression took.

How frequently is data collected and what is the reference period Frequency: weekly
for the data collected?
Reference period: -56 to -1 calendar days relative to the
date of data collection

What data records are extracted? All inspection lots for goods receipt inspection from manufacturing
that were created in the reference period.

What details are extracted? As outlined in the KPI catalog entry for KWQM000162 on the
Technical tab in the Detail List column.

 Note
For information about personal data that's stored and
processed, see Personal Data in Performance Indicators.

 Note
The following image is an example of this process ow. Exactly how each process ow looks in your system depends on your
data. To view a larger version of this image, hover over it with your mouse, open the context menu, and choose the option to
open the image in a new tab. Adjust the zoom level set in your browser if required.

This is custom documentation. For more information, please visit the SAP Help Portal 192
12/19/2022

Process Flow Stages, Blockers, and Other Information

 Remember
The rst stage in every process ow represents the baseline set of business object instances that were created in the
reference time period. The business object instances that progress to any of the subsequent stages are those instances
from the baseline set that meet the criteria for progression.

Business object instances are included in the baseline set when their creation date is within the reference period. Business
object instances that progress to subsequent phases, however, can be considered based on event dates right up to the date
of data collection.

 Note
The term "average times" referred to in descriptions is referring to the lead times between stages and the average days
taken to reach each stage. It's a generic reference to both time references relating to overall progression.

Stage Description Frequent Description


Blockers/Other
Information

Inspection lots All inspection lots for goods receipt Inspection lots Inspection lots that weren't created
created inspection from manufacturing that were manually created automatically by the SAP system.
created in the reference period. The
creation date is the date on which Inspection lots for Inspection lots for materials that require
the inspection lot record was created. material with detailed documentation. Only for these
required inspection lots does the SAP system store
documentation additional change logs for status or eld
changes.

Inspection lots Inspection lots that were canceled after


canceled creation.

This stage represents additional Inspection lots Inspection lots that require a dedicated
activities related to the previous stage. without required inspection plan but for which a plan
inspection plan isn't yet assigned.

This is custom documentation. For more information, please visit the SAP Help Portal 193
12/19/2022

Stage Description Frequent Description


Blockers/Other
Information

Inspection lots with Inspection lots with a dedicated


inspection plan inspection plan.

This stage represents additional Inspection lots Inspection lots for which there are
activities related to the previous stage. without completed outstanding quantities to be posted from
stock posting quality inspection stock to unrestricted-
use stock.

Inspection lots with Inspection lots for which the lot quantity
inspection stock was posted to inspection stock (and not
directly to unrestricted-use stock) when
the inspection lot was created.

This stage represents additional Inspection lots with Inspection lots for which there are
activities related to the previous stage. outstanding short- outstanding short-term characteristics
term characteristics for processing and completion.

Inspection lots with Inspection lots for which all short-term


completed short- characteristics are completed, allowing a
term characteristics usage decision to be made.

This stage represents additional Inspection lots Inspection lots for which the usage
activities related to the previous stage. without usage decision is missing although
decision and with the inspection should be nished
planned inspection according to plan.
end date in the past

Inspection lots Inspection lots for which the usage


without usage decision is missing, but at least
decision and with at one characteristic had the result
least one con rmed con rmed.
result

Inspection lots Inspection lots for which the usage


without usage decision is missing and the manufacturing
decision for which order is already technically completed.
the manufacturing
order is already
technically
completed

Inspection lots with All inspection lots for which a usage Inspection lots with Inspection lots for which the usage
usage decision taken decision has also been processed. This is rejection as usage decision was to reject the goods receipt.
determined based on the date of the decision
code used for the usage decision.
Inspection lots with Inspection lots for which the SAP system
planned automatic could make an automatic usage decision if
usage decision corresponding prerequisites are met.

Standard Performance Indicators


Get an overview of the standard process performance indicators that are currently available in SAP Signavio Process Insights.

 Note
Some throughput performance indicators also include information about whether documents or items were created
manually. This allows the automation rate to be calculated and these throughput performance indictors to display
This is custom documentation. For more information, please visit the SAP Help Portal 194
12/19/2022
information about throughput and automation rates at the same time. You can identify these performance indicators based
on the Category column of the following table.

Legend for Additional Information column:

BRIM : Relevant for data from SAP Billing and Revenue Innovation Management.

Utilities : Relevant for data from SAP for Utilities (IS-U).

 Tip
Selecting the value driver Reduce Meter Reading to Invoice Cycle Time in the application lets you focus speci cally
on performance indicators relevant for SAP for Utilities.

Performance Indicator Name Correction End-to-End Line of Category Additional


ID Recommendations Process Business Information

KFFI000104 Changes in nancial Finance Finance Changes


documents
Lead to Cash Sales

Source to Pay Sourcing &


Procurement

KFFI000105 Canceled nancial Finance Finance Throughput


line items

KFFI000106 Financial documents Finance Finance Automation


created Rate
Governance
Throughput
Lead to Cash

Source to Pay

KFFI000190 Financial document Finance Finance Master Data


type usage (cross-
company code)

KFFI000191 Company code Finance Finance Master Data


usage in nancial
documents

KFFI000202 Overdue and open Finance Finance Backlog


accounts payable
Source to Pay
items

KFFI000212 Open items without Yes Finance Finance Backlog


any payment
Governance
methods
Source to Pay

KFFI000213 Open items where Yes Finance Finance Backlog


supplier is blocked
Governance
for posting
Source to Pay

KFFI000214 Open items blocked Yes Finance Finance Backlog


for payment
Source to Pay

This is custom documentation. For more information, please visit the SAP Help Portal 195
12/19/2022

Performance Indicator Name Correction End-to-End Line of Category Additional


ID Recommendations Process Business Information

KFFI000215 Open items where Yes Finance Finance Backlog


supplier is blocked
Governance
for payment
Source to Pay

KFFI000216 Open items where Yes Finance Finance Backlog


suppliers are
Source to Pay
missing bank details

KFFI000217 Open items where Yes Finance Finance Backlog


suppliers are
Source to Pay
missing address
information

KFFI000302 Overdue and open Finance Finance Backlog


accounts receivable
Lead to Cash
items

KFFI000310 Open items where Yes Finance Finance Backlog


customer has no
ST-A/PI 01V_731* Lead to Cash Sales
dunning procedure

KFFI000311 Open items where Yes Finance Finance Backlog


customer is blocked
ST-A/PI 01V_731* Lead to Cash Sales
in another dunning
run

KFFI000312 Open items where Yes Finance Finance Backlog


customer is blocked
ST-A/PI 01V_731* Lead to Cash Sales
for dunning

KFFI000313 Open items blocked Yes Finance Finance Backlog


for dunning
ST-A/PI 01V_731* Lead to Cash Sales

KFFI000405 Errors during Finance Finance Exception


payment runs
Source to Pay Sourcing &
Procurement

KFFI000406 Payment runs per Yes Finance Finance Throughput


company code
Source to Pay Sourcing &
Procurement

KFFI000409 Company codes Yes Finance Finance Backlog


without payment
ST-A/PI 01V_731* Source to Pay
runs

KFFI000501 Electronic bank Yes Lead to Cash Finance Backlog


statements not
Source to Pay
completely posted

KFFI000502 Electronic bank Finance Finance Backlog


statement items not
Lead to Cash
completely posted

KFFI000504 Electronic bank Finance Finance Throughput


statements imported
Lead to Cash
per day

This is custom documentation. For more information, please visit the SAP Help Portal 196
12/19/2022

Performance Indicator Name Correction End-to-End Line of Category Additional


ID Recommendations Process Business Information

KFFI000705 Open items in Finance Finance Backlog


general ledger
accounts
(aggregated)

KFFI000706 Open items in goods Finance Finance Backlog


receipt/invoice
Source to Pay Sourcing &
receipt clearing
Procurement
account

KFFI000940 Automation rate: Finance Finance Automation


Supplier invoice Rate
Source to Pay
clearing

KFFI001040 Automation rate: Finance Finance Automation


Customer invoice Rate
Lead to Cash
clearing

KFFI001201 Schedule Manager: Yes Finance Finance Throughput


Runtimes and Status

KFFI001303 Open dispute cases Finance Finance Backlog


with last changed
Lead to Cash
date in the past

KFFI001402 Open promise to pay Yes Finance Finance Backlog


cases with promise
Lead to Cash
to pay date in the
past

KFFI001501 Errors during costing Finance Finance Exception


run

KFFI001502 Errors during cost Finance Finance Exception


calculation with
transaction CK11N

KFFI001601 Errors during WIP Finance Finance Exception


calculation for
Manufacturing
manufacturing orders

KFFI001602 Errors during Yes Finance Finance Exception


variance calculation
for manufacturing
orders

KFFI001603 Errors during Yes Finance Finance Exception


manufacturing order
actual settlement

KFFI001605 Errors during Finance Finance Exception


maintenance/internal
order actual
settlement

KFFI001609 Errors during WBS Finance Finance Exception


element/network
order actual
settlement

This is custom documentation. For more information, please visit the SAP Help Portal 197
12/19/2022

Performance Indicator Name Correction End-to-End Line of Category Additional


ID Recommendations Process Business Information

KFFI001701 Incorrect cost Yes Finance Finance Backlog


calculations from
con rmations

KFFI002003 Overdue purchase Yes Source to Pay Sourcing & Backlog


order commitment Procurement
Finance
items assigned to
Finance
orders

KFFI002004 Overdue purchase Yes Governance Sourcing & Backlog


order commitment Procurement
Source to Pay
items assigned to
Finance
projects Finance

Acquire to
Decommission

KFFI002005 Overdue purchase Yes Lead to Cash Finance Backlog


order commitment
Source to Pay
items assigned to
sales Finance

KFFI002305 Internal orders Finance Finance Backlog


created but not
released

KFFI002306 Internal orders Finance Finance Backlog


released but not
technically
completed

KFFI002308 Changes in internal Finance Finance Changes


orders

KFFI002395 Order type usage in Finance Finance Master Data


internal orders

KFFI002501 Dunning runs per Finance Finance Throughput


company code
Lead to Cash

KFFI002601 Billing documents Finance Finance Throughput BRIM


overdue for
Lead to Cash
convergent invoicing

KFFI002602 Overdue convergent Finance Finance Throughput BRIM


invoicing with locked
Lead to Cash
contract account

KFFI002603 Overdue convergent Finance Finance Throughput BRIM


invoicing with locked
Lead to Cash
provider contract

KFFI002604 Provider contracts Finance Finance Throughput BRIM


locked for invoicing
Lead to Cash

KFFI002605 Billing document Finance Finance Throughput BRIM


items created
Lead to Cash
Billing document
items created

This is custom documentation. For more information, please visit the SAP Help Portal 198
12/19/2022

Performance Indicator Name Correction End-to-End Line of Category Additional


ID Recommendations Process Business Information

KFFI002606 Invoice document Finance Finance Throughput BRIM


items created
Lead to Cash

KIISU00101 Overdue utilities Lead to Cash Finance Backlog Utilities


billing orders with
the status "Billable"

KIISU00102 Overdue utilities Lead to Cash Finance Backlog Utilities


billing orders with
the status "Not
billable"

KIISU00103 Overdue utilities Lead to Cash Finance Backlog Utilities


billing orders without
meter reading
document

KIISU00104 Overdue utilities Lead to Cash Finance Backlog Utilities


billing orders without
logical device

KIISU00201 Overdue utilities Lead to Cash Finance Backlog Utilities


invoicing orders
(billing document)

KIISU00203 Utilities invoicing Lead to Cash Finance Backlog Utilities


orders not released
(billing document)

KIISU00204 Utilities billing Lead to Cash Finance Backlog Utilities


document reversals

KIISU00205 Outsorted utilities Lead to Cash Finance Backlog Utilities


billing documents
released

KIISU00302 Utilities invoices with Lead to Cash Finance Backlog Utilities


overdue print
triggers

KIISU00304 Utilities print Lead to Cash Finance Backlog Utilities


document reversals

KIISU00305 Outsorted utilities Lead to Cash Finance Backlog Utilities


print documents
released

KIISU00306 Utilities print Lead to Cash Finance Backlog Utilities


documents overdue
for release

KIPSM00101 Earmarked funds Finance Finance Throughput


created

KIPSM00102 Earmarked fund Finance Finance Throughput


items created

KIPSM00103 Open and overdue Finance Finance Backlog


earmarked fund
items

This is custom documentation. For more information, please visit the SAP Help Portal 199
12/19/2022

Performance Indicator Name Correction End-to-End Line of Category Additional


ID Recommendations Process Business Information

KIPSM00104 Open earmarked Finance Finance Backlog


fund items

KIPSM00105 Changes to Finance Finance Changes


earmarked funds

KIPSM00106 Blocked earmarked Finance Finance Backlog


fund items

KPCONF0110 Failed goods Yes Plan to Ful ll Manufacturing Exception


movements during
production order
con rmation

KPCONF0120 Failed goods Acquire to Supply Chain Exception


movements during Decommission
network order
Governance
con rmation

KPCONF0130 Failed goods Yes Acquire to Asset Exception


movements during Decommission Management
PM/CS order
Lead to Cash Service
con rmation

KPCONF0140 Failed goods Yes Plan to Ful ll Manufacturing Exception


movements during
process order
con rmation

KPCONF0401 Production order Plan to Ful ll Supply Chain Throughput


con rmations

KPCONF0402 Process order Plan to Ful ll Supply Chain Throughput


con rmations

KPIM000101 Stock level of Yes Plan to Ful ll Supply Chain Backlog


unrestricted-use
stock

KPIM000105 Stock level of sales Yes Lead to Cash Supply Chain Backlog
order stock
Plan to Ful ll

KPIM000106 Stock level of Lead to Cash Supply Chain Backlog


customer
Plan to Ful ll
consignment stock

KPIM000107 Stock level of project Yes Governance Supply Chain Backlog


stock
Plan to Ful ll

KPIM000108 Stock level of Yes Plan to Ful ll Supply Chain Backlog


unrestricted-use
stock (batch level)

KPLE000110 Outbound deliveries Yes Lead to Cash Sales Backlog


overdue for goods
Plan to Ful ll Supply Chain
issue posting

KPLE000111 Inbound deliveries Yes Plan to Ful ll Supply Chain Backlog


overdue for goods
Source to Pay
receipt posting

This is custom documentation. For more information, please visit the SAP Help Portal 200
12/19/2022

Performance Indicator Name Correction End-to-End Line of Category Additional


ID Recommendations Process Business Information

KPLE000120 Inbound deliveries Plan to Ful ll Supply Chain Automation


created Rate
Source to Pay
Throughput

KPLE000121 Outbound deliveries Yes Lead to Cash Supply Chain Automation


created Rate
Plan to Ful ll
Throughput

KPLE000190 Con guration check: Plan to Ful ll Supply Chain Customizing


Document ow Con guration
Source to Pay
update from MM to
LE

KPLE000305 Delivery items Yes Finance Finance Backlog


shipped and overdue
Lead to Cash Sales
for billing

KPMRP00108 Planned orders Yes Plan to Ful ll Manufacturing Backlog


(LA/KD) with nish
Supply Chain
basic date in the
past

KPMRP00109 Overdue planned Lead to Cash Supply Chain Backlog


orders assigned to
Plan to Ful ll Sales
sales

KPMRP00201 MRP area planning Yes Plan to Ful ll Supply Chain Backlog
le - materials
marked for deletion

KPMRP00202 MRP area planning Yes Plan to Ful ll Supply Chain Backlog
le - status does not
allow planning

KPMRP00205 MRP planning le - Yes Plan to Ful ll Supply Chain Backlog


materials marked for
deletion

KPMRP00206 MRP planning le Yes Plan to Ful ll Supply Chain Backlog


materials - status
does not allow
planning

KPPP000101 Production orders Plan to Ful ll Manufacturing Backlog


overdue for release

KPPP000103 Production orders Plan to Ful ll Manufacturing Backlog


overdue for delivery
completed

KPPP000106 Production orders Yes Plan to Ful ll Manufacturing Backlog


overdue for deletion
ag

KPPP000107 Production orders Yes Plan to Ful ll Manufacturing Automation


created Rate

Throughput

This is custom documentation. For more information, please visit the SAP Help Portal 201
12/19/2022

Performance Indicator Name Correction End-to-End Line of Category Additional


ID Recommendations Process Business Information

KPPP000108 Production orders Plan to Ful ll Manufacturing Backlog


released without rst
con rmation

KPPP000111 Production order Plan to Ful ll Manufacturing Backlog


components overdue
for consumption

KPPP000121 Overdue production Plan to Ful ll Manufacturing Backlog


orders assigned to
sales

KPPP000190 Order type usage in Plan to Ful ll Manufacturing Master Data


production orders
(cross-plant)

KPPP000201 Process orders Plan to Ful ll Manufacturing Backlog


overdue for release

KPPP000203 Process orders Plan to Ful ll Manufacturing Backlog


overdue for delivery
completed

KPPP000206 Process orders Yes Plan to Ful ll Manufacturing Backlog


overdue for deletion
ag

KPPP000207 Process orders Yes Plan to Ful ll Manufacturing Automation


created Rate

Throughput

KPPP000208 Process orders Plan to Ful ll Manufacturing Backlog


released without rst
con rmation

KPPP000211 Process order Plan to Ful ll Manufacturing Backlog


components overdue
for consumption

KPPP000222 Overdue process Plan to Ful ll Manufacturing Backlog


orders assigned to
sales

KPPP000290 Order type usage in Plan to Ful ll Manufacturing Master Data


process orders
(cross-plant)

KPPP000409 Materials with MRP Yes Plan to Ful ll Supply Chain Exception
list error messages
Source to Pay

KPPP000410 MRP elements to be Yes Plan to Ful ll Supply Chain Backlog


canceled per
Source to Pay
material

KPPURCH201 Purchase order items Yes Source to Pay Sourcing & Automation
created Procurement Rate

Throughput

This is custom documentation. For more information, please visit the SAP Help Portal 202
12/19/2022

Performance Indicator Name Correction End-to-End Line of Category Additional


ID Recommendations Process Business Information

KPPURCH203 Purchase order items Yes Source to Pay Sourcing & Backlog
open and overdue Procurement

KPPURCH212 Purchase order items Governance Sourcing & Backlog


created after invoice Procurement
Source to Pay

KPPURCH221 Changes in purchase Governance Sourcing & Changes


orders Procurement
Source to Pay

KPPURCH222 Purchase order items Governance Sourcing & Backlog


created without Procurement
Source to Pay
reference to contract

KPPURCH223 Overdue purchase Source to Pay Sourcing & Backlog


order items without Procurement
any con rmation

KPPURCH225 New Open purchase order Source to Pay Sourcing & Backlog
items with overdue Procurement
inbound delivery
items

KPPURCH228 MRP-relevant vendor Source to Pay Sourcing & Backlog


con rmations Procurement
overdue

KPPURCH290 Con guration check: Source to Pay Sourcing & Customizing


Suggest "delivery Procurement Con guration
completed"

KPPURCH298 Purchasing Source to Pay Sourcing & Master Data


document type Procurement
ST-A/PI 01V_731*
usage (cross-
company code)

KPPURCH301 Purchase requisition Source to Pay Sourcing & Automation


items created Procurement Rate

Throughput

KPPURCH303 Purchase requisition Yes Source to Pay Sourcing & Backlog


items open and Procurement
overdue

KPPURCH309 Changes in purchase Source to Pay Sourcing & Changes


requisitions Procurement

KPPURCH404 Supplier invoices Finance Finance Automation


created Rate
Source to Pay
Throughput

KPPURCH409 Blocked supplier Finance Finance Backlog


invoice items with
Source to Pay
overdue FI-AP items

KPPURCH411 Supplier invoices Finance Finance Backlog


with overdue FI-AP
Source to Pay
items

This is custom documentation. For more information, please visit the SAP Help Portal 203
12/19/2022

Performance Indicator Name Correction End-to-End Line of Category Additional


ID Recommendations Process Business Information

KPPURCH412 Changes in supplier Finance Finance Changes


invoices
Source to Pay

KPPURCH413 Canceled supplier Finance Finance Throughput


invoices
Source to Pay

KPPURCH508 Distinct errors during Source to Pay Supply Chain Exception


delivery due runs
(stock transport
orders)

KPSD000133 Sales documents Lead to Cash Sales Automation


created Rate

Throughput

KPSD000190 Sales document type Lead to Cash Sales Master Data


usage (cross-sales
area)

KPSD000201 Sales invoices not Yes Finance Finance Backlog


posted to accounting
Lead to Cash Sales

KPSD000208 Sales invoices with Lead to Cash Sales Backlog


open FI-AR items

KPSD000215 Canceling sales Finance Finance Throughput


invoices
Lead to Cash Sales

KPSD000216 Distinct errors during Finance Finance Exception


billing due runs
Lead to Cash Sales

KPSD000218 Sales billing Yes Lead to Cash Sales Automation


documents created Rate

Throughput

KPSD000293 Billing type usage in Lead to Cash Sales Master Data


sales billing
documents (cross-
sales organization)

KPSD000303 Overdue sales Yes Lead to Cash Sales Backlog


schedule line items

KPSD000304 Schedule lines Lead to Cash Sales Backlog


initially not
con rmed for
requested delivery
date

KPSD000306 Missing elds in Yes Lead to Cash Sales Backlog


incomplete sales
document items

KPSD000307 Rejected sales Lead to Cash Sales Throughput


document items

This is custom documentation. For more information, please visit the SAP Help Portal 204
12/19/2022

Performance Indicator Name Correction End-to-End Line of Category Additional


ID Recommendations Process Business Information

KPSD000319 Billing plan dates not Lead to Cash Sales Backlog


billed and overdue

KPSD000321 Sales document Yes Lead to Cash Sales Backlog


items overdue for
billing

KPSD000323 New Manual condition Lead to Cash Sales Backlog


changes in sales
Requires Activation**
document items

KPSD000324 Changes in sales Yes Lead to Cash Sales Changes


documents

KPSD000326 Distinct errors during Lead to Cash Sales Exception


delivery due runs
(sales)

KPSD000327 Deleted items in Lead to Cash Sales Throughput


sales documents

KWMD000203 Changes to customer Governance Finance Changes


master data
Lead to Cash Sales

KWMD000205 Customer master Yes Governance Finance Master Data


data usage in sales
Lead to Cash Sales
billing documents
(per sales area)

KWMD000206 New Customer master Yes New Governance Finance Master Data
data usage in FI-AR
Lead to Cash Sales
(per company code)

KWMD000207 Customer master Finance Finance Master Data


data usage in FI-AR
Governance Sales
(cross-company
code) Lead to Cash

KWMD000309 Changes to supplier Finance Finance Changes


master data
Governance Sourcing &
Procurement
Source to Pay

KWMD000312 New Supplier master data Yes New Governance Finance Master Data
usage in purchasing
Source to Pay Sourcing &
documents (per
Procurement
purchasing
organization)

KWMD000313 Supplier master data Yes Governance Finance Master Data


usage in FI-AP (per
Source to Pay Sourcing &
company code)
Procurement

KWMD000314 Supplier master data Finance Finance Master Data


usage in FI-AP
Governance Sourcing &
(cross-company
Procurement
code) Source to Pay

This is custom documentation. For more information, please visit the SAP Help Portal 205
12/19/2022

Performance Indicator Name Correction End-to-End Line of Category Additional


ID Recommendations Process Business Information

KWMD000501 Terms of payment Finance Finance Master Data


usage in FI-AP
Source to Pay Sourcing &
invoices (per
Procurement
company code)

KWMD000502 Terms of payment Finance Finance Master Data


usage in FI-AP
Source to Pay Sourcing &
invoices (cross-
Procurement
company code)

KWMD000503 Terms of payment Finance Finance Master Data


usage in FI-AR
Lead to Cash Sourcing &
invoices (per
Procurement
company code)

KWMD000504 Terms of payment Finance Finance Master Data


usage in FI-AR
Lead to Cash Sourcing &
invoices (cross-
Procurement
company code)

KWPM000115 Plant maintenance Acquire to Asset Automation


noti cations created Decommission Management Rate

Throughput

KWPM000116 Customer service Plant to Ful ll Service Automation


noti cations created Rate

Throughput

KWPM000117 Plant maintenance Acquire to Asset Backlog


noti cations open Decommission Management
and overdue

KWPM000118 Customer service Plant to Ful ll Service Backlog


noti cations open
and overdue

KWPM000119 Plant maintenance Acquire to Asset Backlog


noti cations pending Decommission Management

KWPM000120 Customer service Plant to Ful ll Service Backlog


noti cations pending

KWPM000203 Plant maintenance Acquire to Asset Automation


orders created Decommission Management Rate

Throughput

KWPM000204 Customer service Plant to Ful ll Service Automation


orders created Rate

Throughput

KWPM000217 Plant maintenance Yes Acquire to Asset Backlog


orders overdue for Decommission Management
release

KWPM000218 Customer service Yes Plan to Ful ll Service Backlog


orders overdue for
release

This is custom documentation. For more information, please visit the SAP Help Portal 206
12/19/2022

Performance Indicator Name Correction End-to-End Line of Category Additional


ID Recommendations Process Business Information

KWPM000219 Plant maintenance Yes Acquire to Asset Backlog


orders released and Decommission Management
overdue for technical
completion

KWPM000220 Customer service Yes Plan to Ful ll Service Backlog


orders released and
overdue for technical
completion

KWPM000221 Plant maintenance Acquire to Asset Backlog


orders not settled Decommission Management
ST-A/PI 01V_731*
Finance

KWPM000222 Customer service Finance Service Backlog


orders not settled
ST-A/PI 01V_731* Plan to Ful ll

KWPM000290 Order type usage in Acquire to Asset Master Data


PM/CS orders Decommission Management
(cross-plant)
Service

KWQM000101 Inspection lots with Plan to Ful ll Manufacturing Backlog


outstanding
Requires Activation** Source to Pay Sourcing &
quantities
Procurement

Supply Chain

KWQM000102 Inspection lots Acquire to Asset Backlog


without usage Decommission Management
decision
Plan to Ful ll Manufacturing

Source to Pay Sourcing &


Procurement

Supply Chain

KWQM000103 Inspection lots Acquire to Asset Backlog


without inspection Decommission Management
Requires Activation**
completion
Plan to Ful ll Manufacturing

Source to Pay Sourcing &


Procurement

Supply Chain

*This standard performance indicator is only available as of ST-A/PI 01V_731. Upgrading to the latest version is always
recommended. Also ensure you implement the latest version of the relevant SAP Note for your ST-A/PI version as outlined
under Technical Prerequisites in the Administration Guide .

**This performance indicator is not active by default. To collect and display data for this performance indicator, your SAP
Signavio Process Insights administrator needs to activate it in the Administration area of the solution. For more information,
see Monitoring and Con guring Data Collection Runs in the Administration Guide .

Filtering to Identify Root Causes


This is custom documentation. For more information, please visit the SAP Help Portal 207
12/19/2022
Get some general information about how to start identifying root causes of issues identi ed.

Filtering Basics
You can use the ltering option for process ows and standard performance indicators to do a root cause analysis. You do this
by selecting one or more of the available lters for your process ow or standard performance indicator. These lters are
speci c to that performance indicator that you're working with, aren't saved when you log off, and are valid for your user only.

Applying lters helps you to identify if a potential issue is generic or speci c to an organizational unit (such as company code,
plant, sales/purchasing organization), process variant (document type or item category), or even to a customer, vendor, or
material, for example. By selecting different lters, you can potentially identify patterns of organizational units, process
variants, and other entities.

Filtering Logic
When you add lters, the lters are always applied from left to right. This means that if you add a lter for selection and then
select values for that lter, the available lter values for subsequent lters that you add for selection are dynamically adjusted
depending on the lter values you've already selected.

Let's say you add a lter for company code (BURKS), and then select lter values for company codes Germany (001) and France
(002). Your data is ltered using an OR operator, which means only data records with company code Germany (001) or France
(002) are returned. The ltering logic is: (BURKS = 001 OR 002).

Let's say you then add a second lter for document type (BSART), and select lter values for document types A and B. The
resulting data records from the rst lter you set for company code are now ltered further using an AND operator to only
return those records that also have document type A or B. The ltering logic is now: ( (BURKS = 001 OR 002) AND (BSART = A
OR B) ).

You can only see the English descriptions for lter values such as company code if you've maintained these descriptions in your
managed system.

 Note
If you change or add any descriptions in your managed system, it can take up to 30 days until these changes are re ected in
SAP Signavio Process Insights.

Recommended Approach
A recommended approach is to identify organizational units to be analyzed or compare results across organizational units,
process variants, or other entities (on a more granular level, such as customers, vendors, or materials). This helps you identify
potential areas for improvement and go deeper into your root cause analysis.

Once you've identi ed a pattern, you can analyze the root cause for this pattern further.

The list of available lters that you can apply can be extensive depending on the performance indicator. It's also possible that
there isn't one systematic problem causing a backlog, but that there are multiple patterns that you need to identify by
combining different lters.

This is custom documentation. For more information, please visit the SAP Help Portal 208

You might also like