Latest SAP Fiori

SAP Fiori Apps for SAP ERP PDF download from SAP Help Portal: http://help.sap.com/fiori_bs2013/helpdata/en/32/f2cd539f185947e10000000a44538d/content.htm Created on August 16, 2014

The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal.

Note This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.

© 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. The information contained herein may be changed without prior notice. 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 and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Table of content

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 1 of 138

Table of content 1 SAP Fiori Apps for SAP ERP 1.1 Adjust Stock 1.1.1 App History: Adjust Stock 1.1.2 App Implementation: Adjust Stock 1.1.3 App Extensibility: Adjust Stock 1.2 Approve Leave Requests 1.2.1 App History: Approve Leave Requests 1.2.2 App Implementation: Approve Leave Requests 1.2.3 App Extensibility: Approve Leave Requests 1.3 Approve Purchase Contracts 1.3.1 App History: Approve Purchase Contracts 1.3.2 App Implementation: Approve Purchase Contracts 1.3.3 App Extensibility: Approve Purchase Contracts 1.4 Approve Purchase Orders 1.4.1 App History: Approve Purchase Orders 1.4.2 App Implementation: Approve Purchase Orders 1.4.3 App Extensibility: Approve Purchase Orders 1.5 Approve Service Entry Sheets 1.5.1 App History: Approve Service Entry Sheets 1.5.2 App Implementation: Approve Service Entry Sheets 1.5.3 App Extensibility: Approve Service Entry Sheets 1.6 Approve Supplier Invoices 1.6.1 App History: Approve Supplier Invoices 1.6.2 App Implementation: Approve Supplier Invoices 1.6.3 App Extensibility: Approve Supplier Invoices 1.7 Approve Requisitions 1.7.1 App History: Approve Requisitions 1.7.2 App Implementation: Approve Requisitions 1.7.3 App Extensibility: Approve Requisitions 1.8 Approve Timesheets 1.8.1 App History: Approve Timesheets 1.8.2 App Implementation: Approve Timesheets 1.8.3 App Extensibility: Approve Timesheets 1.9 Approve Travel Expenses 1.9.1 App History: Approve Travel Expenses 1.9.2 App Implementation: Approve Travel Expenses 1.9.3 App Extensibility: Approve Travel Expenses 1.10 Approve Travel Requests 1.10.1 App History: Approve Travel Requests 1.10.2 App Implementation: Approve Travel Requests 1.10.3 App Extensibility: Approve Travel Requests 1.11 Change Network Activity Status 1.11.1 App History: Change Network Activity Status 1.11.2 App Implementation: Change Network Activity Status 1.11.3 App Extensibility: Change Network Activity Status 1.12 Change Sales Orders 1.12.1 App History: Change Sales Orders 1.12.2 App Implementation: Change Sales Orders 1.12.3 App Extensibility: Change Sales Orders 1.13 Change WBS Element Status 1.13.1 App History: Change WBS Element Status 1.13.2 App Implementation: Change WBS Element Status 1.13.3 App Extensibility: Change WBS Element Status 1.14 Check Price and Availability 1.14.1 App History: Check Price and Availability 1.14.2 App Implementation: Check Price and Availability 1.14.3 App Extensibility: Check Price and Availability 1.15 Confirm Network Activity 1.15.1 App History: Confirm Network Activity 1.15.2 App Implementation: Confirm Network Activity

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 2 of 138

1.15.3 App Extensibility: Confirm Network Activity 1.16 Confirm Production Operations 1.16.1 App Implementation: Confirm Production Operations 1.16.2 App History: Confirm Production Operations 1.17 Confirm Production Orders 1.17.1 App Implementation: Confirm Production Orders 1.17.2 App History: Confirm Production Orders 1.18 Confirm Project Milestone 1.18.1 App History: Confirm Project Milestone 1.18.2 App Implementation: Confirm Project Milestone 1.18.3 App Extensibility: Confirm Project Milestone 1.19 Create Sales Orders 1.19.1 App History: Create Sales Orders 1.19.2 App Implementation: Create Sales Orders 1.19.3 App Extensibility: Create Sales Orders 1.20 Customer Invoices 1.20.1 App History: Customer Invoices 1.20.2 App Implementation: Customer Invoices 1.20.3 App Extensibility: Customer Invoices 1.21 Look Up Retail Products 1.21.1 App History: Look Up Retail Products 1.21.2 App Implementation: Look Up Retail Products 1.21.3 App Extensibility: Look Up Retail Products 1.22 My Benefits 1.22.1 App History: My Benefits 1.22.2 App Implementation: My Benefits 1.22.3 App Extensibility: My Benefits 1.23 My Contacts 1.23.1 App Implementation: My Contacts 1.24 My Leave Requests 1.24.1 App History: My Leave Requests 1.24.2 App Implementation: My Leave Requests 1.24.3 App Extensibility: My Leave Requests 1.25 My Paystubs 1.25.1 App History: My Paystubs 1.25.2 App Implementation: My Paystubs 1.25.3 App Extensibility: My Paystubs 1.26 My Quality Tasks 1.26.1 App Implementation: My Quality Tasks 1.26.2 App History: My Quality Tasks 1.27 My Timesheet 1.27.1 App History: My Timesheet 1.27.2 App Implementation: My Timesheet 1.27.3 App Extensibility: My Timesheet 1.28 My Travel Requests 1.28.1 App History: My Travel Requests 1.28.2 App Implementation: My Travel Requests 1.28.3 App Extensibility: My Travel Requests 1.29 My Spend 1.29.1 App History: My Spend 1.29.2 App Implementation: My Spend 1.29.3 App Extensibility: My Spend 1.30 Order from Requisitions 1.30.1 App History: Order from Requisitions 1.30.2 App Implementation: Order from Requisitions 1.30.3 App Extensibility: Order from Requisitions 1.31 Release Production Orders 1.31.1 App History: Release Production Orders 1.31.2 App Implementation: Release Production Orders 1.32 Report Quality Issue 1.32.1 App Implementation: Report Quality Issue 1.32.2 App History: Report Quality Issue

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 3 of 138

1.33 Track Purchase Order 1.33.1 App History: Track Purchase Order 1.33.2 App Implementation: Track Purchase Order 1.33.3 App Extensibility: Track Purchase Order 1.34 Track Sales Orders 1.34.1 App History: Track Sales Orders 1.34.2 App Implementation: Track Sales Orders 1.34.3 App Extensibility: Track Sales Orders 1.35 Track Shipments 1.35.1 App History: Track Shipments 1.35.2 App Implementation: Track Shipments 1.35.3 App Extensibility: Track Shipments

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 4 of 138

1 SAP Fiori Apps for SAP ERP 1.1 Adjust Stock With the transactional app Adjust Stock you can count products in the store inventory and make adjustments to account for discrepancies such as product shrinkage.

Key Features Perform ad hoc inventory counting Record adjustments for product shrinkage Identify the reason for a stock adjustment

System Landscape Requirements The app consists of front-end components (such as the user interfaces) and back-end components (such as the OData service). The back-end and the front-end components are delivered in separate products and have to be installed in a system landscape that is enabled for SAP Fiori. Product Version Containing Back-End and Front-End Components of the App

SAP Fiori transactional apps for SAP ERP 1.0 SPS01

Back-End Product Versions (with Minimum

SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher

Support Package Stack) Supporting the App

SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment

The following software products must be available in your system landscape: Back-end system (business data) Required product release: SAP Enhancement Package 4 for SAP ERP 6.0 The following software components are required: EA-RETAIL 604 installed with the latest SP GBX02RT4 SP 0 UI add-on (front-end components) Required product release: UI for EHP4 for SAP ERP 6.0 SP09 Required software component: UIX02RT4 SP 0

Note This app is also available in a version for higher back-end releases. For more information, see SAP Help Portal at SAP Fiori for SAP ERP SAP Fiori for SAP ERP 1.0 .

http://help.sap.com/fiori_products

Related Apps Look Up Retail Products

Component for Customer Incidents LO-SRS-MOB

More Information App History: Adjust Stock App Implementation: Adjust Stock App Extensibility: Adjust Stock

1.1.1 App History: Adjust Stock The Adjust Stock app has been enhanced as follows:

SAP Fiori for SAP ERP 1.0 SPS03 (Delivery Date 07/2014) Initial delivery.

1.1.2 App Implementation: Adjust Stock PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 5 of 138

1.1.2 App Implementation: Adjust Stock System Landscape Requirements Before you start to implement the app, ensure that your system landscape has been set up to enable SAP Fiori. This also implies that the front-end and back-end components for your app are already available in this system landscape: SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment

Configuration of Front-End Server

Configuration of SAP Fiori Infrastructure

Back-End Product Versions (with Minimum Support Package Stack) Supporting the App

Product Version Containing Back-End and Front-End Components of the App

SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP Fiori transactional apps for SAP ERP 1.0 SPS01

For more information on the installation of the back-end and front-end components of the app, see Installation Information. For the app, the following software components must be available in your system landscape. These components are contained in the product SAP Fiori transactional apps for SAP ERP : Back-End/Front-End Server

Back-End/Front-End Component

Technical Name of Software Component Support Package Level

Back-end server

Back-end component

GBX02RT4 604

00

Front-end server

Front-end component

UIX02RT4 100

00

Required SAP Notes For Adjust Stock , the following SAP Notes must be available: Back-End/Front-End Server

SAP Note Number

Description

2030061

Release Information Note for the FIORI application Adjust Stock in ECC 604, ECC 605 and ECC 616

Implementation Tasks The following sections list tasks that have to be performed to implement the Adjust Stock app. The tables contain the app-specific data required for these tasks:

Front-End Server: Activate OData Services Component

Technical Name

OData Service (Version Number)

RETAILSTORE_STOCK_CORR_SRV (1)

For more information about activating OData services, see Front-End Server: Activate OData Services.

Front-End Server: Activate UI5 Application Component

Technical Name

UI5 Application

RT_STOCK_COR

For more information about how to activate the UI5 application (ICF service), see Front-End Server: Activate ICF Services of UI5 Application.

Front-End Server: Enable App for Access in SAP Fiori Launchpad There are several steps to be performed to enable the app for access in the SAP Fiori launchpad. You require the listed data to perform these steps. For more information about the steps to be performed, see Setup of Catalogs, Groups, and Roles in the SAP Fiori Launchpad. Component

Technical Name

Semantic Object

Article

Business Role

SAP_ISR_STORE_BCR_STORE_ASSOC

Business Catalog

SAP_ISR_BC_StoreAssociate

Business Catalog Group

SAP_ISR_BCG_StoreAssociate

Technical Role

SAP_ISR_STORE_TCR_T

Technical Catalog

SAP_ISR_STORE_TC_T

LPD_CUST Role

UIRT401

LPD_CUST Instance

TRANSACTIONAL

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 6 of 138

LPD_CUST Instance

TRANSACTIONAL

Front-End and Back-End Server: Assign Role with OData Service Authorization to Users To restrict access to OData services to specific users, you have to assign roles (including OData service authorization for the app) to your users. You have to make the assignment on the back-end and on the front-end server: On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can adjust this role according to your needs. On the front-end server, you can assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs. OData Service (Version Number)

Back-End Server: Delivered Authorization Role (PFCG Role)

Front-End Server: Authorization Role

RETAILSTORE_STOCK_CORR_SRV (1)

SAP_STORE_STOCK_COR_APP

Use an existing role or create a new one

For more information about authorization roles and assigned OData services, see Front-End Server: Assign Role with OData Service Authorization t and Back-End Server: Assign Role with OData Service Authorization to.

Prerequisites for Implementation Before implementing the app, you must ensure the following: Software component EA-RETAIL 604 is installed with the latest SP on the back-end server SAP Enterprise Search is deployed and TREX-based models are imported Software component UIX02RT4 SP 0 is installed on the front-end server Business function Retail, In-Store Merchandise and Inventory Management is configured, and master data is prepared

Configuration Tasks To enable Adjust Stock , you must perform the following configuration tasks:

Set the Retail Store Ruling Price Condition Sales prices are retrieved from the back-end SAP ERP system in the following order of priority: Normal sales price condition

VKPO

Lowest priority

Promotion price condition

VKAO

Higher priority

Retail Store ruling price

VKPF

Highest priority

In the Adjust Stock app, the Retail Store ruling price condition VKPF is required to read the most current price for products from the back-end system. You must configure this condition as follows: 1. Add the VKPF condition type to the list of condition types. Sales and Distribution Basic Functions Pricing Pricing Control 2. Assign the VKPF condition type to the VKP001 procedure.

Define Condition Types

Sales and Distribution Basic Functions Pricing 3. Assign the VKPF condition type to the ruling price.

Define and Assign Pricing Procedures

Logistics General

SAP Retail Store

Sales Prices

Pricing Control

Basic Settings for Sales Prices

.

Additional Required Configuration Configure settings to enable TREX-based SAP Enterprise Search. Ensure that the MATERIAL model is available. In the Customizing activity for SAP Retail Store under Goods Movement Grouping of Business Transactions for Other Goods Movements that a business transaction with key 0002 is defined for product shrinkage and that this business transaction is assigned to the store.

, confirm

Configure Settings to Download Product Images (Optional) This section describes how to configure settings to download product images to the Adjust Stock app. If you use SAP Document Service (DMS) provided by SAP as the product image provider, configure the required settings to enable product image downloads to the app as follows: 1. Create a document for a desired image. In DMS, execute transaction CV01N, and make the following settings: Document Type = DRW Document Part = 000 Document Version = Press Enter and make the Document Status = WR (Work Request). 2. Upload the desired image file. Defined storage category = DMS_C1_ST 3. Link the document to a related product number in SAP ERP. For more information, see http://help.sap.com/businesssuite SAP Product Lifecycle Management Application Help Document Management .

SAP PLM as part of SAP ERP Central Component

If you are not using SAP Document Service (DMS) as the product image provider, provide a BAdI implementation to specify your product image provider.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 7 of 138

Configure Settings to Retrieve Supplemental Product Data (Optional) You can use Business Add-ins (BAdIs) to retrieve supplemental product data such as warranty or other relevant information for the product. You find these in Customizing for SAP Retail Store under In-Store Merchandise and Inventory Management - UI5 Apps Look Up Retail Products . For more information, see App Extensibility: Adjust Stock.

Note The Adjust Stock and Look Up Retail Products apps share the defined BAdIs for supplemental data. If you already defined this BAdI for one app (for example, for Look Up Retail Products ), you do not need to define it again to use it in Adjust Stock .

General Details About the Adjust Stock App The following are general details about the Adjust Stock app: When users access the Adjust Stock app, the system checks whether they are assigned to a store. If they are not assigned to a store, a list of stores is displayed. This list comes from authorization object W_SRS_APPL. Users can change their store assignment anytime by choosing the Settings icon. The assigned store is persisted in table FPB_PERSPARM, which the Adjust Stock app reuses from the SAP In-Store Merchandise and Inventory Management application (Retail In-Store MIM). To integrate with SAP Jam, each user of the Adjust Stock app must have their own account in SAP Jam. They must also register their SAP Jam account email address on the SAP Gateway system. For more information, see http://help.sap.com/sapjam. You can use transaction SLG1 to check the application log in the back-end SAP ERP Retail system. To do so, make the following settings: Object

W_SRS_MOB

Subobject

MOBILE_SC

Details About the Product List in the Adjust Stock App The following section describes specific details about the product list. You add products to the list by pressing the '+' icon and then entering text into the Search field. You can add a single or multiple products to the list this way. You delete products from the list by pressing the checklist icon at the top of the page. You can delete a single or multiple products from the list this way. The Open section contains a list of products for which a count or an adjustment was started, but no data was submitted to the SAP ERP backend. The Completed section contains a list of products that have been counted or adjusted and submitted to the SAP ERP backend. You can control the recency of products displayed in the product list by defining a validity period in the Define Basic Settings for Stock Adjustment Customizing activity under SAP Retail Store In-Store Merchandise and Inventory Management - UI5 Apps Adjust Stock . This ensures that only products in the defined validity period are displayed in the product list. You can predefine a product list for a user by importing records into table ARTICLE_SC_HEAD or, by writing a report. The business key of the product list consists of the store ID, the user ID, and the product number. You can remove products that no longer fall within the defined validity period from the product list by using the RETAIL_ST_SC_CLEANUP_STAGE_TAB function. You can create a report and schedule it in a background job to execute this task. You can set the cleanup frequency according to your business needs, however you should consider that the longer your validity period, the more records will accumulate in the table and if you schedule the cleanup to run less frequently this will impact the performance of the Adjust Stock app.

Details About the Counting Feature in the Adjust Stock App The following section describe specific details about the counting feature. The counting function is product-based. Users enter counts for one product at a time and submit the counts per product. Any product that already has an existing counting document cannot be selected for counting again or to receive a stock adjustment, regardless of its storage location. The stock quantity displayed for a product comes from SAP ERP for Retail and includes the counted or adjusted values applied by the Adjust Stock app. If the user changes the storage location or stock type for a product, the old values will not be retained. Any product counts or adjustments are applied to the new storage location or stock type. Document numbers generated after users submit a product count or adjustment to the back-end system are not visible on the UI. If required, you must get it from the back-end ERP system. Counts are saved under the product location, for example a specific shelf. Users can create as many locations as they want by choosing the Add Product Location button.

Details About the Adjustment Feature in the Adjust Stock App The following section describes specific details about the stock adjustment feature. Adjustments are product-based. Users can enter an adjustment quantity for one product at a time and submit the adjustment per product. Currently only the stock adjustment related to shrinkage, known as business transaction 0002, is supported in the Adjust Stock app. You must customize the movement type as described in the Configuration Tasks section. Document numbers generated after users submit a product count or adjustment to the back-end system are not visible on the UI. If required, you must get it from the back-end ERP system.

More Information For general information about the user management concept in a SAP Fiori environment, see Users in ABAP Front-End System and Users in ABAP Back-End System.

1.1.3 App Extensibility: Adjust Stock PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 8 of 138

You can extend Adjust Stock according to your business needs for different aspects. For this purpose, the following extensibility options are available: You can add new customer fields to the Information section of product detail view. You can add a new section to the product detail view and add new fields to it. You can add logic to the submit process before, after, or in both instances when a count document is submitted to the back-end system. You can add logic to the submit process before, after, or in both instances when an adjustment document is submitted to the back-end system.

Add Fields to Information Section and to New Section of Product Detail View To add new fields in the Product Information section, or in a new section, of the product detail view, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

View

Extension Point

ProductDetails.view. app.xml

To add new fields to

Design Time: Gateway

Design Time: Gateway

Design Time: Extension

Runtime:

Project

Entity

Include (in DDIC

Superclass/Method to Be

Structure)

Redefined

RETAILSTORE_STOCK_CO

Information section: R

Product entity in

RETAIL_ST_SC_ARTICLE_ CL_RETAILSTORE_STOC_0

RETAILSTORE_STOCK_CO

INCL

R project

product_details

1_DPC methods: PRODUCTS_GET_ENT

_item_ext1

ITY

To add new fields to

PRODUCTS_GET_ENT

new section in the Information section:

ITYSET

Product_Details

ENTITY

_Sections_Ext

PRODUCTS_DELETE_

PRODUCTS_CREATE_

ENTITY

Note You must copy the code from the original class and use the enhanced structure where needed. The enhanced structure is available in the redefined GET methods signature (ER_ENTITY type).

UI Controller Hooks To plug in and execute custom code, the following hooks are available in the controller code: Controller

Hook

Use

ProductDetails.Controller.js

extHookOnProductDetailsDataReceived

Allows you to execute code to validate or enrich product information after product data is received from the back-end system

For more information about UI controller hooks, see UI Controller Hooks.

Business Add-Ins (BAdIs) The following Business Add-Ins are available for extensibility purposes: BAdI: Enhancement of Product Details RETAIL_ST_SC_PRODUCT_ENH You can use this BAdI to retrieve additional product information for the Product Detail screen. This BAdI uses the GET_PRODUCT_SUPP_DATA method to retrieve data from the back-end system. BAdI: Enhancement of Details for a Single Product RETAIL_ST_SC_SINGLE_PROD_ENH You can use this BAdI to retrieve additional product information for a single product in the Product Detail screen. This BAdI uses theGET_SINGLE_PRODUCT_SUPP_DATA method.

Add Logic to Submit Process for Count Data You can add logic to validate count data before, after, or in both instances when it is submitted to the back-end system. For this purpose, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs:

UI Controller Hooks To plug in and execute custom code, the following hooks are available in the controller code:

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 9 of 138

Controller

Hook

Use

ProductCount.Controller.js

extHookOnProductCountBeforeSubmit

Allows you to execute code to validate count data before it

ProductCount.Controller.js

extHookOnProductCountAfterSubmit

is submitted to the back-end system Allows you to execute code to validate count data after it is submitted to the back-end system

For more information about UI controller hooks, see UI Controller Hooks.

Add Logic to Submit Process for Adjustment Data UI Controller Hooks To plug in and execute custom code, the following hooks are available in the controller code: Controller

Hook

Use

ProductShrink.Controller.js

extHookOnProductShrinkBeforeSubmit

Allows you to execute code to validate adjustment data before it is submitted to the back-end system

ProductShrink.Controller.js

extHookOnProductShrinkAfterSubmit

Allows you to execute code to validate adjustment data after it is submitted to the back-end system

For more information about UI controller hooks, see UI Controller Hooks.

More Information For a general description of the extensibility options and procedures of Fiori apps, see Extensibility.

1.2 Approve Leave Requests With the transactional app Approve Leave Requests you enable managers to approve or reject leave requests for their direct reports, easily and flexibly from their desktop or mobile device. Key information for the approval decision is available at a glance, including a team calendar that shows overlapping leave requests.

Key Features Browse all requests submitted for approval in a personalized workflow inbox View details for specific requests, including the leave requested, the available balance and any comments relating to the request View a team calendar that shows overlapping leave requests if there are leave conflicts Approve or reject requests (with optional note to the requester)

System Landscape Requirements The app consists of front-end components (such as the user interfaces) and back-end components (such as the OData service). The back-end and the front-end components are delivered with one product and have to be installed in a system landscape that is enabled for SAP Fiori. Product Version Containing Back-End and Front-End Components of the App Back-End Product Versions Supporting the App (Minimum Product Version Stack)

SAP Fiori principal apps for SAP ERP 1.0 SPS03

SAP ERP 6.0 SP15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher

SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment Based on SAP enhancement package 7 of SAP ERP 6.0 also possible: Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

Related Apps My Leave Requests

Component for Customer Messages MOB-UIA-PT-ALR

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 10 of 138

More Information App History: Approve Leave Requests App Implementation: Approve Leave Requests App Extensibility: Approve Leave Requests

1.2.1 App History: Approve Leave Requests The Approve Leave Requests app has been enhanced as follows:

SAP Fiori principal apps for SAP ERP 1.0 SPS 03 (Delivery Date 07/2014) New/Enhanced Extensibility Options

Controller hooks are introduced.

SAP Note for Technical Changes

1931619

SAP Fiori principal apps for SAP ERP 1.0 SPS 02 (Delivery Date 05/2014) New/Enhanced Key Features

No changes.

New/Enhanced Extensibility Options

No changes.

SAP Note for Technical Changes

1931619

SAP Fiori principal apps for SAP ERP 1.0 SPS 01 (Delivery Date 02/2014) New/Enhanced Key Features

No changes.

New/Enhanced Extensibility Options

New extensibility options: You can now add additional attributes in the list items on the Master Details page of the app. You can now hide or add additional fields in the header section on the Details page of the app. OData service can now be extended.

SAP Note for Technical Changes

1931619

SAP Fiori principal apps for SAP ERP 1.0 SPS 00 (Delivery Date 11/2013) Initial delivery.

1.2.2 App Implementation: Approve Leave Requests System Landscape Requirements Before you start to implement the app, ensure that your system landscape has been set up to enable SAP Fiori. This also implies that the front-end and back-end components for your app are already available in this system landscape: SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment Based on SAP enhancement package 7 of SAP ERP 6.0 also possible: Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

Configuration of Front-End Server Back-End Product Versions Supporting the App (Minimum Product Version Stack)

Configuration of SAP Fiori Infrastructure SAP ERP 6.0 SP15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher

Product Version Containing Back-End and

SAP Fiori principal apps for SAP ERP 1.0 SPS03

Front-End Components of the App

For more information on the installation of the back-end and front-end components of the app, see Installation of Back-End Components and Installation of Front-End Components.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 11 of 138

For the app, the following software components must be available in your system landscape. These components are contained in the product SAP Fiori principal apps for SAP ERP : Back-End/Front-End Server

Back-End/Front-End Component

Technical Name of Software Component Support Package Level

Back-end server

Back-end component

GBHCM003 600

10

Front-end server

Front-end component

UIX01HCM 100

03

Required SAP Notes For Approve Leave Requests, the following SAP notes must be available: SAP Note Number

Description

1931619

Release Information

Implementation Tasks The following sections list tasks that have to be performed to implement the Approve Leave Requests app. The tables contain the app-specific data required for these tasks:

Front-End Server: Activate OData Services Component

Technical Name

OData Service (Version Number)

/GBHCM/LEAVEAPPROVAL (1)

For more information about activating OData services, see Front-End Server: Activate OData Services.

Front-End Server: Activate UI5 Application Component

Technical Name

UI5 Application

HCM_LR_APV

For more information about how to activate the UI5 application (ICF service), see Front-End Server: Activate ICF Services of UI5 Application.

Front-End Server: Enable App for Access in SAP Fiori Launchpad There are several steps to be performed to enable the app for access in the SAP Fiori launchpad. You require the listed data to perform these steps. For more information about the steps to be performed, see Setup of Catalogs, Groups, and Roles in the SAP Fiori Launchpad. Component

Technical Name

Semantic Object

LeaveRequest

Business Role

SAP_HCM_BCR_MANAGER_X1

Business Catalog

SAP_HCM_BC_MANAGER_X1

Business Catalog Group

SAP_HCM_BCG_MANAGER_X1

Technical Role

SAP_HCM_TCR_T_X1

Technical Catalog

SAP_HCM_TC_T_X1

LPD_CUST Role

UIX01HCM

LPD_CUST Instance

TRANSACTIONAL

Front-End and Back-End Server: Assign Role with OData Service Authorization to Users To restrict access to OData services to specific users, you have to assign roles (including OData service authorization for the app) to your users. You have to make the assignment on the back-end and on the front-end server: On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can adjust this role according to your needs. On the front-end server, you can assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs. OData Service (Version Number)

Back-End Server: Delivered Authorization Role

Front-End Server: Authorization Role

(PFCG Role) /GBHCM/LEAVEAPPROVAL (1)

SAP_GBHCM_LEAVE_APPROVAL_MGR

Use an existing role or create a new one

For more information about authorization roles and assigned OData services, see Front-End Server: Assign Role with OData Service Authorization t and Back-End Server: Assign Role with OData Service Authorization to.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 12 of 138

Prerequisites for Implementation Before implementing the app, you must ensure the following: Install GBHCM002 component Configure ESS leave solution You use SAP Time Management to manage your employees' time data. You have made the Customizing settings for the Leave Request, Time Accounts, and Team Calendar. For more information, see Customizing for Personnel Management by choosing Employee Self-Service Service-Specific Settings Working Time Leave Request .

Configuration Tasks To enable Approve Leave Requests , you must perform the following configuration tasks: Enable the SICF Services for the Gateway Service name: /GBHCM/LEAVEAPPROVAL Enable the SICF Services for UI5 Service name: HCM_LR_APV Deploy the Business Add-In /GBHCM/BDD_MA_ENABLE_APPS (Manager Approvals: enable apps). For more information on BAdI implementations, see Steps to Activate BAdI Implementations.

More Information For general information about the user management concept in a SAP Fiori environment, see Users in ABAP Front-End System and Users in ABAP Back-End System.

1.2.3 App Extensibility: Approve Leave Requests You can extend Approve Leave Requests according to your business needs for different aspects. For this purpose, the following extensibility options are available: Extending the Master list view You can add additional attributes in list item on the Master screen. Extending the Details view You can hide fields in the header section on Details screen. You can add additional fields in the header section on Details screen.

Note In addition, any of the complete views can be replaced by your own view.

Extending the Master list view To add additional attributes in the list items on the Master screen of the app, the following extensibility entities are available on the different layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

View

Extension Point

Design Time: Gateway Entity

Design Time: Extension Include (in DDIC Structure)

Runtime: Superclass/ Method to Be Redefined

S2.view.xml

extS2ListItem

LEAVEAPPROVAL

/GBHCM/LRA_LREQ_INCL

Superclass: /GBHCM/CL_MANAGER_APPR_RD P2 Method: GET_ENTITYSET_LEAVE_REQUE ST

Extending the Details view To hide or add additional fields in the header section on the Details screen of the app, the following extensibility entities are available on the different layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

View

Extension Point

Design Time: Gateway Entity

Design Time: Extension Include (in DDIC Structure)

Runtime: Superclass/ Method to Be Redefined

S3.view.xml

extS3Header

LEAVEAPPROVAL

/GBHCM/LRA_LREQ_INCL

Superclass: /GBHCM/CL_MANAGER_APPR_RD P2 Method: GET_ENTITY_LEAVE_REQ_DET

extS3Tab

LEAVEAPPROVAL

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

/GBHCM/LRA_LREQ_INCL

Superclass:

Page 13 of 138

/GBHCM/CL_MANAGER_APPR_RD P2 Method: GET_ENTITY_LEAVE_REQ_DET

Further Extensibility Entities Extension Includes In addition to the extension includes described above, the following extension includes are available: DDIC

Extension Include

Use

/GBHCM/S_MA_LA_ACTION2

/GBHCM/LRA_ACTION_INCL

Extends the Action entity.

/GBHCM/S_MA_EMPLOYEE_DETAIL2

/GBHCM/LRA_EMP_INCL

Extends the Employee Details( with corresponsing

/GBHCM/S_MA_LA_ITEM_COUNT2

/GBHCM/LRA_ITCOUNT_INCL

Extends the Item Count entity.

/GBHCM/S_MA_LA_NOTES

/GBHCM/LRA_NOTE_INCL

Extends the Notes entity.

/GBHCM/S_MA_TEAM_CAL_HEADER

/GBHCM/LRA_TCAL_HDR_INCL

Extends the Team Calendar Header entity.

/GBHCM/S_MA_TEAM_CALENDAR2

/GBHCM/LRA_TCAL_INCL

Extends the Team Calendar entity.

/GBHCM/S_MA_LA_TIME_ACCOUNT2

/GBHCM/LRA_TIM_AC_INCL

Extends the Time Account entity.

position) entity.

For more information about extension includes, see Extension Includes.

UI Controller Hooks To plug in and execute custom code, the following hooks are available in the controller code: Controller

Hook

Use

S2.controller.js

extHookChangeFooterButtons

Allows you to add and change buttons for the detail view footer

S3.controller.js

extHookChangeFooterButtons

S4.controller.js

extHookChangeFooterButtons

Allows you to add and change buttons for the detail view footer Allows you to add and change buttons for the detail view footer

For more information about UI controller hooks, see UI Controller Hooks.

More Information For a general description of the extensibility options and procedures of Fiori apps, see Extensibility.

1.3 Approve Purchase Contracts With the transactional app 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.

Note You see only the contracts for which you are responsible. For information about the functional differences between this app and the corresponding SAP ERP back-end functionality, see SAP Note 2037653.

Key Features You can search for specific contracts. You can display details for each contract, for example, the line items with detailed information, such as conditions, target quantities, and target values. You can approve contracts and forward them to colleagues.

Supported Item Categories The Approve Purchase Contracts app supports the following SAP ERP item categories: Service (internal item category: 9) Standard (internal item category: 0) Material Group (internal item category: 8)

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 14 of 138

System Landscape Requirements The app consists of front-end components (such as the user interfaces) and back-end components (such as the OData service). The back-end and the front-end components are delivered with one product and have to be installed in a system landscape that is enabled for SAP Fiori. Product Version Containing Back-End and Front-End Components of the App

SAP Fiori principal apps for SAP ERP 1.0 SPS03

Back-End Product Versions Supporting the App (Minimum Product Version Stack)

SAP ERP 6.0 SP15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher

SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment Based on SAP enhancement package 7 of SAP ERP 6.0 also possible: Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

Related Apps Approve Requisitions Approve Purchase Orders Track Purchase Order Order from Requisitions

Component for Customer Incidents Approve Purchase Contracts (MOB-UIA-MM-APC)

More Information App History: Approve Purchase Contracts App Implementation: Approve Purchase Contracts App Extensibility: Approve Purchase Contracts

1.3.1 App History: Approve Purchase Contracts The Approve Purchase Contracts app has been enhanced as follows:

SAP Fiori principal apps for SAP ERP 1.0 SPS03 (Delivery Date 07/2014) No changes.

SAP Fiori principal apps for SAP ERP 1.0 SPS02 (Delivery Date 05/2014) New/Enhanced Key Features

No changes.

New/Enhanced Extensibility Options

New extensibility options: Add fields to the master list You can add your own fields on each item in the items master list. Add fields to the purchase contract item overview Add fields to the purchase contract item details view Add fields to the service line details view

SAP Note for Technical Changes

1937863

SAP Fiori principal apps for SAP ERP 1.0 SPS01 (Delivery Date 02/2014) No changes.

SAP Fiori principal apps for SAP ERP 1.0 SPS00 (Delivery Date 01/2014) Initial delivery.

1.3.2 App Implementation: Approve Purchase Contracts PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 15 of 138

1.3.2 App Implementation: Approve Purchase Contracts System Landscape Requirements Before you start to implement the app, ensure that your system landscape has been set up to enable SAP Fiori. This also implies that the front-end and back-end components for your app are already available in this system landscape: SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment Based on SAP enhancement package 7 of SAP ERP 6.0 also possible: Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

Configuration of Front-End Server

Configuration of SAP Fiori Infrastructure

Back-End Product Versions Supporting the

SAP ERP 6.0 SP15 or higher

App (Minimum Product Version Stack)

SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher

Product Version Containing Back-End and Front-End Components of the App

SAP Fiori principal apps for SAP ERP 1.0 SPS03

For more information on the installation of the back-end and front-end components of the app, see Installation of Back-End Components and Installation of Front-End Components. For the app, the following software components must be available in your system landscape. These components are contained in the product SAP Fiori principal apps for SAP ERP : Back-End/Front-End Server

Back-End/Front-End Component

Technical Name of Software Component Support Package Level

Back-end server

Back-end component

SRA001 1.0

04

Front-end server

Front-end component

UIX01EAP 100

03

Required SAP Notes For Approve Purchase Contracts , the following SAP Notes must be available: Back-End/Front-End Server

SAP Note Number

Description

Both

1937863

Central note for Approve Purchase Contracts . All other important notes for this app are referenced from the central note.

Implementation Tasks The following sections list tasks that have to be performed to implement the Approve Purchase Contracts app. The tables contain the app-specific data required for these tasks:

Front-End Server: Activate OData Services Component

Technical Name

OData Service (Version Number)

sra001_pcapproval (1)

For more information about activating OData services, see Front-End Server: Activate OData Services.

Front-End Server: Activate UI5 Application Component

Technical Name

UI5 Application

MM_PC_APV

For more information about how to activate the UI5 application (ICF service), see Front-End Server: Activate ICF Services of UI5 Application.

Front-End Server: Enable App for Access in SAP Fiori Launchpad There are several steps to be performed to enable the app for access in the SAP Fiori launchpad. You require the listed data to perform these steps. For more information about the steps to be performed, see Setup of Catalogs, Groups, and Roles in the SAP Fiori Launchpad. Component

Technical Name

Semantic Object

PurchaseContract

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 16 of 138

Business Role

SAP_MM_BCR_Buyer_X1

Business Catalog

SAP_MM_BC_Buyer_X1

Business Catalog Group

SAP_MM_BCG_Buyer_X1

Technical Role

SAP_MM_TCR_T_X1

Technical Catalog

SAP_MM_TC_T_X1

LPD_CUST Role

UIX01MM

LPD_CUST Instance

TRANSACTIONAL

Front-End and Back-End Server: Assign Role with OData Service Authorization to Users To grant access to OData services to specific users, you have to assign roles (including OData service authorization for the app) to your users. You have to make the assignment on the back-end and on the front-end server: On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can adjust this role according to your needs. On the front-end server, you can assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs. OData Service (Version Number)

Back-End Server: Delivered Authorization Role (PFCG Role)

Front-End Server: Authorization Role

sra001_pcapproval (1)

SAP_MM_PC_APV_APP

Use an existing role or create a new one

For more information about authorization roles and assigned OData services, see Front-End Server: Assign Role with OData Service Authorization t and Back-End Server: Assign Role with OData Service Authorization to.

Configuration Tasks If you want to use the Approve Purchase Contracts app, the following prerequisites must be met in Customizing: You use the release strategy in Purchasing (MM-PUR). You have made the corresponding settings in Customizing for Materials Management under Purchasing Contract Release Procedure for Contracts . You have configured the approval workflow for approving purchase contracts. To create work items which can be approved using the app, you have set up a connection between the release strategy and SAP Business Workflow. In addition, you must perform the following configuration tasks:

Workflow Specify the workflow tasks that are relevant for approving purchase contracts. You do this in Customizing for Materials Management under Purchasing Contract Approve Purchase Contracts App Specify Workflow Task IDs for Approve Purchase Contracts App . For more information, see the documentation available in Customizing.

Storage of Notes Users of the Approve Purchase Contracts app can create the following notes: Approval notes Forwarding notes System Behavior Approval Notes Approval notes created in the Approve Purchase Contracts app are stored at header level of the purchase contract. The program logic assumes that text type "K18" can be used for storing the note in the database. Forwarding Notes Forwarding notes created in the Approve Purchase Contracts app are stored with the work item of SAP Business Workflow. Required Activities Approval Notes If text type "K18" does not yet exist, you must create it in Customizing for Materials Management under

Purchasing

Contract

Texts for Contracts

Define Text Types for Header Texts . You have to enter the Sequential Number "18". If your company already uses text type "K18" for a different purpose, you can use the BAdI Extend Runtime of Gateway Service for Approve Contracts App (SRA001_APC_RDP), method SET_ATTRIBUTES, to use a different text type to store the notes. This BAdI is available in Customizing for Materials Management under Purchasing Contract Approve Purchase Contracts App BAdI: Change Data of Approve Purchase Contracts App Forwarding Notes You do not need to create a text type. The note is saved with the workflow item, not with the purchase contract.

More Information For general information about the user management concept in a SAP Fiori environment, see Users in ABAP Front-End System and Users in ABAP Back-End System.

1.3.3 App Extensibility: Approve Purchase Contracts PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 17 of 138

1.3.3 App Extensibility: Approve Purchase Contracts You can extend the Approve Purchase Contracts app for different aspects. For this purpose, the following extensibility options are available: Add fields to the master list You can add your own fields on each item in the items master list. Add fields to the purchase contract item overview Add fields to the purchase contract item details view Add fields to the service line details view

Add Fields to Master List To add customer fields to each item in the master list, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

View

Extension Point

Design Time: Name of Entity Set

Design Time: Extension Include (in DDIC Structure)

S2.view.app.xml

extListItemInfo

WorkflowTaskCollection

SRA001S_PC_WORKFLOW_TASK_ BAdI: SRA001_APC_RDP INCL

Runtime: BAdI to Be Implemented

Method: IF_SRA001_EX_PC_RDP~CHANG E_WORKFLOW_TASK_API

Add Fields to Item Overview To add customer fields to the header area and to the Information area of the purchase contract item overview, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

View

Extension Point

Design Time: Name of Entity Set

Design Time: Extension Include (in DDIC Structure)

S3_header.view.app.xml

extHeaderInfo

HeaderDetailCollection

SRA001S_PC_HEADER_DETAILS BAdI: SRA001_APC_RDP _INCL

extInformation

Runtime: BAdI to Be Implemented

Method:IF_SRA001_EX_PC_RDP ~CHANGE_HEADER_DETAILS_IN FO_API

Add Fields to Item Details To add customer fields to the header area and to the Information area of the purchase contract item details view, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

View

Extension Point

Design Time: Name of Entity Set

Design Time: Extension Include (in DDIC Structure)

ItemDetails.view.xml

extMaterialHeaderInfo

ItemDetailCollection

SRA001S_PC_ITEM_DETAILS_I BAdI: SRA001_APC_RDP NCL

extServiceHeaderInfo extInformation

Runtime: BAdI to Be Implemented

Method: IF_SRA001_EX_PC_RDP~CHANG E_ITEM_DETAILS_INFO_API

Add Fields to Service Line Details To add customer fields to the header area and to the Information area of the service line details view, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

View

Extension Point

Design Time: Name of Entity Set

Design Time: Extension Include (in DDIC Structure)

ItemServiceLine.view.xml

extServiceLineHeaderInfo

ServiceLineCollection

SRA001S_PC_SERVICE_LINE_I BAdI: SRA001_APC_RDP NCL

Runtime: BAdI to Be Implemented

Method: IF_SRA001_EX_PC_RDP~CHANG E_ITEM_DETAILS_INFO_API

Further Extensibility Entities Business Add-Ins (BAdIs)

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 18 of 138

The following BAdIs are available for extensibility purposes: SRA001_APC_MDP You can use this BAdI to enhance the entities, that is, the OData model, of the sra001_pcapproval Gateway service. You can do this to add your own fields, for example. SRA001_APC_RDP You can use this BAdI to change the runtime data that is returned by the Gateway service and displayed on the user interface of the Approve Purchase Contract app. (This is the main purpose of this BAdI.) This includes the use of pictures, changing the list of attachments and notes displayed, and changing the workflow. For more information, see the BAdI documentation and the example implementation. The above described BAdIs are available in Customizing for Materials Management under Purchasing Contract Approve Purchase Contracts App .

More Information For a general description of the extensibility options and procedures of Fiori apps, see Extensibility.

1.4 Approve Purchase Orders With the transactional app 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.

Note You see only the purchase orders for which you are responsible. For information about the functional differences between this app and the corresponding SAP ERP back-end functionality, see SAP Note 2037650.

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.

Supported Item Categories The Approve Purchase Orders app supports the following SAP ERP item categories: Service (internal item category: 9) Limit (internal item category: 1) Standard (internal item category: 0)

System Landscape Requirements The app consists of front-end components (such as the user interfaces) and back-end components (such as the OData service). The back-end and the front-end components are delivered with one product and have to be installed in a system landscape that is enabled for SAP Fiori. Product Version Containing Back-End and

SAP Fiori principal apps for SAP ERP 1.0 SPS03

Front-End Components of the App Back-End Product Versions Supporting the

SAP ERP 6.0 SP15 or higher

App (Minimum Product Version Stack)

SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher

SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment Based on SAP enhancement package 7 of SAP ERP 6.0 also possible: Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

Related Apps Approve Requisitions Approve Purchase Contracts Track Purchase Order Order from Requisitions

Component for Customer Incidents Approve Purchase Orders (MOB-UIA-MM-APO)

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 19 of 138

More Information App History: Approve Purchase Orders App Implementation: Approve Purchase Orders App Extensibility: Approve Purchase Orders

1.4.1 App History: Approve Purchase Orders The Approve Purchase Orders app has been enhanced as follows:

SAP Fiori principal apps for SAP ERP 1.0 SPS03 (Delivery Date 07/2014) No changes.

SAP Fiori principal apps for SAP ERP 1.0 SPS02 (Delivery Date 05/2014) New/Enhanced Key Features

No changes.

New/Enhanced Extensibility Options

Add fields to master list You can add your own fields on each item in the items master list. Add fields to the purchase order item overview Add fields to the purchase order item details Add fields to the service line details Add fields to the service limit details

SAP Note for Technical Changes

1937715

SAP Fiori principal apps for SAP ERP 1.0 SPS01 (Delivery Date 02/2014) No changes.

SAP Fiori principal apps for SAP ERP 1.0 SPS00 (Delivery Date 01/2014) Initial delivery.

1.4.2 App Implementation: Approve Purchase Orders System Landscape Requirements Before you start to implement the app, ensure that your system landscape has been set up to enable SAP Fiori. This also implies that the front-end and back-end components for your app are already available in this system landscape: SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment Based on SAP enhancement package 7 of SAP ERP 6.0 also possible: Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

Configuration of Front-End Server

Configuration of SAP Fiori Infrastructure

Back-End Product Versions Supporting the App (Minimum Product Version Stack)

SAP ERP 6.0 SP15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher

Product Version Containing Back-End and

SAP Fiori principal apps for SAP ERP 1.0 SPS03

Front-End Components of the App

For more information on the installation of the back-end and front-end components of the app, see Installation of Back-End Components and Installation of Front-End Components. For the app, the following software components must be available in your system landscape. These components are contained in the product SAP Fiori principal apps for SAP ERP : Back-End/Front-End Server

Back-End/Front-End Component

Technical Name of Software Component Support Package Level

Back-end server

Back-end component

GBAPP 002 600

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

06

Page 20 of 138

Front-end server

Front-end component

03

UIX01EAP 100

Required SAP Notes For Approve Purchase Orders , the following SAP Notes must be available: Back-End/Front-End Server

SAP Note Number

Description

Both

1937715

Central note for Approve Purchase Orders . All other important notes for this app are referenced from the central note.

Implementation Tasks The following sections list tasks that have to be performed to implement the Approve Purchase Orders app. The tables contain the app-specific data required for these tasks:

Front-End Server: Activate OData Services Component

Technical Name

OData Service (Version Number)

gbapp_poapproval (1)

For more information about activating OData services, see Front-End Server: Activate OData Services.

Front-End Server: Activate UI5 Application Component

Technical Name

UI5 Application

MM_PO_APV

For more information about how to activate the UI5 application (ICF service), see Front-End Server: Activate ICF Services of UI5 Application.

Front-End Server: Enable App for Access in SAP Fiori Launchpad There are several steps to be performed to enable the app for access in the SAP Fiori launchpad. You require the listed data to perform these steps. For more information about the steps to be performed, see Setup of Catalogs, Groups, and Roles in the SAP Fiori Launchpad. Component

Technical Name

Semantic Object

PurchaseOrder

Business Role

SAP_MM_BCR_Buyer_X1

Business Catalog

SAP_MM_BC_Buyer_X1

Business Catalog Group

SAP_MM_BCG_Buyer_X1

Technical Role

SAP_MM_TCR_T_X1

Technical Catalog

SAP_MM_TC_T_X1

LPD_CUST Role

UIX01MM

LPD_CUST Instance

TRANSACTIONAL

Front-End and Back-End Server: Assign Role with OData Service Authorization to Users To grant access to OData services to specific users, you have to assign roles (including OData service authorization for the app) to your users. You have to make the assignment on the back-end and on the front-end server: On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can adjust this role according to your needs. On the front-end server, you can assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs. OData Service (Version Number)

Back-End Server: Delivered Authorization Role

Front-End Server: Authorization Role

(PFCG Role) gbapp_poapproval (1)

SAP_MM_PO_APV_APP

Use an existing role or create a new one

For more information about authorization roles and assigned OData services, see Front-End Server: Assign Role with OData Service Authorization t and Back-End Server: Assign Role with OData Service Authorization to.

Configuration Tasks To enable the Approve Purchase Orders app, the following prerequisites must be met in Customizing: You use the release strategy in Purchasing (MM-PUR). You have made the corresponding settings in Customizing for Materials Management under

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 21 of 138

Purchasing Purchase Order Release Procedure for Purchase Orders . You have configured the approval workflow for approving purchase orders. To create work items which can be approved using the app, you have set up a connection between the release strategy and SAP Business Workflow. In addition, you must perform the following configuration tasks:

Workflow Specify the workflow tasks that are relevant for approving purchase orders. You do this in Customizing for Materials Management under Purchasing Purchase Order Approve Purchase Orders App Specify Workflow Task IDs for Approve Purchase Orders App . For more information, see the documentation available in Customizing.

Storage of Notes Users of the Approve Purchase Orders app can create the following notes: Approval and rejection notes Forwarding notes System Behavior Approval and Rejection Notes Approval and rejection notes created in the Approve Purchase Orders app are stored at header level of the purchase order. The program logic assumes that text type "F18" can be used for storing the note in the database. Forwarding Notes Forwarding notes created in the Approve Purchase Orders app are stored with the work item of SAP Business Workflow. Required Activities Approval and Rejection Notes If text type "F18" does not yet exist, you must create it in Customizing for Materials Management under

Purchasing

Purchase Order

Texts for

Purchase Orders Define Text Types for Header Texts . You have to enter the Sequential Number "18". If your company already uses text type "F18" for a different purpose, you can use the BAdI Extend Runtime of Gateway Service for Approve Purchase Orders App (GBAPP_APV_PO_RDP), method SET_ATTRIBUTES, to use a different text type to store the notes. This BAdI is available in Customizing for Materials Management under Purchasing Purchase Order Approve Purchase Orders App BAdI: Change Data of Approve Purchase Orders App . Forwarding Notes You do not need to create a text type. The note is saved with the workflow item, not with the purchase order.

More Information For general information about the user management concept in a SAP Fiori environment, see Users in ABAP Front-End System and Users in ABAP Back-End System.

1.4.3 App Extensibility: Approve Purchase Orders You can extend the Approve Purchase Orders app for different aspects. For this purpose, the following extensibility options are available: Add fields to master list You can add your own fields on each item in the items master list. Add fields to the purchase order item overview Add fields to the purchase order item details Add fields to the service line details Add fields to the service limit details

Add Fields to Master List To add customer fields to each item in the master list, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

View

Extension Point

Design Time: Name of Entity Set

Design Time: Extension Include (in DDIC Structure)

S2.view.app.xml

extListItemInfo

WorkflowTaskCollection

GBAPPS_PO_WORKFLOW_TASK_I BAdI: GBAPP_APV_PO_RDP NCL

Runtime: BAdI to Be Implemented

Method: IF_GBAPP_EX_APV_PO_RDP~CH ANGE_WORKFLOW_TASK_API

Add Fields to Item Overview To add customer fields to the header area and to the Information area of the purchase order item overview, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs:

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 22 of 138

UI

Back End/ABAP

View

Extension Point

S3.view.app.xml

extHeaderInfo

Design Time: Name of Entity

Design Time: Extension

Runtime: BAdI to Be

Set

Include (in DDIC Structure)

Implemented

HeaderDetailCollection

GBAPPS_PO_HEADER_DETAILS_ BAdI: GBAPP_APV_PO_RDP Method:

INCL

extInformation

IF_GBAPP_EX_APV_PO_RDP~ CHANGE_HEADER_DETAILS_INF O_API

Add Fields to Item Details To add customer fields to the header area and to the Information area of the purchase order item details view, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

View

Extension Point

Design Time: Name of Entity Set

Design Time: Extension Include (in DDIC Structure)

S4.view.xml

extMaterialHeaderInfo

ItemDetailCollection

GBAPPS_PO_ITEM_DETAILS_IN BAdI: GBAPP_APV_PO_RDP Method: IF_GBAPP_EX_APV_PO_RDP~CH

CL

extServiceHeaderInfo

Runtime: BAdI to Be Implemented

extLimitHeaderInfo

ANGE_ITEM_DETAILS_INFO_AP I

extInformation

Add Fields to Service Line Details To add customer fields to the header area of the service line details view, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

View

Extension Point

Design Time: Name of Entity Set

Design Time: Extension Include (in DDIC Structure)

Runtime: BAdI to Be Implemented

ItemServiceLine.view.xml

extServiceLineHeaderInfo

ServiceLineCollection

GBAPPS_PO_SERVICE_LINE_IN BAdI: GBAPP_APV_PO_RDP Method: IF_GBAPP_EX_APV_PO_RDP~CH

CL

ANGE_ITEM_DETAILS_INFO_AP I

Add Fields to Service Limit Details To add customer fields to the header area of the service limit details view, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

View

Extension Point

Design Time: Name of Entity Set

ItemServiceLimit.view.xml extServiceLimitHeaderInfo LimitCollection

Design Time: Extension Include (in DDIC Structure)

Runtime: BAdI to Be Implemented

GBAPPS_PO_LIMITS_INCL

BAdI: GBAPP_APV_PO_RDP Method: IF_GBAPP_EX_APV_PO_RDP~CH ANGE_ITEM_DETAILS_INFO_AP I

Further Extensibility Entities Business Add-Ins (BAdIs) The following BAdIs are available for extensibility purposes: GBAPP_APV_PO_MDP You can use this BAdI to enhance the entities, that is, the OData model, of the gbapp_poapproval Gateway service. You can do this to add your own fields, for example. GBAPP_APV_PO_RDP You can use this BAdI to do change the runtime data that is returned by the Gateway service and displayed on the user interface of the Approve Purchase Order app. (This is the main purpose of this BAdI.) This includes the use of pictures, changing the list of attachments and notes displayed, and changing the workflow. For more information, see the BAdI documentation and the example implementation. The above described BAdIs are available in Customizing for Materials Management under App .

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Purchasing

Purchase Orders

Approve Purchase Orders

Page 23 of 138

More Information For a general description of the extensibility options and procedures of Fiori apps, see Extensibility.

1.5 Approve Service Entry Sheets With the transactional app Approve Service Entry Sheets , you can view and approve pending service entry sheets (SES), or even reject approvals. The app enables you to quickly and efficiently process the approval of service entry sheets while away from your desk.

Key Features The Approve Service Entry Sheets app enables you to: View a list of only those service entry sheets that are approvable and for which you are responsible

Note The system checks the authorization of the release code (M_EINK_FRG) in Customizing. Easily approve your service entry sheets Reject service entry sheets and enter a rejection reason in one step, but not after final approval

Note When a service entry sheet is rejected, it is sent back to the previous approval step. Your rejection notes will be visible in the app to other approvers, and they can also be viewed in the back-end in the Attachment List in the Services for Object menu (Generic Object Service – GOS).

Worklist Within your worklist, you can: Obtain an overview of each service entry sheet, including its description, creation date, value, creator, and service provider Sort according to creation date, total value, and the creator’s name Click on the responsible person to contact her/him by email or phone via business card

Service Header Within the service header, you can: View the information contained in the worklist overview for easy reference Use the details offered in the information tab to assist you in making approval decisions Access service entry sheet notes in form of generic object service texts (GOS), if available

Note Notes can only be edited in the back-end in the Service for Object menu. Examples of commonly used notes are rejection texts. Access service entry sheet attachments (GOS), if available

Note Attachments open in an additional viewer depending on your device configuration. Access the total consumed value (sum of all service entry sheets for a purchase order item) by viewing the overall percentage of consumption, overall consumed value, overall planned value, and overall limit

Service Line Overview Within the service line overview, you can: Obtain an overview of each service line, including its description, quantity, and subtotal value Quickly identify whether a service is fulfilled as planned by viewing the status: Unplanned (not included in purchase order item) Below Plan (value lower than requested in purchase order item) Above Plan (value higher than requested in purchase order item) As Planned (value equal to requested in purchase order item)

Service Line Details Within the service line details, you can: View the information contained in the service line overview for easy reference Quickly identify risk on item level and increase insight by accessing service line number, activity number, tax code, planned value, planned quantity, and company code Verify that service is posted to the correct G/L account using the following Account Assignments data: Description and Category columns contain for example the WBS element, cost center, or profit center Share column contains the percentage of the full amount that will be posted to a particular account

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 24 of 138

G/L Account column contains the account the share will be posted to

System Landscape Requirements The app consists of front-end components (such as the user interfaces) and back-end components (such as the OData service). The back-end and the front-end components are delivered in separate products and have to be installed in a system landscape that is enabled for SAP Fiori. Product Version Containing Back-End and Front-End Components of the App

SAP Fiori transactional apps for SAP ERP 1.0 SPS01

Back-End Product Versions (with Minimum

SAP ERP 6.0 SPS15 or higher

Support Package Stack) Supporting the App

SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher

SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment

Note This app is also available in a version for higher back-end releases. For more information, see SAP Help Portal at SAP Fiori for SAP ERP SAP Fiori for SAP ERP 1.0 .

http://help.sap.com/fiori_products

Component for Customer Incidents MM-SRV

More Information App History: Approve Service Entry Sheets App Implementation: Approve Service Entry Sheets App Extensibility: Approve Service Entry Sheets

1.5.1 App History: Approve Service Entry Sheets The Approve Service Entry Sheets app has been enhanced as follows:

SAP Fiori transactional apps for SAP ERP 1.0 SPS01 (Delivery Date 07/2014) Initial delivery.

1.5.2 App Implementation: Approve Service Entry Sheets System Landscape Requirements Before you start to implement the app, ensure that your system landscape has been set up to enable SAP Fiori. This also implies that the front-end and back-end components for your app are already available in this system landscape: SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment

Configuration of Front-End Server

Configuration of SAP Fiori Infrastructure

Back-End Product Versions (with Minimum Support Package Stack) Supporting the App

SAP ERP 6.0 SPS15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher

Product Version Containing Back-End and Front-End Components of the App

SAP Fiori transactional apps for SAP ERP 1.0 SPS01

For more information on the installation of the back-end and front-end components of the app, see Installation Information. For the app, the following software components must be available in your system landscape. These components are contained in the product SAP Fiori transactional apps for SAP ERP : Back-End/Front-End Server

Back-End/Front-End Component

Technical Name of Software Component Support Package Level

Back-end server

Back-end component

GBX02SAP 600

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

01

Page 25 of 138

Front-end server

Front-end component

01

UIX02EAP 100

Required SAP Notes For Approve Service Entry Sheets , the following SAP notes must be available: Back-End/Front-End Server

SAP Note Number

Description

Back-end Server

1997868

Approve Service Entry Sheets App Backend Corrections

Implementation Tasks The following sections list tasks that have to be performed to implement the Approve Service Entry Sheets app. The tables contain the app-specific data required for these tasks:

Front-End Server: Activate OData Services Component

Technical Name

OData Service (Version Number)

MM_SES_APPROVE (Version 0001)

Front-End Server: Activate UI5 Application Component

Technical Name

UI5 Application

MM_SES_APV - Description: Approve Service Entry Sheets

For more information about how to activate the UI5 application (ICF service), see Front-End Server: Activate ICF Services of UI5 Application.

Front-End Server: Enable App for Access in SAP Fiori Launchpad There are several steps to be performed to enable the app for access in the SAP Fiori launchpad. You require the listed data to perform these steps. For more information about the steps to be performed, see Setup of Catalogs, Groups, and Roles in the SAP Fiori Launchpad. Component

Technical Name

Semantic Object

ServiceEntrySheet

Business Role

SAP_MM_BCR_BUYER

Business Catalog

SAP_MM_BC_BUYER

Business Catalog Group

SAP_MM_BCG_BUYER

Technical Role

SAP_MM_TCR_T

Technical Catalog

SAP_MM_TC_T

LPD_CUST Role

UIAPMM01

LPD_CUST Instance

TRANSACTIONAL

Front-End and Back-End Server: Assign Role with OData Service Authorization to Users To restrict access to OData services to specific users, you have to assign roles (including OData service authorization for the app) to your users. You have to make the assignment on the back-end and on the front-end server: On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can adjust this role according to your needs. On the front-end server, you can assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs. OData Service (Version Number)

Back-End Server: Delivered Authorization Role (PFCG Role)

Front-End Server: Authorization Role

MM_SES_APPROVE (Version 0001)

SAP_MM_SES_APV_APP

Use an existing role or create a new one.

More Information For general information about the user management concept in a SAP Fiori environment, see Users in ABAP Front-End System and Users in ABAP Back-End System.

1.5.3 App Extensibility: Approve Service Entry Sheets You can extend Approve Service Entry Sheets according to your business needs for different aspects. For this purpose, the following extensibility options are available:

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 26 of 138

You can add custom fields at defined extension points. You can add custom tabs to the icon tab bar at defined extension points. You can manipulate the standard model at predefined UI controller hooks. You can enhance the functionality by implementing predefined Business Add-Ins. You can include custom fields via extension includes.

Extensibility Options Extension Points In addition to the extension entities described above, the following extension points are available: For the detail screen Extension Point

Use

extMoreInfo

Adds additional fields to the information area

extTabQuantities

Adds custom tabs to the icon tab bar

extMoreServiceItemListColumns

Adds columns to the service line table

extMoreServiceItemListCells

Adds cell content to the new columns

extTaskList

Adds an additional content at the end of the detail screen

For the sub detail screen Extension Point

Use

extMoreInfo

Adds additional fields to the information area

extMoreAccountAssignmentListColumns

Adds columns to the account assignments table

extMoreAccountAssignmentListCells

Adds cell content to the new columns

extMorePackageAssignmentsListColumns

Adds columns tot the outline hierarchy table

extMorePackageAssignmentListCells

Adds cell content to the new columns

extTaskList

Adds an additional content at the end of the sub detail screen

For more information about extension points, see Extension Points.

UI Controller Hooks To plug in and execute custom code, you can use the following UI controller hooks: Hook

Use

sap.ca.scfld.md.controller.ScfldMasterController~extHookAddOrCha Allows you to add new sort options or change the predefined sort options The system calls this method within the initialization of the UI. ngeSortOptions sap.ca.scfld.md.controller.ScfldMasterController~extHookGetSorte Allows you to change the sort options to determine the sort object or the sort key The system calls this method if you choose the sort option on the UI. rForSortOption

For more information about UI controller hooks, see UI Controller Hooks.

Business Add-Ins (BAdIs) The following BAdI is available for extensibility purposes: BADI_MMSRV_APPROVAL_APP You can use this BAdI to enhance the list of fields used during the approval processes, as well as the check of approval and rejection events, and also to skip or replace the standard process triggered from the app Approve Service Entry Sheets in the MM_SES_APPROVE oData service. This BAdI is available in Customizing under Materials Management App "Approve Service Entry Sheets" .

External Services Management

Business Add-Ins (BAdIs)

BAdI: Changes to Data for

Extension Includes The following extension includes are available to add custom fields to database structures in your back-end system: Extension Includes

Use

MMSES_APV_ACCOUNTING_INCL

Adds custom fields related to accounting information

MMSES_APV_HEADER_DETAIL_INCL

Adds custom fields related to the service entry sheet header

MMSES_APV_ITEM_DETAIL_INCL

Adds custom fields related to the service lines

MMSES_APV_PACKAGE_INCL

Adds custom fields related to the outline information

MMSES_APV_WORKITEM_INCL

Adds custom fields related to the worklist

After you have included custom fields into the database structures, you have to enhance the OData service SES_APPROVAL_SRV with the service builder and include the new fields on the UI via the extension points. For more information about extension includes, see Extension Includes.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 27 of 138

Additional Extensibility Options In addition, you can use the following extensibility options: You can hide all UI controls which have a tag ID assigned. You can display custom texts on the UI by replacing the i18n-file. You can hide a standard application view and add a custom view. You can use custom OData services by enhancing existing OData services with the service builder.

More Information For more information about hiding UI controls, see Concealable UI Controls. For a general description of the extensibility options and procedures of Fiori apps, see Extensibility.

1.6 Approve Supplier Invoices 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. In addition, the app supports completely parked credit memos, in this case the cross invoice amount is negative.

Note By using a Business Add-In in Customizing, you can implement your own workflow. For example, you can implement a workflow to approve invoices from the Financial Accounting (FI) component.

Key Features You can choose a work item from the list view and display it in the detail view.

Note By using Business Add-Ins in Customizing, you can return additional data from the back-end system to the list view and the detail view. In the detail view, you can also adapt business cards, for example, for the buyer or invoice clerk. 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.

Note 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.

Note For each company code, you can specify in Customizing that the History tab for previous supplier invoices is hidden. You can approve or reject supplier invoices, or you can forward them to a colleague.

Note For each company code, you can specify for the functions Approve , Reject , and Forward in Customizing that the user must add a note. Once you have approved or rejected the invoice, the note is attached to the invoice in the back-end system.

System Landscape Requirements The app consists of front-end components (such as the user interfaces) and back-end components (such as the OData service). The back-end and the front-end components are delivered in separate products and have to be installed in a system landscape that is enabled for SAP Fiori. Product Version Containing Back-End and

SAP Fiori transactional apps for SAP ERP 1.0 SPS01

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 28 of 138

Front-End Components of the App Back-End Product Versions (with Minimum Support Package Stack) Supporting the App

SAP ERP 6.0 SPS15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher

SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment

Note This app is also available in a version for higher back-end releases. For more information, see SAP Help Portal at Fiori for SAP ERP SAP Fiori for SAP ERP 1.0 .

http://help.sap.com/fiori_products

SAP

Related Apps Supplier Supplier Invoice

Component for Customer Incidents Logistics Invoice Verification (MM-IV-LIV)

More Information App History: Approve Supplier Invoices App Implementation: Approve Supplier Invoices App Extensibility: Approve Supplier Invoices

1.6.1 App History: Approve Supplier Invoices SAP Fiori transactional apps for SAP ERP 1.0 SPS 01 (Delivery Date 07/2014) Initial delivery.

1.6.2 App Implementation: Approve Supplier Invoices System Landscape Requirements Before you start to implement the app, ensure that your system landscape has been set up to enable SAP Fiori. This also implies that the front-end and back-end components for your app are already available in this system landscape: SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment

Configuration of Front-End Server

Configuration of SAP Fiori Infrastructure

Back-End Product Versions (with Minimum Support Package Stack) Supporting the App

SAP ERP 6.0 SPS15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher

Product Version Containing Back-End and Front-End Components of the App

SAP Fiori transactional apps for SAP ERP 1.0 SPS01

For more information on the installation of the back-end and front-end components of the app, see Installation Information. For the app, the following software components must be available in your system landscape. These components are contained in the product SAP Fiori transactional apps for SAP ERP : Back-End/Front-End Server

Back-End/Front-End Component

Technical Name of Software Component Support Package Level

Back-end server

Back-end component

GBX02SAP 600

01

Front-end server

Front-end component

UIX02EAP 100

01

Required SAP Notes For Approve Supplier Invoices , the following SAP Notes must be available:

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 29 of 138

Back-End/Front-End Server

SAP Note Number

Description

Back-end and front-end servers

2035248

Release Information Note Approve Supplier Invoices

Implementation Tasks The following sections list tasks that have to be performed to implement the Approve Supplier Invoices app. The tables contain the app-specific data required for these tasks:

Front-End Server: Activate OData Services Component

Technical Name

OData Service (Version Number)

MM_SUPPLIER_INVOICE_APPROVE (1)

For more information about activating OData services, see Front-End Server: Activate OData Services.

Front-End Server: Activate UI5 Application Component

Technical Name

UI5 Application

MM_SUPPLINV_APV

For more information about how to activate the UI5 application (ICF service), see Front-End Server: Activate ICF Services of UI5 Application.

Front-End Server: Enable App for Access in SAP Fiori Launchpad There are several steps to be performed to enable the app for access in the SAP Fiori launchpad. You require the listed data to perform these steps. For more information about the steps to be performed, see Setup of Catalogs, Groups, and Roles in the SAP Fiori Launchpad. Component

Technical Name

Semantic Object

SupplierInvoice

Business Role

SAP_MM_BCR_Buyer

Business Catalog

SAP_MM_BC_Buyer

Business Catalog Group

SAP_MM_BCG_Buyer

Technical Role

SAP_MM_TCR_T

Technical Catalog

SAP_MM_TC_T

LPD_CUST Role

UIAPMM01

LPD_CUST Instance

TRANSACTIONAL

Front-End and Back-End Server: Assign Role with OData Service Authorization to Users To grant access to OData services to specific users, you have to assign roles (including OData service authorization for the app) to your users. You have to make the assignment on the back-end and on the front-end server: On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can adjust this role according to your needs. On the front-end server, you can assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs. OData Service (Version Number)

Back-End Server: Delivered Authorization Role (PFCG Role)

Front-End Server: Authorization Role

MM_SUPPLIER_INVOICE_APPROVE (1)

SAP_MM_SUPPLINV_APV_APP

Use an existing role or create a new one

For more information about authorization roles and assigned OData services, see Front-End Server: Assign Role with OData Service Authorization t and Back-End Server: Assign Role with OData Service Authorization to.

Prerequisites for Configuration Before implementing the app, you must ensure the following: You have configured the approval workflow for approving supplier invoices. You have activated the Gateway service MM_SUPPLIER_INVOICE_APPROVE (Version 1) on the Gateway system.

Note The app lists the relevant invoices of all connected back-end systems, considering all clients.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 30 of 138

Configuration To be able to implement the app, you must perform the following configuration tasks in the back-end system: You have defined the company-code-dependent settings for the app. You do this in Customizing for Materials Management under Logistics Invoice Verification Apps for Logistics Invoice Verification Approve Supplier Invoices Define Settings Dependent on Company Codes . 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 .

Note 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 complete, and created an attachment (transaction MIR7).

Note For credit memos, you have posted the incoming invoice (transaction MIRO), parked a credit memo, saved as complete, and created an attachment (transaction MIR7). If a technical user creates the purchase order or parks the incoming invoice (for example, via BAPI, IDoc or eCATT), the app displays no field label for the Buyer or Invoice Clerk , because no user details are available.

More Information For general information about the user management concept in a SAP Fiori environment, see Users in ABAP Front-End System and Users in ABAP Back-End System.

1.6.3 App Extensibility: Approve Supplier Invoices You can extend Approve Supplier Invoices according to your business needs for different aspects. For this purpose, the following extensibility options are available: Extend workflow item list information You can return additional data for each workflow item in the workflow item list. Extend header information You can return additional data for the header or for the Info tab in the detail view of a selected workflow item. Extend history information You can return additional data for the History tab in the detail view of a selected workflow item. Add new tabs You can extend the icon tab bar and add new tabs.

Extend Workflow Item List Information To return additional data for each workflow item in the workflow item list, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

View

Extension Point

Design Time: Gateway Entity

s2.view.xml

CustomerExtensionForObjec WorkflowItem tListItem

Design Time: Extension Include (in DDIC Structure)

Runtime: Superclass/ Method to Be Redefined

MMIV_ASI_S_WORKFLOW_ITEM_ Superclass: MMIV_ASI_FIELD_EXTEND INCL Method: IF_EX_MMIV_ASI_FIELD_EXTE ND~ENRICH_WORKFLOWITEMS

Extend Header Information To return additional data for the header or for the Info tab in the detail view of a selected workflow item, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

View

Extension Point

Design Time: Gateway Entity

s3.view.xml

CustomerExtensionForObjec InvoiceHeader tHeader

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Design Time: Extension Include (in DDIC Structure)

Runtime: Superclass/ Method to Be Redefined

MMIV_ASI_S_INVOICE_HEADER Superclass: MMIV_ASI_FIELD_EXTEND _INCL

Page 31 of 138

Method: IF_EX_MMIV_ASI_FIELD_EXTE ND~ENRICH_HEADER s3.view.xml

MMIV_ASI_S_INVOICE_HEADER Superclass: MMIV_ASI_FIELD_EXTEND _INCL

CustomerExtensionForInfoT InvoiceHeader abForm

Method: IF_EX_MMIV_ASI_FIELD_EXTE ND~ENRICH_HEADER s3.view.xml

MMIV_ASI_S_INVOICE_HEADER Superclass: MMIV_ASI_FIELD_EXTEND _INCL

CustomerExtensionForInfoT InvoiceHeader ab

Method: IF_EX_MMIV_ASI_FIELD_EXTE ND~ENRICH_HEADER

Extend History Information To return additional data for the History tab in the detail view of a selected workflow item, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

View

Extension Point

Design Time: Gateway Entity

s3.view.xml

CustomerExtensionForHisto HistoricalInvoice ryTableColumns

Design Time: Extension Include (in DDIC Structure)

Runtime: Superclass/ Method to Be Redefined

MMIV_ASI_S_HISTORICAL_INV Superclass: MMIV_ASI_FIELD_EXTEND _INCL Method: IF_EX_MMIV_ASI_FIELD_EXTE ND~ENRICH_HISTORY

s3.view.xml

CustomerExtensionForHisto HistoricalInvoice ryTableCells

MMIV_ASI_S_HISTORICAL_INV Superclass: MMIV_ASI_FIELD_EXTEND _INCL Method: IF_EX_MMIV_ASI_FIELD_EXTE ND~ENRICH_HISTORY

Add New Tabs To add new tabs, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

View

Extension Point

Design Time: Gateway Entity

s3.view.xml

CustomerExtensionForAddit Depends on your requirements.

Design Time: Extension Include (in DDIC Structure)

Runtime: Superclass/ Method to Be Redefined

For example:ItemData

Superclass: Depends on your requirements. Method: Depends on your requirements.

ionalTab

Further Extensibility Entities Business Add-Ins (BAdIs) The following BAdIs are available for extensibility purposes: MMIV_ASI_FIELD_EXTEND You can use this BAdI to add your own fields in the Approve Supplier Invoices app. By using the BAdI methods, you can return your own data from the back-end system to the front-end system. MMIV_ASI_WORKFLOW You can use this BAdI to implement your own workflow for the Approve Supplier Invoices app: By using the BAdI method DETERMINE_TASKS you determine your own workflow tasks. You must enter the task IDs in the Customizing activity Specify Workflow Task IDs .

Note To copy a workflow template or a standard task, choose Groups Copy (transaction PFTC_COP). To change a workflow, choose

Tools

Tools

Business Workflow

Business Workflow Development

Development

Workflow Builder

Definition Tools

Workflow Builder

Tasks/Task

(transaction SWDD).

By using the BAdI method EXECUTE_DECISION you implement your own processing logic for a work item. ODATA_BUSCARD You can use this BAdI to adapt the business card in the Approve Supplier Invoices app. For example, you can add the URL address of a photo. The above described BAdIs are available in Customizing for Materials Management under

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Logistics Invoice Verification

Apps for Logistics Invoice

Page 32 of 138

Verification

Approve Supplier Invoices

Business Add-Ins (BAdIs)

.

Extension Points In addition to the extension points described above, the following extension points are available: View

Extension Point

Use

s2.view.xml

CustomerExtensionForObjectListItem

Allows you to extend items in the workflow item list.

s3.view.xml

CustomerExtensionForObjectHeader

Allows you to extend the header area of the detail view.

s3.view.xml

CustomerExtensionForInfoTabForm

Allows you to extend the Info tab inside the existing form.

s3.view.xml

CustomerExtensionForInfoTab

Allows you to extend the Info tab outside the existing form.

s3.view.xml

CustomerExtensionForHistoryTableColumns

Allows you to extend the table columns on the History

s3.view.xml

CustomerExtensionForHistoryTableCells

Allows you to extend the table rows on the History tab.

s3.view.xml

CustomerExtensionForAdditionalTab

Allows you to extend the icon tab bar. You can add new

tab.

tabs.

For more information about extension points, see Extension Points.

More Information For a general description of the extensibility options and procedures of Fiori apps, see Extensibility.

1.7 Approve Requisitions With the transactional app Approve Requisitions , you can view pending purchase requisitions and approve them. If necessary, you can forward approvals to a different employee for further processing.

Note You see only the purchase requisitions for which you are responsible. For information about the functional differences between this app and the corresponding SAP ERP back-end functionality, see SAP Note 2037651.

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 (item-based approval), and you can approve or reject entire purchase requisitions (overall approval). You can forward items of purchase requisitions or entire purchase requisitions to colleagues.

Supported Item Categories The Approve Requisitions app supports the following SAP ERP item categories: Service (internal item category: 9) Limit (internal item category: 1) Standard (internal item category: 0)

System Landscape Requirements The app consists of front-end components (such as the user interfaces) and back-end components (such as the OData service). The back-end and the front-end components are delivered with one product and have to be installed in a system landscape that is enabled for SAP Fiori. Product Version Containing Back-End and

SAP Fiori principal apps for SAP ERP 1.0 SPS03

Front-End Components of the App Back-End Product Versions Supporting the App (Minimum Product Version Stack)

SAP ERP 6.0 SP15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher

SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment Based on SAP enhancement package 7 of SAP ERP 6.0 also possible: Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 33 of 138

Related Apps Approve Purchase Orders Approve Purchase Contracts Track Purchase Order Order from Requisitions

Component for Customer Incidents Approve Requisitions (MOB-UIA-MM-ARE)

More Information App History: Approve Requisitions App Implementation: Approve Requisitions App Extensibility: Approve Requisitions

1.7.1 App History: Approve Requisitions The Approve Requisitions app has been enhanced as follows:

SAP Fiori principal apps for SAP ERP 1.0 SPS03 (Delivery Date 07/2014) No changes.

SAP Fiori principal apps for SAP ERP 1.0 SPS02 (Delivery Date 05/2014) New/Enhanced Key Features

New key features: Overall approval You can now approve all items of a purchase requisition by enabling the overall approval of purchase requisitions. Users can recognize purchase requisitions for which overall approval is enabled as follows: On entries in the master list for which overall approval is possible, the number of items belonging to the requisition is displayed. On entries that only allow item-based approval, a description of the item is displayed instead of the number.

New/Changed Implementation Details

New implementation details: If you use overall approval, you must make the following settings in Customizing: Enable overall release for the relevant document types. Specify the workflow task ID that corresponds to overall release of object type BUS2105. For more information, see App Implementation: Approve Requisitions.

New/Enhanced Extensibility Options

New extensibility options: Add fields to master list You can add your own fields to each item in the master list. Add fields to the purchase requisition item overview. This view is available if you use the overall approval of purchase requisitions. Add fields to the purchase requisition item details view (available for overall approval and item-based approval) Add fields to the service line details view Add fields to the service limit details view

SAP Note for Technical Changes

1937868

SAP Fiori principal apps for SAP ERP 1.0 SPS01 (Delivery Date 02/2014) No changes.

SAP Fiori principal apps for SAP ERP 1.0 SPS00 (Delivery Date 01/2014) Initial delivery.

1.7.2 App Implementation: Approve Requisitions

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 34 of 138

System Landscape Requirements Before you start to implement the app, ensure that your system landscape has been set up to enable SAP Fiori. This also implies that the front-end and back-end components for your app are already available in this system landscape: SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment Based on SAP enhancement package 7 of SAP ERP 6.0 also possible: Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

Configuration of Front-End Server

Configuration of SAP Fiori Infrastructure

Back-End Product Versions Supporting the App (Minimum Product Version Stack)

SAP ERP 6.0 SP15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher

Product Version Containing Back-End and Front-End Components of the App

SAP Fiori principal apps for SAP ERP 1.0 SPS03

For more information on the installation of the back-end and front-end components of the app, see Installation of Back-End Components and Installation of Front-End Components. For the app, the following software components must be available in your system landscape. These components are contained in the product SAP Fiori principal apps for SAP ERP : Back-End/Front-End Server

Back-End/Front-End Component

Technical Name of Software Component Support Package Level

Back-end server

Back-end component

GBAPP 002 600

06

Front-end server

Front-end component

UIX01EAP 100

03

Required SAP Notes For Approve Requisitions , the following SAP Notes must be available: Back-End/Front-End Server

SAP Note Number

Description

Both

1937868

Central note for Approve Requisitions . All other important notes for this app are referenced from the central note.

Implementation Tasks The following sections list tasks that have to be performed to implement the Approve Requisitions app. The tables contain the app-specific data required for these tasks:

Front-End Server: Activate OData Services Component

Technical Name

OData Service (Version Number)

gbapp_prapproval (1)

For more information about activating OData services, see Front-End Server: Activate OData Services.

Front-End Server: Activate UI5 Application Component

Technical Name

UI5 Application

MM_PR_APV

For more information about how to activate the UI5 application (ICF service), see Front-End Server: Activate ICF Services of UI5 Application.

Front-End Server: Enable App for Access in SAP Fiori Launchpad There are several steps to be performed to enable the app for access in the SAP Fiori launchpad. You require the listed data to perform these steps. For more information about the steps to be performed, see Setup of Catalogs, Groups, and Roles in the SAP Fiori Launchpad. Component

Technical Name

Semantic Object

Purchase Requisition

Business Role

SAP_MM_BCR_Buyer_X1

Business Catalog

SAP_MM_BC_Buyer_X1

Business Catalog Group

SAP_MM_BCG_Buyer_X1

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 35 of 138

Technical Role

SAP_MM_TCR_T_X1

Technical Catalog

SAP_MM_TC_T_X1

LPD_CUST Role

UIX01MM

LPD_CUST Instance

TRANSACTIONAL

Front-End and Back-End Server: Assign Role with OData Service Authorization to Users To grant access to OData services to specific users, you have to assign roles (including OData service authorization for the app) to your users. You have to make the assignment on the back-end and on the front-end server: On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can adjust this role according to your needs. On the front-end server, you can assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs. OData Service (Version Number)

Back-End Server: Delivered Authorization Role

Front-End Server: Authorization Role

(PFCG Role) gbapp_prapproval (1)

SAP_MM_PR_APV_APP

Use an existing role or create a new one

For more information about authorization roles and assigned OData services, see Front-End Server: Assign Role with OData Service Authorization t and Back-End Server: Assign Role with OData Service Authorization to.

Configuration Tasks To enable the Approve Requisitions app, the following prerequisites must be met in Customizing: You use the release strategy in Purchasing (MM-PUR). You have made the corresponding settings in Customizing for Materials Management under Purchasing Purchase Requisition Release Procedure Procedure with Classification . You have configured the approval workflow for approving purchase requisitions. When customizing the release strategy, you have indicated whether or not you want to enable overall approval of purchase requisitions or whether you only want to enable approval of requisition items.To enable overall approval, you must enable overall release for the affected document type. You do this in Customizing for Materials Management under Purchasing Purchase Requisition Define Document Types by selecting the OvRel checkbox for the document type, for example for document type NB . To create work items which can be approved using the app, you have set up a connection between the release strategy and SAP Business Workflow. In addition, you must perform the following configuration tasks:

Workflow Specify the workflow tasks that are relevant for approving purchase requisitions. You do this in Customizing for Materials Management under Purchase Requisition Approve Requisitions App Specify Workflow Task IDs for Approve Requisitions App . Note the following:

Purchasing

To enable overall approval of purchase requisitions, specify the workflow task ID that corresponds to overall release of object type BUS2105. To enable approval of purchase requisition items, specify the workflow task ID that corresponds to the release of object type BUS2009. For more information, see the documentation available in Customizing.

Storage of Notes Users of the Approve Requisitions app can create the following notes: Approval and rejection notes Forwarding notes System Behavior Approval and Rejection Notes Approval and rejection notes created in the Approve Requisitions app are stored at item level of the purchase requisition. The program logic assumes that text type "B08" can be used for storing the note in the database. Forwarding Notes Forwarding notes created in the Approve Requisitions app are stored with the work item of SAP Business Workflow. Required Activities Approval and Rejection Notes If text type "B08" does not yet exist, you must create it in Customizing for Materials Management under

Purchasing

Purchase Requisition

Texts for

Purchase Requisitions Define Text Types . You have to enter the Sequential Number "08". If your company already uses text type "B08" for a different purpose, you can use the BAdI Extend Runtime of Gateway Service for Approve Requisitions App (GBAPP_APV_PR_RDP), method SET_ATTRIBUTES, to use a different text type to store the notes. This BAdI is available in Customizing for Materials Management under Purchasing Purchase Requisition Approve Requisitions App BAdI: Change Data of Approve Requisitions App Forwarding Notes You do not need to create a text type. The note is saved with the workflow item, not with the purchase requisition.

.

More Information For general information about the user management concept in a SAP Fiori environment, see Users in ABAP Front-End System and Users in ABAP Back-End System.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 36 of 138

1.7.3 App Extensibility: Approve Requisitions You can extend the Approve Requisitions app for different aspects. For this purpose, the following extensibility options are available: Add fields to master list You can add your own fields to each item in the master list. Add fields to the purchase requisition item overview (if you use the overall approval of purchase requisitions) You can add your own Fields to the purchase requisition item overview; this screen is available if you use the overall approval of purchase requisitions. Add fields to the purchase requisition item details view (if you use overall approval) Add fields to the purchase requisition item details view (if you use item-based approval) Add fields to the service line details view Add fields to the service limit details view

Add Fields to Master List To add customer fields to each item in the master list, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

View

Extension Point

Design Time: Name of Entity Set

Design Time: Extension Include (in DDIC Structure)

S2.view.app.xml

extListItemInfo

WorkflowTaskCollection

GBAPPS_PR_WORKFLOW_TASK_I BAdI: GBAPP_APV_PR_RDP NCL

Runtime: BAdI to Be Implemented

Method: IF_GBAPP_EX_APV_PR_RDP~CH ANGE_DATA_WORKFLOW_INBOX_ API

Add Fields to Item Overview To add customer fields to the header area and to the Information area of the purchase requisition item overview, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

View

Extension Point

Design Time: Name of Entity Set

Design Time: Extension Include (in DDIC Structure)

S3_header.view.app.xml

extHeaderInfo

HeaderDetailCollection

GBAPPS_PR_HEADER_DETAILS_ BAdI: GBAPP_APV_PR_RDP INCL

extInformation

Runtime: BAdI to Be Implemented

Method: IF_GBAPP_EX_APV_PR_RDP~ CHANGE_DATA_HEADER_DETAIL S_API

Add Fields to Item Details (Overall Approval) To add customer fields to the header area and to the Information area of the purchase requisition item details view, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

View

Extension Point

Design Time: Name of Entity Set

ItemDetails.view.xml

extMaterialHeaderInfo

HeaderItemDetailCollectio GBAPPS_PR_ITEM_DETAILS_IN BAdI: GBAPP_APV_PR_RDP

extServiceHeaderInfo

n

Design Time: Extension Include (in DDIC Structure)

CL

extInformation

Runtime: BAdI to Be Implemented

Method: IF_GBAPP_EX_APV_PR_RDP~CH ANGE_DATA_ITEM_DETAILS_AP I

Add Fields to Item Details (Item-Based Approval) To add customer fields to the header area and to the Information area of the purchase requisition item details view, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

View

Extension Point

Design Time: Name of Entity Set

Design Time: Extension Include (in DDIC Structure)

S3.view.app.xml

extHeaderInfo

ItemDetailCollection

GBAPPS_PR_ITEM_DETAILS_IN BAdI: GBAPP_APV_PR_RDP

extInformation

CL

Runtime: BAdI to Be Implemented

Method: IF_GBAPP_EX_APV_PR_RDP~CH ANGE_DATA_ITEM_DETAILS_AP

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 37 of 138

I

Add Fields to Service Line Details To add customer fields to the header area of the service line details view, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

View

Extension Point

Design Time: Name of Entity Set

Design Time: Extension Include (in DDIC Structure)

Runtime: BAdI to Be Implemented

ItemServiceLine.view.xml

extServiceLineHeaderInfo

ServiceLineCollection

GBAPPS_PR_SERVICE_LINE_IN BAdI: GBAPP_APV_PR_RDP Method: IF_GBAPP_EX_APV_PR_RDP~CH

CL

ANGE_DATA_ITEM_DETAILS_AP I

Add Fields to Service Limit Details To add customer fields to the header area of the service limit details view, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

View

Extension Point

Limit.view.xml

Design Time: Name of Entity

Design Time: Extension

Runtime: BAdI to Be

Set

Include (in DDIC Structure)

Implemented

GBAPPS_PR_LIMITS_INCL

BAdI: GBAPP_APV_PR_RDP

extServiceLimitHeaderInfo LimitCollection

Method: IF_GBAPP_EX_APV_PR_RDP~CH ANGE_DATA_ITEM_DETAILS_AP I

Further Extensibility Entities Business Add-Ins (BAdIs) The following BAdIs are available for extensibility purposes: GBAPP_APV_PR_MDP You can use this BAdI to enhance the entities, that is, the OData model, of the gbapp_prapproval Gateway service of the Approve Requisitions app. You can do this to add your own fields, for example. GBAPP_APV_PR_RDP You can use this BAdI to change the runtime data that is returned by the Gateway service and displayed on the user interface of the Approve Requisitions app. (This is the main purpose of this BAdI.) This includes the use of pictures, changing the list of attachments and notes displayed, and changing the workflow. For more information, see the BAdI documentation and the example implementation. The above described BAdIs are available in Customizing for Materials Management under App .

Purchasing

Purchase Requisition

Approve Requisitions

More Information For a general description of the extensibility options and procedures of Fiori apps, see Extensibility.

1.8 Approve Timesheets With the transactional app Approve Timesheets , managers can quickly see all pending approvals for their reports, enabling them to easily approve timesheets, with one click, using their desktop or mobile device.

Key Features Review timesheets for all your employees and view time entry compliance at a glance Alternatively, view time entry details by project and cost object View a weekly summary of time entries, per employee, project, or cost object with an option to view time entry details Approve or reject time entries at both the timesheet and time entry level

System Landscape Requirements The app consists of front-end components (such as the user interfaces) and back-end components (such as the OData service). The back-end and the front-end components are delivered with one product and have to be installed in a system landscape that is enabled for SAP Fiori.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 38 of 138

Product Version Containing Back-End and Front-End Components of the App

SAP Fiori principal apps for SAP ERP 1.0 SPS03

Back-End Product Versions Supporting the

SAP ERP 6.0 SP15 or higher

App (Minimum Product Version Stack)

SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher

SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment Based on SAP enhancement package 7 of SAP ERP 6.0 also possible: Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

Related Apps My Timesheet

Component for Customer Messages MOB-UIA-PT-ATS

More Information App History: Approve Timesheets App Implementation: Approve Timesheets App Extensibility: Approve Timesheets

1.8.1 App History: Approve Timesheets The Approve Timesheets app has been enhanced as follows:

SAP Fiori principal apps for SAP ERP 1.0 SPS 03 (Delivery Date 07/2014) New/Enhanced Extensibility Options

Controller hooks are introduced.

SAP Note for Technical Changes

1931617

SAP Fiori principal apps for SAP ERP 1.0 SPS 02 (Delivery Date 05/2014) New/Enhanced Key Features

Enhanced key features: Attendance/Absence Type recorded in the back end are displayed. Wage Type and Activity Type information are displayed.

New/Enhanced Extensibility Options

No change

SAP Note for Technical Changes

1931617

SAP Fiori principal apps for SAP ERP 1.0 SPS 01 (Delivery Date 02/2014) New/Enhanced Key Features

No change

New/Enhanced Extensibility Options

New extensibility options: Extending the Details view You can now add or hide fields in the header section of the Details Page . You can now extend the table in the Details Page . OData service can now be extended.

SAP Fiori principal apps for SAP ERP 1.0 SPS 00 (Delivery Date 11/2013) Initial delivery.

1.8.2 App Implementation: Approve Timesheets PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 39 of 138

System Landscape Requirements Before you start to implement the app, ensure that your system landscape has been set up to enable SAP Fiori. This also implies that the front-end and back-end components for your app are already available in this system landscape: SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment Based on SAP enhancement package 7 of SAP ERP 6.0 also possible: Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

Configuration of Front-End Server

Configuration of SAP Fiori Infrastructure

Back-End Product Versions Supporting the App (Minimum Product Version Stack)

SAP ERP 6.0 SP15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher

Product Version Containing Back-End and Front-End Components of the App

SAP Fiori principal apps for SAP ERP 1.0 SPS03

For more information on the installation of the back-end and front-end components of the app, see Installation of Back-End Components and Installation of Front-End Components. For the app, the following software components must be available in your system landscape. These components are contained in the product SAP Fiori principal apps for SAP ERP : Back-End/Front-End Server

Back-End/Front-End Component

Technical Name of Software Component Support Package Level

Back-end server

Back-end component

SRA010 1.0

05

Front-end server

Front-end component

UIX01HCM 100

03

Required SAP Notes For Approve Timesheets, the following SAP Notes must be available: SAP Note Number

Description

1931617

Release Information

Implementation Tasks The following sections list tasks that have to be performed to implement the Approve Timesheets app. The tables contain the app-specific data required for these tasks:

Front-End Server: Activate OData Services Component

Technical Name

OData Service (Version Number)

SRA010_TIMESHEET_APPROVAL_SRV

For more information about activating OData services, see Front-End Server: Activate OData Services.

Front-End Server: Activate UI5 Application Component

Technical Name

UI5 Application

HCM_TS_APV

For more information about how to activate the UI5 application (ICF service), see Front-End Server: Activate ICF Services of UI5 Application.

Front-End Server: Enable App for Access in SAP Fiori Launchpad There are several steps to be performed to enable the app for access in the SAP Fiori launchpad. You require the listed data to perform these steps. For more information about the steps to be performed, see Setup of Catalogs, Groups, and Roles in the SAP Fiori Launchpad. Component

Technical Name

Semantic Object

TimeEntry

Business Role

SAP_HCM_BCR_MANAGER_X1

Business Catalog

SAP_HCM_BC_MANAGER_X1

Business Catalog Group

SAP_HCM_BCG_MANAGER_X1

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 40 of 138

Technical Role

SAP_HCM_TCR_T_X1

Technical Catalog

SAP_HCM_TC_T_X1

LPD_CUST Role

UIX01HCM

LPD_CUST Instance

TRANSACTIONAL

Front-End and Back-End Server: Assign Role with OData Service Authorization to Users To restrict access to OData services to specific users, you have to assign roles (including OData service authorization for the app) to your users. You have to make the assignment on the back-end and on the front-end server: On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can adjust this role according to your needs. On the front-end server, you can assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs. OData Service (Version Number)

Back-End Server: Delivered Authorization Role (PFCG Role)

Front-End Server: Authorization Role

SRA010_TIMESHEET_APPROVAL_SRV

SAP_HCM_TS_APV_APP

Use an existing role or create a new one

For more information about authorization roles and assigned OData services, see Front-End Server: Assign Role with OData Service Authorization t and Back-End Server: Assign Role with OData Service Authorization to.

Configuration Tasks To enable Approve Timesheets, you must perform the following configuration tasks: Enable the SICF Services for the Gateway Service name:SRA010_TIMESHEET_APPROVAL_SRV Enable the SICF Services for UI5 Service name:HCM_TS_APV Implement BAdI SRA010_BADI_TIMESHEET_APV (Optional) The BAdI has 4 methods: GET_SUMMARY, TIME_PENDING_GET_ENTITYSET, REJ_REASON_GET_ENTITYSET, APPROVE_REJECT_ACTION. You implement this BAdI if you want any custom implementation logic for any of the standard process of obtaining the following: summary of timesheet entries, pending timesheet entries, approved/rejected timesheet entries, retrieving possible reasons for rejection. For more information, see Steps to Activate BAdI Implementations

More Information For general information about the user management concept in a SAP Fiori environment, see Users in ABAP Front-End System and Users in ABAP Back-End System.

1.8.3 App Extensibility: Approve Timesheets You can extend Approve Timesheets according to your business needs for different aspects. For this purpose, the following extensibility options are available: Extending the Details view You can hide fields in the header section on Details screen. You can add additional fields in the header section on Details screen. You can extend the table in the Details screen.

Note In addition, any of the complete views can be replaced by your own view.

Extending the Details view To hide or add additional fields in the header section of the Details screen, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs: UI View

S3.view.xml

Back End/ABAP Extension Point

extS3Header

Design Time: Gateway Entity

Design Time: Extension

Runtime: Superclass/ Method

Include (in DDIC Structure)

to Be Redefined

SRA010_TIMESHEET_APPROVAL SRA010_S_TIME_PENDING_INC Superclass: CL_SRA010_TIMESHEET_AP_DP _SRV L C_EXT Method: TIME_PENDING_GET_ENTITYSE T SRA010_S_REJ_REASON_INCL

Superclass: CL_SRA010_TIMESHEET_AP_DP

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 41 of 138

C_EXT Method: REJ_REASON_GET_ENTITYSET

To extend the table in the Details screen, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

View

Extension Point

Design Time: Gateway Entity

S3.view.xml

extS3Table

SRA010_TIMESHEET_APPROVAL SRA010_S_TIME_PENDING_INC Superclass: _SRV

Design Time: Extension Include (in DDIC Structure)

Runtime: Superclass/ Method to Be Redefined

CL_SRA010_TIMESHEET_AP_DP

L

C_EXT Method: TIME_PENDING_GET_ENTITYSE T SRA010_S_REJ_REASON_INCL

Superclass: CL_SRA010_TIMESHEET_AP_DP C_EXT Method: REJ_REASON_GET_ENTITYSET

Further Extensibility Entities Extension Includes In addition to the extension includes described above, the following extension includes are available: DDIC

Extension Include

Use

SRA010_S_SUMMARY

SRA010_S_SUMMARY_INCl

Allows you to change the summary information on the app tile of the Fiori Launchpad.

For more information about extension includes, see Extension Includes.

UI Controller Hooks To plug in and execute custom code, the following hooks are available in the controller code: Controller

Hook

Use

S2.controller.js

extHookDisplayEmployeeList

Allows you to add UI or business logic

extHookDisplayCostAssignmentList S3.controller.js

extHookShowWeekData

Allows you to add UI or business logic

extHookShowPeopleData

For more information about UI controller hooks, see UI Controller Hooks.

More Information For a general description of the extensibility options and procedures of Fiori apps, see Extensibility.

1.9 Approve Travel Expenses With the transactional app Approve Travel Expenses , you can review and approve employees' travel expenses on the go or in the office. The app provides details on each receipt, and alerts you if expenses exceed the budget limits defined in your company's travel policy. You can also forward requests to another employee for approval.

Key Features Browse all approval requests in a personalized worklist Display details for a trip (cost assignment, settlement summary, individual receipts per trip) Display details for individual receipts (payment details, notes from requester) Identify travel policy violations – automatic alerts appear when expenses exceed set budget limits Approve travel expenses Reject travel expenses (with note to requester) Forward the approval request to another employee

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 42 of 138

System Landscape Requirements The app consists of front-end components (such as the user interfaces) and back-end components (such as the OData service). The back-end and the front-end components are delivered with one product and have to be installed in a system landscape that is enabled for SAP Fiori. Product Version Containing Back-End and Front-End Components of the App Back-End Product Versions Supporting the App (Minimum Product Version Stack)

SAP Fiori principal apps for SAP ERP 1.0 SPS03

SAP ERP 6.0 SP15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher

SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment Based on SAP enhancement package 7 of SAP ERP 6.0 also possible: Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

Related Apps Approve Travel Requests My Travel Requests

Component for Customer Messages MOB-UIA-FI-ATE: Approve Travel Expenses

More Information App History: Approve Travel Expenses App Implementation: Approve Travel Expenses App Implementation: Approve Travel Expenses

1.9.1 App History: Approve Travel Expenses The Approve Travel Expenses app has been enhanced as follows:

SAP Fiori Principal Apps for SAP ERP 1.0 SPS 003 (Delivery Date 07/2014) No changes.

SAP Fiori Principal Apps for SAP ERP 1.0 SPS 002 (Delivery Date 05/2014) No changes.

SAP Fiori Principal Apps for SAP ERP 1.0 SPS 001 (Delivery Date 02/2014) No changes.

SAP Fiori Principal Apps for SAP ERP 1.0 SPS 00 (Delivery Date 11/2013) Initial delivery.

1.9.2 App Implementation: Approve Travel Expenses System Landscape Requirements Before you start to implement the app, ensure that your system landscape has been set up to enable SAP Fiori. This also implies that the front-end and back-end components for your app are already available in this system landscape: SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment Based on SAP enhancement package 7 of SAP ERP 6.0 also possible:

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 43 of 138

Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS Configuration of Front-End Server

Configuration of SAP Fiori Infrastructure

Back-End Product Versions Supporting the App (Minimum Product Version Stack)

SAP ERP 6.0 SP15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher

Product Version Containing Back-End and Front-End Components of the App

SAP Fiori principal apps for SAP ERP 1.0 SPS03

For more information on the installation of the back-end and front-end components of the app, see Installation of Back-End Components and Installation of Front-End Components. For the app, the following software components must be available in your system landscape. These components are contained in the product SAP Fiori principal apps for SAP ERP : Back-End/Front-End Server

Back-End/Front-End Component

Technical Name of Software Component Support Package Level

Back-end server

Back-end component

SRA008 1.0

05

Front-end server

Front-end component

UIX01TRV 100

02

Required SAP Notes For Approve Travel Expenses , the following SAP Notes must be available on the back-end or front-end server: Back-End/Front-End Server

SAP Note Number

Description

For more information, see the collective SAP Note.

1980947

Collective SAP Note listing all relevant SAP Notes for this app.

Implementation Tasks The following sections list tasks that have to be performed to implement the Approve Travel Expenses app. The tables contain the app-specific data required for these tasks:

Front-End Server: Activate OData Services Component

Technical Name

OData Service (Version Number)

SRA008_SRV (1)

For more information about activating OData services, see Front-End Server: Activate OData Services.

Front-End Server: Activate UI5 Application Component

Technical Name

UI5 Application

FIN_TE_APV

For more information about how to activate the UI5 application (ICF service), see Front-End Server: Activate ICF Services of UI5 Application.

Front-End Server: Enable App for Access in SAP Fiori Launchpad There are several steps to be performed to enable the app for access in the SAP Fiori launchpad. You require the listed data to perform these steps. For more information about the steps to be performed, see Setup of Catalogs, Groups, and Roles in the SAP Fiori Launchpad. Component

Technical Name

Semantic Object Business Role

SAP_TRAVEL_BCR_MANAGER_X1

Business Catalog

SAP_TRAVEL_BC_MANAGER_X1

Business Catalog Group

SAP_TRAVEL_BCG_MANAGER_X1

Technical Role

SAP_TRAVEL_TCR_T_X1

Technical Catalog

SAP_TRAVEL_TC_T_X1

LPD_CUST Role LPD_CUST Instance

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 44 of 138

Front-End and Back-End Server: Assign Role with OData Service Authorization to Users To grant access to OData services to specific users, you have to assign roles (including OData service authorization for the app) to your users. You have to make the assignment on the back-end and on the front-end server: On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can adjust this role according to your needs. On the front-end server, you can assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs. OData Service (Version Number)

Back-End Server: Delivered Authorization Role (PFCG Role)

Front-End Server: Authorization Role

SRA008_SRV (1)

SAP_FIN_TE_APV_APP

Use an existing role or create a new one.

For more information about authorization roles and assigned OData services, see Front-End Server: Assign Role with OData Service Authorization t and Back-End Server: Assign Role with OData Service Authorization to.

Prerequisites for Configuration There are no app-specific prerequisites.

Configuration Tasks To be able to implement the app, you must perform the following configuration tasks: Ensure that the SRA008_T_CONFIG configuration table is maintained: The table must be maintained for a workflow decision key in case of a custom workflow for travel expense approval. A node for this task is provided in Customizing. Ensure that the SRA008_T_TASKTYP configuration table is maintained: The table must be maintained for the task type used for approving the travel expense. A node for this task is provided in Customizing. Ensure that the Travel Management module is installed and configured: As the app relies on configuration data available for the Travel Management module, the module must be installed and configured. In the standard workflow ( Approve Trip ), there is a two-step approval process for travel expenses. The Approve Travel Expenses app is used to perform only one approval process. You can enable one of three workflow tasks in this app: Check Trip Facts Approve Trip Facts (by default, this is used to approve travel expenses) Custom workflow

More Information For general information about the user management concept in a SAP Fiori environment, see Users in ABAP Front-End System and Users in ABAP Back-End System.

1.9.3 App Extensibility: Approve Travel Expenses You can extend Approve Travel Expenses according to your business needs for different aspects. For this purpose, the following extensibility options are available: Name: extTabAttachments Location: S3.view.app.xml Purpose: Add a new tab to the tab container Name: Additionalbuttons Location: S3.controller.js Purpose: Add buttons to the footer toolbar Name: CustomerExtensionForReceiptDetails Location: S4.view.app.xml Purpose: Customize the Receipt Details area

More Information For a general description of the extensibility options and procedures of Fiori apps, see Extensibility.

1.10 Approve Travel Requests With the transactional app Approve Travel Requests , you can approve or reject travel requests in real time using your desktop or mobile device. The app provides details on each request and also allows you to view all of an employee's past requests.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 45 of 138

Key Features Browse all pending travel requests from your employees View details of a travel request Approve travel requests Reject travel requests View the history (approved and rejected) of an employee's travel requests

System Landscape Requirements The app consists of front-end components (such as the user interfaces) and back-end components (such as the OData service). The back-end and the front-end components are delivered with one product and have to be installed in a system landscape that is enabled for SAP Fiori. Product Version Containing Back-End and

SAP Fiori principal apps for SAP ERP 1.0 SPS03

Front-End Components of the App Back-End Product Versions Supporting the App (Minimum Product Version Stack)

SAP ERP 6.0 SP15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher

SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment Based on SAP enhancement package 7 of SAP ERP 6.0 also possible: Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

Related Apps Approve Travel Expenses My Travel Requests

Component for Customer Messages MOB-UIA-FI-ATR: Approve Travel Requests

More Information App History: Approve Travel Requests App Implementation: Approve Travel Requests App Extensibility: Approve Travel Requests

1.10.1 App History: Approve Travel Requests The Approve Travel Requests app has been enhanced as follows:

SAP Fiori for SAP ERP Principal Apps 1.0 SPS 003 (Delivery Date 07/2014) No changes.

SAP Fiori for SAP ERP Principal Apps 1.0 SPS 002 (Delivery Date 05/2014) No changes.

SAP Fiori for SAP ERP Principal Apps 1.0 SPS 001 (Delivery Date 02/2014) No changes.

SAP Fiori for SAP ERP Principal Apps 1.0 SPS 00 (Delivery Date 11/2013) Initial delivery.

1.10.2 App Implementation: Approve Travel Requests PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 46 of 138

System Landscape Requirements Before you start to implement the app, ensure that your system landscape has been set up to enable SAP Fiori. This also implies that the front-end and back-end components for your app are already available in this system landscape: SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment Based on SAP enhancement package 7 of SAP ERP 6.0 also possible: Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

Configuration of Front-End Server

Configuration of SAP Fiori Infrastructure

Back-End Product Versions Supporting the App (Minimum Product Version Stack)

SAP ERP 6.0 SP15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher

Product Version Containing Back-End and Front-End Components of the App

SAP Fiori principal apps for SAP ERP 1.0 SPS03

For more information on the installation of the back-end and front-end components of the app, see Installation of Back-End Components and Installation of Front-End Components. For the app, the following software components must be available in your system landscape. These components are contained in the product SAP Fiori principal apps for SAP ERP : Back-End/Front-End Server

Back-End/Front-End Component

Technical Name of Software Component Support Package Level

Back-end server

Back-end component

SRA009 1.0

04

Front-end server

Front-end component

UIX01TRV 100

02

Required SAP Notes For Approve Travel Requests , the following SAP Notes must be available on the back-end or front-end server: Back-End/Front-End Server

SAP Note Number

Description

For more information, see the collective SAP Note.

1980945

Collective SAP Note listing all relevant SAP Notes for this app.

Implementation Tasks The following sections list tasks that have to be performed to implement the < Approve Travel Requests > app. The tables contain the app-specific data required for these tasks:

Front-End Server: Activate OData Services Component

Technical Name

OData Service (Version Number)

SRA009_SRV (1)

For more information about activating OData services, see Front-End Server: Activate OData Services.

Front-End Server: Activate UI5 Application Component

Technical Name

UI5 Application

ui5_fi_trreq_apv

For more information about how to activate the UI5 application (ICF service), see Front-End Server: Activate ICF Services of UI5 Application.

Front-End Server: Enable App for Access in SAP Fiori Launchpad There are several steps to be performed to enable the app for access in the SAP Fiori launchpad. You require the listed data to perform these steps. For more information about the steps to be performed, see Setup of Catalogs, Groups, and Roles in the SAP Fiori Launchpad. Component

Technical Name

Semantic Object Business Role

SAP_TRAVEL_BCR_MANAGER_X1

Business Catalog

SAP_TRAVEL_BC_MANAGER_X1

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 47 of 138

Business Catalog Group

SAP_TRAVEL_BCG_MANAGER_X1

Technical Role Technical Catalog LPD_CUST Role LPD_CUST Instance

Front-End and Back-End Server: Assign Role with OData Service Authorization to Users To grant access to OData services to specific users, you have to assign roles (including OData service authorization for the app) to your users. You have to make the assignment on the back-end and on the front-end server: On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can adjust this role according to your needs. On the front-end server, you can assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs. OData Service (Version Number)

Back-End Server: Delivered Authorization Role (PFCG Role)

Front-End Server: Authorization Role

SRA009_SRV (1)

SAP_FIN_TR_APV_APP

Use an existing role or create a new one.

For more information about authorization roles and assigned OData services, see Front-End Server: Assign Role with OData Service Authorization t and Back-End Server: Assign Role with OData Service Authorization to.

Configuration Tasks To be able to implement the app, you must perform the following configuration tasks: Ensure that the SRA009_T_CONFIG configuration table is maintained. The table must be maintained for a workflow decision key in case of a custom workflow for travel request approval. A node for this task is provided in Customizing. Ensure that the SRA009_T_TASKTYP configuration table is maintained. The table must be maintained for the task type used for approving the travel request. A node for this task is provided in Customizing.

More Information For general information about the user management concept in a SAP Fiori environment, see Users in ABAP Front-End System and Users in ABAP Back-End System.

1.10.3 App Extensibility: Approve Travel Requests You can extend Approve Travel Requests according to your business needs for different aspects. For this purpose, the following extensibility options are available: To extend Approve Travel Requests , you can use the following extension points: Name: extInfoAdditionalData Location: details.view.app.xml Purpose: Add data to the information tab Name: extTabs Location: details.view.app.xml Purpose: Add a new tab to the tab container Name: Additionalbuttons Location: details.controller.js Purpose: Add buttons to the footer toolbar

More Information For a general description of the extensibility options and procedures of Fiori apps, see Extensibility.

1.11 Change Network Activity Status With the transactional app Change Network Activity Status you can change the system and user status of a network activity.

Key Features You can inherit a user status to all sub-objects of a network activity. Prior to setting the user status to all sub-objects, you can analyze the inheritance summary for all lower level objects of the selected network activity.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 48 of 138

System Landscape Requirements The app consists of front-end components (such as the user interfaces) and back-end components (such as the OData service). The back-end and the front-end components are delivered in separate products and have to be installed in a system landscape that is enabled for SAP Fiori. Product Version Containing Back-End and Front-End Components of the App

SAP Fiori transactional apps for SAP ERP 1.0 SPS01

Back-End Product Versions (with Minimum

SAP ERP 6.0 SPS15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher

Support Package Stack) Supporting the App

SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment

Note This app is also available in a version for higher back-end releases. For more information, see SAP Help Portal at Fiori for SAP ERP SAP Fiori for SAP ERP 1.0 .

http://help.sap.com/fiori_products

SAP

Related Apps Confirm Network Activity

Component for Customer Incidents PS-ST

More Information App History: Change Network Activity Status App Implementation: Change Network Activity Status App Extensibility: Change Network Activity Status

1.11.1 App History: Change Network Activity Status The Change Network Activity Status app has been enhanced as follows:

SAP Fiori Transactional Apps for SAP ERP 1.0 SPS 01 (Delivery Date 07/2014) Initial delivery.

1.11.2 App Implementation: Change Network Activity Status System Landscape Requirements Before you start to implement the app, ensure that your system landscape has been set up to enable SAP Fiori. This also implies that the front-end and back-end components for your app are already available in this system landscape: SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment

Configuration of Front-End Server

Configuration of SAP Fiori Infrastructure

Back-End Product Versions (with Minimum Support Package Stack) Supporting the App

Product Version Containing Back-End and Front-End Components of the App

SAP ERP 6.0 SPS15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP Fiori transactional apps for SAP ERP 1.0 SPS01

For more information on the installation of the back-end and front-end components of the app, see Installation Information. For the app, the following software components must be available in your system landscape. These components are contained in the product SAP Fiori transactional apps for SAP ERP : Back-End/Front-End Server

Back-End/Front-End Component

Technical Name of Software Component Support Package Level

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 49 of 138

Back-end server

Back-end component

GBX02SAP 600

01

Front-end server

Front-end component

UIX02EAP 100

01

Implementation Tasks The following sections list tasks that have to be performed to implement the Change Network Activity Status app. The tables contain the app-specific data required for these tasks:

Front-End Server: Activate OData Services Component

Technical Name

OData Service (Version Number)

PS_NTWKACTVTSTATCHG_SRV (1)

For more information about activating OData services, see Front-End Server: Activate OData Services.

Front-End Server: Activate UI5 Application Component

Technical Name

UI5 Application

PS_ACTYSTAT_CHG

For more information about how to activate the UI5 application (ICF service), see Front-End Server: Activate ICF Services of UI5 Application.

Front-End Server: Enable App for Access in SAP Fiori Launchpad There are several steps to be performed to enable the app for access in the SAP Fiori launchpad. You require the listed data to perform these steps. For more information about the steps to be performed, see Setup of Catalogs, Groups, and Roles in the SAP Fiori Launchpad. Component

Technical Name

Semantic Object

NetworkActivity

Business Role

SAP_PS_BCR_PROJECTMANAGER

Business Catalog

SAP_PS_BC_ProjectManager

Business Catalog Group

SAP_PS_BCG_PROJECTMANAGER

Technical Role

SAP_PS_TCR_T

Technical Catalog

SAP_PS_TC_T

LPD_CUST Role

UIAPPS01

LPD_CUST Instance

TRANSACTIONAL

Front-End and Back-End Server: Assign Role with OData Service Authorization to Users To grant access to OData services to specific users, you have to assign roles (including OData service authorization for the app) to your users. You have to make the assignment on the back-end and on the front-end server: On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can adjust this role according to your needs. On the front-end server, you can assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs. OData Service (Version Number)

Back-End Server: Delivered Authorization Role (PFCG Role)

Front-End Server: Authorization Role

PS_NTWKACTVTSTATCHG_SRV (1)

SAP_PS_ACTY_STATUS_CHG_APP

Use an existing role or create a new one

For more information about authorization roles and assigned OData services, see Front-End Server: Assign Role with OData Service Authorization t and Back-End Server: Assign Role with OData Service Authorization to.

More Information For general information about the user management concept in a SAP Fiori environment, see Users in ABAP Front-End System and Users in ABAP Back-End System.

1.11.3 App Extensibility: Change Network Activity Status You can extend Change Network Activity Status according to your business needs for different aspects. For this purpose, the following extensibility options are available:

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 50 of 138

Extensibility Entity To add a customer field to the app, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

View

Extension Point

Design Time: Gateway Entity

S3.view.xml

extSystemStatusTabContent PS_NTWKACTVTSTATCHG_SRV

S3.view.xml

extUserStatusTabContent

Design Time: Extension Include (in DDIC Structure)

Runtime: Superclass/ Method to Be Redefined

PSACTIVITY_S_INCL

Superclass: IF_PS_ODATA_ACTIVITY_CONF IRM Method: UPDATE_SELECTED_RECORDS UPDATE_ACTIVITY_DETAIL

Additional Extensibility Entities Business Add-Ins (BAdIs) The following BAdIs are available for extensibility purposes: BADI_PS_ODATA_ACTY_CONFIRM You can use this BAdI to add attributes to the existing application. For more information on this BAdI for OData services, see SAP Customizing Implementation Guide Project System Structures Operative Structures Business Add-Ins for OData Services BAdI: Activity OData Service

More Information For a general description of the extensibility options and procedures of Fiori apps, see Extensibility.

1.12 Change Sales Orders With the transactional app Change Sales Orders , you can modify or display sales orders on field interactively on desktop, tablet, and mobile platforms.

Key Features Browse and search your list of sales orders Change ship-to addresses for open order items Access sales orders

System Landscape Requirements The app consists of front-end components (such as the user interfaces) and back-end components (such as the OData service). The back-end and the front-end components are delivered in separate products and have to be installed in a system landscape that is enabled for SAP Fiori. Back-End Components Delivered with (Product Version Stack)

Front-End Components Delivered with (Product Version Stack)

SAP ERP 6.0 SP15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher SAP Fiori principal apps for SAP ERP 1.0 SPS02

SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

Component for Customer Incidents MOB-UIA-SD-CSO (Change Sales Orders)

More Information App History: Change Sales Orders App Implementation: Change Sales Orders App Extensibility: Change Sales Orders

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 51 of 138

1.12.1 App History: Change Sales Orders The Change Sales Order app has been enhanced as follows:

SAP Fiori for SAP ERP 1.0 SPS03 (Delivery Date 07/2014) New/Enhanced Key Features

No change

SAP Note for Technical Changes

1942983

SAP Fiori for SAP ERP 1.0 SPS02 (Delivery Date 05/2014) New/Enhanced Key Features

New/ Changed Extensibility Details

Incoterms Incoterms display in the Item details section of the Track Sales Order app. Multiple Document Types You can view sales orders of different document types. New: Extension points are available for the following: List Item Sales Order Header details Item Column Header Item Column Value Item Level details For more information, see App Extensibility: Change Sales Orders.

New/ Changed Implementation Details

The following activity is available for customizing purposes for Sales and Distribution under Track Sales Order : Additional Sales Order Document Types You can configure multiple document types in addition to the standard sales order document type. For more information, see App Implementation: Change Sales Orders.

SAP Note for Technical Changes

1942983

SAP Fiori for SAP ERP 1.0 SPS01 (Delivery Date 02/2014) New/Enhanced Key Features

Enhanced:

New/Changed BAdIs for Extensibility

New:

You can view more than 100 list items.

OData extensibility You can add back-end extensibility to OData services. Extension points You can add front-end extensibility. The following BAdIs are available for extensibility purposes in Customizing for Sales and Distribution under Track Sales Order : BAdI: Extending the Sales Scheduled Item You can use this BAdI to populate custom fields or extend the business functionality in the Scheduled Items section of the app. BAdI: Extending the Sales Order Item You can use this BAdI to populate custom fields or extend the business functionality in the Item details section of the app. BAdI: Extending the Sales Order Header You can use this BAdI to populate custom fields or extend the business functionality in the Header section of the app. SAP Note for Technical Changes

1942941

SAP Fiori for SAP ERP 1.0 SPS 00 (Delivery Date 11/2013) Initial delivery.

1.12.2 App Implementation: Change Sales Orders System Landscape Requirements Before you start to implement the app, ensure that your system landscape has been set up to enable SAP Fiori. This also implies that the front-end and back-end components for your app are already available in this system landscape:

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 52 of 138

SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment Based on SAP enhancement package 7 of SAP ERP 6.0 also possible: Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

Configuration of Front-End Server

Configuration of SAP Fiori Infrastructure

Back-End Product Versions Supporting the

SAP ERP 6.0 SP15 or higher

App (Minimum Product Version Stack)

SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher

Product Version Containing Back-End and Front-End Components of the App

SAP Fiori principal apps for SAP ERP 1.0 SPS03

For more information on the installation of the back-end and front-end components of the app, see Installation of Back-End Components and Installation of Front-End Components. For the app, the following software components must be available in your system landscape. These components are contained in the product SAP Fiori principal apps for SAP ERP : Back-End/Front-End Server

Back-End/Front-End Component

Technical Name of Software Component Support Package Level

Back-end server

Back-end component

SRA003 1.0

01

Front-end server

Front-end component

UIX01EAP 100

03

Required SAP Notes For Change Sales Orders, the following SAP Note must be available: Back-End/Front-End Server

SAP Note Number

Description

Back-End and Front-End Server

1942983

Release Note for the ERP SD FIORI application - Change Sales Orders

Implementation Tasks The following sections list tasks that have to be performed to implement the Change Sales Orders app. The tables contain the app-specific data required for these tasks:

Front-End Server: Activate OData Services Component

Technical Name

OData Service (Version Number)

SRA018_SO_TRACKING_SRV

Front-End Server: Activate UI5 Application Component

Technical Name

UI5 Application

SD_SO_MAN

Front-End Server: Enable App for Access in SAP Fiori Launchpad There are several steps to be performed to enable the app for access in the SAP Fiori launchpad. You require the listed data to perform these steps. Component

Technical Name

Semantic Object

SalesOrder

Business Role

SAP_SD_BCR_FIELDSALESREP_X1

Business Catalog

SAP_SD_BC_FIELDSALESREP_X1

Business Catalog Group

SAP_SD_BCG_FIELDSALESREP_X1

Technical Role

SAP_SD_TCR_T_X1

Technical Catalog

SAP_SD_TC_T_X1

LPD_CUST Role

UIX01SD

LPD_CUST Instance

TRANSACTIONAL

Front-End and Back-End Server: Assign Role with OData Service Authorization to Users To restrict access to OData services to specific users, you have to assign roles (including OData service authorization for the app) to your users. You have to make the assignment on the back-end and on the front-end server:

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 53 of 138

On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can adjust this role according to your needs. On the front-end server, you can assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs. OData Service (Version Number)

Back-End Server: Delivered Authorization Role (PFCG Role)

Front-End Server: Authorization Role

SRA018_SO_TRACKING_SRV

SRA003/SRA018:SAP_SD_SO_MAN_APP

SAP_SD_BCR_FIELDSALESREP_X1

Configuration Tasks To enable Change Sales Orders , perform these configuration tasks: Ensure that an employee master record is created and check the following: You have implemented SAP ERP HCM and maintained your employees in the HCM personnel records. The employee personnel record has the infotype Communication, with a subtype of System User Name (SY-UNAME) (Infotype 0105, Subtype 0001) If you have not implemented SAP ERP HCM, implement the Sales and Distribution configuration around Use Sales Employees with HR (Tcode: PULT). This IMG setting copies the appropriate HCM tables from the 000 Client and allows the setup of the Employee Record with the Infotype Communication and a Subtype of System User Name (SY-UNAME). (Infotype 0105, Subtype 0001).

Note It associates the USERID of the employee with the personnel number assigned as a partner function sales employee in the customer master Call the transaction SIMGH and open the Change Sales Orders node. By default, the change order functionality is disabled. To enable the change functionality, enter X as the value for the EDITENABLED parameter. By default the value for this parameter is blank. Implement the Define Additional Sales Order Document Types customizing to specify document types other than the default Standard Order (TA) type. Implement the BAdI: Customer Association to Employee to associate employees with specific customers.

More Information For general information about the user management concept in a SAP Fiori environment, see Users in ABAP Front-End System and Users in ABAP Back-End System.

1.12.3 App Extensibility: Change Sales Orders You can extend Change Sales Orders according to your business needs for different aspects. For this purpose, the following extensibility options are available: You can insert custom content to overwrite what is provided as a default inside the extension points. Extension points are inserted in the views of delivered standard applications.

Front-End and Back-End Extensibility Entities To add a customer field to the app, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

View

Extension Point

Design Time: Gateway Entity

S3.view.app.xml

extSOChangePaymentInfo

SRA018_SO_TRACKING_SRV/Sa SRA018_S_SO_HEADER

extSOChangeNotes

Design Time: Extension Include (in DDIC Structure)

lesOrder

Runtime: Superclass/ Method to Be Redefined Superclass: CL_SRA018_SO_TRACKING_DPC _EXT Method: SALESORDERS_GET_ENTITYSET

extSOHeaderDetails

ListItemTemplate.fragment extSalesOrderListAttribut .xml

es extSOChangeAttachments

SRA018_SO_TRACKING_SRV/At SRA018_S_SO_ATTACH tachment

Superclass: CL_SRA018_SO_TRACKING_DPC _EXT Method: ATTACHMENTS_GET_ENTITYSET

CSRA018_SO_TRACKING_SRV/C SRA018_S_CONTACT_ODATA ontact

Superclass: CL_SRA018_SO_TRACKING_DPC _EXT Method: CONTACTS_GET_ENTITYSET

CSRA018_SO_TRACKING_SRV/C SRA018_S_SO_COUNTRY ountry

Superclass: CL_SRA018_SO_TRACKING_DPC _EXT Method:

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 54 of 138

COUNTRIES_GET_ENTITYSET CSRA018_SO_TRACKING_SRV/C SRA018_S_SO_CUSTOMER ustomer

Superclass: CL_SRA018_SO_TRACKING_DPC _EXT Method: CUSTOMERS_GET_ENTITYSET

S4.view.app.xml S3.view.app.xml

extSOItemLevelInfoDetails CSRA018_SO_TRACKING_SRV/O SRA018_S_SO_ITEM extSOItemColumnHeader

rderItem

Superclass: CL_SRA018_SO_TRACKING_DPC _EXT Method: ORDERITEMS_GET_ENTITYSET

extSOItemColumnValue

CSRA018_SO_TRACKING_SRV/S SRA018_S_SO_SCHEDITEM cheduledItem

Superclass: CL_SRA018_SO_TRACKING_DPC _EXT Method: SCHEDULEDITEMS_GET_ENTITY SET

Additional Extensibility Entities Business Add-Ins (BAdIs) The following BAdIs are available for extensibility purposes in Customizing for Sales and Distribution . Use transaction SIMGH to open the Orders”

“Track Sales

node:

BAdI: Extending the Sales Order Header You can use this BAdI to populate custom fields for the sales order header. BAdI: Extending the Sales Order Item You can use this BAdI to populate custom fields for the sales order item. BAdI: Extending the Sales Order Scheduled Item You can use this BAdI to populate custom fields for the scheduled sales order item.

Extension Includes In addition to the extension includes described above, the following extension includes are available: DDIC

Extension Include

Use

SRA018_S_SO_HEADER

SRA018_S_SO_HEADER_INCL

Allows you to add new fields for the sales order header

SRA018_S_SO_ATTACH

SRA018_S_SO_ATTACH_INCL

Allows you to add new fields for sales order attachments

SRA018_S_CONTACT_ODATA

SRA018_S_CONTACT_CI_INCL

Allows you to add new fields for contacts

SRA018_S_SO_COUNTRY

SRA018_S_SO_COUNTRY_INCL

Allows you to add new fields for countries

SRA018_S_SO_CUSTOMER

SRA018_S_SO_CUSTOMER_INCL

Allows you to add new fields for customers

SRA018_S_SO_ITEM

SRA018_S_SO_ITEM_INCL

Allows you to add new fields for sales order items

SRA018_S_SO_SCHEDITEM

SRA018_S_SO_SCHEDITEM_INCL

Allows you to add new fields for sales order items

More Information For a general description of the extensibility options and procedures of Fiori apps, see Extensibility.

1.13 Change WBS Element Status With the transactional app Change WBS Element Status , you can change the system and user status of a work breakdown structure element.

Key Features You can inherit a user status to all sub-objects of a WBS element. Prior to setting the user status to all sub-objects, you can analyze the inheritance summary for all lower level objects of the selected WBS element.

System Landscape Requirements The app consists of front-end components (such as the user interfaces) and back-end components (such as the OData service). The back-end and the front-end components are delivered in separate products and have to be installed in a system landscape that is enabled for SAP Fiori. Product Version Containing Back-End and

SAP Fiori transactional apps for SAP ERP 1.0 SPS01

Front-End Components of the App Back-End Product Versions (with Minimum Support Package Stack) Supporting the App

SAP ERP 6.0 SPS15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 55 of 138

SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment

Note This app is also available in a version for higher back-end releases. For more information, see SAP Help Portal at Fiori for SAP ERP SAP Fiori for SAP ERP 1.0 .

http://help.sap.com/fiori_products

SAP

Related Apps Confirm Network Activity

Component for Customer Incidents PS-ST

More Information App History: Change WBS Element Status App Implementation: Change WBS Element Status App Extensibility: Change WBS Element Status

1.13.1 App History: Change WBS Element Status The Change WBS Element Status app has been enhanced as follows:

SAP Fiori Transactional Apps for SAP ERP 1.0 SPS 01 (Delivery Date 07/2014) New/Enhanced Key Features

New key features: App integration with SAP JAM collaboration platform. Enhanced key features: Master Data status locked When the system status for master data is locked, you cannot delete any system status or edit a user status.

New/Enhanced Extensibility Options

No changes.

SAP Fiori Transactional Apps for SAP ERP 1.0 SPS 00 (Delivery Date 01/2014) Initial delivery.

1.13.2 App Implementation: Change WBS Element Status System Landscape Requirements Before you start to implement the app, ensure that your system landscape has been set up to enable SAP Fiori. This also implies that the front-end and back-end components for your app are already available in this system landscape: SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment

Configuration of Front-End Server

Configuration of SAP Fiori Infrastructure

Back-End Product Versions (with Minimum Support Package Stack) Supporting the App

Product Version Containing Back-End and

SAP ERP 6.0 SPS15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP Fiori transactional apps for SAP ERP 1.0 SPS01

Front-End Components of the App

For more information on the installation of the back-end and front-end components of the app, see Installation Information. For the app, the following software components must be available in your system landscape. These components are contained in the product SAP Fiori

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 56 of 138

transactional apps for SAP ERP : Back-End/Front-End Server

Back-End/Front-End Component

Technical Name of Software Component Support Package Level

Back-end server

Back-end component

GBX02SAP 600

01

Front-end server

Front-end component

UIX02EAP 100

01

Implementation Tasks The following sections list tasks that have to be performed to implement the Change WBS Element Status app. The tables contain the app-specific data required for these tasks:

Front-End Server: Activate OData Services Component

Technical Name

OData Service (Version Number)

PS_WBSELEMENTSTATUSCHANGE_SRV (1)

For more information about activating OData services, see Front-End Server: Activate OData Services.

Front-End Server: Activate UI5 Application Component

Technical Name

UI5 Application

PS_WBSELSTS_CHG

For more information about how to activate the UI5 application (ICF service), see Front-End Server: Activate ICF Services of UI5 Application.

Front-End Server: Enable App for Access in SAP Fiori Launchpad There are several steps to be performed to enable the app for access in the SAP Fiori launchpad. You require the listed data to perform these steps. For more information about the steps to be performed, see Setup of Catalogs, Groups, and Roles in the SAP Fiori Launchpad. Component

Technical Name

Semantic Object

WBSElement

Business Role

SAP_PS_BCR_PROJECTMANAGER

Business Catalog

SAP_PS_BC_ProjectManager

Business Catalog Group

SAP_PS_BCG_PROJECTMANAGER

Technical Role

SAP_PS_TCR_T

Technical Catalog

SAP_PS_TC_T

LPD_CUST Role

UIAPPS01

LPD_CUST Instance

TRANSACTIONAL

Front-End and Back-End Server: Assign Role with OData Service Authorization to Users To grant access to OData services to specific users, you have to assign roles (including OData service authorization for the app) to your users. You have to make the assignment on the back-end and on the front-end server: On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can adjust this role according to your needs. On the front-end server, you can assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs. OData Service (Version Number)

Back-End Server: Delivered Authorization Role (PFCG Role)

Front-End Server: Authorization Role

PS_WBSELEMENTSTATUSCHANGE_SRV (1)

SAP_PS_WBSELSTS_CHG_APP

Use an existing role or create a new one

For more information about authorization roles and assigned OData services, see Front-End Server: Assign Role with OData Service Authorization t and Back-End Server: Assign Role with OData Service Authorization to.

More Information For general information about the user management concept in a SAP Fiori environment, see Users in ABAP Front-End System and Users in ABAP Back-End System.

1.13.3 App Extensibility: Change WBS Element Status You can extend Change WBS Element Status according to your business needs for different aspects. For this purpose, the following extensibility options are

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 57 of 138

available:

Extensibility Entity To add a customer field to the app, the following extensibility entities are available on the different layers. You have to extend each of theses entities according to your specific business needs: UI

Back-End / ABAP

View

Extension Point

S3.view.xml

extSystemStatusTabContent PS_WBSELEMENTSTATUSCHANGE PSWBSELEMENT_S_INCL

S3.view.xml

extUserStatusTabContent

Design Time: Gateway Entity

Design Time: Extension Include (in DDIC Structure)

_SRV

Run Time: Superclass and Method to be Redefined Superclass: IF_PS_ODATA_WBS_STATUS_CH Method: UPDATE_SELECTED_RECORDS

Additional Extensibility Entities Business Add-Ins (BAdIs) The following BAdI is available for extensibility purposes: BADI_PS_ODATA_WBS_STATUS_CHG You can use this BAdI to add attributes to the existing application. For more information on this BAdI for OData services, see SAP Customizing Implementation Guide Project System Structures Operative Structures Business Add-Ins for OData Services BAdI: WBS Element OData Service

More Information For a general description of the extensibility options and procedures of Fiori apps, see Extensibility

1.14 Check Price and Availability With the transactional app Check Price and Availability , you can check the price and availability of products on field interactively on desktop, tablet, and mobile platforms.

Key Features Provides a list of products per customer based on the their last sales orders Provides detailed information about a product from the material master Provides classification information about a selected product, if it is configurable Checks the price and availability of a product based on the quantity and requested delivery date from a specific customer

System Landscape Requirements The app consists of front-end components (such as the user interfaces) and back-end components (such as the OData service). The back-end and the front-end components are delivered in separate products and have to be installed in a system landscape that is enabled for SAP Fiori. Back-End Components Delivered with (Product Version Stack)

Front-End Components Delivered with (Product Version Stack)

SAP ERP 6.0 SP15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher SAP Fiori principal apps for SAP ERP 1.0 SPS02

SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

Component for Customer Incidents MOB-UIA-SD-PA (Check Price and Availability)

More Information App History: Check Price and Availability

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 58 of 138

App Implementation: Check Price and Availability App Extensibility: Check Price and Availability

1.14.1 App History: Check Price and Availability The Check Price and Availability app has been enhanced as follows:

SAP Fiori for SAP ERP 1.0 SPS03 (Delivery Date 07/2014) New/Enhanced Key Features

No change

SAP Note for Technical Changes

1942939

SAP Fiori for SAP ERP 1.0 SPS02 (Delivery Date 05/2014) New/Enhanced Key Features

Enhanced: The issue with the OData service regeneration is fixed. The search returns results from the back-end.

SAP Note for Technical Changes

1942939

SAP Fiori for SAP ERP 1.0 SPS01 (Delivery Date 02/2014) New/Enhanced Key Features

No change.

New/Changed BAdIs for Extensibility

New BAdIs: The following BAdIs are available for extensibility purposes in Customizing for Sales and Distribution under Check Price and Availability : BAdI: Extending Check Price and Availability You can use this BAdI to populate custom fields or extend the business functionality of the app. For more information, see App Extensibility: Check Price and Availability.

SAP Note for Technical Changes

1942939

SAP Fiori for SAP ERP 1.0 SPS 00 (Delivery Date 11/2013) Initial delivery.

1.14.2 App Implementation: Check Price and Availability System Landscape Requirements Before you start to implement the app, ensure that your system landscape has been set up to enable SAP Fiori. This also implies that the front-end and back-end components for your app are already available in this system landscape: SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment Based on SAP enhancement package 7 of SAP ERP 6.0 also possible: Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

Configuration of Front-End Server

Configuration of SAP Fiori Infrastructure

Back-End Product Versions Supporting the App (Minimum Product Version Stack)

Product Version Containing Back-End and Front-End Components of the App

SAP ERP 6.0 SP15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher SAP Fiori principal apps for SAP ERP 1.0 SPS03

For more information on the installation of the back-end and front-end components of the app, see Installation of Back-End Components and Installation of Front-End Components. For the app, the following software components must be available in your system landscape. These components are contained in the product SAP Fiori principal apps for SAP ERP : Back-End/Front-End Server

Back-End/Front-End Component

Technical Name of Software Component Support Package Level

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 59 of 138

Back-end server

Back-end component

SRA016 1.0

05

Front-end server

Front-end component

UIX01EAP 100

03

Required SAP Notes For Check Price and Availability, the following SAP Note must be available: Back-End/Front-End Server

SAP Note Number

Description

Back-End and Front-End Server

1942939

Release Note for the ERP SD FIORI application - Check Price and Availability

Implementation Tasks The following sections list tasks that have to be performed to implement the Check Price and Availability app. The tables contain the app-specific data required for these tasks:

Front-End Server: Activate OData Services Component

Technical Name

OData Service (Version Number)

SRA016_PRICE_AVAIL_SRV

Front-End Server: Activate UI5 Application Component

Technical Name

UI5 Application

SD_PRAV_MON

Front-End Server: Enable App for Access in SAP Fiori Launchpad There are several steps to be performed to enable the app for access in the SAP Fiori launchpad. You require the listed data to perform these steps. Component

Technical Name

Semantic Object

SalesOrder

Business Role

SAP_SD_BCR_FIELDSALESREP_X1

Business Catalog

SAP_SD_BC_FIELDSALESREP_X1

Business Catalog Group

SAP_SD_BCG_FIELDSALESREP_X1

Technical Role

SAP_SD_TCR_T_X1

Technical Catalog

SAP_SD_TC_T_X1

LPD_CUST Role

UIX01SD

LPD_CUST Instance

TRANSACTIONAL

Front-End and Back-End Server: Assign Role with OData Service Authorization to Users To restrict access to OData services to specific users, you have to assign roles (including OData service authorization for the app) to your users. You have to make the assignment on the back-end and on the front-end server: On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can adjust this role according to your needs. On the front-end server, you can assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs. OData Service (Version Number)

Back-End Server: Delivered Authorization Role (PFCG Role)

Front-End Server: Authorization Role

SRA016_PRICE_AVAIL_SRV

SRA016:SAP_SD_PRAV_MON_APP

SAP_SD_BCR_FIELDSALESREP_X1

Configuration Tasks To enable Check Price and Availability , perform these configuration tasks: Map 0105 communication type for the employee PERNR to the system user ID. Enable the SRA016_PRICE_AVAIL_SRV SICF Services for the Gateway and SD_PRAV_MON SICF Services for UI5. Call transaction SIMGH to open the Check Price and Availability node to configure user information with the Sales Order Document type and Price Condition type in the SRA016_T_CONFIG table. Implement the following BAdIs: BAdI: Fetch Customers You can use this BAdI to fetch a list of customers associated with a specific employee. BAdI: Retrieve Product Image

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 60 of 138

You can use this BAdI to retrieve the image of a product.

More Information For general information about the user management concept in a SAP Fiori environment, see Users in ABAP Front-End System and Users in ABAP Back-End System.

1.14.3 App Extensibility: Check Price and Availability You can extend Check Price and Availability according to your business needs for different aspects. For this purpose, the following extensibility options are available: You can insert custom content to overwrite what is provided as a default inside the extension points. Extension points are inserted in the views of delivered standard applications.

Front-End and Back-End Extensibility Entities To add a customer field to the app, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

View

Extension Point

Design Time: Gateway Entity

Design Time: Extension

Runtime: Superclass/ Method

Include (in DDIC Structure)

to Be Redefined

ListItemTemplate.fragment extDefaultProductAttribut SRA016_PRICE_AVAIL_SRV/Pr SRA016_S_PA_PRODUCT_ATTRB Superclass: CL_SRA016_PRICE_AVAIL_DPC .xml es oductAttribute _EXT

extProductAttributes S3.view.app.xml

extProductDefaultDetailAt

Method: PRODUCTATTRIBUTE_GET_ENTI

tributes

TYSET

extProductDetailAttribute s SRA016_PRICE_AVAIL_SRV/Cu SRA016_S_PA_CUSTOMER stomer

Superclass: CL_SRA016_PRICE_AVAIL_DPC _EXT Method: CUSTOMERCOLLECTI_GET_ENTI TYSET

SRA016_PRICE_AVAIL_SRV/Pr SRA016_S_PA_PRODUCT oduct

Superclass: CL_SRA016_PRICE_AVAIL_DPC _EXT Method: PRODUCTCOLLECTIO_GET_ENTI TYSET

SRA016_PRICE_AVAIL_SRV/Pr SRA016_S_PA_PRODUCT_AVAIL Superclass: CL_SRA016_PRICE_AVAIL_DPC oductAvailability _EXT Method: PRODUCTAVAILABIL_GET_ENTI TYSET

Additional Extensibility Entities Business Add-Ins (BAdIs) The following BAdIs are available for extensibility purposes in Customizing for Sales and Distribution . Use transaction SIMGH to open the Availability”

“Check Price and

node:

BAdI: Extending Check Price and Availability You can use this BAdI to populate custom fields such to check the availability and price of items that are on special offer.

Extension Includes In addition to the extension includes described above, the following extension includes are available: DDIC

Extension Include

Use

SRA016_S_PA_PRODUCT_ATTRB

SRA016_S_PA_PRODUCT_ATTRB_INCL

To add fields for product attributes

SRA016_S_PA_PRODUCT_AVAIL

SRA016_S_PA_PRODUCT_AVAIL_INCL

To add fields for product availability

SRA016_S_PA_CUSTOMER

SRA016_S_PA_CUSTOMER_INCL

To add fields for customers

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 61 of 138

SRA016_S_PA_PRODUCT

To add fields for products

SRA016_S_PA_PRODUCT_INCL

More Information For a general description of the extensibility options and procedures of Fiori apps, see Extensibility.

1.15 Confirm Network Activity With the transactional app Confirm Network Activity , you can confirm the processing of an activity within a network.

Key Features A network activity confirmation documents the state of processing for activities and activity elements in a network, and can be used to forecast progress in the future.

Navigation Targets The app offers the possibility to directly access other apps (for example to display detailed information).

Note These linked apps have to be already available in your system landscape or you have to implement them along with this app. Change Network Activity Status

System Landscape Requirements The app consists of front-end components (such as the user interfaces) and back-end components (such as the OData service). The back-end and the front-end components are delivered in separate products and have to be installed in a system landscape that is enabled for SAP Fiori. Product Version Containing Back-End and Front-End Components of the App Back-End Product Versions (with Minimum Support Package Stack) Supporting the App

SAP Fiori System Landscape Options

SAP Fiori transactional apps for SAP ERP 1.0 SPS01

SAP ERP 6.0 SPS15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher Setup of SAP Fiori System Landscape with ABAP Environment

Note This app is also available in a version for higher back-end releases. For more information, see SAP Help Portal at Fiori for SAP ERP SAP Fiori for SAP ERP 1.0 .

http://help.sap.com/fiori_products

SAP

Component for Customer Incidents PS-ST

More Information App History: Confirm Network Activity App Implementation: Confirm Network Activity App Extensibility: Confirm Network Activity

1.15.1 App History: Confirm Network Activity The Confirm Network Activity app has been enhanced as follows:

SAP Fiori Transactional Apps for SAP ERP 1.0 SPS 01 (Delivery Date 07/2014) New/Enhanced Key Features

New: App integration with SAP JAM collaboration platform.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 62 of 138

Enhanced: You can now navigate to the Change Network Activity Status transactional app. New/Enhanced Extensibility Options

No changes.

SAP Fiori Transactional Apps for SAP ERP 1.0 SPS 00 (Delivery Date 01/2014) Initial delivery.

1.15.2 App Implementation: Confirm Network Activity System Landscape Requirements Before you start to implement the app, ensure that your system landscape has been set up to enable SAP Fiori. This also implies that the front-end and back-end components for your app are already available in this system landscape: SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment

Configuration of Front-End Server

Configuration of SAP Fiori Infrastructure

Back-End Product Versions (with Minimum Support Package Stack) Supporting the App

Product Version Containing Back-End and

SAP ERP 6.0 SPS15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP Fiori transactional apps for SAP ERP 1.0 SPS01

Front-End Components of the App

For more information on the installation of the back-end and front-end components of the app, see Installation Information. For the app, the following software components must be available in your system landscape. These components are contained in the product SAP Fiori transactional apps for SAP ERP : Back-End/Front-End Server

Back-End/Front-End Component

Technical Name of Software Component Support Package Level

Back-end server

Back-end component

GBX02SAP 600

01

Front-end server

Front-end component

UIX02EAP 100

01

Implementation Tasks The following sections list tasks that have to be performed to implement the Confirm Network Activity app. The tables contain the app-specific data required for these tasks:

Front-End Server: Activate OData Services Component

Technical Name

OData Service (Version Number)

PS_ACTIVITY_CONFIRM (1)

For more information about activating OData services, see Front-End Server: Activate OData Services.

Front-End Server: Activate UI5 Application Component

Technical Name

UI5 Application

PS_ACTY_CONF

For more information about how to activate the UI5 application (ICF service), see Front-End Server: Activate ICF Services of UI5 Application.

Front-End Server: Enable App for Access in SAP Fiori Launchpad There are several steps to be performed to enable the app for access in the SAP Fiori launchpad. You require the listed data to perform these steps. For more information about the steps to be performed, see Setup of Catalogs, Groups, and Roles in the SAP Fiori Launchpad. Component

Technical Name

Semantic Object

NetworkActivity

Business Role

SAP_PS_BCR_PROJECTMANAGER

Business Catalog

SAP_PS_BC_ProjectManager

Business Catalog Group

SAP_PS_BCG_PROJECTMANAGER

Technical Role

SAP_PS_TCR_T

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 63 of 138

Technical Catalog

SAP_PS_TC_T

LPD_CUST Role

UIAPPS01

LPD_CUST Instance

TRANSACTIONAL

Front-End and Back-End Server: Assign Role with OData Service Authorization to Users To grant access to OData services to specific users, you have to assign roles (including OData service authorization for the app) to your users. You have to make the assignment on the back-end and on the front-end server: On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can adjust this role according to your needs. On the front-end server, you can assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs. OData Service (Version Number)

Back-End Server: Delivered Authorization Role (PFCG Role)

Front-End Server: Authorization Role

PS_ACTIVITY_CONFIRM (1)

SAP_PS_ACTY_CONF_APP

Use an existing role or create a new one

For more information about authorization roles and assigned OData services, see Front-End Server: Assign Role with OData Service Authorization t and Back-End Server: Assign Role with OData Service Authorization to.

More Information For general information about the user management concept in a SAP Fiori environment, see Users in ABAP Front-End System and Users in ABAP Back-End System.

1.15.3 App Extensibility: Confirm Network Activity You can extend Confirm Network Activity according to your business needs for different aspects. For this purpose, the following extensibility options are available:

Extensibility Entity To add a customer field to the app, the following extensibility entities are available on the different layers. You have to extend each of theses entities according to your specific business needs: UI

Back-End / ABAP

View

Extension Point

Design Time: Gateway Entity

Design Time: Extension Include (in DDIC Structure)

Run Time: Superclass and Method to be Redefined

S3.view.xml

extDetailContent

PS_ACTIVITY_CONFIRM

PSACTIVITY_S_INCL

Super Class: IF_PS_ODATA_ACTIVITY_CONF IRM Method: UPDATE_SELECTED_RECORDS

Additional Extensibility Entries Business Add-Ins (BAdIs) The following Business Add-In is available for extensibility purposes: BADI_PS_ODATA_ACTY_CONFIRM You can use this BAdI to add attributes to the existing application. For more information on this BAdI for OData services, see SAP Customizing Implementation Guide Project System Structures Operative Structures Business Add-Ins for OData Services BAdI: Activity OData Service

More Information For a general description of the extensibility options and procedures of Fiori apps, see Extensibility

1.16 Confirm Production Operations With the transactional app Confirm Production Operations production workers can view and confirm order-operations released to their work centers. They can search for the next order-operation 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 you want to confirm. Production workers can partially or finally confirm a production order-operation anytime and from any place using various mobile devices.

Key Features PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 64 of 138

Displays order-operation released to the user’s work center Enables search for a production order-operation by its number or confirmation number Allows to partially or finally confirm an order-operation Provides access to goods movement information during confirmation Allows to sort and filter the list of order-operation by status and time frame. Also allows to sort and filter by operations defined as milestone in SAP ERP back-end. Provides graphical progress bar to view confirmed quantities Runs on SAP HANA, as well as on any other database Is a web-based application that can be easily enhanced using HTML5 Enables direct navigation to Material fact sheet Offers an intuitive and user-friendly navigation

System Landscape Requirements Note This app is also available in a version for higher back-end releases. For more information, see SAP Help Portal at http://help.sap.com/fiori_products -> SAP Fiori for SAP ERP -> SAP Fiori for SAP ERP 1.0. The app consists of front-end components (such as the user interfaces) and back-end components (such as the OData service). The back-end and the front-end components are delivered in separate products and have to be installed in a system landscape that is enabled for SAP Fiori. Product Version Containing Back-End and

SAP Fiori transactional apps for SAP ERP 1.0 SPS01

Front-End Components of the App Back-End Product Versions (with Minimum Support Package Stack) Supporting the App

SAP Fiori System Landscape Options

SAP ERP 6.0 SPS15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher Setup of SAP Fiori System Landscape with ABAP Environment

Technical Requirements The following software products must be available in your system landscape: Back-End System (Business Data) Required product release: SAP enhancement package 7 for SAP ERP 6.0 SP03 Required software components: SAP_APPL 617, EA-APPL 617 UI Add-On (Front-End Components) Required product release: UI for enhancement package 7 for SAP ERP 6.0 Required software components: UIEAAP01 For more information, see App Implementation: Confirm Production Operations

Related Apps Confirm Production Orders Material Fact Sheet

Component for Customer Messages PP-SFC

More Information App History: Confirm Production Operations App Implementation: Confirm Production Operations

1.16.1 App Implementation: Confirm Production Operations System Landscape Requirements The app consists of front-end components (such as the user interfaces) and back-end components (such as the OData service). The back-end and the front-end components are delivered in separate products and have to be installed in a system landscape that is enabled for SAP Fiori. Back-End Components Delivered with (Product SAP enhancement package 7 for SAP ERP 6.0 SPS 05 Version Stack)

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 65 of 138

Front-End Components Delivered with (Product SAP Fiori for SAP ERP 1.0 SPS03 Version Stack) SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

For the app, the following software components must be available in your system landscape. These components are contained in the product SAP Fiori transactional apps for SAP ERP : Back-End/Front-End Server

Back-End/Front-End Component

Technical Name of Software Component Support Package Level

Back-end server

Back-end component

GBX02SAP 600

01

Front-end server

Front-end component

UIX02EAP 100

01

Required SAP Notes For Confirm Production Operations , the following SAP notes must be available: Back-End/Front-End Server

SAP Note Number

Description

Back-End

1893788

Conversions in SAP NetWeaver Gateway Framework

Implementation Tasks The following sections list tasks that have to be performed to implement the Confirm Production Operations app. The tables contain the app-specific data required for these tasks:

Front-End Server: Activate OData Services Component

Technical Name

OData Service (Version Number)

PP_PRODOPS_CONFIRM_SRV

For more information about activating OData services, see Front-End Server: Activate OData Services.

Front-End Server: Activate UI5 Application Component

Technical Name

UI5 Application

PP_PRODOPS_CNF

For more information about how to activate the UI5 application (ICF service), see Front-End Server: Activate ICF Services of UI5 Application.

Front-End Server: Enable App for Access in SAP Fiori Launchpad There are several steps to be performed to enable the app for access in the SAP Fiori launchpad. You require the listed data to perform these steps. For more information about the steps to be performed, see Setup of Catalogs, Groups, and Roles in the SAP Fiori Launchpad. Component

Technical Name

Semantic Object

ProductionOrderConfirmation

Business Role

SAP_PP_BCR_Worker

Business Catalog

SAP_PP_BC_Worker

Business Catalog Group

SAP_PP_BCG_Worker

Technical Role

SAP_PP_TCR_T

Technical Catalog

SAP_PP_TC_T

LPD_CUST Role

UIEAAP01

LPD_CUST Instance

TRANSACTIONAL

Front-End and Back-End Server: Assign Role with OData Service Authorization to Users To restrict access to OData services to specific users, you have to assign roles (including OData service authorization for the app) to your users. You have to make the assignment on the back-end and on the front-end server: On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can adjust this role according to your needs. On the front-end server, you can assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs. OData Service (Version Number)

Back-End Server: Delivered Authorization Role

Front-End Server: Authorization Role

(PFCG Role)

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 66 of 138

PP_PRODOPS_CONFIRM_SRV

Use an existing role or create a new one

SAP_PP_PROD_OPS_CONF_APP

For more information about authorization roles and assigned OData services, see Front-End Server: Assign Role with OData Service Authorization t and Back-End Server: Assign Role with OData Service Authorization to.

Prerequisites for Implementation Before implementing the app, you must ensure the following: Personnel number is entered under Human Resources . To do this, from the SAP Easy Access screen, choose Human Resources Personnel Management Actions . You can also use the transaction code PA40 to create a personnel number.

Administration

HR Master Data

Personnel

SAP name is assigned to the personnel number. To do this, from the SAP Easy Access screen, choose Human Resources Personnel Management Administration . In the Direct Selection section, in the Infotype field enter 105 and in the STy field enter 0001 as the subtype.

HR Master Data

Maintain

Personnel number is assigned to work center under Logistics . To do this, from the SAP Easy Access screen, choose Logistics Production cr01 to create a work center and transaction code cr02 to change a work center. After you create or change a work center, choose Basic Data Production orders exist and are released in SAP ERP.

HRMS

Master Data

Work Centers

. You can also use the transaction code

to assign the personnel number to the work center.

More Information For general information about the user management concept in a SAP Fiori environment, see Users in ABAP Front-End System and Users in ABAP Back-End System.

1.16.2 App History: Confirm Production Operations The Confirm Production Operations app has been enhanced as follows:

SAP Fiori transactional apps for SAP ERP 1.0 (Delivery Date 07/2014) No changes

SAP Fiori Transactional apps for SAP ERP 1.0 (Delivery Date 02/2014) Initial Delivery.

1.17 Confirm Production Orders With the transactional app 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 on devices such as desktop, tablet, and mobile.

Key Features Allows search for a production order by its number Display a list of orders based on the variant configured for the production order and assigned to the user in SAP ERP. Enables perform partial or final confirmation for a production order Provides access to goods movement information during confirmation Provides graphical progress bar to view planned and confirmed quantities Runs on SAP HANA as well as on any other database Is a web-based application that can be easily enhanced using HTML5 Enables direct navigation to Material fact sheet Offers an intuitive and user-friendly navigation

System Landscape Requirements Note This app is also available in a version for higher back-end releases. For more information, see SAP Help Portal at http://help.sap.com/fiori_products -> SAP Fiori for SAP ERP -> SAP Fiori for SAP ERP 1.0. The app consists of front-end components (such as the user interfaces) and back-end components (such as the OData service). The back-end and the front-end components are delivered in separate products and have to be installed in a system landscape that is enabled for SAP Fiori. Product Version Containing Back-End and

SAP Fiori transactional apps for SAP ERP 1.0 SPS01

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 67 of 138

Front-End Components of the App Back-End Product Versions (with Minimum Support Package Stack) Supporting the App

SAP Fiori System Landscape Options

SAP ERP 6.0 SPS15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher Setup of SAP Fiori System Landscape with ABAP Environment

Related Apps Confirm Production Operations Material Fact Sheet

Component for Customer Incidents PP-SFC

More Information App History: Confirm Production Orders App Implementation: Confirm Production Orders

1.17.1 App Implementation: Confirm Production Orders System Landscape Requirements The app consists of front-end components (such as the user interfaces) and back-end components (such as the OData service). The back-end and the front-end components are delivered in separate products and have to be installed in a system landscape that is enabled for SAP Fiori. Back-End Components Delivered with (Product SAP enhancement package 7 for SAP ERP 6.0 SPS 05 Version Stack) Front-End Components Delivered with (Product SAP Fiori for SAP ERP 1.0 SPS03 Version Stack) SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

For the app, the following software components must be available in your system landscape. These components are contained in the product SAP Fiori transactional apps for SAP ERP : Back-End/Front-End Server

Back-End/Front-End Component

Technical Name of Software Component Support Package Level

Back-end server

Back-end component

GBX02SAP 600

01

Front-end server

Front-end component

UIX02EAP 100

01

Required SAP Notes For Confirm Production Orders , the following SAP notes must be available: Back-End/Front-End Server

SAP Note Number

Description

Back-End

1893788

Conversions in SAP NetWeaver Gateway Framework

Implementation Tasks The following sections list tasks that have to be performed to implement the Confirm Production Orders app. The tables contain the app-specific data required for these tasks:

Front-End Server: Activate OData Services Component

Technical Name

OData Service (Version Number)

PP_PRODORD_CONFIRM

For more information about activating OData services, see Front-End Server: Activate OData Services.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 68 of 138

Front-End Server: Activate UI5 Application Component

Technical Name

UI5 Application

PP_PRODORD_CNF

For more information about how to activate the UI5 application (ICF service), see Front-End Server: Activate ICF Services of UI5 Application.

Front-End Server: Enable App for Access in SAP Fiori Launchpad There are several steps to be performed to enable the app for access in the SAP Fiori launchpad. You require the listed data to perform these steps. For more information about the steps to be performed, see Setup of Catalogs, Groups, and Roles in the SAP Fiori Launchpad. Component

Technical Name

Semantic Object

ProductionOrderConfirmation

Business Role

SAP_PP_BCR_Worker

Business Catalog

SAP_PP_BC_Worker

Business Catalog Group

SAP_PP_BCG_ Worker

Technical Role

SAP_PP_TCR_T

Technical Catalog

SAP_PP_TC_T

LPD_CUST Role

UIEAAP01

LPD_CUST Instance

TRANSACTIONAL

Front-End and Back-End Server: Assign Role with OData Service Authorization to Users To restrict access to OData services to specific users, you have to assign roles (including OData service authorization for the app) to your users. You have to make the assignment on the back-end and on the front-end server: On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can adjust this role according to your needs. On the front-end server, you can assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs. OData Service (Version Number)

Back-End Server: Delivered Authorization Role (PFCG Role)

Front-End Server: Authorization Role

PP_PRODORD_CONFIRM

SAP_PP_PROD_ORD_CONF_APP

Use an existing role or create a new one

For more information about authorization roles and assigned OData services, see Front-End Server: Assign Role with OData Service Authorization t and Back-End Server: Assign Role with OData Service Authorization to.

Prerequisites for Implementation Before implementing the app, you must ensure the following: Production order variant is created in SAP ERP (transaction code RPWPORDC1). Production order variant is assigned to the user (transaction code RPWPORDC2). Production orders exist and are released in SAP ERP.

More Information For general information about the user management concept in a SAP Fiori environment, see Users in ABAP Front-End System and Users in ABAP Back-End System.

1.17.2 App History: Confirm Production Orders The Confirm Production Order app has been enhanced as follows:

SAP Fiori for SAP ERP 1.0 SPS 03 (Delivery Date 07/2014) No changes

SAP Fiori for SAP ERP 1.0 SPS 02 (Delivery Date 05/2014) No changes.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 69 of 138

SAP Fiori for SAP ERP 1.0 SPS 01 (Delivery Date 02/2014) No changes.

SAP Fiori for SAP ERP 1.0 SPS 00 (Delivery Date 11/2013) Initial delivery.

1.18 Confirm Project Milestone With the transactional app Confirm Project Milestone app, you can confirm the milestones defined in a project.

Key Features A milestone is used to mark the transition between various phases. If you have completed such milestones in the course of a project, you can set the actual date and subsequently confirm the milestone.

System Landscape Requirements The app consists of front-end components (such as the user interfaces) and back-end components (such as the OData service). The back-end and the front-end components are delivered in separate products and have to be installed in a system landscape that is enabled for SAP Fiori. Product Version Containing Back-End and Front-End Components of the App Back-End Product Versions (with Minimum Support Package Stack) Supporting the App

SAP Fiori System Landscape Options

SAP Fiori transactional apps for SAP ERP 1.0 SPS01

SAP ERP 6.0 SPS15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher Setup of SAP Fiori System Landscape with ABAP Environment

Note This app is also available in a version for higher back-end releases. For more information, see SAP Help Portal at Fiori for SAP ERP SAP Fiori for SAP ERP 1.0 .

http://help.sap.com/fiori_products

SAP

Component for Customer Incidents PS-ST

More Information App History: Confirm Project Milestone App Implementation: Confirm Project Milestone App Extensibility: Confirm Project Milestone

1.18.1 App History: Confirm Project Milestone The Confirm Project Milestone app has been enhanced as follows:

SAP Fiori Transactional Apps for SAP ERP 1.0 SPS 01 (Delivery Date 07/2014) New/Enhanced Key Features

New key features:

New/Enhanced Extensibility Options

No changes.

App integration with SAP JAM collaboration platform.

SAP Fiori Transactional Apps for SAP ERP 1.0 SPS 00 (Delivery Date 01/2014) Initial delivery.

1.18.2 App Implementation: Confirm Project Milestone PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 70 of 138

System Landscape Requirements Before you start to implement the app, ensure that your system landscape has been set up to enable SAP Fiori. This also implies that the front-end and back-end components for your app are already available in this system landscape: SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment

Configuration of Front-End Server

Configuration of SAP Fiori Infrastructure

Back-End Product Versions (with Minimum Support Package Stack) Supporting the App

Product Version Containing Back-End and Front-End Components of the App

SAP ERP 6.0 SPS15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP Fiori transactional apps for SAP ERP 1.0 SPS01

For more information on the installation of the back-end and front-end components of the app, see Installation Information. For the app, the following software components must be available in your system landscape. These components are contained in the product SAP Fiori transactional apps for SAP ERP : Back-End/Front-End Server

Back-End/Front-End Component

Technical Name of Software Component Support Package Level

Back-end server

Back-end component

GBX02SAP 600

01

Front-end server

Front-end component

UIX02EAP 100

01

Implementation Tasks The following sections list tasks that have to be performed to implement the Confirm Project Milestone app. The tables contain the app-specific data required for these tasks:

Front-End Server: Activate OData Services Component

Technical Name

OData Service (Version Number)

PS_MILESTONE_CONFIRM (1)

For more information about activating OData services, see Front-End Server: Activate OData Services.

Front-End Server: Activate UI5 Application Component

Technical Name

UI5 Application

PS_MLST_CONF

For more information about how to activate the UI5 application (ICF service), see Front-End Server: Activate ICF Services of UI5 Application.

Front-End Server: Enable App for Access in SAP Fiori Launchpad There are several steps to be performed to enable the app for access in the SAP Fiori launchpad. You require the listed data to perform these steps. For more information about the steps to be performed, see Setup of Catalogs, Groups, and Roles in the SAP Fiori Launchpad. Component

Technical Name

Semantic Object

ProjectMilestone

Business Role

SAP_PS_BCR_PROJECTMANAGER

Business Catalog

SAP_PS_BC_ProjectManager

Business Catalog Group

SAP_PS_BCG_PROJECTMANAGER

Technical Role

SAP_PS_TCR_T

Technical Catalog

SAP_PS_TC_T

LPD_CUST Role

UIAPPS01

LPD_CUST Instance

TRANSACTIONAL

Front-End and Back-End Server: Assign Role with OData Service Authorization to Users To grant access to OData services to specific users, you have to assign roles (including OData service authorization for the app) to your users. You have to make the assignment on the back-end and on the front-end server: On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can adjust this role according to your needs.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 71 of 138

On the front-end server, you can assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs. OData Service (Version Number)

Back-End Server: Delivered Authorization Role (PFCG Role)

Front-End Server: Authorization Role

PS_MILESTONE_CONFIRM (1)

SAP_PS_MLST_CONF_APP

Use an existing role or create a new one

More Information For general information about how to implement SAP Fiori apps, see System Landscape

1.18.3 App Extensibility: Confirm Project Milestone You can extend Confirm Project Milestone according to your business needs for different aspects. For this purpose, the following extensibility options are available:

Extensibility Entity To add a customer field to the app, the following extensibility entities are available on the different layers. You have to extend each of theses entities according to your specific business needs: UI

Back-End / ABAP

View

Extension Point

Design Time: Gateway Entity

Design Time: Extension Include (in DDIC Structure)

Run Time: Superclass and Method to be Redefined

S3.view.xml

extDetailContent

PS_MILESTONE_CONFIRM

PSMILESTONE_S_INCL

Superclass: IF_PS_ODATA_MLST_CONFIRM Method: UPDATE_SELECTED_RECORDS

Further Extensibility Entities Business Add-Ins (BAdIs) The following Business Add-In is available for extensibility purposes: BADI_PS_ODATA_MLST_CONFIRM You can use this BAdI to add attributes to the existing application. For more information on this BAdI for OData services, see SAP Customizing Implementation Guide Project System Structures Operative Structures Business Add-Ins for OData Services BAdI: Milestone OData Service

Further Information For a general description of the extensibility options and procedures of Fiori apps, see Extensibility

1.19 Create Sales Orders With the transactional app Create Sales Orders , you can create or display sales orders on field interactively on desktop, tablet, and mobile platforms.

Key Features Reorder products by selecting existing customer orders Browse and search for sales orders Display sales order line items Order products by selecting from the material master Browse and search for products in the material master Check on the customer price and availability on a product based on the quantity and requested delivery date from the selected customer Select alternate ship-to addresses based on the information available from the customer master Choose multiple or single shipment for the ordered items

System Landscape Requirements The app consists of front-end components (such as the user interfaces) and back-end components (such as the OData service). The back-end and the front-end components are delivered in separate products and have to be installed in a system landscape that is enabled for SAP Fiori. Back-End Components Delivered with (Product Version Stack)

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

SAP ERP 6.0 SP15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher

Page 72 of 138

SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher Front-End Components Delivered with (Product Version Stack)

SAP Fiori principal apps for SAP ERP 1.0 SPS02

SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

Component for Customer Incidents MOB-UIA-SD-CSO (Create Sales Orders)

More Information App History: Create Sales Orders App Implementation: Create Sales Orders App Extensibility: Create Sales Orders

1.19.1 App History: Create Sales Orders The Create Sales Orders app has been enhanced as follows:

SAP Fiori for SAP ERP 1.0 SPS03 (Delivery Date 07/2014) New/Enhanced Key Features

No change

SAP Note for Technical Changes

1942941

SAP Fiori for SAP ERP 1.0 SPS02 (Delivery Date 05/2014) New/Enhanced Key Features

Enhanced: The issue with the OData service regeneration is fixed.

SAP Note for Technical Changes

1942941

SAP Fiori for SAP ERP 1.0 SPS01 (Delivery Date 02/2014) New/Enhanced Key Features

Enhanced:

New/Changed Extensibility

New:

Sold-To and Ship-To data displays for new sales orders.

OData extensibility You can now add back-end extensibility to OData services. Extension points You can now add front-end extensibility. The following BAdIs are available for extensibility purposes in Customizing for Sales and Distribution under Create Sales Order : BAdI: Extending the Sales Order Item You can use this BAdI to populate custom fields or extend the business functionality in the Item section of the Create Sales Order app. BAdI: Extending the Sales Order Header You can use this BAdI to populate custom fields or extend the business functionality in the Header section of the Create Sales Order app. For more information, see App Extensibility: Create Sales Orders. SAP Note for Technical Changes

1942941

SAP Fiori for SAP ERP 1.0 SPS 00 (Delivery Date 11/2013) Initial delivery.

1.19.2 App Implementation: Create Sales Orders

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 73 of 138

System Landscape Requirements Before you start to implement the app, ensure that your system landscape has been set up to enable SAP Fiori. This also implies that the front-end and back-end components for your app are already available in this system landscape: SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment Based on SAP enhancement package 7 of SAP ERP 6.0 also possible: Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

Configuration of Front-End Server

Configuration of SAP Fiori Infrastructure

Back-End Product Versions Supporting the

SAP ERP 6.0 SP15 or higher

App (Minimum Product Version Stack)

SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher

Product Version Containing Back-End and Front-End Components of the App

SAP Fiori principal apps for SAP ERP 1.0 SPS03

For more information on the installation of the back-end and front-end components of the app, see Installation of Back-End Components and Installation of Front-End Components. For the app, the following software components must be available in your system landscape. These components are contained in the product SAP Fiori principal apps for SAP ERP : Back-End/Front-End Server

Back-End/Front-End Component

Technical Name of Software Component Support Package Level

Back-end server

Back-end component

SRA017 1.0

04

Front-end server

Front-end component

UIX01EAP 100

03

Required SAP Notes For Create Sales Orders, the following SAP Note must be available: Back-End/Front-End Server

SAP Note Number

Description

Back-End and Front-End Server

1942941

Release Note for the ERP SD FIORI application - Create Sales Orders

Implementation Tasks The following sections list tasks that have to be performed to implement the Create Sales Orders app. The tables contain the app-specific data required for these tasks:

Front-End Server: Activate OData Services Component

Technical Name

OData Service (Version Number)

SRA017_SALESORDER_CREATE_SRV

Front-End Server: Activate UI5 Application Component

Technical Name

UI5 Application

SD_SO_CRE

Front-End Server: Enable App for Access in SAP Fiori Launchpad There are several steps to be performed to enable the app for access in the SAP Fiori launchpad. You require the listed data to perform these steps. For more information about the steps to be performed, see Setup of Catalogs, Groups, and Roles in the SAP Fiori Launchpad.

Front-End Server: SAP Fiori Launchpad Components There are several steps to be performed to enable the app for access in the SAP Fiori launchpad. You require the listed data to perform these steps. Component

Technical Name

Business Role

SAP_SD_BCR_FIELDSALESREP_X1

Business Catalog

SAP_SD_BC_FIELDSALESREP_X1

Business Catalog Group

SAP_SD_BCG_FIELDSALESREP_X1

Technical Role

SAP_SD_TCR_T_X1

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 74 of 138

Technical Catalog

SAP_SD_TC_T_X1

LPD_CUST Role

UIX01SD

LPD_CUST Instance

TRANSACTIONAL

Front-End and Back-End Server: Assign Role with OData Service Authorization to Users To restrict access to OData services to specific users, you have to assign roles (including OData service authorization for the app) to your users. You have to make the assignment on the back-end and on the front-end server: On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can adjust this role according to your needs. On the front-end server, you can assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs. OData Service (Version Number)

Back-End Server: Delivered Authorization Role

Front-End Server: Authorization Role

(PFCG Role) SRA017_SALESORDER_CREATE_SRV

SRA017:SAP_SD_SO_CRE_APP

SAP_SD_BCR_FIELDSALESREP_X1

Configuration Tasks To enable Create Sales Orders , perform these configuration tasks: Ensure that an employee master record is created as follows: You have implemented SAP ERP HCM and maintained your employees in the HCM personnel records. The employee personnel record has the infotype Communication, with a subtype of System User Name (SY-UNAME) (Infotype 0105, Subtype 0001) If you have not implemented SAP ERP HCM, you must implement the Sales and Distribution configuration around Use Sales Employees with HR (Tcode: PULT). This IMG setting copies the appropriate HCM tables from the 000 Client and allows the setup of the Employee Record with the Infotype Communication and a Subtype of System User Name (SY-UNAME). (Infotype 0105, Subtype 0001).

Note It associates the USERID of the employee with the personnel number assigned as a partner function sales employee in the customer master Call transaction SIMGH to open the Create Sales Orders node to configure user information using the following parameters: Document Type (DOCTYPE) By default, the app uses the standard order document type (technical key TA resp. OR). Changing this to something other than a sales order may significantly impact the functionality of the application. Order Period (ORDPERIOD) This defines how many days into the past sales orders are retrieved. The suggested value is 30 days. Search Period (SEAPERIOD) This defines how many days into the past a search must look for sales orders that match the search criteria. The suggested value is 90 days. Ship To Party (SHIP_TO/PARTNER_ROLE) This defines which partner role in the customer master is used for the ship-to party. The suggested value is WE. Forwarding Agent (FORWARDING_AGENT/PARTNER_ROLE) This defines which partner role in the customer master is used for the forwarding agent. The suggested value is SP. Implement the following BAdIs: Customer Association to Employee You can use this BAdI to associate employees with specific customers. Retrieve Product Image You can use this BAdI in the Create Sales Orders add-on and this does not have a default implementation.

More Information For general information about the user management concept in a SAP Fiori environment, see Users in ABAP Front-End System and Users in ABAP Back-End System.

1.19.3 App Extensibility: Create Sales Orders You can extend Create Sales Orders according to your business needs for different aspects. For this purpose, the following extensibility options are available: You can insert custom content to overwrite what is provided as a default inside the extension points. Extension points are inserted in the views of delivered standard applications.

Front-End and Back-End Extensibility Entities To add a customer field to the app, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs: UI View

Back End/ABAP Extension Point

Design Time: Gateway Entity

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Design Time: Extension Include (in DDIC Structure)

Runtime: Superclass/ Method to Be Redefined

Page 75 of 138

SalesOrderReviewCart.view extReviewOrderCostDetails SRA017_SALESORDER_CREATE_ SRA017_S_SO_HEADER_INCL .app.xml

SRV/ SalesOrder

Superclass: CL_SRA017_DPC_EXT Method: CONTACTS_GET_ENTITYSET

S3.view.app.xml

extSalesOrderDetail

SOItemDetail.view.xml

extSOItemTableColumnHeade r extSOItemTableColumnValue SRA017_SALESORDER_CREATE_ SRA017_S_SO_CUSTOMER_INCL Superclass: L_SRA017_DPC_EXT SRV/ Customer Method: CUSTOMERS_GET_ENTITYSET

SalesOrderCartDetails.vie extShippingAndPayment

SRA017_SALESORDER_CREATE_ SRA017_S_SO_ITEM_INCL

Superclass:

w.app.xml

SRV/ Order Item

CL_SRA017_DPC_EXT Method: ORDERITEMS_GET_ENTITYSET

SRA017_SALESORDER_CREATE_ SRA017_S_SO_PARTNERADDR_I Superclass: CL_SRA017_DPC_EXT SRV/ Partner Address NCL Method: PARTNERADDRESSES_GET_ENTI TYSET SalesOrderReviewCart.view extSOCCartTableColumnHead SRA017_SALESORDER_CREATE_ SRA017_S_SO_PRODUCT_INCL .app.xml

er

SRV/ Product

SalesOrderCreatePrice

extSOCCartTableColumnHead

Method: PRODUCTS_GET_ENTITYSET

AndAvailabilityCheck.view er .app.xml

Superclass: CL_SRA017_DPC_EXT

extSOCCartTableColumnValu e

SalesOrderCreateCart.view extSOCCartTableColumnValu .app.xml

e extSOCCartTableColumnValu e

ListItemTemplate.view.app extSalesOrderListAttribut .xml

es SRA017_SALESORDER_CREATE_ SRA017_S_SO_PRODATTR_INCL Superclass: CL_SRA017_DPC_EXT SRV/ Product Attribute Method: PRODUCTATTRIBUTE_GET_ENTI TYSET

Additional Extensibility Entities Business Add-Ins (BAdIs) The following extensibility BAdIs are available in Customizing for Sales and Distribution . Call transaction SIMGH to open the

“Create Sales Order”

node:

BAdI: Extending the Sales Order Header You can use this BAdI to populate custom fields for the sales order header. BAdI: Extending the Sales Order Item You can use this BAdI to populate custom fields for sales order items.

Extension Includes In addition to the extension includes described above, the following extension includes are available: DDIC

Extension Include

Use

SRA017_S_SO_HEADER

SRA017_S_SO_HEADER_INCL

Allows you to add new fields in the sales order header

SRA017_S_SO_ITEM

SRA017_S_SO_ITEM_INCL

Allows you to add new fields in sales order items

More Information For a general description of the extensibility options and procedures of Fiori apps, see Extensibility.

1.20 Customer Invoices With the transactional app Customer Invoices , you can display invoices on field interactively on desktop, tablet, and mobile platforms.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 76 of 138

Key Features Display invoices status and details in a comprehensive layout Display invoices and memos in a single application Break down invoice amounts by item, shipment or taxes Search by customer, document number, purchase order and sales order Filter and sort your invoice data

System Landscape Requirements The app consists of front-end components (such as the user interfaces) and back-end components (such as the OData service). The back-end and the front-end components are delivered in separate products and have to be installed in a system landscape that is enabled for SAP Fiori. Back-End Components Delivered with (Product Version Stack)

Front-End Components Delivered with (Product Version Stack)

SAP ERP 6.0 SP15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher SAP Fiori principal apps for SAP ERP 1.0 SPS02

SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

Component for Customer Incidents MOB-UIA-SD-CI (Customer Invoices)

More Information App History: Customer Invoices App Implementation: Customer Invoices App Extensibility: Customer Invoices

1.20.1 App History: Customer Invoices The Customer Invoices app has been enhanced as follows:

SAP Fiori for SAP ERP 1.0 SPS03 (Delivery Date 07/2014) New/Enhanced Key Features

No change

SAP Note for Technical Changes

1942936

SAP Fiori for SAP ERP 1.0 SPS02 (Delivery Date 05/2014) New/Enhanced Key Features

Enhanced: The issue with the OData service regeneration is fixed. The search returns results from the back-end. Cleared invoices no longer display. The number of invoices correctly display on the Launchpad tile.

SAP Note for Technical Changes

1942936

SAP Fiori for SAP ERP 1.0 SPS01 (Delivery Date 02/2014) New/Enhanced Key Features

Enhanced: Freight conditions are considered in the total freight amount. The sales employee name displays in the contact data section.

New/Changed BAdIs for Extensibility

New: OData extensibility You can add back-end extensibility to OData services Extension points You can add front-end extensibility.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 77 of 138

The following BAdIs are available for extensibility purposes in Customizing for Sales and Distribution under Invoice Tracking : BAdI: Extending Customer Invoices You can use this BAdI to populate custom fields or extend the business functionality of the app. For more information, see App Extensibility: Customer Invoices. SAP Note for Technical Changes

1942936

SAP Fiori for SAP ERP 1.0 SPS 00 (Delivery Date 11/2013) Initial delivery.

1.20.2 App Implementation: Customer Invoices System Landscape Requirements Before you start to implement the app, ensure that your system landscape has been set up to enable SAP Fiori. This also implies that the front-end and back-end components for your app are already available in this system landscape: SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment Based on SAP enhancement package 7 of SAP ERP 6.0 also possible: Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

Configuration of Front-End Server

Configuration of SAP Fiori Infrastructure

Back-End Product Versions Supporting the App (Minimum Product Version Stack)

Product Version Containing Back-End and

SAP ERP 6.0 SP15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher SAP Fiori principal apps for SAP ERP 1.0 SPS03

Front-End Components of the App

For more information on the installation of the back-end and front-end components of the app, see Installation of Back-End Components and Installation of Front-End Components. For the app, the following software components must be available in your system landscape. These components are contained in the product SAP Fiori principal apps for SAP ERP : Back-End/Front-End Server

Back-End/Front-End Component

Technical Name of Software Component Support Package Level

Back-end server

Back-end component

SRA021 1.0

04

Front-end server

Front-end component

UIX01EAP 100

03

Required SAP Notes For Customer Invoices, the following SAP Note must be available: Back-End/Front-End Server

SAP Note Number

Description

Back-End and Front-End Server

1942936

Release Note for the ERP SD FIORI application Customer Invoices

Implementation Tasks The following sections list tasks that have to be performed to implement the Customer Invoices app. The tables contain the app-specific data required for these tasks:

Front-End Server: Activate OData Services Component

Technical Name

OData Service (Version Number)

SRA021_SRV

Front-End Server: Activate UI5 Application Component

Technical Name

UI5 Application

SD_INV_MON

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 78 of 138

Front-End Server: Enable App for Access in SAP Fiori Launchpad There are several steps to be performed to enable the app for access in the SAP Fiori launchpad. You require the listed data to perform these steps. Component

Technical Name

Semantic Object

SalesOrder

Business Role

SAP_SD_BCR_FIELDSALESREP_X1

Business Catalog

SAP_SD_BC_FIELDSALESREP_X1

Business Catalog Group

SAP_SD_BCG_FIELDSALESREP_X1

Technical Role

SAP_SD_TCR_T_X1

Technical Catalog

SAP_SD_TC_T_X1

LPD_CUST Role

UIX01SD

LPD_CUST Instance

TRANSACTIONAL

Front-End and Back-End Server: Assign Role with OData Service Authorization to Users To restrict access to OData services to specific users, you have to assign roles (including OData service authorization for the app) to your users. You have to make the assignment on the back-end and on the front-end server: On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can adjust this role according to your needs. On the front-end server, you can assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs. OData Service (Version Number)

Back-End Server: Delivered Authorization Role (PFCG Role)

Front-End Server: Authorization Role

SRA021_SRV

SRA021:SAP_SD_INV_MON_APP

SAP_SD_BCR_FIELDSALESREP_X1

Technical Data The following tables list technical objects specific to Customer Invoices:

Back-End Components OData Service

Authorization Role (PFCG Role)

SRA021_SRV

SAP_SD_INV_MON_APP

For more information about authorization roles and assigned OData services, see Front-End Server: Assign Role with OData Service Authorization t and Back-End Server: Assign Role with OData Service Authorization to.

Front-End Server: UI5 Application Component

Technical Name

UI5 application

SD_INV_MON

For more information about how to activate the UI5 application (ICF service), see Front-End Server: Activate ICF Services of UI5 Application.

Front-End Server: SAP Fiori Launchpad Components Component

Technical Name

Business Role

SAP_SD_BCR_FIELDSALESREP_X1

Business Catalog

SAP_SD_BC_FIELDSALESREP_X1

Business Catalog Group

SAP_SD_BCG_FIELDSALESREP_X1

Technical Role

SAP_SD_TCR_T_X1

Technical Catalog

SAP_SD_TC_T_X1

LPD_CUST Role

UIX01SD

LPD_CUST Instance

TRANSACTIONAL

Configuration Tasks To enable Customer Invoices , perform these configuration tasks: Ensure that an employee master record is created and check the following: You have implemented SAP ERP HCM and maintained your employees in the HCM personnel records. The employee personnel record has the infotype Communication, with a subtype of System User Name (SY-UNAME) (Infotype 0105, Subtype 0001)

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 79 of 138

If you have not implemented SAP ERP HCM, implement the Sales and Distribution configuration around Use Sales Employees with HR (Tcode: PULT). This IMG setting copies the appropriate HCM tables from the 000 Client and allows the setup of the Employee Record with the Infotype Communication and a Subtype of System User Name (SY-UNAME). (Infotype 0105, Subtype 0001).

Note It associates the USERID of the employee with the personnel number assigned as a partner function sales employee in the customer master. Configure user information by calling the transaction SIMGH to open the Invoice Tracking node. Implement the BAdI: Customer Association to Employee. You can use this BAdI to implement a method for associating employees to customers.

More Information For general information about the user management concept in a SAP Fiori environment, see Users in ABAP Front-End System and Users in ABAP Back-End System.

1.20.3 App Extensibility: Customer Invoices You can extend Customer Invoices according to your business needs for different aspects. For this purpose, the following extensibility options are available: You can insert custom content to overwrite what is provided as a default inside the extension points. Extension points are inserted in the views of delivered standard applications.

Front-End and Back-End Extensibility Entities To add a customer field to the app, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

View

Extension Point

Design Time: Gateway Entity

Design Time: Extension Include (in DDIC Structure)

Runtime: Superclass/ Method to Be Redefined

SRA021_SRV/Contact

SRA021_S_CONTACT_INCL

Superclass: CL_SRA021_DPC_EXT Method: CONTACTS_GET_ENTITYSET

SRA021_SRV/Customer

SRA021_S_CUSTOMER_INCL

Superclass: CL_SRA021_DPC_EXT Method: CUSTOMERS_GET_ENTITYSET

ListItemTemplate.fragment extInvoiceListAttributes

SRA021_SRV/Invoice

SRA021_S_INVOICE_INCL

Superclass: CL_SRA021_DPC_EXT

.xml

Method: INVOICES_GET_ENTITYSET SRA021_SRV/Item

SRA021_S_ITEM_INCL

Superclass: CL_SRA021_DPC_EXT Method: ITEMS_GET_ENTITYSET

S3.view.app.xml

extInvoiceDetails

SRA021_SRV/SOItem

SRA021_S_SOITEM_INCL

extIconTab

extInvoiceGeneralInfo

Superclass: CL_SRA021_DPC_EXT Method: SOITEMS_GET_ENTITYSET

SRA021_SRV/DetailInvoice

SRA021_S_DETAIL_INVOICE_I Superclass: CL_SRA021_DPC_EXT NCL Method: DETAILINVOICES_GET_ENTITY

Additional Extensibility Entities Business Add-Ins (BAdIs) The following BAdIs are available for extensibility purposes in Customizing for Sales and Distribution . Use transaction SIMGH to open the

“Invoice Tracking”

node: BAdI: Extending Customer Invoices You can use this BAdI to populate custom fields such as for invoice details.

Extension Includes In addition to the extension includes described above, the following extension includes are available:

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 80 of 138

DDIC

Extension Include

Use

SRA021_S_CONTACT_DATA

SRA021_S_CONTACT_INCL

Allows you to add fields for contacts

SRA021_S_CUSTOMER_DATA

SRA021_S_CUSTOMER_INCL

Allows you to add fields for customers

SRA021_S_DETAIL_INVOICE

SRA021_S_DETAIL_INVOICE_INCL

Allows you to add fields for invoice details

SRA021_S_INVOICE

SRA021_S_INVOICE_INCL

Allows you to add fields in the master details invoice section

SRA021_S_ITEM

SRA021_S_ITEM_INCL

Allows you to add fields in the item details invoice section

SRA021_S_SOITEM

SRA021_S_SOITEM_INCL

allows you to add extra fields to the list of sales order numbers

More Information For a general description of the extensibility options and procedures of Fiori apps, see Extensibility.

1.21 Look Up Retail Products With the transactional app Look Up Retail Products you get real-time access to information about products in your store and their availability. The app allows you to see detailed information about a product, as well as stock levels for the product in your store and in stores nearby.

Key Features Access real-time product, promotion, and stock information See style, color, or size variants of a product See product availability in nearby stores Find any store by entering its description, ID, or address in the search field

System Landscape Requirements The app consists of front-end components (such as the user interfaces) and back-end components (such as the OData service). The back-end and the front-end components are delivered in separate products and have to be installed in a system landscape that is enabled for SAP Fiori. Product Version Containing Back-End and Front-End Components of the App Back-End Product Versions (with Minimum Support Package Stack) Supporting the App

SAP Fiori System Landscape Options

SAP Fiori transactional apps for SAP ERP 1.0 SPS01

SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher Setup of SAP Fiori System Landscape with ABAP Environment

The following software products must be available in your system landscape: Back-end system (business data) Required product release: SAP Enhancement Package 4 for SAP ERP 6.0 The following software components are required: GBX02RT4 SP 0 EA-RETAIL 604 installed with the latest SP UI add-on (front-end components) Required product release: UI for EHP4 for SAP ERP 6.0 SP09 Required software components: UIX02RT4 SP 0

Note This app is also available in a version for higher back-end releases. For more information, see SAP Help Portal at SAP Fiori for SAP ERP SAP Fiori for SAP ERP 1.0 .

http://help.sap.com/fiori_products

Component for Customer Messages LO-SRS-MOB

More Information App History: Look Up Retail Products App Implementation: Look Up Retail Products App Extensibility: Look Up Retail Products

1.21.1 App History: Look Up Retail Products PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 81 of 138

1.21.1 App History: Look Up Retail Products The Look Up Retail Products app has been enhanced as follows:

SAP Fiori for SAP ERP 1.0 SPS03 (Delivery Date 07/2014) Initial delivery.

1.21.2 App Implementation: Look Up Retail Products System Landscape Requirements Before you start to implement the app, ensure that your system landscape has been set up to enable SAP Fiori. This also implies that the front-end and back-end components for your app are already available in this system landscape: SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment

Configuration of Front-End Server

Configuration of SAP Fiori Infrastructure

Back-End Product Versions (with Minimum Support Package Stack) Supporting the App

Product Version Containing Back-End and Front-End Components of the App

SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP Fiori transactional apps for SAP ERP 1.0 SPS01

For more information on the installation of the back-end and front-end components of the app, see Installation Information. For the app, the following software components must be available in your system landscape. These components are contained in the product SAP Fiori transactional apps for SAP ERP : Back-End/Front-End Server

Back-End/Front-End Component

Technical Name of Software Component Support Package Level

Back-end server

Back-end component

GBX02RT4 604

00

Front-end server

Front-end component

UIX02RT4 100

00

Required SAP Notes For Look Up Retail Products , the following SAP Notes must be available: Back-End/Front-End Server

SAPNote Number

Description

Front-End Server

2030063

Release Information Note for the FIORI application Look Up Retail Products in ECC 604, ECC 605 and ECC 616

Implementation Tasks The following sections list tasks that have to be performed to implement the Look Up Retail Products app. The tables contain the app-specific data required for these tasks:

Front-End Server: Activate OData Services Component

Technical Name

OData Service (Version Number)

RETAILSTORE_PRODUCT_LKP_SRV (1)

For more information about activating OData services, see Front-End Server: Activate OData Services.

Front-End Server: Activate UI5 Application Component

Technical Name

UI5 Application

RT_PRODUCT_LKP

For more information about how to activate the UI5 application (ICF service), see Front-End Server: Activate ICF Services of UI5 Application.

Front-End Server: Enable App for Access in SAP Fiori Launchpad There are several steps to be performed to enable the app for access in the SAP Fiori launchpad. You require the listed data to perform these steps. For more information about the steps to be performed, see Setup of Catalogs, Groups, and Roles in the SAP Fiori Launchpad.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 82 of 138

Component

Technical Name

Semantic Object

Article

Business Role

SAP_ISR_STORE_BCR_STORE_ASSOC

Business Catalog

SAP_ISR_BC_StoreAssociate

Business Catalog Group

SAP_ISR_BCG_StoreAssociate

Technical Role

SAP_ISR_STORE_TCR_T

Technical Catalog

SAP_ISR_STORE_TC_T

LPD_CUST Role

UIRT401

LPD_CUST Instance

TRANSACTIONAL

For more information about the steps to be performed, see Setup of Catalogs, Groups, and Roles in the SAP Fiori Launchpad.

Front-End and Back-End Server: Assign Role with OData Service Authorization to Users To grant access to OData services to specific users, you have to assign roles (including OData service authorization for the app) to your users. You have to make the assignment on the back-end and on the front-end server: On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can adjust this role according to your needs. On the front-end server, you can assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs. OData Service (Version Number)

Back-End Server: Delivered Authorization Role (PFCG Role)

Front-End Server: Authorization Role

RETAILSTORE_PRODUCT_LKP_SRV (1)

SAP_STORE_PRDCT_LKP_APP

Use an existing role or create a new one

For more information about authorization roles and assigned OData services, see Front-End Server: Assign Role with OData Service Authorization t and Back-End Server: Assign Role with OData Service Authorization to.

Prerequisites for Implementation Before implementing the Look Up Retail Products app, you must ensure the following: Software component EA-RETAIL 604 is installed with the latest SP on the back-end server Software component GBX02RT4 SP 0 is installed on the back-end server SAP Enterprise Search is deployed and TREX-based models are imported Software component UIX02RT4 SP 0 is installed on the front-end server Business function Retail, In-Store Merchandise and Inventory Management is configured, and basic master data is prepared

Configuration Tasks To enable Look Up Retail Products , you must perform the following configuration tasks in the back-end system, or as specified:

Required Configuration Tasks Set the VKPF Pricing Condition In the Look Up Retail Products app, the retail store ruling price condition VKPF is required to read the most current price for products from the back-end system. You must customize this condition as follows: 1. Add the VKPF condition type to the list of condition types. Create the VKPF condition type if it is not found. Sales and Distribution Basic Functions Pricing Pricing Control 2. Assign the VKPF condition type to the VKP001 pricing procedure.

Define Condition Types

Sales and Distribution Basic Functions Pricing 3. Assign the VKPF condition type to the ruling price.

Define and Assign Pricing Procedures

Pricing Control

Logistics General SAP Retail Store Sales Prices Basic Settings for Sales Prices Enable SAP TREX-based Enterprise Search Configure settings to enable TREX-based SAP Enterprise Search. Ensure that the MATERIAL model is available. For more information, see Service Marketplace

Installation & Upgrade Guides

SAP NetWeaver

SAP NetWeaver Enterprise Search 7.3

SAP

.

Optional Configuration Tasks The following configuration tasks are optional and can be implemented according to your business needs. Configure Settings to Download Product Images If you are using SAP Document Service (DMS) provided by SAP as the product image provider, configure the required settings to enable product image downloads as follows: 1. Create a document for a desired image. In DMS, execute transaction CV01N, and make the following settings: Document Type = DRW Document Part = 000 Document Version = Press Enter and make the Document Status = WR (Work Request). 2. Upload the desired image file.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 83 of 138

Defined storage category = DMS_C1_ST 3. Link the document to a related product number in SAP ERP. For more information, see .http://help.sap.com/businesssuite SAP Product Lifecycle Management SAP PLM as part of SAP ERP Central Component Application Help Document Management . If you are not using SAP Document Service (DMS) as the product image provider, provide a BAdI implementation to specify your product image provider. Configure Settings to Retrieve Supplemental Product Data You can use the following Business Add-ins (BAdIs) to retrieve supplemental product data such as warranty descriptions or more detailed product information. You find these in Customizing for SAP Retail Store under In-Store Merchandise and Inventory Management - UI5 Apps Look Up Retail Products .

Note When you define these BAdIs once, they can also be shared by the Adjust Stock app. BAdI: DMS Configuration for Supplemental Data in Product Lookup You use this BAdI to retrieve configuration information for the Supplemental Data Query for Product Lookup BAdI. BAdI: Supplemental Data Query for Product Lookup You use this BAdI to retrieve supplemental data for the product. For more information, see App Extensibility: Look Up Retail Products Additional Optional Configuration Add information for nearby stores using transaction WSD_CBP. Create variants of generic articles with transaction MM41. This transaction relates products to other similar products. For more information, see SAP Library at help.sap.com then go to ERP 6.0

SAP for Industries

SAP for Retail

. Choose Application Help then SAP Library . Choose

SAP Retail as Part of SAP ERP

Master Data

Article Master Data

Enhancement Package 5 for SAP

Articles: Article Categories

Additional Configuration-Related Information You can use transaction SLG1 in the back-end SAP ERP Retail system to check the application log. Enter the settings as follows: Object

W_SRS_MOB

Sub-object

MOBILE_PL

To integrate with SAP Jam, each user of the Look Up Retail Products app must have their own account in SAP Jam. They must also register their SAP Jam account email address on the SAP Gateway system and ensure that they use the same one for their SAP Jam account. For more information, see help.sap.com/sapjam. When users access the Look Up Retail Products app, the system first checks whether they are assigned to a store. If they are not assigned to a store, a list of stores is displayed. This list comes from authorization object W_SRS_APPL. Users can change their store assignment anytime through the Settings icon. The assigned store is persisted in table FPB_PERSPARM, which the app reuses from the SAP In-Store Merchandise and Inventory Management application (Retail In-Store MIM). The following shipment/goods receipt types are supported for incoming shipments: Purchase order Material document Handling unit You can set the validity period of each document through the following Customizing activity in Logistics - General : SAP Retail Store Goods Movement Basic Settings for Goods Receipt 1. In the Control of PDC Procedures section, set the value of the Retail Store MDE Scenario to 2 and save this setting. This ensures that required fields related to customization for Retail Store are displayed. 2. In the Other Fields for PDC Control section, set the value of the Days Following After Date field to reflect the required validity period in days. 3. Assign the schema to the current store.

More Information For general information about the user management concept in a SAP Fiori environment, see Users in ABAP Front-End System and Users in ABAP Back-End System.

1.21.3 App Extensibility: Look Up Retail Products You can extend Look Up Retail Products according to your business needs and control how much product information store associates can see. For this purpose, the following extensibility options are available: You can show or hide the following information in the product detail view: Product number, EAN/UPC code, product weight, and quantity available Promotion information Quantities expected in incoming shipments Quantities available in nearby stores Style, color, and size variants You can add a new section to the Information tab of the product detail view and add new fields to it. You can add a new section to the Promotions tab of the product detail view and add new fields to it. You can add a new tab to the product detail view, and extend it with new sections and new fields.

Enhance Product Detail View To enhance the product detail view,, the extensibility entities listed below are available on the different software layers. You have to extend each of these entities

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 84 of 138

according to your specific business needs:

Display of UI Controls To show or hide specific product details on the app, the following UI controls can be hidden on the app UI. You implement the control by setting the Visible attribute to True or False in the Components.js file, in the section where customization points are set. For more information, see sap.ui.viewModifications in the implementation. View

Control ID

Use

retail.store.productlookup.view.ProductDet ARTICLE_DETAILS_ITF ails retail.store.productlookup.view.ProductDet PROMOTIONS_ITF ails retail.store.productlookup.view.ProductDet STOCK_ITF ails

Allows you to hide the Product Detail tab and prevent navigation to that information on the app. Allows you to hide the Promotion tab and prevent navigation to that information on the app. Allows you to hide the Stock tab and prevent navigation to that information on the app. Allows you to hide the Similar Items tab and prevent navigation to information about product variants on the app.

retail.store.productlookup.view.ProductDet AA_ITF ails

For more information about hiding UI controls, see Concealable UI Controls.

UI Controller Hooks To plug in and execute custom code, the following hooks are available in the controller code: Controller

Hook

Use

ProductDetails.Controller.js

extHookOnProductDetailsDataReceived

Allows you to execute code after successfully receiving product data to enrich or validate product details

For more information about UI controller hooks, see UI Controller Hooks.

Add New Fields to Information Tab in Product Detail View To add new fields to the Information tab of the product detail view, the following extensibility entities are available on the different layers. You have to extend each of these according to your specific business needs: UI View

Back End/ABAP Extension Point

Design Time: Gateway Entity

ProductDetails.view.app.x Product_Information_Form_ Article entity in the ml

Ext

RETAILSTORE_PRODUCT_LKP

To add new fields in the Information tab page

project

Design Time: Extension Include (in DDIC Structure)

Runtime: Superclass/Method to Be Redefined

RETAIL_ST_ARTICLE_INCL

CL_RETAILSTORE_PRODUCT_DP C methods: ARTICLES_GET_ENTITY ARTICLES_GET_ENTITYS ET ALTERNATIVEARTIC_GET _ENTITY ALTERNATIVEARTIC_GET _ENTITYSET You must copy the code from the original class and use the enhanced structure where needed. The enhanced structure is available in the redefined method signature as the ER_ENTITY type.

Business Add-Ins (BAdIs) The following Business Add-In is available for extensibility purposes: BAdI: Enhancement of Information Displayed in Product Details RETAIL_ST_PL_PRODUCT_ENH You can use this BAdI to provide additional product information. This BAdI uses the GET_PRODUCT_SUPP_DATA method to retrieve data from the back-end system when a product list is first displayed or refreshed, or when a product is searched. It provides data to the additional product information fields.

Add New Section and New Fields to Promotions Tab in Product Detail View To add a new section and new fields to the Promotions tab of the product detail view, the following extensibility entities are available on the different layers. You have to extend each of these according to your specific business needs: UI View

Back End/ABAP Extension Point

Design Time: Gateway Entity

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Design Time: Extension

Runtime: Superclass/Method to

Page 85 of 138

ProductDetails.view.app.x Product_Promo_Sections_Ex Promotion entity in the ml

Include (in DDIC Structure)

Be Redefined

RETAIL_ST_PROMOTION_INCL

CL_RETAILSTORE_PRODUCT_DP

t

RETAILSTORE_PRODUCT_LKP

C methods:

To add new fields in the Information tab page

project

PROMOTIONS_GET_ENTITYSET You must copy the code from the original class and use the enhanced structure where needed. The enhanced structure is available in the redefined method signature as the ER_ENTITY type.

Business Add-Ins (BAdIs) The following Business Add-In is available for extensibility purposes: BAdI: Enhancement of Information Displayed in the Promotions Tab RETAIL_ST_PL_PROMOTION_ENH You can use this BAdI to provide promotion information for a product. This BAdI uses the GET_PROMOTION_SUPP_DATA method to provide data to the product information when a product is selected in the product list and the promotion information is loaded.

Add New Tab Pages To add a new tab page to the product detail view, and add new sections and fields to it, the following extension points are available:

Extension Points In addition to the extension points described above, the following extension points are available: View

Extension Point

Use

ProductDetails.view.app.xml

Extension_Product_Detail_Tab

You can add fields from the standard delivered back-end

To add a new tab to the product detail view

ABAP service, or from your extended back-end ABAP service.

For more information about extension points, see Extension Points.

Business Add-Ins (BAdIs) The following Business Add-Ins are available for extensibility purposes: BAdI: Enhancement of Information Displayed in Product Details RETAIL_ST_PL_PRODUCT_ENH You can use this BAdI to provide additional product information. This BAdI uses the GET_PRODUCT_SUPP_DATA method to retrieve data from the back-end system when a product list is first displayed or refreshed, or when a product is searched. It provides data to the additional product information fields. BAdI: Enhancement of Information Displayed in the Promotions Tab RETAIL_ST_PL_PROMOTION_ENH You can use this BAdI to provide promotion information for a product. This BAdI uses the GET_PROMOTION_SUPP_DATA method to provide data to the product information when a product is selected in the product list and the promotion information is loaded.

More Information For a general description of the extensibility options and procedures of Fiori apps, see Extensibility.

1.22 My Benefits With the transactional app My Benefits you can provide a quick and easy overview of the benefit plans in which an employee is enrolled, ensuring that the employee has all the details of the benefits offered by their company at their fingertips.

Key Features Display the benefit plans in which you are enrolled by plan categories Display eligible benefit plans for which you have not yet enrolled Display plan details of a selected benefit plan, for example, your coverage, pre-tax cost, and so on View the benefit overview or detailed information for any given date Access links to benefit plan documents to find information on the definition of benefit plans Open the Benefits Summary statement as a PDF that can be downloaded locally

System Landscape Requirements The app consists of front-end components (such as the user interfaces) and back-end components (such as the OData service). The back-end and the front-end components are delivered with one product and have to be installed in a system landscape that is enabled for SAP Fiori.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 86 of 138

Product Version Containing Back-End and

SAP Fiori principal apps for SAP ERP 1.0 SPS03

Front-End Components of the App Back-End Product Versions Supporting the App (Minimum Product Version Stack)

SAP Fiori System Landscape Options

SAP ERP 6.0 SP15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher Setup of SAP Fiori System Landscape with ABAP Environment Based on SAP enhancement package 7 of SAP ERP 6.0 also possible: Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

Component for Customer Messages MOB-UIA-PA-MBE

More Information App History: My Benefits App Implementation: My Benefits App Extensibility: My Benefits

1.22.1 App History: My Benefits The My Benefits app has been enhanced as follows:

SAP Fiori principal apps for SAP ERP 1.0 SPS 03 (Delivery Date 07/2014) New/Enhanced Extensibility Options

Controller hooks are introduced.

SAP Note for Technical Changes

1931616

SAP Fiori principal apps for SAP ERP 1.0 SPS 02 (Delivery Date 05/2014) New/Enhanced Key Features

No changes.

New/Enhanced Extensibility Options

No changes.

SAP Note for Technical Changes

1931616

SAP Fiori principal apps for SAP ERP 1.0 SPS 01 (Delivery Date 02/2014) New/Enhanced Key Features

No changes.

New/Enhanced Extensibility Options

New extensibility options: Extending the Details view You can add additional fields in the header section on Details page You can add additional icon tabs on the Details page OData service can now be extended.

SAP Note for Technical Changes

1931616

SAP Fiori principal apps for SAP ERP 1.0 SPS 00 (Delivery Date 11/2013) Initial delivery.

1.22.2 App Implementation: My Benefits System Landscape Requirements Before you start to implement the app, ensure that your system landscape has been set up to enable SAP Fiori. This also implies that the front-end and back-end components for your app are already available in this system landscape:

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 87 of 138

SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment Based on SAP enhancement package 7 of SAP ERP 6.0 also possible: Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

Configuration of Front-End Server

Configuration of SAP Fiori Infrastructure

Back-End Product Versions Supporting the App (Minimum Product Version Stack)

SAP ERP 6.0 SP15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher

Product Version Containing Back-End and Front-End Components of the App

SAP Fiori principal apps for SAP ERP 1.0 SPS03

For more information on the installation of the back-end and front-end components of the app, see Installation of Back-End Components and Installation of Front-End Components. For the app, the following software components must be available in your system landscape. These components are contained in the product SAP Fiori principal apps for SAP ERP : Back-End/Front-End Server

Back-End/Front-End Component

Technical Name of Software Component Support Package Level

Back-end server

Back-end component

SRA007 1.0

04

Front-end server

Front-end component

UIX01HCM 100

03

Required SAP Notes For My Benefits , the following SAP Notes must be available: SAP Note Number

Description

1931616

Release Information

Implementation Tasks The following sections list tasks that have to be performed to implement the My Benefits app. The tables contain the app-specific data required for these tasks:

Front-End Server: Activate OData Services Component

Technical Name

OData Service (Version Number)

SRA007_BENEFITS_SRV

For more information about activating OData services, see Front-End Server: Activate OData Services.

Front-End Server: Activate UI5 Application Component

Technical Name

UI5 Application

HCM_BEN_MON

For more information about how to activate the UI5 application (ICF service), see Front-End Server: Activate ICF Services of UI5 Application.

Front-End Server: Enable App for Access in SAP Fiori Launchpad There are several steps to be performed to enable the app for access in the SAP Fiori launchpad. You require the listed data to perform these steps. For more information about the steps to be performed, see Setup of Catalogs, Groups, and Roles in the SAP Fiori Launchpad. Component

Technical Name

Semantic Object

BenefitPlan

Business Role

SAP_HCM_BCR_EMPLOYEE_X1

Business Catalog

SAP_HCM_BC_EMPLOYEE_X1

Business Catalog Group

SAP_HCM_BCG_EMPLOYEE_X1

Technical Role

SAP_HCM_TCR_T_X1

Technical Catalog

SAP_HCM_TC_T_X1

LPD_CUST Role

UIX01HCM

LPD_CUST Instance

TRANSACTIONAL

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 88 of 138

Front-End and Back-End Server: Assign Role with OData Service Authorization to Users To restrict access to OData services to specific users, you have to assign roles (including OData service authorization for the app) to your users. You have to make the assignment on the back-end and on the front-end server: On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can adjust this role according to your needs. On the front-end server, you can assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs. OData Service (Version Number)

Back-End Server: Delivered Authorization Role (PFCG Role)

Front-End Server: Authorization Role

SRA007_BENEFITS_SRV

SAP_HCM_BEN_MON_APP

Use an existing role or create a new one

For more information about authorization roles and assigned OData services, see Front-End Server: Assign Role with OData Service Authorization t and Back-End Server: Assign Role with OData Service Authorization to.

Prerequisites for Implementation Before implementing the app, you must ensure the following: Activate HR-BEN business function Software component dependencies are already maintained in PPMS, so the SAINT tool takes care of the dependency validation. Since the SAP Fiori My Benefits application relies on the configuration data available for Standard HR Benefits module, it is a mandatory prerequisite for the application to have HR Benefits (HR-BEN) available and configured.

Configuration Tasks To enable My Benefits, you must perform the following configuration tasks: Enable the SICF Services for the Gateway Service name: SRA007_BENEFITS_SRV Enable the SICF Services for UI5 Service name: HCM_BEN_MON Deploy the Business Add-In SRA007_BADI_BENEFITS For instructions on how to activate BAdI implementations, see Steps to Activate BAdI Implementations.

More Information For general information about the user management concept in a SAP Fiori environment, see Users in ABAP Front-End System and Users in ABAP Back-End System.

1.22.3 App Extensibility: My Benefits You can extend My Benefits according to your business needs for different aspects. For this purpose, the following extensibility options are available: Extending the Details view You can hide fields in the header section on Details screen You can add additional fields in the header section on Details screen You can add additional icon tabs on the Details screen

Note In addition, any of the complete views can be replaced by your own view.

Extending the Details view To hide or add a field, or to add additional icon tabs to the Details screen, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

View

Extension Point

Design Time: Gateway Entity

Design Time: Extension Include (in DDIC Structure)

Runtime: Superclass/ Method to Be Redefined

S3.view.xml

extS3Header

SRA007_BENEFITS_SRV

SRA007_BENEFIT_INCL

Superclass: CL_SRA007_BENEFITS_DPC_EX T Method: BENEFITS_GET_ENTITYSET

S3.view.xml

extS3IconTabFilter

SRA007_BENEFITS_SRV

SRA007_BENEFICIARY_INCL

Superclass: CL_SRA007_BENEFITS_DPC_EX T Method:

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 89 of 138

BENEFICIARIES_GET_ENTITYS ET SRA007_DEPENDANT_INCL

Superclass: CL_SRA007_BENEFITS_DPC_EX T Method: DEPDENDENTS_GET_ENTITYSET

SRA007_INVESTMENT_INCL

Superclass: CL_SRA007_BENEFITS_DPC_EX T Method: INVESTMENTS_GET_ENTITYSET

SRA007_FILEDATA_INCL

Superclass: CL_SRA007_BENEFITS_DPC_EX T Method: /IWBEP/IF_MGW_APPL_SRV_RU NTIME~EXECUTE_ACTION

S4.view.xml

extS4Header

SRA007_BENEFITS_SRV

SRA007_BENEFIT_INCL

Superclass: CL_SRA007_BENEFITS_DPC_EX T Method: BENEFITS_GET_ENTITYSET

S4.view.xml

extS4IconTabFilter

SRA007_BENEFITS_SRV

SRA007_BENEFICIARY_INCL

Superclass: CL_SRA007_BENEFITS_DPC_EX T Method: BENEFICIARIES_GET_ENTITYS ET

SRA007_DEPENDANT_INCL

Superclass: CL_SRA007_BENEFITS_DPC_EX T Method: DEPDENDENTS_GET_ENTITYSET

SRA007_INVESTMENT_INCL

Superclass: CL_SRA007_BENEFITS_DPC_EX T Method: DEPDENDENTS_GET_ENTITYSET

SRA007_INVESTMENT_INCL

Superclass: CL_SRA007_BENEFITS_DPC_EX T Method: INVESTMENTS_GET_ENTITYSET

SRA007_FILEDATA_INCL

Superclass: CL_SRA007_BENEFITS_DPC_EX T Method: /IWBEP/IF_MGW_APPL_SRV_RU NTIME~EXECUTE_ACTION

S5.view.xml

extS5Header

SRA007_BENEFITS_SRV

SRA007_BENEFIT_INCL

Superclass: CL_SRA007_BENEFITS_DPC_EX T Method: BENEFITS_GET_ENTITYSET

S5.view.xml

extS5IconTabFilter

SRA007_BENEFITS_SRV

SRA007_BENEFICIARY_INCL

Superclass: CL_SRA007_BENEFITS_DPC_EX T Method: BENEFICIARIES_GET_ENTITYS ET

SRA007_DEPENDANT_INCL

Superclass: CL_SRA007_BENEFITS_DPC_EX T Method: DEPDENDENTS_GET_ENTITYSET

SRA007_INVESTMENT_INCL

Superclass: CL_SRA007_BENEFITS_DPC_EX T Method: INVESTMENTS_GET_ENTITYSET

SRA007_FILEDATA_INCL

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Superclass: CL_SRA007_BENEFITS_DPC_EX

Page 90 of 138

T Method: /IWBEP/IF_MGW_APPL_SRV_RU NTIME~EXECUTE_ACTION S6.view.xml

extS6Header

SRA007_BENEFITS_SRV

SRA007_BENEFIT_INCL

Superclass: CL_SRA007_BENEFITS_DPC_EX T Method: BENEFITS_GET_ENTITYSET

S6.view.xml

extS6IconTabFilter

SRA007_BENEFITS_SRV

SRA007_BENEFICIARY_INCL

Superclass: CL_SRA007_BENEFITS_DPC_EX T Method: BENEFICIARIES_GET_ENTITYS ET

SRA007_DEPENDANT_INCL

Superclass: CL_SRA007_BENEFITS_DPC_EX T Method: BENEFICIARIES_GET_ENTITYS ET

SRA007_INVESTMENT_INCL

Superclass: CL_SRA007_BENEFITS_DPC_EX T Method: INVESTMENTS_GET_ENTITYSET

SRA007_FILEDATA_INCL

Superclass: CL_SRA007_BENEFITS_DPC_EX T Method: /IWBEP/IF_MGW_APPL_SRV_RU NTIME~EXECUTE_ACTION

S7.view.xml

extS7Header

SRA007_BENEFITS_SRV

SRA007_BENEFIT_INCL

Superclass: CL_SRA007_BENEFITS_DPC_EX T Method: BENEFITS_GET_ENTITYSET

S7.view.xml

extS7IconTabFilter

SRA007_BENEFITS_SRV

SRA007_BENEFICIARY_INCL

Superclass: CL_SRA007_BENEFITS_DPC_EX T Method: BENEFICIARIES_GET_ENTITYS ET

SRA007_DEPENDANT_INCL

Superclass: CL_SRA007_BENEFITS_DPC_EX T Method: DEPDENDENTS_GET_ENTITYSET

SRA007_INVESTMENT_INCL

Superclass: CL_SRA007_BENEFITS_DPC_EX T Method: INVESTMENTS_GET_ENTITYSET

SRA007_FILEDATA_INCL

Superclass: CL_SRA007_BENEFITS_DPC_EX T Method: /IWBEP/IF_MGW_APPL_SRV_RU NTIME~EXECUTE_ACTION

S8.view.xml

extS8Header

SRA007_BENEFITS_SRV

SRA007_BENEFIT_INCL

Superclass: CL_SRA007_BENEFITS_DPC_EX T Method: BENEFITS_GET_ENTITYSET

S8.view.xml

extS8IconTabFilter

SRA007_BENEFITS_SRV

SRA007_BENEFICIARY_INCL

Superclass: CL_SRA007_BENEFITS_DPC_EX T Method: BENEFICIARIES_GET_ENTITYS ET

SRA007_DEPENDANT_INCL

Superclass: CL_SRA007_BENEFITS_DPC_EX T Method:

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 91 of 138

DEPDENDENTS_GET_ENTITYSET SRA007_INVESTMENT_INCL

Superclass: CL_SRA007_BENEFITS_DPC_EX T Method: INVESTMENTS_GET_ENTITYSET

SRA007_FILEDATA_INCL

Superclass: CL_SRA007_BENEFITS_DPC_EX T Method: /IWBEP/IF_MGW_APPL_SRV_RU NTIME~EXECUTE_ACTION

Further Extensibility Entitie Extension Includes In addition to the extension includes described above, the following extension includes are available: DDIC

Extension Include

Use

SRA007_SUMMARY

SRA007_SUMMARY_INCL

Allows you to change the summary information displayed on app tile of the Fiori Launchpad.

For more information about extension includes, see Extension Includes.

UI Controller Hooks To plug in and execute custom code, the following hooks are available in the controller code: Controller

Hook

Use

S3.controller.js

extHookInitAdditionalTabs

Allows you to initialize additional tabs of the tab bar from code

extHookChangeFooterButtons

Allows you to add and change buttons for the detail view footer

extHookInitAdditionalTabs

Allows you to initialize additional tabs of the tab bar from code

extHookChangeFooterButtons

Allows you to add and change buttons for the detail view footer

extHookInitAdditionalTabs

Allows you to initialize additional tabs of the tab bar from code

extHookChangeFooterButtons

Allows you to to add and change buttons for the detail view footer

extHookInitAdditionalTabs

Allows you to initialize additional tabs of the tab bar from code

extHookChangeFooterButtons

Allows you to to add and change buttons for the detail view footer

extHookInitAdditionalTabs

Allows you to initialize additional tabs of the tab bar from code

extHookChangeFooterButtons

Allows you to to add and change buttons for the detail view footer

extHookInitAdditionalTabs

Allows you to initialize additional tabs of the tab bar from code

extHookChangeFooterButtons

Allows you to to add and change buttons for the detail view footer

S4.controller.js

S5.controller.js

S6.controller.js

S7.controller.js

S8.controller.js

For more information about UI controller hooks, see UI Controller Hooks.

More Information For a general description of the extensibility options and procedures of Fiori apps, see Extensibility.

1.23 My Contacts Type: Transactional app

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 92 of 138

Description With My Contacts , you can create, modify or display customer contact information on field interactively on desktop, tablet, and mobile platforms. The app allows you to easily manage and access your contacts.

Key Features Browse, search, sort, filter your list of contacts Edit existing contacts Create new contacts or duplicate existing contacts Access customer contact information Add notes and attachments to contacts

Technical Requirements Product Version: SAP enhancement package 4 for SAP ERP 6.0 SP05 or higher SAP enhancement package 5 for SAP ERP 6.0 SP03 or higher SAP enhancement package 6 for SAP ERP 6.0 SP01 or higher UI add-on SAP Fiori transactional apps for SAP ERP 1.0 (FIORI ERP APPLICATIONS X2 1.0) For more information, see App Implementation: My Contacts.

SAP Component for Customer Messages SD-CUST (Customer)

1.23.1 App Implementation: My Contacts Technical Data The following tables list technical objects specific for My Contacts :

Back-End Components OData Service (Version Number)

Authorization Role (PFCG Role)

SD_MYCONTACTS

SAP_SD_MYCONT_APP

Front-End Components Component

Technical Name

UI5 Application

SD_MYCONTACTS

Business Role

SAP_SD_BCR_FIELDSALESREP

Business Catalog

SAP_SD_BC_FIELDSALESREP

Business Catalog Group

-

For more information about how to implement these technical objects, see Central Implementation Information.

Prerequisites for Configuration Before implementing the app, you must ensure that you have enabled the Logistics S&D Simplification (SD_01) business function.

Configuration To enable the app, you must perform the following configuration tasks in table maintenance for view FIORI_COMMON_CUS (transaction SM30): Common OData Customizing Setting (table FIORI_COMMON_CUS) In this activity, you define the default setting for Sales Partner for the OData service SD_MYCONTACTS, which is used by My Contacts . In the standard system, the default setting for Sales Partner is SE (Sales Employee). The BAdI Get Contact List for My Contacts (see below) uses this parameter to limit the contact person list that is returned by the OData service to only those contacts belonging to customers that are assigned to a field sales representative.

Extensibility To extend the app, you can use the following Business Add-Ins (BAdIs):

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 93 of 138

BAdI: Get Contact List for My Contacts (BADI_CMD_GET_CONTACT_LIST) You use this BAdI to fetch the contact list returned by the OData service to the individual field sales representative. BAdI: Get Contact Details for My Contacts (BADI_CMD_GET_CONTACT_DETAILS) You use this BAdI to get details for contacts returned by the OData service to the individual field sales representative. BAdI: Modify Contact Details for My Contacts (BADI_CMD_SET_CONTACT_DETAILS) You use this BAdI to modify details of contacts returned by the OData service to the individual field sales representative. For more information, see the documentation for these BAdIs in the BAdI Builder (transaction SE18).

Note These BAdIs are not available in Customizing.

1.24 My Leave Requests With the transactional app My Leave Requests you can enable employees to create and submit leave requests quickly and flexibly, using their desktop or mobile device. The app lets users track the status of their requests and view their current leave balance.

Key Features Create leave requests, including partial day leave Select the leave period using an integrated calendar that shows non-working days, holidays, booked leave, and leave pending approval Add a note for the approver Display a summary of your leave entitlement, leave taken so far, and available balance Display your leave requests and check their approval status Withdraw or change leave requests

System Landscape Requirements The app consists of front-end components (such as the user interfaces) and back-end components (such as the OData service). The back-end and the front-end components are delivered with one product and have to be installed in a system landscape that is enabled for SAP Fiori. Product Version Containing Back-End and Front-End Components of the App Back-End Product Versions Supporting the App (Minimum Product Version Stack)

SAP Fiori System Landscape Options

SAP Fiori principal apps for SAP ERP 1.0 SPS03

SAP ERP 6.0 SP15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher Setup of SAP Fiori System Landscape with ABAP Environment Based on SAP enhancement package 7 of SAP ERP 6.0 also possible: Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

Related Apps Approve Leave Requests

Component for Customer Messages MOB-UIA-PT-MLR

More Information App History: My Leave Requests App Implementation: My Leave Requests App Extensibility: My Leave Requests

1.24.1 App History: My Leave Requests The My Leave Requests app has been enhanced as follows:

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 94 of 138

SAP Fiori principal apps for SAP ERP 1.0 SPS 03 (Delivery Date 07/2014) New/Enhanced Extensibility Options

Controller hooks are introduced.

SAP Note for Technical Changes

1931618

SAP Fiori principal apps for SAP ERP 1.0 SPS 02 (Delivery Date 05/2014) New/Enhanced Key Features

No change

New/Enhanced Extensibility Options

No change

SAP Note for Technical Changes

1931618

SAP Fiori principal apps for SAP ERP 1.0 SPS 01 (Delivery Date 02/2014) New/Enhanced Key Features

No change

New/Enhanced Extensibility Options

New extensibility options: You can now add or hide additional fields in the main view. You can now hide or add additional fields in the History view. You can now hide or add additional fields in the Entitlements view. OData service can now be extended.

SAP Note for Technical Changes

1931618

SAP Fiori principal apps for SAP ERP 1.0 SPS 00 (Delivery Date 11/2013) Initial delivery.

1.24.2 App Implementation: My Leave Requests System Landscape Requirements Before you start to implement the app, ensure that your system landscape has been set up to enable SAP Fiori. This also implies that the front-end and back-end components for your app are already available in this system landscape: SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment Based on SAP enhancement package 7 of SAP ERP 6.0 also possible: Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

Configuration of Front-End Server

Configuration of SAP Fiori Infrastructure

Back-End Product Versions Supporting the App (Minimum Product Version Stack)

Product Version Containing Back-End and Front-End Components of the App

SAP ERP 6.0 SP15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher SAP Fiori principal apps for SAP ERP 1.0 SPS03

For more information on the installation of the back-end and front-end components of the app, see Installation of Back-End Components and Installation of Front-End Components. For the app, the following software components must be available in your system landscape. These components are contained in the product SAP Fiori principal apps for SAP ERP : Back-End/Front-End Server

Back-End/Front-End Component

Technical Name of Software Component Support Package Level

Back-end server

Back-end component

GBHCM002 600

12

Front-end server

Front-end component

UIX01HCM 100

03

Required SAP Notes For My Leave Requests , the following SAP Notes must be available: SAP Note Number

Description

1931618

Release Information

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 95 of 138

Implementation Tasks The following sections list tasks that have to be performed to implement the app. The tables contain the app-specific data required for these tasks:

Front-End Server: Activate OData Services Component

Technical Name

OData Service (Version Number)

/GBHCM/LEAVEREQUEST (2)

For more information about activating OData services, see Front-End Server: Activate OData Services.

Front-End Server: Activate UI5 Application Component

Technical Name

UI5 Application

HCM_LR_CRE

For more information about how to activate the UI5 application (ICF service), see Front-End Server: Activate ICF Services of UI5 Application.

Front-End Server: Enable App for Access in SAP Fiori Launchpad There are several steps to be performed to enable the app for access in the SAP Fiori launchpad. You require the listed data to perform these steps. For more information about the steps to be performed, see Setup of Catalogs, Groups, and Roles in the SAP Fiori Launchpad. Component

Technical Name

Semantic Object

LeaveRequest

Business Role

SAP_HCM_BCR_EMPLOYEE_X1

Business Catalog

SAP_HCM_BC_EMPLOYEE_X1

Business Catalog Group

SAP_HCM_BCG_EMPLOYEE_X1

Technical Role

SAP_HCM_TCR_T_X1

Technical Catalog

SAP_HCM_TC_T_X1

LPD_CUST Role

UIX01HCM

LPD_CUST Instance

TRANSACTIONAL

Front-End and Back-End Server: Assign Role with OData Service Authorization to Users To restrict access to OData services to specific users, you have to assign roles (including OData service authorization for the app) to your users. You have to make the assignment on the back-end and on the front-end server: On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can adjust this role according to your needs. On the front-end server, you can assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs. OData Service (Version Number)

Back-End Server: Delivered Authorization Role (PFCG Role)

Front-End Server: Authorization Role

/GBHCM/LEAVEREQUEST (2)

SAP_GBHCM_LEAVE_REQUEST_EMPL

Use an existing role or create a new one

For more information about authorization roles and assigned OData services, see Front-End Server: Assign Role with OData Service Authorization t and Back-End Server: Assign Role with OData Service Authorization to.

Prerequisites for Implementation Before configuring the app, you must ensure the following: Configure ESS leave solution You use SAP Time Management to manage your employees' time data. You have made the Customizing settings for the Leave Request, Time Accounts, and Team Calendar. For more information, see Customizing for Personnel Management by choosing Employee Self-Service Service-Specific Settings Working Time Leave Request .

Configuration Tasks To enable My Leave Requests, you must perform the following configuration tasks: Enable the SICF Services for the Gateway Service name: /GBHCM/LEAVEREQUEST Enable the SICF Services for UI5 Service name: HCM_LR_CRE

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 96 of 138

Deploy the following Business Add-Ins: /GBHCM/BDD_ELR_APPROVER (Employee Leave Request: Approver) /GBHCM/BDD_ELR_ICON (Employee Leave Request: Icons) /GBHCM/BDD_ELR_MESSAGE (Employee Leave Request: Message) /GBHCM/BDD_ELR_CONFIGURATION (Employee Leave Request: Configuration) /GBHCM/BDD_ELR_TEAMCALENDAR (Employee Leave Request: Team Calendar) /GBHCM/BDD_ELR_TIMEACCOUNTS (Employee Leave Request: Time Account data) For more information on BAdI implementations, see Steps to Activate BAdI Implementations.

More Information For general information about the user management concept in a SAP Fiori environment, see Users in ABAP Front-End System and Users in ABAP Back-End System.

1.24.3 App Extensibility: My Leave Requests You can extend My Leave Requests according to your business needs for different aspects. For this purpose, the following extensibility options are available: Extending all the views You can hide fields in all the views, that is, Main view (S1), History view (S3, S6B), and Entitlements (S2). You can add additional fields in all views. Extending the master view You can add additional attributes in list item on the Master screen (S3).

Note S3 view is extended using S3.controller.js.

Note In addition, any of the complete views can be replaced by your own view.

Extending the Main or Entry view To hide or add additional fields in the main view, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

View

Extension Point

Design Time: Gateway Entity

Design Time: Extension Include (in DDIC Structure)

Runtime: Superclass/ Method to Be Redefined

S1.view.xml

extS1Field

LEAVEREQUEST V2

/GBHCM/S_ELR_LEAVE_

Superclass: /GBHCM/CL_MGW_RDT_ELR_V2

REQU_INCL

Method: GET_ENTITYSET_LEAVEREQUES T /GBHCM/S_ELR_ABS_TYPE_ V2_INCL

Superclass: /GBHCM/CL_MGW_RDT_ELR_V2 Method: GET_ENTITYSET_ABSENCETYPE

/GBHCM/S_ELR_APPROVER_ INCL

Superclass: /GBHCM/CL_MGW_RDT_ELR_V2 Method: GET_ENTITYSET_APPROVER

/GBHCM/S_ELR_WORK_SCHED _INCL

Superclass: /GBHCM/CL_MGW_RDT_ELR_V2 Method: GET_ENTITYSET_WORK_SCHEDU LE

/GBHCM/S_ELR_WS_LEGEND _INCL

Superclass: /GBHCM/CL_MGW_RDT_ELR_V2 Method: GET_ENTITYSET_WS_LEGEND

Extending the History view To hide or add additional fields in the History view, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 97 of 138

View

Extension Point

Design Time: Gateway Entity

Design Time: Extension Include (in DDIC Structure)

Runtime: Superclass/ Method to Be Redefined

S6B.view.xml

extS6BIconTab

LEAVEREQUEST V2

/GBHCM/S_ELR_LEAVE_

Superclass: /GBHCM/CL_MGW_RDT_ELR_V2

REQU_INCL

Method: GET_ENTITYSET_LEAVEREQUES T

Extending the Entitlements view To hide or add additional fields in the Entitlements view, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

View

Extension Point

Design Time: Gateway Entity

Design Time: Extension Include (in DDIC Structure)

Runtime: Superclass/ Method to Be Redefined

S2.view.xml

extS2ColItem

LEAVEREQUEST V2

/GBHCM/S_ELR_TIME

Superclass: /GBHCM/CL_MGW_RDT_ELR_V2

_ACCOUNT_INCL

Method: GET_ENTITYSET_TIMEACCOUNT S2.view.xml

extS2ColHeader

LEAVEREQUEST V2

ANYSTRING

ANYSTRING

Further Extensibility Entities Extension Includes In addition to the extension includes described above, the following extension includes are available: DDIC

Extension Include

Use

/GBHCM/S_ELR_CONFIGURATION_V2

/GBHCM/S_ELR_CONFIG_INCL

Extends the Configuration entity.

/GBHCM/S_ELR_FIELDSELECTION_V2

/GBHCM/S_ELR_FIELDSELECT_ INCL

Extends the Field Selection entity.

/GBHCM/S_ELR_LRQ_ADD_FIELD_V2

/GBHCM/S_ELR_LRQ_ADD_FLD _INCL

Extends the Leave Request Additional Field entity.

/GBHCM/S_ELR_PICKLIST_V2

/GBHCM/S_ELR_PICKLIST _INCL

Extends the PickList entity.

/GBHCM/S_ELR_TEAM_CALENDAR_V2

/GBHCM/S_ELR_TEAM _CALNDR_INCL

Extends the Team Calendar entity.

/GBHCM/S_ELR_TIME_ACCOUNT_V2

/GBHCM/S_ELR_TIME _ACCOUNT_INCL

Extends the Time Account entity.

For more information about extension includes, see Extension Includes.

UI Controller Hooks To plug in and execute custom code, the following hooks are available in the controller code: Controller

Hook

Use

S1.controller.js

extHookChangeFooterButtons

Allows you to add and change buttons for the detail view footer

extHookRouteMatchedHome

Allows you to add UI or business logic

extHookRouteMatchedChange extHookClearData extHookInitCalendar extHookTapOnDate extHookSetHighlightedDays extHookDeviceDependantLayout extHookSubmit extHookOnSubmitLRCfail extHookOnSubmitLRCsuccess

S2.controller.js

S3.controller.js

extHookCallDialog

Allows you to modify the dialog content

extHookTimeAccountCollection

Allows you to modify the TimeAccountCollection

extHookChangeFooterButtons

Allows you to add and change buttons for the detail view footer

extHookChangeFooterButtons

Allows you to add and change buttons for the detail view footer

extHookLeaveRequestCollection

Allows you to modify the LeaveRequestCollection

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 98 of 138

S6B.controller.js

extHookItemTemplate

Allows you to modify the itemTemplate

extHookDetailView

Allows you to add or change UI and business logic

extHookChangeFooterButtons

Allows you to add and change buttons for the detail view footer

extHookWithdrawDialogContent

Allows you to add and change content of withdraw dialog

For more information about UI controller hooks, see UI Controller Hooks.

More Information For a general description of the extensibility options and procedures of Fiori apps, see Extensibility.

1.25 My Paystubs With the transactional app My Paystubs you can enable employees to check and manage a digital version of all their paystubs issued by the company for each payroll period, easily and flexibly using their desktop or mobile device.

Key Features View a list of your paystubs issued by the company Check the details of a paystub Download and store a PDF version of a paystub locally on a device or using a Cloud-based storage solution

System Landscape Requirements The app consists of front-end components (such as the user interfaces) and back-end components (such as the OData service). The back-end and the front-end components are delivered with one product and have to be installed in a system landscape that is enabled for SAP Fiori. Product Version Containing Back-End and Front-End Components of the App

SAP Fiori principal apps for SAP ERP 1.0 SPS03

Back-End Product Versions Supporting the

SAP ERP 6.0 SP15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher

App (Minimum Product Version Stack)

SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment Based on SAP enhancement package 7 of SAP ERP 6.0 also possible: Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

Component for Customer Messages MOB-UIA-PY-MPS

More Information App History: My Paystubs App Implementation: My Paystubs App Extensibility: My Paystubs

1.25.1 App History: My Paystubs The My Paystubs app has been enhanced as follows:

SAP Fiori principal apps for SAP ERP 1.0 SPS 03 (Delivery Date 07/2014) New/Enhanced Extensibility Options

Controller hooks are introduced.

SAP Note for Technical Changes

1931620

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 99 of 138

SAP Fiori principal apps for SAP ERP 1.0 SPS 02 (Delivery Date 05/2014) New/Enhanced Key Features

New key features: Include customer-specific Wage Types for Deductions and Gross Pay using the BAdI BADI_SRA006

New/Enhanced Extensibility Options

No changes.

SAP Note for Technical Changes

1931620

SAP Fiori principal apps for SAP ERP 1.0 SPS 01 (Delivery Date 02/2014) New/Enhanced Key Features

No changes.

New/Enhanced Extensibility Options

New extensibility options: Extending the Master list page You can now add additional attributes in the list items on the Master List page. Extending the Details page You can now add additional fields in the header section on the Details page. OData service can be extended.

SAP Fiori principal apps for SAP ERP 1.0 SPS 00 (Delivery Date 11/2013) Initial delivery.

1.25.2 App Implementation: My Paystubs System Landscape Requirements Before you start to implement the app, ensure that your system landscape has been set up to enable SAP Fiori. This also implies that the front-end and back-end components for your app are already available in this system landscape: SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment Based on SAP enhancement package 7 of SAP ERP 6.0 also possible: Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

Configuration of Front-End Server

Configuration of SAP Fiori Infrastructure

Back-End Product Versions Supporting the App (Minimum Product Version Stack)

SAP ERP 6.0 SP15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher

Product Version Containing Back-End and Front-End Components of the App

SAP Fiori principal apps for SAP ERP 1.0 SPS03

For more information on the installation of the back-end and front-end components of the app, see Installation of Back-End Components and Installation of Front-End Components. For the app, the following software components must be available in your system landscape. These components are contained in the product SAP Fiori principal apps for SAP ERP : Back-End/Front-End Server

Back-End/Front-End Component

Technical Name of Software Component Support Package Level

Back-end server

Back-end component

SRA006 1.0

05

Front-end server

Front-end component

UIX01HCM 100

03

Required SAP Notes For My Paystubs , the following SAP Notes must be available: SAP Note Number

Description

1931620

Release Information

Implementation Tasks The following sections list tasks that have to be performed to implement the My Paystubs app. The tables contain the app-specific data required for these tasks:

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 100 of 138

Front-End Server: Activate OData Services Component

Technical Name

OData Service (Version Number)

SRA006_SRV (1)

For more information about activating OData services, see Front-End Server: Activate OData Services.

Front-End Server: Activate UI5 Application Component

Technical Name

UI5 Application

HCM_PS_MON

For more information about how to activate the UI5 application (ICF service), see Front-End Server: Activate ICF Services of UI5 Application.

Front-End Server: Enable App for Access in SAP Fiori Launchpad There are several steps to be performed to enable the app for access in the SAP Fiori launchpad. You require the listed data to perform these steps. For more information about the steps to be performed, see Setup of Catalogs, Groups, and Roles in the SAP Fiori Launchpad. Component

Technical Name

Semantic Object

RemunerationStatement

Business Role

SAP_HCM_BCR_EMPLOYEE_X1

Business Catalog

SAP_HCM_BC_EMPLOYEE_X1

Business Catalog Group

SAP_HCM_BCG_EMPLOYEE_X1

Technical Role

SAP_HCM_TCR_T_X1

Technical Catalog

SAP_HCM_TC_T_X1

LPD_CUST Role

UIX01HCM

LPD_CUST Instance

TRANSACTIONAL

Front-End and Back-End Server: Assign Role with OData Service Authorization to Users To restrict access to OData services to specific users, you have to assign roles (including OData service authorization for the app) to your users. You have to make the assignment on the back-end and on the front-end server: On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can adjust this role according to your needs. On the front-end server, you can assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs. OData Service (Version Number)

Back-End Server: Delivered Authorization Role (PFCG Role)

Front-End Server: Authorization Role

SRA006_SRV (1)

SAP_HCM_PS_MON_APP

Use an existing role or create a new one

For more information about authorization roles and assigned OData services, see Front-End Server: Assign Role with OData Service Authorization t and Back-End Server: Assign Role with OData Service Authorization to.

Prerequisites for Implementation Before implementing the app, you must ensure the following: Configure parameters to allow employees to view the salary statement as a PDF-based form. Your employees can print the salary statement from the Web application or save it. Paystubs are displayed in SAP Fiori in the same manner as they are displayed in Employee Self-Service (ESS) Applications. Refer to the following document in the SAP Library for detailed information: Business Package for Employee Self-Service (SAP ERP) 1.0 and expand the pages as follows: Employee Self-Service (ESS) Applications Benefits and Payment Salary Statement .

Configuration Tasks To enable My Paystubs, you must perform the following configuration tasks: Enable the SICF Services for the Gateway Service name: SRA006_SRV Enable the SICF Services for UI5 Service name: HCM_PS_MON Deploy the following business add-in (BAdI): XSS_REM_INTERFACE using the classic BAdI implementation The XSS_REM_INTERFACE BAdI is required to filter paystub statements after a payroll run. This BAdI, which is present in the ECC system, belongs to the software component EA-HRRXX. Ensure that the following method of the BAdI is implemented: IF_EX_XSS_REM_INTERFACE~PROVIDE_FILTERED_RGDIR. Deploy the BAdI as a classic BAdI. BADI_SRA006

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 101 of 138

Provides you the flexibility for calculating the Net pay, Gross pay and Deductions for a particular payslip. For instructions on how to activate BAdI implementations, see Steps to Activate BAdI Implementations.

More Information For general information about the user management concept in a SAP Fiori environment, see Users in ABAP Front-End System and Users in ABAP Back-End System.

1.25.3 App Extensibility: My Paystubs You can extend My Paystubs according to your business needs for different aspects. For this purpose, the following extensibility options are available: Extending the Master list view You can add additional attributes in list item on the Master screen. Extending the Details view extS3Header You can hide fields in the header section on Details screen. You can add additional fields in the header section on Details screen. extS3PhoneHeader You can hide fields in the header section on Details screen on your phone. You can add additional fields in the header section on Details screen on your phone.

Note In addition, any of the complete views can be replaced by your own view.

Extending the Master list view (extS2ListItem) To add additional attributes in the list items on the Master screen of the app, the following extensibility entities are available on the different layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

View

Extension Point

Design Time: Gateway Entity

Design Time: Extension Include (in DDIC Structure)

Runtime: Superclass/ Method to Be Redefined

S2.view.xml

extS2ListItem

SRA006_SRV

SRA006_PAYSLIP_INCL

Superclass: CL_SRA006_DPC_EXT Method: PAYSLIPS_GET_ENTITYSET

SRA006_PDFPAYSLIP_INCL

Superclass: CL_SRA006_DPC_EXT Method: PDFPAYSLIPS_GET_ENTITYSET

Extending the Details view on a desktop (extS3Header) To hide or add additional fields in the header section on the Details screen of the app, the following extensibility entities are available on the different layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

View

Extension Point

Design Time: Gateway Entity

Design Time: Extension Include (in DDIC Structure)

Runtime: Superclass/ Method to Be Redefined

S3.view.xml

extS3Header

SRA006_SRV

SRA006_PAYSLIP_INCL

Superclass: CL_SRA006_DPC_EXT Method: PAYSLIPS_GET_ENTITYSET

SRA006_PDFPAYSLIP_INCL

Superclass: CL_SRA006_DPC_EXT Method: PDFPAYSLIPS_GET_ENTITYSET

Extending the Details view on a phone (extS3PhoneHeader) To hide or add additional fields in the header section on the Details screen of the app on your phone, the following extensibility entities are available on the different layers. You have to extend each of these entities according to your specific business needs: UI View

Back End/ABAP Extension Point

Design Time: Gateway Entity

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Design Time: Extension Include (in DDIC Structure)

Runtime: Superclass/ Method to Be Redefined

Page 102 of 138

S3_Phone.view.xml

extS3PhoneHeader

SRA006_SRV

SRA006_PAYSLIP_INCL

Superclass: CL_SRA006_DPC_EXT Method: PAYSLIPS_GET_ENTITYSET

SRA006_PDFPAYSLIP_INCL

Superclass: CL_SRA006_DPC_EXT Method: PDFPAYSLIPS_GET_ENTITYSET

Further Extensibility Entities UI Controller Hooks To plug in and execute custom code, the following hooks are available in the controller code: Controller

Hook

Use

S3.controller.js

extHookChangeFooterButtons

Allows you to add and change buttons for the detail view footer

S3_Phone.controller.js

extHookChangeFooterButtons

Allows you to add and change buttons for the detail view footer

For more information about UI controller hooks, see UI Controller Hooks.

More Information For a general description of the extensibility options and procedures of Fiori apps, see Extensibility.

1.26 My Quality Tasks With the transactional app My Quality Tasks , you can track and confirm your quality tasks created within quality issues (known in the back-end system as quality notifications). You can use the app on a number of mobile devices and standalone systems. The app introduces a new approach for processing quality tasks on the fly and minimizes the need to generate worklists using transaction QM12 in the system. The app enables you to access and process all quality tasks reported for your user regardless of the source quality notification. The app pulls and displays all quality tasks created (for you) in the system (using the transaction QM02). This improves the whole process of completing quality tasks.

Key Features Complete quality tasks using various devices and platforms List all quality tasks created for a user

System Landscape Requirements Note This app is also available in a version for higher back-end releases. For more information, see SAP Help Portal at http://help.sap.com/fiori_products -> SAP Fiori for SAP ERP -> SAP Fiori for SAP ERP 1.0. The app consists of front-end components (such as the user interfaces) and back-end components (such as the OData service). The back-end and the front-end components are delivered in separate products and have to be installed in a system landscape that is enabled for SAP Fiori. Back-End Components Delivered with (Product SAP enhancement package 7 for SAP ERP 6.0 SPS 05 Version Stack) Front-End Components Delivered with (Product SAP Fiori for SAP ERP 1.0 SPS03 Version Stack) SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

Related Fiori Apps Report Quality Issue

Component for Customer Messages

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 103 of 138

QM-QN-NM

More Information App History: My Quality Tasks App Implementation: My Quality Tasks App Extensibility: My Quality Tasks

1.26.1 App Implementation: My Quality Tasks System Landscape Requirements Before you start to implement the app, ensure that your system landscape has been set up to enable SAP Fiori. This also implies that the front-end and back-end components for your app are already available in this system landscape: SAP Fiori System Landscape Options

Configuration of Front-End Server

Setup of SAP Fiori System Landscape with ABAP Environment Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS Configuration of SAP Fiori Infrastructure

Back-End Components Delivered with (Product SAP enhancement package 7 for SAP ERP 6.0 SPS 05 Version Stack) Front-End Components Delivered with (Product SAP Fiori for SAP ERP 1.0 SPS03 Version Stack)

For the app, the following software components must be available in your system landscape. These components are contained in the product SAP Fiori transactional apps for SAP ERP : Back-End/Front-End Server

Back-End/Front-End Component

Technical Name of Software Component Support Package Level

Back-end server

Back-end component

GBX02EAP 600

01

Front-end server

Front-end component

UIX02EAP 100

01

Required SAP Notes For My Quality Tasks , the following SAP Notes must be available: Back-End/Front-End Server

SAP Note Number

Description

Front-end server

1947532

Corrections for Fiori App My Quality Tasks

Release Information Note

1931282

General Information: QM

Implementation Tasks The following sections list tasks that have to be performed to implement the My Quality Tasks app. The tables contain the app-specific data required for these tasks:

Front-End Server: Activate OData Services Component

Technical Name

OData Service (Version Number)

QM_TASK_SRV (1)

For more information about activating OData services, see Front-End Server: Activate OData Services.

Front-End Server: Activate UI5 Application Component

Technical Name

UI5 Application

UI_QM_TASKS

For more information about how to activate the UI5 application (ICF service), see Front-End Server: Activate ICF Services of UI5 Application.

Front-End Server: Enable App for Access in SAP Fiori Launchpad There are several steps to be performed to enable the app for access in the SAP Fiori launchpad. You require the listed data to perform these steps. For more information about the steps to be performed, see Setup of Catalogs, Groups, and Roles in the SAP Fiori Launchpad. Component

Technical Name

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 104 of 138

Semantic Object

QualityNotificationTask

Business Role

SAP_QM_BCR_QUALITYENGINEER

Business Catalog

SAP_QM_BC_QUALITYENGINEER

Business Catalog Group

SAP_QM_BCG_QUALITYENGINEER

Technical Role

SAP_QM_TCR_T

Technical Catalog

SAP_QM_TC_T

LPD_CUST Role

UIAPQM01

LPD_CUST Instance

TRANSACTIONAL

Front-End and Back-End Server: Assign Role with OData Service Authorization to Users To restrict access to OData services to specific users, you have to assign roles (including OData service authorization for the app) to your users. You have to make the assignment on the back-end and on the front-end server: On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can adjust this role according to your needs. On the front-end server, you can assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs. OData Service (Version Number)

Back-End Server: Delivered Authorization Role (PFCG Role)

Front-End Server: Authorization Role

QM_TASK_SRV (1)

SAP_QM_MYQUALITYTASKS_APP

Use an existing role or create a new one

For more information about authorization roles and assigned OData services, see Front-End Server: Assign Role with OData Service Authorization t and Back-End Server: Assign Role with OData Service Authorization to.

Prerequisites for Implementation There are no prerequisites for implementation for the app.

Configuration Tasks The configuration of the My Quality Tasks app is controlled by Customizing activities that are available under Quality Management Fiori Apps for Quality Management . By default, the Customizing activities are delivered with predefined settings. However, you can check the settings in client 000 and adapt them as appropriate for your business case. You do not need to perform any specific configuration before you use the My Quality Tasks app.

Note The settings that you make at application level are stored in the cache of your Web browser. For this reason, if you want to discard these settings and revert to the default settings that come from Customizing, you should delete your browsing history and clear the cache of your Web browser.

More Information For general information about the user management concept in a SAP Fiori environment, see Users in ABAP Front-End System and Users in ABAP Back-End System.

1.26.2 App History: My Quality Tasks The My Quality Tasks app has been enhanced as follows:

SAP Fiori for SAP ERP 1.0 SPS 03 (Delivery Date 07/2014) No Changes

SAP Fiori for SAP ERP 1.0 SPS 02 (Delivery Date 05/2014) No changes.

SAP Fiori for SAP ERP 1.0 SPS 01 (Delivery Date 02/2014) New/Enhanced Key Features

No changes.

New/Enhanced Extensibility Options

Extensibility mechanisms are available in the app.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 105 of 138

For more information, see: App Extensibility: My Quality Tasks

SAP Fiori for SAP ERP 1.0 SPS 00 (Delivery Date 11/2013) Initial delivery.

1.27 My Timesheet With the transactional app My Timesheet you can enable employees to manage their time entries quickly and efficiently using their desktop or mobile device.

Key Features Using Quick Entry, enter time for an entire week, month, or for all missing time entries View the time entry status overview for a month View weekly time entry details at a glance, with one-step release or delete Create time entry for a single day or multiple days in a single step Option to review and modify existing timesheet entries

System Landscape Requirements The app consists of front-end components (such as the user interfaces) and back-end components (such as the OData service). The back-end and the front-end components are delivered with one product and have to be installed in a system landscape that is enabled for SAP Fiori. Product Version Containing Back-End and Front-End Components of the App

SAP Fiori principal apps for SAP ERP 1.0 SPS03

Back-End Product Versions Supporting the App (Minimum Product Version Stack)

SAP Fiori System Landscape Options

SAP ERP 6.0 SP15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher Setup of SAP Fiori System Landscape with ABAP Environment Based on SAP enhancement package 7 of SAP ERP 6.0 also possible: Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

Related Apps Approve Timesheets

Component for Customer Messages MOB-UIA-PT-MTS

More Information App History: My Timesheet App Implementation: My Timesheet App Extensibility: My Timesheet

1.27.1 App History: My Timesheet The My Timesheet app has been enhanced as follows:

SAP Fiori principal apps for SAP ERP 1.0 SPS 03 (Delivery Date 07/2014) New/Enhanced Extensibility Options

Controller hooks are introduced.

SAP Note for Technical Changes

1931621

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 106 of 138

SAP Fiori principal apps for SAP ERP 1.0 SPS02 (Delivery Date 05/2014) New/Enhanced Key Features

No changes.

New/Enhanced Extensibility Options

No changes.

SAP Note for Technical Changes

1931621

SAP Fiori principal apps for SAP ERP 1.0 SPS 01 (Delivery Date 02/2014) New/Enhanced Key Features

Enhanced key features: Enhanced search help for manual time entry. Recording of time entries for Wage Type . Decimal input supported for time entry.

New/Enhanced Extensibility Options

New extensibility options: Extending the Week Entry view Extending the Create Entry view OData service can be extended

SAP Note for Technical Changes

1931621

SAP Fiori principal apps for SAP ERP 1.0 SPS 00 (Delivery Date 11/2013) Initial delivery.

1.27.2 App Implementation: My Timesheet System Landscape Requirements Before you start to implement the app, ensure that your system landscape has been set up to enable SAP Fiori. This also implies that the front-end and back-end components for your app are already available in this system landscape: SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment Based on SAP enhancement package 7 of SAP ERP 6.0 also possible: Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

Configuration of Front-End Server

Configuration of SAP Fiori Infrastructure

Back-End Product Versions Supporting the App (Minimum Product Version Stack)

SAP ERP 6.0 SP15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher

Product Version Containing Back-End and Front-End Components of the App

SAP Fiori principal apps for SAP ERP 1.0 SPS03

For more information on the installation of the back-end and front-end components of the app, see Installation of Back-End Components and Installation of Front-End Components. For the app, the following software components must be available in your system landscape. These components are contained in the product SAP Fiori principal apps for SAP ERP : Back-End/Front-End Server

Back-End/Front-End Component

Technical Name of Software Component Support Package Level

Back-end server

Back-end component

SRA002 1.0

05

Front-end server

Front-end component

UIX01HCM 100

03

Required SAP Notes For My Timesheet , the following SAP Notes must be available: SAP Note Number

Description

1931621

Release Information

Implementation Tasks The following sections list tasks that have to be performed to implement the My Timesheet app. The tables contain the app-specific data required for these tasks:

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 107 of 138

Front-End Server: Activate OData Services Component

Technical Name

OData Service (Version Number)

SRA002_TIMESHEET_SRV (1)

For more information about activating OData services, see Front-End Server: Activate OData Services.

Front-End Server: Activate UI5 Application Component

Technical Name

UI5 Application

HCM_TS_CRE

For more information about how to activate the UI5 application (ICF service), see Front-End Server: Activate ICF Services of UI5 Application.

Front-End Server: Enable App for Access in SAP Fiori Launchpad There are several steps to be performed to enable the app for access in the SAP Fiori launchpad. You require the listed data to perform these steps. For more information about the steps to be performed, see Setup of Catalogs, Groups, and Roles in the SAP Fiori Launchpad. Component

Technical Name

Semantic Object

TimeEntry

Business Role

SAP_HCM_BCR_EMPLOYEE_X1

Business Catalog

SAP_HCM_BC_EMPLOYEE_X1

Business Catalog Group

SAP_HCM_BCG_EMPLOYEE_X1

Technical Role

SAP_HCM_TCR_T_X1

Technical Catalog

SAP_HCM_TC_T_X1

LPD_CUST Role

UIX01HCM

LPD_CUST Instance

TRANSACTIONAL

Front-End and Back-End Server: Assign Role with OData Service Authorization to Users To restrict access to OData services to specific users, you have to assign roles (including OData service authorization for the app) to your users. You have to make the assignment on the back-end and on the front-end server: On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can adjust this role according to your needs. On the front-end server, you can assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs. OData Service (Version Number)

Back-End Server: Delivered Authorization Role (PFCG Role)

Front-End Server: Authorization Role

SRA002_TIMESHEET_SRV (1)

SAP_HCM_TS_CRE_APP

Use an existing role or create a new one

For more information about authorization roles and assigned OData services, see Front-End Server: Assign Role with OData Service Authorization t and Back-End Server: Assign Role with OData Service Authorization to.

Prerequisites for Implementation Before implementing the app, you must ensure the following: Set the Business Suite Roles for the app. My Timesheet uses the Data Entry Profile (DEP) to determine the usage and behavior for the client. The System Administrator maintains the DEP for each user in the CVR parameter. To set the DEP, from the SAP GUI, go to

System

User Profile

Own Data

.

Note If no DEP is set, the default DEP, ESS, is used. If no default DEP is found, the client receives an error message. You use SAP Cross-Application Time Sheet (CATS). The Timesheet must be set up. For the SAP Fiori application, you can use the model data entry profile ESS, which has been designed to meet the special requirements of Employee Self-Service. For more information, see the Implementation Guide for the Cross-Application Time Sheet. You must have created personnel numbers in the SAP system for all employees who are to record data. The personnel number must be related to the employee’s system user name in the Communication (0105) infotype. For more information, see Assigning an SAP User ID to a Personnel Number You have used the user parameter CVR to assign each employee a specific data entry profile, which they use to enter their working times. This profile determines the data entry process and the layout of the timesheet. If this user parameter has not been stored, the system uses the ESS data entry profile as standard. You have assigned all users the required authorizations. SAP delivers a standard role that contains these authorizations.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 108 of 138

Constraints Compared with CATS classic, the following constraints exist for this Fiori application: For this app, time administrators or data entry personnel cannot record working time data. The following SAP enhancements are not supported by this app: CATS0004 (Deactivate Functions on the User Interface) You make the necessary settings in Customizing. CATS0007 (Subscreen on Initial Screen) CATS0011 (Customer Functions) CATS0012 (Subscreen on Data Entry Screen)

More Information Customizing Settings for Data Entry Profiles Implementing User Parameters Settings and Customizing

Configuration Tasks To enable My Timesheet, you must perform the following configuration tasks: Enable the SICF Services for the Gateway Service Name:SRA002_TIMESHEET_SRV. Enable the SICF Services for UI5 Service name: HCM_TS_CRE Deploy the required Business Add-Ons (BAdIs) for the application. BADI_SRA002_FIELDRANKINGS Determines the order in which cost objects are given importance for display in the cost assignment. BADI_SRA002_PICKLIST_TXTFILTER Extends the text search used by the Cost Assignment search. The default is to search for the text in field IDs and descriptions. This BAdI extends the search across other cost object attributes. BADI_SRA002_QUICKENTRY_BEGDA Determines the beginning date for calculating missing entries for Auto Entry and the My Timesheet app tile. BADI_SRA002_QUICKENTRY_PROJ BAdI to change the project proposal for quick entry. BADI_SRA002_WCSTATUSES Determines the handling of CATS statuses highlighted in the monthly calendar. Allows for mapping other statuses to the three statuses used in My Timesheet. For more information, see Steps to Activate BAdI Implementations.

More Information For general information about the user management concept in a SAP Fiori environment, see Users in ABAP Front-End System and Users in ABAP Back-End System.

1.27.3 App Extensibility: My Timesheet You can extend My Timesheet according to your business needs for different aspects. For this purpose, the following extensibility options are available: Extending the Week Entry view You can add a new column in the Week Entry view. Extending the Create Entry view You can add a new field in the Create Entry view.

Note In addition, any of the complete views can be replaced by your own view.

Extending the Week Entry view To add a new column in the Week Entry view of the app, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

View

Extension Point

Design Time: Gateway Entity

Design Time: Extension Include (in DDIC Structure)

Runtime: Superclass/ Method to Be Redefined

S3.view.xml

extS3Column

SRA002_TIMESHEET_SRV

SRA002_S_TIMEDATA_ENTITY_ Superclass: CL_SRA002_TIMESHEET_DPC INCL Method: TIMEDATALIST_GET_ENTITYSE T SRA002_S_WORKCAL_ENTITY_I Superclass: CL_SRA002_TIMESHEET_DPC NCL

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 109 of 138

Method: WORKCALENDARS_GET_ENTITYS ET

Extending the Create Entry view To add a new field in the Create Entry view of the app, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

View

Extension Point

Design Time: Gateway Entity

Design Time: Extension Include (in DDIC Structure)

Runtime: Superclass/ Method to Be Redefined

S31.view.xml

extS31FormElement

SRA002_TIMESHEET_SRV

SRA002_S_PROFILE_ENTITY_I Superclass: CL_SRA002_TIMESHEET_DPC NCL Method: PROFILEFIELDS_GET_ENTITYS ET SRA002_S_WORKLIST_ENTITY_ Superclass: CL_SRA002_TIMESHEET_DPC INCL Method: WORKLISTCOLLECTI_GET_ENTI TYSET

Further Extensibility Entities Extension Includes In addition to the extension includes described above, the following extension includes are available: DDIC

Extension Include

Use

SRA002_S_INITIALINFO

SRA002_S_INITIALINFO_INCL

Extends the Initial Info entity.

SRA002_S_SUMMARY

SRA002_S_SUMMARY_INCL

Allows you to change the summary information on app tile of the Fiori Launchpad.

For more information about extension includes, see Extension Includes.

UI Controller Hooks To plug in and execute custom code, the following hooks are available in the controller code: Controller

Hook

Use

S2.controller.js

extHookCalendarMonthChange

Allows you to add UI or business logic

extHookGetUserInfo extHookGetTimeSheetCalendar extHookUpdateData S3.controller.js

extHookReleaseEntriesSummary

Allows you to add UI or business logic

extHookOnSubmit extHookOnItemSelect extHookUpdateData extHookGetTimeSheetCalendar extHookLoadList extHookUpdatePageData S31.controller.js

extHookOnSuggestedInputHelp

Allows you to add UI or business logic

extHookOnInputHelp extHookUpdateData

For more information about UI controller hooks, see UI Controller Hooks.

More Information For a general description of the extensibility options and procedures of Fiori apps, see Extensibility.

1.28 My Travel Requests PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 110 of 138

With the transactional app My Travel Requests , you can manage your own travel requests in real time using your desktop or mobile device. The app allows you to create, edit, submit, and delete requests. You can also check the status of a particular request at any time.

Key Features Create a new travel request Submit travel requests to your organizational manager Browse existing travel requests in detail Edit existing travel requests and resubmit Delete existing travel requests

System Landscape Requirements The app consists of front-end components (such as the user interfaces) and back-end components (such as the OData service). The back-end and the front-end components are delivered with one product and have to be installed in a system landscape that is enabled for SAP Fiori. Product Version Containing Back-End and Front-End Components of the App Back-End Product Versions Supporting the App (Minimum Product Version Stack)

SAP Fiori principal apps for SAP ERP 1.0 SPS03

SAP ERP 6.0 SP15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher

SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment Based on SAP enhancement package 7 of SAP ERP 6.0 also possible: Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

Related Apps Approve Travel Expenses Approve Travel Requests

Component for Customer Messages MOB-UIA-FI-MTR: My Travel Requests

More Information App History: My Travel Requests App Implementation: My Travel Requests App Extensibility: My Travel Requests

1.28.1 App History: My Travel Requests The My Travel Requests app has been enhanced as follows:

SAP Fiori for SAP ERP Principal Apps 1.0 SPS 003 (Delivery Date 07/2014) No changes.

SAP Fiori for SAP ERP Principal Apps 1.0 SPS 002 (Delivery Date 05/2014) No changes.

SAP Fiori for SAP ERP Principal Apps 1.0 SPS 001 (Delivery Date 02/2014) No changes.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 111 of 138

SAP Fiori for SAP ERP Principal Apps 1.0 SPS 00 (Delivery Date 11/2013) Initial delivery.

1.28.2 App Implementation: My Travel Requests System Landscape Requirements For the app, the following software components must be available in your system landscape. These components are contained in the product SAP Fiori principal apps for SAP ERP : Back-End/Front-End Server

Back-End/Front-End Component

Technical Name of Software Component Support Package Level

Back-end server

Back-end component

SRA004 1.0

04

Front-end server

Front-end component

UIX01TRV 100

02

Required SAP Notes For My Travel Requests , the following SAP Notes must be available: Back-End/Front-End Server

SAP Note Number

Description

For more information, see the collective SAP Note.

1980943

Collective SAP Note listing all relevant SAP Notes for this app.

Implementation Tasks The following sections list tasks that have to be performed to implement the < My Travel Requests > app. The tables contain the app-specific data required for these tasks:

Front-End Server: Activate OData Services Component

Technical Name

OData Service (Version Number)

SRA004_SRV (1)

For more information about activating OData services, see Front-End Server: Activate OData Services.

Front-End Server: Activate UI5 Application Component

Technical Name

UI5 Application

ui5_fi_trreq_cr

For more information about how to activate the UI5 application (ICF service), see Front-End Server: Activate ICF Services of UI5 Application.

Front-End Server: Enable App for Access in SAP Fiori Launchpad There are several steps to be performed to enable the app for access in the SAP Fiori launchpad. You require the listed data to perform these steps. Component

Technical Name

Semantic Object Business Role

SAP_TRAVEL_BCR_EMPLOYEE_X1

Business Catalog

SAP_TRAVEL_BC_EMPLOYEE_X1

Business Catalog Group

SAP_TRAVEL_BCG_EMPLOYEE_X1

Technical Role Technical Catalog LPD_CUST Role LPD_CUST Instance

Front-End and Back-End Server: Assign Role with OData Service Authorization to Users To grant access to OData services to specific users, you have to assign roles (including OData service authorization for the app) to your users. You have to make the assignment on the back-end and on the front-end server: On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can adjust this role according to your needs. On the front-end server, you can assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 112 of 138

OData Service (Version Number)

Back-End Server: Delivered Authorization Role (PFCG Role)

Front-End Server: Authorization Role

SRA004_SRV (1)

SAP_FIN_TR_CRE_APP

Use an existing role or create a new one.

For more information about authorization roles and assigned OData services, see Front-End Server: Assign Role with OData Service Authorization t and Back-End Server: Assign Role with OData Service Authorization to.

More Information For general information about the user management concept in a SAP Fiori environment, see Users in ABAP Front-End System and Users in ABAP Back-End System.

1.28.3 App Extensibility: My Travel Requests You can extend My Travel Requests according to your business needs for different aspects. For this purpose, the following extensibility options are available: Extension Points

To extend My Travel Requests , you can use the following extension points: Name: extInfoAdditionalData Location: detail.view.app.xml Purpose: Add data to the information tab Name: extTabs Location: detail.view.app.xml Purpose: Add a new tab to the tab container Name: Additionalbuttons Location: detail.controller.js Purpose: Add buttons to the footer toolbar

More Information For a general description of the extensibility options and procedures of Fiori apps, see Extensibility.

1.29 My Spend With the transactional app My Spend , you can track the budget and spending status of your departments and projects, anywhere and anytime. This app consolidates budget and spending information and visualizes it in an easy-to-consume way.

Key Features View budget and actual spending data of your departments and projects Display the overview of a specific area, including the budgeted and actual spending Drill down by various dimensions and to the corresponding accounts

Note This app runs on desktops and tablets, but not on smartphones.

System Landscape Requirements The app consists of front-end components (such as the user interfaces) and back-end components (such as the OData service). The back-end and the front-end components are delivered with one product and have to be installed in a system landscape that is enabled for SAP Fiori. Product Version Containing Back-End and Front-End Components of the App Back-End Product Versions Supporting the App (Minimum Product Version Stack)

SAP Fiori System Landscape Options

SAP Fiori principal apps for SAP ERP 1.0 SPS03

SAP ERP 6.0 SP15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher Setup of SAP Fiori System Landscape with ABAP Environment Based on SAP enhancement package 7 of SAP ERP 6.0 also possible: Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 113 of 138

Component for Customer Incidents MOB-UIA-FI-MS

More Information App History: My Spend App Implementation: My Spend App Extensibility: My Spend

1.29.1 App History: My Spend The My Spend app has been enhanced as follows:

SAP Fiori principal apps for SAP ERP 1.0 SPS 03 (Delivery Date 07/2014) No changes.

SAP Fiori principal apps for SAP ERP 1.0 SPS 02 (Delivery Date 05/2014) No changes.

SAP Fiori principal apps for SAP ERP 1.0 SPS 01 (Delivery Date 02/2014) No changes.

SAP Fiori principal apps for SAP ERP 1.0 SPS 00 (Delivery Date 11/2013) Initial delivery.

1.29.2 App Implementation: My Spend System Landscape Requirements Before you start to implement the app, ensure that your system landscape has been set up to enable SAP Fiori. This also implies that the front-end and back-end components for your app are already available in this system landscape: SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment Based on SAP enhancement package 7 of SAP ERP 6.0 also possible: Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

Configuration of Front-End Server

Configuration of SAP Fiori Infrastructure

Back-End Product Versions Supporting the App (Minimum Product Version Stack)

SAP ERP 6.0 SP15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher

Product Version Containing Back-End and Front-End Components of the App

SAP Fiori principal apps for SAP ERP 1.0 SPS03

For more information on the installation of the back-end and front-end components of the app, see Installation of Back-End Components and Installation of Front-End Components. For the app, the following software components must be available in your system landscape. These components are contained in the product SAP Fiori principal apps for SAP ERP : Back-End/Front-End Server

Back-End/Front-End Component

Technical Name of Software Component Support Package Level

Back-end server

Back-end component

SRA012 1.0

03

Front-end server

Front-end component

UIX01EAP 100

03

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 114 of 138

Required SAP Notes For My Spend , the following SAP Notes must be available: Back-End/Front-End Server

SAP Note Number

Description

Back-end server and front-end server

1940348

Collective SAP Note for the My Spend app

Implementation Tasks The following sections list tasks that have to be performed to implement the My Spend app. The tables contain the app-specific data required for these tasks:

Front-End Server: Activate OData Services Component

Technical Name

OData Service (Version Number)

SRA012_SPEND_SRV (0001)

For more information about activating OData services, see Front-End Server: Activate OData Services.

Front-End Server: Activate UI5 Application Component

Technical Name

UI5 Application

FIN_SPE_MON

For more information about how to activate the UI5 application (ICF service), see Front-End Server: Activate ICF Services of UI5 Application.

Front-End Server: Enable App for Access in SAP Fiori Launchpad There are several steps to be performed to enable the app for access in the SAP Fiori launchpad. You require the listed data to perform these steps. For more information about the steps to be performed, see Setup of Catalogs, Groups, and Roles in the SAP Fiori Launchpad. Component

Technical Name

Semantic Object

CostObjectVariance

Business Role

SAP_FIN_BCR_CostManager_X1

Business Catalog

SAP_FIN_BC_CostManager_X1

Business Catalog Group

SAP_FIN_BCG_CostManager_X1

Technical Role

SAP_FIN_SPE_MON_APP

Technical Catalog

SAP_FIN_TC_T_X1

LPD_CUST Role

UIX01FI

LPD_CUST Instance

TRANSACTIONAL

Front-End and Back-End Server: Assign Role with OData Service Authorization to Users To restrict access to OData services to specific users, you have to assign roles (including OData service authorization for the app) to your users. You have to make the assignment on the back-end and on the front-end server: On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can adjust this role according to your needs. On the front-end server, you can assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs. OData Service (Version Number)

Back-End Server: Delivered Authorization Role (PFCG Role)

Front-End Server: Authorization Role

SRA012_SPEND_SRV (1)

SAP_FIN_SPE_MON_APP

SAP_FIN_BCR_CostManager_X1

For more information about authorization roles and assigned OData services, see Front-End Server: Assign Role with OData Service Authorization t and Back-End Server: Assign Role with OData Service Authorization to.

Configuration Tasks To enable My Spend , you must perform the following configuration tasks: User role configuration: Front-end system (gateway system) 1. Run transaction SU01, specify a user and click Edit . 2. On the Roles tab, enter the following roles: SAP_FIN_TCR_T_X1 SAP_FIN_BCR_COSTMANAGER_X1 3. Click Save .

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 115 of 138

Back-end system (ECC system with business data) If the gateway system and the back-end system are on the same system, follow these steps in the same system: 1. Run transaction PFCG, enter role SAP_FIN_SPE_MON_APP and click Copy . 2. Enter a target role, for example, Z_FIN_SPE_MON_APP, and click Copy All . 3. Click Edit . 4. On the Authorization tab, click Propose Profile Name . 5. Click Save . 6. Click Change Authorization Data . 7. Enter the controlling areas to which the user has access. 8. Click Save . 9. Enter values for other authorization objects to which the user has access. 10. Click Save and then Generate , and the status of authorization becomes “ generated ”. 11. Assign this role to the user by following the steps introduced in Front-end system (gateway system) in the back-end system. Business configuration: 1. Run transaction FPB_MAINTAIN_PERS_S in the back-end system. 2. Enter DIA_CCMONITOR in Personalization Dialog , enter your target user, and then click Execute . 3. Specify your controlling area, cost center group, cost element group, and then click Save . (Cost Center Group and Cost Element Group are required, because the application cannot recognize individual values.) 4. In the next page, enter DIA_IOMONITOR in Personalization Dialog , enter your target user, and then click Execute . 5. Specify your controlling area, internal order group, cost element group, and then click Save . (Cost Center Group and Cost Element Group are required, because the application cannot recognize individual values.)

More Information For general information about the user management concept in a SAP Fiori environment, see Users in ABAP Front-End System and Users in ABAP Back-End System.

1.29.3 App Extensibility: My Spend You can extend My Spend according to your business needs in different aspects. For this purpose, the following extensibility options are available: Extensibility in list tree table In addition to the predefined columns in list tree table, you can add more columns from the back-end system to list tree table. Extensibility in line items In addition to the predefined columns in line items, you can add more columns from the back-end system to line items.

Extensibility in List Tree Table To add a column in list tree table, the following extensibility entities are available on different software layers. You have to extend each of these entities according to your specific business needs: UI View

Extension Point

fin.co.myspend.view.ListTreeTable

extTreeTableColumnHeaders extTreeTableColumnValues

Extensibility in Line Items To add a column in line items, the following extensibility entities are available on different software layers. You have to extend each of these entities according to your specific business needs: UI View

Extension Point

fin.co.myspend.view.LineItems

extLineItemsColumnHeaders extLineItemsColumnValues

More Information For a general description of the extensibility options and procedures of Fiori apps, see Extensibility.

1.30 Order from Requisitions With the transactional app 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.

Note Order from Requisitions does not support service items. For more information about the functional differences between this app and the corresponding

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 116 of 138

SAP ERP back-end functionality, see SAP Note 2037648. Order from Requisitions is not optimized for use with a phone. Please use a tablet or desktop device.

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

System Landscape Requirements The app consists of front-end components (such as the user interfaces) and back-end components (such as the OData service). The back-end and the front-end components are delivered with one product and have to be installed in a system landscape that is enabled for SAP Fiori. Product Version Containing Back-End and Front-End Components of the App Back-End Product Versions Supporting the App (Minimum Product Version Stack)

SAP Fiori System Landscape Options

SAP Fiori principal apps for SAP ERP 1.0 SPS03

SAP ERP 6.0 SP15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher Setup of SAP Fiori System Landscape with ABAP Environment Based on SAP enhancement package 7 of SAP ERP 6.0 also possible: Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

Related Apps Approve Requisitions Approve Purchase Orders Approve Purchase Contracts Track Purchase Order

Component for Customer Incidents Order from Requisitions (MOB-UIA-MM-OR)

More Information App History: Order from Requisitions App Implementation: Order from Requisitions App Extensibility: Order from Requisitions

1.30.1 App History: Order from Requisitions The Order from Requisitions app has been enhanced as follows:

SAP Fiori principal apps for SAP ERP 1.0 SPS03 (Delivery Date 07/2014) No changes.

SAP Fiori principal apps for SAP ERP 1.0 SPS02 (Delivery Date 05/2014) New/Enhanced Key Features

No new or enhanced features, corrections only.

New/Enhanced Extensibility Options

No changes.

SAP Note for Technical Changes

1940571

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 117 of 138

SAP Fiori principal apps for SAP ERP 1.0 SPS01 (Delivery Date 02/2014) No changes.

SAP Fiori principal apps for SAP ERP 1.0 SPS00 (Delivery Date 01/2014) Initial delivery.

1.30.2 App Implementation: Order from Requisitions System Landscape Requirements Before you start to implement the app, ensure that your system landscape has been set up to enable SAP Fiori. This also implies that the front-end and back-end components for your app are already available in this system landscape: SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment Based on SAP enhancement package 7 of SAP ERP 6.0 also possible: Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

Configuration of Front-End Server

Configuration of SAP Fiori Infrastructure

Back-End Product Versions Supporting the App (Minimum Product Version Stack)

Product Version Containing Back-End and Front-End Components of the App

SAP ERP 6.0 SP15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher SAP Fiori principal apps for SAP ERP 1.0 SPS03

For more information on the installation of the back-end and front-end components of the app, see Installation of Back-End Components and Installation of Front-End Components. For the app, the following software components must be available in your system landscape. These components are contained in the product SAP Fiori principal apps for SAP ERP : Back-End/Front-End Server

Back-End/Front-End Component

Technical Name of Software Component Support Package Level

Back-end server

Back-end component

SRA013 1.0

05

Front-end server

Front-end component

UIX01EAP 100

03

Required SAP Notes For Order from Requisitions , the following SAP Notes must be available: Back-End/Front-End Server

SAP Note Number

Description

Both

1940571

Central note for Order from Requisitions . All other important notes for this app are referenced from the central note.

Implementation Tasks The following sections list tasks that have to be performed to implement the Order from Requisitions app. The tables contain the app-specific data required for these tasks:

Front-End Server: Activate OData Services Component

Technical Name

OData Service (Version Number)

sra013_po_from_pr_srv (1)

Front-End Server: Activate UI5 Application Component

Technical Name

UI5 Application

MM_PURORD_OR

For more information about how to activate the UI5 application (ICF service), see Front-End Server: Activate ICF Services of UI5 Application.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 118 of 138

Front-End Server: Enable App for Access in SAP Fiori Launchpad There are several steps to be performed to enable the app for access in the SAP Fiori launchpad. You require the listed data to perform these steps. For more information about the steps to be performed, see Setup of Catalogs, Groups, and Roles in the SAP Fiori Launchpad. Component

Technical Name

Semantic Object

PurchaseRequisition

Business Role

SAP_MM_BCR_Buyer_X1

Business Catalog

SAP_MM_BC_Buyer_X1

Business Catalog Group

SAP_MM_BCG_Buyer_X1

Technical Role

SAP_MM_TCR_T_X1

Technical Catalog

SAP_MM_TC_T_X1

LPD_CUST Role

UIX01MM

LPD_CUST Instance

TRANSACTIONAL

Front-End and Back-End Server: Assign Role with OData Service Authorization to Users To grant access to OData services to specific users, you have to assign roles (including OData service authorization for the app) to your users. You have to make the assignment on the back-end and on the front-end server: On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can adjust this role according to your needs. On the front-end server, you can assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs. OData Service (Version Number)

Back-End Server: Delivered Authorization Role (PFCG Role)

Front-End Server: Authorization Role

sra013_po_from_pr_srv (1)

SAP_MM_PURORD_OR_APP

Use an existing role or create a new one

For more information about authorization roles and assigned OData services, see Front-End Server: Assign Role with OData Service Authorization t and Back-End Server: Assign Role with OData Service Authorization to.

Prerequisites for Implementation Before implementing the app, you must ensure that the business users who will use the Order from Requisitions app have the authorizations required for creating orders from requisitions in the SAP GUI.

More Information For general information about the user management concept in a SAP Fiori environment, see Users in ABAP Front-End System and Users in ABAP Back-End System.

1.30.3 App Extensibility: Order from Requisitions You can extend the Order from Requisitions app for different aspects. For this purpose, the following extensibility option is available: Add Fields to Supplier Details

Add Fields to Supplier Details To add customer fields to the Order from Requisitions app, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

View

Extension Point

Design Time: Gateway Entity

Design Time: Extension Include (in DDIC Structure)

Runtime: Data Structure to Be Redefined

FS_Supplier.view.xml

supplierDetailsHeader

SupplierInfo

SRA013_S_VENDOR_INCL

SRA013_S_VENDOR_DETAILS

FS_Supplier.view.xml

supplierDetailsContact

SupplierContact

SRA013_S_VENDOR_CONTACT_I SRA013_S_VENDOR_CONTACT NCL

FS_Supplier.view.xml

supplierDetailsData

SupplierInfo

SRA013_S_VENDOR_INCL

SRA013_S_VENDOR_DETAILS

FS_Supplier.view.xml

supplierDetailsPurData

SupplierInfo

SRA013_S_VENDOR_INCL

SRA013_S_VENDOR_DETAILS

Further Extensibility Entities

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 119 of 138

Business Add-Ins (BAdIs) The following BAdIs are available for extensibility purposes: SRA013_CREATE_PO_FROM_PR_MPC You can use this BAdI to enhance the supplier-related entities of the sra013_po_from_pr_srv Gateway service, for example, to add your own fields. SRA013_CREATE_PO_FROM_PR_DPC You can use this BAdI to enhance the supplier data that is retrieved from the back-end system. You can also use it to display pictures of supplier contacts in supplier fact sheets. The above listed BAdIs are available in Customizing for Materials Management under

Purchasing

Purchase Orders

Order from Requisitions App

.

UI Controller Hooks To plug in and execute custom code, the following hooks are available in the controller code: Controller

Hook

Use

FS_Supplier.controller.js

extHookOnDataReceived

Allows you to check and change the supplier data.

For more information about UI controller hooks, see UI Controller Hooks.

More Information For a general description of the extensibility options and procedures of Fiori apps, see Extensibility.

1.31 Release Production Orders With the transactional app, 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.

Key Features Provides an overview of production orders to be released based on individual variants Gives end users immediate overview of missing parts Detailed screen that provides end users with decision-critical information (date and time, system and user status, relevant work centers, missing part information for operations, etc.) Search engine to identify and filter production orders Provides the ability to perform the material availability check on one or more production orders Possible to navigate to the stock requirement list from the material description from the detail screen or from the missing parts overview screens. Columns in the overview table can be sorted in ascending or descending order. Availability check can be performed to find missing parts that is displayed with an alert box displaying the number of missing parts.

System Landscape Requirements Note This app is also available in a version for higher back-end releases. For more information, see SAP Help Portal at http://help.sap.com/fiori_products -> SAP Fiori for SAP ERP -> SAP Fiori for SAP ERP 1.0. The app consists of front-end components (such as the user interfaces) and back-end components (such as the OData service). The back-end and the front-end components are delivered in separate products and have to be installed in a system landscape that is enabled for SAP Fiori. Product Version Containing Back-End and Front-End Components of the App Back-End Product Versions (with Minimum Support Package Stack) Supporting the App

SAP Fiori System Landscape Options

SAP Fiori transactional apps for SAP ERP 1.0 SPS01

SAP ERP 6.0 SPS15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher Setup of SAP Fiori System Landscape with ABAP Environment

Component for Customer Incidents PP-SFC

More Information PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 120 of 138

App History: Release Production Orders App Implementation: Release Production Orders

1.31.1 App History: Release Production Orders The Release Production Orders app has been enhanced as follows:

SAP Fiori Transactional apps for SAP ERP 1.0 (Delivery Date 07/2014) No Changes

SAP Fiori Transactional apps for SAP ERP 1.0 (Delivery Date 02/2014) New/Enhanced Key Features

New key features: Switch off Production Order count You can now switch off the production order count for each variant. This additional flag shall be set in the backend. If the flag is set, the count is not displayed for this variant if this variant is not active / selected by the end user. Material availability check You can now trigger the material availability check via the client. Sort overview table You can now sort all the columns on the overview screen.

SAP Fiori Transactional apps for SAP ERP 1.0 (Delivery Date 02/2013) Initial delivery.

1.31.2 App Implementation: Release Production Orders System Landscape Requirements The app consists of front-end components (such as the user interfaces) and back-end components (such as the OData service). The back-end and the front-end components are delivered in separate products and have to be installed in a system landscape that is enabled for SAP Fiori. Back-End Components Delivered with (Product SAP enhancement package 7 for SAP ERP 6.0 SPS 05 Version Stack) Front-End Components Delivered with (Product SAP Fiori for SAP ERP 1.0 SPS03 Version Stack) SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

For the app, the following software components must be available in your system landscape. These components are contained in the product SAP Fiori transactional apps for SAP ERP : Back-End/Front-End Server

Back-End/Front-End Component

Technical Name of Software Component Support Package Level

Back-end server

Back-end component

GBX02SAP 600

01

Front-end server

Front-end component

UIX02EAP 100

01

Required SAP Notes For Release Production Orders , the following SAP Note must be available: Back-End/Front-End Server

SAP Note Number

Description

Back-End

1931275

Fiori-App: “"Release Production Orders"” corrections

Implementation Tasks The following sections list tasks that have to be performed to implement the app. The tables contain the app-specific data required for these tasks:

Front-End Server: Activate OData Services

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 121 of 138

Component

Technical Name

OData Service (Version Number)

PP_PRODORDER_RELEASE_SRV

For more information about activating OData services, see Front-End Server: Activate OData Services.

Front-End Server: Activate UI5 Application Component

Technical Name

UI5 Application

PP_PRODORD_REL

For more information about how to activate the UI5 application (ICF service), see Front-End Server: Activate ICF Services of UI5 Application.

Front-End Server: Enable App for Access in SAP Fiori Launchpad There are several steps to be performed to enable the app for access in the SAP Fiori launchpad. You require the listed data to perform these steps. For more information about the steps to be performed, see Setup of Catalogs, Groups, and Roles in the SAP Fiori Launchpad. Component

Technical Name

Business Role

SAP_PP_BCR_PRODSUPERVISOR SAP_PP_BCR_WORKER

Business Catalog Group

SAP_PP_BCR_WORKER

Technical Role

SAP_PP_TCR_T

Technical Catalog

SAP_PP_TC_T

Front-End and Back-End Server: Assign Role with OData Service Authorization to Users To restrict access to OData services to specific users, you have to assign roles (including OData service authorization for the app) to your users. You have to make the assignment on the back-end and on the front-end server: On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can adjust this role according to your needs. On the front-end server, you can assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs. OData Service (Version Number)

PP_PRODORDER_RELEASE_SRV

Back-End Server: Delivered Authorization Role (PFCG Role) SAP_PP_PRODORD_REL_APP

Front-End Server: Authorization Role

Use an existing role or create a new one

For more information about authorization roles and assigned OData services, see Front-End Server: Assign Role with OData Service Authorization t and Back-End Server: Assign Role with OData Service Authorization to.

Prerequisites For Configuration Before you can use the app with your production order data, you must ensure the following: You have created one or several variants in the backend using transaction Create Variant for Production Order Selection (RPSPOR1). The variants must be assigned to a user in transaction Assign Variant for Production Order Selection to User (RPSPOR2).

More Information For general information about the user management concept in a SAP Fiori environment, see Users in ABAP Front-End System and Users in ABAP Back-End System.

1.32 Report Quality Issue With the transactional app Report Quality Issue , you can easily report quality issues (known in the back-end system as quality notifications) that occur in the premises of an organizational plant. You can use the app on a number of mobile devices and standalone systems. The app introduces a new approach for reporting quality issues on the fly and minimizes the need to contact other people in the quality management area to perform the task of quality notification reporting. Additionally, the app enables you to access all your quality issues regardless of the reporting source. The app pulls and displays all quality issues that were created in the system (either by using the transaction QM02 or reported on another instance of the same app). This improves the whole process of reporting and handling quality issues.

Key Features Report quality issues using various devices and platforms List reported quality issues

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 122 of 138

System Landscape Requirements Note This app is also available in a version for higher back-end releases. For more information, see SAP Help Portal at http://help.sap.com/fiori_products -> SAP Fiori for SAP ERP -> SAP Fiori for SAP ERP 1.0. The app consists of front-end components (such as the user interfaces) and back-end components (such as the OData service). The back-end and the front-end components are delivered in separate products and have to be installed in a system landscape that is enabled for SAP Fiori. Back-End Components Delivered with (Product SAP enhancement package 7 for SAP ERP 6.0 SPS 05 Version Stack) Front-End Components Delivered with (Product SAP Fiori for SAP ERP 1.0 SPS03 Version Stack) SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

Related Fiori Apps My Quality Tasks

Component for Customer Messages QM-QN-NM

More Information App History: Report Quality Issue App Implementation: Report Quality Issue App Extensibility: Report Quality Issue

1.32.1 App Implementation: Report Quality Issue System Landscape Requirements Before you start to implement the app, ensure that your system landscape has been set up to enable SAP Fiori. This also implies that the front-end and back-end components for your app are already available in this system landscape: SAP Fiori System Landscape Options

Configuration of Front-End Server

Setup of SAP Fiori System Landscape with ABAP Environment Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS Configuration of SAP Fiori Infrastructure

Back-End Components Delivered with (Product SAP enhancement package 7 for SAP ERP 6.0 SPS 05 Version Stack) Front-End Components Delivered with (Product SAP Fiori for SAP ERP 1.0 SPS03 Version Stack)

For the app, the following software components must be available in your system landscape. These components are contained in the product SAP Fiori transactional apps for SAP ERP : Back-End/Front-End Server

Back-End/Front-End Component

Technical Name of Software Component Support Package Level

Back-end server

Back-end component

GBX02EAP 600

01

Front-end server

Front-end component

UIX02EAP 100

01

Required SAP Notes For Report Quality Issue , the following SAP Notes must be available: Back-End/Front-End Server

SAP Note Number

Description

Front-end server

1949475

Corrections for Fiori App Report Quality Issues

Release Information Note

1931282

General Information: QM

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 123 of 138

Implementation Tasks The following sections list tasks that have to be performed to implement the Report Quality Issue app. The tables contain the app-specific data required for these tasks:

Front-End Server: Activate OData Services Component

Technical Name

OData Service (Version Number)

QM_NOTIF_SRV (1)

For more information about activating OData services, see Front-End Server: Activate OData Services.

Front-End Server: Activate UI5 Application Component

Technical Name

UI5 Application

UI_QM_CREATE

For more information about how to activate the UI5 application (ICF service), see Front-End Server: Activate ICF Services of UI5 Application.

Front-End Server: Enable App for Access in SAP Fiori Launchpad There are several steps to be performed to enable the app for access in the SAP Fiori launchpad. You require the listed data to perform these steps. For more information about the steps to be performed, see Setup of Catalogs, Groups, and Roles in the SAP Fiori Launchpad. Component

Technical Name

Semantic Object

QualityNotification

Business Role

SAP_QM_BCR_QUALITYENGINEER

Business Catalog

SAP_QM_BC_QUALITYENGINEER

Business Catalog Group

SAP_QM_BCG_QUALITYENGINEER

Technical Role

SAP_QM_TCR_T

Technical Catalog

SAP_QM_TC_T

LPD_CUST Role

UIAPQM01

LPD_CUST Instance

TRANSACTIONAL

Front-End and Back-End Server: Assign Role with OData Service Authorization to Users To restrict access to OData services to specific users, you have to assign roles (including OData service authorization for the app) to your users. You have to make the assignment on the back-end and on the front-end server: On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can adjust this role according to your needs. On the front-end server, you can assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs. OData Service (Version Number)

Back-End Server: Delivered Authorization Role (PFCG Role)

Front-End Server: Authorization Role

QM_NOTIF_SRV (1)

SAP_QM_REPORTQUALITYISSUE_APP

Use an existing role or create a new one

For more information about authorization roles and assigned OData services, see Front-End Server: Assign Role with OData Service Authorization t and Back-End Server: Assign Role with OData Service Authorization to.

Prerequisites for Implementation There are no prerequisites for implementation for the app.

Configuration Tasks The configuration of the Report Quality Issue app is controlled by Customizing activities that are available under Quality Management Fiori Apps for Quality Management . By default, the Customizing activities are delivered with predefined settings. However, you can check the settings in client 000 and adapt them as appropriate for your business case. To enable Report Quality Issue , you must perform the following configuration tasks: Configure the Assigned To field as optional. 1. Start Customizing and open the activity: Quality Management Quality Notifications Notification Creation Partners Define Partner Determination Procedures Define Partner Determination Procedure . 2. Select the Quality Management radio button and choose Change Partner . 3. Select the Q3 Internal ProbMessage partner determination procedure and then choose Functions in Determination Procedure . 4. For the Coordinator (user) entry, deselect the check box in the Partner Mandatory column. If you do not perform the configuration above, the Assigned To field remains mandatory and you cannot report a quality issue without filling it out. However,

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 124 of 138

technically this field is not required for the reporting of a quality issue and therefore it is not available during the initial quality issue reporting. Enable the attachment of images in quality issues. 1. Start Customizing and open the activity: Cross-Application Components Document Management Control Data Define Document Types 2. Choose the DOC document type and make sure that the following radio buttons are selected: Revision Level Assignment Version Assignment Archiving Authorization Make sure that the Default Application field is set to JPG . 3. Open the Define object links folder and make sure that a link to the object QMQEL exists.

.

Note The settings that you make at application level are stored in the cache of your Web browser. For this reason, if you want to discard these settings and revert to the default settings that come from Customizing, you should delete your browsing history and clear the cache of your Web browser.

More Information For general information about the user management concept in a SAP Fiori environment, see Users in ABAP Front-End System and Users in ABAP Back-End System.

1.32.2 App History: Report Quality Issue The Report Quality Issue app has been enhanced as follows:

SAP Fiori for SAP ERP 1.0 SPS 03 (Delivery Date 07/2014) No Changes

SAP Fiori for SAP ERP 1.0 SPS 02 (Delivery Date 05/2014) No changes.

SAP Fiori for SAP ERP 1.0 SPS 01 (Delivery Date 02/2014) New/Enhanced Key Features

No changes.

New Extensibility Options

Extensibility mechanisms are available in the app. For more information, see: App Extensibility: Report Quality Issue

SAP Fiori for SAP ERP 1.0 SPS 00 (Delivery Date 11/2013) Initial delivery.

1.33 Track Purchase Order With the transactional app 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.

Note Track Purchase Order does not support stock transfer and subcontracting orders. For more information about the functional differences between this app and the corresponding SAP ERP back-end functionality, see SAP Note 2037645. If you use Track Purchase Order on a smartphone and you display the items of a purchase order, the columns Ordered and Paid are not displayed due to the limited space available on smartphones.

Key Features The following documents can be displayed for each purchase order: Purchase requisition Goods receipt Invoice

System Landscape Requirements PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 125 of 138

The app consists of front-end components (such as the user interfaces) and back-end components (such as the OData service). The back-end and the front-end components are delivered with one product and have to be installed in a system landscape that is enabled for SAP Fiori. Product Version Containing Back-End and Front-End Components of the App Back-End Product Versions Supporting the App (Minimum Product Version Stack)

SAP Fiori principal apps for SAP ERP 1.0 SPS03

SAP ERP 6.0 SP15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher

SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment Based on SAP enhancement package 7 of SAP ERP 6.0 also possible: Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

Related Apps Approve Requisitions Approve Purchase Orders Approve Purchase Contracts Order from Requisitions

Component for Customer Incidents Track Purchase Order (MOB-UIA-MM-TPO)

More Information App History: Track Purchase Order App Implementation: Track Purchase Order App Extensibility: Track Purchase Order

1.33.1 App History: Track Purchase Order The Track Purchase Order app has been enhanced as follows:

SAP Fiori principal apps for SAP ERP 1.0 SPS03 (Delivery Date 07/2014) No changes.

SAP Fiori principal apps for SAP ERP 1.0 SPS02 (Delivery Date 05/2014) New/Enhanced Key Features

No changes.

New/Enhanced Extensibility Options

New extensibility options: Add fields to the purchase order details header Add fields to the Information area of the purchase order item details Add fields to the Information area of the purchase requisition details Add fields to the Information area of the goods receipt details Add fields to the Information area of the invoice receipt details

SAP Note for Technical Changes

1940542

SAP Fiori principal apps for SAP ERP 1.0 SPS01 (Delivery Date 02/2014) New/Enhanced Key Features

New key feature: You can now display purchase requisition details.

New/Enhanced Extensibility Options

No changes.

SAP Note for Technical Changes

1940542

SAP Fiori principal apps for SAP ERP 1.0 SPS00 (Delivery Date 01/2014) PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 126 of 138

Initial delivery.

1.33.2 App Implementation: Track Purchase Order System Landscape Requirements Before you start to implement the app, ensure that your system landscape has been set up to enable SAP Fiori. This also implies that the front-end and back-end components for your app are already available in this system landscape: SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment Based on SAP enhancement package 7 of SAP ERP 6.0 also possible: Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

Configuration of Front-End Server

Configuration of SAP Fiori Infrastructure

Back-End Product Versions Supporting the App (Minimum Product Version Stack)

Product Version Containing Back-End and Front-End Components of the App

SAP ERP 6.0 SP15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher SAP Fiori principal apps for SAP ERP 1.0 SPS03

For more information on the installation of the back-end and front-end components of the app, see Installation of Back-End Components and Installation of Front-End Components. For the app, the following software components must be available in your system landscape. These components are contained in the product SAP Fiori principal apps for SAP ERP : Back-End/Front-End Server

Back-End/Front-End Component

Technical Name of Software Component Support Package Level

Back-end server

Back-end component

SRA020 1.0

05

Front-end server

Front-end component

UIX01EAP 100

03

Required SAP Notes For Track Purchase Order , the following SAP Notes must be available: Back-End/Front-End Server

SAP Note Number

Description

Both

1940542

Central note for Track Purchase Order . All other important notes for this app are referenced from the central note.

Implementation Tasks The following sections list tasks that have to be performed to implement the Track Purchase Order app. The tables contain the app-specific data required for these tasks:

Front-End Server: Activate OData Services Component

Technical Name

OData Service (Version Number)

sra020_po_tracking_srv (1)

For more information about activating OData services, see Front-End Server: Activate OData Services.

Front-End Server: Activate UI5 Application Component

Technical Name

UI5 Application

MM_PURORD_TPO

For more information about how to activate the UI5 application (ICF service), see Front-End Server: Activate ICF Services of UI5 Application.

Front-End Server: Enable App for Access in SAP Fiori Launchpad There are several steps to be performed to enable the app for access in the SAP Fiori launchpad. You require the listed data to perform these steps. For more information about the steps to be performed, see Setup of Catalogs, Groups, and Roles in the SAP Fiori Launchpad. Component

Technical Name

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 127 of 138

Semantic Object

PurchaseOrder

Business Role

SAP_MM_BCR_Buyer_X1

Business Catalog

SAP_MM_BC_Buyer_X1

Business Catalog Group

SAP_MM_BCG_Buyer_X1

Technical Role

SAP_MM_TCR_T_X1

Technical Catalog

SAP_MM_TC_T_X1

LPD_CUST Role

UIX01MM

LPD_CUST Instance

TRANSACTIONAL

Front-End and Back-End Server: Assign Role with OData Service Authorization to Users To grant access to OData services to specific users, you have to assign roles (including OData service authorization for the app) to your users. You have to make the assignment on the back-end and on the front-end server: On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can adjust this role according to your needs. On the front-end server, you can assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs. OData Service (Version Number)

Back-End Server: Delivered Authorization Role (PFCG Role)

Front-End Server: Authorization Role

sra020_po_tracking_srv (1)

SAP_MM_PURORD_TPO_APP

Use an existing role or create a new one

For more information about authorization roles and assigned OData services, see Front-End Server: Assign Role with OData Service Authorization t and Back-End Server: Assign Role with OData Service Authorization to.

Prerequisites for Implementation Before implementing the Track Purchase Order app, you must ensure that the business users who will use the app have the authorizations required for tracking purchase orders in the SAP GUI.

More Information For general information about the user management concept in a SAP Fiori environment, see Users in ABAP Front-End System and Users in ABAP Back-End System.

1.33.3 App Extensibility: Track Purchase Order You can extend the Track Purchase Order app for different aspects. For this purpose, the following extensibility options are available: Add fields Add fields Add fields Add fields Add fields

to the purchase order details header to the Information area of the purchase order item details to the Information area of the purchase requisition details to the Information area of the goods receipt details to the Information area of the invoice receipt details

Add Fields to Purchase Order Details Header To add customer fields to the header of purchase order details, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

View

Extension Point

Design Time: Gateway Entity

Design Time: Extension Include (in DDIC Structure)

Runtime: Data Structure to Be Redefined

S3.view.app.xml

detailsHeader

PODetailedData

SRA020_S_PO_DETAILED_INCL SRA020_S_PO_DETAILED

Add Fields to Purchase Order Item Details To add customer fields to the Information area of the purchase order item details, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

View

Extension Point

Design Time: Gateway Entity

Design Time: Extension Include (in DDIC Structure)

POItem.view.app.xml

itemDetailsInformation

POItemDetailData

SRA020_S_PO_ITEM_DETAILED SRA020_S_PO_ITEM_DETAILED

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Runtime: Data Structure to Be Redefined

Page 128 of 138

_INCL

Add Fields to Purchase Requisition Details To add customer fields to the Information area of the purchase requisition details, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

View

Extension Point

PR_Factsheet.view.app.xml factSheetInformation

Design Time: Gateway Entity

Design Time: Extension Include (in DDIC Structure)

Runtime: Data Structure to Be Redefined

PRFactsheet

SRA020_S_PR_ITEM_DATA_INC SRA020_S_PR_ITEM_DATA L

Add Fields to Goods Receipt Details To add customer fields to the Information area of the goods receipt details, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

View

Extension Point

Design Time: Gateway Entity

Design Time: Extension Include (in DDIC Structure)

GoodReceipt.view.app.xml

goodsReceiptInformation

GoodsReceiptHeader

SRA020_S_GOODS_RECEIPT_HD SRA020_S_GOODS_RECEIPT_HD R_INCL

Runtime: Data Structure to Be Redefined

R

Add Fields to Invoice Receipt Details To add customer fields to the Information area of the invoice receipt details, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

View

Extension Point

Design Time: Gateway Entity

Design Time: Extension Include (in DDIC Structure)

Runtime: Data Structure to Be Redefined

InvoiceReceipt.view.app.x invoiceReceiptInformation InvoiceHeader

SRA020_S_INVOICEHEADER_IN SRA020_S_INVOICEHEADER

ml

CL

Further Extensibility Entities Business Add-Ins (BAdIs) The following BAdIs are available for extensibility purposes: SRA020_PO_TRACKING_MPC You can use this BAdI to enhance the entities of the sra020_po_tracking_srv Gateway service, for example, to add your own fields. For more information, see the BAdI documentation and the example implementation. SRA020_PO_TRACKING_DPC You can use this BAdI to enhance the purchase order data that is retrieved from the back-end system. You can also use it to display pictures of supplier contacts in supplier fact sheets. For more information, see the BAdI documentation and the example implementation. The above listed BAdIs are available in Customizing for Materials Management under

Purchasing

Purchase Orders

Track Purchase Order App

.

UI Controller Hooks To plug in and execute custom code, the following hooks are available in the controller code: Controller

Hook

Use

S2.controller.js

extHookOnPOListReceived

Allows you to check and change the data in the list of purchase orders.

For more information about UI controller hooks, see UI Controller Hooks.

More Information For a general description of the extensibility options and procedures of Fiori apps, see Extensibility.

1.34 Track Sales Orders

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 129 of 138

With the transactional app Track Sales Orders , you can you can track or display sales orders on field interactively on desktop, tablet, and mobile platforms.

Key Features Display sales orders for assigned customers View sales orders aggregated by purchase order numbers Search for sales orders Display sales order items and their status Display delivery schedules and their status

System Landscape Requirements The app consists of front-end components (such as the user interfaces) and back-end components (such as the OData service). The back-end and the front-end components are delivered in separate products and have to be installed in a system landscape that is enabled for SAP Fiori. Back-End Components Delivered with (Product Version Stack)

Front-End Components Delivered with (Product Version Stack)

SAP ERP 6.0 SP15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher SAP Fiori principal apps for SAP ERP 1.0 SPS02

SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

Component for Customer Incidents MOB-UIA-SD-TSO (Track Sales Orders)

More Information App History: Track Sales Orders App Implementation: Track Sales Orders App Extensibility: Track Sales Orders

1.34.1 App History: Track Sales Orders The Track Sales Orders app has been enhanced as follows:

SAP Fiori for SAP ERP 1.0 SPS03 (Delivery Date 07/2014) New/Enhanced Key Features

No change

SAP Note for Technical Changes

1942942

SAP Fiori for SAP ERP 1.0 SPS02 (Delivery Date 05/2014) New/Enhanced Key Features

New: Incoterms Incoterms display in the Item details section of the Track Sales Order app. Multiple Document Types You can view sales orders of different document types.

New/ Changed Extensibility Details

New: Extension points are available for the following: List Item Sales Order Header details Item Column Header Item Column Value Item Level details For more information, see App Extensibility: Track Sales Orders.

New/ Changed Implementation Details

The following activity is available for customizing purposes for Sales and Distribution under Track Sales Order : Additional Sales Order Document Types

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 130 of 138

You can configure multiple document types in addition to the standard sales order document type. For more information, see App Implementation: Track Sales Orders. SAP Note for Technical Changes

1942942

SAP Fiori for SAP ERP 1.0 SPS01 (Delivery Date 02/2014) New/Enhanced Key Features

Enhanced: Potential access issue to the Track Sales Order app via the Launchpad is fixed. You can view more than 100 list items.

New/Changed Extensibility Details

New: OData extensibility You can add back-end extensibility to OData services. Extension points You can add front-end extensibility. The following BAdIs are available for extensibility purposes in Customizing for Sales and Distribution under Track Sales Order : BAdI: Extending the Sales Order Scheduled Item You can use this BAdI to populate custom fields or extend the business functionality in the Scheduled Items section of the app. BAdI: Extending the Sales Order Item You can use this BAdI to populate custom fields or extend the business functionality in the Item section of the app. BAdI: Extending the Sales Order Header You can use this BAdI to populate custom fields or extend the business functionality in the Header section of the app.

SAP Note for Technical Changes

1942942

SAP Fiori for SAP ERP 1.0 SPS 00 (Delivery Date 11/2013) Initial delivery.

1.34.2 App Implementation: Track Sales Orders System Landscape Requirements Before you start to implement the app, ensure that your system landscape has been set up to enable SAP Fiori. This also implies that the front-end and back-end components for your app are already available in this system landscape: SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment Based on SAP enhancement package 7 of SAP ERP 6.0 also possible: Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

Configuration of Front-End Server

Configuration of SAP Fiori Infrastructure

Back-End Product Versions Supporting the App (Minimum Product Version Stack)

Product Version Containing Back-End and Front-End Components of the App

SAP ERP 6.0 SP15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher SAP Fiori principal apps for SAP ERP 1.0 SPS03

For more information on the installation of the back-end and front-end components of the app, see Installation of Back-End Components and Installation of Front-End Components. For the app, the following software components must be available in your system landscape. These components are contained in the product SAP Fiori principal apps for SAP ERP : Back-End/Front-End Server

Back-End/Front-End Component

Technical Name of Software Component Support Package Level

Back-end server

Back-end component

SRA018 1.0

04

Front-end server

Front-end component

UIX01EAP 100

03

Required SAP Notes For Track Sales Order, the following SAP Note must be available:

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 131 of 138

Back-End/Front-End Server

SAP Note Number

Description

Back-End and Front-End Server

1942942

Release Note for the ERP SD FIORI application - Track Sales Orders

Implementation Tasks The following sections list tasks that have to be performed to implement the Track Sales Orders app. The tables contain the app-specific data required for these tasks:

Front-End Server: Activate OData Services Component

Technical Name

OData Service (Version Number)

SRA018_SO_TRACKING_SRV

Front-End Server: Activate UI5 Application Component

Technical Name

UI5 Application

SD_SO_MON

Front-End Server: Enable App for Access in SAP Fiori Launchpad There are several steps to be performed to enable the app for access in the SAP Fiori launchpad. You require the listed data to perform these steps. Component

Technical Name

Semantic Object

SalesOrder

Business Role

SAP_SD_BCR_FIELDSALESREP_X1

Business Catalog

SAP_SD_BC_FIELDSALESREP_X1

Business Catalog Group

SAP_SD_BCG_FIELDSALESREP_X1

Technical Role

SAP_SD_TCR_T_X1

Technical Catalog

SAP_SD_TC_T_X1

LPD_CUST Role

UIX01SD

LPD_CUST Instance

TRANSACTIONAL

Front-End and Back-End Server: Assign Role with OData Service Authorization to Users To restrict access to OData services to specific users, you have to assign roles (including OData service authorization for the app) to your users. You have to make the assignment on the back-end and on the front-end server: On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can adjust this role according to your needs. On the front-end server, you can assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs. OData Service (Version Number)

Back-End Server: Delivered Authorization Role (PFCG Role)

Front-End Server: Authorization Role

SRA018_SO_TRACKING_SRV

SRA018:SAP_SD_SO_MON_APP

SAP_SD_BCR_FIELDSALESREP_X1

Configuration Tasks To enable Track Sales Orders , perform these configuration tasks. Ensure that an employee master record is created and check the following: You have implemented SAP ERP HCM and maintained your employees in the HCM personnel records. The employee personnel record has the infotype Communication, with a subtype of System User Name (SY-UNAME) (Infotype 0105, Subtype 0001) If you have not implemented SAP ERP HCM, implement the Sales and Distribution configuration around Use Sales Employees with HR (Tcode: PULT). This IMG setting copies the appropriate HCM tables from the 000 Client and allows the setup of the Employee Record with the Infotype Communication and a Subtype of System User Name (SY-UNAME). (Infotype 0105, Subtype 0001).

Note It associates the USERID of the employee with the personnel number assigned as a partner function sales employee in the customer master. Call transaction SIMGH and open the Track Sales Orders node to configure user information using the following parameters: Document Type (DOCTYPE) By default, the app uses the standard order document type (technical key TA resp. OR). Order Period (ORDPERIOD) This defines how many days into the past sales orders are retrieved. The suggested value is 30 days. Search Period (SEAPERIOD) This defines how many days into the past a search must look for sales orders that match the search criteria. The suggested value is 90 days.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 132 of 138

Ship To Party (SHIP_TO/PARTNER_ROLE) This defines which partner role in the customer master is used for the ship-to party. The suggested value is WE. Forwarding Agent (FORWARDING_AGENT/PARTNER_ROLE) This defines which partner role in the customer master is used for the forwarding agent. The suggested value is SP. Implement the Define Additional Sales Order Document Types customizing to specify document types other than the default Standard Order (TA) type. Implement the BAdI: Customer Association to Employee to associate employees with specific customers.

More Information For general information about the user management concept in a SAP Fiori environment, see Users in ABAP Front-End System and Users in ABAP Back-End System.

1.34.3 App Extensibility: Track Sales Orders You can extend Track Sales Orders according to your business needs for different aspects. For this purpose, the following extensibility options are available: You can insert custom content to overwrite what is provided as a default inside the extension points. Extension points are inserted in the views of delivered standard applications.

Front-End and Back-End Extensibility Entities To add a customer field to the app, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

View

Extension Point

Design Time: Gateway Entity

S3.view.app.xml

extSOChangePaymentInfo

SRA018_SO_TRACKING_SRV/Sa SRA018_S_SO_HEADER

extSOChangeNotes

Design Time: Extension Include (in DDIC Structure)

lesOrder

Runtime: Superclass/ Method to Be Redefined Superclass: CL_SRA018_SO_TRACKING_DPC _EXT Method: SALESORDERS_GET_ENTITYSET

extSOHeaderDetails

ListItemTemplate.fragment extSalesOrderListAttribut .xml

es extSOChangeAttachments

SRA018_SO_TRACKING_SRV/At SRA018_S_SO_ATTACH tachment

Superclass: CL_SRA018_SO_TRACKING_DPC _EXT Method: ATTACHMENTS_GET_ENTITYSET

CSRA018_SO_TRACKING_SRV/C SRA018_S_CONTACT_ODATA ontact

Superclass: CL_SRA018_SO_TRACKING_DPC _EXT Method: CONTACTS_GET_ENTITYSET

CSRA018_SO_TRACKING_SRV/C SRA018_S_SO_COUNTRY ountry

Superclass: CL_SRA018_SO_TRACKING_DPC _EXT Method: COUNTRIES_GET_ENTITYSET

CSRA018_SO_TRACKING_SRV/C SRA018_S_SO_CUSTOMER ustomer

Superclass: CL_SRA018_SO_TRACKING_DPC _EXT Method: CUSTOMERS_GET_ENTITYSET

S4.view.app.xml

extSOItemLevelInfoDetails CSRA018_SO_TRACKING_SRV/O SRA018_S_SO_ITEM

S3.view.app.xml

extSOItemColumnHeader

rderItem

Superclass: CL_SRA018_SO_TRACKING_DPC _EXT Method: ORDERITEMS_GET_ENTITYSET

extSOItemColumnValue

CSRA018_SO_TRACKING_SRV/S SRA018_S_SO_SCHEDITEM cheduledItem

Superclass: CL_SRA018_SO_TRACKING_DPC _EXT Method: SCHEDULEDITEMS_GET_ENTITY SET

Additional Extensibility Entities

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 133 of 138

Business Add-Ins (BAdIs) The following BAdIs are available for extensibility purposes in Customizing for Sales and Distribution . Use transaction SIMGH to open the Orders”

“Track Sales

node:

BAdI: Extending the Sales Order Header You can use this BAdI to populate custom fields for the sales order header. BAdI: Extending the Sales Order Item You can use this BAdI to populate custom fields for the sales order item. BAdI: Extending the Sales Order Scheduled Item You can use this BAdI to populate custom fields for the scheduled sales order item.

Extension Includes In addition to the extension includes described above, the following extension includes are available: DDIC

Extension Include

Use

SRA018_S_SO_HEADER

SRA018_S_SO_HEADER_INCL

Allows you to add new fields for the sales order header

SRA018_S_SO_ATTACH

SRA018_S_SO_ATTACH_INCL

Allows you to add new fields for sales order attachments

SRA018_S_CONTACT_ODATA

SRA018_S_CONTACT_CI_INCL

Allows you to add new fields for contacts

SRA018_S_SO_COUNTRY

SRA018_S_SO_COUNTRY_INCL

Allows you to add new fields for countries

SRA018_S_SO_CUSTOMER

SRA018_S_SO_CUSTOMER_INCL

Allows you to add new fields for customers

SRA018_S_SO_ITEM

SRA018_S_SO_ITEM_INCL

Allows you to add new fields for sales order items

SRA018_S_SO_SCHEDITEM

SRA018_S_SO_SCHEDITEM_INCL

Allows you to add new fields for scheduled sales order items

More Information For a general description of the extensibility options and procedures of Fiori apps, see Extensibility.

1.35 Track Shipments With the transactional app Track Shipments , you can provide precise shipment information to your customers quickly and easily from your desktop or mobile device.

Key Features Browse a list of shipments to a customer assigned to the sales representative. See the estimated shipment date and current status at a glance. Filter shipments by status (shipped, scheduled, overdue), or search for all shipments to a specific customer. Display details for a shipment (incl. shipment date, carrier, freight charges, item details, contacts). Click the tracking number for shipped items to go directly to the carrier’s tracking Web site.

System Landscape Requirements The app consists of front-end components (such as the user interfaces) and back-end components (such as the OData service). The back-end and the front-end components are delivered with one product and have to be installed in a system landscape that is enabled for SAP Fiori. Product Version Containing Back-End and Front-End Components of the App Back-End Product Versions Supporting the App (Minimum Product Version Stack)

SAP Fiori System Landscape Options

SAP Fiori principal apps for SAP ERP 1.0 SPS03

SAP ERP 6.0 SP15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher Setup of SAP Fiori System Landscape with ABAP Environment Based on SAP enhancement package 7 of SAP ERP 6.0 also possible: Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

Component for Customer Incidents UI5 Track Shipments (MOB-UIA-SD-TSH).

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 134 of 138

More Information App History: Track Shipments App Implementation: Track Shipments App Extensibility: Track Shipments

1.35.1 App History: Track Shipments The Track Shipments app has been enhanced as follows:

SAP Fiori principal apps for SAP ERP 1.0 SPS 03 (Delivery Date 07/2014) New/Enhanced Key Features

No new or enhanced key features

New/Changed Implementation Details

No new or changed implementation details

New/Enhanced Extensibility Options

The UI controller hook extHookOnDetailDataReceived can be used to change or check detail data.

SAP Note for Technical Changes

2013352

SAP Fiori principal apps for SAP ERP 1.0 SPS 02 (Delivery Date 05/2014) New/Enhanced Key Features

No new or enhanced key features

New/Changed Implementation Details

OData Services are enabled to provide extensibility

New/Enhanced Extensibility Options

ListDetail Additional information for a shipment can be displayed on the shipment list ShipmentDetail Additional information for a shipment can be displayed

SAP Note for Technical Changes

1979388 1972124

SAP Fiori principal apps for SAP ERP 1.0 SPS 01 (Delivery Date 02/2014) No changes.

SAP Fiori principal apps for SAP ERP 1.0 SPS 00 (Delivery Date 11/2013) Initial delivery.

1.35.2 App Implementation: Track Shipments System Landscape Requirements Before you start to implement the app, ensure that your system landscape has been set up to enable SAP Fiori. This also implies that the front-end and back-end components for your app are already available in this system landscape: SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment Based on SAP enhancement package 7 of SAP ERP 6.0 also possible: Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS

Configuration of Front-End Server Back-End Product Versions Supporting the App (Minimum Product Version Stack)

Product Version Containing Back-End and Front-End Components of the App

Configuration of SAP Fiori Infrastructure SAP ERP 6.0 SP15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher SAP Fiori principal apps for SAP ERP 1.0 SPS03

For more information on the installation of the back-end and front-end components of the app, see Installation of Back-End Components and Installation of Front-End Components. For the app, the following software components must be available in your system landscape. These components are contained in the product SAP Fiori principal

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 135 of 138

apps for SAP ERP : Back-End/Front-End Server

Back-End/Front-End Component

Technical Name of Software Component Support Package Level

Back-end server

Back-end component

SRA019 1.0

03

Front-end server

Front-end component

UIX01EAP 100

03

Required SAP Notes For Track Shipments , the following SAP Note must be available: Back-End/Front-End Server

SAP Note Number

Description

Back-End Server

1931055

Employee Assignment to Sold-to Party

Implementation Tasks The following sections list tasks that have to be performed to implement the Track Shipments app. The tables contain the app-specific data required for these tasks:

Front-End Server: Activate OData Services Component

Technical Name

OData Service (Version Number)

SRA019_SHIPMENT_TRACKING_SRV (1)

For more information about activating OData services, see Front-End Server: Activate OData Services.

Front-End Server: Activate UI5 Application Component

Technical Name

UI5 Application

LE_SHIP_MON

For more information about how to activate the UI5 application (ICF service), see Front-End Server: Activate ICF Services of UI5 Application.

Front-End Server: Enable App for Access in SAP Fiori Launchpad There are several steps to be performed to enable the app for access in the SAP Fiori launchpad. You require the listed data to perform these steps. For more information about the steps to be performed, see Setup of Catalogs, Groups, and Roles in the SAP Fiori Launchpad. Component

Technical Name

Business Role

SAP_LE_BCR_TranspSpecialist_X1

Business Catalog

SAP_LE_BC_TranspSpecialist_X1

Business Catalog Group

SAP_LE_BCG_TranspSpecialist_X1

Technical Role

SAP_LE_TCR_T_X1

Technical Catalog

SAP_LE_TC_T_X1

LPD_CUST Role

UIX01LE

LPD_CUST Instance

TRANSACTIONAL

Front-End and Back-End Server: Assign Role with OData Service Authorization to Users To restrict access to OData services to specific users, you have to assign roles (including OData service authorization for the app) to your users. You have to make the assignment on the back-end and on the front-end server: On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can adjust this role according to your needs. On the front-end server, you can assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs. OData Service (Version Number)

Back-End Server: Delivered Authorization Role (PFCG Role)

Front-End Server: Authorization Role

SRA019_SHIPMENT_TRACKING_SRV (1)

SAP_LE_SHIP_MON_APP

Use an existing role or create a new one

For more information about authorization roles and assigned OData services, see Front-End Server: Assign Role with OData Service Authorization t and Back-End Server: Assign Role with OData Service Authorization to.

Configuration Tasks To enable Track Shipments , you must perform the following configuration tasks:

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 136 of 138

Define URL for Carriers In this Customizing activity, you define the URL for the carrier (vendor). It is used to provide a hyperlink from the tracking number. This Customizing activity is available in Customizing for Logistics Execution under Transportation Track Shipments .

More Information For general information about the user management concept in a SAP Fiori environment, see Users in ABAP Front-End System and Users in ABAP Back-End System.

1.35.3 App Extensibility: Track Shipments You can extend Track Shipments according to your business needs for different aspects. For this purpose, the following extensibility options are available: View

Extension Point

Use

ObjectListItemTemplate.fragment.xml

ListDetail

Customer Extension Point shipmentListDetail: Here additional info for a shipment can be displayed on the shipment list

S3.view.app.xml

ShipmentDetail

Customer Extension Point shipmentDetail: Here additional information for a shipment can be displayed

Add Customer Field To add a customer field to Track Shipments , the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs: UI

Back End/ABAP

Optional

View

Extension Point

Design Time: Gateway Entity

Design Time: Extension Include (in DDIC Structure)

BAdI/method to be implemented

Runtime: Superclass/ Method to Be Redefined

ObjectListItemTempla

ListDetail

SRA019_SHIPMENT_TRAC

SRA019_S_LIST_INCL

KING_SRV/

BAdI: SRA019_SHIPMENT_TRA_

Superclass: CL_SRA019_SHIPMENT_TR

ShipmentList

DPC

A_DPC_EXT

Method: IF_SRA019_SHIPMENT_T

Method: SHIPMENTLISTSET_GET_E

RA_DPC~

NTITYSET

te.fragment.xml

CHANGE_SHIPMENT_LIST _APT S3.view.app.xml

ShipmentDetail

SRA019_SHIPMENT_TRAC

SRA019_S_SHIP_DETAIL

KING_SRV/

_INCL

ShipmentDetail

BAdI: SRA019_SHIPMENT_TRA_

Superclass: CL_SRA019_SHIPMENT_TR

DPC

A_DPC_EXT

Method: IF_SRA019_SHIPMENT_T

Method: SHIPMENTDETAILSE_GET_

RA_DPC~

ENTITY

CHANGE_SHIPMENT_DETA ILS_API

Business Add-Ins (BAdIs) The following BAdIs are available for extensibility purposes: BD_SRA019_FREIGHT_CHARGE You can use this BAdI to retrieve the freight charge for a given shipment. It is called when the user executes the OData service to retrieve the header details for the Track Shipments application. BD_SRA019_IMG_RETRIEVER You can use this BAdI to retrieve the images for partners. It is called when the user executes the OData service to retrieve the partner image for the Track Shipments application. BD_SRA019_USR_TO_CUSTOMER You can use this BAdI to implement a method for associating employees to customers. SRA019_SHIPMENT_TRA_DPC You can use this BAdI to change the shipment data that is retrieved from the back-end system and displayed on the user interface of the Track Shipments app. SRA019_SHIPMENT_TRA_MPC You can use this BAdI to enhance the entities (the OData model) of the SRA019_SHIPMENT_TRACKING SAP NetWeaver Gateway service of the Track Shipments app. This allows you to add your own fields. These BAdIs are available in Customizing for Logistics Execution under

Transportation

Track Shipments

.

UI Controller Hooks To plug in and execute custom code, the following hooks are available in the controller code: Controller

Hook

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Use

Page 137 of 138

S3.controller.js

extHookOnDetailDataReceived

Allows you to check and change the shipment detail data.

For more information about UI controller hooks, see UI Controller Hooks.

More Information For a general description of the extensibility options and procedures of Fiori apps, see Extensibility.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 138 of 138