SAP Offline Word Templatesapidp/... · Web viewSAP Offline Word Template Keywords Template Last...

Building Block Configuration GuideSAP Fiori apps rapid-deployment solutionDocument Version: 2.0 – 2016-01-15

CUSTOMER

Deployment of SAP Fiori Transactional Apps (MF1)

Typographic ConventionsType Style Description

Example Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options.Textual cross-references to other documents.

Example Emphasized words or expressions.

EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.

Example Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.

Example Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example> Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

EXAMPLE Keys on the keyboard, for example, F2 or ENTER .

Deployment of SAP Fiori Transactional Apps (MF1)Table of Contents

CUSTOMER© 2016 SAP SE or an SAP affiliate company. All rights

reserved. 2

Document HistoryVersion Date Change

1.0 2015-07-06 First version

1.1 2015-10-13 Chapter 4.2 adapted (my Inbox app included)

2.0 2016-01-15 General UpdatesChapter 'Transportation' addedChapter 'App Activation Tool' added



reserved. 3

Table of Contents1 Purpose

2 Generic Configuration for Transactional Apps2.1 Settings in the SAP Gateway System

3 App-Specific Configuration for SAP Fiori Transactional Apps3.1 Get Technical Information3.2 Assign the Backend Role for the User3.3 App Activation Tool3.4 Activate OData Service

3.4.1 Automated Activation with Task Lists3.4.2 Manual Activation

3.5 Activate UI Services3.5.1 Automated Activation with Task Lists3.5.2 Manual Activation

3.6 Assign a User to the SAP Fiori Launchpad3.7 Running an Application Standalone

4 Additional App-Specific Configuration4.1 Generic Settings for Manager-Role Applications

4.1.1 Create System Alias for Backend Workflow in the SAP Gateway System4.1.2 Activation of OData Service in SAP Gateway

4.2 My Inbox App4.2.1 Configure Task Decisions4.2.2 Define an Approval Scenario4.2.3 Assign the App in the Launchpad4.2.4 Implement BAdI for Task Outcomes

4.3 Additional Configuration Steps for SAP Fiori Apps for SAP CRM4.3.1 My Opportunities4.3.1.1 Define Text Determination Procedure for My Opportunities4.3.1.2 Define Settings for My Opportunities4.3.2 My Leads4.3.2.1 Define Text Determination Procedure for Leads4.3.2.2 Virus Scan4.3.3 My Tasks4.3.3.1 Define Settings for My Tasks4.3.4 My Appointments4.3.4.1 Define Settings for My Appointments

4.4 Report Quality Issue / My Quality Tasks4.4.1 Configuration in the SAP Back-End System for Report Quality Issue4.4.2 Configuration in the Back-End System for My Quality Tasks

4.5 Additional Configuration Steps for SAP Fiori PP-MRP Apps4.5.1 Setup RFC Connection SAP_ERP_PP

4.6 Adapting the Business Logic in the Backend System



reserved. 4

5 SAP Fiori Launchpad5.1 Access the SAP Fiori Launchpad5.2 Access the Launchpad Designer5.3 Change Background Image for SAP Fiori Launchpad Logon Page5.4 Adapting the Logout Page in the SAP Fiori Launchpad

6 Transportation

7 Further Information Resources



reserved. 5

1 PurposeThe purpose of this document is to describe the steps required to configure transactional apps end-to-end.The document covers the following topics:

1. Generic configuration for transactional apps.2. App-specific configuration: Implementation walkthrough example with the SAP Fiori apps

reference library.3. Additional app-specific configuration.4. Troubleshooting.

Deployment of SAP Fiori Transactional Apps (MF1)Further Information Resources


reserved. 6

2 Generic Configuration for Transactional Apps

Prerequisites

You have carried out the installation of SAP Gateway completely.

NoteFind the steps to install SAP Gateway in the Package Configuration Guide of this RDS package.

2.1 Settings in the SAP Gateway System

NoteSee further important settings outlined in the SAP Fiori Technical Foundation Configuration guide (EE0) included in this RDS package that are mandatory for the configuration of SAP Fiori transactional apps, for example:

o Basic Configurationo Creating Trusted Connection from SAP System to SAP Gatewayo Add Backend Systemo Creating System Alias on Gatewayo Activating the SAP Gateway systemo Setting up the Fiori Launchpad and Launchpad Designer



reserved. 7

3 App-Specific Configuration for SAP Fiori Transactional Apps

Purpose

Deployment Options:In this section, the configuration steps to activate an SAP Fiori transactional application are described. There are three different alternatives how to activate the required OData and UI Services which are all described in this document. Each alternative has its advantages and you can choose and decide yourself which way to go:1. Automated Activation: Using Task Lists you can activate all required services in a single step once

you have all required metadata at hand. Choose this way if you need to activate a huge number of apps.

2. Manual Activation: All required steps are described one-by-one. You can use this way either as trouble shooting, to check the configuration or in case you implement only a small amount of Fiori apps.

3. Using the App Activation Tool: This is a Fiori app itself delivered by SAP. Once configured, it provides you a Fiori UI to activate the OData and UI Services for Transactional Apps and Factsheets. This app provides a comprehensive overview on the activated services. You need to install an additional Add On in the used SAP Frontend Server and do some quick configuration. This is a very helpful tool if you deploy a large number of apps being connected to multiple Backend Systems (since the app displays what systems the OData service is connected to).

Example Walk Through:Here, we use the SAP Fiori (ERP) app Create Sales Orders as an example. All the other apps are configured likewise – using the respective technical metadata available from the SAP Fiori apps reference library.

NoteSome apps require additional configuration steps, for example, certain manager-role based apps need workflow services to be activated. See the details in chapter “Additional App-Specific Configuration”.

Prerequisites

Make sure that the following prerequisites are fulfilled: o You have set up the system landscape and checked all the software requirements. o You have checked the RDS-specific SAP Note for further information. Find the link on the Step-

by-Step Guide.o You have checked that all additionally required (app-specific) SAP Notes have been

implemented. Using the Fiori apps reference library you can navigate to the respective app-specific content to find additional information on SAP Notes.



reserved. 8

http://www.sap.com/fiori-apps-library


o The required users have been generated in the SAP system and SAP Gateway system. The users in the SAP system and Gateway system must be identical.

NoteFor more information on SAP Fiori in general, see the SAP help portal: http://help.sap.com/fiori.

3.1 Get Technical Information1. Access the SAP Fiori apps reference library. 2. The SAP Fiori apps reference library provides key information for each app. Access it via the

following link:

Link http://www.sap.com/fiori-apps-library3. Go to the information page for the Create Sales Orders app.4. On the App Details view, choose Implementation Information Configuration.5. Note down the following technical details you need for the configuration steps to come:

Section under Configuration Technical Detail

OData Services → Back-End Authorization Role (PFCG)

SAP_SD_SO_CRE_APP

OData Services → OData Service SRA017_SALESORDER_CREATE_SRV

Technical Configuration → SAPUI5 Application SD_SO_CRE

Technical Configuration → PFCG role for Business Catalog

SAP_SD_BCR_FIELDSALESREP_X1

NoteThe implementation information covers the following details:

o Product Features: provides links to Help Portal pages on the Create Sales Orders appo Installation: provides software requirements information like the front-end and back-end

components as well as required SAP Notes o Configuration: lists app-specific data required to configure the appo Extensibility: provides information on extending the UI5 application the front-end server (for

example, extension points in views)o Support: provides the component for customer messages

3.2 Assign the Backend Role for the User 1. In the SAP back-end system, access the activity using one of the following navigation options:2. On the Role Maintenance screen, enter the Back-End Authorization Role you noted down before in

the Role field: SAP_SD_SO_CRE_APP.



reserved. 9



http://help.sap.com/fiori

IMG Menu Tools → Administration → User Maintenance → Role Administration → Roles

Transaction Code PFCG

3. Choose Change.4. On the Change Roles screen, choose the User tab page, input the user ID as backend user..5. Choose Save (Ctrl+S).

3.3 App Activation Tool

Purpose

The App Activation tool can be used to activate the required OData and UI Services. If you use the App Activation Tool, the following chapters 'Activate OData Service' and 'Activate UI Services' are fully covered and can be skipped during the implementation.The App Activation is an SAP Fiori App itself and some installation and configuration steps are required to get it running. These steps are described in this chapter in the Prerequisites section.The Procedure section describes the usage of the App Activation app itself.

Prerequisites

Make sure you perform the following activities: Install the SAPUIFT component on your SAP Frontend Server (find details in the 'Software and

Delivery Requirements' document). It requires SAP_UI (minimum 4.40 SP 10) software component and SAP_GWFND (minimum 7.40 SP9). In case your Frontend Server is on SAP Netweaver 7.31 you cannot use the App Activation.

Check the following two notes for the App Activation: 2147950 and 2146390. Call transaction VSCANPROFILE (Virus Scan Profile) and activate the virus scan profile

'/UI2/FT_CONF_UI/BOM_UPLOAD'.

CautionThe profile '/UI2/FT_CONF_UI/BOM_UPLOAD' should only be flagged as 'Active' or as 'Default

Profile'. Do not set both flags at the same time.

In order to assign the App Activation app to the Fiori Launchpad call transaction PFCG and assign the role SAP_FIORITECH_ADMIN to your user.

Activate the following OData services. Call transaction /IWFND/MAINT_SERVICE and activate the following services (in case you need assistance how to use this transaction check next chapter 'Activate OData Service - Manual Activation'):/UI2/FT_CONFIG_UI - choose system alias 'Local';/UI2/TRANSPORT - choose system alias 'Local' (should already be active).



reserved. 10

https://service.sap.com/sap/support/notes/2146390


Activate the following services in transaction SICF (in case you need assistance how to use this transaction check next chapter 'Activate UI Service - Manual Activation'):/SAP/BC/UI2/BOM_UPLOAD/SAP/BC/UI5_UI5/UI2/SAPCONFLP

NoteIn case you need additional information on the App Activation tool, check the following link: http://help.sap.com/saphelp_fiorierpx1_100/helpdata/en/b8/8eeb54a8056368e10000000a4450e5/content.htm

Procedure1. Download the required metadata from the SAP Fiori Apps Reference Library to your local drive or a

network drive. Use this link:https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/services/downloads/downloadServiceList.xsjs

2. Open the Fiori Launchpad. Find a generic link here or call transaction /n/UI2/FLP. 3. Open the App Activation tile .

4. Choose Update Reference Library in the lower left corner.5. The Upload SAP Fiori Apps Reference Library dialog shows up. Browse for the XML file you have

downloaded in the first step and choose Upload. The required metadata is now uploaded to your SAP Frontend Server.

6. Once a success message has been displayed, choose OK.7. Search for the catalog the apps you want to activate are in. Choose the respective Catalog.



reserved. 11

https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/services/downloads/downloadServiceList.xsjs

https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/services/downloads/downloadServiceList.xsjs

http://help.sap.com/saphelp_fiorierpx1_100/helpdata/en/b8/8eeb54a8056368e10000000a4450e5/content.htm



NoteThe app shows not only Transactional Apps but also the Factsheets which are assigned to a certain catalog. The Odata and UI Service of the Factsheets can be activated in the same way.

8. Choose the system of the SAP Backend System you want to connect to.9. You can now switch on the UI Services (Activate Application option) and the OData Service below

the UI Service either one by one going through the list or activate all apps and OData services for your catalog by choosing option Activate All. In the upcoming dialog you can change the Service Names in the way it meets your requirements, assign a Package and the required transport requests.



reserved. 12

10. Once activated a success message shows up. The result looks like this:

Result

You have now activated the required OData and UI Services. You can skip the following chapters 'Activate ODATA Service' and 'Activate UI Service'.

3.4 Activate OData Service

3.4.1 Automated Activation with Task Lists

Purpose

In this chapter, you perform ABAP system configuration tasks in an automated way by using predefined task lists for an easier and faster configuration.



reserved. 13

Preparation

You can download the required metadata for the task list using the SAP Fiori Apps Reference Library. Perform the following steps:1. Access the SAP Fiori apps reference library. 2. The SAP Fiori apps reference library provides key information for each app. Access it via the

following link:

Link http://www.sap.com/fiori-apps-library3. Search for Category by Product Version (Front-End)4. Choose the Front-End Component you are interested in, i.e. SAP Fiori principal apps 1.0 for SAP

ERP.5. You get a list of all apps which are part of the selected Front-End Component. Choose all the apps

you want to implement in this result list (in case you want to implement all apps choose:

6. Choose Aggregate in the lower left corner to get an aggregated view of your selection. Scroll down to section OData Services to see the list of the required OData services:

7. Choose Export list of OData Services. You have now downloaded a list 'oData Services.csv'8. Scroll to section ICF Nodes for SAPUI5 Applications to see the list of the required UI services.

Choose Export list of ICF Nodes to download the list 'ICF Nodes.csv' of required UI services for further usage.

You have now a list of OData Services and UI Services at hand which can be used for activation via task lists as described in the Procedure section.

NoteAll of the following automated configuration steps can be carried out manually, which is described in the next chapter.

Procedure1. Log on to your SAP ABAP system.2. Call the following transaction:

Transaction Code STC01



reserved. 14



3. On the Task Manager for Technical Configuration screen, insert SAP_GATEWAY_ACTIVATE_ODATA_SERV in the Task List field.

4. Choose Generate Task List Run (F8). The Maintain Task List Run screen is displayed

5. For the first line item (Define OData Services for Activation), select the checkbox in the Execute column.

6. Choose the Fill Parameters icon in the Parameter column.7. In the input field of the pop-up, insert Enter the OData services in the following format: <SERVICE

NAME><SPACE><VERSION>, for example, SRA017_SALESORDER_CREATE_SRV 1

NoteYou can paste in the list of OData services you have prepared in the Preparation section of this chapter.

8. Choose Continue. Make sure that there are green lights in the task log indicating a proper task setting and configuration.

9. On the Maintain Task List Run screen, select the checkbox for “Select System Alias for Activation” in the Execute column. Choose the Fill Parameters icon in the Parameter column.

10. On the Edit Variants screen, insert the SAP System Alias in the input field.11. Save and go back.12. On the Maintain Task List Run screen, select the checkbox for “Select OData Services for

Activation” in the Execute column. Choose the Fill Parameters icon in the Parameter column.13. On the Select to be activated OData services screen, select the checkboxes of the services to be

activated, for example SRA017_SALESORDER_CREATE_SRV.14. Save and go back.15. Choose Start/Resume Task List Run in Dialog (or in Background). Once the task list run has been

finished successfully, green lights appear in task log.

NoteBefore executing the task list, make sure that all Execute checkboxes are selected.

Result

You have successfully carried out the task list run SAP_GATEWAY_ACTIVATE_ODATA_SERV.



reserved. 15

3.4.2 Manual Activation

NoteIf you have already carried out the activation of OData services in an automated way with task lists, you can skip this step.

Procedure1. In the SAP Gateway system, access the activity using the following navigation options:

Transaction Code /IWFND/MAINT_SERVICE

IMG Menu SAP NetWeaver → Gateway→ OData Channel → Administration → General Settings →Activate and Maintain Services

2. On the Service Catalog screen, choose Add Service.3. On the Add Service screen, enter the System Alias that has been created when in the course of the

configuration in the SAP Gateway system. You can also use F4 help. 4. Enter the OData service: SRA017_SALESORDER_CREATE_SRV.5. Alternatively, you can also get a list of services available from the system. After step 3, you choose

Get Services. A list of services is displayed. From the services listed choose the OData service: SRA017_SALESORDER_CREATE_SRV.

6. Choose Enter.7. Select the service from the list.8. Choose Add selected services.9. In the Add Service pop-up, enter the name of the Package being used in the Package Assignment

field.10. Select Standard Mode in the ICF Node section.11. Select the Set current client as default client in ICF Node checkbox. 12. Choose Continue (Enter).

Assign your workbench and customizing requests and confirm the displayed messages.13. Confirm the information message that the metadata was loaded successfully.14. Choose Back.15. From the Service Catalog, select the record you have just created.16. Choose Gateway Client.17. Choose Execute (F8). 18. The HTTP Response is displayed and an XML-File shows up in the lower right corner. This indicates

that the Web Service is configured properly.

NoteFor Web Service calls, you must maintain authorization object S_SERVICE. You then assign the Web Service operations to a role in transaction PFCG.Find more information in this SAP Help Portal location.



reserved. 16

http://help.sap.com/saphelp_nw73ehp1/helpdata/en/63/ed7746b6044288928b1382232ec10a/content.htm

Note In case an error message shows up indicating that the http request failed then check the following:1. Does the trusted RFC connection work properly?2. Check in the Trust Manager (transaction strust) if the SSL certificates are set up properly so

the gateway system can communicate properly with the respective backend system.

NoteYou can double in transaction SICF if the service was activated. Perform the following steps:

19. In the SAP Gateway system, access the activity using the following navigation option:

Transaction Code SICF

20. Choose Execute (F8).21. Choose the following navigation path on the Maintain service screen:

Navigation Path default_host → sap → opu → odata → sap

22. The service SRA017_SALESORDER_CREATE_SRV is displayed and activated here.

3.5 Activate UI Services

3.5.1 Automated Activation with Task Lists

Purpose

In this chapter, you activate UI services in an automated way by using predefined task lists.

NoteAll of the following automated configuration steps can be carried out manually, which is described in the next chapter.

Procedure1. Log on to your SAP ABAP system2. Call the following transaction:



reserved. 17

Transaction Code STC01

3. On the Task Manager for Technical Configuration screen, insert SAP_BASIS_ACTIVATE_ICF_NODES in the Task List field.

NoteYou can paste in the list of UI Services 'ICF Nodes.csv' services you have prepared in the Preparation section of chapter Activate OData Service - Automated Activation with Task Lists.

4. Choose Generate Task List Run (F8). The Maintain Task List Run screen is displayed. 5. Select the checkbox in the Execute column for Activate HTTP Services (SICF). 6. Choose the Fill Parameters icon in the Parameter column.7. On the Activation of ICF Services screen, insert the path of the ICF service node (URL):

/sap/bc/ui5_ui5/sap/SD_SO_CRE

NoteThe virtual host is pre-defined (DEFAULT_HOST).If the Expand Flag is set, the subsequent nodes in the ICF service tree are also activated.If you want to insert multiple service paths/URLs, just copy and paste the list of URLs into the first line. All the URLs will be inserted into their own line – so as not to insert each URL separately.

8. Save and go back. 9. On the Maintain task List Run screen choose Start/Resume Task List Run in Dialog (or in

Background). Once the task list run has been finished successfully, green lights appear in task log.

NoteBefore executing the task list, make sure that all Execute checkboxes are selected.

Result

You have successfully carried out the task list run SAP_BASIS_ACTIVATE_ICF_NODES to activate single HTTP services according to transaction SICF.



reserved. 18

3.5.2 Manual Activation

NoteIf you have already carried out the activation of UI services in an automated way with task lists, you can skip this step.

Procedure1. In the SAP Gateway system, access the activity using the following navigation option:


2. Choose Execute (F8).3. For activating the UI5 Service (that is: SD_SO_CRE, see from above), choose the following

navigation path on the Maintain service screen:

Navigation Path default_host → sap → bc → ui5_ui5 → sap

4. Select the service SD_SO_CRE from the list.5. Right-click this service and choose Activate Service.

3.6 Assign a User to the SAP Fiori Launchpad1. In the SAP Gateway system, access the activity using one of the following navigation options:

IMG Menu Tools → Administration → User Maintenance → Role Administration → Roles

Transaction Code PFCG

2. On the Role Maintenance screen, enter the PFCG role for Business Catalog you noted down before in the Role field: SAP_SD_BCR_FIELDSALESREP_X1.

3. Choose Change.4. On the Change Roles screen, choose the User tab page.5. Insert the user ID/name in the user assignment area. 6. Choose Save (Ctrl+S).



reserved. 19

3.7 Running an Application Standalone

Use

Some SAP delivered Fiori apps can run in standalone mode. In this case the SAP Fiori Launchpad needs not to be accessed before calling the Fiori app. No target mapping and catalog assignment on front end server is required in this case (which is basically implied in the previous chapter 'Assign a User to the SAP Fiori Launchpad').However - the systems and the users must be fully configured to run the apps standalone.Find a list apps running standalone in this SAP Note 2103156 'Launching Fiori apps in standalone mode'.

Procedure

The URL to access the Fiori app in standalone mode must be assembled in this way:

http://<server>:<port>/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html?sap-client=<client>#Shell-runStandaloneApp?sap-ushell-SAPUI5.Component=<ComponentName>&sap-ushell-url=<Encoded-URL>&<AdditionalApplicationParameterKey>=<AdditionalApplicationParameterValue>

NoteParts of the URL need to be encoded by Java Script.

ExampleAs an example the URL to access the myOpportunity app is given:

https://dewdfgwp01089.wdf.sap.corp:44300/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html?sap-client=120#Shell-runStandaloneApp?sap-ushell-SAPUI5.Component=cus.crm.opportunity&sap-ushell-url=%252Fsap%252Fbc%252Fui5_ui5%252Fsap%252Fcrm_opprtnty&AccountId=422149

It can be derived like this:<Regular access to the SAP Fiori Launchpad>: https://dewdfgwp01089.wdf.sap.corp:44300/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html<Used SAP Client>: ?sap-client=120<run the app in standalone mode>: #Shell-runStandaloneApp<which SAP UI5 application to be called - can be checked in SE80 'BSP Application' search your app and check 'Components.js'>: ?sap-ushell-SAPUI5.Component=cus.crm.opportunity<encoded Java script URL for '/sap/bc/ui5_ui5/sap/crm_opprtnty' - basically that's the used UI service>: &sap-ushell-url=%252Fsap%252Fbc%252Fui5_ui5%252Fsap%252Fcrm_opprtnty<optional parameter to reduce the hits on the specified account ID>: &AccountId=422149



reserved. 20

https://dewdfgwp01089.wdf.sap.corp:44300/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html





NoteThere are additional parameters available. Check the documentation on the help portal for full details:http://help.sap.com/saphelp_uiaddon10/helpdata/en/53/7758e0deb0477386ea400c915073b3/frameset.htm



reserved. 21

http://help.sap.com/saphelp_uiaddon10/helpdata/en/53/7758e0deb0477386ea400c915073b3/frameset.htm

http://help.sap.com/saphelp_uiaddon10/helpdata/en/53/7758e0deb0477386ea400c915073b3/frameset.htm

4 Additional App-Specific Configuration Note

It is absolutely mandatory to check the SAP Fiori Help Portal pages for the individual apps (http://help.sap.com/fiori) if there are additional configuration steps required. The following chapter covers a selection of apps requiring additional settings. Due to the constant enhancement of the SAP Fiori apps, it might be the case that meanwhile more extra settings are required. In any case, check http://help.sap.com/fiori as an initial step and check the information provided.

4.1 Generic Settings for Manager-Role Applications

Use

There are manager- role Fiori applications - approval apps in particular - that require additional configuration steps.

NoteThere are more configuration steps required for the Approve Requests app. See the next chapter for more details.

4.1.1 Create System Alias for Backend Workflow in the SAP Gateway System

Use

An additional system Alias is required to access the workflows of the connected back-end systems in a proper way.

Procedure1. Access the activity using the following navigation options:

Transaction Code SPRO

IMG Menu SAP NetWeaver → Gateway→ OData Channel → Configuration → Connection Settings → SAP Gateway to SAP System → Manage SAP System Aliases



reserved. 22



2. Choose New Entries.3. Maintain the following values:

Field Name Entry Value

SAP System Alias <Backend Alias>_PGW

Description <Description>

Local GW Not selected

For Local App Selected

RFC Destination Trusted RFC Connection to the Backend System

Software Version /IWPGW/BWF

In case you are configuring a local gateway deployment you need to maintain the following values:


SAP System Alias Local_PGW

Description <Description>

Local GW Selected

For Local App Selected

RFC Destination <Create in SM59 an empty RFC destination of Connection Type 3 - and maintain the RDC Destination here>

Software Version /IWPGW/BWF

NoteA system Alias to the SAP back-end system should already exist with Software Version Default.

NoteDo not use any special characters in the system alias since this may cause problems once the Odata services are being called!

Result

Additional system alias for the Process Gateway was created.



reserved. 23

4.1.2 Activation of OData Service in SAP Gateway

Use

In this step, you activate gateway services in the Gateway system. The task processing service is a generic workflow service that calls then the application-specific services.

Prerequisites

Make sure that a system alias is created for your back-end system.

Procedure

See the details on how to perform this step in the chapter Gateway System: Activate OData Service in SAP Gateway, and use the following values:


System Alias <Backend Alias>_PGW

Technical Service Name Taskprocessing

NoteThe system Alias is the one for the Process Gateway that was created in the previous step.

4.2 My Inbox App The My Inbox app is a generic workflow approval app. It can be configured in a way that work items from multiple Workflows can be approved in this app. Hence it is not possible to describe in general how to configure this app. However – the relevant configuration steps are covered in a generic manner.

NoteCheck the Release Information Note for this app carefully.

SAP Note No Content Comments

2106212 Release Information Note for SAP Fiori My Inbox



reserved. 24


PrerequisitesYou have carried out the workflow-related tasks outlined in the configuration steps in chapter Generic Settings for Manager-Role Applications.

4.2.1 Configure Task Decisions

Use

In this step, you assign the decision options from your workflow task to the “approve” and “reject” options in the My Inbox application. This step is carried through in the SAP back-end system.

Procedure1. Access the transaction using the following navigation path:


IMG Menu SAP NetWeaver → SAP Gateway Service Enablement → Content → Workflow Settings → Maintain Task Names and Decision Options

2. Choose New Entries.3. On the Change View “Step Name”: Overview enter the following information:

Field Value

Workflow ID <Workflow Template ID>

Step ID <Step ID in workflow template>

Icon MIME Repository Path Leave blank.

Step Description <Enter the task name>

4. On Change View “Step Name”: Overview screen select <Workflow Template ID> row.

NoteIf the step type for the workflow task is User Decision, you can skip the next steps. In this case, the first decision option is always assigned to POSITIVE (approve), and the second option to NEGATIVE (reject).

5. On Dialog Structure, choose Decision Keys.6. Choose New Entries.7. In the table Decision Keys, enter the following information:

Field Value

Key <The decision key you want to use for approval>



reserved. 25

Field Value

Nature POSITIVE

NoteThe Decision Key corresponds to the Outcome Name for the task in the Workflow Builder.

8. Repeat the previous step with the following information:

Field Value

Key <The decision key you want to use for approval>

Nature NEGATIVE

NoteThe Decision Key corresponds to the Outcome Name for the task in the Workflow Builder.

9. Choose Save.

Result

You assigned the decision options to approve and rejects options.

4.2.2 Define an Approval Scenario

Use

In this step, you define an Approval Scenario for the myInbox app. This step is carried through in the SAP Gateway System.

Procedure1. Access the activity using the following transaction code:


IMG Path SAP NetWeaver → SAP Gateway Service Enablement → Content → Task Gateway→ Task Gateway Service → Scenario Definition.

2. Choose SAP Reference IMG or press F5.3. Execute Scenario Definition activity.4. Choose New Entries5. On the Scenario Definition table, enter the following information:



reserved. 26

Field Value

Scenario Identifier <Scenario Identifier>, that is: My Inbox

Scenario Display Name <Scenario Display Name>

Scenario Order 94

Technical Service Name /IWPGW/TASKPROCESSING

Version 1

EntitySet External Name Task

Property External Name TaskDefinitionID

Default Sort by Property <Name of field for default sort order>

Mass Action Checked

Quick Act Checked6. Choose Save.7. On the Change View “Scenario Definition”: Overview screen, select the My Inbox row.8. In the Dialog Structure, choose Assign Consumer Type to Scenario queries.9. Choose New Entries.10. In Assign Consumer Type to Scenario, enter the following values:

Task Gateway Consumer Type

MOBILE

TABLET

DESKTOP

11. Choose Save.12. Choose Back.

Result

After you have completed this procedure, you added a scenario, assigned a consumer type, and defined tasks.

4.2.3 Assign the App in the LaunchpadUseIn this step the tile created in the previous step is assigned the SAP Fiori Launchpad.

Procedure1. Start the SAP Fiori Launchpad using the URL:

http://<Gatewayhost>:<port>/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html2. Select button Show/hide Group panel in case the groups are hidden on the left-hand bar



reserved. 27

3. Select Open Catalog.4. The app my Inbox shows up in the list. Select the + button to add the app to your home screen.5. Choose the back arrow in the upper right corner.6. The app shows up in the My Home area.

ResultThe My Inbox Application can be accessed via the Launchpad.

4.2.4 Implement BAdI for Task OutcomesUseThis BAdI is located in the SAP back-end system. To handle a decision that is made on a task a BAdI needs to be implemented that contain the logic for it. The BAdI class needs the same logic for completing the task that is assigned in the dialog of the business workflow.

In a nutshell the BAdI implementation is required to map the results values when selecting ‘Approve’ or ‘Reject’ in the Fiori app to the logic (return values) required in the business workflow.

ProcedureFind the BAdI here:

Transaction Code Se18

Name /IWWRK/BADI_WF_BEFORE_UPD_IB

ResultThe My Inbox app returns the required decision values to complete the workflows properly.



reserved. 28

4.3 Additional Configuration Steps for SAP Fiori Apps for SAP CRM

4.3.1 My Opportunities

4.3.1.1 Define Text Determination Procedure for My Opportunities

Use

The text types to be used need to be configured in the text object. With the following setting the text type accepts changes and the texts are being logged.

Procedure 1. Access the activity using the following navigation options:


SAP Reference IMG Menu Customer Relationship Management Basic Functions Text Management Define Text Determination Procedure

2. Choose Object CRM_ORDERH.3. Choose Procedure.4. Select text determination procedure that has been specified for transaction type of opportunities

(OPSM0001).5. Select the Definition of Procedure view.6. Specify the value P (Log) in the Changes field for at least one text type.7. Choose Save.

4.3.1.2 Define Settings for My Opportunities

Use

Use this setting to define the transaction types for opportunities to be used. When you create opportunities using the My Opportunities app, the system allows you to choose only from those transaction types that have been defined in this Customizing activity.



reserved. 29



SAP Reference IMG Menu Customer Relationship Management Transaction Settings for Opportunities Define Settings for “My Opportunities” App

2. Create the following entry:

Field Value

Transaction Type

<insert the transaction types to be used>

3. Choose Save.

4.3.2 My Leads

4.3.2.1 Define Text Determination Procedure for Leads

Use

The text types to be used need to be configured in the text object. With the following setting the text type accepts changes and the texts are being logged.



SAP Reference IMG Menu Customer Relationship Management Basic Functions Text Management Define Text Determination Procedure

2. Choose Object CRM_ORDERH.3. Choose Procedure.4. Select text determination procedure that has been specified for transaction type of opportunities

(LEAD0001).5. Select the Definition of Procedure view.6. Specify the value P (Log) in the Changes field for at least one text type.7. Choose Save



reserved. 30

4.3.2.2 Virus Scan

UseSAP provides an interface for virus scanners to prevent manipulated or malicious files from damaging the system. To manage the interface and to find out which file types are checked or blocked, use the virus scan profiles.If you encounter problems with the virus scan profile, proceed as follows to switch off the virus scan.



SAP Reference IMG Menu

SAP NetWeaver Gateway oData Channel Administration General Settings Define Virus Scan Profile

2. Choose Virus Scan Switched Off.3. Choose Execute.

4.3.3 My Tasks

4.3.3.1 Define Settings for My Tasks

Use

Only tasks of the transaction type assigned in this customizing setting are displayed by the Fiori app. New tasks created via the Fiori app are of this transaction type.



SAP Reference IMG Menu Customer Relationship Management Transaction Settings for Activities Define Settings for “My Tasks” App




reserved. 31

Field Value

Transaction Type

< insert the transaction types to be used >

Text Type for Title

<for example A001>

Text Type for Note

<for example A001>

Noteo Transaction type

The app displays only those tasks from the CRM backend that have this transaction type. When a new task is created from the app, the system uses this transaction type.

o Text type that is used for the task titleThe text type you choose needs to be contained in the text determination procedure that has been assigned to the transaction type you entered above.

o Text type that is used for the notes sectionThe text type you choose needs to be contained in the text determination procedure that has been assigned to the transaction type you entered above.

3. Choose Save.

4.3.4 My Appointments

4.3.4.1 Define Settings for My Appointments

Use

Only appointments of the transaction type assigned in this customizing setting are displayed by the Fiori app. New appointments created via the Fiori app are of this transaction type.



SAP Reference IMG Menu Customer Relationship Management Transaction Settings for Activities Define Settings for “My Appointments” App




reserved. 32

Field Value

Transaction Type

< insert the transaction types to be used >

Text Type <for example A002>

Int. Partner <for example 00000032>

Field Value

Ext. Partner <for example 00001000>

3. Choose Save.

Noteo Transaction type

The app displays only those appointments from the CRM backend that have this transaction type. When a new appointment is created from the app, the system uses this transaction type.Make sure that you choose a transaction type from a transaction category for which, the Include Activity in Calendar option has been activated.If you want your users to be able to set an appointment to Private, the transaction category must allow this (option Private Appointments Allowed).

o Text type that is used for the notes sectionThe text type you choose needs to be contained in the text determination procedure that has been assigned to the transaction type you entered above.

4.4 Report Quality Issue / My Quality Tasks

4.4.1 Configuration in the SAP Back-End System for Report Quality Issue

Use

This customizing settings in the SAP ERP back-end system defines the behavior (data being displayed and so on.) for the Report Quality Issue SAP Fiori application.

Procedure 1. Access the activity using one of the following navigation options:

SAP IMG Menu Quality Management Fiori Apps for Quality Management Configure Quality Management Apps




reserved. 33

2. Select New Entries and make the following entries:

Field Name Description User Action and Values

App ID Q01

Application Name Report Quality Issue

Plnt <your plant>

Cat.Prof. Catalog profile created above QMOBILE

NoteIn case the SAP delivered notification type Q3 is used maintain here:QM0000001

Max.Rec. Number of notifications to be displayed

Max.Rec.

3. Save your settings.4. Select the newly created row.5. Select the folder Common Configuration.6. Select New Entries and maintain the following values:


Typ QM

NoteIn case the SAP delivered notfication type Q3 is used maintain here:Q3

Default Selected7. Save your settings8. Select the folder Attachment Configuration.9. Select New Entries and maintain the following values:


Category DMS_C1_ST

File Size 10000000

Logical file QOD_IMAGE10. Save your settings.



reserved. 34

Result

You can now create a Quality Notification via the Fiori app of type QM.

4.4.2 Configuration in the Back-End System for My Quality Tasks

Use

This document describes the required backend settings in the ERP so that the Fiori app My Quality Tasks can be used.

Procedure 1. Access the activity using one of the following navigation options:

SAP IMG Menu Quality Management Fiori Apps for Quality Management Configure Quality Management Apps


2. Select New Entries and make the following entries:


App ID Q02

Application Name My Quality Notification3. Save your settings.4. Select the newly created row.5. Select the folder Common Configuration.6. Select New Entries and maintain the following values:


Typ *

Default Selected7. Save your settings

Result

You can now see incoming Tasks in the Fiori app.



reserved. 35

NoteIn case you have configured your own Quality Notification Type (i.e. you are using a different one as Q3) additional settings are required to create Quality Tasks from a Quality Notification. This is not described in this document. In case you want to populate the Fiori app My Quality Tasks with tasks you can you Quality Notification Type Q3 for this purpose.

4.5 Additional Configuration Steps for SAP Fiori PP-MRP Apps

Purpose

As of SAP Fiori for SAP ERP 1.0 SPS03, the following apps are delivered for Material Requirements Planning: Monitor Material Shortages Manage Material Shortages Monitor External Requirements Manage External Requirements Monitor Internal Requirements Manage Internal Requirements Monitor Production Orders or Process Orders Manage Production Orders or Process Orders

The purpose of this chapter is to outline additional configuration steps for these SAP Fiori MRP apps.

NoteThe SAP HANA database is mandatory for working with SAP Fiori apps for MRP. All restrictions concerning the handling of materials on an SAP HANA database are also valid for the MRP apps. For more information, see the Help portal.

4.5.1 Setup RFC Connection SAP_ERP_PP

Purpose

In this step, you configured the RFC connection SAP_ERP_PP with connection type H and choose Trusted Relationship as the Logon Procedure. This RFC connection is used for navigating to the back-end system to view the stock/requirements list or change material data. If you use a different name for the RFC connection, you have to change the system alias for the entries Stock Requirements List and Change Material in transaction LPD_CUST for role UIAPPP01 and instance TRANSACTIONAL.



reserved. 36

http://help.sap.com/fiori_bs2013/helpdata/en/83/abb152784afb27e10000000a44176d/content.htm?frameset=/en/77/5be452a5130275e10000000a44538d/frameset.htm&current_toc=/en/ba/954353a531e647e10000000a441470/plain.htm&node_id=147&show_children=false

Procedure1. In the Gateway system, access the activity using the following navigation option:

Transaction Code SM59

2. On the Configuration of RFC Connections screen, choose Create.3. On the RFC Destination screen, make the following entries:

Tab Field Name Values

- RFC Destination SAP_ERP_PP

- Connection Type H (HTTP Connection to ABAP System)

- Description <description>

Technical Settings Target Host <target host>

Technical Settings Service No. <port>

Technical Settings Proxy PW Status Is initial

Logon & Security [Logon with User area]Trust RelationshipClientPW Status

[select the checkbox] <client>Is initial

Logon & Security [Security Options area]SSLSSL Certificate

[select the Active checkbox]DEFAULT SSL Client (Standard)

4.6 Adapting the Business Logic in the Backend SystemFor many apps the business logic of the app can be influenced by implementing the available Business Add-In (BAdI) in the connected back-end system. The BAdI Builder can be accessed using the following navigation path:

IMG Menu Tools → ABAP workbench→ Utilities → Business Add-Ins → Definition

Transaction Code SE18

The app-specific details need to be checked in the official Fiori documentation published via help.sap.com.



reserved. 37

5 SAP Fiori Launchpad

5.1 Access the SAP Fiori Launchpad

Use

The SAP Fiori Applications can be accessed via the SAP Fiori Launchpad. Using the SAP Fiori Launchpad allows the users to access all SAP Fiori applications where they are assigned to accessing one single page.

Procedure

The SAP Fiori Launchpad can be accessed using this URL:

http://<Gatewayhost>:<port>/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html

NoteIf the default client is not the client with which to display the Launchpad, you have to include the sap client string to the URL: http://<Gatewayhost>:<port>/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html?sap-client=<client number>

NoteIn case no SAP Fiori application is assigned to a certain user the Fiori Launchpad remains empty. How to assign a user to is described in the next chapter.

Result

The user’s home page can be launched.

NoteMake sure that you have assigned the respective PFCG role to the user. See the details in step Gateway System: Assign a User to the SAP Fiori Launchpad.



reserved. 38

5.2 Access the Launchpad Designer

Use

The Fiori launchpad designer is the standard tool for: Configuring the tiles for static app launchers, dynamic app launchers, and target mapping. Creating pre-configured groups and catalogs for the home page. Transporting the configurations via correction requests / packages or customizing workbench.

Procedure

The Launchpad Designer can be accessed using the following URL:

http://<Gatewayhost>:<port>/sap/bc/ui5_ui5/sap/arsrvc_upb_admn/main.html

Result

The Launchpad Designer is launched and changes in the SAP Fiori Launchpad can be performed.

NoteAn additional building block is delivered with the SAP Fiori apps rapid-deployment solution to address detailed requirements for the launchpad settings: Launchpad Configuration (EE3).

5.3 Change Background Image for SAP Fiori Launchpad Logon Page

Use

This chapter describes how to change the SAP logo and background, on mobile device and desktop, for the login page to the SAP Fiori Launchpad. Customer may want to replace the SAP logo or the background with special Corporate Branding.


Transaction Code SE80

IMG Menu Tools → ABAP Workbench → Overview → Object Navigator2. Choose MIME Repository.3. Navigate to folder PUBLIC → BC → UI2 → logon → img.



reserved. 39

4. The 3 relevant files are stored in img folder:login_background_mobile.jpglogin_background.jpgsap_logo.png

5. Download the files to a local folder – for backup reasons – by right-click on the respective file. Choose Download and save file to local folder.

6. Upload new file, for example, <customer_logo.png> by right-clicking the sap_logo.png file and choosing Upload/Download → Upload and Replace.

7. Upload the file.

NoteCheck the resolution and size of the pictures. For large screens, a high resolution is recommended.For branding the app itself, use the Theme Designer for SAP Fiori (MF4) configuration guide.

Result

After uploading the new picture, the old file is replaced. The effect is immediately visible once you login again, to the SAP Fiori Launchpage.

5.4 Adapting the Logout Page in the SAP Fiori Launchpad

Use

Once the user is logging out from the SAP Fiori Launchpad via the Log Out button a Logoff page is displayed. This section describes how to redirect the html call to a different page. This example describes the redirection to SAP Fiori Launchpad again. Any other URL might be set here which, fits to the customer needs.

Procedure1. Access the following transaction:


2. Choose Execute (F8).3. Expand the folder default_host → sap4. Find the services navigating to this path:

Path External Service Name

public → bc →icf → logoff Logoff5. Double-click the selected service.



reserved. 40

6. Choose Change(Ctrl+F1) .7. Select tab Error Pages.8. Select sub-tab Logoff Page.9. Choose option Redirect to URL. Enter the URL to be called after the logout in the field Redirect.

NoteFor a redirection to the SAP Fiori Launchpad enter the following link:http://<Gatewayhost>:<port>/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html

10. Select Save.11. Select Display → Change (CTRL+F1) button.

Result

Once logging out from the SAP Fiori Launchpad the html page maintained is being called.



reserved. 41

6 Transportation

Use

When implementing and configuring this rapid-deployment solution in a multi-tier customer landscape, the applied configuration settings need to be transported from one system landscape to the next (that is, from a development landscape to a quality landscape and to a productive landscape in case of a 3 tier landscape environment). This section describes additional aspects which need to be taken into consideration while configuring SAP Fiori in a multi-tier landscape. As a prerequisite, the ABAP transport system between the systems needs to be configured properly. Configuration settings that can be transported using the APAB transportation mechanisms and where no additional or subsequent steps are required are not mentioned in the following list.

Procedure

Find in the following table an overview on the steps where additional considerations are required.

Chaptername Comment/Additional information

Back-End system: Assign the Backend Role for the User

The user assignment needs to be carried through in each system. Find additional information on transporting pfcg Roles here:http://help.sap.com/saphelp_nw70ehp2/helpdata/en/6d/7c8cfd410ea040aadf92e1f78107a4/content.htm

Gateway System: Assign a User to the SAP Fiori Launchpad

Gateway System: Activate UI5 Services

The UI5 Services to be used need to be activated in each system - no transport mechanism available here.

Gateway System: Activate OData Service

During manual activation of an OData service a package and a transport request is assigned. The respective OData service activation can be transported.Make sure that in the target system the underlying RFC connection is named properly (check the setting for the System Alias where the RFC connection is assigned to) and is pointing to the right system. Once you activate the OData service via task list you need to perform the task list run in each tier landscape.

Create System Alias for Backend Workflow in the SAP Gateway System

Make sure that in the target system the underlying RFC connection is named properly (check the setting for the System Alias where the RFC connection is assigned to) and is pointing to the right backend system.



reserved. 42

http://help.sap.com/saphelp_nw70ehp2/helpdata/en/6d/7c8cfd410ea040aadf92e1f78107a4/content.htm

http://help.sap.com/saphelp_nw70ehp2/helpdata/en/6d/7c8cfd410ea040aadf92e1f78107a4/content.htm



reserved. 43

7 Further Information Resources On SAP Community Network (SCN), there are several information sources on topics around troubleshooting and lessons learned about how to deal with SAP Fiori app implementation. See a selection of information resources here: SAP Fiori - Generic troubleshooting steps: http://scn.sap.com/docs/DOC-48863 All things on Fiori: http://scn.sap.com/docs/DOC-41598



reserved. 44

http://scn.sap.com/docs/DOC-41598



www.sap.com/contactsap

© 2016 SAP SE or an SAP affiliate company. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.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 or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies. Please see www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.

Material Number:

http://www.sap.com/corporate-en/legal/copyright/index.epx

Date post:	16-Apr-2018
Category:	Documents
Upload:	dohanh
View:	223 times
Download:	4 times

SAP Offline Word Templatesapidp/... · Web viewSAP Offline Word Template Keywords Template Last...

Documents