Out-Of-The-Box Business Process

Analytics Key Figure Measures in SAP

Earlywatch Alert

------------ User Documentation ------------

“Business Key Figures”
Document date : 29th January 2016 (enhances V1.2 from 31th August 2015)
Document classification: Customer

News in document
13th May 2015 First document version

31th August 2015 - “Appendix – Obstacles” added

- Prerequisites added (SAP Note 2196109, role SAP_MANAGED_BPOANA_DIS, ST-
A/PI Version ‘R’ SP02)
- “Appendix – Available key figures” table showing the amount of key figures per
business process added
- Graphic showing Asian letters removed

29th January 2016 Added “Appendix – Troubleshooting”

Contents
1 Prerequisites .................................................................................................................................... 3
2 Enablement ..................................................................................................................................... 3
3 Configuration in SAP Solution Manager Work Center “Solution Manager Configuration” ................. 4
3.1 How to reach that work center? ................................................................................................ 4
3.2 What to do in the SAP Earlywatch Alert content configuration? ................................................ 5
4 Content............................................................................................................................................ 6
4.1 Data collected ........................................................................................................................... 6
4.2 Information shown in report ..................................................................................................... 7
4.3 Information shown in session .................................................................................................... 7
5 FAQ – Frequently asked questions ................................................................................................... 8
6 Appendix – Further information ....................................................................................................... 9
6.1 SAP Note Reference 1257308 - “FAQ: Verwendung des EarlyWatch Alerts“............................... 9
6.2 Help in SAP Support Network .................................................................................................... 9
6.3 Online Help for SAP Earlywatch Alert content configuration for BPA content ............................ 9
7 Appendix – Available key figures .................................................................................................... 10
8 Appendix – Obstacles ..................................................................................................................... 12
9 Appendix – Troubleshooting .......................................................................................................... 13
1 Prerequisites
I. Managed system: Has to be an ERP like system with logistics business data as key figures
mainly concentrate on improvement potential in ERP like logistics.
II. Managed system: Correct authorization for data collection in SDCCN TASK PROCESSOR
(e.g. SAP_MANAGED_BPOANA_DIS)
III. SAP Solution Manager: Service delivery framework needs to have the most up to date
version (see service content update, AGS_UPDATE), at least ST-SER *_2010_1 SP26.
IV. SAP Solution Manager: Service platform framework (ST 710) needs version SP12 at
least.
V. SAP Solution Manager: Make sure SAP Note 2196109 “DSVAS: Session customizing not
pushed to managed system” is implemented
VI. Both systems: Service software framework needs version (ST-A/PI) 01R_* SP02.
VII. SAP EWA needs to be configured as normal.
VIII. BPA content needs to be allowed according to configuration (“BPA ACTIVE” [->]).

2 Enablement
The following four phases can be categorized.

Phase A: Configure SAP EWA for BPA key figure content [->].
Phase B: Data collection is triggered asynchronously with next SAP EWA processing.
Phase C: BPA key figure data is shown in the following SAP EWA.
Phase D: BPA key figures are always collected in periods according to the settings (“Frequency in
Month” [->]) and shown in the following week.
3 Configuration in SAP Solution Manager Work Center “Solution
Manager Configuration”

3.1 How to reach that work center?

I. Transaction SOLMAN_WORKCENTER
II. Either directly choosing register tab “Solution Manager Configuration” or via tab
“SAP Solution Manager Administration” and “Related Links” / “Configuration” /
“Solution Manager Configuration”.
III. In “Solution Manager Configuration” choose “Earlywatch Alert Management” / Step
“5.2”.
3.2 What to do in the SAP Earlywatch Alert content configuration?
I. Choose solution that contains the system.
II. Set “BPA active” for the relevant system.
III. Set “Frequency in Month” for the relevant system.
4 Content

4.1 Data collected

The following structure is used for transferring the data from managed system to SAP Solution
Manager.

Fieldname Position Size Type Description

METRIC 1 12 Char Technical key figure ID
OBJ_ID 2 8 Char Object ID describing the meaning of the data, like organizations or
document types
FIELD01 3 12 Char Collected data ID
DESCR01 4 34 Char Collected data description
DESCR01_HEX 5 66 Char Collected data description (hex decimal)
FIELD02 6 9 Char Collected data ID
DESCR02 7 9 Char Collected data description
DESCR02_HEX 8 13 Char Collected data description (hex decimal)
FIELD03 9 9 Char Collected data ID
DESCR03 10 9 Char Collected data description
DESCR03_HEX 11 13 Char Collected data description (hex decimal)
FIELD04 12 9 Char Collected data ID
DESCR04 13 9 Char Collected data description
DESCR04_HEX 14 13 Char Collected data description (hex decimal)
MEASURE 15 9 Integer Value of measure
PERCENT 16 9 Packed Value of measure in percentage
Num
4.2 Information shown in report
In the report, there is some general information on the subject itself and also a rating and a findings
description for each collected and evaluated key figure.

You can find a sample report here.

4.3 Information shown in session

In the session, there is additional data available regarding top ten organizational units and top ten
document types for each key figure.

Tab “Meta Data” ID 11 shows the time of last data collection. That means the SAP EWA of the week
after that date is the one that should contain the key figure data.
5 FAQ – Frequently asked questions

(1) Is the age distribution currently part of the SAP EWA?

No, not yet. This information is available in the SAP GSS BPA&I (SAP Service Marketplace &
SAP Support Portal) – Guided Self Service Business Process Analysis & Improvement.
(2) Are the top ten oldest and youngest documents shown in SAP EWA?
No, not yet. This information is available in the SAP GSS BPA&I (SAP Service Marketplace &
SAP Support Portal) – Guided Self Service Business Process Analysis & Improvement.
(3) Where can I change the managed system client of the data collected?
Data is collected according to the SDCCN data collection settings. SDCCN task processor
defines the relevant client.
(4) Are more than those key figures available?
Yes, there are many more out-of-the-box key figures available (SAP Service Marketplace &
SAP Support Portal).
6 Appendix – Further information

6.1 SAP Note Reference 1257308 - “FAQ: Verwendung des EarlyWatch

Alerts“
“Business Key Figures
The SAP EarlyWatch Alert report chapter Business Key Figures is optional for ERP-like
systems and can be configured in Work Center Solution Manager Configuration in the
scenario EarlyWatch Alert Management step Configure EWA Content. You can find a sample
report here.”

6.2 Help in SAP Support Network

https://support.sap.com/support-programs-services/services/earlywatch-alert/documentation.html

6.3 Online Help for SAP Earlywatch Alert content configuration for BPA
content

Scope

In this step, you can activate the chapter „Business Key Figures“ in your SAP EarlyWatch Alert Report
for ERP systems. You can find an example of this chapter in the Media Library of SAP EarlyWatch
Alert in the SAP Support Portal (https://service.sap.com/ewa).

The Business Process Analysis includes the collection and pre-evaluation of business KPIs that can
indicate improvement potential for your business processes. Example KPIs are: (1) Number of
deliveries with overdue invoices, and (2) Number of overdue purchase order items.

The data collection is asynchronous. When you activate this feature, data collection will be triggered
by the next EWA data collection. The data will then be available with the following EWA (normally
one week later).

Background

The data is collected in a separate background job, BPMON_*, in the managed system, and is
scheduled in parallel to the SDCCN data collection job. The runtime of the job depends on the
amount of business data in your ERP system, so monitor the job, especially the first time it runs.

Default settings

The business-specific analyses are not active, per default. If the analysis is activated, the default data
collection frequency is every three months.
7 Appendix – Available key figures
Table below shows the available key figures by business process and key figure type.

Related Business Process Key figure TP Key figure BL Key figure LT Total

Warehouse Management 3 3 6
Replenishment 2 3 5
Repetitive Manufacturing 0 5 5
Procure To Pay 4 7 11
Plant Maintenance 2 4 6
Plan To Produce 3 12 15
Order To Cash 3 12 1 16
Finance 0 7 1 8
Total 17 53 2 72

Related Business Process Key figure Key figure type*

Warehouse Management Inbound Transfer Order Items created TP
Warehouse Management Inbound Transfer Order Items open BL
Warehouse Management Outbound Transfer Order Items created TP
Warehouse Management Outbound Transfer Order Items open BL
Warehouse Management Transfer Requirement Items created TP
Warehouse Management Transfer Requirement Items open BL

Related Business Process Key figure Key figure type*

Replenishment Outbound Deliveries created TP
Replenishment Overdue Outbound Deliveries BL
Replenishment Overdue Stock Transport Order Items w/o Outb. Del. Compl. BL
Replenishment Overdue Stock Transport Order Schedule Lines BL
Replenishment Stock Transport Order Items created TP

Related Business Process Key figure Key figure type*

Repetitive Manufacturing Failed Goods Movements (Cumulated records) BL
Repetitive Manufacturing Failed Goods Movements (Single records) BL
Repetitive Manufacturing Firmed Planned Orders (PE) in the past BL
Repetitive Manufacturing Unfirmed Planned Orders (PE) in the past BL
Repetitive Manufacturing Unprocessed Goods Movements BL

Related Business Process Key figure Key figure type*

Procure To Pay Blocked invoices for payment BL
Procure To Pay Inbound Deliveries created TP
Procure To Pay Open Purchase Order Items BL
Procure To Pay Overdue Inbound Deliveries BL
Procure To Pay Overdue PO items BL
Procure To Pay Overdue Purchase Requisition Items BL
Procure To Pay Planned Orders with Planned Opening Date in the past BL
Procure To Pay Plauf w. Opening Date in Offset Period (next 7days) TP
Procure To Pay PO items TP
Procure To Pay Purchase Order Items without Final Invoice Indicator BL
Procure To Pay Purchase Requisition Items created TP
 Related Business Process Key figure Key figure type*
Plant Maintenance Failed goods movements BL
Plant Maintenance Notifications created TP
Plant Maintenance Overdue Notifications BL
Plant Maintenance Work Orders created TP
Plant Maintenance Work Orders in phase created BL
Plant Maintenance Work Orders in phase released BL

Related Business Process Key figure Key figure type*

Plan To Produce Failed costing: Production Orders BL
Plan To Produce Failed goods movement BL
Plan To Produce Failed goods movements BL
Plan To Produce Planned orders (inhouse production) TP
Plan To Produce Planned Orders with Planned Opening Date in the past BL
Plan To Produce Process Orders created (last 90 days) TP
Plan To Produce Process Orders overdue for Del. Ind. and not Closed BL
Plan To Produce Process Orders overdue for Delivery Completed BL
Plan To Produce Process Orders overdue for release BL
Plan To Produce Process Orders released without First Confirmation BL
Plan To Produce Production Orders created (last 90 days) TP
Plan To Produce Production Orders overdue for Del. Ind. and not Closed BL
Plan To Produce Production Orders overdue for Delivery Completed BL
Plan To Produce Production Orders overdue for Release BL
Plan To Produce Production Orders released without First Confirmation BL

Related Business Process Key figure Key figure type*

Order To Cash Credit Memo Requests BL
Order To Cash Deliveries with overdue invoices BL
Order To Cash Invoices created TP
Order To Cash Invoices not posted to FI BL
Order To Cash LT: Delivery Item PGI -> INV LT
Order To Cash Missing fields in incomplete sales order items BL
Order To Cash Orders (GI in the past but not delivered) BL
Order To Cash Orders billed not delivered BL
Order To Cash Orders not billed (Order related billing) BL
Order To Cash Outbound Deliveries created TP
Order To Cash Overdue Outbound Deliveries BL
Order To Cash Percentage of SL items initially not confirmed BL
Order To Cash Return Order BL
Order To Cash Return Order Items BL
Order To Cash Sales Order Schedule Line Items overdue BL
Order To Cash Sales Orders TP

Related Business Process Key figure Key figure type*

Finance Bank Statement Items not completed BL
Finance Blocked items FI-AP for payment (cash disc. loss) BL
Finance Early Payments FI-AP (before cash discount 1) BL
Finance Lockbox Items not completely posted BL
Finance LT: Invoice Item -> Clearing LT
Finance MM Invoices in Ref. Per. with different Paym Terms BL
Finance Overdue customer payments (actual fiscal year) BL
Finance SD Invoice in Ref.Per. with different Payment Terms BL

* Key figure can be of type throughput (TP), backlog (BL) and lead time (LT)
8 Appendix – Obstacles

(1) No data is collected even though collection job (“BPMON_RA_[SID]_[CLIENT]_[YYYYMMDD]”)

runs successful and in data collection processing time per key figure is very fast.

 (A) Check authorization (e.g. SAP_MANAGED_BPOANA_DIS) for data collection in SDCCN TASK
PROCESSOR (user of background job “/BDL/TASK_PROCESSOR”) in [Managed System].

(2) No configuration data is transferred to the [Managed System].

 (A) ST-A/PI Version R '00' has to be avoided (update to ST-A/PI Version R '02')
 (B) Check for SAP Note 2196109 “DSVAS: Session customizing not pushed to managed system” in
[SAP Solution Manager]
9 Appendix – Troubleshooting
The scenarios in SAP EWA Business Key Figure (BKF) chapter can be divided into the following five
cases.

(1) No Customizing in SAP Solution Manager System: The customizing is not yet configured in
customer SAP Solution Manager system (e.g. SSM).
(2) No Customizing in Managed System: The customizing is correctly configured in SAP Solution
Manager system (e.g. SSM) but customizing is not available in customer Managed System (e.g. PRD)
(3) No Data Found in SAP EWA session: Customizing is complete in both above mentioned systems
but no data was collected.
(4) No Data is allowed to be displayed: Data was correctly collected and is available for SAP EWA
session but "Business Key Figures" chapter is missing in report and not filled in the session.
(5) Not all data is displayed: For chapter "Business Key Figures" data seems to be missing in SAP EWA
session.

For issue analysis we use the session check "Business Process Analytics - Key Figures in EarlyWatch
Alert"
Here we focus on the first ("Customizing Settings") and second ("Meta Data") register tab.

Register Tab "Customizing Settings":

Register Tab "Meta Data":

Case Differentiation

Case (1) "Customizing Settings" contains value: SPACE for ID 01. ⇒ Please configure chapter
usage in Work Center SAP Solution Manager Configuration.

Case (2) "Meta Data" contains value: "No customizing found" for ID 11. Please verify ST-A/PI
version in SAP Solution Manager and Managed System (use Version R SP00, use SP02) and
SAP Note 2196109 for both systems. ⇒ Implement missing software components or / and SAP
Notes and change configuration (e.g. "Frequency in month" back and forth) to trigger customizing
transport from SAP Solution Manager to Managed System. Verify after next data collection cycle
as configured in Work Center SAP Solution Manager Configuration.

Case (3a) "Meta Data" contains value: "No data found" for ID 11. ⇒ The 1st SAP EWA after
configuration triggers the data collection. The 2nd SAP EWA (normally following week) fetches the
data and presents it.

Case (3b) "Meta Data" contains value: "No data found" or "Date of BPA..." for ID 11. Please add
the necessary authorization (e.g. SAP_MANAGED_BPOANA_DIS via copy to Z*) to the user that
runs the SDCCN Task Processor (normally BG Job /BDL/TASK_PROCESSOR) in managed
system (e.g. PRD). Remember: Generated an authorization profile from the role! ⇒ Verify after
next data collection cycle as configured in Work Center SAP Solution Manager Configuration.

Case (4) "Meta Data" contains value: "Date of BPA..." for ID 11. Similiar to POINT (1), a change
might have happened to the configuration effecting that Business Key Figures chapter is not
active any longer for the current managed system. ⇒ Reactivate the configuration for that
system.

Case (5a) In some occasions it may be that not all possible key figures were collected during
data collection and so only a few key figures from total possible ones are shown in the report. ⇒
Here it is important to know that additional customizing is shipped (if RFC destination is correctly
found) from SAP Solution Manager to Managed System in those cases. As a result the full key
figure set will be collected within the next data collection cycle.

Case (5b) Individual issue analysis is required here. ⇒ Please open an incident in component
SV-SMG-SER-EWA indicating that "Business Key Figures chapter in SAP EWA needs to be
analyzed and describing the problem for finding and reproducing it.
In general please note that the "Frequency in month" is decisive for when the
data collection does happen in managed system. That means when data
collection ran and no data was shipped to the session then is it necessary to
wait until next data collection run is scheduled. That is last data collection run
plus additional the time specified for next data collection by "Frequency in
month" parameter.

For first starts it might be helpful to set the "Frequency in month" to 1

(meaning one month) or 0 (meaning one week).