SAP Offline Word Template - wiki.myftp.orgwiki.myftp.org/sap/bp/s4hana1709/Library/... · Web...

Building Block Configuration GuideDocument Version: 1.6 – 2017-07-06

CUSTOMER

SAP S4HANA Other App Types Deployment (MAL)

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 .

2

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

SAP S4HANA Other App Types Deployment (MAL)Table of Contents

Document HistoryVersion Date Change

1.0 2015-11-15 Version 1

1.1 2016-03-23 Technical Update

1.2 2016-10-14 Technical UpdateNew Chapter for 'Automated Activation with Task Lists' for Web Dynpro Applications

1.3 2017-01-31 Update chapter 3.1.2 'Replicate App Descriptors from Back-End System'

1.4 2017-02-03 Update chapter 3.1.1 'Create RFC connections to connect the Frontend server to the Backend server'

1.5 2017-04-25 Technical Update

1.6 2017-06-07 Update for SAP S/4 HANA 1709, on-premise edition

SAP S4HANA Other App Types Deployment (MAL)Document History

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

reserved. 3

Table of Contents1 Purpose

2 Prerequisites

3 Configuration3.1 Replication of Backend Catalogs

3.1.1 Creating RFC connections to connect the Frontend server to the Backend server3.1.2 Mapping the System Aliases to Logical System Aliases3.1.3 Replicating App Descriptors from Back-End System

3.2 Creating an HTTP RFC Destination to Back-End Server3.3 Adding an NWBC App to the Fiori Launchpad

3.3.1 Activating Services for NWBC / SAP GUI for HTML Apps3.3.2 Creating an NWBC Target Mapping into Catalog3.3.3 Adding an NWBC App Tile into Catalog and Group

3.4 Web Dynpro App Configuration3.4.1 Getting App’s Technical Information3.4.2 Checking/Creating Required HTTP Connection3.4.3 Back-End system: Activating Web Dynpro Application3.4.3.1 Automated Activation with Task Lists3.4.3.2 Manual Activation3.4.4 Back-End System: Assigning the Backend Role for the User3.4.5 Activating Gateway Service in ABAP Front-End Server3.4.6 Assign a User to the SAP Fiori Launchpad

4 Transportation

4


SAP S4HANA Other App Types Deployment (MAL)Table of Contents

1 PurposeIn an SAP S/4 HANA implementation not only the SAP Fiori app types like transactional apps, fact sheets and analytical apps are important - but also other applications, such as Web Dynpro and NetWeaver Business Client applications. These must be configured so that they can be accessed via the SAP Fiori Launchpad. This guide provides the information needed to configure these app types and make them available in the Fiori Launchpad.

SAP S4HANA Other App Types Deployment (MAL)Configuration


reserved. 5

2 PrerequisitesBefore starting with the activities of this building block, complete the configuration of the building blocks 'SAP S/4 HANA Fiori Foundation Configuration (MAA)' and 'SAP S/4 HANA Fiori Basic Network and Security Configuration (MAB)'.

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 that all additionally required (app-specific) SAP Notes have been

implemented. o The required users have been generated in the SAP S/4 HANA system and ABAP Front-End

server. The users in the SAP S/4 HANA system and ABAP Front-End server must be identical.In order to find information on the prerequisite requirements for each application, go to SAP Fiori apps reference library, choose the application name and navigate to Implementation Information → Installation → Front-End Components / Back-End Components (ABAP) / Required SAP Notes.

6


SAP S4HANA Other App Types Deployment (MAL)Transportation

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


3 Configuration

3.1 Replication of Backend CatalogsThe technical catalogs for NWBC apps and WebDynpro apps have been moved from the Front-End Server to the Back-End Server, starting from S/4 HANA OP Edition 1602. For additional information you can also check the SAP Note 2235246.

NoteIf relevant for your system version, please implement the SAP Notes 2243529, 2256680 and 2269272 to get corrections related to accessing NWBC or WebDynpro apps from the SAP Fiori Launchpad.

3.1.1 Creating RFC connections to connect the Frontend server to the Backend server

UseTo consume catalogs containing Web Dynpro and NetWeaver Business Client / SAP GUI for HTML apps from a back-end system, it is mandatory to configure two types of RFC connections to the back-end system. In this section, it is described how to create these RFC connections.

Procedure1. Log in to the ABAP Front-End Server.2. Call the following transaction:

Transaction Code SM59

3. Create ABAP connections (type 3) named <System_Alias>_RFC to the back-end system for each of the system aliases. This type of connection is used to replicate app descriptors from the back-end server to the front-end server. Applications which use Web Dynpro and SAP GUI for HTML UI technology carry app descriptors which provide information required to access them from the SAP Fiori Launchpad.

4. Create HTTP connections (type H) with SSL enabled named <System_Alias>_HTTPS to the back-end system for each of the system aliases. This type of connection is used for the link resolution in the Fiori Launchpad runtime. Find details on how to create this connection in the section 'Creating an HTTP RFC Destination to Back-End Server' of this document.

CautionIn order to avoid problems when calling the Web Dynpro or SAP GUI for HTML apps in the connected S/4 HANA system, stay consistent regarding the usage of HTTPS protocol. Please also make sure that SNC has been activated.



reserved. 7

3.1.2 Mapping the System Aliases to Logical System AliasesUseThe business catalogs shipped by SAP contain system aliases which are used to call an app in a specific system, for example, S4FIN or S4CMD. In a customer system landscape, several system aliases may point to the same physical source system. To reduce administrative effort, SAP recommends creating entries in the table /UI2/SYSALIASMAP to map the SAP system aliases to logical system aliases, which stand for the physical back-end systems connected to the front-end system. In this section, the procedure to perform this mapping is described.Procedure1. Log in to the ABAP Front-End server.2. Call the following transaction:


3. In the Table/View field, enter the view /UI2/V_ALIASMAP and choose Maintain.4. The table has the following structure:

Field Name Key DescriptionMANDT Yes ClientSYSALIAS_SRC Yes Source System AliasSYSALIAS_TGT Target System Alias

Choose Edit → New entries.5. Maintain the view according to your landscape. An example is provided below:

Client Source System Alias Target System AliasS4FIN ERPCLNT100S4LO ERPCLNT100

6. Choose Save.

NoteMapping allows you to define global or client dependent mapping. In case of global mapping, the client field shall be left empty. Client-dependent definition has priority over global definition

3.1.3 Replicating App Descriptors from Back-End System

UseTo enable the access from the SAP Fiori Launchpad to applications that use Web Dynpro and SAP GUI for HTML technology, you have to replicate information about these applications from the back-end server to the front-end server. Each app has an app descriptor which provides this information. Please note that you have to execute the replication before you enter the Launchpad Designer to create your own catalogs. Only after the replication you will see the apps in the Technical Catalogs view. In this section, the steps that you need to follow to replicate the app descriptors are described.

8




Transaction Code /UI2/APPDESC_GET

3. In the catalog ID field, enter SAP_*_BC_* (business catalogs). This will select all technical catalogs and their comprised apps.

4. Select the Testmode checkbox and choose Execute. The catalogs will not be replicated; a log is displayed.

5. If the log does not contain any errors, deselect the Testmode checkbox and choose Execute.6. In the Launchpad Designer, ensure that the SAP_TC* catalogs are replicated.

7. Choose a SAP_TC_CA_PR catalog, and then choose the Target Mapping tab. Select one of the target mappings and then click on Configure. Ensure that the System Alias has been mapped to the logical system alias, as described in the previous chapter.



reserved. 9

NoteIt may happen that a technical catalog already exists in the SAP S/4 HANA system, but, for any reason, no business catalogs are available. In this case this technical catalog does not get replicated using the transaction /UI2/APPDESC_GET. In case you need this technical catalog, you can execute the following steps as a workaround:1. Call transaction SE38.2. Enter report name /UI2/GET_APP_DESCR_REMOTE_DEV and choose Execute.3. Maintain the System Alias, Catalog ID, Extraction Mode and select the suitable option for

Testmode.Result: The technical catalogs have been replicated. You can now use the 'SAP Fiori Launchpad Designer' to maintain the required metadata as the business catalogs etc. This report is also used for replicating customer-created content.

3.2 Creating an HTTP RFC Destination to Back-End Server

UseNWBC and Web Dynpro applications use an HTTP RFC connection to the back-end system. This chapter describes how to configure this connection.



3. On the Configuration of RFC Connections screen, choose Create.

10



4. On the RFC Destination screen, enter the RFC Destination, for example ERPCLNT180_HTTP or ERPCLNT180_HTTPS and the Connection Type as H and then choose Save (Ctrl+S ).

5. Choose the Technical Settings tab, enter Target Host as your SAP S/4 HANA system hostname and Service No. as its HTTP/HTTPS port.

6. Choose the Logon & Security tab; choose Logon with User as Trust Relationship. If you're using HTTPS port, choose SSL as Active.

7. Choose Connection Test and Save if a dialog box appears. Ensure that the Status HTTP Response is 404.

NoteSM59 does not allow you to create several destinations with the same name even if the connection types are different. The trick for referencing several destinations by the same name is to have multiple SM59 entries with the same basename and different extensions (_RFC, _HTTP, _HTTPS) to distinguish between the different types of connections. More information can be found under this link.

3.3 Adding an NWBC App to the Fiori LaunchpadNWBC apps are links to NWBC pages of transaction codes in the SAP S/4 HANA system. These applications are no SAPUI5 apps. The tile and target mapping entries in the Launchpad Designer are pre-delivered for all SAP-delivered apps. In this section, the integration of the Web GUI app 'Change Sales Order' to the SAP Fiori Launchpad using the Launchpad Designer is described.

NoteStarting with SAP UI Add-on 2.0 SPS01, the SAP Fiori Launchpad configuration is done using the Launchpad Designer for all application types, including NWBC and Web Dynpro applications. It is recommended to use the Launchpad Designer instead of the transaction Overview of Launchpads (transaction code LPD_CUST) for the configuration of tile catalogs, tiles and target mappings for reasons of simplicity and performance during runtime.

3.3.1 Activating Services for NWBC / SAP GUI for HTML Apps

UseA couple of services need to be active on the ABAP Front End Server. In case they are not active yet, activate them.

Procedure1. Log in to the Front-End server.2. Call the following transaction:

Transaction Code SICF

3. Choose Execute. The Maintain Service window displays.4. Activate the following services:



reserved. 11

http://scn.sap.com/community/netweaver-business-client/blog/2015/06/01/configuring-remote-systems-in-sm59

o /sap/bc/guio /sap/bc/ui2/nwbco /sap/bc/apc/sap/webgui_serviceso /sap/bc/gui/sap/its/webguio /sap/bc/gui/sap/its/typeaheado /sap/public/bc/uro /sap/public/bc/its/mimes

5. Run the transaction SIAC_PUBLISH_ALL_INTERNAL to activate the Web GUI services. When the activation is completed, you should see a screen indicating that the activation was done successfully.

3.3.2 Creating an NWBC Target Mapping into Catalog

Procedure1. In the Launchpad Designer, choose the catalog SAP_SD_BC_SO_PROC_OP, and then choose the

Target Mappings tab.2. Choose the SalesDocument change line and then choose Create Reference.3. In the Select Catalog dialog box, choose the catalog, e. g. Z_RDS_BC.4. Check if the Target Mapping is added into the Catalog Z_RDS_BC.

3.3.3 Adding an NWBC App Tile into Catalog and Group

Procedure1. In the Launchpad Designer, choose the Catalog Z_RDS_BC and verify that the target mapping to

the NWBC app already exists.2. On the right side panel, choose Tiles and then choose the + Add Tile.

12



3. On the Select a tile template screen, choose App Launcher - Static.4. The Configure: 'App Launcher - Static' screen shows up. Enter Title, for example, Change Sales

Order, and Subtitle and choose an Icon. It will be displayed in the Launchpad tile. Select the flag Use semantic object navigation. Enter the Semantic Object as SalesDocument and Action as change. (They need to be the same as the Semantic Object and Action in the Target Mapping.)

5. Choose Save. The screen will automatically guide you back to the catalog Z_RDS_BC.6. Switch to the Groups tab in the left-hand pane. Choose the group Z_RDS_BCG (if the group is not

available, create it), and then choose the + Add Tile.7. On the Add Tile to Group 'Z_RDS_BCG' screen, choose the input help button.

8. In the Catalogs dialog box, choose the Z_RDS_BC catalog. All tiles of this catalog will be displayed. Tiles with a green check are already added to the group, whereas tiles with a grey plus are not yet part of it.

9. Choose the grey plus button below the tile. It will turn to the green check and the tile will be added. Choose the back arrow and check if the tile is added to the group.

3.4 Web Dynpro App Configuration

PurposeIn this section, the configuration steps to activate the Web Dynpro application 'Trial Balance Version 2' are described. This configuration consists of the SAP Fiori Launchpad configuration, i.e. the tile and the target mapping, and the back-end configuration, i.e. the Web Dynpro application itself. The back-end and the front-end components are delivered in separate products and they have to be installed in a



reserved. 13

system landscape that is enabled for SAP Fiori. Refer to SAP Fiori apps reference library for a list of the available Web Dynpro applications delivered via SAP products.

NoteSimilarly to the NWBC apps, the SAP Fiori Launchpad configuration for Web Dynpro applications is done using the Launchpad Designer. It is recommended to use the Launchpad Designer instead of the transaction Overview of Launchpads (transaction code LPD_CUST) for the configuration of tile catalogs, tiles and target mappings for reasons of simplicity and performance during runtime.

3.4.1 Getting App’s Technical Information1. Access the SAP Fiori apps reference library: http://www.sap.com/fiori-apps-library and click on All

Apps.2. In the top left search bar, enter the application's name and choose the magnifying glass icon.

For example, enter 'Trial Balance' and the result is as following:

3. Choose Implementation Information → Configuration and note down the following technical details that are required for the configuration steps in the subsequent sections:

# Section under Configuration

Technical Detail

1 Technical Catalog SAP_TC_FIN_ACC_BE_APPS2 Business Catalog SAP_SFIN_BC_GL_GEN_REP3 Business Role SAP_BR_GL_ACCOUNTANT4 Web Dynpro Application FIS_FPM_OVP_TRIAL1 (for the standard view)

NoteFor the comparison view, you also need to activate the following Web Dynpro application: FIS_FPM_OVP_TRIAL2

14





5 Semantic Object GLAccount6 Semantic Action analyzeTrialBalance

Note Double-check the Business Role and the Web Dynpro application name. Go to SAP Fiori apps reference library → < application name> → Implementation Information → Installation → Read more in Implementation Documentation / Configuration Documentation. If you are not able to find this link from the SAP Fiori apps reference library, open SAP Help directly and go to the corresponding documentation. See the Trial Balance Version 2 application as an example: http://help.sap.com/sfin300 → SAP Fiori for S/4HANA Finance → SAP Fiori for S/4HANA Finance → General Ledger Accountant → Trial Balance → App Implementation: Trial Balance.

3.4.2 Checking/Creating Required HTTP ConnectionIn the Launchpad Designer (ABAP Front-End Server, transaction FLPD_CUST), access the business catalog found in the SAP Fiori apps reference library.1. Choose the Target Mapping tab.2. Click on the Target Mapping for your Web Dynpro application, i.e. Trial Balance, and select

Configure at the bottom of the Launchpad Designer.3. A System Alias (e. g. S4FIN) is displayed. Ensure that this system alias has been mapped to the

logical system alias, as described in the section 3.1.2.

3.4.3 Back-End system: Activating Web Dynpro Application

3.4.3.1 Automated Activation with Task Lists

PurposeIn this chapter, you activate UI services for the Web Dynpro applications in an automated way by using predefined task lists. In the configuration guide 'SAP S/4 HANA Fiori Apps Deployment' of the building block MAD, chapter 'Get Technical Information', it is described how to derive the required list of UI services from the SAP Fiori apps reference library. Use the csv file you downloaded for 'ICF Nodes for WebDynpro Applications' and proceed to the steps described below.

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

Procedure1. Log in to your SAP S/4 HANA system.2. Call the following transaction:



reserved. 15

http://help.sap.com/sfin300




Transaction Code STC01

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

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/webdynpro/sap/FIS_FPM_OVP_TRIAL1

NoteIf you want to insert multiple service paths / URLs, copy and paste the list of URLs into the first line. All the URLs will be inserted into their own line.

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 icons appear in the task log.

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

ResultYou have successfully carried out the task list run SAP_BASIS_ACTIVATE_ICF_NODES to activate ICF services using the transaction SICF.

3.4.3.2 Manual Activation

NoteIf you have already carried out the activation of UI services automatically using task lists (previous chapter), you may skip this step.

16



Procedure1. Log in to the SAP S/4 HANA system.2. Call the following transaction:

Transaction Code SICF

3. Choose Execute (F8 ).4. To activate the Web Dynpro Application FIS_FPM_OVP_TRIAL1, choose the following navigation

path on the Maintain service screen:

Navigation Path /sap/bc/webdynpro/sap

5. Choose the service FIS_FPM_OVP_TRIAL1, right-click on it and choose Activate Service.6. Choose the service FIS_FPM_OVP_TRIAL2, right click on it and choose Activate Service.

3.4.4 Back-End System: Assigning the Backend Role for the User

1. Log in to the SAP S/4 HANA system.2. Access the activity using one of the following navigation options:

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

Transaction Code PFCG

3. On the Role Maintenance screen, enter the Back-End Authorization Role you noted down before from the SAP Help documentation, for example: SAP_SFIN_ACC_REPORTING.

4. Copy the role to your customer namespace and save.5. Choose the User tab page, enter the user ID as the back-end user. 6. Choose Save (Ctrl+S ).

3.4.5 Activating Gateway Service in ABAP Front-End Server

PurposeIn case the app to be implemented shows dynamic values in the Launchpad tile, oData services deliver the values to be displayed. However, the required oData service might not be activated. In this section, it is described how to identify the required service and how to activate it.

Procedure1. Open the Launchpad Designer:

http(s)://<Front-End Server Hostname>:<Front-End Server Port>/sap/bc/ui5_ui5/sap/arsrvc_upb_admn/main.html

2. Search the technical catalog.



reserved. 17

3. Choose the tile for the application.4. Note down the Service URL displayed:

NoteIn case the section Dynamic Data is missing for your app, this step is obsolete. Then no OData service needs to be configured or activated.

5. In the ABAP Front-End server, access the activity using one of the following navigation options:

Transaction Code /IWFND/MAINT_SERVICE

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

6. On the Service Catalog screen, choose Add Service.7. On the Add Service screen, enter the System Alias that has been created during the configuration

in the ABAP Front-End server. You can also use F4 help. 8. Enter the OData service, e. g. FCLM_BAM_SRV.

NoteThe required service name is always the one after the path '/sap/opu/odata/sap/'.

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

field.13. Select Standard Mode in the ICF Node section.14. Select the Set current client as default client in ICF Node checkbox and choose Continue (Enter ).15. Assign your workbench and customizing requests and confirm the displayed messages.16. Confirm the information message that the metadata was loaded successfully.17. Choose Back.18. From the Service Catalog, select the record you have just created.19. Choose Gateway Client.20. Choose Execute (F8 ).21. The HTTP Response is displayed and an XML file appears in the lower right corner. This indicates

that the web service is configured properly.

NoteFor web service calls you must maintain authorization the object S_SERVICE and then assign the web service operations to a role in transaction PFCG.

18



3.4.6 Assign a User to the SAP Fiori Launchpad1. Log in to the ABAP Front-End server.2. Access the activity using one of the following navigation options:

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

Transaction Code PFCG

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

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

Note In case you want to add or create your own custom catalogs and groups including Web Dynpro applications the same steps as described for NWBC applications are required:o Create a target mapping, and o Add a tile into Catalog and Group .



reserved. 19

4 Transportation

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

ProcedureFind in the following table an overview of the steps where additional considerations are required.

Chapter name Comment/Additional informationCreating an HTTP RFC Destination to Back-End ServerCreating an HTTP RFC Destination to Back-End Server

The HTTP RFC Destinations to be used need to be activated in each system - no transport mechanism available here.

Assignment of http Connection to All Apps in a Fiori Launchpad

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. Checking/Creating Required

HTTP Connection

Creating an NWBC Target Mapping into Catalog

Once a transport request is assigned in the Launchpad Designer all settings can be transported.Find more information in configuration 'SAP S4HANA Fiori Launchpad Operation (MAG)'Adding an NWBC App Tile into

Catalog and GroupBack-End System: Assigning 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: Assigning a User to the SAP Fiori Launchpad

20



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

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

Chapter name Comment/Additional informationGateway System: Activating Gateway Service in SAP Gateway

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.



reserved. 21

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

SAP Offline Word Template - wiki.myftp.orgwiki.myftp.org/sap/bp/s4hana1709/Library/... · Web...

Documents

Transcript of SAP Offline Word Template - wiki.myftp.orgwiki.myftp.org/sap/bp/s4hana1709/Library/... · Web...