How to guide-fiori-mm_en_xx

SAP Fiori Apps for the
SAP ERP Application MM
SAP SE
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
How to implement apps on top of the SAP Best
Practices Baseline packages
Based on the example of US Baseline V3.607
How-to Guide: V2.00

SAP Fiori Apps for the SAP ERP Application MM
© SAP SE Page 2 of 87
Copyright
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication maybe reproduced or transmitted in any form or for any purpose withoutthe
express permission ofSAP SE or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are
trademarks or registered trademarks ofSAP SE (or an SAP affiliate company) in Germanyand other
countries.Please see http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional
trademark information and notices.
Some software products marketed bySAP SE and its distributors contain proprietarysoftware components
of other software vendors.
National productspecifications mayvary.
These materials are provided by SAP SE or an SAP affiliate companyfor informational purposes only,
withoutrepresentation or warranty of any kind, and SAP SE or its affiliated companies shall notbe liable for
errors or omissions with respectto the materials.The only warranties for SAP SE or SAP affiliate company
products and services are those that are setforth in the express warranty statements accompanying such
products and services,if any. Nothing herein should be construed as constituting an additional warranty.
In particular,SAP SE or its affiliated companies have no obligation to pursue any course ofbusiness
outlined in this documentor any related presentation,or to develop or release any functionalitymentioned
therein.This document,or any related presentation,and SAP SE’s or its affiliated companies’ strategyand
possible future developments,products,and/or platform directions and functionalityare all subjectto change
and may be changed by SAP SE or its affiliated companies atany time for any reason withoutnotice.The
information in this documentis nota commitment,promise,or legal obligation to deliver any material,code,
or functionality. All forward-looking statements are subjectto various risks and uncertainties thatcould cause
actual results to differ materiallyfrom expectations. Readers are cautioned notto place undue reliance on
these forward-looking statements,which speak onlyas of their dates,and they should notbe relied upon in
making purchasing decisions.

Icons
Icon Meaning
Caution
Example
Note
Recommendation
Syntax
Typographic Conventions
Type Style Description
Example text Words or characters that appear on the screen. These include field
names, screen titles, pushbuttons as well as menu names, paths and
options.
Cross-references to other documentation.
Example text Emphasized words or phrases in body text, titles of graphics and
tables.
EXAMPLE TEXT Names of elements in the system. These include report names,
program names, transaction codes, table names, and individual key
words of a programming language, when surrounded by body text, for
example, SELECT and INCLUDE.
Example text Screen output. This includes file and directory names and their paths,
messages, source code, names of variables and parameters as well as
names of installation, upgrade and database tools.
EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the
ENTER key.
Example text Exact user entry. These are words or characters that you enter in the
system exactly as they appear in the documentation.
<Example text> Variable user entry. Pointed brackets indicate that you replace these
words and characters with appropriate entries.

Content
SAP Fiori Apps for ERP Baseline – Application MM .............................................................8
1 Purpose of SAP Fiori ...................................................................................................8
2 Overview Matrix for MM Fiori Apps ...............................................................................9
3 Content Relevance: Ready-to-Activate – Ready-to-Demo Versions .............................. 15
4 Transactional MM Apps ............................................................................................. 15
4.1 Approving Purchase Order ................................................................................... 15
4.1.1 Description .................................................................................................... 15
4.1.2 Key Features ................................................................................................. 15
4.1.3 Business Purpose for Approve Purchase Order................................................ 15
4.1.4 How to Access and Use the App ..................................................................... 16
4.1.5 Configuration for Baseline Scope Items ........................................................... 17
4.2 Order from Requisition ......................................................................................... 20
4.2.1 Description .................................................................................................... 20
4.2.2 Key Features ................................................................................................. 20
4.2.3 Business Purpose for Order from Requisition ................................................... 20
4.3 Tracking Purchase Order...................................................................................... 22
4.3.1 Description .................................................................................................... 22
4.3.2 Key Features ................................................................................................. 23
4.3.3 Business Purpose for Track Purchase Order.................................................... 23
4.4 Approving Purchase Contracts.............................................................................. 25
4.4.1 Description .................................................................................................... 25
4.4.2 Key Features ................................................................................................. 25
4.4.3 Business Purpose for Approve Purchase Contracts .......................................... 25
4.5 Approving Requisitions......................................................................................... 29
4.5.1 Description .................................................................................................... 29
4.5.2 Key Features ................................................................................................. 29
4.5.3 Business Purpose for Approve Requisitions ..................................................... 30

4.6 My Purchasing Document Items ............................................................................ 36
4.6.1 Description .................................................................................................... 36
4.6.2 Key Features ................................................................................................. 36
4.6.3 Business Purpose for My Purchasing Document Items ..................................... 36
4.7 Approve Service Entry Sheet ................................................................................ 38
4.7.1 Description .................................................................................................... 38
4.7.2 Key Features ................................................................................................. 38
4.7.3 Business Purpose for Approve Service Entry Sheet .......................................... 38
4.8 Approve Supplier Invoice ...................................................................................... 40
4.8.1 Description .................................................................................................... 40
4.8.2 Key Features ................................................................................................. 40
4.8.3 Business Purpose for Approve Supplier Invoices.............................................. 40
5 Analytical Apps MM................................................................................................... 45
5.1 SAP Smart Business Apps for Inventory Management............................................ 45
5.1.1 SAP Smart Business for Valuated Stock Value................................................. 45
5.1.1.1 Description ............................................................................................. 45
5.1.1.2 Key Features.......................................................................................... 45
5.1.1.3 Business Purpose................................................................................... 46
5.1.1.4 How to Access and Use the App .............................................................. 46
5.1.1.5 Configuration for Baseline ....................................................................... 47
5.1.2 SAP Smart Business App Valuated Stock Quantity........................................... 50
5.1.2.1 Description ............................................................................................. 50
5.1.2.2 Key Features.......................................................................................... 50
5.1.3 SAP Smart Business App Range of Coverage ................................................. 55
5.1.3.1 Description ............................................................................................. 55
5.1.3.2 Key Features.......................................................................................... 55

5.1.4 SAP Smart Business App Inventory Turnover .................................................. 59
5.1.4.1 Description ............................................................................................. 59
5.1.4.2 Key Features.......................................................................................... 59
5.2 SAP Smart Business Apps for Purchasing ............................................................. 64
5.2.1 SAP Smart Business App Non Managed Spend ............................................... 64
5.2.1.1 Description ............................................................................................. 64
5.2.1.2 Key Features.......................................................................................... 64
5.2.2 SAP Smart Business App Contract Usage ....................................................... 69
5.2.2.1 Description ............................................................................................. 69
5.2.2.2 Key Features.......................................................................................... 69
5.2.3 SAP Smart Business App Off Contract Spend .................................................. 73
5.2.3.1 Description ............................................................................................. 73
5.2.3.2 Key Features.......................................................................................... 73
5.2.3.3 Business Purpose of SAP Smart Business App Off Contract Spend ........... 74
5.2.4 SAP Smart Business App Contract Expiry........................................................ 78
5.2.4.1 Description ............................................................................................. 78
5.2.4.2 Key Features.......................................................................................... 78
5.2.5 SAP Smart Business App Unused Contracts.................................................... 82
5.2.5.1 Description ............................................................................................. 82
5.2.5.2 Key Features.......................................................................................... 82
5.2.5.3 Business Purpose of SAP Smart Business App Unused Contracts............. 82

6 Fact Sheets for MM ................................................................................................... 86

SAP Fiori Apps for ERP Baseline – Application
MM
1 Purpose of SAP Fiori
SAP Fiori is a collection of apps that represent the new SAP user experience. SAP Fiori apps
have a consistent design language and make use of a common technical infrastructure. They
provide a consistent end-to-end user experience and can be used across all device types without
creating additional implementation effort.
Organized by user role, the SAP Fiori launchpad is the central entry hub to all Fiori apps where
users access apps via tiles. The launchpad has services for navigation, personalization, single
sign-on, and search. The launchpad and the tiles are flexible and can be adapted to your needs.
You can use the search in the SAP Fiori launchpad to perform a cross-entity search through core
SAP Business Suite applications. The search uses the SAP NetWeaver Embedded Search
technology on a SAP HANA database. New SAP HANA-enabled search models are delivered for
core business objects.
The Fiori apps focus on critical and common activities and are designed around how people work:
 Role-based: Fiori apps decompose complex applications into a task-based experience with
one central entry point for each user.
 Responsive: Fiori apps adapt to all sizes, devices, versions, and channels to provide a
common user experience across all channels.
 Simple: Fiori apps follow the 1-1-3 experience (1 user, 1 scenario, 3 screens). They know and
provide the right context and meaningful data integration.
 Coherent user experience with apps that speak the same design language. This implies
coherence for common activities as well as coherence for your brand.
 Instant value with a low barrier to adoption, enabling customers to adapt and users to
personalize.
 Interactive on desktop, tablet, and mobile platforms
All UIs are built using state-of-the-art technology such as HTML5 and SAP UI5 mobile. Fiori apps
allow you to access the most recent version of your back-end data via OData services. Through
previously defined roles and authorizations, you can specify which apps and which data a user is
allowed to access.
The purpose of this document is to give the user all necessary information around the SAP Fiori
apps for MM to be able to run them on top of the SAP Best Practices MM processes.

The packages listed below are prerequisites for the configuration described in this
guide.
You will find references to the documentation belonging to these packages in the
corresponding chapters of this document:
 SAP HANA Live rapid-deployment solution:
http://service.sap.com/rds-shl
 SAP Fiori Infrastructure rapid-deployment solution:
http://service.sap.com/rds-fiori-infrastructure
 SAP Fiori Apps rapid-deployment solution:
http://service.sap.com/rds-fiori-apps
2 Overview Matrix for MM Fiori Apps
The following matrix shows the existing Fiori roles available within the MM application and the
assigned Fiori apps. The Fiori apps can be used within the mentioned baseline processes and
can replace an existing process step. It is important to understand that Fiori apps can replace
only single process steps and not a complete process. In other cases, Fiori apps offer
functionality to enhance existing processes.

Fiori Role Fiori App Short Description Mapping to Scope Item
(Baseline Scope Item) IDs
Fiori
Application
Type
SAP HANA
Mandatory
SAP_MM_BCR_Buyer_X1 PO Approval With Approve Purchase Orders,
you can view pending purchase
orders and approve them. If
necessary, you can forward
approvals to a different
employee for further processing.
Consumable Purchasing (129)
Procurement without QM (130)
Procurement Contract (133)
Procurement of Third-party
Resources (208)
Transactional No
SAP_MM_BCR_Buyer_X1 Order from
Requisition
With Order from Requisitions,
you can convert approved
purchase requisitions into
purchase orders. The app
assigns matching suppliers to
each purchase requisition, and
then bundles the requisitions to
create a purchase order for each
supplier.
Transactional No
SAP_MM_BCR_Buyer_X1 Track
Purchase
Order
With Track Purchase Order, you
can view important purchase
order information. For each
purchase order, the app shows
the overall order fulfillment
status, the quantities and
values, and a graphical view of
the process flow. If a purchase
order is based on purchase
requisitions, these documents
can be displayed.
Resources (208)
Transactional No

SAP_MM_BCR_Buyer_X1 Approve
Purchase
Contracts
With Approve Purchase
Contracts, you can view pending
purchase contracts and approve
them. If necessary, you can
forward approvals to a different
Procurement Contract (133) Transactional No
SAP_MM_BCR_Buyer_X1 Approve
Requisitions
With Approve Requisitions, you
can view pending purchase
requisitions and approve them. If
approvals to a different
Transactional No
SAP_MM_BCR_BUYER My
Purchasing
Document
Items
With My Purchasing Document
Items, you can display all
purchase orders, contracts, and
scheduling agreements in your
client.
Stock Transfer with Delivery
(134)
Return to Vendor (136)
Resources (208)
External Procurement of
Services (209)
Quality Management for
Procurement with Vendor
Evaluation (127)
Subcontracting (138)
Transactional No

SAP_MM_BCR_BUYER Approve
Service Entry
Sheet
With Service Entry Sheets, you
can view pending, service entry
sheets and approve them. If
approvals to different employee
for further processing.
Services (209)
Transactional No
SAP_MM_BCR_BUYER Approve
Supplier
Invoice
With Approve Supplier Invoice,
you can view pending, parked
supplier invoices and approve
them. If necessary, you can
forward approvals to different
Procurement of Third-Party
Resources (208)
Services (209)
Procurement and
Consumption of Consigned
Inventory (139)
Transactional No
Purchasing Apps Analytical
Contract
Usage
With Contract Usage, you can
compare the expected release
amount against the actual
release amount of contracts in a
specific time frame.
Procurement Contract (133) Analytical Yes
Non-managed
Spend
With Non-Managed Spend, you
can display the spend for
suppliers that was not matched
to a purchase order as a
percentage of the total spend.
All Baseline MM scope items Analytical Yes
Contract
Expiry
With Contract Expiry, you can
identify purchase contracts that
will expire within a specific time
frame.

Unused
Contracts
With Unused Contracts, you can
identify contracts for which a
release has not taken place
within a specific time frame.
Off-Contract
Spend
With Off-Contract Spend, you
can analyze the total spend
amount in relation to purchase
orders that do not have a
contract reference.
Contract (133) Analytical Yes
Inventory Management
Apps
Analytical
Valuated
Stock Value
With Valuated Stock Value, you
can display the closing valuated
stock value based on a specific
end date.
Stock Handling: Scrap and
Blocked Stock (131)
Resources (208)
Evaluation (127)
Procurement and
Inventory (139)
Physical Inventory / Inventory
Count & Adjustment (137)
Analytical Yes

Valuated
Stock Quantity
With Valuated Stock Quantity,
you can display the closing
valuated stock quantity based
on a specific end date.
Stock Handling: Scrap and
Blocked Stock (131)
Resources (208)
Evaluation (127)
Procurement and
Inventory (139)
Physical Inventory / Inventory
Count & Adjustment (137)
Analytical Yes
Range of
Coverage
With Range of Coverage, you
can determine how long your
company can manage with the
current stock, based on the
determined consumption of
stock in the past.
Procurement and
Inventory (139)
Analytical Yes
Inventory
Turnover
With Inventory Turnover, you
can determine how often the
average material was destocked
and restocked in a specific time
frame.
Analytical Yes

3 Content Relevance: Ready-to-Activate –
Ready-to-Demo Versions
For the Ready-to-Activate version, the complete content described in this document is relevant.
For the Ready-to-Demo version, you can skip all the chapters which treat configuration topics.
The following subchapters are relevant for each Fiori application:
 Description
 Key Features
 Business purpose
 Procedure
4 Transactional MM Apps
4.1 Approving Purchase Order
4.1.1 Description
With Approve Purchase Orders, you can view pending purchase orders and approve them. If
necessary, you can forward approvals to a different employee for further processing.
4.1.2 Key Features
 You can search for specific purchase orders.
 You can display details for each purchase order, for example, the line items with detailed
information, such as account assignment and conditions.
 You can approve or reject purchase orders, and you can forward them to a colleague.
4.1.3 BusinessPurposefor Approve PurchaseOrder
This app can be seen as an enhancement of our existing baseline scope items and can be used
as replacement of the approve purchase order transaction ME29N.
As opposed to the standard transaction, the purchasing manager or buyer can use this
transactional app to quickly get information about a purchase order, for example, conditions, and
can approve, reject or forward it. Under this assumption, this app can be used together with
several scope items. In the following, you find the scope items for which this app fits best from a
business perspective:
See master data listed in the Business Process Documentation for the scope item:

Purchase Order Type Standard PO, for example, NB
Purchasing Organization 1000
Purchasing Group 100
Vendor 300000
Order Type Standard PO, for example, NB
Vendor 300000
Plant 1000
Vendor 300000
Plant 1000
Procurement of Third-party Resources (208)
Vendor 300100
Plant 1000
Vendor 300000
Plant 1000
4.1.4 How to Access and Use the App
1. Launch the SAP Fiori system via the appropriate URL and log on with the appropriate user
and password for the buyer.
2. From the home page, click the tile for Approve Purchase Order.
A list of purchase orders appears.

3. Select a purchase order depending on the process for which you want to run the application.
You can use the Search field to find a purchase order (search by supplier name or purchase
order number), and then select the purchase order.
A list of possible purchase orders is displayed. Purchase order details include account
assignment, delivery date, delivery plant and inco terms.
4. To approve a purchase order, select the order and choose Approve in the lower right corner.
4.1.5 Configuration for Baseline Scope Items
The following section includes a short checklist for the necessary configuration steps for the
activation and usage of the app. Details are described in the relevant configuration guides for the
SAP Fiori Apps rapid-deployment solution and the SAP Fiori Infrastructure rapid-deployment
solution.
1. User role in the backend system via transaction PFCG:
Assign the necessary backend role for the Approve Purchase Order Fiori app in the ERP
system to the user used for the launchpad logon. For details, see Configuration Guide: SAP
Fiori Apps for SAP ERP - Logistics (MEV).
Approve Purchase Order SAP_MM_PO_APV_APP
2. Activation of gateway service in the SAP gateway server with transaction
/IWFND/MAINT_SERVICE :
For details on how to perform this step, see SAP Fiori Apps for SAP ERP - Logistics (MEV),
chapter Activation of Gateway Service in SAP NetWeaver Gateway. Use the following values:
Fiori App Name Field Name Entry Value
Approve Purchase
Order
System Alias <SYSTEM ALIAS of ERP>
External Service
Name
gbapp_poapproval
3. Activate gateway and UI5 services with transaction SICF in the gateway server:
Fiori App Name Service Path Service Name
Approve
Purchase Order
sap → opu → odata →
sap
gbapp_poapproval (1)
sap → bc → ui5_ui5
→sap
MM_PO_APV
4. Assign a user to the SAP Fiori launchpad
For details on how to perform this step, see the SAP Generic Fiori Enablement Guide (MF1),
chapter Assign a User to the SAP Fiori Launchpad. Use the following values:
App Approve Purchase order

Role SAP_MM_BCR_Buyer_X1
The role must be assigned to the user used during launchpad logon with transaction PFCG.
The user needs to be maintained in the gateway server.
5. Create the following settings in addition to the Customizing of the Baseline package:
Before implementing the app, you must ensure the following:
 You use the release strategy in Purchasing (MM-PUR).
 You have set up a connection between the release strategy and SAP Business Workflow.
 You have configured the approval workflow for approving purchase orders.
 The business users that will use the Approve Purchase Orders app have the
authorizations required for approving purchase orders in the SAP GUI.
 To enable Approve Purchase Orders, you have specified the workflow tasks that are
relevant for approving purchase orders. You do this in the Customizing for Materials
Management under Purchasing → Purchase Order → Approve Purchase Orders App →
Specify Workflow Task IDs for Approve Purchase Orders App.
6. Configuration Details in Connection with the Baseline Customizing:
1. Go to the SAP Customizing Implementation Guide (transaction SPRO): Materials
Management → Purchase Order → Release Procedures for Purchase Orders → Edit
Characteristic:
o R2R_PURCH_GRP
o R2R_PURCH_ORD_TYPE
o R2R_PURCH_ORD_VALUE
2. Choose Edit Class. Remove char R2R_PURCH_GRP and R2R_PURCH_ORD_VALUE
from class R2R_CL_REL_CEKKO (class type: 032).
3. Choose Define Release Procedure and change the release strategy configuration:
o Create release group V_T16FG_2 – No Change
o Create release code VV_T16FC_2 – Enter 01 in the Code column
o Select release indicator: No changes in release indicators
o Select release group PH and display the details and go back.
o Select release code and enter workflow 1.

o Save and go back.
o Select Workflow and enter the Agent ID (corresponds to the user in your system who
has to approve the purchase orders)
o Access transaction PFTC. Enter Workflow Template and workflow 20000075.
o Choose the Triggering events tab.
Alternatively, choose Basic Data (Hat symbol in the application toolbar) in the
workflow definition.
o Select the step and choose Call binding editor. Run the check and activate it (Event
Setting → Event Linkage activated)
o Access transaction SWDD and enter WS20000075 to verify that the binding is correct.
Select Release of purchase order and choose Enter.
o Make sure the binding for TS20000166 and rule 20000027 with Agent Assignment
on:
Note that CFO has to be replaced with the user in your system who is defined to
release purchase orders.

o After you have added the required configuration settings, you can run the app
together with the SAP Best Practices Baseline Customizing.
The app does not work with stock transfer orders. The supported item categories for
this app are: standard, service, and limit.
In the current SAP Best Practices Baseline Customizing, release strategies have
been set up for PO Header.
Workflow is not in scope for PO Release Strategies in the current Baseline scope.
As a result, these Customizing changes lead to a different behavior compared to
what is described in the original Baseline business process documentation.
4.2 Order from Requisition
4.2.1 Description
With Order from Requisitions, you can convert approved purchase requisitions into purchase
orders. The app assigns matching suppliers to each purchase requisition, and then bundles the
requisitions to create a purchase order for each supplier.
 Order from Requisitions is not optimized for use with a phone. Please use a
tablet or desktop device.
 Order from Requisitions does not support service items.
4.2.2 Key Features
 Display approved purchase requisitions that are not yet assigned to suppliers
 Assign suppliers to a selected set of purchase requisitions
 Select the relevant supplier if multiple suppliers can deliver the product
 Bundle a selected set of purchase requisitions by supplier and simulate the purchase
orders (one purchase order per supplier)
 Review simulated purchase orders
 Create purchase orders
4.2.3 BusinessPurposefor Order from Requisition
This app can be seen as an enhancement of the existing SAP Best Practices Baseline scope
items in which purchase orders are created out of requisitions. The app allows you to execute a
lot of steps in a single interface: Assign suppliers, simulate purchase orders, and finally, create
the purchase orders. In contrast to the standard transaction, you can use the simulated purchase
order as a collector for requisitions.
Under this assumption, this app can be used together with several scope items. In the following,
you find the scope items for which this app fits best from a business perspective:

Vendor 300000
Plant 1000
Vendor 300000
Plant 1000
and password for the purchaser.
2. From the home page, choose the tile for Order from Requisitions.
3. If no data is selected, choose the Approved PRs button to get a list of approved purchase
requisitions. Select a purchase requisition via the checkmark. To assign a supplier, choose
the Assign Supplier button in the lower right corner.
4. The purchase requisition now appears under assigned purchase requisition. To display it,
choose Assigned PRs above.
5. You can now simulate a PO for this purchase requisition.
6. This simulated PO now is listed under simulated POs. To display it, choose Simulated POs
above.
The following section includes a short checklist for the necessary configuration steps that are
required for the activation and usage of the app. Details are described in the relevant
configuration guides for the SAP Fiori Apps rapid-deployment solution and the SAP Fiori
Infrastructure rapid-deployment solution.
Assign the necessary backend role for the Order from Requisition Fiori app in the ERP
Order from Requisition SAP_MM_PURORD_OR_APP

Order from
requisition
External Service
Name
sra013_po_from_pr_srv (1)
chapter Activate Gateway and UI5 Services.
Order from
requisition
sap
sra013_po_from_pr_srv (1)
sap → bc → ui5_ui5 →
sap
MM_PURORD_OR
App Order from Requisition
Role SAP_MM_BCR_Buyer_X1
The Order from Requisitions Fiori app does not require any additional Customizing
settings to be able to run on the SAP Best Practices Baseline Customizing.
The app does not work with stock transfer requisitions which are used in the SAP
Best Practices Baseline scope item 134. The supported item categories for this app
are: standard, service, and limit.
To find a purchase requisition in the app, set a filter (for example, release date) and
search by using the scroll bar.
4.3 Tracking Purchase Order
4.3.1 Description
With Track Purchase Order, you can view important purchase order information. For each
purchase order, the app shows the overall order fulfillment status, the quantities, values, and a

graphical view of the process flow. When a purchase order is based on purchase requisitions,
these documents can be displayed.
4.3.2 Key Features
The following documents can be displayed for each purchase order:
 Purchase requisition
 Goods receipt
 Invoice
4.3.3 BusinessPurposefor TrackPurchase Order
items in which purchase orders are created. The app is intuitive and user friendly and allows you
to display a lot of information in a single interface: for each purchase order, the app shows the
overall order fulfillment status, the quantities and values, and a graphical view of the process flow.
If a purchase order is based on purchase requisitions, these documents can be displayed.
Purchase Order Type Standard PO, for example, NB
Purchasing Group 100
Vendor 300000
Vendor 300000
Plant 1000
Vendor 300000
Plant 1000
Vendor 300100

Plant 1000
2. From the home page, choose the tile for Track Purchase Orders.
3. You can search for purchase orders by company name or purchase order ID.
4. You can also set a filter defining the time frame when the purchase orders were created or
search for purchase orders with alerts.
5. The purchase order is then displayed on the right side of the app.
6. You can now display ordered, invoiced and paid items.
Assign the necessary backend role for the Track Purchase Order Fiori app in the ERP system
to the user used for the launchpad logon. For details, see configuration guide SAP Fiori
Purchase Agent (MEF).
Track Purchase Order SAP_MM_PURORD_TPO_APP
Track Purchase
Order
External Service
Name
sra020_po_tracking_srv (1)

Track Purchase
Order
sap
sra020_po_tracking_srv (1)
→sap
MM_PURORD_OR
App Track Purchase Order
Role SAP_MM_PURORD_TPO_APP
The Tracking Purchase Order Fiori app does not require any additional Customizing
settings to be able to run on the SAP Best Practices Baseline Customizing.
The app cannot be used for stock transfer orders. Purchase orders with the order
type NB are supported by this app. The supported item categories for this app are:
standard, service, and limit work.
Currently, if you want to display a purchase order, you have created in the system,
you can enter the PO number directly in the search field of the app.
4.4 Approving Purchase Contracts
4.4.1 Description
With Approve Purchase Contracts, you can view pending purchase contracts and approve them.
If necessary, you can forward approvals to a different employee for further processing.
4.4.2 Key Features
 You can search for specific contracts.
 You can display details for each contract
 You can approve contracts and forward them to colleagues.
4.4.3 BusinessPurposefor Approve PurchaseContracts
items in which purchase contracts are created. The app allows you to display a lot of information

in a single interface: for example, line items with detailed information, such as conditions, target
quantities, and target values. In the same interface, the purchase contract can be approved and
also forwarded. This collaboration is not possible in the standard GUI.
Vendor 300000
Plant 1000
and password for the purchasing manager or agent.
2. From the home page, choose the tile for Approve Purchase Contracts.
3. In the search field on the left, you can search for the respective purchase contracts. As a
result, the purchase contract with all details is displayed on the right side of the app.
4. You can select the Approve button on the lower right corner to approve the purchase contract,
or you forward it to a colleague instead.
Assign the necessary backend role for the Approve Purchase Contract Fiori app in the ERP
Approve Purchase
Contract
SAP_MM_PC_APV_APP
Approve Purchase System Alias <SYSTEM ALIAS of ERP>

Contract External Service
Name
sra001_pcapproval (1)
Approve
Purchase
Contract
sap
sra001_pcapproval (1)
→sap
MM_PC_APV
chapter Assign a User to the SAP Fiori Launchpad, and use the following values.
App Approve Purchase Contract
Role SAP_MM_PC_APV_APP
5. Change the following settings in the SAP Best Practices Baseline Customizing:
 You need to set up the release strategy in Purchasing (MM-PUR).
 You have configured the approval workflow for approving purchase contracts
Detailed steps:
Management → Purchasing → Contract → Release Procedure for contracts
2. Choose Edit Characteristics. Enter the characteristic R2R_PURCH_ORD_TYPE and
add the values MK (Quantity Contract), WK (Value Contract) .
3. Go to Release Groups and create release group P1:
4. Go to Release Codes and create release code P1:

5. Release indicator: no change.
6. Go to Release Strategy and create the following settings:
 Group: P1
 Strategy: 10
 Description: Overall Release
7. Select release group P1 and go to details.
8. Go to Classification and select Quantity Contract (MK) in the Value field.
9. Go to Workflow and Assign release code to a release point (only with workflow)
Select the object type user (US) and enter the user who can approve purchasing
contracts:
You have to exchange CFO with the user in your system who is authorized for the
approval of purchasing contracts.
10. Go to transaction PFTC:
 Choose the task type: Workflow templates
 Enter the task: 20000079
 Choose Maintain and go to the Triggering Events tab.
 Choose the button on the left in first line to activate the binding.
11. Go to transaction SWDD:
 Enter workflow: 20000079
 Under Steps, select the line : Release of contract

 On the right side of the screen, enter the task: TS20000172
 Choose the Define Binding Autom. button.
 Under Agents, select Rule and enter 20000029.
12. Choose the Define Binding Autom. button.
 Select Agent Assignment
 Select the Create Agent Assignment button from the menu.
 Enter the user who should approve purchasing contracts in your system.
In the standard SAP Best Practices Baseline Customizing, no approval for purchase
contracts has been set up. Therefore, the specific Customizing for this app will influence
related Baseline scope items.
4.5 Approving Requisitions
4.5.1 Description
With Approve Requisitions, you can view pending purchase requisitions and approve them. If
necessary, you can forward approvals to a different employee for further processing.
4.5.2 Key Features
 You can search for specific purchase requisitions.
 You can display detailed information for purchase requisitions, for example, account
assignment or attachments.

 You can approve or reject items of a purchase requisition, and you can forward them to
colleagues.
 Only approval at item level is supported; that is, you can approve the items of requisitions
individually. Approval at header level, that is, overall release of a purchase requisition, is
not supported.
 You see only the purchase requisitions for which you are responsible.
4.5.3 BusinessPurposefor Approve Requisitions
items in which purchase requisitions are created. The app allows you to display a lot of
information in a single interface: for each purchase requisition, the app shows material, quantity,
price per unit and so on. You can navigate to the details of the supplier. With one click, you can
either approve, reject, or forward the requisition.
Vendor 300000
Plant 1000
Vendor 300000
Plant 1000
2. From the home page, choose the tile for Approve Requisitions.
3. You can search for a purchase requisition by purchase requisition ID.
The purchase requisition is then displayed on the right side.
4. You can now approve, reject, or forward it by selecting the buttons in the lower right corner.

Assign the necessary backend role for the Approve Requisitions Fiori app in the ERP system
to the user used for the launchpad logon. For details, see Configuration Guide: SAP Fiori
Apps for SAP ERP - Logistics (MEV).
Approve Requisitions SAP_MM_PR_APV_APP
Approve
Requisitions
External Service
Name
gbapp_prapproval (1)
Approve
requisitions
sap
gbapp_prapproval (1)
→sap
MM_PR_APV
App Approve Requisitions
Role SAP_MM_PR_APV_APP
5. Change the following settings in the SAP Best Practices Baseline Customizing:
 You need to set up the release strategy in Purchasing (MM-PUR).
When customizing the release strategy, you do not use overall release. This setting is
intended for approval at header level, which is not supported for this app.
 You have configured the approval workflow for approving purchase requisition items.

 To enable Approve Requisitions, you must specify the workflow tasks that are relevant
for approving purchase requisitions. You do this in the Customizing for Materials
Management under Purchasing → Purchase Requisition → Approve Requisitions App →
Specify Workflow Task IDs for Approve Requisitions App.
Detailed steps:
Management → Purchasing → Purchase requisitions → Release procedure →
Procedure with classification
2. Go to Characteristics and create the following characteristics:
 R2R_PLANT: Navigate to the Addnl Data tab and enter table name CEBAN and
field name WERKS:
 Navigate to the Values tab, and in the Char Value field, enter 1000, and as
description Plant 1000:
 R2R_PURCH_REQ_TYPE - with NB: Navigate to the Addnl data tab and enter
table name CEBAN and field name BSART.

 Navigate to the Values tab, and in the Char Value field, enter NB, and as
description Purchase Req:
13. Go to Edit Classes and create the class FGR_EBAN. Assign the characteristics
R2R_PURCH_REQ_TYPE and R2R_PLANT.
14. Create a PR Release Strategy:
 Choose Set up procedure with classification. Go to Release Groups and create
the following release group:
 Go to Release Code and create the following release code:
 Release indicator – No Change
15. Go to Release Strategies and create the following release strategy:

16. Go to classification and enter the following values for the characteristics:
17. Save and go back.
18. Choose Workflow and select user (US) and enter the user who can approve
purchase requisitions in your system:
19. Access transaction PFTC:
1. Choose workflow template and enter 00000038.
2. Go to the Triggering Events tab.
3. Activate the binding in the first line and save.
20. Access transaction SWDD :
1. Enter workflow WS00000038.

2. In the Navigation Area, choose Release Requisition.
3. In the right part of the screen, enter task TS00007986.
5. Under Agents, select Rule and enter 00000148.
7. Choose the Agent Assignment button for this task.
8. On the Standard task: Maintain Agent Assignment screen, choose the Create
Agent Assignment button:
The app cannot be used for stock transfer purchase requisitions (Stock Transfer with
Delivery (134)). The supported item categories for this app are: standard, service,
and limit.
In the standard SAP Best Practices Baseline Customizing, no approval for purchase
requisitions has been set up. Therefore, the specific Customizing for this app will
influence related Baseline scope items.

4.6 My Purchasing Document Items
4.6.1 Description
With the My Purchasing Document Items app, you can view purchase orders, scheduling
agreements and contracts.
4.6.2 Key Features
 You can search across any relevant searchable fields such as material, purchasing group and
supplier and so on.
 You can search by status such as overdue, confirmation missing and so on.
 Grouping feature that allows you to quickly see which documents belonging to a specific
supplier and so on are relevant for processing in one go with all related documents
4.6.3 BusinessPurposefor My PurchasingDocumentItems
items where purchase documents are created. The app allows you to display several items of
information in a single interface: as purchaser, you need to identify which POs are not confirmed,
are behind delivery schedule or are over-fulfilled without having to search various places. You
need to be able to quickly find a PO by material, cost center and so on
Under this assumption, this app can be used together with most of the MM scope items.
2. From the home page, choose the tile for My Purchasing Document Items.
3. You can search for the purchasing document via entering material, purchasing group etc.
4. You can display all document types or only POs , contracts and so on.
5. To group, for example, POs by material group, choose the Group By button in the upper
right corner.
Additional documentation is available in the SAP Help Portal:
http://help.sap.com/fiori_bs2013/helpdata/en/ff/83425323a71f37e10000000a423f68/content.htm?
frameset=/en/ff/83425323a71f37e10000000a423f68/frameset.htm&current_toc=/en/ba/954353a5
31e647e10000000a441470/plain.htm&node_id=267

Assign the necessary backend role for the My Purchasing Document Items Fiori app in the
ERP system to the user used for the launchpad logon. For details, see Configuration Guide:
Generic Enablement of SAP Fiori (MF1).
My Purchasing Document Items SAP_MM_PURDOC_LIST_APP
For details on how to perform this step, see Generic Enablement of SAP Fiori (MF1)., chapter
Activation of Gateway Service in SAP NetWeaver Gateway. Use the following values:
My Purchasing
Document Items
External Service
Name
ME2STAR_OD_SRV (1)
Activate Gateway and UI5 Services.
Fiori App
Name
Service Path Service Name
My
Purchasing
Document
Items
sap → opu →
odata → sap
ME2STAR_OD_SRV (1)
sap → bc →
ui5_ui5 →sap
/default_host/sap/bc/ui5_ui5/sap/mm_purd
oc_list
Assign a User to the SAP Fiori Launchpad. Use the following values:
App My Purchasing Document Items
Role SAP_MM_PURDOC_LIST_APP
Before configuring the app, you must ensure the following:
 The implementation must be based on SAP NetWeaver SP06 or higher.
 You must ensure that the business users who use the My Purchasing Document Items app
have the authorizations required for displaying purchase orders, contracts and scheduling
agreements in the SAP GUI. In addition, you can grant authorization to users so that they will
see price information in purchase order items.
You do not have to perform any changes in the Baseline customizing.

4.7 Approve Service Entry Sheet
4.7.1 Description
The app enables you to quickly and efficiently process the approval of service entry sheets
entered by a service provider while away from your desk.
Value, service location, service period, accounting data, service lines, notes and attachments can
be quickly checked via this app in one go.
4.7.2 Key Features
 List of pending service entry sheets
 Display of all details relevant for approval decision
 Detailed business card of the creator of the service entry sheet
 Reject service entry sheets
 Search and sort function
 Approve service entry sheet
 Reject service entry sheet with a note
4.7.3 BusinessPurposefor Approve Service Entry Sheet
items where service entry sheets are created.
Under this assumption, this app can be used together with the following scope items:
External Procurement of Services (209)
2. From the home page, choose the tile for Approve Service Entry Sheets.
3. In the search field on the left, you can search for a service entry sheet. The service entry
sheet is then displayed on the right side of the app.
A short text is displayed as key information, the business card of the service entry sheet
creator, header details, fulfillment status: percentage of consumed value and consumed value.
You can also display attachments linked to the service entry sheets.
4. You can now approve, reject or forward it by selecting the buttons in the lower right corner.

http://help.sap.com/fiori_bs2013/helpdata/en/64/1a96523ef7224fe10000000a445394/content.htm
?frameset=/en/ff/83425323a71f37e10000000a423f68/frameset.htm&current_toc=/en/ba/954353a
531e647e10000000a441470/plain.htm&node_id=251
Assign the necessary backend role for the Approve Service Entry Sheets Fiori app in the
ERP system to the user used for the launchpad logon. For details, see Configuration Guide:
Approve Service Entry Sheets SAP_MM_SES_APV_APP
Approve Service
Entry Sheets
External Service
Name
MM_SES_APPROVE (Version 0001)
Fiori App
Name
Approve
Service
Entry
Sheets
sap → opu →
odata → sap
MM_SES_APPROVE (Version 0001)
sap → bc →
ui5_ui5 →sap
MM_SES_APV — Description: Approve
Service Entry Sheets
App Approve Service Entry Sheets
Role SAP_MM_SES_APV_APP

You have to perform changes in the Baseline customizing:
The existing release procedure for service in the Baseline customizing has to be
modified:
Management → External Services Management → Define Release Procedure
for Services Entry Sheet → Select Release Strategies → Change Release
Strategy Y1:
2. Choose Classification and enter the order type NB.
3. Under Purchasing group, the group YQ4 is configured for this release procedure
in the SAP Best Practices Baseline Customizing. Therefore, in the
corresponding purchase order for services (with item category D), the purchase
groups YQ4 has to be used when the PO is created.
4.8 Approve Supplier Invoice
4.8.1 Description
With the transactional app Approve Supplier Invoices, you can display supplier invoices that are
assigned to you by SAP Business Workflow. You can approve or reject the corresponding work
item. If necessary, you can forward a work item to a different employee for further processing.
You can use the standard workflow to approve completely parked incoming invoices.
4.8.2 Key Features
 List of invoices that need approval including search functionality
 Details of supplier invoice including attachment of the original invoice document
 Business card of responsible purchaser and invoice clerk for easy contact
 Reference to purchase order
 Add own notes to the approval process
 View history of previously approved and rejected invoices from the same supplier
 Approve, reject and forward invoices
4.8.3 BusinessPurposefor Approve SupplierInvoices
This app can be seen as an enhancement of our existing SAP Best Practices Baseline scope
items where supplier invoices are created.
Under this assumption this app can be used together with the following scope items from the
Baseline:
ProcurementwithoutQM(130)

External Procurementof Services(209)
Procurement and Consumption of Consigned Inventory (139)
2. From the home page, choose the tile for Approve Supplier Invoices.
3. In the Search field, you can search for a supplier invoice by entering related information, for
example, supplier. The supplier invoice is then displayed on the right side.
In the detail view, you can navigate between several tabs:
 Attachments
You see a list of all files that are attached to the invoice document. Depending on your
browser and settings, as well as the file type of the attachment, the attachment is
displayed either in a new browser tab or in a window of a program corresponding to the
file type.
 Notes
You can add notes, which are displayed on the Notes tab with a time stamp. These notes
are only attached to the work item of the app.
 Info
You see information data.
In the Purchase Order field, you see the purchase order number. If there is more than
one purchase order, the total number is displayed as additional information (for example:
(1 of 2)).
 History
You see a list of invoices you received from the current supplier and that you have
already approved.
4. You can now approve, reject or forward it by selecting the buttons in the lower right corner.
http://help.sap.com/fiori_bs2013/helpdata/en/8b/98ef5249620375e10000000a44538d/content.ht
m?frameset=/en/ff/83425323a71f37e10000000a423f68/frameset.htm&current_toc=/en/ba/95435
3a531e647e10000000a441470/plain.htm&node_id=298

Assign the necessary backend role for the Approve Supplier Invoices Fiori app in the ERP
system to the user used for the launchpad logon. For details, see Configuration Guide:
Approve Supplier Invoices SAP_MM_SES_APV_APP
Approve Supplier
Invoices
External Service
Name
MM_SUPPLIER_INVOICE_APPROVE (1)
Fiori App
Name
Approve
Supplier
Invoices
sap → opu →
odata → sap
MM_SUPPLIER_INVOICE_APPROVE (1)
sap → bc →
ui5_ui5 →sap
MM_SUPPLINV_APV
App Approve Supplier Invoices
Role SAP_MM_SUPPLINV_APV_APP
The following Customizing has to be created for the app:
 You have specified the workflow tasks that are relevant for approving supplier invoices. You
do this in Customizing for Materials Management under Logistics Invoice Verification → Apps
for Logistics Invoice Verification → Approve Supplier Invoices → Specify Workflow Task IDs.
 To set up the standard workflow in your back-end system, you must assign a
release group to the vendor and to the workflow agent, define the release

criteria, and activate the workflow for assigned agents. For more information,
see Customizing activity Specify Workflow Task IDs.
 For the standard workflow and standard task, you can display the relevant
invoices in the back-end system using the SAP Business Workplace transaction
(SBWP). The invoices are grouped in the inbox according to the Invoice Parking:
Approve Release task.
 For completely parked incoming invoices, you have created the following transactional back-
end data for the vendor assigned to the release group:
 You have created a purchase order (transaction ME21N).
 You have posted a goods receipt (transaction MIGO), if the master data requires it.
 You have parked the incoming invoice, saved as completed, and created an attachment
(transaction MIR7).
You have to perform the following changes in the SAP Best Practices Baseline Customizing:
1. Go to the SAP Customizing Implementation Guide (transaction SPRO): Logistics Invoice
Verification → Define Release Criteria. Enter the following values.
Note that BPINST corresponds to the user who is authorized to release supplier
invoices in your system.
2. Choose Activate Workflow Template for Release for Posting
3. Choose Activate Event Linking.
4. Activate the workflow:

5. Access transaction SWDD. Enter the workflow: WS20001004.
6. Select the step Invoice Release.
7. On the right part of the screen, choose the Control tab.
8. Enter the task: Task ID: TS20000881
9. Make sure that the binding exists:
10. In the Task Properties section, choose the yellow Agent assignment for task button.
11. Enter the user who is allowed to release parked supplier invoices in your system.
13. Enter the release group 0001 into the vendor master data record of the respective
vendors whose invoices should be released via the app:

5 Analytical Apps MM
Be aware that the following settings (filters, dimensions, measures and so on) are
examples. You should configure these analytical apps according to your business
requirements and focus of interest.
5.1 SAP Smart Business Apps for Inventory
Management
5.1.1 SAP SmartBusiness for Valuated Stock Value
5.1.1.1 Description
With Valuated Stock Value, you can display the closing valuated stock value based on a specific
end date. The closing stock enables you to get an overview of the distribution according to the
dimensions plant, type of material, or product hierarchy. This information about the aggregated
stock situation allows you to react in a timely manner.
5.1.1.2 Key Features
 Display the closing valuated stock value based on a specific end date.
 Get an overview of the distribution according to the dimensions plant, type of material, or
product hierarchy.

 Calculation Rule:
The closing valuated stock value is the key date value at the end of a specific time frame. To
determine the valuated stock, all relevant postings, for example, all goods movements or
price changes, are considered.
5.1.1.3 BusinessPurpose
items in which goods are received or issued. A warehouse manager, for example, can quickly get
an overview about the current stock situation.
You may consider using the Valuated Stock Value app for the following scope items:
 Procurement without QM (130)
 Stock Handling: Scrap and Blocked Stock (131)
 Return to Vendor (136)
 Procurement of Third-party Resources (208)
 Quality Management for Procurement with Vendor Evaluation (127)
 Procurement and Consumption of Consigned Inventory (139)
 Physical Inventory / Inventory Count & Adjustment (137)
5.1.1.4 How to Access and Use the App
1. Launch Fiori launchpad in your browser. (Example URL:
https://[server]:[port]/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html )
2. On the home screen, choose Show Groups at the upper left corner. A panel with all available
groups appears on the left-hand side.
3. Choose the group you have created for this app, for example, SAP Smart Business Valuated
Stock Value. All tiles you have configured for this app appear under this group.
4. If you have defined generic drill-down or custom drill-down for a tile, you can click the tile,
which brings you to the drill-down app.
 If it is a generic drill-down, you can view the following information based on your
configuration:
If you have enabled KPI Header Details, you can view the warning and critical
information prefilled from the KPI evaluation defined. You can also view a trend chart if
you have enabled and defined time series.
If you have enabled the filter functionality, you can find your specified filters which you
can use to filter the views below.
The views you have defined will also be displayed. If you have defined multiple views,
you can use the dropdown box to switch between them.
 If it is a custom drill-down, you will be directed to a custom program that has been
created. See also Business Process Description: Smart Business Apps based on SAP
HANA Live (H10)

5.1.1.5 Configuration for Baseline
KPI Definition
1. Launch KPI modeler in your browser. (Example URL:
https://[server]:[port]/sap/bc/ui5_ui5/sap/ca_kpi/modeler/index.html)
2. Choose the action menu in the bottom left corner. In the pop-up list, choose Add KPI.
3. On the Add New KPI screen, create the following entries:
Field Name User Action and Values Mandatory
Field
KPI Code Technical ID, for example, ZVSVKPI X
KPI Title The KPI Title appears in the launchpad later on X
Semantic Object A Semantic Object is not needed
Improvement
Direction
Indicates which kind of value of KPI is meaningful
for the application (Maximizing/Minimizing/Target):
Minimizing
X
Value Type Currency X
OData Path Path of the XSOData service file:
/sap/hba/r/ecc/odata/mm/im/kpi.xsodata
X
Measure Provide measure from Entity Set:
ClsgVltdStockValInCoCodeCrcy_E
X
4. Choose Save and Continue.
Add Evaluation
1. Select the Evaluations button and select Add Evaluation.
On the Add Evaluation screen, you can create or apply a variant, maintain parameters,
thresholds, trends, and set authorizations for users.
Field Name User Action and Values
Variant ID Technical code, for example, ZVSVEVALUATION
Variant Title Title of the variant
Filter Settings Define a filter, for example, client
Input Parameters You need to provide values for all defined input parameters from
the Entity Set. Check if the values exist in the backend system.
Add filter to: SAP Client, for example, 120
Plant, for example, 1000
Material, H11

Add Input Parameter P_StartDate, for example, 01.01.2014
P_EndDate, for example, 01.01.2014
2. Choose Next to go to the screen and enter the Evaluation Text:
Evaluation Text For example, Valuated Stock Value
The Evaluation Text later appears on the tile in the launchpad.
Scaling Factor Select the appropriate scaling factor based on the expected KPI
value.
Decimal Choose the appropriate decimal format, for example, 00.00
Unit For example, USD
3. Choose Next to go to the screen and enter the threshold:#
Target Define a target, for example, 500
Improvement
Direction
For Improvement Direction Target, the attributes below can be
maintained (optional).
Warning High Indicates threshold value for KPI (is displayed yellow)
Critical High Indicates threshold value for KPI (is displayed red)
You have defined your target KPI with target value 500, you have set the “Warning
High” to 550 and the “Critical High” to 600. This means, if the KPI value exceeds 500,
the color code with which it is displayed is yellow. If the value exceeds 550, it is
displayed red.
4. Choose Next.
5. On the Apply Trend screen, choose Activate and authorize. Select the users who should be
able to use this KPI.
6. Choose Finish.
7. Activate the KPI.
Go back to the home screen of the KPI modeler. Enter the KPI name in the Search field in the
right upper corner and press Enter.
Click the KPI tile. To activate the KPI, choose Activate.
8. To create visualization and tile type, open the menu to access Explore Visualizations in the
lower left corner.
9. Select Explore Visualizations.
Visualization can only be added for active KPIs and evaluations.
10. On the Manage Visualizations screen, select the corresponding evaluation on the left side of
the screen.

11. Choose Add Tile in the lower right corner.
12. In the Tile Type field, enter KPI Tile.
13. Select a tile format.
 Tile Type: for example, KPI Tile
 Tile Format: for example, Numeric Tile
14. Choose OK.
Drill-Down Definition
1. Choose Drill Down and choose Configure Details in the lower right corner.
On the Drill Down definition screen, create the following settings:
Show As For example, Chart and Table
Default View For example, Chart
Select Type For example, Bar
View Name Analyze Stock Value 1
Order By By Measure- Descending
2. Select Measures:
ClsgVltdStockValInCoCodeCrcy_E,
AvgVltdStockValInCoCodeCrcy_E,
3. Select Dimensions:
Client, Plant, Material, Start_Date, End_Date
Limit records to: 10
4. Activate KPI Header Details and Activate Filter by setting the switches to ON.
5. Define the Header Details by clicking KPI Header Details and Define Filter dimensions.
6. Save your drill-down configuration and leave the KPI modeler.
7. Display SAP Smart Business KPI in the Fiori launchpad:
1. Log on to the launchpad with the user that you assigned to the KPI.
2. Open the groups menu and create your own group (optional)
3. Open the tile catalog (make sure you have the necessary roles assigned to your user).
4. Search your tile with the KPI title you used during creation.
5. You can add tiles to your Fiori launchpad:
o If you choose the + button. The tiles are added to My Home.

o If you drag and drop the tiles to a specific group.
If you navigate back, the tile will appear on the launchpad start page.
For more information, refer to the following configuration guides:
service.sap.com/rds-shl → Find the content library:
Configuration Guide: HANA Model Configuration – Smart Business Apps (H70)
Configuration Guide: Smart Business Apps based on HANA Live Configuration (H71)
Configuration Guide: SAP Smart Business for Inventory Management based on HANA Live (H76)
5.1.2 SAP SmartBusiness App Valuated Stock Quantity
5.1.2.1 Description
With Valuated Stock Quantity, you can display the closing valuated stock quantity based on a
specific end date. The closing stock enables you to get an overview of the distribution according
to the dimensions plant, type of material, or product hierarchy. This information about the
aggregated stock situation allows you to react in a timely manner.
Query View: sap.hab.r.ecc.MaterialValStockOnDateQuery
Displays the closing valuated stock quantity on a specific end date
Calculation Rule:
The closing valuated stock quantity is the key date quantity at the end of a specific time frame. To
determine the valuated stock, all relevant postings, for example, all goods movements, are
considered.
The point in time, in this case, the day on which a business process took place, is important to
determine its share in the calculation result. This includes the calculation of average values and
quantities.
To get a realistic calculation of averages for all average inventories, a specific weighting
approach is used in the Inventory Management KPIs: for the calculation of each business
process, such as a goods receipt, the posting date is considered in relation to the number of days
within the specific time frame. The posting date of the business process itself is considered with
half a day.
items in which goods are received or issued. A warehouse manager, for example, can quickly get
an overview about the current stock situation and reduce the quantity and costs.
You may consider using the Valuated Stock Quantity app for the following scope items:
 Procurement without QM (130)
 Stock Handling: Scrap and Blocked Stock (131)

 Return to Vendor (136)
 Procurement of Third-party Resources (208)
 Quality Management for Procurement with Vendor Evaluation (127)
 Procurement and Consumption of Consigned Inventory (139)
 Physical Inventory / Inventory Count & Adjustment (137)
1. Open Fiori launchpad in your browser. (Example URL:
https://[server]:[port]/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html)
3. Choose the group you have created for this app, for example, SAP Smart Business Valuated
Stock Quantity. All tiles you have configured for this app appear under this group.
configuration:
HANA Live (H10)
KPI Definition

Field
KPI Code Technical ID, for example, ZZVSQKPI X
KPI Title Valuated Stock Quantity
The KPI Title later appears in the launchpad.
X
Improvement
Direction
Indicates which kind of value of KPI is meaningful
for the application (Maximizing/Minimizing/Target):
Minimizing
X
Value Type Quantity X
X
ClsgVltdStockQtyInValnUnit
X
Add Evaluation
Variant ID Technical code, for example, ZVSQEVALUATION
Variant Title Title of the variant, for example, VSQEVALUATION
Filter Settings Define a filter, for example, client = 120, plant = 1000, material =
H11, material type = HAWA
Verify that the respective value exist in the backend system.
Add Input Parameter Start_Date, for example, 01.01.2014
End-Date, for example, 31.12.2014
Evaluation Text For example, Valuated Stock Quantity
value. For example, Automatic
Decimal Choose the appropriate decimal format, for example, for US
0.000

Unit For example, Piece
Target Define a target, for example, 50
Improvement
Direction
For Improvement Direction Minimize, the attributes below can be
If your KPI is a minimizing KPI with target value 50, you have set the “Warning High”
to 100 and the “Critical High” to 350. This means, if the KPI value exceeds 100, the
color code with which it is displayed is yellow. If the value exceeds 350, it is displayed
red.
4. Choose Next.
able to use this KPI, for example, BPINST.
6. Choose Finish.
lower left corner.
the screen.
14. Choose OK.

Show As For example, Chart
View Name Analyze Stock Quantity 1
Order By By Measure- Ascending
2. Select Measures:
ClsgVltdStockQtyInValnUnit,
AvgVltdStockQtyInValnUnit
3. Select Dimensions:
Client, Plant, Material, Start_Date, End_Date
Limit records to: 10
4. Activate KPI Header Details and Activate Filter by setting the switches to ON.
5. To define the Header Details, choose KPI Header Details. Select Material and select the filter
dimensions: choose Plant, Material, Start Date, End Date.
6. Save your drill-down configuration and leave the KPI modeler.
7. Display SAP Smart Business KPI in the Fiori launchpad:
1. Log on to the launchpad with the user that you assigned to the KPI.
2. Open the groups menu and create your own group (optional)
3. Open the tile catalog (make sure you have the necessary roles assigned to your user).
4. Search your tile with the KPI title you used during creation.
5. You can add tiles to your Fiori launchpad:
o If you choose the + button. The tiles are added to My Home.
o If you drag and drop the tiles to a specific group.
If you navigate back, the tile will appear on the launchpad start page.
For more information, refer to the following configuration guides:
service.sap.com/rds-shl → Find the content library:
Configuration Guide: HANA Model Configuration – Smart Business Apps (H70)
Configuration Guide: Smart Business Apps based on HANA Live Configuration (H71)
Configuration Guide: SAP Smart Business for Inventory Management based on HANA Live (H76)

5.1.3 SAP SmartBusiness App Range of Coverage
5.1.3.1 Description
With Range of Coverage, you can determine how long your company can manage with the
current stock, based on the determined consumption of stock in the past.
Query view: sap.hba.r.ecc.MaterialValStockQuantityRngeOfCvrgQuery
Displays the range of coverage based on the current valuated stock quantity on a specific end
date.
This calculation enables warehouse managers to avoid critical situations, for example, an
impending shortfall regarding the range of coverage for a specific material.
This app makes sense in the Baseline scope items where stock is consumed or issued.
Calculation Rule:
Range of Coverage is the relation between the current valuated stock quantity divided by the
average consumption per day.
You may consider using this app for the following scope items:
 Procurement without QM
 Stock Handling: Scrap and Blocked Stock
 Stock Transfer with Delivery
 Stock Transfer without Delivery
 Return to Vendor
 Physical Inventory / Inventory Count and Adjustment
 Procurement and Consumption of Consigned Inventory
1. Open Fiori launchpad in your browser. (Example URL:
https://[server]:[port]/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html)
3. Choose the group you have created for this app, for example, SAP Smart Business Range of
Coverage. All tiles you have configured for this app appear under this group.

configuration:
HANA Live (H10)
KPI Definition
Field
KPI Code Technical ID, for example, ZROCKPI X
KPI Title Range of Coverage
The KPI Title later appears in the launchpad.
X
Improvement
Direction
Indicates which kind of value of KPI is meaningful for
the application (Maximizing/Minimizing/Target):
Maximizing
X
Value Type Number X
X
Entity Set Name of the OData Entity Set:
MaterialValStockQuantityRngeOfCvrgQuery
X
RangeOfCoverageInDays
X

Add Evaluation
Variant ID Technical code, for example, ZROCEVALUATION
Variant Title Range of coverage
Filter Settings Define a filter, for example, a specific purchasing organization.
Verify that the respective value exists in the backend system.
Add filter to: SAP Client, for example, 120
(Plant, for example, 1100; Material, H10; it depends if you want
to have an average value over all materials or if you want to
focus on one material, for example)
Add Input Parameter P_StartDate equal to, for example, 20140101
P_MaximumRngeOfCvrgInDays equal to, for example, 100
P_EndDate equal to, for example, 20141231
Evaluation Text For example, Range of Coverage
value.
Decimal Choose the appropriate decimal format, for example, 00.00
Unit For example, Days
Target Define a target, for example, 500 days
Improvement
Direction
For Improvement Direction Maximize, the attributes below can be
If your KPI is a maximizing KPI with target value 50, you have set the “Warning High”
to 100 and the “Critical High” to 350. This means, if the KPI value exceeds 100, the

color code with which it is displayed is yellow. If the value exceeds 350, it is displayed
red.
4. Choose Next.
able to use this KPI.
6. Choose Finish.
lower left corner.
the screen.
14. Choose OK.
Show As For example, Chart and Table
View Name Analyze Range of Coverage
Order By By Measure- Descending
2. Select Measures: RangeOfCoverageInDays
3. Select Dimensions: Client, Plant, Material, Start_Date, End_Date

How to guide-fiori-mm_en_xx

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to How to guide-fiori-mm_en_xx

Similar to How to guide-fiori-mm_en_xx (20)

More from Lokesh Modem

More from Lokesh Modem (20)

Recently uploaded

Recently uploaded (20)

How to guide-fiori-mm_en_xx