SAP Signavio Insights
SAP Signavio Insights
SAP Signavio Insights
PUBLIC
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.
This is custom documentation. For more information, please visit the SAP Help Portal 1
12/19/2022
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:
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:
How frequently data is collected and what reference period or status applies
Whether your administrator needs to speci cally activate data collection for the performance indicator (if it's not
activated by default)
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.
This is custom documentation. For more information, please visit the SAP Help Portal 2
12/19/2022
This is custom documentation. For more information, please visit the SAP Help Portal 3
12/19/2022
This is custom documentation. For more information, please visit the SAP Help Portal 4
12/19/2022
Related Information
KPI Catalog
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:
ISU_INVOICING_PARTY
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
BRIM : Relevant for data from SAP Billing and Revenue Innovation Management.
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.
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
This is custom documentation. For more information, please visit the SAP Help Portal 6
12/19/2022
This is custom documentation. For more information, please visit the SAP Help Portal 7
12/19/2022
KPPURCH261 Purchase order item Plan to Ful ll Sourcing & Process Progress
creation to invoice Procurement
Source to Pay
receipt creation
This is custom documentation. For more information, please visit the SAP Help Portal 8
12/19/2022
This is custom documentation. For more information, please visit the SAP Help Portal 9
12/19/2022
This is custom documentation. For more information, please visit the SAP Help Portal 10
12/19/2022
*This process ow is only available as of ST-A/PI 01V_731. Upgrading to the latest version is always recommended.
General Information
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.
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.
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
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 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.
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
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 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 .
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
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
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.
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.
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
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.
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.
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.
ST-A/PI 01V_731*
This is custom documentation. For more information, please visit the SAP Help Portal 17
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 .
General Information
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
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.
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
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.
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.
General Information
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.
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
Contracts created All utilities contracts that were created in Contracts locked for Utilities contracts that are locked for
the reference period. billing billing.
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.
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
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
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
This is custom documentation. For more information, please visit the SAP Help Portal 22
12/19/2022
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
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
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.
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.
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 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
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
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
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 27
12/19/2022
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 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
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
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
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.
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
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).
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.
This is custom documentation. For more information, please visit the SAP Help Portal 31
12/19/2022
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
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
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.
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
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).
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.
This is custom documentation. For more information, please visit the SAP Help Portal 34
12/19/2022
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
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
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 36
12/19/2022
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.
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.
This is custom documentation. For more information, please visit the SAP Help Portal 37
12/19/2022
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.
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.
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.
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.
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 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
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.
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.
This is custom documentation. For more information, please visit the SAP Help Portal 41
12/19/2022
General Information
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
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.
This is custom documentation. For more information, please visit the SAP Help Portal 43
12/19/2022
This is custom documentation. For more information, please visit the SAP Help Portal 44
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 .
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.
General Information
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.
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.
This is custom documentation. For more information, please visit the SAP Help Portal 47
12/19/2022
This is custom documentation. For more information, please visit the SAP Help Portal 48
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 .
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.
General Information
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.
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.
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 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
This is custom documentation. For more information, please visit the SAP Help Portal 51
12/19/2022
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 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.
General Information
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.
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.
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
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 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
This is custom documentation. For more information, please visit the SAP Help Portal 54
12/19/2022
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
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 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 with Delivery items that are entirely blocked for
header delivery delivery because the Delivery block
block (document header) indicator is set
General Information
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.
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.
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.
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.
This is custom documentation. For more information, please visit the SAP Help Portal 57
12/19/2022
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
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
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 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
General Information
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
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.
This is custom documentation. For more information, please visit the SAP Help Portal 60
12/19/2022
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.
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
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
This is custom documentation. For more information, please visit the SAP Help Portal 61
12/19/2022
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
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
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
General Information
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
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.
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.
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
This is custom documentation. For more information, please visit the SAP Help Portal 64
12/19/2022
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 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 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.
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
This is custom documentation. For more information, please visit the SAP Help Portal 65
12/19/2022
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:
General Information
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.
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 67
12/19/2022
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 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 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 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
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
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
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.
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
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 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.
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
This is custom documentation. For more information, please visit the SAP Help Portal 71
12/19/2022
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.
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.
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.
This is custom documentation. For more information, please visit the SAP Help Portal 72
12/19/2022
General Information
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
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.
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.
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
This is custom documentation. For more information, please visit the SAP Help Portal 74
12/19/2022
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 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 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.
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
This is custom documentation. For more information, please visit the SAP Help Portal 75
12/19/2022
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:
General Information
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.
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 77
12/19/2022
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 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 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
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
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
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
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.
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
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 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.
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.
This is custom documentation. For more information, please visit the SAP Help Portal 81
12/19/2022
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.
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.
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.
This is custom documentation. For more information, please visit the SAP Help Portal 82
12/19/2022
General Information
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
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.
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.
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
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.
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 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.
General Information
This is custom documentation. For more information, please visit the SAP Help Portal 85
12/19/2022
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.
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.
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
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 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.
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
This is custom documentation. For more information, please visit the SAP Help Portal 87
12/19/2022
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 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.
General Information
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.
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.
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
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
General Information
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.
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.
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
This stage represents additional Purchase order Purchase order items for which a block
activities related to the previous stage. items blocked indicator set.
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.
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
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
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.
This is custom documentation. For more information, please visit the SAP Help Portal 93
12/19/2022
General Information
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.
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.
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
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
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)
This is custom documentation. For more information, please visit the SAP Help Portal 95
12/19/2022
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
General Information
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.
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.
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
This is custom documentation. For more information, please visit the SAP Help Portal 97
12/19/2022
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.
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.
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
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.
General Information
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.
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 100
12/19/2022
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.
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.
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
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
This is custom documentation. For more information, please visit the SAP Help Portal 101
12/19/2022
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.
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
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.
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.
This is custom documentation. For more information, please visit the SAP Help Portal 102
12/19/2022
General Information
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
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.
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
This is custom documentation. For more information, please visit the SAP Help Portal 104
12/19/2022
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
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
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
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
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
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
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.
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.
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.
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.
ST-A/PI 01V_731*
This is custom documentation. For more information, please visit the SAP Help Portal 108
12/19/2022
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.
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.
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*
This is custom documentation. For more information, please visit the SAP Help Portal 109
12/19/2022
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.
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.
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 .
General Information
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
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.
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
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
General Information
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
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.
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
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.
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.
This is custom documentation. For more information, please visit the SAP Help Portal 115
12/19/2022
General Information
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
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.
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
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.
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
This is custom documentation. For more information, please visit the SAP Help Portal 118
12/19/2022
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.
General Information
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.
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 120
12/19/2022
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
This stage represents additional Scheduling Scheduling agreement items for which a
activities related to the previous stage. agreement items deletion indicator is set.
deleted
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
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
This is custom documentation. For more information, please visit the SAP Help Portal 121
12/19/2022
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.
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.
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
General Information
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.
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
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
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.
This stage represents additional Quantity contract Quantity contract items for which a
activities related to the previous stage. items deleted deletion 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
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.
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
General Information
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
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.
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
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
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.
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.
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.
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.
General Information
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.
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.
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
This stage represents additional Sales billing Sales billing documents that have a
activities related to the previous stage. documents canceled cancelation indicator
This is custom documentation. For more information, please visit the SAP Help Portal 129
12/19/2022
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
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
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
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
* 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.
General Information
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.
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
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
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
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
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
Note
This information requires change logs
to be available that might already have
been deleted in the system
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
General Information
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.
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.
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
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
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 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
General Information
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.
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.
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
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
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.
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
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.
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.
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
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
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.
General Information
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.
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
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
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.
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.
General Information
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.
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 146
12/19/2022
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 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
This is custom documentation. For more information, please visit the SAP Help Portal 147
12/19/2022
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.
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.
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.
General Information
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:
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
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.
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.
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
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 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.
General Information
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.
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.
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
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
This is custom documentation. For more information, please visit the SAP Help Portal 153
12/19/2022
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
General Information
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
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.
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
This is custom documentation. For more information, please visit the SAP Help Portal 155
12/19/2022
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"
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.
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
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
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
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
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.
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
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
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
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
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.
This is custom documentation. For more information, please visit the SAP Help Portal 159
12/19/2022
General Information
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
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.
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
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.
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.
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.
General Information
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.
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.
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
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
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
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
General Information
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.
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 166
12/19/2022
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
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
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
This is custom documentation. For more information, please visit the SAP Help Portal 167
12/19/2022
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.
General Information
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
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.
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
This is custom documentation. For more information, please visit the SAP Help Portal 169
12/19/2022
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 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
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
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
General Information
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
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.
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
This is custom documentation. For more information, please visit the SAP Help Portal 172
12/19/2022
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 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
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.
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.
General Information
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.
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.
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 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
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.
General Information
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
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.
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
This is custom documentation. For more information, please visit the SAP Help Portal 177
12/19/2022
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 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.
General Information
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.
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.
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
This is custom documentation. For more information, please visit the SAP Help Portal 179
12/19/2022
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 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.
General Information
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.
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.
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
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 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 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 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
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
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
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.
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.
This is custom documentation. For more information, please visit the SAP Help Portal 184
12/19/2022
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 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.
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
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
This is custom documentation. For more information, please visit the SAP Help Portal 185
12/19/2022
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.
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
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.
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.
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.
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 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.
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
This is custom documentation. For more information, please visit the SAP Help Portal 188
12/19/2022
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
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.
General Information
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.
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.
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.
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.
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.
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 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
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.
General Information
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
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.
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.
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
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.
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 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.
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.
BRIM : Relevant for data from SAP Billing and Revenue Innovation Management.
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.
Source to Pay
This is custom documentation. For more information, please visit the SAP Help Portal 195
12/19/2022
This is custom documentation. For more information, please visit the SAP Help Portal 196
12/19/2022
This is custom documentation. For more information, please visit the SAP Help Portal 197
12/19/2022
Acquire to
Decommission
This is custom documentation. For more information, please visit the SAP Help Portal 198
12/19/2022
This is custom documentation. For more information, please visit the SAP Help Portal 199
12/19/2022
KPIM000105 Stock level of sales Yes Lead to Cash Supply Chain Backlog
order stock
Plan to Ful ll
This is custom documentation. For more information, please visit the SAP Help Portal 200
12/19/2022
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
Throughput
This is custom documentation. For more information, please visit the SAP Help Portal 201
12/19/2022
Throughput
KPPP000409 Materials with MRP Yes Plan to Ful ll Supply Chain Exception
list error messages
Source to Pay
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
KPPURCH203 Purchase order items Yes Source to Pay Sourcing & Backlog
open and overdue Procurement
KPPURCH225 New Open purchase order Source to Pay Sourcing & Backlog
items with overdue Procurement
inbound delivery
items
Throughput
This is custom documentation. For more information, please visit the SAP Help Portal 203
12/19/2022
Throughput
Throughput
This is custom documentation. For more information, please visit the SAP Help Portal 204
12/19/2022
KWMD000206 New Customer master Yes New Governance Finance Master Data
data usage in FI-AR
Lead to Cash Sales
(per company code)
KWMD000312 New Supplier master data Yes New Governance Finance Master Data
usage in purchasing
Source to Pay Sourcing &
documents (per
Procurement
purchasing
organization)
This is custom documentation. For more information, please visit the SAP Help Portal 205
12/19/2022
Throughput
Throughput
Throughput
Throughput
This is custom documentation. For more information, please visit the SAP Help Portal 206
12/19/2022
Supply Chain
Supply Chain
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 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