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

© SAP SE Page 28 of 28

SAP Fiori Apps for the SAP ERP Application PP

Copyright

© 2014 SAP SE or an SAP affiliate company. 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 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 of SAP SE (or an SAP affiliate company) in Germany and 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 by SAP SE and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company 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.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be 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. /


Contents

SAP Fiori Apps for ERP Baseline – Application PP 6

1 Purpose of SAP Fiori 6

2 Overview Matrix for PP Fiori Apps 7

3 Ready-to-Activate / Fully-Activated Version 11

4 Technical/System Prerequisites for Transactional Apps 11

5 Transactional PP Apps 12

5.1 General Configuration 12

5.2 Required SAP Notes 12

5.3 Technical Data 12

5.3.1 Back-End Components 12

5.3.2 Front-End Components: UI5 Application 13

5.3.3 Front-End Server: SAP Fiori Launchpad Components 13

5.3.4 Technical Requirements 14

5.3.5 Configuration and App Implementation for Baseline Processes 14

5.3.6 Assign User Roles in the Back-End System 14

5.3.7 Activation of Gateway Service in the SAP Gateway Server with Transaction 15

5.4 Material Requirements Planning 17

5.4.1 Business Purpose for Material Requirements Planning 17

5.4.2 Monitor Material Shortages 17

5.4.3 Manage Material Shortages 19

5.4.4 Monitor External Requirements 20

5.4.5 Manage External Requirements 21

5.4.6 Supported Scope Items 22

5.5 Production Order Handling 23

5.5.1 Business Purpose for Production Order Handling 23

5.5.2 Production Order Release 23

5.5.3 Confirm Production Operations 24

5.5.4 Confirm Production Orders 25

5.5.5 Supported Scope Items 26

6 Technical/System Prerequisites for SAP Smart Business Apps 26

7 Technical/System Prerequisites for Fact Sheets 27

8 Fact Sheets for PP 27

8.1 Fact Sheet for Production Order 27

8.1.1 Description 27

8.1.2 Navigation Targets 27

8.1.3 Transactions 27

8.1.4 Technical Requirements 27

8.1.5 Technical Data 28

SAP Fiori Apps for ERP Baseline – Application PP

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 PP to be able to run them on top of the SAP Best Practices MM processes.

© SAP SE Page 28 of 28

SAP Fiori Apps for the SAP ERP Application PP

2  Overview Matrix for PP Fiori Apps

The following matrix shows the existing Fiori roles available within the MM application and the assigned Fiori apps.

© SAP SE Page 28 of 28

SAP Fiori Apps for the SAP ERP Application PP

Fiori Role / Fiori App / Short Description / Mapping to Scope Item
(Baseline Scope Item) IDs / Fiori Application
Type / SAP HANA Mandatory /
Material Requirements Planner - Buy Scenarios Only / Monitor Material Shortages / You can monitor material shortages in a selected area of responsibility. You can specify a shortage definition and a time horizon to determine which materials you want to check. You can specify a shortage definition and a time horizon to determine which materials you want to check. / Make-to-Stock Production - Discrete Industry (MTS)* (145) / Transactional / No
Manage Material Shortages / You can check the coverage of your materials based on the settings you made in the Monitor Material Shortages app. To help you solve your shortages, the system proposes different solutions. You can simulate the solution to preview its effects and you can apply the solution that best solves your issue. / Make-to-Stock Production - Discrete Industry (MTS)* (145) / Transactional / No
Monitor External Requirements / You can monitor the uncovered requirements originating from sales orders and stock transport orders in a selected area of responsibility. You can specify a shortage definition and a time horizon to determine which uncovered external requirements you want to check. / Make-to-Stock Production - Discrete Industry (MTS)* (145) / Transactional / No
Manage External Requirements / You can check your uncovered and delayed items based on the settings you made in the Monitor External Requirements app. To help you cover your external requirements, the system proposes different solutions. You can simulate the solution to preview its effects and you can apply the solution that best solves your issue. / Make-to-Stock Production - Discrete Industry (MTS)* (145) / Transactional / No
SAP Production Planning & Control / Confirm Production Orders / A production worker can perform partial or final confirmations for production orders through a simplified and intuitive UI. The app provides fast order input and simplified order confirmation procedures that are available for desktop, tablet, and mobile. / Make-to-Stock Production - Discrete Industry (MTS)* (145) / Transactional / No
Confirm Production Operations / Production workers can view and confirm order operations released to their work centers. They can search for the next order operation that they want to confirm by its number or confirmation number. They can use various sorting and filtering options that speed up and simplify the search for an order operation that they want to confirm. Production workers can partially or finally confirm a production order operation anytime and from any place using various mobile devices. / Make-to-Stock Production - Discrete Industry (MTS)* (145) / Transactional / No
Production Supervisor / Release Production Orders / Production supervisors can release production orders using a highly intuitive and user-friendly application. The browser based application supports desktop, tablet and mobile devices. / Make-to-Stock Production - Discrete Industry (MTS)* (145) / Transactional / No
Production Order / This fact sheet displays contextual information about the Production Order. You can navigate to its related entities and you can access related transactions in operational systems. / Make-to-Stock Production - Discrete Industry (MTS)* (145) / Fact sheet / No
Planned Order / This fact sheet displays contextual information about the Planned Order. You can navigate to its related entities and you can access related transactions in operational systems, or you can navigate to related transactional applications. / Make-to-Stock Production - Discrete Industry (MTS)* (145) / Fact sheet / No
Process Order / This fact sheet displays contextual information about the process order. You can navigate to its related entities and you can access related transactions in operational systems, or you can navigate to related transactional applications. / Make-to-Stock Production – Process Industry (146) / Fact sheet / No
Resource / This fact sheet displays contextual information about the resource. You can navigate to its related entities and you can access related transactions in operational systems, or you can navigate to related transactional applications. / Make-to-Stock Production - Discrete Industry (MTS)* (145)
Make-to-Stock Production – Process Industry (146) / Fact sheet / No
Work Center / This fact sheet displays contextual information about the work center. You can navigate to its related entities and you can access related transactions in operational systems, or you can navigate to related transactional applications. / Make-to-Stock Production - Discrete Industry (MTS)* (145)
Make-to-Stock Production – Process Industry (146) / Fact sheet / No

© SAP SE Page 28 of 28

SAP Fiori Apps for the SAP ERP Application PP

* For Wave 2, the MRP Fiori apps are capable to manage external procurements such as purchase orders or purchase requisitions. All scope items using procured materials (raw or semi-finished) can use these Fiori Apps.

·  Procurement without QM (130)

·  Stock Transfer with Delivery (MRP run requires 130) (134)

·  Make-to-Stock Production – Discrete Industry (MTS) (145)

·  Make-to-Stock Production – Process Industry (146)

3  Ready-to-Activate / Fully-Activated Version

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  Technical/System Prerequisites for Transactional Apps

The prerequisite for using the SAP Fiori transactional apps is implementing the relevant application independent parts provided by the SAP Fiori apps rapid-deployment solution. This version of SAP Fiori apps rapid-deployment solution includes new SAP Fiori apps and enables the implementation of SAP NetWeaver Gateway, SAP UI5 and any of the SAP Fiori transactional apps. In general, it is necessary to set up the SAP Fiori system landscape.

The solution includes a description of the general configuration steps required to manually set up the configuration within the system landscape and information about the software installation. We have three scenarios for Fiori: transactional apps, analytical apps and fact sheets. Each scenario has its specific systems or software that need to be installed. By reading through the referenced documents, you should be able to set up your own Fiori landscape based on your existing system environment.