configuration and use of smart business for sap master data governance

Author: Dirk Riemer 28.05.2014

Configuration and Use of Smart Business for SAP Master Data Governance


Smart Business for SAP Master Data Governance 7.0 Feature Pack

Content:

1. General Information ....................................................................................................... 5

1.1 Business Use Case and Overview ............................................................................................................ 5

1.2 User Benefits ............................................................................................................................................... 5

1.3 Existing MDG Analytics Application (Available Since MDG 6.0 EhP6) ................................................. 5

2. General Information and System Setup ....................................................................... 6

2.1 General Information .................................................................................................................................... 7

2.2 Technical Prerequisites .............................................................................................................................. 7

2.2.1 Component for Customer Messages ....................................................................................................... 7

2.2.2 SAP Master Data Governance ................................................................................................................. 7

2.2.3 SAP HANA ............................................................................................................................................... 7

2.2.4 SAP Smart Business ................................................................................................................................ 7

2.3 Required User Types .................................................................................................................................. 7

2.3.1 MDG ABAP Backend User ....................................................................................................................... 8

2.3.2 User for Two-Way Connection between the MDG ABAP Backend and the HANA Database ................ 8

2.3.3 Users and Roles for SAP Smart Business ............................................................................................... 8

2.4 Database Schema / Required Database Tables ....................................................................................... 9

2.5 Database Connection ............................................................................................................................... 10

2.6 SAP LT Replication ................................................................................................................................... 11

3. Generation of HANA Content ...................................................................................... 11

3.1 General Concept ....................................................................................................................................... 11

3.1.1 HANA Private Views ............................................................................................................................... 11

3.1.2 HANA Reuse Views ............................................................................................................................... 11

3.1.3 HANA Query Views ................................................................................................................................ 16

3.1.4 OData Services ...................................................................................................................................... 18

3.2 How To Generate HANA content ............................................................................................................. 18

3.2.1 Running the HANA Content Generator Report ...................................................................................... 19

3.2.2 Outcome of View Regeneration ............................................................................................................. 19

3.2.3 Troubleshooting for View Generation Process ...................................................................................... 19

4. Detailed Description KPIs ............................................................................................ 20

Summary ......................................................................................................................................................... 20

4.1 Erroneous Requests ................................................................................................................................. 20

4.1.1 Description ............................................................................................................................................. 20

4.1.2 Time-Independent .................................................................................................................................. 21

4.2 Finally Approved Requests ...................................................................................................................... 21



4.2.1 Description ............................................................................................................................................. 21


4.2.3 Time-Dependent ..................................................................................................................................... 22

4.3 Finally Rejected Requests ....................................................................................................................... 23

4.3.1 Description ............................................................................................................................................. 23


4.3.3 Time-Dependent ..................................................................................................................................... 23

4.4 Open Change Requests ........................................................................................................................... 25

4.4.1 Description ............................................................................................................................................. 25


4.4.3 Time-Dependent ..................................................................................................................................... 25

4.5 Total Change Requests ............................................................................................................................ 26

4.5.1 Description ............................................................................................................................................. 26


4.5.3 Time-Dependent ..................................................................................................................................... 26

4.6 Average Delay Time .................................................................................................................................. 27

4.6.1 Description ............................................................................................................................................. 27


4.6.3 Time-Dependent ..................................................................................................................................... 28

4.7 Processing Time Exceeded ..................................................................................................................... 30

4.7.1 Description ............................................................................................................................................. 30


4.7.3 Time-Dependent ..................................................................................................................................... 30

4.8 Average Processing Time ........................................................................................................................ 32

4.8.1 Description ............................................................................................................................................. 32


4.8.3 Time-Dependent ..................................................................................................................................... 33

4.9 Long-Running Requests (Finalized) ....................................................................................................... 34

4.9.1 Description ............................................................................................................................................. 34


4.9.3 Time-Dependent ..................................................................................................................................... 35

4.10 Long-Running Requests (Open) ...................................................................................................... 36

4.10.1 Description ...................................................................................................................................... 36

4.10.2 Time-Independent ........................................................................................................................... 36

4.10.3 Time-Dependent ............................................................................................................................. 37

4.11 Overdue .............................................................................................................................................. 38

4.11.1 Description ...................................................................................................................................... 38


4.11.3 Time-Dependent ............................................................................................................................. 38

4.12 Potentially Overdue .......................................................................................................................... 39

4.12.1 Description ...................................................................................................................................... 39




4.12.3 Time-Dependent ............................................................................................................................. 40

4.13 On Time .............................................................................................................................................. 41

4.13.1 Description ...................................................................................................................................... 41


4.13.3 Time-Dependent ............................................................................................................................. 41

4.14 Change Requests without Due Date/SLA ....................................................................................... 43

4.14.1 Description ...................................................................................................................................... 43


4.14.3 Time-Dependent ............................................................................................................................. 44

5. Advanced Topics .......................................................................................................... 45

5.1.1 Client Handling ....................................................................................................................................... 45

5.1.2 Authorization Concept ............................................................................................................................ 45

5.1.3 Extensibility ............................................................................................................................................ 45

5.1.4 Language Dependency .......................................................................................................................... 46

5.1.5 FAQ / Tips & Tricks ................................................................................................................................ 46

6. Defining a Tile in SAP Smart Business (Step by Step) ............................................. 46

6.1 Create KPI .................................................................................................................................................. 46

6.2 Add New Variant ........................................................................................................................................ 47

6.3 Add Evaluation .......................................................................................................................................... 47

6.4 Search and Activate KPI Tile ................................................................................................................... 48

6.5 Create Visualizations ................................................................................................................................ 48

6.6 Add KPI Tile ............................................................................................................................................... 49

6.7 Check KPI Tile ........................................................................................................................................... 49



1. General Information

1.1 Business Use Case and Overview

SAP Smart Business applications provide insight into the real-time operations of your business by collecting and displaying KPIs directly in your browser. To do this, SAP Smart Business combines the data and analytical power of SAP HANA with the integration and the interface components of SAP Business Suite. To enable the implementation of SAP Smart Business applications in SAP Master Data Governance, this guide describes the tasks and concepts necessary for initial setup and configuration of all components in the SAP Smart Business system landscape.

For MDG, Smart Business Tiles do not run out of the box, because MDG uses generated database tables. Therefore, the customer must generate HANA content. This document guides you through the prerequisites and steps to configure Smart Business Content for MDG.

You can only enable the dashboard for SAP Smart Business for Master Data Governance if the system landscape includes the following:

SAP Master Data Governance 7.0 including SP02 (Feature Pack) on SAP ERP 6.0 (SAP Enhancement Package 7)

SAP NetWeaver 7.4 with a SAP HANA database (installed or side-by-side).

A dashboard for the MDG governance process and for the master data owner allows the following:

Monitoring of KPIs, SLAs, and alerts to identify deviations in process with corresponding follow-up actions to solve issues

Measurement of service quality through on-spot performance insights

Real-time drill down capabilities to analyze data, to trigger tasks, and to trigger collaboration

Easy creation of ad-hoc reports related to process quality and request volumes

1.2 User Benefits

Optimization of master data governance processes to create data efficiently, timely and in high quality by

Identifying process issues in large amounts of information in real time

Collaboration with the relevant and responsible person

Access to data using different devices (desktop, pad)

Systematic analysis of SLA failures

1.3 Existing MDG Analytics Application (Available Since MDG 6.0 EhP6)

With MDG 6.0 EHP6, SAP supports BI Content; reports and functions that analyze how effectively change requests are processed in your organization.

You can analyze change requests from the following perspectives:

Processing times

For example, display a graphic indicating what proportion of change requests violate Service Level Agreements.

Statuses

For example, view a graphic indicating what proportion of change requests are in process.

Change requests involving you.

You can also turn insight into action.



MDG comes with a small set of BI queries that support the visual analysis and overall monitoring of the change requests. They are included in two Web Dynpro Applications (List View) and one dashboard which is based upon Xcelsius. Therefore, a BI Java Server and a browser with flash plug-in is are the prerequisites to access the information. MDG Analytics is based on operational analytics in ECC. The Infoprovider is an ODP (Operation Data Provider) which is located in the ECC system and not in BW.

General

The process is more visible. Statistics and graphics allow you to identify and fix gaps in the process, bottlenecks, and errors. You can navigate directly to problematic change requests and fix the problems.

Processing Times

You can detect peak and off-peak times during the processing of change requests. You can compare processing times to SLAs and identify which change requests meet or exceed a specified due date. You can also measure how long it takes to process change requests, both by change request type and by data model.

Statuses

You can identify the change request types that are processed quickly and the ones that are processed slowly. You can access summaries of the statuses of change requests (for example, final rejected, final approved, created). You can also analyze why change requests of a particular status include errors or get rejected.

2. General Information and System Setup

HANA-based analytics provide direct access to SAP business data either using standard SQL or using OData. Business data are exposed through the Virtual Data Model, which consists of understandable database views derived by direct access to database tables of the business suite system.

These views can be consumed directly by rich client UIs (such as HTML5, SAP Business Objects, Excel, and so on) without any additional software layer (for example, an ABAP application system) in between (two-tier architecture).

HANA-based Analytics at Business Suite provides HANA views for analytical purposes based on the Business Suite data model. In the beginning, the views are executed on a HANA database that installed side-by-side with a Business Suite backend system (Replication Scenario). Once Business Suite systems are running with a HANA database as an active area (Integrated Scenario), the HANA-based Analytics views are used for this deployment scenario as well.



2.1 General Information

Before you use Smart Business for SAP Master Data Governance, you must complete some preparatory tasks to set up the technical infrastructure. Two key tasks are as follows:

Enabling the initial generation of the HANA Content (especially the Calculation Views) from the ABAP stack

Ensuring data is present in the HANA database for analytical evaluations during runtime.

For this the following steps need to be completed in advance:

Preparation of users required for system setup

Preparation of database schema:

Creation of database schema

Assignment of the database schema to a SAP HANA database user as standard database schema

Addition of database tables to this database schema

Enabling data replication to these tables via SAP Landscape Transformation (Side-By-Side Deployment)

Configuration of the database connection between the MDG ABAP System and the HANA Database

Optional: Entering of a connection from DBCON as DB Con Name for MDG in the MDG Landscape Profile

Enabling replication using SAP Landscape Transformation in case of side-by-side deployment

The details of these steps will be covered in the following sub-chapters.

2.2 Technical Prerequisites

2.2.1 Component for Customer Messages

Use component CA-MDG-ANR to open Customer messages regarding SAP Smart Business for SAP

Master Data Governance.

2.2.2 SAP Master Data Governance

You have installed SAP Master Data Governance 7.0, Support Package 2, which allows you to enable the consumption of change-request related HANA content in SAP Smart Business for Master Data Governance.

2.2.3 SAP HANA

You have installed SAP HANA Platform Support Package Stack 07 to enable the use of features that are related to the HANA database and described in this document.

2.2.4 SAP Smart Business

You have installed and configured SAP Smart Business 1.0 SP01 to enable the use of the features that are related to the Tile Definition for SAP Smart Business described in this document.

2.3 Required User Types

When you perform the initial setup and handling steps required to enable SAP Smart Business for SAP Master Data Governance, you must use a different set of user types. This chapter gives an overview of these user types and their required privileges that enable the users to execute the required steps or tasks.



2.3.1 MDG ABAP Backend User

For the execution of the generation report that creates the HANA content an ABAP user in the MDG Backend is required. The user needs to have administrator privileges, for example using the Master Data Governance Administrator (SAP_MDG_ADMIN) role.

Required Authorizations:

General authorization for the execution of ABAP reports

Execution of transactions (especially MDG_GEN_HBA_CR)

Authorization for authorization group MDGADMIN

2.3.2 User for Two-Way Connection between the MDG ABAP Backend and the HANA Database

A database user is required to connect the MDG ABAP backend system with the HANA Database. This user executes the creation of the HANA content within the HANA Database. For this user, you must set the following privileges are required for the relevant software package:

Authorization to read objects (packages, calculation views)

Create and activate Packages

Create and activate Calculation Views

Create files (.xsodata, .xsapp, .xsprivileges, .xsaccess)

In addition, it is important that a standard database schema (for example, SAP_MDG) is assigned to this user

(his database schema is an important prerequisite for the Calculation View generation as the underlying database tables (for example USMD120C) need to be present in this database schema that is assigned to the

connecting user.

2.3.3 Users and Roles for SAP Smart Business

In order to use SAP Smart Business, you must use SAP HANA roles and users in addition to the PFCG roles and ABAP users required in the frontend server. For details on setting up SAP Smart Business in your landscape please refer to the Administration Guide for SAP Smart Business Applications.

In general, to create and consume SAP Smart Business content, the following PFCG and HANA roles must be assigned to the appropriate users.

Frontend

Description Role

Provides access to the KPI catalog SAP_KPIFRW_TCR_S

SAP HANA

Description Role

For all users, you must assign the general role

sap.hba.apps.kpi.s.roles:SAP_SMART_BUSINESS_RUNTIME

For users who must manage and model KPIs, you must assign the role

sap.hba.apps.kpi.s.roles:SAP_SMART_BUSINESS_MODELER

http://help.sap.com/saphelp_ssb/helpdata/en/2d/740c5260e57b38e10000000a445394/frameset.htm



2.4 Database Schema / Required Database Tables

The Calculation Views that are generated or created are accessing database tables stored in a specific database schema (for example SAP_MDG) within the HANA Database. As a prerequisite, several database

tables need to be present in this database schema upfront. It is important to choose the schema that is assigned as the standard database schema to the user itemized in the database connection table (DBCON)

on the ABAP system. As a prerequisite the database schema, of course, must either exist or be created in the HANA Database.

The following database tables are required and need to be mapped in this corresponding schema:

Object/Entity Corresponding Database Table Description

Change Request Header Data USMD120C Change Request

Change Request Type USMD110C Type of Change Request

USMD110T Type of Change Request (Text Table)

Change Request Reason USMD211T Change Request: Reason (Text Table)

Change Request Reject Reason USMD212T Change Request: Reason for Rejection

Change Request Priority USMD210T Change Request: Priority (Text Table)

Change Request SLAs USMD1102 Define Service Level Agreement for Change Request Types

Change Request User Data / Name Mapping

USR21 User Name/Address Key Assignment

ADRP Persons (Business Address Services)

Change Request Type Business Activity Assignment

USMD1601 Business Activity: Type of Change Request

Business Activity USMD160C Business Activity: Definition

USMD160T Business Activity (Text Table)

Logical Action Text USMD170T Logical Action (Text Table)

Edition Type USMD010C Type of Edition

USMD010T Type of Edition (Text Table)

Change Request Status USMD130T Status of Change Request (Text Table)

OTC MDGI_OTC_BS Object Type Codes

MDGI_OTC_T_BS Object Type Code Descriptions

Data Model USMD001T Data Model: Text Table

To execute Change Request based analytics for the abovementioned database tables, the following conditions must exist:

The database tables must be filled with data from the corresponding MDG ABAP system (in the Side-By-Side deployment)



The MDG ABAP system must be configured by means of a replication using SAP Landscape Transformation in this case.

Additional remark: Even though analytical scenarios work with specific data sets or specific parts of tables, all the above-mentioned database tables are a technical prerequisite for the Calculation View generation and must exist in the corresponding database schema.

2.5 Database Connection

The connection from the MDG ABAP System to the HANA Database is a prerequisite for HANA Content generation and can be maintained via transaction DBCO. The connections itemized here will be offered as

generation targets for the HANA Content generation report.

Maintain the following information:

DB Connection

The logical name of the database connection.

DBMS

The type of database system. This has to be HDB (SAP HANA Database) for the scenario described in this guide.

User Name

The database user for which the database connection is opened. As described before it is important that for the user mentioned here the database schema (which is used for the MDG database tables) is maintained as the standard database schema. This information is essential as during the HANA Content generation exactly this database schema will be used for the Calculation View generation.

DB password

Password for setting up the connection to the database This field contains the password of the user with which the database connection is established.

Connection info

Database-specific information for a database connection

This field contains the technical information that is analyzed in native SQL in the CONNECT statement in

order to open the database connection. The exact information required depends on the database.

Further technical settings are available

As described, the datasets maintained here are offered for the HANA content generation report as possible target systems or databases. For convenience reasons, the database connection name for MDG specified in the Implementation Guide is used as a default. You can find and maintain this information in Customizing for Master Data Governance (transaction MDGIMG) under General Settings

-> Technical Settings for Master Data -> Define MDG Landscape Profile.



2.6 SAP LT Replication

In the case of a side-by-side deployment it is necessary to set up the SAP LT Replication Server for the above mentioned tables before any views are generated.

You can find detailed instructions in the document Installation Guide – Trigger-Based Data Replication Using SAP LT Replication Server for SAP HANA, which is available from the SAP HANA Platform (https://help.sap.com/hana_platform) page in the SAP Library.

3. Generation of HANA Content

3.1 General Concept

The HANA content for MDG Applications consists of views that are built up by different calculation views and files for the OData service, for example .xsodata, .xsaccess, .xsapp and .xsprivileges. Within

these calculation views we distinguish between view categories, for example private views, reuse views and query views.

Private Views

Private views are encapsulated SQL calculations on database tables or even other private views.

Reuse Views

Reuse views are the building blocks of private views that expose the business data in a well-structured and consistent way. They incorporate the relevant business data in SAP Business Suite systems. Reuse views are designed for reuse by other views and they do not have to be consumed directly by analytic tools.

Query Views

Query views are always the top view in a hierarchy of views. They are considered for direct use by analytic applications. In the next sections we are going to explain the content of views and their properties within our delivered views for MDG Applications.

3.1.1 HANA Private Views

The views for MDG Applications do not contain any private views.

3.1.2 HANA Reuse Views

The views for MDG Applications contain several reuse views. Within these reuse views, SQL operations are executed to provide the relevant business data of the change request header object.

Name of Reuse View Joined Database Tables/Reuse Views

Description

ChangeRequestHeaderBasic USMD120C Change Request Data

https://help.sap.com/hana_platform

https://help.sap.com/hana_platform



ChangeRequestType USMD110C Change Request Type Data

USMD110T

ChangeRequestEditionType USMD110C

USMD010T

Edition Type Data

UsernameConversion USR21

ADRP

Username Data

ChangeRequestObjectTypeCode USMD160C

USMD160T

Business Object Type Code Data

ChangeRequestBusinessActivityOTC USMD1601

ChangeRequestObjectTypeCode

Business Activity relevant Object Type Code Data

The reuse views shown above are consumed by the main reuse view ChangeRequestHeader. This view

also accesses different database tables for collecting all the relevant business data for the change request header. The table below shows all reuse views and database tables for the view ChangeRequestHeader:

Name of Reuse View Joined Database Tables/Reuse Views Description

ChangeRequestHeader ChangeRequestHeaderBasic Complete dataset for Change Request Header with additional calculated fields

ChangeRequestType

USMD210T

USMD211T

USMD212T

USMD130T

USMD1102

UsernameConversion

ChangeRequestEditionType

ChangeRequestBusinessActivityOTC

MDGI_OTC_BS

MDGI_OTC_T_BS

USMD001T

The reuse view ChangeRequestHeader provides the following business data for the change request

header:

Column/Data Semantical Unit (Unit)

Label Description

SAPClient Number (Character)

SAPClient SAP Client

ChangeRequest Number (Character)

Change Request

Change Request ID

ChangeRequestDescription Text (Character) Description Description of Change



Request

ChangeRequestType Text (Character) Type Code Change Request Type

ChangeRequestTypeName Text (Character) Type Change Request Type Description

ChangeRequestPriority Text (Character) Priority Code Change Request Priority

ChangeRequestPriorityName Text (Character) Priority Change Request Priority Description

ChangeRequestStatus Number (Character)

Status Code Change Request Status

ChangeRequestStatusName Text (Character) Status Change Request Status Description

ChangeRequestReason Number (Character)

Reason Code Change Request Reason

ChangeRequestReasonName Text (Character) Reason Change Request Reason Description

ChangeRequesRejectionReason Number (Character)

Rejection Reason Code

Reason for Rejection

ChangeRequestRejectionReasonName Text (Character) Rejection Reason

Reason for Rejection Description

ChangeRequestHasSingleObject Flag[X or

SPACE] (Character)

Has Single Object

Single Object Maintenance

ChangeRequestIsParallel Flag[X or

SPACE] (Character)

Is Parallel Change Request is processed in parallel mode

Edition Number (Character)

Edition Edition

EditionType Text (Character) Edition Type Code

Edition Type

EditionTypeName Text (Character) Edition Type Edition Type Name

EditionTypeDataModel Text (Character) Edition Type Data Model Code

Edition Type used Data Model

EditionTypeDataModelName Text (Character) Edition Type Data Model

Edition Type Data Model Description

EditionValidity Text (Character) Edition Validity Validity of Edition

FiscalYearVariant Text (Character) Fiscal Year Variant

Fiscal Year Variant

EditionTypeIsRetired Text (Character) Edition Type is Retired

Edition Type is closed

LogicalAction Text (Character) Logical Action Code

Business Activity

LogicalActionName Text (Character) Logical Action Business Activity Description

DataModel Text (Character) Data Model Code

Data Model



DataModelName Text (Character) Data Model Data Model Description

ObjectTypeCodeName Text (Character) Business Object Type Code

Business Object Type

ObjectTypeCodeMainName Text (Character) Business Object Type Main

Business Object Type of Main Object

CreationDateTime Timestamp (Decimal)

Creation Date Time

Timestamp of Creation

ReleaseDateTime Timestamp (Decimal)

Release Date Time

Timestamp of Release

DataIsActivated Text (Character) Data Is Activated

Data of Change Request is activated (X

or Space)

ChangeRequestDraftStep Number (Character)

Draft Step Code Last step processed in draft

CreatedByUsername Text (Character) Created By User Name of Requestor

ReleasedByUsername Text (Character) Released By User Name of Approver

SLADays Number (Integer) SLA Days SLA: Maximum number of days

SLAHrs Number (Character)

SLA Hours SLA: Maximum number of hours

DueDate Date (Character) Due Date Due Date of Change Request

MainEntity Text (Character) Main Entity Main Entity Type of Change Request

BusinessActivityName Text (Character) Business Activity

Business Process Description

BusinessActivity Text (Character) Business Activity Code

Business Process

ObjectTypeCode Text (Character) Business Object Type Code

Business Object Type Code

ObjectTypeCodeMain Text (Character) Business Object Type Code Main

Business Object Type Code of Main Object

The reuse view ChangeRequestHeader also contains several SQL operations and calculations. Therefore,

in addition to the business data, this view also offers the following calculated columns and measures to support the analysis of the data:

Calculated Column Semantical Unit (Unit)

Label Description

TotalChangeRequest Number (Integer) Total Change Requests

Measure for total number of Change Requests

TotalProcessingTime* Days (Integer) Total Processing Time

Measure for total processing time



TotalSLAExpiryDays* Days (Integer) Total SLA Expiry Days

Measure for total of SLA expiry

TotalDueDateExpiryDays* Days (Integer) Total Due Date Expiry Days

Measure for total of due date expiry

TotalExpiryDays* Days (Integer) Total Expiry Days Measure for the total expiry of a change request

CreationDate_E Date (Date) Creation Date Date of Creation

ReleaseDate_E Date (Date) Released Date Date of Release

CreationDateYearWeek_E YearWeek (Character) Creation Date Year Week

Year and week of Creation

ReleasedDateYearWeek_E YearWeek (Character) Release Date Year Week

Year and week of Release

CreationDateYearMonth_E YearMonth (Character) Creation Date Year Month

Year and Month of Creation

ReleasedDateYearMonth_E YearMonth (Character) Release Date Year Month

Year and Month of Release

CreationDateYearQuarter_E YearQuarter (Character)

Creation Date Year Quarter

Year and Quarter of Creation

ReleasedDateYearQuarter_E YearQuarter (Character)

Release Date Year Quarter

Year and Quarter of Release

CreationDateYear_E Year (Character) Creation Date Year

Year of Creation

ReleasedDateYear_E Year (Character) Release Date Year

Year of Release

DueDate_E Date (Date) Due Date Due Date

SLAHalfDay HalfDay (Integer) SLA Half Day SLA: Half Day (1 or 0)

ProcessingTime Days (Integer) Processing Time Processing time

SLAIsDefined Flag[X or SPACE]

(Character)

SLA Is Defined SLA is defined

DueDateIsDefined Flag[X or SPACE]

(Character)

Due Date Is Defined

Due Date is set

SLAExpiryDays Days (Integer) SLA Expiry Days SLA expiration

DueDateExpiryDays Days (Integer) Due Date Expiry Days

Due Date expiration

DaysLeftSLAExpiry Days (Integer) Days Left For SLA Expiry

Days left until SLA will expire

DaysLeftDueDateExpiry Days (Integer) Days Left For Due Date Expiry

Days left until Due Date will expire

DaysLeftExpiry Days (Integer) Days Left For Expiry

Days left until closest expiry either SLA or Due Date

ExpiresToday Flag[X or SPACE]

(Character)

Expires Today Due Date or SLA Date is today

SLAIsExpired Flag[X or SPACE]

(Character)

SLA Is Expired SLA is expired



DueDateIsExpired Flag[X or SPACE]

(Character)

Due Date Is Expired

Due Date is expired

IsDelayed Flag[X or SPACE]

(Character)

Is Delayed Change Request is delayed either due to SLA or Due Date

ExpiryDays Days (Integer) Expiry In Days Maximum of an Expiration of Change Request either due to SLA or Due Date violation

IsFinalized Flag (Character) Is Finalized Change Request is finalized

SLADate Date (Date) SLA Date Date for SLA expiration

IsDraft Flag[X or SPACE]

(Character)

Is Draft Change Request is saved as draft

IsFinallyApproved Flag[X or SPACE]

(Character)

Is Finally Approved

Change Request is of status finally approved

IsFinallyRejected Flag[X or SPACE]

(Character)

Is Finally Rejected

Change Request is of status finally rejected

IsErroneous Flag[X or SPACE]

(Character)

Is Erroneous Change Request is of status erroneous

DataModel_E Text (Character) Data Model Code Data Model of Change Request

DataModelName_E Text (Character) Data Model Data Model Description of Change Request

*These total values can be used to calculate averages.

3.1.3 HANA Query Views

The views for MDG Applications contain three query views. These query views use the results of the reuse view ChangeRequestHeader and therefore they offer all columns and calculated columns as offered from

the reuse view as described in the previous section. In addition these query views provide further functionality as several input variables and parameters. The following query views with different input variables and parameters are available:

Name of Query View Input Variables/Parameters Description

ChangeRequestHeaderQuery V_SAPClient Change Request Header Data with no time-based analysis

ChangeRequestHeaderCreatedDateQuery V_SAPClient

P_StartDate

P_EndDate

P_PastDays

P_OffsetDays

Change Request Header Data with time-based analysis on the creation date of the Change Request

ChangeRequestHeaderReleasedDateQuery V_SAPClient

P_StartDate

Change Request Header Data with time-based



P_EndDate

P_PastDays

P_OffsetDays

analysis on the released date of the Change Request

In addition to the data provided by the reuse view ChangeRequestHeader, the above query views provide

further measures for average values and analysis of the input parameters for a given time period:

Calculated Column Semantical Unit (Unit)

Label Description

AverageProcessingTime Days (Integer) Average Processing Time

Measure for average number of processing time

AverageSLAExpiryDays Days (Integer) Average SLA Expiry In Days

Measure for average of SLA expiry

AverageDueDateExpiryDays Days (Integer) Average Due Date Expiry In Days

Measure for average of due date expiry

AverageExpiryDays Days (Integer) Average Expiry In Days

Measure for the average expiry of change requests in days

IsValidForPeriod Flag[X or SPACE]

(Character)

Is Valid For Period

Valid Change Request within specified time period

The calling application must provide input parameters, for example an OData service (for more information, see the next section.) Depending on the request, the following input parameters for the time period must be set:

P_StartDate (Default Value 31.12.9999)

P_EndDate (Default Value 31.12.9999)

P_PastDays (Default Value 999999)

P_OffsetDays (Default Value 0)

The following kinds of time periods are possible:

No time period

Use the default values for all abovementioned input parameters. Note: the default for IsValidForPeriod is SPACE.

A fixed time period

For example 01.01.2013 until 31.12.2013.

Set the parameters P_StartDate and P_EndDate. Apply default values to P_PastDays and

P_OffsetDays.

A relative time period

For example the last 30 days. Set P_PastDays to the number of days for a given time period.

Set P_StartDate, P_EndDate, and P_OffstDays to the default values.

A relative time period with an offset in the past



Specify the P_OffsetDays parameter has as an offset to a given time period. For example, the time

period of 30 days before the time period of the last 30 days. For this example, you set the parameter P_OffsetDays to 30 and you set the parameter P_PastDays to 30 as well. You set P_StartDate and

P_EndDate to the default values.

This is an additional feature to get several time periods of the same number of days in the past, which can be compared. The comparison can be used to analyze trends within a given time period.

In case of a given time period, the calculated column with the flag IsValidForPeriod is set to X if the

change request is valid for the given time period and is set to SPACE if the change request is not within the given time period. Thus if the analysis is for a given time period, a filter has to be set to the column IsValidForPeriod.

3.1.4 OData Services

The MDG applications support access to the data using a service that uses the OData protocol. The OData service file is called ChangeRequestHeader.xsodata. This service provides access to the three query

views which provide different entity sets.

ChangeRequestHeaders

ChangeRequestCreatedDateHeaders

ChangeRequestReleasedDateHeaders

All three entity sets provide the measures TotalChangeRequests, AverageProcessingTime,

AverageSLAExpiryDays, AverageDueDateExpiryDays and AverageExpiryDays. While the entity

set ChangeRequestHeaders does not have any input parameters,

ChangeRequestCreatedDateHeaders and ChangeRequestReleasedDateHeaders provide four input

parameters to specify a time period as described in the previous section.

3.2 How To Generate HANA content

You can generate and activate HANA content using report MDG_ANLY_GENERATE_HBA_CR_CONT in the

package MDG_ANALYTICS_SOURCES. The content can then be consumed by Analytical Reporting Tools

such as SAP Smart Business.

The MDG_ANALYTICS_SOURCES report generates necessary HANA Views and OData services (.XSODATA)

that represent the basis for the mentioned KPIs in the Chapter 4. The files .XSACCESS, .XSAPP,

.XSODATA as well as .XSPRIVILEGES (with no content) will be generated.

The files itself have the following meaning/purpose:

.XSAPP: An application-specific file in a repository package that defines the root folder of a native SAP

HANA application. All files in that package (and any subpackages) are available to be called via URL. This file is generated without any content on purpose and it is used as a technical access point for accessing the content of the corresponding package where the file is located.

.XSODATA: A design-time object that defines an OData service that exposes SAP HANA data from a

specified end point. During the HANA content generation the file ChangeRequestHeader.xsodata is

created which comprises the HANA objects (i.e. HANA Query Views described in chapter ‎3.1.4) which are exposed via OData.

.XSACCESS: An application-specific configuration file that defines permissions for a native SAP HANA

application, for example, to manage access to the application and running objects in the package. The .XSACCESS file is generated with the “Basic”-Authentication method as a default. For more information

have a look at the SAP HANA Developer Guide listed below.

.XSPRIVILEGES: A file that defines a privilege that can be assigned to an SAP HANA Extended

Application Services application, for example, the right to start or administer the application.

Hint: The files are generated with sample content that you must adapt according to the project related purposes. A detailed documentation about this can be found in chapter 3.5 “Creating the Application Descriptors” of the SAP HANA Developer Guide. You can also refer to the SAP HANA Modelling Guide.

http://www.saphana.com/docs/DOC-3816




3.2.1 Running the HANA Content Generator Report

1. Run transaction MDG_GEN_HBA_CR

2. Choose your target HANA Database Connection and the target HANA Package for the generated content.

If you choose default connection, the connection from the MDG customizing will be considered as described in the Chapter 2.

3. Select the Create package checkbox to create the target package in HANA, in case no package exists.

4. Choose the Execute button. 5. Pay attention to the messages displayed as an output list about the generation process with

corresponding success, warning or error color indications.

You can find the generate content in the target system in Repositories tab in the perspective SAP HANA Development.

3.2.2 Outcome of View Regeneration

If you run the report after the HANA content is generated, the system generates new versions of the HANA views and OData services. .XSACCESS, .XSAPP and .XSPRIVILEGES are overwritten.

3.2.3 Troubleshooting for View Generation Process

1. I am not able to run the generation report via transaction MDG_GEN_HBA_CR.

Ensure your user has the correct authorizations for the execution of transactions and reports. Ensure the authorization group MDGADMIN is assigned to your user.

2. Can I set a default HANA Database Connection?

The view is generated using the default HANA Database Connection, if this connection is configured in Customizing. You can maintain the connection in the MDG Landscape Profile activity in Customizing for Master Data Governance (transaction MDGIMG). The details are described in chapter ‎2.5.

3. The view generation process stops with the error message that the package does not exist.

In the entry screen of the MDG Analytics: HANA Content Generator report (transaction MDG_GEN_HBA_CR),

enter a package or choose the Create Package checkbox.

4. The view generation process stops with error messages related to missing authorizations.

Ensure that the user has at least the authorizations mentioned in chapter ‎2.3.2. The user is required for the replication process and is configured at the level of the database connection (transaction DBCO). The error

message texts can give helpful information.



5. What do I do if not all views are completely generated?

The MDG Analytics: HANA Content Generator report (transaction MDG_GEN_HBA_CR) generates each view

sequentially. Sequential generation is required as the views are organized in a hierarchy and heavily depend on each other. If somewhere in this view hierarchy one view cannot be generated, the report does not generate subsequent views.

To ensure all views are completely generated, check the report log, identify which view stopped the view generation, and resolve the errors in that view. Execute transaction MDG_GEN_HBA_CR again.

6. I receive generic errors that refer to the failed activation of the Calculation Views.

Generic activation errors are mostly based on missing database tables in the customer-defined HANA Database schema used for the generation process. Ensure that all database tables mentioned in chapter ‎2.4 are present in the corresponding database schema.

7. I am not able to start the generation process due to technical error messages.

Ensure that the system is set up as described in detail in chapter 2. The following combination of settings is especially important:

The user that is configured for the generation process

The HANA Database schema assigned to the user

The HANA Database connection

4. Detailed Description KPIs

Summary

In this chapter, you see how to utilize the generated SAP HANA queries to get deep insight to your change requests analytics. A set of sample KPIs is provided below. You can create additional KPIs or extend the KPIs described below.

For all BI-clients consuming these queries you can calculate the described KPIs by applying the related measures, filters and dimensions of the different query types.

Note:

For the time dependent queries there are dedicated parameter values with a specific semantics (either you use P_StartDate and P_EndDate for explicit timeframe definition or P_OffsetDays

and P_PastDays for relative timeframe specification):

The following selections take all change requests in the system/client into account:

P_StartDate = 9999-12-31 (YYYY-MM-DD)

P_EndDate = 9999-12-31 (YYYY-MM-DD)

The following selections take all change requests that are either created or released in the last P_PastDays from today into account:

P_OffsetDays = 0 (Integer)

P_PastDays = 999999 (Integer)

4.1 Erroneous Requests

4.1.1 Description

With Erroneous Requests, you can display all change requests in the system that are in an erroneous state

and cannot be finalized. Alternatively you can select a period of time when the erroneous requests were

created. The business benefits of this KPI are that it provides possible insights into ways to avoid the error



situation, enables you to overcome process obstacles, and helps you to remove “dead-end” change

requests.

4.1.2 Time-Independent

Entity Set ChangeRequestHeaders

Measure TotalChangeRequests

Number of change requests (without dimension)

Calculation Rules The query delivers the total number of MDG change requests in which the change request is erroneous.

Dimensions Filter

SAPClient (should be specified)

IsErroneous = X

Input Parameters

None

Time-Dependent

4.2 Finally Approved Requests

4.2.1 Description

With Finally Approved Requests, you can display change requests that are finally approved and created in

a specific period of time. Alternatively you can display the number of all approved change requests created in

the system or select all change requests released in specific period of time. The business benefit of this KPI

is that it provides possible insights into the volume of change requests per creation reason and can be

compared to the number of rejected requests.


Entity Set ChangeRequestCreatedDateHeaders



Calculation Rules The query delivers the total number of MDG change requests that are finally approved.

Dimensions Filter:


Disapproved = X

Input Parameters

None



4.2.3 Time-Dependent




Calculation Rules The query delivers the total number of MDG change requests that meet the following conditions:

Creation date meets either of the following criteria:

Occurs in a user-specified timeframe (for example January to June)

Occurs in either of the following:

A specified number of days in the past (for example last 10 days)

A specified offset preceding the specified number of days in the past (for example, 10 days before last 10 days).

Change request is finally approved.

Input Filter:


IsValidForPeriod = X

IsApproved = X

Input Parameters (Mandatory)




P_OffsetDays = n (Integer)

Entity Set ChangeRequestReleasedDateHeaders

Type Number of change requests (without dimension)


Approved (= Released) date meets either of the following criteria:





Change request is finally approved.

Input Filter:



IsApproved = X



Input Parameters (Mandatory)





4.3 Finally Rejected Requests

4.3.1 Description

With Finally Rejected Requests, you can display all change requests that are finally rejected and created in a

given period of time. Alternatively you can display the number of all rejected requests created in the system

or all rejected requests rejected in a given period of time. The business benefit of this KPI is that it provides

possible insights into the volume of rejected change requests by rejection reasons and can be used to

reduce the number of rejected requests.



Measure

TotalChangeRequests


Calculation Rules The query delivers the total number of MDG change requests that are finally rejected.

Dimensions Filter:


IsRejected = X

Input Parameters

None



Measure

TotalChangeRequests







A specified offset preceding the specified number of days in the past



(for example, 10 days before last 10 days).

Change request is finally rejected.

Input Filter:



IsRejected = X

Input Parameters (Mandatory):






Type: number of change requests (without dimension)

Measure

TotalChangeRequests



Rejection (= Released) date meets either of the following criteria:





Change request is finally rejected.

Input Filter:



IsRejected = X








4.4 Open Change Requests

4.4.1 Description

With Open Change Requests, you can display the number of open change requests that were created in a

given period of time. Alternatively, you can display the number of all open change requests created in the

system. The business benefit of this KPI is that it provides possible insights into the current workload and

helps to optimize the processing time of the open change requests.



Measure

TotalChangeRequests


Calculation Rules The query delivers the total number of MDG change requests that are not finalized.

Dimensions Filter:


IsFinalized ≠ X


None



Measure

TotalChangeRequests



Rejection (= Released) date meets either of the following criteria:





Change request is not finalized.



Input Filter:



IsFinalized ≠ X






4.5 Total Change Requests

4.5.1 Description

With Total Change Requests, you can display the number of change requests that were created in a given

period of time. Alternatively, you can display the number of all change requests created in the system. The

business benefit of this KPI is that it provides insights into the workload of change requests created and

allows you to predict future trends based on the historic data.



Measure

TotalChangeRequests


Calculation Rules The query delivers the total number of MDG change requests.

Dimensions Filter:



None



Measure

TotalChangeRequests


Calculation Rules The query delivers the total number of MDG change requests for which the creation date meets either of the following criteria:







Input Filter:



Input Parameters:





4.6 Average Delay Time

4.6.1 Description

With Average Delay Time you can display the average delay time of finalized change requests that violate

either the given due date or a defined SLA or both. The business benefit of this KPI is that it provides

possible insights into ways to reduce the average delay time.



Measure

AverageExpiryDays

Average delay of change requests (in days)


Change request is finalized

The expected finalization date is late because either or both of the following conditions are true:

The actual processing time exceeds the due date. In other words, the date in which the change request was released or rejected is greater than the due date.

The actual processing time violates the SLA of the change request. In other words, if you subtract the creation date of the change request from the date in which the change request was released or rejected, the result exceeds the number of days specified in the service level agreement for the change request type and priority.

Dimensions Filter:




IsFinalized = X

IsDelayed equals ‘X’

Input Parameters:

None



Measure

AverageExpiryDays












Input Filter:



IsFinalized = X










Measure

AverageExpiryDays



Released date meets either of the following criteria:









Input Filter:



IsFinalized = X









4.7 Processing Time Exceeded

4.7.1 Description

With Processing Time Exceeded, you can display the number of finalized change requests that violated the

given due date or a defined Service Level Agreement (SLA) or both. The business benefit of this KPI is that it

provides possible insights into ways to reduce the delay time.








Due date exceeded: the date in which the change request was released or rejected is greater than the due date.

SLA violated: if you subtract the creation date of the change request from the date in which the change request was released or rejected, the result exceeds the number of days specified in the service level agreement for the change request type and priority.

Dimensions Filter:


IsFinalized = X


Input Parameters

None

















Input Filter:



IsFinalized = X



















SLA violated: if you subtract the creation date of the change request from the date in which the change request was released or rejected, the result



exceeds the number of days specified in the service level agreement for the change request type and priority.

Input Filter:



IsFinalized = X







4.8 Average Processing Time

4.8.1 Description

With Average Processing Time, you can display the average processing time of finalized change requests.

The business benefit of this KPI is that it provides possible insights into how to optimize the average

processing time.



Measure AverageProcessingTime

Average processing time of change requests (in days).






Dimensions Filter:


IsFinalized = X



Input Parameters:

None















Input Filter:



IsFinalized = X









Calculation Rules The query delivers the total number of MDG change requests that meet the



following conditions:










Input Filter:



IsFinalized = X






4.9 Long-Running Requests (Finalized)

4.9.1 Description

With Long-Running Requests, you can display all change requests that were created and then either

approved or rejected within a given period of time (for example, 3 months) and where the processing time

exceeded a specific threshold (for example, 20 days). Alternatively you can display the number of all long-

running requests in the system or all long-running requests finalized (approved or rejected) in a given period

of time. The business benefit of this KPI is that it provides possible insights into ways to improve the change

request flow and reduce the number of long-running requests.






Number of change requests (without dimension).


Change request is finalized.

Actual processing time is greater than a given threshold of m days.

Dimensions Filter:


IsFinalized = X

ProcessingTime > m

Input Parameters:

None













Input Filter:



IsFinalized = X

ProcessingTime > m

Input Parameters:


















Input Filter:



IsFinalized = X

ProcessingTime > m






4.10 Long-Running Requests (Open)

4.10.1 Description

With Long-Running Requests, you can display all open change requests within a given period of time (for

example, 3 months), or all open requests in the system, in cases where the processing time exceeds a

specific threshold (such as 10 days). The business benefit of this KPI is that it provides possible insights into

ways to improve the change request process and reduce the number of long-running requests.










Dimensions Filter:


IsFinalized ≠ X

ProcessingTime > m

Input Parameters:

None













Input Filter:



IsFinalized ≠ X

ProcessingTime > m








4.11 Overdue

4.11.1 Description

With Overdue, you can display the number of all open change requests in the system that exceed the given

due date and or violate a defined Service Level Agreement (SLA) or both. Alternatively you can display the

number of all delayed requests created in a given period of time. The business benefit of this KPI is that it

provides possible insights into ways to reduce the number of delayed change requests and so allows you to

accelerate the remaining processing time.









Dimensions Filter:


IsFinalized ≠ X


Input Parameters (Mandatory): None
















Input Filter:



IsFinalized ≠ X







4.12 Potentially Overdue

4.12.1 Description

With Potentially Overdue, you can display the number of open change requests that might exceed the given

due date and or violate a defined Service Level Agreement soon. To determine what you mean by soon, you

can define a given threshold such as overdue in n= 3 days. Alternatively, you can display the number of all

delayed requests created in a given period of time. The business benefit of this KPI is that it provides

possible insights into ways to reduce the number of delayed change requests and accelerate the remaining

processing time.








Change request is not finalized

Change request will be late within m days

If you add m days to the current date the result either exceeds the due date or violates the SLA of the change request, or both.

Dimensions Filter:


IsFinalized ≠ X

DaysLeftExpiry < m

Input Parameters: None












Change request will be late within m days

If you add m days to the current date, the result either exceeds the due date or violates the SLA of the change request, or both.

Input Filter:



IsFinalized ≠ X



DaysLeftExpiry < m






4.13 On Time

4.13.1 Description

With On Time, you can display the number of finalized change requests that either do not exceed the given

due date, or do not violate the SLA, or do not breach both conditions. Alternatively, you can display the

number of all delayed requests created in a given period of time. The business benefit of this KPI is that

provides a number that can be used when comparing overdue requests with on-time requests.






Change Request is finalized

Change Request is not delayed

Dimensions Filter:


IsFinalized = X

IsDelayed ≠ X






Calculation Rules The query delivers the total number of MDG change requests that meet the



following conditions:




A specified number of days in the past (for example last 10 days).



Actual Processing time is greater than a given threshold of m days.

Input Filter:



IsFinalized = X

IsDelayed ≠ X

Input Parameters:















Actual Processing time is greater than a given threshold of m days.

Input Filter:





IsFinalized = X

IsDelayed ≠ X

Input Parameters:





4.14 Change Requests without Due Date/SLA

4.14.1 Description

With Change Requests without Due-Date/SLA, you can display the number of all open change requests that

are missing one or both of the following defined finalization periods: due date and SLA. Alternatively, you can

display the number of all delayed requests created in a given period of time. The business benefit of this KPI

is that it provides possible insights into ways to accelerate the processing time by monitoring the change

requests against the finalization periods assigned to them.







Due date has no value and no SLA is defined for the given change request type and priority

Dimensions Filter:


IsFinalized ≠ X

SLAIsDefined ≠ X

DueDateIsDefined ≠ X















Due date has no value and no SLA is defined for the given change request type and priority.

Input Filter:



IsFinalized ≠ X

SLAIsDefined ≠ X

DueDateIsDefined ≠ X

Input Parameters:







5. Advanced Topics

5.1.1 Client Handling

SAP Business Systems often separate their data using either table column CLIENT or table column MANDT,

both of which occur in all database tables that cover client dependent data. SAP software ensures that these clients and their data are strictly separated like independent systems. If a user logs on to the system, the session is always assigned to a specific client and access to other clients is usually not allowed.

For HANA Based Analytical Applications, you must manually incorporate this behavior. All views that cover client-dependent data must include either a mandatory input parameter SAPClient or a variable

V_SAPClient. This is because a select statement on a view covering client-dependent data can only be

executed if a parameter or variable specifying the client exists. Tools that access the data are also forced to provide this client information. Therefore, such queries are always executed within a single client.

5.1.2 Authorization Concept

The generated HANA Content and the generated Calculation Views follow the general concepts of the authorization model of SAP HANA.

For an overview of the authorization model, as well as more detailed information about how this authorization model as it is implemented for SAP HANA, see HANA Developer Guide, starting in chapter 11 Setting Up Roles and Authorizations.

You must define HANA privileges to restrict the access of reporting tools to the generated Calculation Views. Examples of reporting tools include Excel, BI, BOBJ, and SAP Smart Business. In addition to general System Privileges (which can be used for performing system level operations) and the Package Privilege (which can be used to permit for reading specific objects within a package), you must consider the following privilege types:

Object Privilege

These privileges restrict access to a specific database table or to a (calculation) view. The Object Privileges are part of the SQL standard and enable the administrator to entirely grant or to revoke access to specific objects.

Analytic Privilege

These privileges grant access to different portions of data in the same (calculation) view depending on the current combination of user and business role. Example Sales data for all regions are contained within one calculation view. However, regional sales managers should only see the data for their region. In this case, you can model an analytic privilege so that all users can query the view, but the system only returns data that individual users are authorized to see.

In conclusion, you must configure the abovementioned techniques and privileges according to the corresponding Business Scenario that must be implemented in the system. For more details on these topics, see the previously mentioned SAP HANA Developer Guide. Subchapter 11.4.4 Analytic Privileges is especially relevant.

Furthermore, you can apply authorization-relevant settings for the OData-Services that expose HANA content to the outside world. You can apply the relevant settings in the Application Descriptor Files that are covered in chapter ‎3.2. A detailed documentation how to apply these settings, see chapter 3.5 Creating the Application Descriptors of the SAP SAP HANA Developer Guide.

5.1.3 Extensibility

If you want to enhance the generated HANA Content (especially if you want to enhance the Calculation Views), according to the business requirements, see the following SCN-Based Guide: How to Enhance SAP HANA Live.




https://scn.sap.com/docs/DOC-44726

https://scn.sap.com/docs/DOC-44726



Although this guide refers directly to the SAP HANA Live program, the basic principles for extending and enhancing the MDG Calculation views are essentially the same.

5.1.4 Language Dependency

HANA views are only available in English.

Note: To get consistent results across all languages used in the SAP Smart Business Dashboard, ensure all language-dependent attributes are provided. Otherwise, the system aggregates numbers under the category ‘No Value.’ This aggregation leads to different results dependent on the language.

5.1.5 FAQ / Tips & Tricks

You can find some tips and tricks regarding the use of SAP HANA, in the SAP HANA developer guide, which

is located in the SAP Library. Go to the SAP HANA Platform page. The guide is available under

Development Information.

You can find some tips and tricks for in the central guide for SAP Smart Business, which is available from the

SAP Smart Business Cockpits (http://help.sap.com/ssb) page.

6. Defining a Tile in SAP Smart Business (Step by Step)

6.1 Create KPI

Seq. Execution Steps Action Details Expected Results/ Checks

1.1 Call KPI modeler

Start the Internet Browser and call the URL of the KPI modeler:

https://<URL>:<PORT>/sap/bc/ui5_ui5/sap/

ca_kpi/modeler/index.html

Exchange the following attributes:

<URL> = URL of the server

<PORT> = Port for the service, for example 4085.

The KPI modeler home page is shown.

Additional info on KPI modeler: http://help.sap.com/ssb

1.2 Initiate KPI creation

On the lower left corner of the browser window, choose the selection list button and select Add KPI to create a new KPI.

Page ‘Add New KPI’ is shown.

1.3 Enter code, title and description

Enter a meaningful KPI code without spaces. Descriptive fields for KPI are filled.

1.4 Enter tags In the field Tags enter some keywords which describes the tile to be created. Enter tags separated by commas.

Tags are provided.

1.5 Define KPI details

Select an improvement direction, for example Minimizing (Lower is better). Define the value type, for example Number, and provide a KPI owner.

KPI details are defined.

1.6 Enter path for OData service

Enter the OData path using the following syntax: /<PATH>/<SERVICE>.

The path to the OData service has been

http://help.sap.com/hana_platform

http://help.sap.com/ssb






<PATH> = Path to workspace repository. For

example, /home/hba/mdg/ana/odata

<SERVICE> = OData service file name. For example, ChangeRequestHeader.xsodata

defined. Be aware that the path is case sensitive.

1.7 Select entity set Select the entity set provided by the OData service. For example, ChangeRequestHeaders. If the

selection list is empty, verify the OData path entered in step 1.6.

Entity set is shown and could be selected.

1.8 Select Measure Select a counter (calculated columns) that is needed as measure. For example the number of Change Requests TotalChangeRequests.

Measure has been defined.

1.9 Save KPI Click the Save and Continue button. A success message indicates that the KPI has been saved and a new window ‘Add Evaluation’ is shown.

6.2 Add New Variant


2.1 Enter ID, title, and tags Next you have to create a variant. Enter a variant ID and a variant title. Enter tags separated by commas. You can reuse the tags used for the KPI definition.

ID, title, and tags for variant is shown.

2.2 Add filter and input parameter

You must define at least one filter or at least one input parameter. Define for example SAPClient as a filter with the

ID of the MDG hub client. The input parameters are defined by the entity set. Check the entity selected in first step if no parameters are offered or if the wrong input parameters are offered.

A filter, an input parameter, or both have been defined.

2.3 Add variant Choose Next. Tile successful saved.

6.3 Add Evaluation


3.1 Enter parameters For the new evaluation, you must enter an evaluation text, such as ‘Last 90 days’.

Add tags separated by commas. You can reuse the tags used for the KPI definition.

Text and tags for evaluation shown.

3.2 Add evaluation Choose Next. Screen for the threshold is shown.

3.3 Define target and thresholds

Define values for the thresholds and choose Next.

Thresholds values accepted by system.

3.4 Apply trend Skip this step if you do not define a trend for your tile. Choose the Activate and

Activation was successful.




authorize button. Note: You must first define Evaluation with offset before it can be applied as trend.

3.5 Define authorizations Select and check the users permitted to call and view the KPI tile. Choose the Finish button to finalize the evaluation.

Authorization was successful generated.

3.6 Finalize KPI tile Choose the Finish button to close the screen Add new KPI.

Search screen shown.

6.4 Search and Activate KPI Tile


4.1 Search KPI tile Enter in the search field the initials used for your KPI. If necessary, reduce the result list by clicking the filter category KPIs and Inactive.

KPI with target icon is shown in search results.

4.2 Activate KPI tile Click the target icon and choose the Activate button.

Activation successful started.

6.5 Create Visualizations


5.1 Initiate creation of visualizations

Last step in the KPI Modeler is the creation of visualizations. On the lower left corner of the browser window, choose the selection list button and select Manage Visualizations. Search again with the initials used for your KPI.

The Manage Visualizations screen opens with your KPI evaluations.

5.2 Create visualizations Mark the line of the relevant evaluation on the left side and choose the Add Tile button.

A pop-up for tile creation is shown.

5.3 Specify tile attributes Select KPI Tile for tile type and define the format as Numeric Tile. Choose OK. You can repeat this step to add different tile types.

Screen ‘Manage Visualizations’ is shown with new tile.

5.4 Create drill-down Click the Drill-Down icon and choose the Configure Details button. Mark Create Configuration and choose OK.

Pop-up for drill-down configuration is shown.

5.5 Define view parameters Select as view type Chart and Bar. Enter a view name, for example By Type.

Select By Measure – Descending and choose as selected measure a calculated column, for example TotalChangeRequests. Select an

output column as a dimension, for example, Type Name of Change Request. You can repeat this step to add

Required parameters for views are defined.




several views by clicking the label Add View.

5.6 Activate header and filters

Switch on the KPI header details and the filters. Click the icons for KPI Header Details and Filter:. Enter values for header details. Enter dimensions for filters. Choose Ok. Choose Ok again on both pop-up windows.

Switch buttons are switched on. Annotation and drill-down successful configured.

6.6 Add KPI Tile

Seq. Execution Steps

Action Details Expected Results/ Checks

6.1 Start the Fiori Launchpad

In the Internet browser, open the Fiori Launchpad by entering its URL:

https://<URL>:<PORT>/sap/bc/ui5_ui5/ui2/ushell

/shells/abap/FioriLaunchpad.html

Exchange the following attributes:

<URL> = URL of the server

<PORT> = Port for the service, for example 4085.

The Fiori Launchpad home page is shown.

6.2 Open tile catalog

Click the upper left corner to open the menu. Click Tile Catalog to open the tile catalog.

Tile catalog is shown.

6.3 Search for KPI tile

Search with your initials for the tile you want to display on the launchpad.

One or more KPI tile types are shown in search result list.

6.4 Add KPI tile Click on the ‘+’ to add the desired KPI tile to the home screen. You can also use drag and drop to add the tile in a group defined before. When finished adding tiles, choose the back button in the upper left corner.

The new KPI tile added is shown on the Fiori Launchpad home page.

6.7 Check KPI Tile


7.1 Show KPI details Click the KPI tile to start the Generic Drill-Down Application that shows details of the KPI.

Chart is shown with KPI details.

7.2 Switch drill-down In the dropdown list, select another drill-down.

Selection list allows several drill-downs if defined. Make sure that all views can be selected as defined.

7.3 Activate filter Click the Filter icon in the upper right corner. Define a filter with several values

Available filters are shown on top. Make




selected. sure that all filters are listed as defined.

7.4 Use drill-down for chart value

In the chart, click one value shown and select an additional view.

New view shows only the data of the selected value.

7.5 Create personalized KPI tile

In the detail view, reduce the number of results by setting one or more filters. Afterwards click the icon Send in the lower right corner and choose the option Add to Catalog. Provide a name for the tile. Afterwards, search for the new personalized tile in the catalog and add it to your launchpad.

Make sure that for the personalized tile the data is shown as you have defined before.

Copyright 2015 SAP SE. All rights reserved ©

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

These materials are provided “as is” without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials.

SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these materials. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages.

SAP NetWeaver “How-to” Guides are intended to simplify the product implementation. While specific product features and procedures typically are explained in a practical business context, it is not implied that those features and procedures are the only approach in solving a specific business problem using SAP NetWeaver. Should you wish to receive additional information, clarification or support, please refer to SAP Consulting.

Any software coding and/or code lines / strings (“Code”) included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent.

Disclaimer

Some components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components.

Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way.

configuration and use of smart business for sap master data governance

Documents

sap smart business

sap hana

use of smart business

hana database

business use case

general information

sap lt replication

mdg abap backend user