INSTALLATION GUIDE PUBLIC Document Version: 1.0 2016-12-08 SAP Workplaces for Insurance 1.0 SP06 2018 SAP SE or an SAP affiliate company. All rights reserved. THE BEST RUN
Content 1 Apps for Insurance from SAP....3 1.1 Component Overview of Apps for Insurance Services from SAP.... 4 2 Installation of FS-IPW Components.... 7 2.1 Pre-installation....7 2.2 Installation....8 Front-End Server....8 Creation of Semantic Objects....12 Configuring Maintain Business Partner Tile....12 Implementing a Logout Page....13 Roles and Authorizations.... 16 Web Dispatcher....17 Client....18 3 Next Steps....19 2 P U B L I C Content
1 Apps for Insurance from SAP The FS-IPW component contains a bundle of transactional apps for insurance services from SAP that run on the SAP Fiori Launchpad. The following apps are available: Create Insurance Quote My Insurance Worklist My Underwriting Worklist Create Group Insurance Quote (Since SP02) My Insurance Tasks (Since SP02) Create Insurance Quote from Master (Since SP05) Create Master Insurance Quote (Since SP05) Product Information The system landscape consists of front-end components and back-end components. These apps for insurance from SAP are part of the front-end components. Component UI for SAP Workplaces for Insurance Software Component Version UIFSIPW 100 Support Package SP06 Delivery Date 12/2016 Integration Data is exchanged between the apps and the back-end components using OData services. Setup of App Environment for Insurance Services from SAP You can use transactional apps to access the SAP Fiori system landscape in an ABAP environment. Before implementing an app, set up the system landscape to enable SAP Fiori. An app requires front-end components (providing the user interface and the connection to the back end) and back-end components (providing the data). The front-end components and the back-end components are delivered in separate products and have to be installed in a system landscape that is enabled for SAP Fiori. Apps for Insurance from SAP P U B L I C 3
The following diagram provides a high-level overview of the Fiori-based insurance applications: FS-IPW_architecture2 1.1 Component Overview of Apps for Insurance Services from SAP This is a component overview of the Apps for Insurance Services from SAP. Client To be able to run the insurance apps, the runtime environment (for example, the browser) of the client must support HTML5. 4 P U B L I C Apps for Insurance from SAP
SAP Web Dispatcher The apps send requests to several systems, depending on the application type and the connected system landscape, using the following process: The client first loads the UIs for the SAP Fiori apps. Then, while it is running, the app consumes data from the back-end systems. Standard browsers have a same origin policy, meaning that HTTPS requests for the UI data and the back-end data must communicate with just one web address. To meet this requirement, a reverse proxy server must be installed between the client and the SAP system. The reverse proxy server acts as the only point of entry for all HTTPS requests. Depending on the requests sent by the app, the reverse proxy server selects the appropriate application server, the ABAP front-end server or the SAP Gateway server. ABAP Front-End Server The ABAP front-end server contains all the infrastructure components for an SAP Fiori app. The UI components and the gateway are based on SAP NetWeaver. Typically, both are deployed on the same server. The central UI component is a framework that provides the common infrastructure for all SAP Fiori apps: SAP Fiori launchpad is the basis of all SAP Fiori UIs, and provides fundamental functions for SAP Fiori apps such as logon, surface sizing, navigation between apps, and role- based app catalogs. End-users access the SAP Fiori apps from the SAP Fiori launchpad. The specific UIs for the apps are delivered as: Create Insurance Quote My Insurance Worklist My Underwriting Worklist Create Group Insurance Quote (Since SP02) My Insurance Tasks (Since SP02) Create Insurance Quote from Master (Since SP05) Create Master Insurance Quote (Since SP05) They must be additionally installed on the front-end server. The following SAP Notes provide important overview information: SAP Note Number Target Server Description 2136369 Front-End server General information: Fiori UI infrastructure components, Q2/2015 2136366 Front-End server General information: Fiori SAP Gateway 2.0, Q2/2015 Apps for Insurance from SAP P U B L I C 5
Java Back-End server (Business Functionality Layer) The Java back-end component FS-QUO is installed in the business functionality layer, providing the business logic and the back-end data, including roles and authorizations. The back-end server runs on SAP NetWeaver. 6 P U B L I C Apps for Insurance from SAP
2 Installation of FS-IPW Components 2.1 Pre-installation Before installing the system landscape for SAP Fiori, make sure that all dependencies have been met. Prerequisites Verify the setup of the following software: A database, consisting of one of the following: SAP HANA 1.0 SPS11 or SAP HANA 1.0 SPS12 IBM DB2 version 10.5 FP5 (10.5.0.5) Oracle 11g Release 2, Oracle 12c Release 1 Microsoft SQL Server 2012 Standard or Enterprise Edition Microsoft SQL Server 2014 Standard or Enterprise Edition SAP NetWeaver version 7.4 SPS15 SAP Underwriting for Insurance (FS-QUO) version 3.0 SP04 Refer to the applicable SAP product documentation for additional information on these SAP products. Network architecture You have to decide which network zones the components of the SAP Fiori system landscape will reside in. For example, consider if the clients should be able to access the SAP Fiori apps over the Internet, or only within the company's intranet. Or, consider if there's a DMZ and if the SAP Web Dispatcher is deployed there. Depending on your network architecture, make sure you have the right security measures in place, such as a secure firewall configuration. System landscape The system landscape for SAP Fiori apps consists of different components for the front-end and the back-end. For more information, see Setting Up SSO for SAP Fiori Landscapes with ABAP Environments on the SAP Help Portal at http://help.sap.com/fiori_bs2013/helpdata/en/c2/d3a453ce09d444e10000000a44538d/ frameset.htm. Installation of FS-IPW Components P U BL IC 7
Single Sign-On (SSO) Components can be, depending on your system landscape: SAP Gateway on front-end server Java back-end server (FS-QUO) For a full discussion of using SSO with Fiori apps, see "User Authentication and Single Sign On" on the SAP Help Portal at http://help.sap.com/fiori_bs2013/helpdata/en/ec/bcaa539fe03543e10000000a44538d/ content.htm. Browser prerequisites SAP Fiori apps require a web browser that supports HTML5. For additional information, see SAP Note 1935915. Using Fiori apps and browsers Occasionally, you may encounter the following errors when using Fiori apps: Could not open app. Try again later. Service Failed. Contact your system administrator. If this occurs, clear your browser cache and log in again. In Firefox, you may have to manually import a security certificate from the Fiori app server. For detailed instructions on these tasks, see your browser s help files. 2.2 Installation 2.2.1 Front-End Server 1. Check or install the required SAP Gateway and Central UI components. On your front-end server, the following components have to be available: SAP NetWeaver components SAP Gateway components Central UI components Verify the following components, with the correct versions, are in place. 8 P U B L I C Installation of FS-IPW Components
Product Version Details SAP NetWeaver 7.4 SPS15 See the SAP NetWeaver 7.4 product page on the Help Portal. Go to Installation and Upgrade Information Installation Guide. SAP Gateway component Comprised component version: SAP NW GATEWAY FOUNDATION (SAP_GWFND) SP15 (As of SAP NetWeaver 7.4, the components GW_CORE, IW_FND and IW_BEP are replaced by this new software component for the SAP Gateway foundation.) Central UI component Comprised component version: USER INTERFACE TECHNOLOGY 7.50 (SAP_UI 750) SP05 with SAPUI5 CLIENT RUNTIME 1.00 UI5CLIENT38P_8-80000549 2. You must specify the settings for supported languages in the SAP Gateway system. These languages are English, Korean, Chinese, and Chinese (simplified). Settings include default and logon languages. You must install the same language packages for SAP Fiori in the SAP Gateway system and the SAP Business Suite back-end system. Ensure that the default language of the SAP Gateway system is the same as the default language of the back-end system, for example, English. If this isn't the case, ensure that the SAP Gateway system contains a subset of the languages of the back-end system. The logon language for the ABAP Application Server is set according to the following process: 1. If the Mandatory Logon Data indicator has been activated for a service in transaction SICF, the system uses the language that was entered there. 2. If this isn't the case, but the HTTP request contains the language in the HTTP header (as a header or a form field), you log onto the system using this language. 3. The browser settings of the calling client are then used. The system selects as the logon language the first language from the list that is maintained in the browser, and which is also installed in the SAP system. The language list is specified using the HTTP header field accept-language. Note In Internet Explorer, you can set the required language by choosing Tools Internet Options Languages. 4. If no language is defined by this process, the classic SAP system mechanisms are used. The logon language is based on the user settings (in transaction SU01) and if nothing is entered here, the default language of the SAP system is used automatically. 3. Install the front-end component UIFSIPW 100. We recommend that you use Software Update Manager in combination with Maintenance Optimizer to install the components. This facilitates SAP NetWeaver-based application system upgrades, enhancement package updates, and support package installation, while offering a harmonized UI. Software Update Manager is shipped as part of the software logistics toolset (SL Toolset) 1.0 independently of the applications. Installation of FS-IPW Components P U BL IC 9
You can download Software Update Manager from the Software Downloads area of the SAP Support Portal at https://support.sap.com/en/my-support/software-downloads.html. Go to Installation & Upgrades and choose Access Downloads. The SAP Software Downloads launchpad opens. Enter Software Update Manager in the Search field. Maintenance Optimizer in SAP Solution Manager is the central point of access for all maintenance activities. It supports the installation of updates and upgrades and completely manages the maintenance activities for your whole solution, and is centrally accessible from inside SAP Solution Manager. You can find more information on this wiki page. 2.2.1.1 Downloading the Components You can download the product versions from the SAP Software Download launchpad. Procedure 1. Go to the Software Downloads launchpad at https://launchpad.support.sap.com/#/softwarecenter. 2. Choose Search for Software. 3. Enter the technical name of the software component (UIFSIPW 100). 4. Download the SPs of the component. Note SPs are non-cumulative for ABAP components. Next Steps After downloading the components, you can start the installation and update manually. Ensure that the components installed in the landscape are at the latest support package level. 10 P U B L I C Installation of FS-IPW Components
2.2.1.2 Installing and Updating Product Versions with SAP Solution Manager You can install and update product versions with SAP Solution Manager. Procedure 1. In SAP Solution Manager, run transaction lmdb. On the Product Systems tab, select your product system and choose Display. 2. In the navigation tree, choose the top node (Product System). 3. On the Maintenance Transactions tab, under Maintenance Optimizer Transactions, choose Create Transaction. 4. Under Choose File Selection Mode, choose Calculate Files Automatically and then choose Continue. 5. On the Operations tab, under Update Options, select the Maintenance change option and choose Continue. 6. For product versions on the ABAP server: If you aren't running the relevant support package stack for SAP NetWeaver yet, set it as your target stack under Select Target and choose Continue. This will update your ABAP server to the chosen support package stack. 7. Confirm the Major Target by choosing Continue. 8. Select all product versions that you want to install. For information about the required product versions of your product, see the following documentation: Central components: Installation Requirements in the documentation of your SAP Fiori system landscape setup. Product-specific components for transactional apps and fact sheets: Installation Information in the documentation of the respective SAP Fiori product. 9. Confirm and add them to the download basket. If not all dependencies as given in the respective tables are automatically resolved, you must select them manually. 10. Confirm the download basket by choosing Continue. 11. On the Stack Files tab, download the system-specific stack XML file: In the ABAP system, for the Software Update Manager (SUM) 12. Save and close the Maintenance Optimizer windows. 13. Download the calculated files from the SAP Download Center. Make the downloaded files and XML files available on your systems, which need to be updated. 14. For product versions on the ABAP server that you want to install or update, do the following: a. Start the SUM on the ABAP server. b. Connect from your local PC using the browser. A Java web start application starts. c. Configure the SUM, pointing to the downloaded xml file and execute the installation and update procedure on your system. Installation of FS-IPW Components P U BL IC 11
2.2.2 Creation of Semantic Objects You need to create some semantic objects on the ABAP front-end server. As part of the UIFSIPW 100 installation process, the following semantic objects must be manually created on the ABAP front-end server using the /UI2/SEMOBJ transaction: Semantic Object Semantic Object Name Since InsuranceQuote Insurance Quote SP00 UnderwritingCase Underwriting Case SP00 GroupInsuranceQuote Group Insurance Quote SP02 InsuranceTask Insurance Task SP02 MasterInsurancePolicy Master Insurance Policy SP05 MasterInsuranceQuote Master Insurance Quote SP05 BusinessPartner 1 Business Partner SP06 For details, refer to https://help.sap.com/saphelp_uiaddon10/helpdata/en/ 60/9c84bbacb04fd8a17bdb5da742815f/content.htm. 2.2.3 Configuring Maintain Business Partner Tile We can configure a Maintain Business Partner tile to leverage the ERP BP functionalities within FS-IPW. Prerequisites SSO between SAP Gateway on front-end server (FS-IPW) and SAP ERP BP is enabled. Procedure 1. On the frond-end (FS-IPW) server, In SM59 (Transaction Code), create a RFC destination (SAP_FS_BP) with the following properties, and then perform a quick ping test. a. In the Connection Type filed, enter H. b. On the Technical Settings tab, enter the Target Host and Service No. to point to the ERP BP system. 1 Reused 12 P U B L I C Installation of FS-IPW Components
Note If ERP BP system isn't in the same domain as FS-IPW front-end server, you need to use SAP Web Dispatcher to bypass the domain issue. For more information, see SAP Note 2389824. c. On the Logon & Security tab, choose Do Not Use a User and Leave Language empty if you want to use the language from the calling application (from Launchpad logon language). d. On the Logon & Security tab, choose Send Assertion Ticket for Dedicated Target Sys. pointing to SID and client of back-end server (ERP BP system). e. On the Logon & Security tab, choose Active under SSL. 2. In Fiori Launchpad Designer, configure the target mapping. a. Choose the application type Transaction (as the default configuration). b. Set the system alias as SAP_FS_BP (configured in SM59). c. Add parameter BUS_JOEL_MAIN-CHANGE_NUMBER (Format: Table Name-Column Name) used for BP navigation with parameters in FS-IPW Fiori Apps. Related Information SAP Note 1257108 http://scn.sap.com/community/netweaver-business-client/blog/2015/06/01/configuring-remote-systemsin-sm59 2.2.4 Implementing a Logout Page A custom logout page is required to log out of the back-end server during the Fiori Launchpad logout process. For a general discussion of this issue, see http://help.sap.com/saphelp_uiaddon10/helpdata/en/66/ a7a5de69b340c4ac857a5c0d95de6c/content.htm. The following link provides a sample custom logout page invoking the logout URL from FS-QUO. Note that this only works when the logout page is setup in Web Dispatcher unless the full FS-QUO Java back-end URL is provided. http://help.sap.com/saphelp_uiaddon10/helpdata/en/8b/d342ae2cca4097b13e30dfba335c09/content.htm The high level-steps in this process are as follows: 1. Create a custom logout HTML page and upload it to the ABAP front-end server as a BSP application. 2. Configure an external alias for the ICF node /sap/public/bc/icf/logoff to redirect the logout to the custom logout page. Installation of FS-IPW Components P U BL IC 13
2.2.4.1 Creating a Custom Logout HTML Page and Upload It to the ABAP Front-end Server as a BSP Application You need to create a custom logout HTML page and upload it to the ABAP front-end server as a BSP application. Procedure 1. Add the logout rules to the SAP Web Dispatcher. Ensure the logout URLs to be used are routed to the correct system. wdisp/system_<rule number> = SID=<Gateway System ID>, EXTSRV=https://<external system server host and port>, SRCSRV=*:<Fiori Launchpad port>, SRCURL=<data services roots, example: /sap/opu/odata/,separated by ;> Or wdisp/system_<rule number> = SID=<Gateway System ID>,MSHOST=<message server host>, MSPORT=<message server port>,srcsrv =*:<Fiori Launchpad port>,srcurl=<data services roots, example: /sap/opu/odata/,separated by ;> 2. Create the custom logout page. The URL of this logout page must use SAP Web Dispatcher as its origin. For each system from which you want to log out, add a request Logout call with the proper logout URL. For a J2EE server and issue a GET request to logout servlet, for example /csiroot/logout. For ABAP systems, call the /public/bc/icf/logoff service on each server. Redirect to the actual logout page: document.location = <custom logout page> This redirects to the launchpad login page, instead of the front-end server s default /public/bc/icf/ logoff node. The following is an example logout page: <!DOCTYPE html> <html> <head> <meta http-equiv="content-type" content="text/html;charset=utf-8" /> <meta http-equiv="x-ua-compatible" content="ie=edge" /> <meta http-equiv="cache-control" content="no-cache, no-store, mustrevalidate" /> <meta http-equiv="pragma" content="no-cache" /> <meta http-equiv="expires" content="0" /> <script src="<your_flp_url>/resources/sap/ui/thirdparty/jquery/ jquery-1.11.1.js"></script> </head> <body> <em id="message">logout is in progress...</em> <script> (function () { "use strict"; /*global document, jquery*/ 14 P U B L I C Installation of FS-IPW Components
var ipending = 0; function finishlogout() { ipending -= 1; if (ipending <= 0) { //logout done for all URLs //Change message text on logout page document.getelementbyid("message").innerhtml = "You are logged out"; //(3) Client-side redirect // Redirect back to the Fiori Launchpad login page document.location = "<your_flp_url>"; } } function requestlogout(surl) { ipending += 1; jquery.post(surl).always(finishlogout); } // FS-QUO logout URL (accessible only via Web Dispatcher unless using // full URL to the Java back-end server) requestlogout("/csiroot/logout"); }()); </script> </body> </html> For more information about the Fiori launchpad, see the following topics: Launching the Launchpad Customizing the Launchpad URL Establish a Connection from Back-End System to Front-End Server 3. Upload the custom logout page as a UI5 BSP Node, using Transaction Code SE38 and report /UI5/ UI5_REPOSITORY_LOAD. Note The custom logout page can be accessed as a BSP node. The custom logout page should be publically accessible, but the UI5 BSP node requires user authorization. A public node reference to the custom logout page must be created. 4. To create a custom logout page node, perform the following steps: a. Run transaction SICF. b. Select the Public Service Node s namespace /sap/public/bsp/sap. c. Open the Create Service Wizard icon. d. Accept the Warning and Hints messages. e. Select the Internal Alias radio button. f. Enter the Name and Description for the public custom logout page node. g. Choose the newly-created UI5 BSP Node and choose Continue. 5. Finally, redirect /sap/public/bc/icf/logoff to the custom logout page as follows: a. Run Transaction Code SCIF. b. Use the public custom logout page node s page as the /sap/public/bc/icf/logoff node s logoff page. Installation of FS-IPW Components P U BL IC 15
2.2.4.2 Configuring an External Alias for ICF Node to Redirect Logout to Custom Logout Page You need to configure an external alias for ICF node to redirect logout to custom logout page. Procedure 1. Login to ABAP front-end system and execute transaction SCIF. 2. Go to node /sap/public/bc/icf/logoff. 3. Once the service loads, go to Error Pages Logoff Page Redirect to URL. 4. Choose the pencil icon and enter the redirection URL as /sap/bc/ui5_ui5/ui2/ushell/shells/ abap/fiorilaunchpad.html. 5. Choose Save to save your entries. 6. If the wizard prompts for credentials, the password entry needs to be made here to complete the implementation. 7. Go to the Logon Data tab and clear the User and Password fields and choose Save again. 2.2.5 Roles and Authorizations Role and authorizations are configured on both the ABAP front-end server and the Java back-end server. On ABAP front-end servers, installing UIFSIPW 100 provides some roles for FS-IPW Fiori app access. These roles must not be used as-is. They can be copied to the Z namespace for customization. For example, Z_UI2_USER_700. There are also other Fiori Launchpad-related roles that are required by the platform and are documented in the Fiori Launchpad setup guide. The required ABAP roles are: Create Insurance Quote SAP_IPW_BCR_INSUW_T SAP_IPW_BCR_INSAGENT_T My Insurance Worklist SAP_IPW_BCR_INSUW_T SAP_IPW_BCR_INSAGENT_T My Underwriting Worklist SAP_IPW_BCR_INSUW_T Create Group Insurance Quote (Since SP02) SAP_IPW_BCR_INSUW_T SAP_IPW_BCR_INSAGENT_T My Insurance Tasks (Since SP02) SAP_IPW_BCR_INSUW_T SAP_IPW_BCR_INSAGENT_T Create Insurance Quote from Master (Since SP05) 16 P U B L I C Installation of FS-IPW Components
SAP_IPW_BCR_INSUW_T SAP_IPW_BCR_INSAGENT_T Create Master Insurance Quote (Since SP05) SAP_IPW_BCR_INSUW_T SAP_IPW_BCR_INSAGENT_T Caution Within each app, assign only one role to each user. On the Java back-end server, users will need to be assigned UME (User Management Engine) roles for quotation and underwriting OData service access by the FS-IPW Fiori apps. The required UME groups are as follows: SAP_UW_AUDIT SAP_UW_HOUSEHOLD SAP_UW_LIFE SAP_UW_SYSTEM The required back-end roles are as follows: Quotation Web (suggested user group: Agents, Underwriters) SAP_PQM_URL_QUO SAP_PQM_URL_EAPP Underwriting Web (suggested user group: Underwriters) Note SAP_PQM_URL_UW SAP_PQM_URL_EAPP These roles can also access the eapp runtime functions. The following roles can be created on demand to meet additional requirements: To allow a user to perform assigning submission operation, create SAMPLE_DATA_ENTRY_AGENT role and assign it to specific groups. To grant a user the write access to underwriting cases, create UWSUBMISSION_DATA_ENTRY role and assign it to specific groups. 2.2.6 Web Dispatcher Install the SAP Web Dispatcher 7.40 as the reverse proxy. For instructions, see http://help.sap.com/nw74 and navigate to Application Help Function-Oriented View Application Server Application Server Infrastructure Components of SAP NetWeaver Application Server SAP Web Dispatcher Administration of the SAP Web Dispatcher Operating the SAP Web Dispatcher Importing the SAP Web Dispatcher. For more information, see Configuring SAP Web Dispatcher on the SAP Help Portal at http://help.sap.com/ fiori_bs2013/helpdata/en/43/019d5254a43258e10000000a423f68/frameset.htm. Installation of FS-IPW Components P U BL IC 17
In addition, Web Dispatcher routing must be configured for FS-QUO. To configure the Web Dispatcher for FS- IPW, you must configure the ABAP front-end server and the Java back-end server as target systems. The routing rule for the ABAP target systems must include: /sap/ The routing rule for the Java target system must include: /logon_ui_resources/ /csiroot/ /pqm/ /ipw/ /uw/ /fs.ipw.myuwworklist/ 2.2.7 Client SAP Fiori apps are designed for both desktop and mobile device. A HTML5-capable web browser is recommended. For more information about supported combinations of device, browser and operating system, see SAP Note 1935915. For Android and ios devices, you can use SAP Fiori Client. This native application renders SAP Fiori application content, and provides more reliable asset caching. For ios, it additionally supplies an enhanced attachment viewing process. For more information about SAP Fiori Client, see SAP Help Portal at http://help.sap.com/fiori-client and choose SAP Fiori Client User Guide. 18 P U B L I C Installation of FS-IPW Components
3 Next Steps This section explains what you need to do after the installation or upgrade. In this release, the generation of sequential application number and policy number is supported, but it's disabled by default. To use this feature, you need to enable it in Administrative Console. For more information, see Chapter "SAP Workplaces for Insurance (IPW)" of the SAP Underwriting for Insurance Developer Guide. Next Steps P U B L I C 19
Important Disclaimers and Legal Information Hyperlinks Some links are classified by an icon and/or a mouseover text. These links provide additional information. About the icons: Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements with SAP) to this: The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information. SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct. Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information. Beta and Other Experimental Features Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the experimental features in a live operating environment or with data that has not been sufficiently backed up. The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP. Example Code Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example code unless damages have been caused by SAP's gross negligence or willful misconduct. Gender-Related Language We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders. 20 P U B L I C Important Disclaimers and Legal Information
Important Disclaimers and Legal Information P U BL IC 21
www.sap.com/contactsap 2018 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 https://www.sap.com/about/legal/trademark.html for additional trademark information and notices. THE BEST RUN