SAP Policy Management 5 · PDF fileThese include report names, program ... SAP Policy...

Installation Guide

SAP Policy Management

Document Version: 1.0 – 2017-04-27

CUSTOMER

SAP Policy Management 5.4 Installation Guide

2

Customer

© 2017 SAP SE or an SAP affiliate

company. All rights reserved.

4

Introduction

Typographic Conventions

Type Style Description

Example Words or characters quoted from the screen. These include field names, screen titles,

pushbuttons labels, menu names, menu paths, and menu options.

Textual cross-references to other documents.

Example Emphasized words or expressions.

EXAMPLE Technical names of system objects. These include report names, program names,

transaction codes, table names, and key concepts of a programming language when they

are surrounded by body text, for example, SELECT and INCLUDE.

Example Output on the screen. This includes file and directory names and their paths, messages,

names of variables and parameters, source text, and names of installation, upgrade and

database tools.

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

they appear in the documentation.

<Example> Variable user entry. Angle brackets indicate that you replace these words and characters

with appropriate entries to make entries in the system.

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

SAP Policy Management 5.4

Introduction

Customer


company. All rights reserved. 3

Document History

Version Date Change

1.0 2017-04-27 First version of this guide

4

Customer



4

Introduction

Table of Contents

1 Introduction ................................................................................................................................... 6 1.1 About this Document ............................................................................................................................ 6 1.2 Integration .............................................................................................................................................. 6 1.3 Implementation Considerations .......................................................................................................... 7 1.4 Naming Conventions ............................................................................................................................. 8 1.5 Documentation ...................................................................................................................................... 9

1.5.1 Application Help SAP Policy Management ......................................................................... 9 1.5.2 New Features in SAP Policy Management 5.4 ................................................................... 9 1.5.3 Related Guides ...................................................................................................................... 9

1.6 General Quick Links ............................................................................................................................. 10 1.7 Before You Start ................................................................................................................................... 11

1.7.1 Accessing the SAP Software Download Center ................................................................ 11 1.7.2 SAP Download Manager ...................................................................................................... 11 1.7.3 Ordering Software on CD or DVD ....................................................................................... 11 1.7.4 License Key ........................................................................................................................... 11 1.7.5 Password .............................................................................................................................. 12 1.7.6 SAP Notes for the Installation ............................................................................................. 12

2 Installation ................................................................................................................................... 14 2.1 Planning .................................................................................................................................................14

2.1.1 Required Documentation about Product Engine ..............................................................14 2.1.2 Definition of Languages Used ............................................................................................. 15 2.1.3 Clarification of Required Product Engine Version .............................................................16 2.1.4 Clarification of Authorization Concept ...............................................................................16

2.2 Installation Activities ............................................................................................................................16 2.2.1 Installing SAP Policy Management 5.4 ..............................................................................16 2.2.2 Installing the Product Engine .............................................................................................. 17

3 Configuration ............................................................................................................................... 19 3.1 SAP Notes .............................................................................................................................................19 3.2 Configuration Activities ........................................................................................................................19

3.2.1 Delivery of Customizing SAP Policy Management 5.4 .....................................................19 3.2.2 Creating an Output Device ................................................................................................. 20 3.2.3 Integration of SAP Components ........................................................................................ 20 3.2.4 Defining Companies ............................................................................................................ 23 3.2.5 Maintaining Calendar .......................................................................................................... 23 3.2.6 Maintaining Number Range Intervals ................................................................................ 24 3.2.7 Configuring the Product Engine ........................................................................................ 29 3.2.8 Configuring SAP Business Workflow ................................................................................ 30 3.2.9 Configuring Policy Management, Group Insurance Features ......................................... 32 3.2.10 User Group .......................................................................................................................... 33 3.2.11 Optional Installation of Enterprise Search ........................................................................ 33 3.2.12 Setting Up Cash-Before-Cover (Optional) ........................................................................ 33 3.2.13 Settings for Performance ................................................................................................... 33


Introduction

Customer



3.2.14 First Check ........................................................................................................................... 33

4 Additional Information ............................................................................................................... 35 4.1 Deinstalling SAP Policy Management 5.4 .......................................................................................... 35 4.2 Customizing ......................................................................................................................................... 35 4.3 Post-Installation Steps ........................................................................................................................ 35 4.4 Interrupted Installation ........................................................................................................................ 35 4.5 Support ................................................................................................................................................. 35

6

Customer



4

Introduction

1 Introduction

1.1 About this Document

Purpose

This Installation Guide describes the installation and configuration process for SAP Policy Management (FS-PM).

Target Audience

• Consultants

• System administrators

• Others

Constraints

This guide does not provide:

• Installation and Customizing information for the product engine msg.PM

• Installation and Customizing information for the product engine SAP Product Lifecycle Management for

Insurance (FS-PRO)

• Installation, configuration and integration of other applications

• Complete Configuration and Customizing information for SAP Policy Management

1.2 Integration

SAP Policy Management is embedded in the SAP for Insurance landscape and uses interfaces to communicate

with other applications such as BP (SAP Business Partner), FS-CD (SAP Collections and Disbursements for

Insurance), FS-CM (SAP Claims Management), FS-ICM (SAP Incentive and Commission Management), FS-RI

(SAP Reinsurance), and so on.

For more information about integration, see the SAP Policy Management -> Application Help -> SAP Library for

SAP Policy Management -> Integration.

https://uacp2.hana.ondemand.com/viewer/p/SAP_POLICY_MANAGEMENT


Introduction

Customer



To run SAP Policy Management 5.4, you need a connection to a product engine. You can integrate one of the

following product engines into SAP Policy Management 5.4:

• msg.PM

• SAP Product Lifecycle Management for Insurance (FS-PRO)

Alternatively, you can connect a different product engine.

1.3 Implementation Considerations

Before installing SAP Policy Management, consider the following notes concerning the installation of SAP Policy

Management:

Keyword Note

SAP NetWeaver The required SAP NetWeaver release for SAP Policy Management 5.4 is SAP

NetWeaver 7.50, SP06 (or higher).

SAP ERP • SAP recommends to run SAP Policy Management (FS-PM) 5.4 always based

on the last support package available and together with one of the following

SAP enhancement packages:

o SAP enhancement package 7 for SAP ERP 6.0, SP12 (or a higher SP)


• You must install SAP Policy Management 5.4 and SAP ERP 6.0 on different

SAP NetWeaver instances.

• In case you use two different physical systems, you must ensure that one of

the following conditions apply to the two different physical systems:

o Both physical systems are Unicode systems.

o None of the physical systems is a Unicode system.

SAP Policy

Management add-on for

Group Insurance (FS-

PM-PMG)

FS-PM-PMG is an add-on implementation based on SAP Policy Management.

FS-PM-PMG is automatically installed with FS-PM (contrary to FS-PM-AUTO).

However, if you want to use FS-PM-PMG you must activate FS-PM-PMG explicitly

in your system.

For more information about the installation of FS-PM-PMG, see SAP Policy

Management, Add-On for Group Insurance -> Installation and Upgrade Information

-> Installation Guide.

SAP Policy

Management add-on for

Auto Insurance (FS-PM-

AUTO)

FS-PM-AUTO is an add-on implementation based on SAP Policy Management.

If you use FS-PM-AUTO, always ensure that the corresponding FS-PM-AUTO

support package is available before you use the last available FS-PM support

package.

FS-PM

RCreate new business

Periodic upate

Information

Change / universal ChangeResetReverse

Msg.pm

RCalculate

Import data

PM data

FS-CD

Collection

Disbursements

FS-CD data

R

FS-CM

Claims

Handling

FS-CM data

R

FS-ICM

Commissions

FS-ICM data

R

FS-RI

Reinsurance

FS-RI data

R

Business

Partner

BP data

R

FI

FI data

R

FPO

FPO data

R RCalculate

Import data

FS-PRO/

FS_PWS

FS-PRO

data

R

Msg.pm data

FS-QUO

Create new business

Find Policy

Retrieve Policy

FS-QUO data

https://uacp2.hana.ondemand.com/viewer/p/SAP_POLICY_MANAGEMENT,_ADD-ON_FOR_GROUP_INSURANCE

https://uacp2.hana.ondemand.com/viewer/p/SAP_POLICY_MANAGEMENT,_ADD-ON_FOR_GROUP_INSURANCE

8

Customer



4

Introduction

Keyword Note

Support Package SAP system Support Packages can only be imported into SAP Policy Management

if they are released for SAP Policy Management.

1.4 Naming Conventions

In this documentation, the following naming conventions apply.

Terminology

Term Description


(Abbreviation: FS-PM)

Official name for SAP Policy Management

FSPM Name of the software component for SAP Policy Management

SAPK-540XXINFSPM Name of the component and the version for searching for notes on

installation in SAPNET.

For notes about Support Packages, the characters XX are replaced by the

number for the Support Package, for example, search for notes about

Support Package 02 → SAPK-54002INFSPM.

Variables

Variables Description

<SAPSID> SAP system ID in uppercase letters

<sapsid> SAP system ID in lowercase letters

<DBSID> Database system ID in uppercase letters

<dbsid> Database system ID in lowercase letters

<SAINT_INSTDIR> Installation directory for the SAP installation tool SAINT

<INSTDIR> Installation directory for the SAP system

<DVD-DIR> Directory on which a DVD is installed

<OS> Operating system name within a path

The following examples show how the variables are used:


Introduction

Customer



Example

Log on as user <sapsid>adm and change to the directory /usr/sap/<SAPSID>. If your SAP system ID is

C11, log on as user c11adm and change to the directory /usr/sap/C11.

1.5 Documentation

1.5.1 Application Help SAP Policy Management

You can find the application help for SAP Policy Management under SAP Policy Management -> Application Help -

> SAP Library for SAP Policy Management.

1.5.2 New Features in SAP Policy Management 5.4

For information about what is new and what has changed since the last release, see SAP Policy Management ->

What's New.

1.5.3 Related Guides

Title Internet Address Description

Master Guide

SAP for

Insurance

SAP Policy Management → Installation and Upgrade

→ Master Guide SAP for Insurance

Entrance point for planning an

installation in your system

landscape

How-To Guides

SAP Policy

Management

SAP Policy Management → How-to Guides Information about how to perform

specific tasks and additional

documentation required to plan,

install, operate, and use SAP

Policy Management

Installation

Guide

SAP NetWeaver

SAP NetWeaver 7.50 → Installation and Upgrade →

Installation Guide

Information about how to plan and

install SAP NetWeaver 7.50

Installation

Guide

SAP ERP

SAP ERP → Installation and Upgrade → Installation

Guide


install SAP ERP 6.0 enhancement

package 7

Installation

Guide

See chapter 2.1.1.1





https://uacp2.hana.ondemand.com/viewer/p/SAP_NETWEAVER_750

https://uacp2.hana.ondemand.com/viewer/product/SAP_ERP/6.0.7/en-US

10

Customer



4

Introduction

Title Internet Address Description

Msg.PM

Installation

Guide

FS-PRO

SAP Product Lifecycle Management for Insurance →

Installation and Upgrade → Installation Guide


install SAP Product Lifecycle

Management for Insurance 3.0

Integration

Guide

SAP Policy

Management

with FS-PRO

SAP Product Lifecycle Management for Insurance →

Integration → Integration Guide

Information about how to combine

the SAP Policy Management with

Product and SAP Policy Lifecycle

Management for Insurance

Installation

Guide

SAP Policy

Management

add-on for Auto

Insurance (FS-

PM-AUTO)

SAP Policy Management Add-On for Auto Insurance

→ Installation and Upgrade → Installation Guide


install SAP Policy Management

add-on for Auto Insurance 1.5

Installation

Guide

SAP Policy

Management

add-on for

Group Insurance

SAP Policy Management, Add-On for Group

Insurance → Installation and Upgrade → Installation

Guide


install SAP Policy Management

add-on for Group Insurance 1.1

1.6 General Quick Links

Title Internet Address

SAP Notes https://support.sap.com/notes

Installation and Upgrade Guides http://service.sap.com/instguides

Product Availability Matrix https://support.sap.com/release-upgrade-maintenance/pam.html

Sizing http://service.sap.com/sizing

Security http://service.sap.com/security

SAP Help Portal http://help.sap.com

https://uacp2.hana.ondemand.com/viewer/p/SAP_PRODUCT_LIFECYCLE_MANAGEMENT_FOR_INSURANCE


https://uacp2.hana.ondemand.com/viewer/p/SAP_POLICY_MANAGEMENT_ADD-ON_FOR_AUTO_INSURANCE

https://uacp2.hana.ondemand.com/viewer/p/SAP_POLICY_MANAGEMENT,_ADD-ON_FOR_GROUP_INSURANCE?q=SAP%20Policy%20Management%20add-on%20for%20Group%20Insurance&state=PRODUCTION&format=standard,html,pdf,others

https://uacp2.hana.ondemand.com/viewer/p/SAP_POLICY_MANAGEMENT,_ADD-ON_FOR_GROUP_INSURANCE?q=SAP%20Policy%20Management%20add-on%20for%20Group%20Insurance&state=PRODUCTION&format=standard,html,pdf,others

https://support.sap.com/notes

http://service.sap.com/instguides

https://support.sap.com/release-upgrade-maintenance/pam.html

http://service.sap.com/sizing

http://service.sap.com/security

http://help.sap.com/


Introduction

Customer



1.7 Before You Start

1.7.1 Accessing the SAP Software Download Center

• Software Download Center: https://support.sap.com/swdc

• Installations and Upgrades: https://support.sap.com/installations or https://support.sap.com/release-

upgrade-maintenance/upgrade-info.html

• Support Packages and Patches: https://support.sap.com/patches

If you experience problems when downloading software, create a customer message under component XX-SER-

SWFL-ESD.

1.7.2 SAP Download Manager

To download software from the Software Download Center, use the SAP Download Manager on SAP Support

Portal at https://support.sap.com/swdc → Download Manager.

If you experience problems with the SAP Download Manager, create a customer message under component XX-

SER-SAPSMP-SDM.

1.7.3 Ordering Software on CD or DVD

As an alternative to downloading software from the Software Download Center, you can also order software on CD

or DVD from the SAP Software Shop. For more information, see SAP Support Portal at

https://support.sap.com/swdc → Software Download.

If you experience problems when ordering software, create a customer message under component XX-SER-

SWFL-SHIP.

1.7.4 License Key

On installation of an SAP system, a temporary license key that is valid for four weeks is created automatically. You

must apply for a permanent license key immediately after having installed your SAP software (for more

information, see SAP Note 94998). To do so, see SAP Support Portal at https://support.sap.com/licensekey.

You will need the authorization LICENSE KEY ASSIGNMENT (for more information, see SAP Notes 103926 and

124703).

If you have any problems, create a customer message under component XX-SER-LIKEY.

The CD License Keys & License Audit is part of your software package. It contains the complete documentation

and important information about the license auditing tools and the preparations you need to make for license

auditing.

https://support.sap.com/swdc

https://support.sap.com/installations

https://support.sap.com/release-upgrade-maintenance/upgrade-info.html

https://support.sap.com/release-upgrade-maintenance/upgrade-info.html

https://support.sap.com/patches



http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=DISPL_TXT&_NNUM=94998&

https://support.sap.com/licensekey



12

Customer



4

Introduction

1.7.5 Password

The password for SAP Policy Management 5.4 that is required for installation is defined in SAP Note 2412645.

1.7.6 SAP Notes for the Installation

Before you start the installation, you must read the following SAP Notes. These SAP Notes contain the most

recent information on the installation.

Important additional information for SAP Policy Management 5.4

SAP Note Number Title

2412645 Release strategy for ABAP add-on FSPM 540

2428681 Release Information Note (RIN) for FSPM 540

SAP Notes about the installation procedure


19466 Downloading SAP kernel patches

83458 OCS Info: Patch download from SAP Service

Marketplace

94998 Requesting license keys and deleting systems

103926 User administration

124703 Authorization for license key request

159442 Releasing the Engineering Workbench

337623 Customizing after implementation or upgrade

830722 Current Note for language transports in Release 7.00

1280603 Returning of Long Text Messages from

CACS00_RFC_CASE

SAP Notes about inclusion in the solution


33040 Options in exchange upgrade with Add-On
















Introduction

Customer



SAP Notes about installing and connecting to Product Engine (msg.PM)


718815 msg.PM connection: Combination of individual

components

2151449 Release strategy for ABAP add-on MSGPMCON

SAP Notes about add-ons


33040 Options in exchange upgrade with add-on

70228 Add-Ons: Conditions

160168 Support Packages for SAP Add-Ons






14

Customer



4

Installation

2 Installation

2.1 Planning

Purpose

Before you start with the installation of SAP Policy Management 5.4, it is important that you plan your installation

exactly. Careful planning is a prerequisite for the successful installation of the system.

Note

SAP Note 2412645 provides information about planning the installation of SAP Policy Management

5.4.

The following sections give you an overview of the topics that must be considered in the planning phase. Use the

links to the notes and additional information to help you to plan the installation,

2.1.1 Required Documentation about Product Engine

2.1.1.1 Product Engine msg.PM

If you use the product engine msg.PM, you require the following documents for preparing and executing the

installation of product engine msg.PM and connecting it to FS-PM. Technical Customizing is also described.

• Documentation msg.ProductManager User Guide

(\msg.PM_3.4.13.1\Documents\english\PMDesigner\PDF\PMDesigner_34.pdf)

• Documentation msg.ProductManager Technical Overview

(\msg.PM_3.4.13.1\Documents\english\PMOverview\PDF\PMTechnicalOverview_34.pdf)

• Documentation msg.ProductManager Installation Guide

(\msg.PM_3.4.13.1\Documents\english\PMAdminstration\PDF\PMInstallGuide_34.pdf)

• Documentation msg.ProductManagerAdministration Guide

(\Caiman_34130.*\Documents\english\ msg.PM-Connection Administration Manual FS-PM.pdf)

• Documentation Product Management System msg.PM (TomatosX)

(\TomatosX_3.4.13.1\3_Documents\english\PDF\TOMATOSX_34.pdf)

• Documentation Remote Administration of TomatosX

(\TomatosX_3.4.13.1\3_Documents\english\PDF\TomatosX_RemoteCtrl_34.pdf)



Installation

Customer



Note

You can find the documentation for msg.PM under the following directory on your system DVD or CD:

msg.PM_3.4.13.1\Documents\

2.1.1.2 Product Engine FS-PRO

If you use the product engine SAP Product Lifecycle Management for Insurance (FS-PRO), you require the

following documents for preparing and executing the configuration of the FS-PRO product engine and linking it to

FS-PM. For more information, see the following documentation:

Title Path

SAP Product Lifecycle

Management for Insurance -

Installation Guide

SAP Product Lifecycle Management for Insurance → Installation and

Upgrade → Installation Guide

SAP Policy Management with

SAP Product Lifecycle

Management for Insurance -

Integration Guide

SAP Product Lifecycle Management for Insurance → Integration →

Integration Guide

2.1.2 Definition of Languages Used

SAP Policy Management 5.4 supports the following languages:

• Arabic - Saudi-Arabia

• Czech - Czech Republic

• German - Germany

• English - USA

• Spanish - Spain

• French - France

• Korean - South Korea

• Dutch - Netherlands

• Portuguese - Brazil

• Slovakian - Slovakia

• Turkish - Turkey

• Chinese traditional - Taiwan



16

Customer



4

Installation

Clarify which languages are to be used in the live implementation.

2.1.3 Clarification of Required Product Engine Version

Clarify which combination of SAP Policy Management and product engine version you want to install.

If you use msg.PM as the product engine, use the Note 718815 to clarify which combination you have to install. In

each case, ensure that you use the currently valid version of msg.PM and the Compile plug-in.

2.1.4 Clarification of Authorization Concept

Before installing SAP Policy Management, clarify how you want to assign authorizations for SAP Policy

Management 5.4. Create an authorization concept that provides information about the roles and authorization

concepts used.

For more information, see SAP Policy Management → Security → Security Guide → chapter Authorization.

2.2 Installation Activities

2.2.1 Installing SAP Policy Management 5.4

Perform the following steps:

1. Install SAP NetWeaver 7.50, SP06 (or a higher SP).

2. Install SAP ERP 6.0.

3. Install one of the following SAP enhancement packages for SAP ERP 6.0:



4. Install software component FSPM 5.4 in accordance with SAP Note 2412645.

The note contains the following installation information:

1. General

2. Overview

a) SAP Product Availability Matrix (PAM)

b) Download

c) Modifications

d) Retrofit

3. FSPM 540

a) Installation

b) Delta upgrade





Installation

Customer



c) Supplement upgrade

d) Support Package

Note the following concerning the installation steps mentioned above:

• You must install SAP Policy Management 5.4 and SAP ERP 6.0 on different SAP NetWeaver instances.

• In case you use two different physical systems, you must ensure that one of the following conditions apply to

the two different physical systems:

o Both physical systems are Unicode systems.

None of the physical systems is a Unicode system.

2.2.2 Installing the Product Engine

2.2.2.1 Installing the Product Engine msg.PM

2.2.2.1.1 Product Engine Designer

To develop products with msg.PM, you need the PM.Designer component. This lets you enter product data

using a graphical interface. For more information, see msg.ProductManager Installation Guide (see chapter 2.1.1.1)

2.2.2.1.2 Installing Product Engine Runtime

To enable you to use the definitions of the insurance products in your live business, without directly linking to the

development environment, you need a runtime component for the Product Engine.

For msg.PM, the runtime component is called PM.Runtime. The product definitions are provided for PM.Runtime

as compilates, which are created by the PM.Designer.

PM.Runtime not only delivers static product information (structure information) but also realizes the product

behavior defined in the business design. PM.Runtime performs calculations for the SAP Policy Management in-

force business management system, and executes business processes on a copy of the live data.

For more information about the installation, see the msg.ProductManagerAdministration Guide (see chapter

2.1.1.1).

2.2.2.1.3 Installing Caiman

Product data import transfers product-specific data from msg.PM product collections to SAP Policy

Management. This is achieved with CAIMAN. CAIMAN executes FS-PM-specific checks and, as long as no errors

occur, it imports the compilate with the product data.

18

Customer



4

Installation

For a thorough description of the installation, see the msg.ProductManagerAdministration Guide (see chapter

2.1.1.1 and within the guide see section 2.1 Caiman Installation).

2.2.2.2 Installing the Product Engine FS-PRO

You can find detailed information about the SAP Product Lifecycle Management for Insurance (FS-PRO)

installation in the corresponding Installation Guide and Integration Guide (see 2.1.1.2).


Configuration

Customer



3 Configuration

Purpose

This chapter describes the most important steps of the configuration process for the SAP Policy Management

after the installation.

3.1 SAP Notes

Notes about inclusion in the solution


2041665 Setting up the "Cash-Before-Cover" function

2149019 Set up dunning procedure for lapse

2071448 Setting up the "Substitution" function

Official SAP Notes about Add-Ons


337623 Customizing after installation or upgrade

3.2 Configuration Activities

3.2.1 Delivery of Customizing SAP Policy Management 5.4

Copy of Sample Customizing to Customer Clients

Installing SAP Policy Management 5.4 also imports sample Customizing in the SAP sample client 000. In most

cases, sample Customizing is copied to the customer clients, where specific changes can be made.

For more information about Customizing for FS-PM, see SAP Note 337623 (Customizing after installation or

upgrade).






20

Customer



4

Configuration

Manual Comparison of Sample Customizing

If changes and enhancements have already been made to customer clients, ensure that no customer

modifications or enhancements are overwritten when copying Customizing.

For example, if you want to copy sample Customizing for a Service Pack, you must first compare sample

Customizing for client 000 with Customizing for the customer client. You can do this using the Customizing

Cross-System Viewer.

To access the Customizing Cross-System Viewer, choose on the SAP Easy Access screen Tools → Customizing →

Customizing Cross-System Viewer.

3.2.2 Creating an Output Device

Start transaction SPAD and create a new output device.

Note

Create an output device LOCLWEB with the device type PDF1 if you use Adobe Forms.

3.2.3 Integration of SAP Components

3.2.3.1 Connecting to SAP Components

For each of the components listed below, you have to create a Remote Function Module (RFM) destination if they

are not located in the same physical system as SAP Policy Management. Subsequently, the name of the RFM

destination must be declared in SAP Policy Management.

To do so, make the following settings in Customizing for SAP Policy Management under Policy Management →

Integration → Process Primary Settings for Interfaces to External Systems:

Connection to Name of the logical

destination:

Additional Information

SAP Business Partner (BP) GP See 3.2.3.2

SAP Incentive and Commission

Management for Insurance (FS-

ICM)

CS See 3.2.3.3

SAP Collections and

Disbursements for Insurance

(FS-CD)

CD See 3.2.3.4

SAP Claims Management (FS-

CM)

CM


Configuration

Customer



Connection to Name of the logical

destination:


SAP Reinsurance Management

(FS-RI)

RI

Financial Accounting FI

Organization Management

(OM)

OA

OU

Two entries are required:

• If OM is not located in the same physical system

as SAP Policy Management, an RFC destination

must be created for this system. The name of

the logical destination is OA.

If OM is located in the same physical system as

SAP Policy Management, the destination can be

omitted, however the OA has to be specified.

Finally you will have to add a class to the logical

destination OA: Its name is

/PM0/CL_ABT_OM_HANDLER.

• A second destination, OU, is needed for handling

the association of organizational units to policy

elements. The RFC destination is not used, but

you must assign the class /PM0/CL_AB_INT_OM

to this destination.

Portfolio Assignment (PFO) PO

SAP Loans Management (FS-

CML)

CL For more Information, see SAP Policy Management

→ How-To Guides →Integration Guide for CML-

Based Policy Loans

Business Partner (Privileged

Access)

GV See 3.2.3.2

Object Management OM

3.2.3.2 Business Partner Integration

If the SAP component business partner (FS-BP) is not located in the same physical system as SAP Policy

Management, the search helps and business partner selection functions do not work correctly in FS-BP. The BAPI

BAPI_HELPVALUES_GET performs a data selection in the FS-BP system that corresponds to the selection of the

standard search help. However, this data selection ignores additional fields, such as the field for the date of birth.

Currently, a data selection in FS-BP using BAPIs cannot be executed satisfactorily because the existing BAPI

BUPA_SEARCH selects business partners by address data only. To ensure that the search helps take the relevant

fields into account (for example, the date of birth), you must create the relevant append search helps and hide the

search helps that are no longer required.

To add data other than address data to the data selection function for business partners, SAP has created

database views directly in the database tables of the FS-BP system. For this to work in FS-PM, a transport request


22

Customer



4

Configuration

on the basis of the object list /PM0/ABT_BP_STKL is required. You must import this transport request to the

remote system that contains the FS-BP component.

Note

If the component check is activated, the following message may be displayed in the status column in the

queue overview: Does not match component version.

See SAP Note 1742547 (Information about component version check in TMS) how to deactivate the

component check or how to ignore the result of the component check.

Then, call transaction SM30 in the remote system. Select the table BAPIF4T and define an authorization module

for the following values:

Object Type Verb Data element Function name

BUS1006 <customer module>

BUS1006 GETDETAIL <customer module>

You can use the function module BF_BAPI_F4_AUTHORITY as a template for your function module (<customer

module>). This function module provides the interface. Copy this function module. For more information, see the

relevant documentation. Note that you must grant the relevant authorization for the search help to work.

3.2.3.3 FS-ICM/PFO Integration

If SAP Incentive and Commission Management for Insurance (FS-ICM) is installed in a remote system, you must

copy the FS-ICM transfer structures to the FS-PM system. To do this, choose in Customizing for SAP Policy

Management Policy Management → Integration → Incentive and Commission Management FS-ICM → Copy

Transfer Structures of FS-ICM → Copy Transfer Structures of FS-ICM. The name of the commission application is

determined during the generation in FS-ICM.

For more information on the integration of FS-ICM, see Basic Settings for Connection to Commission

Management.

To use Portfolio Assignment (PFO), you have to activate this in FS-PM as well as in FS-ICM. For more information

on activating PFO, see SAP Policy Management -> Application Help -> SAP Library for SAP Policy Management ->

Integration -> Integration with SAP Incentive and Commission Management for Insurance FS-ICM -> Basic Settings

to Integrate Incentive and Commission Management.

The use of PFO by FS-PM is based on the objects delivered in the standard PFO system. However, an FS-PM-

specific enhancement of the attributes of the business assignment object (BAO object) is required. Add the

following attributes to the customer include CI_PFO_S_GZOCATT in portfolio assignment:

Component Component type

DIRECTRATE_VL CACSCOMMSHARE

INDIRECTRATE_VL CACSPRODSHARE


https://help.sap.com/viewer/DRAFT/2f97c46b09a9420c998853f4b0187777/5.4.0.0/en-US/4e8d658644220668e10000000a421937.html

https://help.sap.com/viewer/DRAFT/2f97c46b09a9420c998853f4b0187777/5.4.0.0/en-US/4e8d658644220668e10000000a421937.html



Configuration

Customer



Component Component type

COMMISROLE_CD CACSROLE

COMCONTGRP_ID CACS_CTRTBU_ID_GRP

OWNER_FG CACSFLGGROUPRESP

BSNESSPARTNER_ID CACS_GPART_INV

3.2.3.4 FS-CD Integration

In the remote system in which FS-CD is installed, call transaction SM30, select the table BAPIF4T, and define an

authorization module for the following values:

Object Type Verb Data element Function name

INSOBJECT_MD <customer module>

You can use the function module BF_BAPI_F4_AUTHORITY as a template for your function module (<customer

module>). This function module provides the interface. Copy this function module. For more information, see the

relevant documentation.

Note that you must grant the relevant authorization for the search help to work.

3.2.4 Defining Companies

Maintain the companies in the Customizing activity Policy Management → General Settings → Define Companies.

Note

As the Customizing is based on companies and a business partner is a precondition for setting up a

company, at least one single business partner is (technically) required in the FS-PM system. This is true

even if the business partner is stored in a remote system (for instance, the ERP system), as described in

the section Integration of SAP Components.

3.2.5 Maintaining Calendar

If you use the Customizing activity Define Stock Exchanges for maintaining the exchanges, you first have to define

the underlying exchange calendars.

You maintain the calendars in Customizing for SAP NetWeaver under General Settings → Maintain Calendar.

24

Customer



4

Configuration

3.2.6 Maintaining Number Range Intervals

The definition of number ranges defines the areas in which numbers are specified for certain business objects,

such as applications or policies.

Note

The defined number range intervals are not automatically transported, which means that they are not

copied when copying sample Customizing. You have to redefine the number range intervals in the

customer clients.

In SAP Policy Management, number range intervals must be defined for the number ranges mentioned in the

following tables. You can see the footnotes below each table.

You maintain the number ranges in Customizing for Policy Management under General Settings → Number

Ranges as follows:

Number Range Intervals for In-Force Business Management

Number

Range

Meaning Required Intervals Note

/PM0/ABN04 Change options 1

/PM0/ABN08 Policy numbers

(internal)

1 Must not overlap with the contract numbers.

Must be centrally registered in a number range

list to avoid conflicts with the integrated

systems.1

/PM0/ABN08 Policy numbers

(external)

2 Must not overlap with the contract numbers.



systems.1

/PM0/ABN09 Application numbers

(internal)

1

/PM0/ABN09 Application numbers

(external)

2

/PM0/ABN16 Contract numbers 1 Must not overlap with the policy numbers.



systems.1

/PM0/ABN16 2 Must not overlap with the policy numbers.



systems.1

/PM0/ABN26 Background

processing

01


Configuration

Customer



Number

Range


/PM0/ABN28 Folders for fast entry

screen

1 The interval number is fixed. The underscore is

a space

/PM0/ABN29 Fast entry screen

number


a space.

/PM0/ABN35 Deposit number 1 Must be centrally registered in a number range


systems.1

/PM0/ABN41 Provisional contract

numbers

1 Must be centrally registered in a number range


systems.1

/PM0/ABN42 Policy loans 1 Must be centrally registered in a number range


systems.1

/PM0/ABN43 Migration runs 1

/PM0/ABN45 Dependency

numbers

1

/PM0/ABN46 Coverage numbers 01 To avoid overlap, the number range interval

must be maintained in a central number range

list.1

Subcoverage numbers and coverage numbers

must not overlap. Therefore, you must choose

the interval in such a way as to avoid overlap.

The number range intervals must be different

for each system and client if the data is to run

in the same operational system client. Data

from test systems and production systems is

not likely to run in the same operational

system client. If this possibility is ruled out,

you may use the same number range interval

for each system and client in the FS-PM

system.

You should maintain this number range

interval even if no RI system is connected.

/PM0/ABN47 Subcoverage

numbers

01 To avoid overlap, the number range interval


list.1

Subcoverage numbers and coverage numbers

must not overlap. Therefore, you must choose

the interval in such a way as to avoid overlap.



26

Customer



4

Configuration

Number

Range








system.



/PM0/ABN48 Accumulation IDs 01 To avoid overlap, the number range interval


list.1









system.



1 Numbers from this number range can affect the data of third-party systems. You must ensure that, for instance,

after a productive system is copied the copied FS-PM system does not affect the production data of a third-party

system.

Number Range Intervals for Business Intelligence (BI)

Number

Range


/PM0/ABN49 Run numbers of BI

transformation run -

Policy Management

01



Object Management

01



Master Policy

01


transformation run –

Coinsurance

01


Configuration

Customer



Number Range Intervals for Integration

Number

Range


/PM0/ABN38 Account creation in

FS-CD

01 The numbers are used to create contract

accounts in FS-CD. Ensure no overlaps in

definition for systems that lead to the same

FS-CD system.1

/PM0/ABN23 Risk Group Numbers 01

1 Numbers from this number range can affect the data of third-party systems. You have to ensure that, for

instance, after a productive system is copied the copied FS-PM system does not affect the production data of a

third-party system.

Number Range Intervals for Master Policy

Number

Range


/PM0/ABN15 Master policy

numbers (internal)

01

/PM0/ABN15 Master policy

numbers (external)

02

Number Range Intervals for Object Management

Number

Range


/PM0/ABN21 Object management 1 One number range number for each object

category /PM0/ABN21 2

/PM0/ABN21 3

/PM0/ABN21 4

/PM0/ABN21 5

/PM0/ABN21 6

/PM0/ABN21 7

/PM0/ABN21 8

Number Range Intervals for Coinsurance

Number

Range


/PM0/ABN44 Distribution plans 1

/PM0/ABN44 2

28

Customer



4

Configuration

Number Range Intervals for Fund Management

Number

Range


/PM0/ABN10 Fund numbers 1

/PM0/ABN19 Fund ranges 1

/PM0/ABN40 Globally forecasted

and globally closed

fund orders

01

/PM0/ABN39 Forecasted and

closed fund orders

01

Number Range Intervals for Third-Party Collections Management

Number

Range


/PM0/ABN37 Employers 1 Must be centrally registered in a number range


systems.1



third-party system.

Number Range Intervals for Sample Application Management

Number

Range


/PM0/ABN30 Sample template

number

1

/PM0/ABN27 Folders of sample

applications


a space.

Number Range Intervals for Correspondence Management

Number

Range


/PM0/ABN18 Document numbers 1

Number Range Intervals for Accounting Component

Number

Range


/PM0/ABN24 Business case

number

01

/PM0/ABN31 Cash flow

documents

01


Configuration

Customer



Number

Range


/PM0/ABN32 Non cash flow

documents

01

/PM0/ABN33 Reinsurance

documents

01

/PM0/ABN34 Totals documents 01 Must be centrally registered in a number range


systems.1

/PM0/ABN34 Totals documents

(for simulation)

02



third-party system.

3.2.7 Configuring the Product Engine

Each policy is based on a product that is defined in a product engine. For this reason, SAP Policy Management is

always connected to a single product engine, which usually is one of the following:

• msg.PM

• SAP Product Lifecycle Management for Insurance (FS-PRO)

Note

Only one product engine can be connected to FS-PM. The integration of multiple FS-PRO systems, or

multiple msg.PM systems, with an FS-PM system is not possible either.

3.2.7.1 Configuring the msg.pm Environment

Configuration TomatosX

TomatosX is the runtime component of the msg.PM environment. Communication between SAP Policy

Management and TomatosX is handled through an RFC connection. Options and parameters of the connection

and functionality need to be specified within a configuration file, which is read by TOMATOSX upon start. The

configuration file must be located in the same directory as the TOMATOSX shell command is invoked from.

For more information about the configuration, see chapter 2.1.1.1 (msg.ProductManager Administration Guide,

section 2.2 TomatosX Configuration.

30

Customer



4

Configuration

Configuration of Caiman

Product data import transfers product-specific data from msg.PM product collections to SAP Policy

Management. This is achieved with CAIMAN. CAIMAN executes FS-PM-specific checks and, as long as no errors

occur, it imports the compilate with the product data.

An initial import into SAP Policy Management has to be made. Without this initial import, no calculation is possible

because the /PM0/4_* tables are empty in a new SAP Policy Management system. You can use the sample

content provided by SAP for test purposes.

For a complete description of the configuration and the product data import, see chapter 2.1.1.1

(msg.ProductManager Administration Guide, section 2.1 Caiman Configuration and section 3.2 Product Data

Import.

3.2.7.2 Configuring the FS-PRO Environment

You can find detailed information about configuring the FS-PRO environment SAP Product Lifecycle Management

for Insurance → Integration → Integration Guide for SAP Product and Policy Lifecycle Management.

3.2.8 Configuring SAP Business Workflow

• Maintain the standard settings for SAP Business Workflow in the Customizing for SAP NetWeaver under SAP

NetWeaver → Application Server → Business Management → SAP Business Workflow → Maintain Standard

Settings.

Note

In this Customizing activity, the verification workflow must be started twice.

Starting the verification workflows creates two work items in the SAP Business Workplace with the title

First Step in Workflow Verification. These work items must be performed.

• Identify the tasks as General Tasks: In the processing assignment, the FS-PM-specific tasks classified as

General Tasks must be maintained in the SAP Business Workflow. You do this for the following tasks on the

SAP Easy Access screen under Tools → Business Workflow → Development → Definition Tools → Tasks/Task

Groups → Change (transaction PFTC_CHG):

o 16107914: DOWNPAYMENT accepted application

o 16107915: DOWNPAYMENT refused application

o 16107916: Resumption of processing for an application

o 16107917: Resubmission of an application

o 16107919: Forwarding an application

o 16107921: Synchronizing an insured object

o 16107922: IBC: for checking

o 16107923: Reassessing a policy

o 16107925: Unrolling a business transaction




Configuration

Customer



o 16107926: Accepting or rejecting

o 16107927: Post-processing after rejection

o 16107928: FS-PM: Forwarded application (postal code check)

o 16107929: Forwarded application (amount check)

o 16107930: Displaying a policy

o 16107931: Processing completed

o 16107932: Probable maximum loss

o 16107933: Renewal

o 16107936: Rejection of template

o 16107938: Workflow for dual control

o 16107939: Dual control: Application deferred

• Execute type linkages. You can find the transaction on the SAP Easy Access screen under Tools → Business

Workflow → Development → Utilities → Events → Type Linkages (transaction SWETYPV).

Make the following settings:

o Set Linkage Activated

o Behavior Upon Error Feedback: Do not change linkage for the following events:

o /PM0/ABAPP - CREATE_FORWARD

o /PM0/ABPLC - CREATE_REMIND

o /PM0/ABAPP - CREATE_RESUME

o /PM0/ABOIO - CHANGED

o /PM0/ABPSJ - ON_CHANGE_INSOBJ

o /PM0/ABAPP - CREATE_DOWNPAYMENT

o /PM0/ABAPP - CREATE_APPROVE

o /PM0/ABAPP - CREATE_FORWARD_CHK_AMOUNTS

o /PM0/ABAPP - CREATE_FORWARD_CHK_ZIP

o /PM0/ABIBC - FOR_CHECKING

o /PM0/ABPLC - CREATE_DISPLAY

o /PM0/ABPLC - CREATE_UNROLL

o /PM0/ABPLC - CREATE_PML

o /PM0/ABPLC - CREATE_REASSESS

o /PM0/ABAPP - CREATE_DCRELEASE

o /PM0/ABAPP - CREATE_DCRETURN

o /PM0/ABAPP - CREATE_RENEWAL

o /PM0/ABAPP - CREATE_RESUME_BG

o /PM0/ABAPP - CREATE_POSITIONING_BG

o /PM0/ABPLC - CREATE_POSITIONING_BG_FAIL

• Execute instance coupling: Instance coupling must be activated for the object category event combinations

listed below. You must set the option for the behavior for error messages to Do not change coupling. You do

this on the SAP Easy Access screen under Tools → Business Workflow → Development → Utilities → Events →

Instance Linkages.

32

Customer



4

Configuration

o /PM0/ABPLC - END_REMIND

o /PM0/ABAPP - END_RESMUME

o /PM0/ABAPP - END_APPROVE

o /PM0/ABIBC - END_IBC_FOR_CHECKING

o /PM0/ABPLC - END_REASSESS

o /PM0/ABAPP - END_FORWARD

o /PM0/ABAPP - END_DCRELEASE

o /PM0/ABAPP - END_DCRETURN

o /PM0/ABAPP - END_RENEWAL

o /PM0/ABAPP - END_RESUME_BG

o /PM0/ABAPP - END_POSITIONING_BG

o /PM0/ABPLC - END_POSITIONING_BG_FAIL

Note

The user who sets up the workflow must have the profile SAP_ALL.

For more information, search for Configuring Workflow Customizing in the documentation of SAP

NetWeaver at SAP NetWeaver 7.5.

3.2.9 Configuring Policy Management, Group Insurance Features

In order to use Policy Management, Group Insurance Features in SAP Policy Management, you must perform the

following steps:

• Customizing

Activate Policy Management, Group Insurance Features in Customizing for Policy Management for Group

Insurance under Switching Group Insurance.

• Policy Based Technology (PBT)

Insert the customer variant for Policy Management, Group Insurance Features into the Policy Based

Technology (PBT) by performing the following steps:

1. Choose /PM0/3fw_start.

2. Choose the application 00001 for FS-PM.

3. Insert the customer variant PMG to the SAP List Viewer by entering a previous variant, for example PM0.

4. Adapt the additional customer variants, in order to display the new entry in the correct sequence.

https://uacp2.hana.ondemand.com/viewer/p/SAP_NETWEAVER_750


Configuration

Customer



For more information , see SAP Policy Management -> How-To Guides -> Configuration Guide for Policy

Management, Group Insurance Features.

3.2.10 User Group

If a user wants to release a new business in FS-PM, the user must assigned to user group SB (via transaction

SU01).

3.2.11 Optional Installation of Enterprise Search

To install Enterprise Search, see SAP Note 1468939.

3.2.12 Setting Up Cash-Before-Cover (Optional)

To set up Cash-Before-Cover, see SAP Note 2041665

3.2.13 Settings for Performance

We strongly recommend to consider the performance settings, which are mentioned in the performance guide

(see SAP Policy Management → How-to Guides → Performance Guide).

The performance guide presents tools, guides and best practices on how Policy Management (FS-PM) can be

used in a performant way.

3.2.14 First Check

✓ Activity

Are all database tables empty?

Have background jobs been started?

Are all Customizing activities complete?

Start transaction /PM0/ABC_FSPM. This is the central access for processing with SAP Policy

Management.

Select New Business process.

Enter a new business, including the release.

https://help.sap.com/viewer/p/SAP_POLICY_MANAGEMENT




34

Customer



4

Configuration

✓ Activity

For more information about the procedure, see SAP Policy Management -> Application Help -> SAP

Library for SAP Policy Management -> In-Force Business Management -> Business Processes ->

New Business Business Process.

Ensure that test entries do not negatively affect live use, by:

• Entering a complete live case

• Emptying the database tables completely

• Reversing the entered transaction

Ensure that the changes and enhancements you made are saved in the system.




Customer



4 Additional Information

4.1 Deinstalling SAP Policy Management 5.4

It is not possible to deinstall SAP Policy Management 5.4.

4.2 Customizing

Note that sample Customizing for SAP Policy Management must either be copied completely or it must be filled

with the appropriate customer-specific data. Otherwise the entire system will not work.

SAP Policy Management does not run without the runtime component for the product engine.

4.3 Post-Installation Steps

You can find additional information about the steps to be executed after the installation in the SAP Note 2428681

(Release Information Note (RIN) for FSPM 540).

4.4 Interrupted Installation

Notes for restarting after interruption of installation:

Installation Phase Interruption Procedure

FS-PM 5.4 installation Restarting the installation procedure is controlled by the SAINT transaction. The

transaction must be restarted, and the installation process continues.

4.5 Support

SAP Policy Management Support

Corrections are provided online for SAP Policy Management 5.4, according to the Support Packages for the SAP

core components. Similar to these, the SAP Policy Management 5.4 Support Packages are imported with the

patch engine SPAM.


36

Customer



4


The SAP Policy Management 5.4 Support Packages correct errors in SAP Policy Management programs. For

more information about working with Support Packages, see SAP Note 160168.

For an overview of the available SAP Policy Management 5.4 Support Packages, see SAP Note 1729533, or SAP

Service Marketplace at https://support.sap.com/patches.

Information on the availability of Support Packages is available on SAP Service Marketplace at

https://support.sap.com/maintenance-schedule.

Support Packages are available for download on SAP Service Marketplace at https://support.sap.com/swdc.

The Support Package Manager (formerly called SAP Patch Manager, transaction SPAM) helps you apply Support

Packages to your SAP system.

The SAP Note Assistant lets you load, implement, and organize individual SAP Notes efficiently. It also recognizes

dependencies between SAP Notes, Support Packages, and modifications. You can find more information on SAP

Service Marketplace at http://service.sap.com/noteassistant.

Caution

After installing a SAP Policy Management 5.4 Support Package, you must always perform a Customizing

comparison for the SAP Policy Management tables using transaction SCU0.



https://support.sap.com/patches

https://support.sap.com/maintenance-schedule


http://service.sap.com/noteassistant



Customer



Further Information

For more information about support for FS-PM, see SAP Note 717724.

Caution

Upgrades for new release are not sent out automatically, but only on request.

Support for Partner Products

While running an SAP product, you may encounter errors that are not caused by the SAP product, but by the

database, operating system, hardware, or another application product instead.

Note the following when requesting support for such problems:

• Case 1: The product was purchased through SAP.

This usually involves the databases or application products (for example, from Requisite). In this case, SAP is

your contact for support of these products and we assume responsibility for finding a solution with the

product vendor within the scope of the SAP Maintenance Agreement.

• Case 2: The product was not purchased through SAP.

This applies to all other products (such as all operating systems and hardware including the databases IBM

DB2/390, IBM DB2/400, MS SQL, non-SAP application products and some more database administration

tools/features). This applies also to Product Engine msg.PM of msg systems ag.

The contact for support for these products is the product vendor. If the error was originally reported to SAP,

SAP Support will forward the message concerned to the respective partner’s support organization. SAP has

agreements with all partners that clearly define the procedures for forwarding these customer support

messages.

Note that the partner will provide support only if you have a valid support contract with the product vendor for

the product in question. Note also that the service times (weekends and nights, for example) are an important

element of this contract.

Support for DB2 UDB (formerly DB2 CS) is as indicated in Case 1. Check if your support contracts correspond to

the recommendations of our partners or the above-mentioned conditions or both and, if necessary, contact the

partner directly or a service provider for the partner product.

Partner Software Included in this Shipment

The SAP Policy Management shipment from SAP SE includes the third-party product msg.PM. You can order the

required license keys directly from msg systems ag.

Note

Support mailbox for Product Engine msg.PM: [email protected].


mailto:[email protected]

www.sap.com/contactsap

Material Number

© 2017 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 AG. The information contained herein

may be changed without prior notice.

Some software products marketed by SAP

AG and its distributors contain proprietary

software components of other software

vendors.

National product specifications may vary.

These materials are provided by SAP AG and

its affiliated companies (“SAP Group”) for

informational purposes only, without

representation or warranty of any kind, and

SAP Group shall not be liable for errors or

omissions with respect to the materials. The

only warranties for SAP Group products and

services are those that are set forth in the

express warranty statements accompanying

such products and services, if any. Nothing

herein should be construed as constituting

an additional warranty.

SAP and other SAP products and services

mentioned herein as well as their respective

logos are trademarks or registered

trademarks of SAP AG in Germany and other

countries. Please see

www.sap.com/corporate-

en/legal/copyright/index.epx#trademark for

additional trademark information and

notices.

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

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

SAP Policy Management 5 · PDF fileThese include report names, program ... SAP Policy...

Documents

Transcript of SAP Policy Management 5 · PDF fileThese include report names, program ... SAP Policy...