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 3 of 4
SAP Fiori Apps for the SAP ERP Application PS
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
/ 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
FIORI Apps for ERP Baseline - Application PS 6
1 Purpose of FIORI 6
2 Overview Matrix for PS Fiori Apps 8
3 Ready-to-Activate / Fully-Activated Version 12
4 Transactional PS Apps 13
4.1 Change WBS Element Status 13
4.1.1 Description 13
4.1.2 Key Features 13
4.1.3 Business Purpose for Change WBS Element Status 13
4.1.4 Procedure 14
4.1.5 Configuration for Baseline Scope Items 14
4.2 Confirm Project Milestone 16
4.2.1 Description 16
4.2.2 Key Features 16
4.2.3 Business Purpose for Confirm Project Milestone 16
4.2.4 Procedure 16
4.2.5 Configuration for Baseline Scope Items 17
4.3 Confirm Network Activities 18
4.3.1 Description 18
4.3.2 Key Features 18
4.3.3 Business Purpose for Confirm Network Activities 18
4.3.4 Procedure 19
4.3.5 Configuration for Baseline Scope Items 19
4.4 Change Network Activity Status 20
4.4.1 Description 20
4.4.2 Key Features 20
4.4.3 Business Purpose for Change Network Activities Status 20
4.4.4 Procedure 21
4.4.5 Configuration for Baseline Scope Items 21
5 Analytical Apps PS 23
5.1 SAP Smart Business Apps for Project Execution 23
5.1.1 Due WBS Element 24
5.1.2 Due Network Activities 28
5.1.3 Due Project Milestone 32
5.1.4 WBS Element Cost Variance 35
5.1.5 WBS Element Cost at Risk 40
5.1.6 Project Report 44
6 Fact sheets for PS 49
6.1 Procedure 49
SAP Fiori Apps for ERP Baseline – Application PS
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 PS to be able to run them on top of the SAP Best Practices PS 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 PS Fiori Apps
The following matrix shows the existing Fiori roles available within the PS 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.
© SAP SE Page 3 of 4
SAP Fiori Apps for the SAP ERP Application PS
Fiori Role / Fiori App / Short description / Mapping to scope item(Baseline scenario) IDs / FIORI application type / HANA mandatory /
SAP_PS_BCR_PROJECTMANAGER / Change WBS Element Status / You can change the system and user status of a work breakdown structure element / Project with Fixed Price and T&M Billing (196)
Internal Projects (197)
Internal Product Development (210)
SAP Best Practices for Chemicals: Overhaul Management (886) and Investment Management in Plant Maintenance (932)
SAP Best Practices for Discrete Manufacturing: Engineer-to-Order (ETO) – Project Assembly (240) / Transactional / No
SAP_PS_BCR_PROJECTMANAGER / Confirm Project Milestone / You can confirm the milestones defined in a project / SAP Best Practices for Discrete Manufacturing: Engineer-to-Order (ETO) – Project Assembly (240) / Transactional / No
SAP_PS_BCR_PROJECTMANAGER / Confirm Network Activity / You can confirm the processing of an activity within a network / SAP Best Practices for Chemicals: Overhaul Management (886)
SAP Best Practices for Discrete Manufacturing: Engineer-to-Order (ETO) – Project Assembly (240) / Transactional / No
SAP_PS_BCR_PROJECTMANAGER / Change Network Activity Status / You can change the system and user status of a network activity / SAP Best Practices for Chemicals: Overhaul Management (886)
SAP Best Practices for Discrete Manufacturing: Engineer-to-Order (ETO) – Project Assembly (240) / Transactional / No
SAP Smart Business for Project Execution
SAP_PS_BCR_PROJECTMANAGER_A / Due WBS Element / This tile shows the number of WBS elements that are due / Project with Fixed Price and T&M Billing (196)
Internal Projects (197)
Internal Product Development (210)
SAP Best Practices for Chemicals: Overhaul Management (886) and Investment Management in Plant Maintenance (932)
SAP Best Practices for Discrete Manufacturing: Engineer-to-Order (ETO) – Project Assembly (240) / Analytical / Yes
SAP_PS_BCR_PROJECTMANAGER_A / Due Network Activities / Tile shows number of network activities that are due / SAP Best Practices for Chemicals: Overhaul Management (886)
SAP Best Practices for Discrete Manufacturing: Engineer-to-Order (ETO) – Project Assembly (240) / Analytical / Yes
SAP_PS_BCR_PROJECTMANAGER_A / Due Project Milestones / Tile shows number of project milestones that are due / SAP Best Practices for Discrete Manufacturing: Engineer-to-Order (ETO) – Project Assembly (240) / Analytical / Yes
SAP_PS_BCR_PROJECTMANAGER_A / WBS Element Cost Variance / This tile shows the number of WBS elements that are exceeding planned costs / Project with Fixed Price and T&M Billing (196)
Internal Projects (197)
Internal Product Development (210)
SAP Best Practices for Chemicals: Overhaul Management (886) and Investment Management in Plant Maintenance (932)
SAP Best Practices for Discrete Manufacturing: Engineer-to-Order (ETO) – Project Assembly (240) / Analytical / Yes
SAP_PS_BCR_PROJECTMANAGER_A / WBS Element Costs at Risk / This tile shows the number of WBS elements that are approaching close to planned costs / Project with Fixed Price and T&M Billing (196)
Internal Projects (197)
Internal Product Development (210)
SAP Best Practices for Chemicals: Overhaul Management (886) and Investment Management in Plant Maintenance (932)
SAP Best Practices for Discrete Manufacturing: Engineer-to-Order (ETO) – Project Assembly (240) / Analytical / Yes
SAP_PS_BCR_PROJECTMANAGER_A / Project Report / Used to analyze project details such as overview, scheduling, finance, procurement, and risks related information / Project with Fixed Price and T&M Billing (196)
Internal Projects (197)
Internal Product Development (210)
SAP Best Practices for Chemicals: Overhaul Management (886) and Investment Management in Plant Maintenance (932)
SAP Best Practices for Discrete Manufacturing: Engineer-to-Order (ETO) – Project Assembly (240) / Analytical / Yes
Fact sheets
Project Definition / This fact sheet displays contextual information about a project. You can navigate to its related business objects and access related transactions in operational systems / Project with Fixed Price and T&M Billing (196)
Internal Projects (197)
Internal Product Development (210)
SAP Best Practices for Chemicals: Overhaul Management (886) and Investment Management in Plant Maintenance (932)
SAP Best Practices for Discrete Manufacturing: Engineer-to-Order (ETO) – Project Assembly (240) / Fact sheet / Yes
WBS elements / This fact sheet displays contextual information about a work breakdown structure (WBS) element in a project structure. You can navigate to its related business objects and access related transactions in operational systems / Project with Fixed Price and T&M Billing (196)
Internal Projects (197)
Internal Product Development (210)
SAP Best Practices for Chemicals: Overhaul Management (886) and Investment Management in Plant Maintenance (932)
SAP Best Practices for Discrete Manufacturing: Engineer-to-Order (ETO) – Project Assembly (240) / Fact sheet / Yes
Network / This fact sheet displays contextual information about a network in a project. You can navigate to its related business objects and access related transactions in operational systems. / SAP Best Practices for Chemicals: Overhaul Management (886)
SAP Best Practices for Discrete Manufacturing: Engineer-to-Order (ETO) – Project Assembly (240) / Fact sheet / Yes
Network Activity / This fact sheet displays contextual information about a network activity in a project. You can navigate to its related business objects and access related transactions in operational systems / SAP Best Practices for Chemicals: Overhaul Management (886)
SAP Best Practices for Discrete Manufacturing: Engineer-to-Order (ETO) – Project Assembly (240) / Fact sheet / Yes
Activity Confirmation / This fact sheet displays contextual information about individual confirmations for each network activity. You can navigate to its related business objects and access related transactions in operational systems / SAP Best Practices for Chemicals: Overhaul Management (886)
SAP Best Practices for Discrete Manufacturing: Engineer-to-Order (ETO) – Project Assembly (240) / Fact sheet / Yes
Project Milestone / This fact sheet displays contextual information about a milestone in a project. You can navigate to its related business objects. / SAP Best Practices for Discrete Manufacturing: Engineer-to-Order (ETO) – Project Assembly (240) / Fact sheet / Yes
© SAP SE Page 3 of 4
SAP Fiori Apps for the SAP ERP Application PS