Integration Guide. Document Version:

Transcription

1 SAP Product Lifecycle Management for Insurance 3.0 SP03 FP2 SAP Underwriting for Insurance 3.0 SP03 FP2 SAP Policy Management 5.3 CUSTOMER Integration Guide Document Version:

2 Typographic Conventions Type Style Example Example EXAMPLE Example Example <Example> EXAMPLE Description 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. Emphasized words or expressions. 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. 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. Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. Keys on the keyboard, for example, F2 or ENTER. 2

3 Document History Document Version Date Change Initial Version. Document History 3

4 Table of Contents 1 Introduction About this Document References Required Releases for the Integration Naming Conventions Post-Installation Setup Checklist Setting up Connection for FS-PRO and FS-PM for Product Replication Configuring RFC Destinations in products Configuring RFC Destinations in NetWeaver Setting up Product Replication from FS-PM Prerequisites for IFBC Template Import Importing IFBC Templates Importing PBT Tables Manually adding precision values for currency fields Importing Non-IFBC Tables Importing CBO Tables Viewing the Import Log Using the PBT Schema Synchronization Performing Database Simulations Performing Database Synchronizations Setting Up Connection between FS-PRO and FS-PM for IFBC Creating a User for RFC Call and Granting Authorizations in FS-PM Configuring RFC Destinations in products Configuring RFC Destinations in NetWeaver Verifying Custom Publishing Services are Selected in FS-PRO Choosing Operation Mode for IFBC Import in FS-PRO Productive System Landscape Setting Up Connection between FS-PM and FS-PRO Runtime Customizations in SAP Policy Management Defining Product Module Groups for Runtime Adapter Assigning Implementation Classes to Product Engine Interfaces Technical Information for Integration Credential Handling from FS-PM to FS-PRO Creating a User in FS-PRO Authentication for PWS Providing a WSDL for PWS Endpoint at Customer Site Defining a Port for a PWS Provider Endpoint Setting Up Connection between FS-QUO and FS-PM Creating a User in FS-PM Table of Contents

5 6.2 Configuring the Connection in FS-QUO Configuring RFC Destinations in products Configuring RFC Destinations in NetWeaver Testing RFC destinations Use of XSLT Transformation Using the APIF Wrapper Using Native APIF Using the Business Partner Search Adapter in FS-PM Setting Up the Connection between FS-QUO and ERP-BP Creating a User Configuring the Connection in FS-QUO Configuring RFC Destinations in products Configuring RFC Destinations in NetWeaver Testing RFC destinations Product Configuration in FS-PRO Data Models SAP Insurance Reference Data Model SAP PnC Data Model and SAP LnA Insurance Data Model SAP PnC Combined Data Model and SAP LnA Combined Data Model Template Libraries Sample Household Product and Library Company Templates Inherited Templates for Main Axis Objects Inherited Templates for Lateral Objects Important Upgrade Consideration Product Configuration Configuring a Product in FS-PRO Creating Company-Level Templates Creating the Marketable Product Creating and Assembling Main Axis Objects Creating and Assembling Lateral Objects Test Rating Using Product Web Services Static Product Information for IFBC Types of Entities Provided IFBC Components in Product Configurator Location of the IFBC Components Configuring Static Product Information for IFBC Configuring Product-level IFBC Components Configuring Main Axis IFBC Components Configuring Lateral IFBC Components Configuring IFBC Integration Services Rating Configuring ratings in FS-PRO Rating Insurance Products Imported from FS-PM into FS-PQM using PMQ.Runtime Business Partners Configuring eapp for FS-QUO Integration Main eapp Configuration Components Configuring eapp Table of Contents 5

6 8.7.3 Configuring Product Hierarchy Configuring Policy eapp Configuring eapp for Other Main Axis Entities Configuring Questions and Views for Lateral Objects Configuring Questions and Views for Business Partners bplookup Stem Overview of Java Stems Using Stems Business Partner Address Configuring the Fields to Add an Insurable Object Configuring Multi-Level Risk Renderer Settings Removing the Renewals and Premium Audits Menu Options in FS-QUO Publishing a Product in FS-PRO Publish the Product, Send Structure Info, and Deploy Download the Generated XML File for IFBC IFBC Import of FS-PRO Product Data IFBC Import Product Module Group Customizing in FS-PM Assigning Business Transactions Enhancement Options Areas to be Enhanced in Different Systems Entities and Templates in FS-PRO Supported Enhancement Scenarios Using Entities Provided Out-of-the-Box Adding New Fields to an Out-of-the-Box Entity Adding New Fields in FS-PRO List of Provided Entities Appendix Terms for Included Open Source Software Table of Contents

7 1 Introduction 1.1 About this Document Use This document provides information on how to combine the following SAP for Insurance components to an integrated insurance solution for Product and Policy Lifecycle Management: SAP Product Lifecycle Management for Insurance (FS-PRO) for product configuration SAP Underwriting for Insurance (FS-QUO) for writing new business SAP Policy Management (FS-PM) for handling subsequent policy processing SAP ERP including Business Partner (ERP-BP) for providing and storing business partner data The document is aimed at system administrators or technical consultants to help them set up the relevant connections between the different components. Furthermore, it provides a guideline for product developers and business analysts on what needs to be considered when configuring and publishing an insurance product in FS-PRO that is designed to be consumed by FS-QUO and FS-PM. Section 8 of this guide describes how to configure a product in FS-PRO that can be consumed in FS-QUO (for new business) and FS-PM (for subsequent policy processing). Section 4 provides information on how to establish the connection between FS-PRO and FS-PM for transferring static product information, whereas the steps for publishing the product in FS-PRO and importing the data into IFBC are described in the subsequent sections. Section 5 deals with the configuration settings for the run-time adapter between FS-PM and FS-PRO runtime. It is explained how to establish the connection between FS-QUO and FS-PM in section 6. This connection will be used for transferring policy data from FS-QUO to FS-PM and for the business partner search in FS-QUO. Whereas creating new business partners or changing existing business partners is handled through a direct access to the component ERP-BP, which is described in section 7. Section 10 provides information on enhancement options for this integration scenario. In section 7, you can find additional information, such as the supported FS-PM entities in this integration scenario. Notes: The focus of this guide is on the specifics for the new integration scenario. The description of the already existing functions of FS-PRO, FS-QUO, and FS-PM is not part of this integration guide (see also the references in section 1.2). The product configuration topics in this document are intended for product developers and business analysts who are familiar with Product Configurator concepts and how to use it. Introduction 7

8 The following graphics outline all of the components with their relevant interfaces. In your implementation process, one of the initial design choices to make is to decide which rating engine to use. If you are using FS-PRO as your rating engine, see Diagram 1. If you are using msg.pm as your rating engine, see Diagram 2. For more information on configuring ratings in both scenarios, see section 8.5 Rating. Diagram 1: Integration Components for FS-PRO as the Rating Engine Diagram 2: Integration Components for msg.pm as the Rating Engine Explanation of diagrams 1. Define products in msg.pm Designer, and publish to FS-PM s IFBC. 2. Import PBT and IFBC product definitions to FS-PRO s Product Configurator. 8 Introduction

9 3. Publish products to FS-QUO. 4. Generate msg.pm runtime product rules file (QAR) in msg.pm Designer. 5. Create quotes in FS-QUO. 6. After issuing, manage policies in FS-PM. Prerequisites You have installed the following components: SAP Product Lifecycle Management for Insurance (FS-PRO) SAP Underwriting for Insurance (FS-QUO) SAP Policy Management (FS-PM) SAP ERP including Business Partner (ERP-BP) For more information, see the installation guides listed in section References Title Internet Address Description SAP Product Lifecycle Management for Insurance - Installation Guide SAP Underwriting for Insurance - Installation Guide SAP Product Lifecycle Management for Insurance - Product Configurator User Guide SAP Product Lifecycle Management for Insurance - Enterprise Deployment, Integration, and Administration User Guide SAP Underwriting for Insurance - Developer Guide SAP Policy Management - Installation Guide SAP Policy Management - Enhancement Guide -> SAP FS-PRO 3.0 -> 3.0 -> Installation Guide -> SAP FS-QUO 3.0 -> 3.0 -> Installation Guide -> SAP FS-PRO 3.0 -> 3.0 -> Product Configurator User Guide -> SAP FS-PRO 3.0 -> 3.0 -> Enterprise Deployment, Integration, and Administration Guide -> SAP FS-QUO 3.0 -> 3.0 -> Developer Guide Installation and Upgrade Information -> Installation Guide Additional Information -> How-To Guides and Additional Documentation - SAP Service Describes the installation process for the SAP component SAP Product Lifecycle Management for Insurance (FS-PRO) Describes the installation process for the SAP component SAP Underwriting for Insurance (FS-QUO) Describes the Product Configurator features and functionality Describes the administrative activities in FS-PRO Describes the FS-QUO architecture, how to extend the default FS-QUO behavior, and how to modify the configuration Describes the installation process for the SAP component SAP Policy Management (FSPM) Describes all enhancement options within SAP Policy Management Introduction 9

10 Title Internet Address Description Marketplace-> SAP FS-PM 5.3 Enhancement Guide. Master Guide SAP for Insurance Installation and Upgrade Information -> Master Guide Describes the deployment options for FS-PM running together with SAP ERP 1.3 Required Releases for the Integration You can use the integrated insurance solution for Product and Policy Lifecycle Management as of the following releases: SAP Product Lifecycle Management for Insurance (FS-PRO) 2.0, SP 06 (see also SAP Note ) SAP Underwriting for Insurance (FS-QUO) 2.0, SP 06 (see also SAP Note ) SAP Policy Management (FS-PM) 5.2, SP Naming Conventions In this documentation, the following naming conventions apply: Mapping of FS-PRO and FS-PM Terms In some cases, different terms are used in FS-PRO and FS-PM to describe the same concept. These terms are listed in the following table: Term in FS-PRO IFBC Column IFBC Control Attribute Term in FS-PM Characteristic (IFBC) Attribute (IFBC) Abbreviations In the following table, the most important abbreviations used in this integration guide are listed: Title SAP Policy Management SAP Product Lifecycle Management for Insurance SAP Underwriting for Insurance In-Force Business Configurator Application Interface Policy-Based Technology Enterprise Services Custom Business Object (ABAP term) Abbreviation FS-PM FS-PRO FS-QUO IFBC APIF PBT ES CBO 10 Introduction

11 1.5 Post-Installation Setup Checklist This document describes the post-installation steps that must be performed to complete the setup of an integrated environment with FS-PM, FS-PRO, and FS-QUO. After you complete these procedures, you can configure a product in FS-PRO or test the Sample Household Product Prerequisite: The standalone FS-PM, FS-PRO, and FS-QUO components must be successfully installed following the instructions in the Installation Guides. Post-Installation Procedure Role More Information 1 Set up a connection for FS-PRO and FS-PM for product replication. Note: If you are using product replication, you must configure IFBC settings in Admin Console. See section Set up the connection between FS-PRO and FS-PM for IFBC. 3 Set up the connection between FS-PM and FS-PRO Runtime. 4 Set up the connection between FS-QUO and FS-PM. Note: This procedure is required only if you are integrating FS-QUO with FS-PM and FS-PRO. 5 Set up the connection between FS-QUO and ERP-BP. Note: This procedure is required only if you are integrating FS-QUO with FS-PM and FS-PRO. 6 Set up Product Web Services and test rating. Note: This procedure is required for any product that you configure in FS-PRO. Complete this procedure before you test the Sample Household Product. 7 Configure the Multi-Level Risk Renderer settings in FS- QUO. Note: This procedure is required only if you are integrating FS-QUO with FS-PM and FS-PRO. For more information, see Configuring Multi-Level Risk Renderer Settings. 8 Configure Customizing settings for IFBC import in FS- PM. Notes: Do this procedure if you publish an existing product (such as the Sample Household Product) as part of the installation setup. Later, when you configure and publish your own products in FS-PRO, perform this step as needed. Technical Consultant or equivalent role Technical Consultant, System Administrator, or equivalent role Technical Consultant, System Administrator, or equivalent role Technical Consultant, System Administrator, or equivalent role Technical Consultant, System Administrator, or equivalent role Technical Consultant, System Administrator, or equivalent role Technical Consultant, System Administrator, or equivalent role Technical Consultant or equivalent role Chapter 2 (page 12) Chapter 4 (page 21) Chapter 5 (page 27) Chapter 6 (page 36) Chapter 7 (page 43) Section (page 64) Section (page 123) Chapter 10 (page 127) Introduction 11

12 2 Setting up Connection for FS-PRO and FS- PM for Product Replication This section describes how to set up the connection between FS-PM and FS-PRO for the replication of IFBC Templates into FS-PRO. This replication is triggered from the Tools Menu > Product Replication in FS-PRO. There are four items you can import: IFBC templates PBT channel model structures Non IFBC relevant entities (Global domain tables) CBO Customizing tables For more information on importing these items, see Setting up Product Replication from FS-PM (page 7). Before you can import, some pre-configuration steps are required. Data from FS-PM is transferred to FS-PRO by calling the RFC-enabled function modules. Before the function module can be called successfully, you must perform the following activities to set up the connection in FS-PRO: 2.1 Configuring RFC Destinations in products In order to let the system know which destination name will be used in the application, the NetWeaver destination names need to be defined in the product. 1. Login to FS-PRO and open the SAP Global Reference Object component. 2. Go to Configuration > Integration > RFC >Remote Function System. 3. A predefined set of system types are provided. You can used the default name or assign a name of your choosing. This will be the name of the RFC Destination that you will create in NetWeaver. System Type From System To System Destination Name ifbc FS-PRO FS-PM FSPM_DEST pbt FS-PRO FS-PM FSPM_DEST If the required system type is not listed, you will need to create a new row, with the new system type and a name. 4. Build the metadata and publish the SAP Global Reference Object. 2.2 Configuring RFC Destinations in NetWeaver You need to create RFC destinations for each product repository in your integration. You need to create at least two destinations: one for FS-PM and one for ERP-BP. By default the content is expecting a destination named BP_DEST and FSPM_DEST, these will need to be created unless you have modified the default destinations in the product. The 12 Setting up Connection for FS-PRO and FS-PM for Product Replication

13 destinations need to be created on the NetWeaver server where your application is deployed and need to be mapped in FS-PRO. 1. Login to NetWeaver. You must have Administrator permission on NetWeaver 2. Go to Configuration > Destinations. 3. On the General Data screen, specify the following information: o Hosting System Leave the default value selected by NetWeaver in place. o Destination Name Enter the name of the destination. The name must be unique and must be identical to the equivalent destination name that you created in products. Best practice is to use a naming convention that allows easy identification of the target instance. o Destination Type Select RFC as the destination type. 4. Click Next. 5. On the Connection and Transport Security screen, specify the following information: o Load Balancing Set this value to No. o Local System Connection Leave this value unchecked. o Target Name Enter the name of the host. This information can be found on the SAP Login screen. o System number Enter the system number of the target system. This information can be found in the Instance No. column on the SAP Login screen. o System ID Enter the system ID of the target system. This information can be found in the SID column on the SAP Login screen. o SNC Set this value to Inactive. 6. Click Next. 7. On the Logon Data screen, you can specify either a predefined service user or the current user. If you select to use the current user, then also specify whether a login ticket or an assertion ticket should be used for the authentication. Specify the following information: o Authentication Select a value from the dropdown. o Language Enter the short name for the appropriate language. o Client Enter the name of the client. This information can be found on the SAP Login screen. o User Name Enter the user name. o Password Enter the password for the specified user name. o Destination Name Select This Destination. 8. Click Next. 9. On the Pool Settings screen, select the Pooled Connection Mode checkmark. 10. Click Finish. 11. Test the connection. Select the new destination and click Ping Destination. Setting up Connection for FS-PRO and FS-PM for Product Replication 13

14 3 Setting up Product Replication from FS-PM You use out-of-the box templates to inherit from and create your own templates and use these for your IFBC template replication from FS-PM. There are four items you can import from FS-PM: IFBC templates PBT channel model structures Non-IFBC relevant entities (Global domain tables) CBO customizing tables Before you import, you must complete the following prerequisites: Configure RFC destinations in products (section 2.1) Configure RFCs destinations in NetWeaver (section 2.2) Configure IFBC Settings in FS-PRO Admin Console (section 2.3) Configure Prerequisites for IFBC Template Import (section 3.1) 3.1 Prerequisites for IFBC Template Import You must complete all preparation work before you can use IFBC import. Note: Only do these steps for the products you intend to import from FS-PM. 1. In Product Studio, go to the Product Repository. 2. Create a folder called Template Library and label the Modifier Type as Configuration Group. 3. In the Template Library folder, create a Components folder for the enum list import and label the Modifier Type as Component Folder. 4. In the Template Library folder, create a folder for each Object Modifier Type (from FS-PM). For example, Contracts, Coverages, Premiums, Policyholders, and so on. 14 Setting up Product Replication from FS-PM

15 5. Inside each folder you created, create one template using the following naming convention: 6. <Company Name><LoB><Object> template based on the SAP <LoB><Object> template. 7. Each folder should contain the template for the correct LoB and Object that you want to import such as LnA for Life Product Import or PnC for PnC Product Import. 8. For example, in the Premiums folder if you want to import a Life line business product, you must create a new object with the following details: o Name: ABC Company LnA Premium Template o Modifier Type: Premium o Based On: SAP LnA Premium Template There are three objects which are common across all lines of business, and their naming convention uses Common instead of LoB, such as the SAP Common Premium Payer Template. For these objects you must create a new object with the following details: o Name: ABC Company Common Premium Payer Template o Modifier Type: Premium Payer o Based On: SAP Common Premium Payer Template 9. For each template that you created, double-click the template to open it. 10. From the Product Tree, click the Identification folder, and select SAP <Object> id. 11. On the Values tab select the ProductModuleId column, and fill in the values for the product template IDs from FS-PM for the object category that you want to import. Note: If more than one template ID exists, use comma separation between each ID. 12. Repeat these steps for all objects you want to import. Important: Make sure all the templates (belonging to the Sales product that you are trying to import) are released in FS-PM before you attempt to import the product in FS-PRO. Setting up Product Replication from FS-PM 15

16 3.2 Importing IFBC Templates After you complete the prerequisites, you replicate the products that were created from the templates and then begin the template import process. To import IFBC templates in FS-PRO, do the following: 1. From the menu bar, click Tools, and select Product Replication. The Product Replication window appears. The IFBC Import tab contains a list of available FS-PM product templates that you can import. You can also search for a template by Template ID or Template Name. IFBC Import Column Descriptions Template ID Template Name Delta Check Identification number for the template Name of the FS-PM template that you can import Pop up window for Template Update that reconciles old and new templates and makes a recommendation whether or not to import. Note: You must perform an Import before you can do a Delta Check. A Delta Check does not delete templates; it just makes recommendations. See the following section, Performing a Delta Check. Last Import in FS-PRO Status Date and time when templates were last imported Status of the template (Success or Failed) 2. Select the templates that you want to import using the checkbox to the left of the Template ID column. 3. Click Import. Note: You can only import five products at a time. Otherwise, you receive an error message. Note that the import process could take some time if the templates have a large amount of content. 4. Perform a Delta Check, if necessary. The Delta check tells you when the product was last imported and updated and makes sure that FS-PM and FS- PRO have the same version of the product. A Delta Check does not delete templates; it just makes recommendations. You must manually delete templates, if needed. Performing a Delta Check When you click the icon in the Delta Check column, the Template Update window appears with the following information. Template Update Column Descriptions Template ID Template Name Last Update in FS-PM Last Import in FS-PRO Import Required Identification number for the template Name of the FS-PM template that you can import Date and time when templates were last updated Date and time when templates were last imported System recommendation if import is required 16 Setting up Product Replication from FS-PM

17 3.3 Importing PBT Tables On the PBT Import tab, you import PBT tables. If you do not see the table you want, you can also search for a table by Table Description. Note: Once you import a column the first time in FS-PRO, any changes you make to this column in FS-PM must be done manually in FS-PRO. 1. Select the templates that you want to import using the checkbox to the left of the Table Description column. Note: If you want to import any tables that are not in the list contact SAP development. 2. Click Import. Important: Do not delete any items from the system repository or issues can occur. SAP is not responsible for items you delete from the system repository. PBT Import Column Descriptions Table Description Table Name Name of entity that you are importing from FS-PM Name of the table you are importing. Each Table Name begins with one of the following prefixes, based on the type of product: ABDA Basis APDA PnC ALDA Life MDA Auto SAP Data Definition Name Location where the columns are getting stored. Note: You can import new columns that you added to the table in FS-PM. Last Import in FS-PRO Status Date and time when templates were last imported Status of the template (Success or Failed) Manually adding precision values for currency fields For PBT Import to work with multi-currency, you must manually add precision values for the following columns: DEBIT_AM MACCCOSTS_AM BPML_AM To manually add precision for currency fields, do the following: 1. Add the precision values for the following areas: Product area Precision values to add Product Configurator data definitions SAP DD Manual Cost Posting Template > Column > DEBIT_AM SAP DD Manual Cost Posting Template > Column > MACCCOSTS_AM SAP DD Coverage > Column > BPML_AM Setting up Product Replication from FS-PM 17

18 Product area Precision values to add Designer flowstore ABDAMACOST > DEBIT_AM ABDAMACOST > MACCCOSTS_AM ABDACOV > BPML_AM Note: 2 is the amount you must specify for precision. 2. After you added the precision values, build and synch the flowstore to update your database. Important: Sync flowstore will require attention from a database administrator since the precision will increase without increasing the overall data length. Your database administrator must alter the column precision and also perform some temporary data porting for any existing data due to the precision changes on existing columns. For more information, see the SAP Note: due to the precision changes on existing columns, there is a manually steps to change them. 3.4 Importing Non-IFBC Tables On the Non-IFBC Import tab, you import Non-IFBC tables. Note: Initially, the window takes time to populate. Once populated, the table data appears. If you do not see the table you want, you can also search for a table by Table Description. Italicized names are out-of-the-box tables, and tables you imported are non-italicized. 1. Select the templates you want to import using the checkbox to the left of the Table Description column. There is no limit to how many tables you can import. Note: If you want to import any tables that are not in the list contact SAP development. 2. Click Import. Important: Do not delete any items from the system repository or issues can occur. SAP is not responsible for items you delete from the system repository. Non-IFBC Import Column Descriptions Table Description Table Name Name of entity that you are importing from FS-PM Name of the table you are importing. Note: If you are importing tables that begin with the letter T (for example, T006), the import process takes time. Last Import in FS-PRO Status Date and time when templates were last imported Status of the template (Success or Failed) 18 Setting up Product Replication from FS-PM

19 3.5 Importing CBO Tables On the CBO Import tab, you import CBO tables. 1. (Optional) SAP provides an out-of-the-box object called SAP Extended Global Reference Object in the Template Library. This is where the imported CBO tables are stored. You can change the name of this object, if you prefer. If you change the name of the object, then you must configure the new name in Admin Console so that the CBO import works correctly. To do this, complete the following steps in this order: o On the System tab, select the Configuration folder and navigate to Configuration > PC > Env > IFBC Replication Setting. o On the table that appears, in the Name column, find ExtendedGlobalRefOjbect. The default column lists the system default name. o In the Override column, type the new name that you want to call the object, and click Save. 2. Type the name of the table you want to import. If there is more than one table, then separate the table names with a comma. 3. Click Import and the CBO table is imported. 3.6 Viewing the Import Log The import log helps you understand the status of the template import process. It tells you what was imported, how much time it took to import, and why it failed (if not succeeded). [INFO] gives you general status information on the import. [SEVERE] tells you why the import failed. 3.7 Using the PBT Schema Synchronization The PBT Schema Synchronization performs an analysis of the differences between the remote system and your SAP system. You perform either of the following functions: Simulation to review database table differences before any changes or reconciliations are made. Synchronization to perform a database synchronization immediately. Note: SAP recommends you perform a simulation before you synchronize your databases Performing Database Simulations To run a database simulation before synchronizing, do the following: 1. Log into the SAP Product Lifecycle Management for Insurance Administrative Console. 2. Go to Product > PBT Schema Synchronization. A PTB Schema Synchronization dialog box appears with options to simulate or synchronize. 3. Click Simulate. o If there were no errors in the simulation, you receive the following message: No issues found in test simulation. You may now perform the actual synchronization. Setting up Product Replication from FS-PM 19

20 o If there were errors in the simulation, you can review those errors and make any updates before running the synchronization Performing Database Synchronizations To synchronize the databases, do the following: 1. Log into the SAP Product Lifecycle Management for Insurance Administrative Console. 2. Go to Product > PBT Schema Synchronization. A PTB Schema Synchronization dialog box appears with options to simulate or synchronize. 3. Click Synchronize. o If there were no errors in the synchronization process, you receive the following message: Successfully synchronized schema. Please build metadata to complete the entire process. o If there were errors, you must fix the errors and repeat the synchronization process. 4. To build metadata, see "Building all objects of a type" in the SAP Product Lifecycle Management for Insurance Product Configurator User Guide. 20 Setting up Product Replication from FS-PM

21 4 Setting Up Connection between FS-PRO and FS-PM for IFBC This section describes how to set up the connection between FS-PRO and FS-PM for the replication of static product data to IFBC. This replication consists of the following steps: 1. In FS-PRO: Send the IFBC structure with the static data of a marketable product to FS-PM. 2. In FS-PM: Data is stored in the import buffer. 3. In FS-PM: Perform the IFBC import. Before you can perform these steps, some preparatory configuration steps are required. Data from FS-PRO is transferred to FS-PM and imported to IFBC by calling the RFC-enabled function module /PM0/ABC_IBC_RECEIVE_GNRL. This function module is called if you publish a marketable product and the IFBC structure is sent to FS-PM. Before the function module can be called successfully, you must perform the activities described in the following subsections. 4.1 Creating a User for RFC Call and Granting Authorizations in FS-PM Note: The user must have the authorizations for the following activities: Temporary storage of product deliveries in import buffer triggered by sending the IFBC structure from FS-PRO to FS-PM Execution of the IFBC import, including permission for writing transport entries and creating log entries To create the user for the RFC call with these two required authorizations, proceed as follows in FS-PM: 1. Call up transaction SU Create the appropriate user. Note: In the following documentation, only those settings are described that are relevant for the integration of FS- PRO and FS-PM. 3. On the Logon Data tab, enter System in User Type field (the user should be a system user, not a dialog user). In all other fields, you can enter the values according to your requirements. 4. On the Roles tab, create a new role and grant the relevant authorizations (see the subsequent steps). 5. Double-click the relevant Role field. 6. Choose the Authorizations tab. 7. In the Maintain Authorization Data and Generate Profiles section, choose Change Authorization Data. 8. Create the authorizations as described in the following table: Authorization Object Field Assigned Value(s) S_RFC (Authorization Check for RFC Access) ACTVT (Activity) RFC_NAME (Name (Whitelist) of RFC object to which access is allowed) 16 (Execute) /PM0/ABC_IBC_RECEIVE_GNRL Setting Up Connection between FS-PRO and FS-PM for IFBC 21

22 Authorization Object Field Assigned Value(s) S_DATASET (Authorization for file access) S_TRANSPRT (Transport Organizer) RFC_TYPE (Type of RFC object to which access is to be allowed) ACTVT (Activity) FILENAME (Physical file name) PROGRAM (Program Name with Search Help) ACTVT (Activity) TTYPE Request Type (Change and Transport System) FUNC 34 (Write) * (no specific entry required) SAPLSTRF 01 (Create or generate) CUST TASK /PM0/IBCT (FS-PM: Template for In-Force Business Configurator) /PM0/APPLI (Application ID) /PM0/ENTIT (Entity ID) * POLICY /PM0/OPERA (Template Operation) AIM DEL IMP LOG REL /PM0/TMPID (Template ID) * /PM0/TMPTY (Template Type) * 9. Save the data. 4.2 Configuring RFC Destinations in products In order to let the system know which destination name will be used in the application, the NetWeaver destination names need to be defined in the product. 1. Login to FS-PRO and open the SAP Global Reference Object component. 2. Go to Configuration > Integration > RFC >Remote Function System. 3. A predefined set of system types are provided. You can used the default name or assign a name of your choosing. This will be the name of the RFC Destination that you will create in NetWeaver. System Type From System To System Destination Name ifbc FS-PRO FS-PM FSPM_DEST pbt FS-PRO FS-PM FSPM_DEST If the required system type is not listed, you will need to create a new row, with the new system type and a name. 4. Build the metadata and publish the SAP Global Reference Object. 22 Setting Up Connection between FS-PRO and FS-PM for IFBC

23 4.3 Configuring RFC Destinations in NetWeaver You need to create RFC destinations for each product repository in your integration. You need to create at least two destinations: one for FS-PM and one for ERP-BP. The destinations need to be created on the NetWeaver server where your application is deployed and need to be mapped in FS-PRO. 1. Login to NetWeaver. You must have Administrator permission on NetWeaver 2. Go to Configuration > Destinations. 3. On the General Data screen, specify the following information: o Hosting System Leave the default value selected by NetWeaver in place. o Destination Name Enter the name of the destination. The name must be unique and must be identical to the equivalent destination name that you created in products. Best practice is to use a naming convention that allows easy identification of the target instance. o Destination Type Select RFC as the destination type. 4. Click Next. 5. On the Connection and Transport Security screen, specify the following information: o Load Balancing Set this value to No. o Local System Connection Leave this value unchecked. o Target Name Enter the name of the host. This information can be found on the SAP Login screen. o System number Enter the system number of the target system. This information can be found in the Instance No. column on the SAP Login screen. o System ID Enter the system ID of the target system. This information can be found in the SID column on the SAP Login screen. o SNC Set this value to Inactive. 6. Click Next. 7. On the Logon Data screen, you can specify either a predefined service user or the current user. If you select to use the current user, then also specify whether a login ticket or an assertion ticket should be used for the authentication. Specify the following information: o Authentication Select a value from the dropdown. o Language Enter the short name for the appropriate language. o Client Enter the name of the client. This information can be found on the SAP Login screen. o User Name Enter the user name. o Password Enter the password for the specified user name. o Destination Name Select This Destination. 8. Click Next. 9. On the Pool Settings screen, select the Pooled Connection Mode checkmark. 10. Click Finish. 11. Test the connection. Select the new destination and click Ping Destination. Setting Up Connection between FS-PRO and FS-PM for IFBC 23

24 4.4 Verifying Custom Publishing Services are Selected in FS-PRO The SAP Insurance UWA Product Template object provides the following services that you can run immediately after a product is published: Send Structure Info to IFBC Runs the rules in the IFBC Integration Services API in each entity to generate the XML structure that IFBC needs. Upload & Deploy to Runtime Uploads the published product JAR to the product repository and deploys it to the Runtime environment of the Product Web Services Manager. The WSDL is generated with the deployment. By default, these services are selected so that they appear in the Publish dialog. You can choose these services when you publish the product. Before you publish a product for the first time, check that these services are selected in your product. Proceed as follows: 1. In Product Configurator, open your marketable product, and go to the following location: [My Marketable Product] > Configuration > Product Services > Custom Publishing 2. In the Values tab, check that the Send Structure Info to IFBC and Upload & Deploy to Runtime services are selected. 4.5 Choosing Operation Mode for IFBC Import in FS-PRO In FS-PRO, you must choose the operation mode for the IFBC import. The following operation modes for the IFBC import are possible: IV_IMPORT_MODE_CD = '0': This operation mode only tests the RFC interface (/PM0/ABC_IBC_RECEIVE_GNRL). No data will be stored in the import buffer and thus no data can be imported into IFBC. IV_IMPORT_MODE_CD = '1': This operation mode stores data in the import buffer. You can import these stored data only manually into IFBC at a later time. IV_IMPORT_MODE_CD = '2': This operation mode stores data in the import buffer and starts the IFBC import automatically in simulation mode. You can perform the IFBC import manually as an update run at a later time. IV_IMPORT_MODE_CD = '3': This operation mode stores data in the import buffer and starts the IFBC import automatically as an update run. Where to choose the operation mode See section When to use which operation mode Use operation mode '3' if there is no indication that unexpected side effects may occur, for example after minor changes to product modules on the FS-PRO side. Use operation modes '1' and '2' during the development of new products to keep the risk low that the automatic import of a new product invalidates existing product templates. 24 Setting Up Connection between FS-PRO and FS-PM for IFBC

25 4.6 Productive System Landscape For the integration of FS-PRO and FS-PM, a productive system landscape should consist of the following ABAP systems: development system consolidation or quality system production system If you send the IFBC structure from FS-PRO to FS-PM, the data should be sent to an appropriate client of the development system. This client must be able to forward IFBC content to subsequent systems in the landscape (for instance, through the consolidation system to the production system). Consequently, the client must be set up in a way that it enables it to handle transport requests. To ensure this, do the following: 1. Check the client settings in the development system as follows: 12. Call up transaction SCC Select the relevant client. 14. Choose (Details). 15. In Changes and Transports for Client-Specific Objects section, ensure that the Automatic recording of changes radio button is selected (see screenshot below). Only if this is not the case, perform the following step Configure IFBC for mandatory transports. To do so, proceed as follows: 1. Choose Define Template Type in Customizing for Policy Management under In-Force Business Management Basis In-Force Business Configurator. Setting Up Connection between FS-PRO and FS-PM for IFBC 25

26 2. For the application ID Policy and template type 1 (Product Template), set the transport options to Transport mandatory (see graphic below). Once the systems are set up, the publishing of a marketable product in FS-PRO leads to the creation of a transport request. This transport request must be released in the development system once the product templates fulfill the requirements of the product model. Afterwards, you can verify the quality in the consolidation system. Once all of the tests that you have performed with your product have the green status, the collected transports can be sent out to the production system. 26 Setting Up Connection between FS-PRO and FS-PM for IFBC

27 5 Setting Up Connection between FS-PM and FS-PRO Runtime 5.1 Customizations in SAP Policy Management To make the runtime of the product engine FS-PRO available for rating calls from FS-PM you must perform the following customizations: Define Product Module Groups (for runtime adapter) Assign Implementation Classes to Product Engine Interfaces Defining Product Module Groups for Runtime Adapter You can find the Customizing activity Define Product Module Groups in Customizing for Policy Management under In- Force Business Management -> Basis -> Basic Settings. Make the following entries in the Customizing activity: 1. Select the group dimension INTPM (Integration of Product Manager) and double-click Assign Product Model Class to Group Dimension. 2. Select the product model class PRODUKT and make the following entries: 1. At Product Module Groups level, define a product module group, such as FSPRO. 2. At Assignment of Product Module ID to PBS Groups level, assign the product module ID _CONHHLD to product module group FSPRO. 3. Select the product model class VERKAUFSPRODUKT and make the following entries: 1. At Product Module Groups level, define a product module group, such as FSPRO. 2. At Assignment of Product Module ID to PBS Groups level, assign the product module ID _POLHHLD to product module group FSPRO. Note: The two values _CONHHLD and _POLHHLD refer to the control attribute Product Module ID in the product templates for the contract and for the policy provided by FS-PRO for the sample product 'Sample Household Product' Assigning Implementation Classes to Product Engine Interfaces You can find the Customizing activity Assign Implementation Classes to Product Engine Interfaces in Customizing for Policy Management under Integration -> Product Engine. Make the following entries for the new product module group FSPRO (which means the product engine FS-PRO): Interface Name Entity Implementation Class to Be Assigned /PM0/IF_ABR_PM_UTILITY (Analyzes IFBC entries at runtime) /PM0/ABDAPOLICY /PM0/CL_ABH_PM_UTILITY Setting Up Connection between FS-PM and FS-PRO Runtime 27

28 Interface Name Entity Implementation Class to Be Assigned /PM0/IF_ABR_PM_UTILITY (Analyzes IFBC entries at runtime) /PM0/IF_APP_MAP_PRO (Implementation of the mapping for the service request and service response) /PM0/IF_APR_PM_CALCULATION (Product engine interface that is called from within FS-PM) /PM0/ABDAPOLPR /PM0/ABDAPOLICY /PM0/ABDAPOLPR /PM0/CL_ABH_PM_UTILITY /PM0/CL_APP_MAP_PRO /PM0/CL_APH_PM_CALCULATION_PRO Note: The Entity field determines if the product module group is interpreted as product module group on sales product level (corresponds to entity /PM0/ABDAPOLICY) or as product module group on product level (corresponds with entity /PM0/ABDAPOLPR). 5.2 Technical Information for Integration All entity structures in the Service Consumer PRODUCT (ABAP Class /PM0/CO_PROXY_PWS_PRO) contain the field RUNTIME_OBJECT_ID. This field identifies each entity instance. CREATE: In case FS-PRO creates a new entity (for instance, it attaches a new clause), the value of the field RUNTIME_OBJECT_ID is initial. CHANGE: The RUNTIME_OBJECT_ID that is passed from FS-PM to FS-PRO must remain unchanged in FS-PRO. DELETE: If an entity instance is passed from FS-PM to FS-PRO, but not returned to FS-PM, it will be deleted in FS-PM. Processing of Entities In the following table, you can find a description of how any product engine should process the FS-PM entities. For example: In the operation PCRATING, the product engine is not allowed to insert or delete a coverage. However, the product engine is allowed to update a coverage. In the operation PCRATING, the product engine is allowed to insert, update, and delete a clause. 28 Setting Up Connection between FS-PM and FS-PRO Runtime

29 5.3 Credential Handling from FS-PM to FS-PRO This section describes the configuration of the point-to-point connection between the FS-QUO/FS-PRO product web service (PWS) provider and the corresponding FS-PM product web service consumer. The PWS is a SOAP web service. The service interface contains five synchronous service operations. They follow a query response Enterprise Service Transaction Communication pattern. In particular, no data from FS-PM is persisted in FS-PRO. However, the PWS is not an SAP Enterprise Service. The definition of the PWS is maintained locally in FS- PRO and not in the Enterprise Service Repository. In the following graphic, you can see the PWS in both systems and the corresponding service operations: FS-PM Deployment Unit Insurance Policy Management Process Component Product Web Service Interface Outbound PC_RATING_WS Outbound Operation pcratingwsrequest pcratingwsresponse FS-PRO Deployment Unit Rating Engine Process Component Product Web Service Interface Inbound pcratingws Inbound Operation Property And Casulty Insurance Application PC_MOD_CONTRACT_WS Outbound Operation PC_ADJUSTMENT_WS Outbound Operation pcmodcontractwsrequest pcmodcontractwsresponse pcadjustmentwsrequest pcadjustmentwsresponse pcmodcontractws Inbound Operation pcadjustmentws Inbound Operation Rating PC_MIGRATION_WS Outbound Operation pcmigrationwsrequest pcmigrationwsresponse pcmigrationws Inbound Operation PC_ACCOUNT_REP_VAL_ WS Outbound Operation pcaccountrepvalwsrequest pcaccountrepvalwsresponse pcaccountrepvalws Inbound Operation Setting Up Connection between FS-PM and FS-PRO Runtime 29

30 FS-PRO implements a PWS. FS-PM implements the counterpart consumer PWS /PM0/CO_PROXY_PWS_PRO. This consumer PWS is part of FS-PM standard implementation and does not need to be created on the customer side Creating a User in FS-PRO The SOAP message requires a FS-PRO user name and password. You can create a user in the Role Painter of the Product Configurator Administrative Console. Note: In the Job Title panel, select System. This category includes the authentication required for product web services. For information about creating a user in FS-PRO, see the topic about adding new employees to job titles in the Enterprise Deployment, Integration, and Administration User Guide Authentication for PWS A message-based authentication is required for the PWS. User credentials such as user name and password are passed in the wsse header of a SOAP envelope. In case of an HTTP request, the SOAP envelope is embedded in the HTTP body. A SOAP action in the SOAP header specifies the required service operation. HTTP Message Structure using SOAP HTTP Header Body Request Response Line MIME Header MIME Field Name:value POST HTTP/1.0 Authorization Header is a Mime Header Authorization: Basic d2lratpwzwrpyq== <Username:Password> Base64bit SOAPAction: Trailer SOAP Envelope.. <wsse:security. SOAP Header <wsse:usernametokenwsu:id="usernametoken-1"> <wsse:username>muster</wsse:username> <wsse:password>*********</wsse:password> </wsse:usernametoken> </wsse:security>.. SOAP Body Maintenance and, in particular, the adding of credentials for a point-to-point connection is handled by defining a logical port in the FS-PM system of a customer system landscape (see section 5.3.3). The logical port represents the counterpart consumer of the PWS provider FS-PRO system of a customer system landscape. 30 Setting Up Connection between FS-PM and FS-PRO Runtime

31 SOAMANAGER generates a port based on a concrete (binding) Web Services Description Language (WSDL) for an endpoint. It contains the following information: Functional descriptions Transport binding information, such as the URL and access path Product web service - policy information Providing a WSDL for PWS Endpoint at Customer Site You must create and store a concrete (binding) WSDL for an FS-PRO PWS endpoint at the customer site. Note: Before you generate the WSDL, check that the following settings are configured: In the FS-PRO Administrative Console, the location of the Product Web Services Manager is specified, and the PrePostPublishingEnabled setting is set to Yes. For information about these settings, see about configuring Product Web Services Manager in the SAP Product Lifecycle Management for Insurance Installation Guide. In Product Configurator, the Upload & Deploy to Runtime service is selected in your marketable product's Custom Publishing component. For information about this component, see Verifying Custom Publishing Services are Selected in FS-PRO (page 23). Proceed as follows: 1. In Product Configurator, publish the product. Note: For information about publishing the product, see Publish the Product, Send Structure Info, and Deploy (page 125). 2. Log in to the FS-PRO Administrative Console at the following address: 3. Go to the following location: Product > Manage Product Web Services 4. Choose the Runtime tab. In the left panel, choose the name of your product (for example, Sample Household ProductA web service document appears in the right panel. Setting Up Connection between FS-PM and FS-PRO Runtime 31

32 5. Click WSDL. The following example shows the link: A browser appears, showing the WSDL file. 6. Copy the URL from the browser address bar. This URL is required when defining a port for a PWS provider endpoint (see chapter 5.3.4) Defining a Port for a PWS Provider Endpoint As a prerequisite for maintenance and adding credentials for a point-to-point connection, you must define a port for a PWS provider endpoint. To do so, proceed as follows: 1. Call up transaction SOAMANAGER in FS-PM. 2. On the Service Administration tab, click Web Service Configuration. The Web Service Configuration screen appears. 3. In the Search Criteria section, enter the object name /PM0/CO_PROXY_PWS_PRO and choose Search. 4. In the Search Result section, click the internal name /PM0/CO_PROXY_PWS_PRO. 32 Setting Up Connection between FS-PM and FS-PRO Runtime

33 5. On the Configurations tab, choose Create and then WSDL Based Configuration. 6. Enter the Logical Port Name according to your requirements. If required, select the Logical Port is Default checkbox and choose Next. Note: A single logical port must be defined as the default port. 7. Read the PWS concrete (binding) WSDL. To do so, enter the URL and the credentials (user name and password) for WSDL access. Note: You can find the URL of the WSDL location in FS-PRO Administration Console (see section 5.3.3). Setting Up Connection between FS-PM and FS-PRO Runtime 33

34 8. Select the binding entry in the Overview of Possible Combinations Identified by WSDL Document section. 9. Enter the credentials (user name and password) for the SOAP message-based authentication. 34 Setting Up Connection between FS-PM and FS-PRO Runtime

35 10. If required, adjust the transport binding data. For example, if you change the URL protocol information, you must adapt the port accordingly. 11. On the next tabs, choose Next until you reach the Operation Settings tab. Choose Finish. Setting Up Connection between FS-PM and FS-PRO Runtime 35

36 6 Setting Up Connection between FS-QUO and FS-PM This section describes the following topics: Creating a User in FS-PM Configuring the Connection in FS-QUO Use of XSLT Transformation Use of APIF Wrapper Using a Business Partner Search Adapter in FS-PM Note: These procedures are required only if you are integrating FS-QUO with FS-PM and FS-PRO. 6.1 Creating a User in FS-PM Create the appropriate user using transaction SU01. You can find the relevant authorizations in the following template roles: SAP_FSPM_S_TMPL_CONSUME_RFC (FS-PM: Use of Remote Function Call-Modules); Function Group /PM0/ABT_APIF_WRAPPER SAP_FSPM_S_TMPL_CREATE_POLICY (FS-PM: Create Policy) SAP_FSPM_S_TMPL_DISPLAY_POLICY (FS-PM: Display Policy) SAP_FSPM_S_TMPL_MNG_INS_OBJ (FS-PM: Edit Insurable Object) To find the template roles, proceed as follows: 1. Call up transaction PFCG. 2. Enter the relevant role and choose (Display) 3. On the Authorizations tab, choose Display Authorization Data. Note: For the connection between FS-QUO and FS-PM, the relevant function group is /PM0/ABT_APIF_WRAPPER (template role SAP_FSPM_S_TMPL_CONSUME_RFC). 6.2 Configuring the Connection in FS-QUO To send policy XML from FS-QUO to FS-PM, you must configure FS-QUO with the proper connection details. Proceed as follows: 1. Log in to the FS-QUO Administrative Console at the following address: 2. Go to the following location: Configuration > Application > AuthoritySuite > Env > FS-PM Integration Setting 36 Setting Up Connection between FS-QUO and FS-PM

37 3. For each row, set the Override field to a value that corresponds to the FS-PM environment, and save. Notes: o You do not have to set an override value for parameters that start with jco.client. These parameters have been functionally replaced with RFC destinations and are no longer used, except if you have legacy configurations using JCo version 2.1. o Get the values to enter from FS-PM. The values must match in both environments. o The FS-PM database only allows three login attempts using the jco.client.user and jco.client.passwd values. If the login fails after three attempts, the database access locks and you will need to contact the DBA. 4. In the tree, go to the following location: Configuration > Application > AuthoritySuite > Env > Application Environment 5. Find the FSPMEnabled row, set the Override field to Yes, and save. 6. Reload the configuration settings. 6.3 Configuring RFC Destinations in products In order to let the system know which destination name will be used in the application, the NetWeaver destination names need to be defined in the product. 1. Login to FS-PRO and open the SAP Global Reference Object component. 2. Go to Configuration > Integration > RFC >Remote Function System. 3. A predefined set of system types are provided. You can used the default name or assign a name of your choosing. This will be the name of the RFC Destination that you will create in NetWeaver. System Type From System To System Destination Name policy FS-QUO FS-PM FSPM_DEST insuobj FS-QUO FS-PM FSPM_DEST bpartner FS-QUO ERP-BP BP_DEST searchhelp FS-QUO FS-PM FSPM_DEST generic FS-QUO FS-PMBP FSPM_DEST If the required system type is not listed, you will need to create a new row, with the new system type and a name. 4. Build the metadata and publish the SAP Global Reference Object. 6.4 Configuring RFC Destinations in NetWeaver You need to create RFC destinations for each product repository in your integration. You need to create at least two destinations: one for FS-PM and one for ERP-BP. The destinations need to be created on the NetWeaver server where your application is deployed and need to be mapped in FS-PRO. 1. Login to NetWeaver. You must have Administrator permission on NetWeaver 2. Go to Configuration > Destinations. 3. On the General Data screen, specify the following information: Setting Up Connection between FS-QUO and FS-PM 37

38 o Hosting System Leave the default value selected by NetWeaver in place. o Destination Name Enter the name of the destination. The name must be unique and must be identical to the equivalent destination name that you created in products. Best practice is to use a naming convention that allows easy identification of the target instance. o Destination Type Select RFC as the destination type. 4. Click Next. 5. On the Connection and Transport Security screen, specify the following information: o Load Balancing Set this value to No. o Local System Connection Leave this value unchecked. o Target Name Enter the name of the host. This information can be found on the SAP Login screen. o System number Enter the system number of the target system. This information can be found in the Instance No. column on the SAP Login screen. o System ID Enter the system ID of the target system. This information can be found in the SID column on the SAP Login screen. o SNC Set this value to Inactive. 6. Click Next. 7. On the Logon Data screen, you can specify either a predefined service user or the current user. If you select to use the current user, then also specify whether a login ticket or an assertion ticket should be used for the authentication. Specify the following information: o Authentication Select a value from the dropdown. o Language Enter the short name for the appropriate language. o Client Enter the name of the client. This information can be found on the SAP Login screen. o User Name Enter the user name. o Password Enter the password for the specified user name. o Destination Name Select This Destination. 8. Click Next. 9. On the Pool Settings screen, select the Pooled Connection Mode checkmark. 10. Click Finish. 11. Test the connection. Select the new destination and click Ping Destination. 6.5 Testing RFC destinations You can verify that the connectivity defined in the destinations is functional. 1. Log in to the FS-QUO Administrative Console at the following address: 2. Select System > Test SAP Server Connectivity. 3. Go to the Test JCo3 Feature tab, select the destination and click Connect to test the connection. 4. Repeat these steps for all destinations. 5. A pop up message indicates whether the connection is valid or invalid. 38 Setting Up Connection between FS-QUO and FS-PM

39 6.6 Use of XSLT Transformation In an integrated environment with FS-PM, when a producer or underwriter issues a policy in FS-QUO, a policy XML is generated. To create a corresponding policy in FS-PM, the following occurs: When a policy is bound in FS-QUO, FS-QUO sets the composite keys that FS-PM needs in the URS (memory representation of the policy model), FS-QUO gets the values for the composite keys from the product tables. To determine which values to get, FS-QUO references the APIF Composite Key Configuration component in Product Configurator. The following figure shows the composite key configuration for the ABDAAGENT table: FS-QUO populates the AGENT_ID column of the ABDAAGENT table in the URS with the unique identifier, PK_ID, from the ABDAAGENT product table. FS-QUO also populates the POLICY_ID column of the ABDAAGENT table in the URS with the SECPOL_ID of ABDAAGENT product table's parent. By default, personal P and C products are configured to reference the SAP Global Reference Object that contains the APIF Composite Key Configuration component. This reference is configured using the GlobalReferenceProductName key in the following component: [Marketable Product] > Configuration > Config Notes: o The APIF Composite Key Configuration component is already configured with the entities that are used for household products. You do not need to modify this component when configuring household products. o For more information about the APIF Composite Key Configuration component, see the Product Model Help. FS-QUO creates the policy XML from the URS. FS-QUO uses XSLT to transform the policy XML into a format that FS-PM can consume. FS-QUO provides an XSL style sheet that includes the entities used for Sample Household. The transformed data is sent to FS-PM using APIF. Note: If you want to add a field to FS-QUO, you must modify the XSL style sheet. For more information about the steps involved in this enhancement scenario, contact your SAP implementation team or SAP Support. Setting Up Connection between FS-QUO and FS-PM 39

40 6.7 Using the APIF Wrapper If a product uses FS-PRO as the rating engine, then APIF Wrapper must be used. This section described how a quote which was created in FS-QUO is processed in FS-PM to create a policy in FS-PM. FS-PM uses the product module ID/PM_ID to find the appropriate product template in IFBC. However, FS-QUO does not know this product module ID/PM_ID but uses the product base ID/template ID (received from FS-PRO) to determine the product template. To merge both IDs (product base ID/template ID in FS-PRO/FS-QUO and product module ID/PM_ID in FS-PM), the APIF wrapper was created in FS-PM, which is realized in the function module /PM0/ABT_APIF_WRAPPER. This function module can handle the product base ID/template ID and it derives the proper product module ID/PM_ID for IFBC. The APIF wrapper works as follows: The APIF Wrapper can only be used in the integration scenario between FS-QUO and FS-PM. All other scenarios are not supported. The call of the APIF Wrapper only works for single policy processing. Mass processing is not supported. You can only create new policies with the APIF Wrapper. If an error occurs during creation of a new policy, the application will not be saved, and no application log will be created. You receive error messages in the corresponding parameter of the wrapper to correct the delivered data in FS-QUO. The call of the function module is synchronous. This means if the connection is lost, FS-QUO has to check whether the policy was created. To do this, you have the following options in FS-QUO: o You implement a read functionality in FS-QUO to search for the policy in FS-PM. o FS-QUO sends the quote once again through the APIF Wrapper. The APIF Wrapper checks if the FS-QUO quote in question already exists in FS-PM (as a policy). If this is the case, a success message with the existing policy is returned. To check if the policy has been created, FS-PM provides the BAdI /PM0/ABT_CHK_EXISTING_POL. In this BAdI, you can implement your own logic to identify if the policy already exists. FS-PM delivers a standard implementation which uses the external application ID in the policy data which must be filled by FS-QUO (see also step 1 in the graphic below). You can find the BAdI in Customizing for Policy Management under Integration -> Application Interface -> Business Add-Ins -> BAdI: Check If Policy Is Already Created. Since FS-QUO does not know the commission contract from FS-ICM which is necessary to create a policy in FS- PM, you can use the BAdI /PM0/ABT_GET_COMMIS_INFO to fill the commission participant and the commission participation role. FS-PM provides a standard implementation for this BAdI (see also step 2 in the graphic below). You can find the BAdI in Customizing for Policy Management under Integration -> Application Interface -> Business Add-Ins -> BAdI: Determination of Information for Commission Participant. There are rules configured in the product now to populate ICM-related information. For products using the APIF Wrapper, you do not need to execute these rules. If the policy does not already exist in FS-PM and no error occurs, the general APIF function module /PM0/ABT_APIF_REL_FB is called to create the policy (see also step 3 in the graphic below). 40 Setting Up Connection between FS-QUO and FS-PM

41 Sequence of interaction between FS-QUO and FS-PM: 6.8 Using Native APIF If a product uses msg.pm as the rating engine, then Native APIF must be used. Note: Native APIF is the default out-of-the-box selection for all products using msg.pm as the rating engine and has been enhanced to support multi-currency. To choose a native APIF implementation, go to the ID component of your product and select the desired BookingService attribute. The available selections are: o Native APIF (default) o APIF Wrapper (described in the previous selection) o Auto APIF (for future use) Setting Up Connection between FS-QUO and FS-PM 41

42 When configuring FS-PRO for integration with FS-PM, the same data is represented in two different ways in the two systems. As a result, the components need to be mapped between the two systems. This is done in the SAP Global Reference Object under Configuration > Integration > APIF Input Parameter Mapping. o TableName is used by FS-PRO. o InputParameter is used by FS-PM. SourceColumnName and TargetColumnName are attributes in Configuration > Integration > APIF Composite Key Configuration. If any new tables.columns are added on the customer side, they must be entered under Configuration > Integration > APIF Transient Fields. 6.9 Using the Business Partner Search Adapter in FS-PM To use the search adapter of SAP Business Partner in Financial Services (ERP-BP) in FS-PM, you must copy the search helps from FS-PM to SAP ERP. For more information, see SAP Note Setting Up Connection between FS-QUO and FS-PM

43 7 Setting Up the Connection between FS-QUO and ERP-BP This section describes the following topics: Creating a User Configuring the Connection in FS-QUO Note: These procedures are required only if you are integrating FS-QUO with FS-PM and FS-PRO. 7.1 Creating a User Create the appropriate user using transaction SU01. You can find the relevant authorizations in the following template roles: SAP_FSPM_S_TMPL_CONSUME_RFC (FS-PM: Use of Remote Function Call Modules); Function Group /PM0/ABB_REMOTE_BP SAP_FSPM_S_TMPL_CREATE_POLICY (FS-PM: Create Policy) SAP_FSPM_S_TMPL_DISPLAY_POLICY (FS-PM: Display Policy) SAP_FSPM_S_TMPL_MNG_INS_OBJ (FS-PM: Edit Insurable Object) To find the template roles, proceed as follows: 1. Call up transaction PFCG. 2. Enter the relevant role and choose (Display) 3. On the Authorizations tab, choose Display Authorization Data. Note: For the connection between FS-QUO and ERP-BP, the relevant function group is /PM0/ABB_REMOTE_BP (template role SAP_FSPM_S_TMPL_CONSUME_RFC). 7.2 Configuring the Connection in FS-QUO ERP-BP (SAP Business Partner for Financial Services) manages business partner data (for example, account names and addresses). To create new business partners from FS-QUO (for example, add an account), FS-QUO must be able to connect to ERP-BP. When an underwriter or producer adds a business partner in FS-QUO, FS-QUO sends a request to ERP-BP. ERP-BP creates the partner and returns the new partner ID to FS-QUO. FS-QUO stores this partner ID and sends this information along with the policy data at binding time. Important: There may be multiple instances of Business Partner in the landscape. FS-QUO must be connected to the Business Partner that the corresponding FS-PM is connecting to. FS-QUO searches for Business Partners (Policy Holder, Premium Payer, etc.) from the connected Business Partner and adds Business Partner to the connected Business Partner instance. For example, suppose that you create a business partner for FS-QUO, but searching for a partner does not produce results. This might mean that FS-QUO is connected to ERP-BP, but there is a connection issue between FS-PM and ERP-BP. As another example, if you cannot create an account in FS-QUO, there is a connection issue between FS-QUO and ERP-BP. Setting Up the Connection between FS-QUO and ERP-BP 43

44 For more information about ERP-BP, see the FS-PM Application Help Configuring RFC Destinations in products In order to let the system know which destination name will be used in the application, the NetWeaver destination names need to be defined in the product. 1. Login to FS-PRO and open the SAP Global Reference Object component. 2. Go to Configuration > Integration > RFC >Remote Function System. 3. A predefined set of system types are provided. You can used the default name or assign a name of your choosing. This will be the name of the RFC Destination that you will create in NetWeaver. System Type From System To System Destination Name policy FS-QUO FS-PM FSPM_DEST insuobj FS-QUO FS-PM FSPM_DEST bpartner FS-QUO ERP-BP BP_DEST searchhelp FS-QUO FS-PM FSPM_DEST generic FS-QUO FS-PM FSPM_DEST If the required system type is not listed, you will need to create a new row, with the new system type and a name. 4. Build the metadata and publish the SAP Global Reference Object Configuring RFC Destinations in NetWeaver You need to create RFC destinations for each product repository in your integration. You need to create at least two destinations: one for FS-PM and one for ERP-BP. The destinations need to be created on the NetWeaver server where your application is deployed and need to be mapped in FS-PRO. 1. Login to NetWeaver. You must have Administrator permission on NetWeaver 2. Go to Configuration > Destinations. 3. On the General Data screen, specify the following information: o Hosting System Leave the default value selected by NetWeaver in place. o Destination Name Enter the name of the destination. The name must be unique and must be identical to the equivalent destination name that you created in products. Best practice is to use a naming convention that allows easy identification of the target instance. o Destination Type Select RFC as the destination type. 4. Click Next. 5. On the Connection and Transport Security screen, specify the following information: o Load Balancing Set this value to No. o Local System Connection Leave this value unchecked. o Target Name Enter the name of the host. This information can be found on the SAP Login screen. 44 Setting Up the Connection between FS-QUO and ERP-BP

45 o System number Enter the system number of the target system. This information can be found in the Instance No. column on the SAP Login screen. o System ID Enter the system ID of the target system. This information can be found in the SID column on the SAP Login screen. o SNC Set this value to Inactive. 6. Click Next. 7. On the Logon Data screen, you can specify either a predefined service user or the current user. If you select to use the current user, then also specify whether a login ticket or an assertion ticket should be used for the authentication. Specify the following information: o Authentication Select a value from the dropdown. o Language Enter the short name for the appropriate language. o Client Enter the name of the client. This information can be found on the SAP Login screen. o User Name Enter the user name. o Password Enter the password for the specified user name. o Destination Name Select This Destination. 8. Click Next. 9. On the Pool Settings screen, select the Pooled Connection Mode checkmark. 10. Click Finish. 11. Test the connection. Select the new destination and click Ping Destination Testing RFC destinations You can verify that the connectivity defined in the destinations is functional. 1. Log in to the FS-QUO Administrative Console at the following address: 2. Select System > Test SAP Server Connectivity. 3. Go to the Test JCo3 Feature tab, select the destination and click Connect to test the connection. 4. Repeat these steps for all destinations. 5. A pop up message indicates whether the connection is valid or invalid. Setting Up the Connection between FS-QUO and ERP-BP 45

46 8 Product Configuration in FS-PRO This section describes concepts and procedures for configuring property and casualty (P and C) and life and annuity (L and A) products in Product Configurator that will be used by FS-QUO and FS-PM. Note: The prerequisites for understanding and using this information are the following: You have been introduced to the fundamentals of Product Configurator through the training course curriculum. You are familiar with SAP Product Lifecycle Management for Insurance. 8.1 Data Models A data model in Product Configurator is a representation of the database tables and columns that store marketable product information. A data model is composed of data definition objects that contain related data elements and attributes. FS-PRO provides the following five data models for products that work with FS-PRO and FS-PM: SAP Insurance Reference Data Model SAP PnC Data Model SAP PnC Combined Data Model SAP LnA Insurance Data Model SAP LnA Combined Data Model The SAP PnC Data Model or SAP LnA Data Model is assembled in template that your marketable products inherit from. Generally, you do not need to modify the data model templates and assembled location. However, you can extend the data model content to capture additional information that your product and organization need. For more information about extending the data model, see Adding New Fields in FS-PRO (page 131). For information about the provided templates, see Templates in FS-PRO (page 49). For general information about object inheritance and templates, see the SAP Product Lifecycle Management for Insurance Product Configurator User Guide SAP Insurance Reference Data Model The SAP Insurance Reference Data Model object is a representation of the following: A subset of the basis tables that FS-PM uses to store policy information (Extended DD Policy data definition object). These basis tables are common to products in all lines of business. The tables that FS-QUO uses to store transactional information (FSQUO Policy Quote data definition object) This data model is referenced in objects so that the tables and columns in the model are included in the XML file that is created and deployed to FS-QUO. These tables are already defined as flowstore tables in Designer. 46 Product Configuration in FS-PRO

47 Location of the Standalone Object Product Studio > System Repository > SAP Insurance Base Library > Data Models > SAP Insurance Reference Data Model Where Used (First Referenced) This data model is first referenced in the SAP Insurance UWA templates because products of all types, such as P and C (property and casualty) and L and A (life and annuity), need this data. By referencing this model, the rules in main axis and lateral objects can access the information. This configuration is specified in the following component using the REFERENCE_PRODUCT key: Product Studio > System Repository > SAP Insurance Base Library > [Object Folder] > SAP Insurance UWA [Object Type] Template > Configuration > Config The following figure shows the data model referenced in the UWA premium template: The SAP Insurance Reference Data Model is also assembled in the SAP PnC Combined Data Model and the SAP LnA Combined Data Model. For more information about the combined model, see SAP PnC Combined Data Model and SAP LnA Combined Data Model (page 48). The Extended DD Policy Data Definition The Extended DD Policy data definition object contains a subset of the tables and columns that FS-PM uses to store product information. The data definitions represent the structure of the main axis objects required in FS-PM.You configure marketable products in Product Configurator using a structure that mimics this data model. This structure dictates where these objects can be located. When configuring the product, you can check this data model to see where the objects can be placed. Notes: All data definitions other than the main axis objects represent the tables for lateral objects. The Data Definitions folder contains objects that are prefixed with "SAP DD" (for example, SAP DD Contract Bundle). These data definitions are representations of the tables in FS-PM. Do not modify these objects. Instead, if you want to make changes to these data definitions (for example, add columns), modify the "Extended DD" objects provided in the Company Library. These objects inherit from the "SAP DD" objects. By modifying the extended objects instead of the DD objects, the data provided with FS-PRO is separated from your company data. This configuration is helpful for preserving company data during upgrades. For more information about modifying data definitions, see Adding New Fields in FS-PRO (page 131). The Column objects in the Data Definitions define all of the FS-PM columns that FS-PRO can access for data capture and rating. Product Configuration in FS-PRO 47

48 8.1.2 SAP PnC Data Model and SAP LnA Insurance Data Model The SAP PnC Data Model and SAP LnA Insurance Data Model objects are a representation of the tables and columns that extend from the tables in the SAP Insurance Reference Data Model. These extension tables contain additional columns that are only relevant to P and C products and L and A products. Note: For more information about how tables are extended, see the data definitions and REF NAME descriptions in the SAP Product Lifecycle Management for Insurance Product Configurator User Guide. You assemble the data model into your templates for P and C products or L and A products. Marketable products inherit this configuration so that the tables and columns in the model are included in the XML file that is created and deployed to FS-QUO. Location of the Standalone Objects Product Studio > System Repository > SAP PnC Insurance Template Library > Data Models > SAP PnC Data Model Product Studio > System Repository > SAP LnA Insurance Template Library > Data Models > SAP LnA Insurance Data Model Where Used (First Assembled) Product Studio > System Repository > SAP Insurance Base Library > Products > SAP Insurance UWA Product Template > Data Models SAP PnC Combined Data Model and SAP LnA Combined Data Model This SAP PnC Combined Data Model includes the SAP Insurance Reference Data Model and P and C-specific data definitions. This model is provided as part of the SAP PnC Insurance Template Library for P and C products. This data model is referenced in P and C main axis objects so that the tables and columns in the model are included in the XML file that is created and deployed to FS-PM during publishing. This SAP LnA Combined Data Model includes the SAP Insurance Reference Data Model and L and A-specific data definitions. This model is provided as part of the SAP LnA Insurance Template Library for L and A products. This data model is referenced in L and A main axis objects so that the tables and columns in the model are included in the XML file that is created and deployed to FS-PM during publishing. Location of the Standalone Object Product Studio > System Repository > SAP PnC Insurance Template Library > Data Models > SAP PnC Combined Data Model Product Studio > System Repository > SAP LnA Insurance Template Library > Data Models > SAP LnA Combined Data Model 48 Product Configuration in FS-PRO

49 Where Used (First Referenced) This data model is first referenced in the SAP PnC templates or SAP LnA templates. By referencing this model, the rules in main axis objects can access the data. This configuration is specified in the following component using the REFERENCE_PRODUCT key: Product Studio > System Repository > SAP PnC Insurance Template Library > [Object Folder] > SAP PnC [Object Type] Template > Configuration > Config Or Product Studio > System Repository > SAP LnA Insurance Template Library > [Object Folder] > SAP LnA [Object Type] Template > Configuration > Config Notes: The REFERENCE_PRODUCT key is initially set to SAP Insurance Reference Data Model in the UWA templates that the SAP PnC or SAP LnA templates inherit from. The UWA templates apply to all types of products. At the SAP PnC level or LnA level, this value is overridden with SAP PnC Combined Data Model or SAP LnA Combined Data Model to include the P and C or L and A -specific data definitions. If a lateral object requires data from the SAP PnC Data Model or SAP LnA Data Model (product extension tables) or another data model, you can override the REFERENCE_PRODUCT key to use that model. This configuration controls the values that appear in Rule Painter > Table and Column Picker. The following figure shows the data model reference in the P and C coverage template: Notes: Marketable product objects do not inherit from templates that are specific to lines of business. Instead, products inherit from a UWA product template. The UWA template references the SAP Insurance Reference Data Model, not the SAP Combined PnC Data Model or SAP Combined LnA Data Model. Because P and C products need the data in the SAP PnC Data Model, the SAP PnC Data Model is assembled directly in the Data Models folder of P and C marketable products. With this configuration, the data from the SAP Insurance Reference Data Model and SAP PnC Data Model are included in the XML file that is created and deployed to FS-QUO during publishing for P and C products. Because L and A products need the data in the SAP LnA Data Model, the SAP LnA Data Model is assembled directly in the Data Models folder of L and A marketable products. With this configuration, the data from the SAP Insurance Reference Data Model and SAP LnA Data Model are included in the XML file that is created and deployed to FS- QUO during publishing for P and C products. For more information about marketable product templates, see Inherited Templates for Main Axis Objects (page 52).Templates in FS-PRO Templates in FS-PRO contain the objects and product structure that marketable products need. These templates specify the features and functions that FS-PRO, FS-QUO, and FS-PM use to manage products and calculate premiums. When you install FS-PRO and the provided bootstraps, these templates are automatically placed in Product Studio > System Repository in Product Configurator. Product Configuration in FS-PRO 49

50 To create your marketable product, you inherit from the provided templates and configure additional rules, data, and structures. Inheritance lets you base products on templates so that you do not have to define details that are common to groups of products. By inheriting a template, you can extend the already-defined details by specifying your own product requirements. We also recommend that you create your own templates that contain data specific to your organization. You can organize templates by categories such as lines of business and programs. For example, P and C products inherit from the provided SAP PnC [Object] Template. To create your own templates, you can do the following: Create a [Your Company] PnC [Object] Template to store all of your company-specific P and C data. Create a [Your Company] Commercial [Object] Template for data that is specific to commercial products and a [Your Company] Personal [Object] Template for data that is specific to personal products. From the company commercial or personal layer, you can create [Your Company] Household [Object] Template for data that is specific to household products. In the object templates, you can assemble the objects that are common to the object type. For example. policyholder can be assembled in [Your Company] Insurance UWA Product Template because it is required by all lines of businesses. For coverage, the limits and deductibles that only pertain to Home Contents can be assembled in the Home Contents Coverage Template. With this configuration, you can create variations of that coverage without constructing the object again for each variation. 8.2 Template Libraries FS-PRO provides a template library. This library contains folders for each object that you can use to create line of business specific templates and use them as a base to import other IFBC templates. For example, in the adjustments folder you can create a company specific object such as <ABC Company> <LnA> <Adjustment> template based on SAP <LoB><Object> template. Note: SAP recommends that you do not rename folder names within this library. In Product Configurator, the System Repository folder contains the following template libraries for P and C products: SAP Insurance Base Library This folder contains the default base templates and objects for insurance products. The templates labeled with "UWA" (for example, SAP Insurance UWA Coverage Template) inherit from the base templates and are for products that work with FS-PRO, FS-PM, and FS-QUO. SAP PnC Insurance Template Library The templates in this library inherit from the UWA templates in the SAP Insurance Base Library. These templates specify the features and functions that apply to all P and C products. SAP AUTO Insurance Template Library The templates in this library specify features and functions that apply to all auto products. SAP Long Term Insurance Template Library The templates in this library specify features and functions that apply to all long term products. System Group This folder contains the system objects that the Product Configurator environment needs. Underwriting Application Template Library The objects in this library are used for configuring FS-QUO, mainly the Underwriting Application Configuration object. For more information about the objects in these libraries and how the templates are structured, see the Product Model Help. 50 Product Configuration in FS-PRO

51 8.2.1 Sample Household Product and Library FS-PRO provides a SAP Sample Content Library in the System Repository in Product Configurator. This library contains templates and objects for the Sample Household Product. You can refer to this product to see an example of inherited templates, rating, and other configured integration objects. After you set up the connections between FS-PRO, FS- QUO, and FS-PM, you can use this product to test integration Company Templates FS-PRO provides a Company Library in Product Studio > Product Repository in Product Configurator. You can use this folder as your organization's library and add marketable products and associated main access objects to it. This library contains Company Insurance UWA templates that you can use to configure common settings that apply to all main axis objects across lines of business. Note: We recommend that you rename the Company folder and Company objects with your organization's name. For example, if your organization's name is ABC, rename Company Library to ABC Library and rename Company Insurance UWA Contract Template to ABC Insurance UWA Contract Template. However, do not rename extended objects (for example, Extended Underwriting Application Configuration). The following figure shows a template in the Company Library: For example, if all of your P and C, health, and life and annuity products require clauses, you can add a Clauses folder to the Company Insurance UWA Contract Template. In all of your products that inherit from this template, the contract object would contain this folder. You can create and assemble clause objects in it. Product Configuration in FS-PRO 51

52 The following example shows the inherited templates in the Sample Household Contract object: This main axis object has several template layers. These templates contain configurations that are specific to the following: All contracts in the company (Company Insurance UWA Contract Template) All P and C contracts (SAP PnC Contract Template) In the provided Sample Household Product, the following templates represent additional company layers: All P and C contracts for the Sample company (Sample PnC Contract Template) All household contracts in the Sample company (Sample Household Contract Template) Inherited Templates for Main Axis Objects The inherited template layers differ for marketable products and other types of main axis objects, such as contract bundles, contracts, coverage bundles, coverages, and sub coverages. The template layers can differ because lines of business can have different structures. For example, certain layers for main axis objects can contain common folders and objects so that those templates can be reused across multiple lines of business. 52 Product Configuration in FS-PRO

53 Templates for Main Axis Objects Excluding Marketable Products The following example shows how the templates are used in inheritance for a contract object: The layers with a solid outline are provided with FS-PRO. The layers with a dashed outline are templates that you can create and modify in your company library. Note: FS-PRO provides the Company Insurance UWA Contract Template, but you can modify it as needed for your organization. An example of this inheritance is in the Sample Household Contract. For more information about this object, see the Sample Household Product Guide. Product Configuration in FS-PRO 53

54 Templates for Marketable Products Unlike other main axis objects, marketable product objects do not inherit from templates that are specific to lines of business (for example, SAP PnC [Object] Template). These types of templates are excluded because packaged products might contain products from different lines of business. For example, a packaged product that includes P and C and L and A products would not inherit from an SAP PnC template that contains configurations that only apply to P and C products. The following figure shows an example of the inherited templates for a household product: The layers with a solid outline are provided with FS-PRO. The layers with a dashed outline are templates that you can create in your company library. Note: FS-PRO provides the Company Insurance UWA Product Template, but you can modify it as needed for your organization. An example of this inheritance is in the Sample Household Product. For more information about this object, see the Sample Household Product Guide. 54 Product Configuration in FS-PRO

55 8.2.4 Inherited Templates for Lateral Objects Lateral objects are stored in the SAP sample content library. The following example shows how the templates are used in inheritance for a premium object: The layers with a solid outline are provided with FS-PRO. The layers with a dashed outline are templates that you can create in your company library. An example of this inheritance is in the Sample Home Contents Underinsurance Waiver Clause. For more information about this sample object, see the Sample Household Product Guide Important Upgrade Consideration Do not modify the base templates and objects in the System Repository. To make changes to your environment and products, create and modify your own company templates that inherit from the SAP template, SAP Insurance UWA [Object] templates in the Company Library. Upgrades are only supported for products that were created based on the provided product model that consists of these inherited template layers. If you deviate from the out-of-the-box model, you will have the responsibility to maintain the forward and backward compatibility to the latest model. 8.3 Product Configuration Configuring a product in Product Configurator involves creating objects that inherit from provided templates, assembling the objects in the appropriate locations, and configuring the components in those objects. Product Configuration in FS-PRO 55

56 Note: To complete the configuration, you must be experienced with the fundamentals of Product Configurator, including inheritance and script rules. Each topic in this section provides references for more information about configuring the specific component. More information is available as follows: For an example of a configured product, see the Sample Household Product. If you are integrating FS-PRO, FS- QUO, and FS-PM, the Sample Household Product contains objects in User Interface folders that let you configure the FS-QUO GUI. If you are integrating FS-PRO and FS-PM, the Sample Household Product PRO does not contain the User Interface objects. In this document, both versions are referred to as Sample Household Product. For details about Product Configurator components and the values to enter, see the Product Model Help, as indicated. For an example of how a product is configured, see the Sample Household Content Guide. For information about how to use Product Configurator, see the SAP Product Lifecycle Management for Insurance Product Configurator User Guide Configuring a Product in FS-PRO To create a product that works with FS-PRO, FS-QUO, and FS-PM, you must configure objects in Product Configurator and specify data that correlates with FS-PM. Note: Before you configure products in Product Configurator, check SAP Notes on SAP Service Marketplace ( for any prerequisite tasks that must be performed. For example, we occasionally describe changes that you must manually perform in the imported bootstrap content for a particular release. Follow these steps: 1. Discuss, plan, and model your product to determine the required objects and the layers that they belong to. 2. Create Company-Level Templates (page 56). 3. Create the Marketable Product (page 58). 4. Create and Assemble Main Axis Objects (page 59). 5. Create and Assemble Lateral Objects (page 62). 6. Test Rating Using Product Web Services (page 64). 7. Publish the product Creating Company-Level Templates FS-PRO provides templates that include preconfigured settings that most marketable products need. You can create and configure templates that include settings that are specific to your company and lines of business. The provided Company Library already contains Company Insurance UWA templates for main axis objects. You can create templates for lateral objects and templates at additional layers, as needed. Note: As a best practice, rename the Company folder and Company objects with your organization's name. 56 Product Configuration in FS-PRO

57 The following example shows the custom templates configured for the Sample Household Contract object: In your company, the inheritance list might look similar to the following example: ABC Household Contract ABC Household Contract Template ABC PnC Contract Template SAP PnC Contract Template ABC Insurance UWA Contract Template SAP Insurance UWA Contract Template SAP Insurance Contract Base For more information about templates and the provided Company Library, see Templates in FS-PRO (page 49). For more information about creating objects that inherit from other objects, see the SAP Product Lifecycle Management for Insurance Product Configurator User Guide. Product Configuration in FS-PRO 57

58 8.3.3 Creating the Marketable Product Proceed as follows: 1. Create an object that inherits from the appropriate product template. This object is typically placed in the following location: Product Studio > Product Repository > [Company] Library > Products 2. Configure the components in each of the following folders: Folder Description of Contents More Information Identification Uniquely identifies a marketable product Product Model Help > SAP Insurance UWA Templates > SAP Insurance UWA Product Template > Identification Data Models Assembled data model Data Models (page 46) User Interface eapp configuration objects Configuring eapp ( page 93) Rating Underwriting Rating Rules and Rating Lookup Rules Components used for the FS-QUO GUI, and underwriting rules and data including the following: Column Default Value Settings Validation Rules Calculations Rules Referral Rules Checklist Items Rating (page 83) Product Model Help > SAP Insurance UWA Templates > SAP Insurance UWA Product Template > Underwriting Contract Bundles Assembled contract bundle objects Product Model Help > SAP Insurance UWA Templates > SAP Insurance UWA Coverage Bundle Template Contracts Assembled contract objects Product Model Help > SAP Insurance UWA Templates > SAP Insurance UWA Contract Template Configuration IFBC [Object] Integration Services - IFBC information Static Product Information for IFBC (page 67) Reference Data FSPM Validation - FS-PM response Config - Specifies the Reference object Assembled reference components containing marketable product information for lookup Product Model Help > SAP Insurance UWA Templates > SAP Insurance UWA Product Template > Configuration > Integration > FSPM Validation Product Model Help > SAP Insurance UWA Templates > SAP Insurance UWA Product Template > Configuration > Config Product Model Help > SAP Insurance UWA Templates > SAP Insurance UWA Product Template > Reference Data 58 Product Configuration in FS-PRO

59 3. Create folders and objects for lateral objects that are specific to your product. For example, the Sample Household Product includes the following folders in the product object: Folder Description of Contents More Information Policyholder Assembled policyholder object Business Partners (page 85) Product Model Help > SAP Insurance UWA Templates > SAP Insurance UWA Policyholder Template Representatives External References Assembled representative (agent) objects Assembled external reference objects Business Partners (page 85) Product Model Help > SAP Insurance UWA Templates > SAP Insurance UWA Agent Template Business Partners (page 85) Product Model Help > SAP Insurance UWA Templates > SAP Insurance UWA External Reference Template Note: You can assemble these lateral objects in the appropriate template. For example, policyholder is required for FS-PM, so you can create and assemble the policyholder object in the [Company] UWA template layer Creating and Assembling Main Axis Objects Important! For this release, configure individual contracts or contract bundles that contain contracts. Do not configure both individual contracts and bundles in a product. For this release, configure individual coverages or coverage bundles that contain coverages. Do not configure both individual coverages and bundles in a product. For each main axis object that you want to create, proceed as follows: 1. Create an object that inherits from the appropriate object template. This object is typically placed in the following location: Product Studio > Product Repository > [Company] Library > [Object Name] Example: Product Studio > Product Repository > [Company] Library > Contracts 2. Configure the components in each of the following folders: Folder Description of Contents More Information Identification Uniquely identifies the object Product Model Help > SAP Insurance UWA Templates > SAP Insurance UWA [Object] Template > Identification User Interface eapp configuration objects Configuring eapp ( page 93) Rating Underwriting Rating Rules and Rating Lookup Rules Components used for the FS-QUO GUI, and underwriting rules and data including the following: Column Default Value Settings Validation Rules Calculations Rules Rating (page 83) Product Model Help > SAP Insurance UWA Templates > SAP Insurance UWA [Object] Template > Underwriting Product Configuration in FS-PRO 59

60 Folder Description of Contents More Information Referral Rules Checklist Items Configuration IFBC [Object] Integration Services - IFBC information Static Product Information for IFBC (page 67) Reference Data FSPM Validation - FS-PM response Config - Specifies the Reference object Assembled reference components containing contract information for lookup Product Model Help > SAP Insurance UWA Templates > SAP Insurance UWA [Object] Template > Configuration > Integration > FSPM Validation Product Model Help > SAP Insurance UWA Templates > SAP Insurance UWA [Object] Template > Configuration > Config Product Model Help > SAP Insurance UWA Templates > SAP Insurance UWA [Object] Template > Reference Data For contracts, configure the following additional folders: Folder Description of Contents More Information Coverage Bundles Assembled contract bundles Product Model Help > SAP Insurance UWA Templates > SAP Insurance UWA Coverage Bundle Template Coverages Assembled coverage objects Product Model Help > SAP Insurance UWA Templates > SAP Insurance UWA Coverage Template For coverages, configure the following additional folders: Folder Description of Contents More Information Sub Coverages Assembled sub coverage objects Product Model Help > SAP Insurance UWA Templates > SAP Insurance UWA Sub Coverage Template 3. Create folders and objects for lateral objects that are specific to your product. For example, the Sample Household Product includes the following folders in the contract object: Folder Description of Contents More Information Clauses Assembled clause objects Product Model Help > SAP Insurance UWA Templates > SAP Insurance UWA Clause Template External References Assembled external reference objects Business Partners (page 85) Product Model Help > SAP Insurance UWA Templates > SAP Insurance UWA External Reference Template Premiums Assembled premium objects Product Model Help > SAP Insurance UWA Templates > SAP Insurance UWA Premium Template Premium Payers Assembled premium payer objects Product Model Help > SAP Insurance UWA Templates > SAP Insurance UWA Premium Payer Template Related Contracts Assembled contract objects Product Model Help > SAP Insurance UWA Templates > SAP Insurance UWA Contract Template 60 Product Configuration in FS-PRO

61 Folder Description of Contents More Information Representatives Surcharges and Discounts Assembled representative (agent) objects Assembled surcharge and discount objects Business Partners (page 85) Product Model Help > SAP Insurance UWA Templates > SAP Insurance UWA Agent Template Product Model Help > SAP Insurance UWA Templates > SAP Insurance UWA Surcharge Discount Template The Sample Household Product also includes the following folders in the coverage object: Folder Description of Contents More Information Deductibles Assembled deductible objects Product Model Help > SAP Insurance UWA Templates > SAP Insurance UWA Deductible Template Insured Objects Assembled insured objects Product Model Help > SAP Insurance UWA Templates > SAP Insurance UWA Insured Object Template Limits Assembled limit objects Product Model Help > SAP Insurance UWA Templates > SAP Insurance UWA Limit Template Premiums Assembled premium and premium tax objects Product Model Help > SAP Insurance UWA Templates > SAP Insurance UWA Premium Template Note: You can assemble these lateral objects in the appropriate template. For example, policyholder is required for FS-PM, so you can create and assemble the policyholder object in the [Company] UWA template layer. 4. Assemble the main axis object in a template. Note: If you want to reuse the object in different products, you can assemble the object in a template. An object can have a structure that is relevant to different products. If you assemble the object in a template, you can reuse this object and its structure, but write calculation rules specific for each product. For example, you can assemble a coverage object in the following contract template so that the entire contract including the assembled coverages can be reused in different products: Product Studio > Product Repository > ABC Library > Contracts > ABC Insurance UWA Contract Template Product Configuration in FS-PRO 61

62 5. Repeat steps 1-4 for every main axis object that you want to add to your product. In the following example, the Sample Home Contents Coverage is assembled in the Sample Household Contract Template. The Sample Household Contract inherits from the Sample Household Contract Template and is assembled in the Sample Household Product Creating and Assembling Lateral Objects For each lateral object that you want to create, proceed as follows: 1. Create an object that inherits from the appropriate lateral object template. This object is typically placed in the following location: Product Studio > Product Repository > [Company] Library > [Lateral Object Folder] Example: Product Studio > Product Repository > [Company] Library > Policyholders 62 Product Configuration in FS-PRO

63 2. Configure the components in each of the following folders: Folder Description of Contents More Information Identification Uniquely identifies the object Product Model Help > SAP Insurance UWA Templates > SAP Insurance UWA [Object] Template > Identification User Interface eapp configuration objects Configuring eapp ( page 93) Rating Underwriting Rating Rules and Rating Lookup Rules Components used for the FS-QUO GUI, and underwriting rules and data including the following: Column Default Value Settings Validation Rules Calculations Rules Referral Rules Checklist Items Rating (page 83) Product Model Help > SAP Insurance UWA Templates > SAP Insurance UWA [Object] Template > Underwriting Configuration IFBC [Object] Integration Services - IFBC information Static Product Information for IFBC (page 67) Reference Data Config - Specifies the Reference object Assembled reference components containing contract information for lookup Product Model Help > SAP Insurance UWA Templates > SAP Insurance UWA [Object] Template > Configuration > Config Product Model Help > SAP Insurance UWA Templates > SAP Insurance UWA [Object] Template > Reference Data 3. Assemble the lateral object in the appropriate template. Note: If you want to reuse the object in different products, you can assemble the object in a template. An object can have a structure that is relevant to different products. If you assemble the object in a template, you can reuse this object and its structure, but write calculation rules specific for each product. For example, you can assemble a lateral object in the following coverage template so that the entire coverage including the assembled lateral objects can be reused in different products: Product Studio > Product Repository > [Company] Library > Coverages > ABC Insurance UWA Coverage Template Product Configuration in FS-PRO 63

64 4. Repeat steps 1-3 for every lateral object that you want to add to your product. In the following example, the Sample Home Contents Underinsurance Waiver Clause is assembled in the Sample Household Contract Template. The Sample Household Contract inherits from the Sample Household Contract Template and is assembled in the Sample Household Product Test Rating Using Product Web Services In FS-PRO, product web services are rules that are exposed as web services in a WSDL file. At run-time, FS-PM calls the FS-PRO product web services for rating and checking a policy. The SAP Insurance UWA Product Template provides product web services that you can select when you configure your marketable product. These provided services handle the transfer of data between FS-PRO and FS-PM. The pcratingws and pcmodcontractws services are already implemented in the template to initiate a rating rule. The other services in the template are not yet implemented. You can modify these services as needed. The SAP Insurance UWA Product Template also includes data schemas named SAPInsurancePnCPolicyModelSchema and SAPInsuranceLnAPolicyModelSchema. These schemas specify the data that is passed in and out of FS-PM for product configuration and rating for P and C products. 64 Product Configuration in FS-PRO

65 The following example shows the product web services and data schema objects: As part of product configuration, after you configure your product, you can test rating using these product web services. You can create a request that mimics a request that FS-PM would send to FS-PRO. The test translates this request into a URS object and calls the calculatepremium service. This service runs the rating rules at all levels of the product and returns the calculated values. The web service response includes these values. Notes: Do not modify the web services or data schema in the provided templates. If you want to modify the services, you can deviate the rule or override the entire data value row in your company template. If you want to add fields to pass to FS-PM, you must make a copy of the data schema and modify that copy. For more information about the steps involved in adding a field to the marketable product, see Adding New Fields in FS-PRO (page 131). For more information about product web services, see the SAP Product Lifecycle Management for Insurance Product Configurator User Guide. For FS-PM to call the product web services, the connection between FS-PM and web services on FS-PRO must be configured. For information about this connection, see Credential Handling from FS-PM to FS-PRO (page 29). Proceed as follows: 1. Check that Product Web Services Manager is configured in the following: o FS-PRO Administrative Console o FS-QUO (Designer) Administrative Console Note: For information about this configuration, see the Enterprise Deployment, Integration, and Administration Guide. 2. Publish, deploy, and upload the product to the FS-QUO Product Web Services runtime. 3. Log in to the FS-QUO Administrative Console at the following address: Product Configuration in FS-PRO 65

66 4. Go to the following location: Product > Manage Product Web Services 5. Choose the Runtime tab. 6. In the left panel, choose the name of your product (for example, Sample Household Product). A web service document appears in the right panel. 7. In the Operations field, select pcratingws, and choose Test, as shown in the following example: A tab appears, showing request and response dialogs. 8. In the Request dialog, enter the following: o User name and password to access Product Configurator o Values that are required for rating Note: To see which values are required or optional, see the tables and columns in the SAPInsurancePnCPolicyModelSchema and SAPInsuranceLnAPolicyModelSchema component in Product Configurator. For example, if a column within a table has a Min Occurs value of 0, that value is optional in the request. 9. Choose Execute. 10. In the Response dialog, look for the names of the columns that you configured to display data. Note: To display data, you must also configure rules to set the values in the columns. To see an example of how rules are configured to set values, see the Sample Household Product. For example, in the Sample Household Product, the following columns are configured to display data: o ANNPREMAFTTAX o ANNPREMBEFTAX If these names have values in the response, the web service ran correctly. The values shown depend on the rating calculation. 66 Product Configuration in FS-PRO

67 8.4 Static Product Information for IFBC For every entity that requires a product template in IFBC, the corresponding information must be configured in FS- PRO. After a marketable product is configured and published in Product Configurator, the product structure, including the corresponding IFBC information, is sent to IFBC using an XML file. The appropriate product templates are then created in IFBC. By setting up the corresponding information in FS-PRO and IFBC, new policy and endorsement information can be transferred between FS-PM and FS-PRO for rating. For more information about IFBC, entities, and templates, see the SAP FS-PM Application Help Types of Entities Provided The product templates provided in FS-PRO map to IFBC entities provided in FS-PM 5.3. For information about the IFBC template values, see the IFBC application help. The libraries and product templates that are provided in FS-PRO are split into four lines of business: SAP PnC Insurance Template Library SAP LnA Insurance Template Library SAP AUTO Insurance Template Library SAP Longterm Insurance Template Library Note: If you want to configure your product to map to IFBC entities that are not already included in the FS-PRO libraries, contact your SAP implementation team or SAP Support IFBC Components in Product Configurator In Product Configurator, all of the main axis and lateral objects in your product include IFBC-related components that define the information required in IFBC product templates. When configuring a product, you must select values in these components that map to the IFBC templates. This only applies if you are going to perform an IFBC push from FS- PRO to FS-PM.By using the information in these components, FS-PRO can traverse the product configuration and gather information for the XML file for IFBC. Note: To define additional characteristics, see Adding New Fields in FS-PRO (page 131). Product Configuration in FS-PRO 67

68 8.4.3 Location of the IFBC Components Each entity in the XML file that is published from Product Configurator and sent to IFBC includes basic data, subordinate information, control attributes, and column details. The following table shows where to configure this required information in Product Configurator: IFBC Entity Information Basic Data (for example, name and ID) Where Configured in Product Configurator [Entity/Object name] > Identification > SAP [Object type name] Id Example: Sample Household Contract > Identification > SAP Contract Id Note: You must specify the IFBC template ID in this component using the TemplateId field. This value is passed using the PRODUCT_BASE_ID tag in the XML file. If the object that you are configuring is used in multiple places (for example, in multiple products) and contain data that is unique to its parent object, you must specify a unique template ID. For example, if a coverage appears in two contracts with different control attribute values, the template ID of the coverage in each contract must be different. Otherwise, if the same template ID is used by the two coverages, the later import will overwrite the earlier one. Subordinates [Entity/Object name] > Identification > SAP [Object type name] Id Example: Sample Household Contract > Identification > SAP Contract Id Enter values for the following subordinate information: MinCardinality MaxCardinality AutoInclude Flag Note: Subordinate information does not apply at the product level. Therefore, these columns do not appear in [Product name] > Identification > SAP Product Id. This is the product-level component. Control Attributes [Entity/Object name] > Configuration > Integration > IFBC [Object type name] Integration Services > IFBC Control Attributes Example: Sample Household Contract > Configuration > Integration > IFBC Contract Integration Services > IFBC Control Attributes Column Details (Characteristics/Marks) [Entity/Object name] > Configuration > Integration > IFBC [Object type name] Integration Services > IFBC Column Details Example: Sample Household Contract > Configuration > Integration > IFBC Contract Integration Services > IFBC Column Details If a column detail has a range of values, also configure the following component: 68 Product Configuration in FS-PRO

69 IFBC Entity Information Where Configured in Product Configurator [Entity/Object name] > Configuration > Integration > IFBC [Object type name] Integration Services > IFBC Column Details > IFBC Column Ranges If a column detail has a default value, also configure the following component: [Entity/Object name] > Underwriting > SAP Column Default Values If a column detail has an enumeration list, also modify the following components: [Product name] > Configuration > Integration > IFBC Product Integration Services > IFBC Column Lists [Entity/Object name] > Reference Data > Domain Tables For more information about these IFBC components, what they do, how they map to IFBC entities, and the values to configure, see the Product Model Help Configuring Static Product Information for IFBC To create a product that works with FS-PRO and FS-PM, you must configure the IFBC-related components in Product Configurator and specify data that correlates with IFBC product templates. Proceed as follows: 1. Configuring Product-level IFBC Components (page 69). 2. Configuring Main Axis IFBC Components (page 73). 3. Configuring Lateral IFBC Components (page 78). 4. (Optional) Configuring IFBC Integration Services (page 82). 5. Publish the product and send the IFBC XML (page 125) Configuring Product-level IFBC Components Proceed as follows: 1. In Product Configurator, open your marketable product. Product Configuration in FS-PRO 69

70 2. Open the SAP Product Id component and enter the basic data in a row, as shown in the following example: Important! If this object is used in multiple places, you must change the IFBC template ID specified in the TemplateId field. For more information about specifying a unique template ID, see the basic data description on page Open the IFBC Control Attributes component and select the control attributes that apply, as shown in the following example: Notes: o You can override the predefined values with different values. o You can specify a text value for a control attribute in the TextValue field. o To select a value from predefined values, select a value from the DropdownListValue field. 70 Product Configuration in FS-PRO

71 4. Open the IFBC Column Details component and select the characteristics (marks) that apply, as shown in the following example: Note: You can override the predefined values with different values. 5. If a column detail has an associated range of values, expand the detail row, and in the IFBC Column Ranges component, do one of the following: o Select a row. o Create a row, enter the low and high values of the range, and select the row. The following example shows a column detail that has two ranges: Product Configuration in FS-PRO 71

72 6. If a column detail has a default value, open the SAP Column Default Values component, create a row, enter the column name and its default value, and select the row, as shown in the following example: 7. If a column detail has an enumeration list, do the following: 1. In your company library, go to the Components > Domain Tables folder, create an object with Modifier Type Reference, and define the values of the enumeration list in the object. 2. The following example shows Reference objects in the Domain Tables folder: Note: If the Components > Domain Tables folder does not exist in your company library, create it. 3. In your product, open the IFBC Column Lists component, create a row, and enter information to define the domain table that you created in your company library. 72 Product Configuration in FS-PRO

73 Note: The ComponentName field specifies the component name that contains the enumeration values. This value must match the name defined in the domain table component that you created. The following example shows a component name that matches the name in the domain table in the previous example: 4. Go to [Your Marketable Product] > Reference Data > Domain Tables folder, add (search and assemble) the domain table that you created in your company library. Notes: o If the Reference Data > Domain Tables folders do not exist in your product folder, create them. o The SAP Insurance Base Library > IFBC Integration Objects > Components > Column Lists folder contains predefined domain tables that can assemble in products. In your entity's Reference Data > Domain Tables folder, you can add (search and assemble) these domain tables. 5. Open each domain that that you assembled and select all the rows. 6. Open the following component and specify the LIST_ID you defined in the IFBC Column Lists: [Your Marketable Product] > Configuration > Integration > IFBC Product Integration Services > IFBC Column Details Configuring Main Axis IFBC Components For each main axis object (such as contracts and coverages) assembled in your product, you must configure the IFBCrelated components. Proceed as follows: 1. In Product Configurator, open your marketable product. 2. Open the SAP [Object type name] Id component and enter the basic data in a row, as shown in the following example: Product Configuration in FS-PRO 73

74 Important! If this object is used in multiple places (for example, in multiple products), you must change the IFBC template ID specified in the TemplateId field. For more information about specifying a unique template ID, see the basic data description on page Enter the subordinate information in the Min Cardinality, Max Cardinality, and Auto Include Flag fields, as shown in the following example: 4. Open the IFBC Control Attributes component and select the control attributes that apply, as shown in the following example: Notes: o You can override the predefined values with different values. o You can specify a text value for a control attribute in the TextValue field. o To select a value from predefined values, select a value from the DropdownListValue field. 5. Open the IFBC Column Details component and select the characteristics (marks) that apply, as shown in the following example: Note: You can override the predefined values with different values. 6. If a column detail has an associated range of values, expand the detail row, and in the IFBC Column Ranges component, do one of the following: o Select a row. o Create a row, enter the low and high values of the range, and select the row. 74 Product Configuration in FS-PRO

75 The following example shows a column detail that has four ranges: 7. If a column detail has a default value, open the SAP Column Default Values component, create a row, enter the column name and its default value, and select the row, as shown in the following example: 8. If a column detail has an enumeration list, do the following: 1. In your company library, go to the Components > Domain Tables folder, create an object with Modifier Type Reference, and define the values of the enumeration list in the object. Product Configuration in FS-PRO 75

76 The following example shows Reference objects in the Domain Tables folder: Note: If the Components > Domain Tables folder does not exist in your company library, create it. 2. In your product, open the IFBC Column Lists component, create a row, and enter information to define the domain table that you created in your company library. Note: The ComponentName field specifies the component name that contains the enumeration values. This value must match the name defined in the domain table component that you created. The following example shows a component name that matches the name in the domain table in the previous example: 76 Product Configuration in FS-PRO

77 3. In the entity's Reference Data > Domain Tables folder, add (search and assemble) the domain table that you created in your company library, as shown in the following example: Note: The SAP Insurance Base Library > IFBC Integration Objects > Components > Column Lists folder contains predefined domain tables that you can assemble in products. In your entity's Reference Data > Domain Tables folder, you can add (search and assemble) these domain tables. 4. Open each domain that that you assembled and select all the rows, as shown in the following example: Product Configuration in FS-PRO 77

78 5. Open the entity's IFBC Column Details component and specify the LIST_ID you defined in the IFBC Column Lists: Configuring Lateral IFBC Components For each lateral object (such as limits and deductibles) assembled in your product, you must configure the IFBCrelated components. Proceed as follows: 1. In Product Configurator, open your marketable product. 2. Open the SAP [Object type name] Id component and enter the basic data in a row, as shown in the following example: Important! If this object is used in multiple places (for example, in multiple products), you must change the IFBC template ID specified in the TemplateId field. For more information about specifying a unique template ID, see the basic data description on page Enter the subordinate information in the Min Cardinality, Max Cardinality, and Auto Include Flag fields, as shown in the following example: 78 Product Configuration in FS-PRO

79 4. Open the IFBC Control Attributes component and select the control attributes that apply, as shown in the following example: Notes: o You can override the predefined values with different values. o You can specify a text value for a control attribute in the TextValue field. o To select a value from predefined values, select a value from the DropdownListValue field. 5. Open the IFBC Column Details component and select the characteristics (marks) that apply, as shown in the following example: Note: You can override the predefined values with different values. 6. If a column detail has an associated range of values, expand the detail row, and in the IFBC Column Ranges component, do one of the following: o Select a row. o Create a row, enter the low and high values of the range, and select the row. The following example shows a column detail that has three ranges: Product Configuration in FS-PRO 79

80 7. If a column detail has a default value, open the SAP Column Default Values component, create a row, enter the column name and its default value, and select the row, as shown in the following example: 8. If a column detail has an enumeration list, do the following: 1. In your company library, in the Components > Domain Tables folder, create an object with Modifier Type Reference, and define the values of the enumeration list in the object. The following example shows Reference objects in the Domain Tables folder: Note: If the Components > Domain Tables folder does not exist in your company library, create it. 80 Product Configuration in FS-PRO

81 2. In your product, open the IFBC Column Lists component, create a row, and enter information to define the domain table that you created in your company library. Note: The ComponentName field specifies the component name that contains the enumeration values. This value must match the name defined in the domain table component that you created. The following example shows a component name that matches the name in the domain table in the previous example: 3. In the entity's Reference Data > Domain Tables folder, add (search and assemble) the domain table that you created in your company library. Note: The SAP Insurance Base Library > IFBC Integration Objects > Components > Column Lists folder contains predefined domain tables that you can assemble in products. In your entity's Reference Data > Domain Tables folder, you can add (search and assemble) these domain tables. 4. Open each domain that that you assembled and select all the rows, as shown in the following example: 5. Open the entity's IFBC Column Details component and specify the LIST_ID you defined in the IFBC Column Lists: Product Configuration in FS-PRO 81

82 8.4.8 Configuring IFBC Integration Services Optionally, you can modify the rules that define the values for the IFBC Import Mode Code and Clear Table Flag. Note: For more information about the mode codes and table flags, see Choosing Operation Mode for IFBC Import in FS-PRO (page 24). You can also enter comments to publish as part of the XML file for IFBC. These comments provide additional information about the product import. These settings are configured at the product level. Important! The configuration at the product level includes an IFBC Integration Services API component. Do not modify the rules in this component. These rules traverse the product tree and retrieve the basic data, subordinates information, control attributes, and column details for each entity in the tree. Proceed as follows: 1. In Product Configurator, open your marketable product, and go to the following location: [Your Marketable Product] > Configuration > Integration > IFBC Product Integration Services > IFBC Integration Services API 2. Modify the Import Mode Code or Clear Table Flag, as follows: 1. Find the getimportmodecode or getcleartableflag row, and override it, as shown in the following example: 2. Open the rule. 3. Uncomment the value that you want to assign to the setting, and comment out the other output values. 4. Save and build the rule. 82 Product Configuration in FS-PRO

83 3. Enter a comment for the product import, as follows: 1. Find the getcomment row, and override it. 2. Open the rule. 3. In the result variable, enter a comment for the product import, as shown in the following example: 4. Save and build the rule. 8.5 Rating You can configure ratings in two ways: Configure ratings in FS-PRO (see section ) Rate insurance products imported from FS-PM into FS-PQM using PMQ.Runtime (see section Error! Reference source not found.) Rating rules are defined in the following two components at all levels of the product: SAP Rating Rules SAP Rating Lookup Rules Each product, contract, coverage, sub coverage, and lateral object that is relevant to rating includes these components. Rating rules are included at all levels of the product because the rules can call different tables for data. You must configure the rating rules in each of these objects Configuring ratings in FS-PRO If you are using FS-PRO as your rating engine, see the following topics: Premiums How Rating Works Where to Configure Rating Product Configuration in FS-PRO 83

84 Premiums As part of your product configuration, a premium object must be configured in the contract and coverage levels. For example, in the Sample Household Product, premiums are configured to roll up from coverage to contract and are not annualized. The premium object at the contract level creates a record of the sum of all coverage premiums of the same type. The premium object at the coverage level creates a record of all sub coverage premiums. The rating rules in the lateral objects (for example, deductibles, and surcharges and discounts) can impact these premium values. For your product, you can configure premiums according to your business requirements. After FS-PM calls FS-PRO to calculate rating, FS-PRO runs all of the rating rules in the product and passes the premium values (for example, annual premium, premium by payment frequency, and annual premium after tax) to FS- PM. Note: Premium objects can be configured at the contract, coverage bundle, and coverage levels because IFBC needs the information to create tables at the different levels. Although premium objects are assembled at both levels, the XML file to IFBC shows only one premium template How Rating Works When FS-PM sends a request for policy information to be rated for a new business, the following web service runs: [Product Name] > Configuration > Integration > Product Web Services > Product Web Services > pcratingws When a business is changed, the following web service runs: [Product Name] > Configuration > Integration > Product Web Services > Product Web Services > pcmodcontractws For other post-bind transactions, you can modify the rules in the following three web services: [Product Name] > Configuration > Integration > Product Web Services > Product Web Services > pcaccountrepvalws [Product Name] > Configuration > Integration > Product Web Services > Product Web Services > pcadjustmentws [Product Name] > Configuration > Integration > Product Web Services > Product Web Services > pcmigrationws The following occurs: This service calls the calculatepremium product service and passes the policy information from FS-PM. The calculatepremium service calls the rateproduct rule at the product level. This rule finds all the contracts, coverage bundles, coverages, sub coverages, and lateral objects in the product and runs their rating rules. When rating at all the levels complete, the web service sends the information back to FS-PM. If you configured FS-QUO to integrate with FS-PM as the GUI to write new business, FS-QUO calculates the policy quote and passes it to FS-PM. However, FS-PM ignores this passed premium and calls calculatepremium product service instead to rerate the premium Where to Configure Rating Note: To configure rating, you must be familiar with script rules and what your organization wants to calculate. For more information about script rules, see the rule scripting language topics in the SAP Product Lifecycle Management for Insurance Product Configurator User Guide. To see an example of rating rules, see the Sample Household Product. To configure rating, proceed as follows: 1. In Product Configurator, open the marketable product. 84 Product Configuration in FS-PRO

85 2. (Optional) Go to [Product Name] > Rating > SAP Rating Rules, and modify the PreRatePolicy and PostRatePolicy functions. 3. For each contract, do the following: 1. Go to [Contract Name] > Rating > SAP Rating Rules. 2. In the Values tab, modify the ratecontract rule as needed. 3. Save the changes. 4. For each coverage, do the following: 1. Go to [Coverage Name] > Rating > SAP Rating Rules. 2. In the Values tab, modify the ratecoverage rule as needed. 3. Save the changes. 5. For each lateral object, do the following: 1. Go to [Object Name] > Rating > SAP Rating Rules. 2. In the Values tab, modify the initialize and rating rules as needed. 3. Save the changes. Notes: You must assemble and configure a premium object in your contract and coverage objects. The SAP Insurance UWA Premium Template provides the following rules: o initcontractpremium o initcoveragepremium o ratecontractpremium Depending on where you assemble the premium object, select the appropriate initialization rule for the coverage or contract. If you configure multiple contracts, coverages, or sub coverages, you must configure selection and initialization rules. For help with this configuration, contact your SAP implementation team or SAP Support Rating Insurance Products Imported from FS-PM into FS-PQM using PMQ.Runtime For rating insurance products that you import from FS-PM into the FS-PQM environment (FS-PRO or FS-QUO), you must use PMQ.Runtime as the rating engine. PMQ.Runtime is the runtime component of msg.pmq, It is packaged with the FS-PRO installer (ZIP file) and is automatically installed in the FS-PQM environment during the installation process. Note that you can run PMQ.Runtime using rule unit test only at the web service layer. Also, to use PMQ.Runtime as the rating engine, you must make the rating rules available in the FS-PQM environment. Following is a summary of the sequential activities to accomplish this: A. Export the product data, which includes the rating rules, from the FS-PM environment. B. Convert the exported product data to a PMQ data format. C. Upload the file in PMQ data format to the FS-PQM environment. D. Update product configuration in FS-PRO to use the uploaded file during rating. Product Configuration in FS-PRO 85

86 Exporting product data from the FS-PM environment The product data in FS-PM, which includes the rating rules, is developed using PM.Designer. The runtime component of msg.pmq (that is, PMQ,Runtime) can only read this data after you convert it to a PMQ data format: EAR or QAR. However, before you can do the conversion, you must export the product data into an intermediary format called a PM3 compilate. You use PM.Designer to generate a PM3 compilate. Export product data into a PM3 compilate Please refer to msg.pmq documentation for instructions Converting product data to a PMQ data format EAR and QAR are the only supported data formats for PMQ. So PQM.Runtime only reads product data and rating rules from content libraries that are packaged as deployment units in the form of EAR or QAR files. You use PMQ.Builder to convert PM3 compilates, the intermediary data format exported from PM.Designer which contains the product data and rules, into EAR or QAR files. PMQ.Builder is bundled with the FS-PRO installer (ZIP file). Convert PM3 compilate into EAR or QAR file Please refer to msg.pmq documentation for instructions Uploading product data in PMQ data format to the FS- PQM environment For rating or rule unit tests of insurance products that you import from FS-PM into the FS-PQM environment, PQM.Runtime reads rating rules from EAR or QAR files which contains the product data and rating rules exported from the FS-PM environment. You upload the EAR or QAR files to the FS-PQM environment to make it available for PMQ.Runtime using the Administrative Console of the respective environment. Upload EAR or QAR files to FS-PQM environment 1. Log in to the Administrative Console. 86 Product Configuration in FS-PRO

87 2. In the System menu, choose Edit File System. 3. At the bottom-left area of the left pane, in the Path list, select PA Custom Integration Folder (Write). Product Configuration in FS-PRO 87

88 4. At the top-left area of the left pane, expand the hierarchy and choose the content folder. 5. Inside the content folder, in the right pane, right click and choose Upload from the context menu. 88 Product Configuration in FS-PRO

89 6. Browse and select the EAR or QAR file and upload Updating product configuration in FS-PRO to use the uploaded file containing product data during rating Uploading the EAR or QAR file containing the product data and rating rules to the FS-PQM environment makes it available for PMQ.Runtime, but you must update the product configuration in FS-PRO to specify that this EAR or QAR file is to be used during rating. If you content file is specific to a LOB, it is suggested that you do this configuration in a higher level template to maximize reuse. Product Configuration in FS-PRO 89

90 Update product configuration in FS-PRO to specify the uploaded EAR or QAR file for use during rating 1. Log in to the Product Configurator. 2. Search and open the product you want to rate using PMQ.Runtime (in our case this is the Life Capital H0000S0002 (1.0D) product). 3. In the product tree, in the Configuration (1.0D) folder, choose the Config component. 4. On the Values tab, right-click the row heading at the far left of any row. 5. In the context menu, choose Add. 6. In the new row, specify the following values for the Key and Value columns (attributes): o Key: contentfilename 90 Product Configuration in FS-PRO

91 o Value: <filename.qar or filename.ear>, where filename is the name of the content file that you uploaded. 7. Choose (Save). 8.6 Business Partners ERP-BP (SAP Business Partner for Financial Services) manages business partner data (for example, producer names and addresses). In Product Configurator, you must configure the corresponding business partner objects in your marketable product. The provided templates include policyholder, agent, beneficiary, and premium payer objects. The SAP Insurance Reference Data Model dictates where these business partner objects can be assembled in your product. For more information about the data model, see SAP Insurance Reference Data Model (page 46). If you are integrating with FS-QUO, an underwriter or producer can add a business partner to a policy. To enable this function, a connection for FS-QUO and ERP-BP must be configured so that adding business partner data can be added. For information about connecting FS-QUO with ERP-BP, see Configuring the Connection in FS-QUO (page 43). o The proper JavaScript code must be included in the eapp fields so that the data can be transferred from FS- QUO to ERP-BP. For information about configuring the business partner fields in FS-QUO, see Configuring Questions and Views for Business Partners (page 108). Notes: Producer and account information fields appear in both FS-QUO General Information screen and eapplication, In the eapplication, the producer ID is automatically populated with the ID of the producer selected in the General Information screen. However, for accounts, you must select the same account in the eapplication as you entered in the General Information screen. FS-PM uses the account information in the eapplication. In FS-PM, the producer is a commission contract partner, and the account is a policyholder. To search for business partners, FS-QUO uses the FS-PM remote function calls to ERP-BP. Product Configuration in FS-PRO 91

92 For more information about the connection between FS-QUO and ERP-BP, see the Configuring the Connection in FS-QUO (page 43). 92 Product Configuration in FS-PRO

93 8.7 Configuring eapp for FS-QUO Integration Note: These procedures in this section are required only if you are integrating FS-QUO with FS-PM and FS-PRO. When a producer or underwriter selects a product in FS-QUO to write a new policy, the Fill Out Application section displays the product information and questions. This user interface includes sections and screens for the contracts and coverages in the product. The risk information is organized into tabs that display horizontally across the screen. The following example shows a Fill Out Application user interface: In Product Configurator, this collection of sections and screens is called the eapp (eapplication). For each marketable product, you configure the eapp by configuring user interface objects at the product (policy), contract, coverage, and sub coverage levels. The objects to configure include questionnaires, views, screens, and rules. Each of these levels have their own eapps. Together, these eapps form the entire user interface shown in the Fill Out Application section of FS-QUO. By configuring the user interface for each contract and coverage, you can reuse those sections and screens in different products. In FS-QUO, when a producer or underwriter clicks a policy, contract, and coverage section in Fill Out Application, the relevant, configured information and questions appear. Product Configuration in FS-PRO 93

94 The following example shows where the eapp is configured in a product in Product Configurator: For more information about eapps, see the SAP Product Lifecycle Management for Insurance Product Configurator User Guide. 94 Product Configuration in FS-PRO

95 8.7.1 Main eapp Configuration Components An eapp includes the following components and their subcomponents: User Interface > [Model Views] These components define the questions, screen controls, and how the questions appear in the user interface. The following example shows model view components: Data Capture > eapp Layout These components define how the user interface is rendered and the order that the producer or underwriter navigates through the product (policy), contract, and coverage eapps. Data Capture > eapplication These components define the screens and data of the eapp for the policy, contract, or coverage level. Each eapp contains screens, questions and views, and rules that call the appropriate data to display in the interface. The following example shows the eapp Layout and eapplication components: SAP UI Lookup Rules This component defines the rules to look up data to display on the interface, such as data to show in drop-down lists. The following example shows the SAP UI Lookup Rules component: The eapp for the product (policy) level also requires the following components to be configured: Data Capture > Quick Access Hierarchy This risk hierarchy defines the main axis objects of the marketable product. Questions > SAP Option Summary Grid Columns This component determines the columns that will be displayed on the Option Summary screen. Product Configuration in FS-PRO 95

96 The following example shows the policy level-specific components: For more information about these eapp components, see the Product Model Help Configuring eapp Note: This document provides the high-level steps for configuring a product with a single contract and a single coverage. For help with configuring multiple contracts or coverages or configuring contract or coverage bundles, contact your SAP implementation team or SAP Support. To configure the eapp for a marketable product, define the main axis and the eapps at the policy, contract, and coverage levels. Proceed as follows: 1. Log in to Product Configurator. 2. Open the marketable product that you want to modify. 96 Product Configuration in FS-PRO

97 4. Configuring Product Hierarchy (page 98). 5. Configuring Policy eapp (page 99). 6. Configuring eapp for Other Main Axis Entities (page 107). 7. Configuring Questions and Views for Lateral Objects (page 107). 8. Configuring Questions and Views for Business Partners (page 108). 9. Configuring the Fields to Add an Insurable Object (page 119). 10. Configuring Multi-Level Risk Renderer Settings (page 123). 11. Publish the product. Notes: For more information about how to configure questionnaires, how to create and assemble objects, and other eapp procedures, see your training course material and the SAP Product Lifecycle Management for Insurance Product Configurator User Guide. For details about the components and columns, see the Product Model Help. Product Configuration in FS-PRO 97

98 8.7.3 Configuring Product Hierarchy This product hierarchy defines the Policy, Contract, Coverage, and Sub Coverage tabs that appear in the eapp in FS- QUO, as shown in the following example: To complete a new policy application, producers and underwriters click through these tabs and complete the customer's policy information as needed. Note: The product hierarchy is defined using the Quick Access Hierarchy component. Although this component is also included in contract object, you configure the product hierarchy at the policy (product) level only. Proceed as follows: 1. Open the following object in Product Configurator: [Your Marketable Product] > User Interface > Data Capture > Quick Access Hierarchy 2. In the Values tab, add rows for the main axis objects, as shown in the following example: These values display as tabs in the user interface. Notes: o You must define rows for Policy Quote and Coverage Bundle and set their DefaultDisplay to False. These rows are required in the eapp configuration but are hidden in the interface. o The Primary Option eapp value must match the EApp Name value in the eapplication component at the contract and coverage levels. o For information about the column values in this component, see the Product Model Help. 98 Product Configuration in FS-PRO

99 3. For each row, expand it and in the Quick Access Hierarchy Detail component, specify the primary key of the data definition table in the Attribute Name column, as shown in the following example: Configuring Policy eapp To configure the Policy eapp, proceed as follows: Define the option summary grid columns (see ) Define the questions at the policy level (see ) Configure the renderer and eapps to display (see ) Configure the eapplication (see ) Defining option summary grid columns 1. Go to the following location in Product Configurator: [Your Marketable Product] > User Interface 2. Configure the SAP Option Summary Grid Columns component. Note: Add rows for values that are shown in FS-PM. For information about this component, see the Product Model Help Defining questions at the policy level The SAP Insurance UWA Product Template is configured with an SAP Policy Model View object. If your product inherits from this template, you can define the questions in the provided SAP Policy Model View object. Note: The policy-level questions for Sample Household Product are not configured in the SAP Policy Model View. Instead, the questions are configured in the Sample Household Policy Model View object. However, the contents of this model view object are structured correctly, similar to the SAP Policy Model View. For your products, define the questions and views in the SAP Policy Model View object at the template level. Product Configuration in FS-PRO 99

100 The following figure shows the model view object in the Sample Household Product: To define questions at the policy level, proceed as follows: 1. Open the product object at the template level. Example: [Your Company] Insurance UWA Product Template Note: If your questions are specific to your product, open that product object (for example, Sample Household Product). You can define the questions in the model view object in the product instead of the template. 2. Choose the model view object. Example (template level): [Your Company] Insurance UWA Product Template > User Interface > SAP Policy Model View Example (sample product): Sample Household Product > User Interface > Sample Household Policy Model View 3. In the Configuration folder, open the Config object, and modify the REFERENCE_PRODUCT as needed. 4. In the Questions folder, define the questions in the questionnaire model object. For example, in the Sample Household Product, the questions are defined in the following questionnaire model object: Note: In your product, define the questions in SAP Policy Model View at the template level. 5. In the Views folder, design how the questions will appear in FS-QUO using the view object. 100 Product Configuration in FS-PRO

101 For example, in the Sample Household Product, the design is defined in the following view object: Note: When configuring the eapplication, you configure the appropriate eapp Screen to refer to this view. Typically, you create templates in your company library. You can modify the inherited SAP Policy Model View object by adding questionnaire model objects and view objects as needed for your company in the template. We recommend that you store the questions and view objects in the following location: Product Studio > Product Repository > [Company Library] > Questions You can then assemble those objects in the SAP Policy Model View object in the template, as shown in the following example: [Your Company] Insurance UWA Product Template User Interface SAP Policy Model View Questions SAP Household Policy Questions SAP Household Policy Questions 2 Views SAP Household Policy Views SAP Household Policy Views 2 Configuration Config Product Configuration in FS-PRO 101

102 Configure the renderer and the eapps to display 1. Go to the following location in Product Configurator: [Your Marketable Product] > User Interface > Data Capture > eapp Layout 2. In the Values tab, add a row with the following values: o eapp Name Name of your entire product eapp (for example, Policy Base eapp). This eapp name must also be defined in the eapp Layout Section component. o Renderer [eapphierarchylayout] o Render Type [Tab]-Tab o Display Name Policy 3. Expand the row that you created for your product eapp. The eapp Layout Section component appears. 4. In Values tab, add a row for all of the eapps in the product and attach them. The following example shows attached eapps: Important! You must add a row for Coverage Bundle and attach it whether you define a coverage bundle eapp or not. 5. Expand the ProducerApplication row, and in the eapp Layout Section component, add and attach the row where Target eapp is the name of the eapp that you specified in the eapp Layout component (for example, Policy Base eapp). The following example shows the eapp row in the eapp Layout component: 102 Product Configuration in FS-PRO

103 The following example shows the matching value in the eapp Layout Section component for the ProducerApplication row: The ProducerApplication row defines the renderer to use. The renderer determines the look-and-feel of the user interface and looks for the eapp to display. Note: The provided SAP Insurance UWA Product Template that products inherit from is configured to use the multi-level risk renderer. We recommend that you do not change this setting. The row in the eapp Layout Section component identifies the name of the product eapp that the renderer must call (for example, Policy Base eapp). The renderer looks for the matching eapp name in the eapp Layout component and calls that eapp. Product Configuration in FS-PRO 103

104 The following example shows the area that is rendered by the ProducerApplication eapp in FS-QUO: The following example shows the Policy Base eapp that the renderer calls: 104 Product Configuration in FS-PRO

105 Configure the eapplication 1. Open the following object: [Your Marketable Product] > User Interface > Data Capture > eapplication 2. Add a row with the following values: o EApp Name Policy Quote eapp o Renderer eappcontent o Render Type [Tab] - Tab o Display Name Policy Quote Note: You must define this Policy Quote eapp so that the proper structure is generated in the policy XML that is used to integrate with FS-PM. This eapp indicates the top level of the structure. The attached screen is also defined but empty. 3. Add a row for your policy eapp, as shown in the following example: 4. Open the following object: [Your Marketable Product] > User Interface > Data Capture > eapplication > eapp Section 5. Add a row with the following values: o Section Name Policy Quote Section o Render Type [Tab] - Tab o Section Order 1 Note: This eapp is required in the generated XML that is used to integrate with FS-PM. The attached screen is also defined but empty. 6. Add a row for your policy section, as shown in the following example: 7. Open the following object: [Your Marketable Product] > User Interface > Data Capture > eapplication > eapp Section > eapp Screen 8. Add a row with the following values: o Screen Name Policy Quote Screen Product Configuration in FS-PRO 105

106 o Screen Id Empty screen o Screen Order 1 o Table Name POLICY_QUOTE Note: You need to define this eapp so that the proper structure is generated in the policy XML that is used to integrate with FS-PM. It is not displayed, so the screen is empty. 9. Add rows for the screens that you want to show at the policy level, including views that you configured for lateral objects. The following example shows the rows for policy-level screens: In the Household Policy row, the Screen Id refers to the Household Policy View in the Sample Household Policy Model View. 10. Open the following object: [Your Marketable Product] > User Interface > Data Capture > eapplication > eapp Section > eapp Screen > eapp Column Info 11. Add rows for validation and calculation rules that you want to run in the eapp. Note: You can define rules that do not set a value to a table column. For example, you can define a rule to add new records to a table before the page appears. For these rules, enter [TABLENAME].SUBJECT as the Column Name in the row. Every table contains a.subject column that does not contain significant data. Therefore, you can specify this column in the required Column Name rule for these types of rules. 106 Product Configuration in FS-PRO

107 In the following example, the initialization rule is highlighted: Configuring eapp for Other Main Axis Entities The eapp configuration at the contract, coverage, and sub coverage levels is similar to the configuration at the policy level. You can refer to Configuring Policy eapp (page 99) for similar instructions. To see an example of how a contract eapp is configured, see the Sample Household Contract in the Sample Household Product. Notes: To see an example of how a contract eapp is configured, see the Sample Household Contract in the Sample Household Product. To see an example of how a coverage eapp is configured, see the Sample Home Contents Coverage in the Sample Household Product. For help with configuring multiple contracts or coverages or configuring contract or coverage bundles, contact your SAP implementation team or SAP Support Configuring Questions and Views for Lateral Objects The user interface for a lateral object is configured in the corresponding Product Configurator object. For example, all products include a policyholder. You configure the user interface for the policyholder by using a Model View object containing questions and views. By configuring the user interface separately from an eapp, the lateral object interface can be reused in different screens. Lateral objects can be configured at all main axis levels, depending on where the lateral object eapp needs to appear. Notes: If the lateral object is a business partner (for example, policyholder and premium payer), skip this topic and follow Configuring Questions and Views for Business Partner (page 108) instead. If the lateral object is an insured object, skip this topic and follow Configuring the Fields to Add an Insurable Object (page 119) instead. Product Configuration in FS-PRO 107

108 Otherwise, proceed as follows: 1. Open the lateral object at the template level. Example: [Your Company] Insurance UWA Surcharge Discount Template Note: If your questions are specific to your product, you can define them in the model view object in the product instead of the template. For example, in the Sample Household Product, choose Sample Household Product > Contracts > Sample Household Contract > Surcharges and Discounts > Sample Installment Payment Surcharge 2. Choose the model view object. Example (template level): [Your Company] Insurance UWA Surcharge Discount Template > User Interface > SAP Surcharge Discount Model View Example (sample product): Sample Household Product > Contracts > Sample Household Contract > Surcharges and Discounts > Sample Installment Payment Surcharge > SAP Surcharge Discount Model View 3. In the Configuration folder, open the Config object, and modify the REFERENCE_PRODUCT as needed. 4. Define the questions in the questionnaire model object. 5. Design how the questions will appear in FS-QUO using the view object. 6. In the eapplication where you want to show the lateral object, configure the appropriate eapp Screen to refer to this view. Notes: o For more information about defining questions and views, see page 99. o To see an example of how the questions and views are configured for a policy-level lateral object, see the Sample Policyholder in the Sample Household Product. o To see an example of how the eapp is configured for a contract-level lateral object, see the Sample Premium Payer in the Sample Household Product Configuring Questions and Views for Business Partners If the lateral object represents a business partner (for example, policyholder and premium payer), you must configure two sets of questions and view objects, as follows: Questions object and View object for the main grid, as shown in the following example: 108 Product Configuration in FS-PRO

109 Questions object and View object for the details view, as shown in the following example: Proceed as follows: 1. Open the lateral object at the template level. Example: [Your Company] Insurance UWA Policyholder Template Note: If your questions are specific to your product, you can define them in the model view object in the product instead of the template. For example, in the Sample Household Product, choose Sample Household Product > Policyholder > Sample Policyholder. 2. Choose the model view object. Example (template level): [Your Company] Insurance UWA Policyholder Template > User Interface > SAP Policyholder Model View Example (sample product): Sample Household Product > Policyholder > Sample Policyholder > User Interface > Sample Household Policyholder Model View 3. In the Configuration folder, open the Config object, and modify the REFERENCE_PRODUCT as needed 4. Define the questions to show in the main grid, as follows: 1. Choose Questions > [Business Partner Type] Questions. Example (template level): Questions > SAP Policyholder Questions Example (sample product): Questions > SAP Household Policy Holder Questions 2. Define the questions. 3. If a question is a drop-down list, do the following: 1. Choose the question, and in the Data List Properties > General tab > Control Type field, select Data List. Product Configuration in FS-PRO 109

110 The following example shows this setting: 2. In the Data Source tab > Product Query field, configure the rule to call the bplookup stem. Note: To find out which function to use for your question, ask your FS-QUO development environment administrator to check the available functions in the stem. For more information about FS-QUO stems, see the FS-QUO Developer Guide. The following example shows a rule that calls the getaddresslistbypartnerid function in the bplookup stem: 4. Define a data grid. 5. Choose the data grid, and in the Data Grid Properties > General tab, select the Has Child Screen checkbox. 110 Product Configuration in FS-PRO

111 The following example shows this setting: 6. In the Data Grid Properties > Advanced tab, enter _GRID in the Script Suffix field. The following example shows this setting: 5. Define the questions that appear when an FS-QUO user wants to add or edit a business partner, as follows: 1. Choose Questions > [Business Partner Type] Details Questions. Example (template level): Questions > SAP Policyholder Details Questions Example (sample product): Questions > SAP Household Policy Holder Details Questions 2. Define the questions. Product Configuration in FS-PRO 111

112 3. If the question is a drop-down list, do the following: 1. Choose the question, and in the Data List Properties > General tab > Control Type field, select Data List. 2. In the Data Source tab > Product Query field, configure the rule to call the bplookup stem. Note: To find out which function to use for your question, ask your FS-QUO development environment administrator to check the available functions in the stem. For more information about FS-QUO stems, see the FS-QUO Developer Guide. 6. Design how the initial business partner questions appear on the main policy, contract, or coverage screen, as follows: 1. Choose Views > [Business Partner Type] View. Example (template level): Views > SAP Policyholder Views Example (sample product): Views > SAP Household Policy Holder View Note: The corresponding questions are defined in the [Business Partner Type] Questions component. 2. Open Questionnaire Painter. 3. Design how the questions appear on the main grid. 4. Configure the add, edit, and delete buttons. 5. Select each button, expand the Event Handlers tab, enter one of the following values in the onclick field, and choose Apply: _addchildrecord([main_grid_table]_grid,'[main_grid_table].record_selected_in') _editchildrecord([main_grid_table]_grid,'[main_grid_table].record_selected_in') _deletechildrecords([main_grid_table]_grid,'[main_grid_table].record_selected_in') The following example shows the buttons and the event handler specified for the add button: The add and edit buttons open the [Business Partner Type] Details View. The following example shows the Policyholder view and the add and edit buttons for the Sample Household Product shown in FS-QUO: 112 Product Configuration in FS-PRO

113 7. Design how the questions for adding or editing a business partner appear, as follows: 1. Choose Views > [Business Partner Type] Details View. Example (template level): Views > SAP Policyholder Details Views Example (sample product): Views > SAP Household Policy Holder Details View Note: This view appears when an FS-QUO user chooses the add or edit button in the [Business Partner Type] View. The corresponding questions are defined in the [Business Partner Type] Details Questions. 2. Open Questionnaire Painter. 3. Design how the questions appear on the details view. 4. Add icons to search, add, and edit the business partner. 5. For each of the icons, select it, and in the right panel, choose Event Handlers. 6. In the onclick field, enter the one of the following code, and choose Apply: showbusinesspartnerscreen('load'); showbusinesspartnerscreen('add'); showbusinesspartnerscreen('edit'); The following example shows the configuration for the Search Policyholder icon in the Sample Household Product: Product Configuration in FS-PRO 113

114 The following example shows the icons for the Sample Household Product in FS-QUO: 8. Configure which business partner fields to display in the add and edit business partner dialogs, as follows 1. Open the following object: Product Studio > Product Repository > [Your Company Library] > Configuration Objects > Extended Underwriting Application Configuration 2. Choose the following component: Business Partner > Business Partner Types 3. Expand the Business Partner row. The Business Partner Fields component appears. 4. Select the rows for the fields that you want to display in the add and edit dialogs, and modify the column values as needed. Notes: o If the field to display is a drop-down list, in the FieldComponentName, specify a value that matches a component in the Field Data folder. o For more information about the columns in this component, see the Product Model Help. The following example shows the Business Partner Fields component and a field that is configured to display a drop-down list: 114 Product Configuration in FS-PRO

115 The following example shows the corresponding component that defines the options in the drop-down list: 9. In the eapplication where you want to show the lateral object, do the following: 1. Open the appropriate eapp Screen. Example: Sample Household Product > User Interface > Data Capture > eapplication > eapp Section > eapp Screen. 2. Add a row for the [Business Partner Type] Details View screen, and edit the Screen Id. The following example shows the Policyholder Details row for the Sample Household Product: 3. In the Questionnaire Layout Painter, add the [Business Partner Type] Details View to the layout. 4. In the layout, select the [Business Partner Type] Details View that was added. Product Configuration in FS-PRO 115

116 5. In the right panel, choose Custom Javascript, paste the following code, and choose Apply: function updatevalue(ids, values) {for(var i=0; i<ids.length; i++) {var column_id = "table_name."+ids[i]; if(column_id == "table_name.birth_dt") {values[i] = values[i] + " 00:00:00.0";} if(document.getelementbyid(column_id)!=null) {document.getelementbyid(column_id).value = trim(values[i]);} } submitflowform('savewithoutvalidation',this);} function showbusinesspartnerscreen(actiontype) {var url = "/csiroot/cservlet/businesspartnerservlet?event="+actiontype+"&type=bp- PARTNER&tbl=mo"; var features = "status=1,"; var feature = "scrollbars=0, width=670,height=380"; if(actiontype=='add' actiontype=='edit') {feature = "scrollbars=1, width=650,height=500";} features += feature; var mywindow = window.open(url, "mywindow", features); mywindow.moveto(500, 200); mywindow.focus(); 8.8 bplookup Stem The section describes the following topics: Overview of Java Stems Using Stems Overview of Java Stems A stem is a short name that represents a Java class. These classes contain related functions that you can use in rule expressions in FS-PRO Product Configurator. For example, the com.camilion.as.stem.fspmintegrationbplookupstemclass (bplookup stem) contains a getaddresslistbypartnerid function. You can define a rule that calls this function to load addresses with a specified partner ID for a coverage. 116 Product Configuration in FS-PRO

117 8.8.2 Using Stems To use stems, proceed as follows: 1. Define a rule in Rule Painter. 2. In the Expression Editor, type the name of the stem that contains the function that you want to use, or you can click the Function Picker icon and populate the Stem List. The stem is the first element (the rule object) in the expression. 3. Type a period (.) following the stem name. The Functions List dialog box opens and displays a list of functions for the specified stem. 4. Select the function that you want use. The function signature is added to the expression. 5. Complete the rule expression as appropriate. For example, Using the bplookup stem. Note: Whenever a stem is specified, the ServiceCommand is passed to the rule. For the key MasterResultSet and ResultSet, you must specify a reference to the POLICY_QUOTE result set. 8.9 Business Partner Address Previously logic was embedded within the javascript to return the business partner address based on the selected record (partner ID). This logic was replaced with a stem function that accomplishes the same thing: CALL getaddresslistbypartnerid IN LIBRARY bplookup WITH <partnerid[string]>, <partnertypename[string]>, <role[string]>, <maxrow[int]> Functions: partnerid[string] Address records should be returned for the specified business partner record (partner ID) partnertypename[string Filter results based on the business partner type role[string] Filter results based on the business partner role maxrow[int] Specifies the number of BP address records that should be returned. Note: The benefit of a stem is that it can be used to return multiple addresses (and list them in a dropdown list) Bank Detail The getbankaccountinfobypartnerid function searches for and returns all configured bank accounts for the specified Business Partner Partner ID. Functions: partnerid[string] Bank Account records should be returned for the specified business partner record (partner ID) partnertypename[string Filter results based on the business partner type paymethod[string] Filter results based on the pay method (eg. Bank Collection) role[string] Filter results based on the business partner role maxrow[int] Specifies the number of BP bank account records that should be returned. Product Configuration in FS-PRO 117

118 Pay Card The "getbankaccountinfobypartnerid IN LIBRARY bplookup WITH <partnerid[string]>, <partnertypename[string]>, <paymethod[string]>, <role[string]>, <maxrow[int]>". Functions: partnerid[string] Bank Account records should be returned for the specified business partner record (partner ID) partnertypename[string] Filter results based on the business partner type paymethod[string] Filter results based on the pay method (eg. Bank Collection) role[string] Filter results based on the business partner role maxrow[int] Specifies the number of BP bank account records that should be returned. For more information, see SAP Underwriting for Insurance 3.0 Developer Guide. The following example shows the JavaScript code for the SAP Household Policy Holder Details View in the Sample Household Product: 118 Product Configuration in FS-PRO

119 This JavaScript code contains the functionality for the showbusinesspartnerscreen('load ADD EDIT'); call in the details view. This code calls a servlet to render the search, add, and edit dialogs. The fields that display are determined by the configuration in the Extended Underwriting Application Configuration. The following example shows an add dialog that is rendered: Configuring the Fields to Add an Insurable Object If the lateral object represents an insured object, you must configure the Extended Underwriting Application Configuration object. You must also configure the associated eapp Screen with a JavaScript function that calls a servlet to add an insured object. Proceed as follows: 1. Open the insured object at the template level. Example: [Your Company] Insurance UWA Insured Object Template Note: If your questions are specific to your product, you can define them in the model view object in the product instead of the template. For example, in the Sample Household Product, choose Sample Household Product > Contracts > Sample Household Contract > Coverages > Sample Household Coverage > Insured Objects > Sample Home Contents Insured Object 2. Choose the model view object. Example (template level): [Your Company] Insurance UWA Insured Object Template > User Interface > SAP Insured Object Model View Example (sample product): Sample Household Product > Contracts > Sample Household Contract > Coverages > Sample Household Coverage > Insured Objects > Sample Home Contents Insured Object > Sample Home Contents Insured Object > User Interface > Sample Household Insured Object Model View 3. In the Configuration folder, open the Config object, and modify the REFERENCE_PRODUCT as needed. Product Configuration in FS-PRO 119

120 4. Choose the following component and define the questions in the main grid: Questions > [Insured Object Name] Questions. Example (template level): Questions > SAP Insured Object Questions Example (sample product): Questions > SAP Household Insured Object Questions 5. Design how the questions appear on the screen, as follows: 1. Choose Views > [Insured Object Name] Questions. Example (template level): Views > SAP Insured Object Views Example (sample product): Views > SAP Household Insured Object View 2. Open Questionnaire Painter. 3. Design how the questions appear on the screen. 4. Configure a create insurable object button. 5. Select the button, expand the Event Handlers tab, enter the following value in the onclick field, and choose Apply: createinsurableobject() The following example shows the event handler specified for the button: 6. Configure which fields to display in the create insurable object view, as follows: 1. Open the following object: Product Studio > Product Repository > [Your Company Library] > Configuration Objects > Extended Underwriting Application Configuration 2. Choose the following component: Insurable Objects > Insurable Object Categories 3. Expand the Home row. The Insurable Object Types component appears. Note: You can create rows for additional categories. 4. Add rows for the insurable object types. Note: A Home Contents row is already configured in this component for the Home category. 120 Product Configuration in FS-PRO

121 5. Expand the row for the insurable object type that you want to configure fields for. For example, expand the Home Contents row. The Insurable Object Fields component appears. 6. Select the rows for the fields that you want to display in the create insurable object view, and modify the column values as needed. Notes: o If the field to display is a drop-down list, in the FieldComponentName, specify a value that matches a component in the Field Data folder. o For more information about the columns in this component, see the Product Model Help. The following example shows the Insurable Object Fields component and a field that is configured to display a drop-down list: The following example shows the corresponding component that defines the options in the drop-down list: 7. In the eapplication where you want to show the insured object view, do the following: 1. Open the appropriate eapp Screen. Example: Sample Home Contents Coverage > User Interface > Data Capture > eapplication > eapp Section > eapp Screen Product Configuration in FS-PRO 121

122 2. Add a row for the Insured Object Screen, and edit the Screen Id. The following example shows the Insured Object Screen row for the Sample Home Contents Coverage: 3. In the Questionnaire Layout Painter, add the insured object view to the layout. 4. In the layout, select the [Insured Object] Level View that was added. 5. In the right panel, choose Custom Javascript, paste the following code, and choose Apply: function createinsurableobject(){ var url = "/csiroot/cservlet/asintegrationservlet?event=create&issave=false&tbl=mo"; var features = 'toolbar=no,location=no,status=no,menubar=no,scrollbars=no,resizable=yes,width=890,height= 680'; var insuobjwin = window.open(url,'targetwindow',features); insuobjwin.focus(); } function updatevalue(ids, values) { for(var i=0; i<ids.length; i++) { var column_id = "table_name."+ids[i] ; if(document.getelementbyid(column_id)!=null){ document.getelementbyid(column_id).value = trim(values[i]); } } } 122 Product Configuration in FS-PRO

123 The following example shows the JavaScript code for the SAP Household Insured Object Level View in the Sample Home Contents Coverage: This JavaScript code contains the functionality for the createinsurableobject(); call in the view object. This code calls a servlet to render the create insurable object dialog. The fields that display are determined by the configuration in the Extended Underwriting Application Configuration Configuring Multi-Level Risk Renderer Settings The provided SAP Insurance UWA Product Template that products inherit from is configured to use the multi-level risk renderer. After you configure the eapp for your product, you must configure settings in the FS-QUO Administrative Console. Proceed as follows: 1. Log in to the FS-QUO Administrative Console at the following address: 2. Choose System > Edit Configuration Settings. 3. Go to the following location: Configuration > Application > AuthoritySuite > Env > Application Environment 4. Find the CustomIncludeScript row, and set the Override field to the following value: /classpath/com/camilion/renderer/multilevelrisk/web/js/commoninclude.js 5. Find the eappcustomgridenabled row, and set Override field to False. 6. Save your changes. Product Configuration in FS-PRO 123

124 8.10 Removing the Renewals and Premium Audits Menu Options in FS-QUO In an integrated environment with FS-PRO, FS-QUO, and FS-PM, FS-QUO is only used to write new policies and not for post-bind transactions. To prevent users from accessing the renewals and premium audits post-bind screens, remove the Manage > Renewals and Manage > Premium Audits menu options from FS-QUO. Proceed as follows: 1. In Product Configurator, open the following object: Product Studio > Product Repository > [Company] Library > Configuration Objects > Extended Underwriting Application Configuration 2. Choose the following component: Extended Underwriting Application Configuration > Role Framework > Role 3. In the Values tab, for each role that will be used in the integrated environment, do the following: 1. Expand the row. The Permission and Portal Menu components appear. 2. Choose the Portal Menu tab. 3. Expand the row where controlname is managemenu. 4. In the Portal Menu Item component, deselect the Premium Audits and Renewals rows. 5. Save your changes. 4. Choose the following component: Extended Underwriting Application Configuration > Screen Framework > Screen 5. In the Values tab, do the following: 1. Expand the Screens_Dialog_WorkList_ProducerWorkFlow_ViewWorkList_Screen row. The Screen Control component appears. 2. Deselect the portalpremauditbtn and portalrenewalsbtn rows. 3. Save your changes. 4. Expand the Screens_Dialog_WorkList_ViewWorkList_Screen row. The Screen Control component appears. 5. Deselect the portalpremauditbtn and portalrenewalsbtn rows. 6. Save your changes. 6. Publish your products. Note: For more information about roles and permissions, see the FS-QUO Developer Guide. 124 Product Configuration in FS-PRO

125 9 Publishing a Product in FS-PRO After the marketable product is configured in Product Configurator, you can publish the product. The publishing process does the following: Creates a product JAR. If FS-PRO is set up to connect to IFBC of FS-PM, the XML representation of the product is sent directly to IFBC (see chapter 4). After publishing the product, you must deploy the product to the servers that need the product data. You can deploy the product JAR to Product Web Services and FS-QUO. The deploy process copies the product JAR to the specified server. For example, after you deploy a product to FS-QUO, you can write a new business for that product using the FS-QUO user interface. FS-QUO then uses XSLT to translate the policy model to an XML format for FS-PM. 9.1 Publish the Product, Send Structure Info, and Deploy Proceed as follows: 1. In Product Configurator, open your marketable product. 2. Choose File > Publish Product. 3. In the Pre and Post Publishing Services section, select the following services: o Send Structure Info to IFBC o Upload & Deploy to Runtime 4. Choose Execute Now or Execute Later. After publishing completes, the generated product structure XML file is sent to IFBC, The product JAR is also uploaded to the product repository and deployed to the Product Web Services Manager runtime. Note: For more information about publishing, see the SAP Product Lifecycle Management for Insurance Product Configurator User Guide. 9.2 Download the Generated XML File for IFBC Optionally, after the product is published and the IFBC post-publish service is executed, you can view the generated XML file that is sent to IFBC. Proceed as follows: 1. In Product Configurator, choose Tools > Scheduled Activity Manager. 2. In the Completed tab, find the publishing task that you performed and choose the Logs/Output icon. 3. Click one of the following and save the file: o Click here to download the XML Downloads the hierarchical XML file o Click here to download the sorted XML Downloads the sorted XML file 4. Open the downloaded XML file in an XML reader. Note: IFBC sends a response file after the import. To see this file, you can click the following link from the Logs/Output dialog: Click here to download the response XML Publishing a Product in FS-PRO 125

126 If the <EV_RC> tag has a 0 (zero) value, the import was successful. If the value is a number other than 0, IFBC encountered an issue. For information about these error codes, see the FS-PM documentation. 126 Publishing a Product in FS-PRO

127 10 IFBC Import of FS-PRO Product Data In addition to the actual IFBC import, you must adapt the following Customizing settings after the IFBC import has been executed: Product Module Group Customizing in FS-PM Assignment of Business Transactions 10.1 IFBC Import Depending on the operation mode you choose in FS-PRO (see section 4.4), either the IFBC import is started automatically or you must start the IFBC import manually. If you have to start the IFBC import manually, perform the Customizing Activity Execute Import of FS-PRO Product Data in Customizing for Policy Management under In-Force Business Management Basis In-Force Business Configurator. For more information, see the documentation of the Customizing activity Product Module Group Customizing in FS-PM The configuration of new products in FS-PRO (or any other product engine) results in new product modules for the product model classes of the coverage-first data model (such as sales product, product, elementary product or subcoverage). A product module is tagged with a unique product module ID that has to be assigned in the IFBC control attributes of the respective product module (see section on how to do this). The product module IDs are part of the static product information that is imported into IFBC. If a new IFBC product template has been created during import, the following applies: The new product module ID must be assigned to new or existing product module groups in FS-PM so that the Customizing settings defined in the product module group Customizing of FS-PM become effective. Without this assignment, policy processing in FS-PM will raise error messages for the new unassigned product modules. To assign the new product module IDs, choose Define Product Module Groups in Customizing for Policy Management under In-Force Business Management -> Basis -> Basic Settings. For more information, see the documentation of this Customizing Activity and section of this guide Assigning Business Transactions To execute business transactions for new IFBC product templates created during the import, you must assign these business transactions to the corresponding IFBC product templates. For more information, look for Assignment of Business Transactions in the application help of SAP Policy Management at IFBC Import of FS-PRO Product Data 127

128 11 Enhancement Options This section describes the following topics; Areas to be Enhanced in Different Systems Entities and Templates in FS-PRO Supported Enhancement Scenarios 11.1 Areas to be Enhanced in Different Systems You can enhance the current integration scenario between the systems FS-PRO, FS-QUO, and FS-PM in the following areas: User interface (in each system) Process/coding (in each system) Database (in each system) Interfaces between the three systems FS-PRO, FS-QUO, and FS-PM In the following graphic, you can see the possible enhancement options: 128 Enhancement Options

129 11.2 Entities and Templates in FS-PRO To enhance FS-PRO, FS-QUO, and FS-PM, you need to know where and how information is typically grouped and stored. The grouping is realized through entities. The integration scenario differentiates between the following entities: Entities Used for the Sample Household Product Examples for these entities are part of the 'Sample Household Product' that is included in the shipment. You can use these examples and configure your own products based on the FS-PRO templates provided. These examples should give guidance how typical product requirements and rating can be implemented (for instance, the adding and removal of a clause in the Product Web Service (PWS) depending on a condition can be learned from the Underinsurance Waiver Clause in the Sample Household Product). Note: Customer specific products will deviate from these examples. Entities not used in the Sample Household Product such as Beneficiary, Contract Bundle, Coverage Bundle These entities are not part of the 'Sample Household Product' since, from a business perspective, they do not make sense for a simple household insurance product. However, these entities are provided in the shipment and ready for use, but you will not find examples of these assembled in a sample product. Customers should be able to add these entities to their products easily if they add the appropriate product configuration as described in sections 4 and For more information about entities, see section Error! Reference source not found.. Note: If you want to use an entity that is not provided out-of-the-box, please contact SAP development Supported Enhancement Scenarios SAP supports the following enhancement scenarios: Customer wants to use entities provided out-of-the box Customer wants to add new fields to an entity Enhancement Options 129

130 Using Entities Provided Out-of-the-Box This section describes how to enhance the integration scenario with entities provided out-of-the box. For more information, see. Proceed as follows: Enhancement of interfaces (mandatory) For the interface FS-QUO -> FS-PM, proceed as follows: On the FS-QUO side, you must adapt the call of the APIF wrapper (see section ). On the FS-PM side, you must adapt the call of the APIF wrapper. Enhancement of processes in FS-PM (optional) In FS-PM, for more information about the enhancement options of processes, see the following references: o Enhancement Guide for SAP Policy Management, section 7 (BAdIs) o Enhancement Guide for SAP Policy Management, section 9 (Enhancement of Standard Business Transactions) o Customizing for Policy Management under In-Force Business Management -> Basis -> Business Processes - > Business Add-Ins (BAdIs) In FS-QUO (see section ) FS-PRO: New rules, etc. (see section ) Adding New Fields to an Out-of-the-Box Entity This section applies if you are using FS-PRO as your product engine. To add new fields to an entity, proceed as follows: Enhancement of database (mandatory) You must enhance the database in FS-PM. For more information, see Enhancement Guide for SAP Policy Management, section 3.1 (DDIC Enhancements) You must enhance the database in FS-PRO (see section ) You must enhance the database in FS-QUO. For more information, contact your SAP implementation team or SAP Support. 130 Enhancement Options

131 Enhancement of user interface (optional, since in some cases no UI is needed) Enhancement of UI in FS-PM. For more information, see Enhancement Guide for SAP Policy Management, section 4 (Changes to User Interface). Enhancement of UI in FS-PRO (see section ) Enhancement of UI in FS-QUO For more information, contact your SAP implementation team or SAP Support. Enhancement of interfaces (optional, since in some cases interfaces are not affected) FS-QUO -> FS-PM: o On the FS-QUO side, you must adapt the call of the APIF wrapper. For more information, contact your SAP implementation team or SAP Support. o On the FS-PM side, no action is required since the APIF wrapper is automatically enhanced after a database enhancement. FS-PM -> FS-PRO: o Call of Product Web Service (PWS) FS-PM -> Other systems like FS-CM, FS-CD, FS-ICM, FS-RI etc. (see Enhancement Guide for SAP Policy Management, section 12 (Integration with Other Components)). Enhancement of processes (optional) In FS-PM: For more information about the enhancement options of processes in FS-PM, see the following references: o Enhancement Guide for SAP Policy Management, section 7 (BAdIs) o Enhancement Guide for SAP Policy Management, section 9 (Enhancement of Standard Business Transactions) o Customizing for Policy Management under In-Force Business Management -> Basis -> Business Processes - > Business Add-Ins (BAdIs) In FS-QUO: For more information, contact your SAP implementation team or SAP Support. FS-PRO: New rules, etc. (see section ) Adding New Fields in FS-PRO To add a new field to an entity, you must modify the product in Product Configurator. For example, you might want to record a new date value for policies. You must add the date field to a contract in the marketable product. Note: If you want to add the new field to FS-QUO, additional configuration is required. For example, to get the date value from a customer, you can add the field to the FS-QUO UI so that producers or underwriters can enter a value. For help with this FS-QUO configuration, contact your SAP implementation team or SAP Support. Enhancement Options 131

132 Add the New Field to IFBC Column Details 1. In Product Configurator, open your marketable product. 2. Open the entity object that you want to add a new field to. 3. Open the following object: [Entity/Object name] > Configuration > Integration > IFBC [Object type name] Integration Services > IFBC Column Details 4. Add a row for the new field, and select it. 5. This configuration specifies the new field as a characteristic (mark). Note: If the corresponding attribute does not exist in the PBT, you must add it to the appropriate channel model. Otherwise, the IFBC import will not work properly. For more information about adding attributes to the PBT, see the PBT documentation. Update the Policy Model Schema 1. Open the following object: [Marketable product] > Configuration > Integration > Product Web Services > XML Definitions > SAPInsurancePnCPolicyModelSchema 2. In the Schema tab, choose View XSD icon. 3. In the XML Definition Viewer, select all the text and copy it. 4. Paste the code into an editor, delete the <xs:sequence> and </xs:sequence> tags, and save the file with an XSD extension. 5. Go to the following location: [Your Company Library] > Components > XML Definitions Note: If this folder does not exist, create it. 6. Create an object of type XML Definition, name it CustomSAPInsurancePnCPolicyModelSchema, and open it. 7. In the Schema tab, choose the Import XSD icon, browse for the XSD file that you created, and choose Upload. The XSD is copied to the new object. 8. Add a new simple element for the new field. 9. Save your changes. 10. Assemble CustomSAPInsurancePnCPolicyModelSchema into the following folder: [Marketable Product] > Configuration > Integration > Product Web Services > XML Definitions Modify Rules to Refer to the Updated Policy Model Schema 1. Go to the following location: [Marketable Product] > Configuration > Integration > Product Web Services > Product Web Services 2. In the Values tab, override the association and values of the rows that contain rules that reference the schema (for example, pcratingws and pcmodcontractws). 3. In each overridden row, do the following: 1. Edit the rule. 2. In Rule Painter, in the xmlrequest row, modify the XML Object Name to CustomSAPInsurancePnCPolicyModelSchema. 132 Enhancement Options

133 3. In the Return Type section, modify the XML Object Name to point to CustomSAPInsurancePnCPolicyModelSchema. Note: When you override rows, data will not be inherited from updated templates. If you change templates or upgrade FS-PRO, we recommend that you delete the override to restore the inherited data, and override the rows again with the rule changes. 4. Save your changes. 5. If the new field affects rating, do the following: 1. Open the object that contains the relevant rating rule, as follows: [Entity/Object name] > Rating > SAP Rating 2. Deviate the rating rule and make changes to include the new field in the calculations or set a value to the new field as a response to FS-PM. 3. Save your changes. Note: For more information about rule deviations, see the SAP Product Lifecycle Management for Insurance Product Configurator User Guide, and search for FS-PRO rule deviation SAP Notes at Update the Data Model You must add the new field to a table (data definition) in the data model. If you want to add a field that is common to products in all lines of business, add the field to the appropriate SAP Insurance Reference Data Model basis table in the following location: Product Studio > Product Repository > [Company] Library > Data Definitions > Extended If you want to add a field that is specific to P and C products, add the field to the appropriate P and C extended table in the following location: Product Studio > Product Repository > [Company] Library > Data Definitions > Extended > PnC Build and Publish the Product 1. Open your marketable product. 2. Build metadata, questionnaire views, screens, and rules. 3. Publish your product and send the structure info to IFBC, The appropriate product templates are updated in IFBC. FS-PM can transfer corresponding policy and endorsement information to FS-PRO for rating using product web service requests. Note: For information about publishing, see Publish the Product, Send Structure Info, and Deploy (page 125). Enhancement Options 133

134 12 List of Provided Entities This section lists the entities that are provided out-of-the-box. Used Entities In the following table, you can find a list of used entities: Technical Name Title Auto Entities /MVA/AMDABM /MVA/AMDACLAIMSU /MVA/AMDACLPART /MVA/AMDACOV /MVA/AMDAEXEQMT /MVA/AMDAPCMP /MVA/AMDAPOLPR /MVA/AMDATR Bonus-Malus Calculate Claim Surrender Bonus-Malus - Claim Comparison Auto Coverage Special Equipment Premium Comparison Auto Contract Region Class Type Other Entities /PM0/ABDAAGENT /PM0/ABDABNF /PM0/ABDABNFCRY /PM0/ABDACBCPAYR /PM0/ABDACLAUSE /PM0/ABDACOV /PM0/ABDACOVCPCO /PM0/ABDACOVPAC /PM0/ABDACRDITOR /PM0/ABDADEDCTBL /PM0/ABDADEP /PM0/ABDADEPREL /PM0/ABDADISTREL /PM0/ABDAEXREF /PM0/ABDAEXTPCL Representative Benefit Beneficiary CBC Amount Payer Clause Coverage Subcoverage (P&C) Coverage Bundle Creditor Deductible Dependency Dependency Assignment Distribution Plan Relationship External Reference Related Policy Claim 134 List of Provided Entities

135 Technical Name /PM0/ABDAEXTPOL /PM0/ABDAINFRD /PM0/ABDALIMIT /PM0/ABDAPOLHLDR /PM0/ABDAPOLICY /PM0/ABDAPOLPR /PM0/ABDAPPDPAC /PM0/ABDAPREM /PM0/ABDAPRMPAYR /PM0/ABDAREPVAL /PM0/ABDARESDEPC /PM0/ABDASBADR /PM0/ABDASBINC /PM0/ABDASUBJCT /PM0/ABDASUPDC /PM0/ALDAADDPRPY /PM0/ALDABNF /PM0/ALDACOLLECT /PM0/ALDACOV /PM0/ALDAINDINC /PM0/ALDAPARTPAY /PM0/ALDAPOLPR /PM0/ALDAPREM /PM0/ALDAPREMDEP /PM0/ALDAPROJEC /PM0/ALDASSHEAD /PM0/ALDASSWITCH /PM0/ALDASUBSAG /PM0/APDACOV /PM0/APDAPOLPR /PM0/ABDASBINC Title Related Policy Dynamic Adjustment Limit Policyholder Policy Contract Contract Package Premium Premium Payer Reported Value Process-Dependent Condition Insured Object Address Assignment Object Management Insured Object Surcharge/Discount Special Deposit Payer Life Benefit Collection Life Coverage Individual Maximum Subsidized Premium Partial Payment Contract Premium Premium Deposit Model Calculation Shift Switch Header Shift Switch Subsidy Agency P&C Coverage P&C Contract Insured Extension List of Provided Entities 135

136 13 Appendix 13.1 Terms for Included Open Source Software This SAP software contains also the third party open source software products listed below. Please note that for these third party products the following special terms and conditions shall apply. 1. This software was developed using ANTLR. 2. gsoap Part of the software embedded in this product is gsoap software. Portions created by gsoap are Copyright (C) Robert A. van Engelen, Genivia inc. All Rights Reserved. THE SOFTWARE IN THIS PRODUCT WAS IN PART PROVIDED BY GENIVIA INC AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 3. SAP License Agreement for STLport SAP License Agreement for STLPort between SAP Aktiengesellschaft Systems, Applications, Products in Data Processing Neurottstrasse Walldorf, Germany (hereinafter: SAP) and you (hereinafter: Customer) a) Subject Matter of the Agreement A) SAP grants Customer a non-exclusive, non-transferrable, royalty-free license to use the STLport.org C++ library (STLport) and its documentation without fee. B) By downloading, using, or copying STLport or any portion thereof Customer agrees to abide by the intellectual property laws, and to all of the terms and conditions of this Agreement. C) The Customer may distribute binaries compiled with STLport (whether original or modified) without any royalties or restrictions. D) Customer shall maintain the following copyright and permissions notices on STLport sources and its documentation unchanged: Copyright 2001 SAP AG E) The Customer may distribute original or modified STLport sources, provided that: o The conditions indicated in the above permissions notice are met; o The following copyright notices are retained when present, and conditions provided in accompanying permission notices are met: Coypright 1994 Hewlett-Packard Company Copyright 1996,97 Silicon Graphics Computer Systems Inc. Copyright 1997 Moscow Center for SPARC Technology. Copyright 1999,2000 Boris Fomitchev Copyright 2001 SAP AG 136 Appendix

137 Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Hewlett-Packard Company makes no representations about the suitability of this software for any purpose. It is provided as is without express or implied warranty. Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Silicon Graphics makes no representations about the suitability of this software for any purpose. It is provided as is without express or implied warranty. Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Moscow Center for SPARC makes no representations about the suitability of this software for any purpose. It is provided as is without express or implied warranty. Boris Fomitchev makes no representations about the suitability of this software for any purpose. This material is provided "as is", with absolutely no warranty expressed or implied. Any use is at your own risk. Permission to use or copy this software for any purpose is hereby granted without fee, provided the above notices are retained on all copies. Permission to modify the code and to distribute modified code is granted, provided the above notices are retained, and a notice that the code was modified is included with the above copyright notice. Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. SAP makes no representations about the suitability of this software for any purpose. It is provided with a limited warranty and liability as set forth in the License Agreement distributed with this copy. SAP offers this liability and warranty obligations only towards its customers and only referring to its modifications. b) Support and Maintenance SAP does not provide software maintenance for the STLport. Software maintenance of the STLport therefore shall be not included. All other services shall be charged according to the rates for services quoted in the SAP List of Prices and Conditions and shall be subject to a separate contract. c) Exclusion of warranty As the STLport is transferred to the Customer on a loan basis and free of charge, SAP cannot guarantee that the STLport is error-free, without material defects or suitable for a specific application under third-party rights. Technical data, sales brochures, advertising text and quality descriptions produced by SAP do not indicate any assurance of particular attributes. d) Limited Liability A) Irrespective of the legal reasons, SAP shall only be liable for damage, including unauthorized operation, if this (i) can be compensated under the Product Liability Act or (ii) if caused due to gross negligence or intent by SAP or (iii) if based on the failure of a guaranteed attribute. B) If SAP is liable for gross negligence or intent caused by employees who are neither agents or managerial employees of SAP, the total liability for such damage and a maximum limit on the scope of any such damage shall depend on the extent to which its occurrence ought to have anticipated by SAP when concluding the contract, due to the circumstances known to it at that point in time representing a typical transfer of the software. C) In the case of Art. 4.2 above, SAP shall not be liable for indirect damage, consequential damage caused by a defect or lost profit. D) SAP and the Customer agree that the typical foreseeable extent of damage shall under no circumstances exceed EUR 5,000. E) The Customer shall take adequate measures for the protection of data and programs, in particular by making backup copies at the minimum intervals recommended by SAP. SAP shall not be liable for the loss of data and its Appendix 137

138 recovery, notwithstanding the other limitations of the present Art. 4 if this loss could have been avoided by observing this obligation. F) The exclusion or the limitation of claims in accordance with the present Art. 4 includes claims against employees or agents of SAP. 4. Adobe Document Services Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and / or other countries. For information on Third Party software delivered with Adobe document services and Adobe LiveCycle Designer, see SAP Note Appendix

139 Appendix 139

140 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see for additional trademark information and notices. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE s or its affiliated companies strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.