Important Operational Systems for SAP Policy … Management Guide Disclaimer April 2017 5 1...

Solution Management Guide

Important Operational Systems for

SAP Policy Management

SAP Policy Management (FS-PM)

Version 1.0 April 2017

Copyright

© 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 SE. The information

contained herein may be changed without prior notice.

Some software products marketed by SAP SE and its

distributors contain proprietary software components of

other software vendors.

National product specifications may vary.

These materials are provided by SAP SE 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 SE 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

Symbols

Symbol Meaning

Caution

Example

Note

Recommendation

Syntax

Solution Management Guide

April 2017 4

Table of Contents

1 DISCLAIMER .......................................................................................................................................... 5

2 PREFACE ................................................................................................................................................. 6

3 OVERVIEW OF OPERATIONAL SYSTEMS..................................................................................... 7

3.1 MSG.PRODUCTMANAGER (MSG.PM) / SAP PRODUCT LIFECYCLE MANAGEMENT FOR INSURANCE

(FS-PRO) ....................................................................................................................................................... 8 3.2 SAP REINSURANCE MANAGEMENT (FS-RI) ....................................................................................... 8 3.3 SAP INCENTIVE AND COMMISSION MANAGEMENT (FS-ICM) ............................................................ 9

3.3.1 Commission (previously FS-CM) ............................................................................................... 9 3.3.2 Portfolio Assignment (FPO) ....................................................................................................... 9

3.4 SAP COLLECTIONS AND DISBURSEMENTS (FS-CD)............................................................................ 9 3.5 SAP ERP GENERAL LEDGER (FI-GL) INTERFACE ............................................................................ 11 3.6 SAP CLAIMS MANAGEMENT (FS-CM) ............................................................................................. 11 3.7 SAP BUSINESS PARTNER .................................................................................................................. 11 3.8 INFORMATION LIFECYCLE MANAGEMENT (ILM) .............................................................................. 11

4 CONCEPTS / INTERACTION / BASIC PRINCIPLES .................................................................... 12

4.1 FS-PM <-> FS-ICM .......................................................................................................................... 12 4.1.1 FS-ICM: ICM Master Data ...................................................................................................... 12 4.1.2 FS-ICM: Processing a Commission Case ................................................................................ 13 4.1.3 FS-PM: Control Settings for Generating a Commission Case ................................................. 14 4.1.4 FS-ICM Commission Case Sequence and Consequences for FS-PM ...................................... 14 4.1.5 FS PM. Integration Customizing for ICM ................................................................................ 17 4.1.6 Packages and Central Classes for the ICM Interface .............................................................. 20

4.2 FS-PM <-> PFO................................................................................................................................ 22 4.2.1 PFO for Commission Participants ........................................................................................... 22 4.2.2 PFO for Organizational Units.................................................................................................. 25 4.2.3 FS-PM: Integration Customizing for PFO ............................................................................... 25 4.2.4 Packages and Central Classes for the PFO Interface .............................................................. 26

4.3 FS-PM <-> FS-CD (COLLECTIONS/DISBURSEMENTS) ...................................................................... 30 4.3.1 FS-CD: Master Data ................................................................................................................ 30 4.3.2 FS-CD: Insurance Object, (Contract) Account, Cash Flows and Information Container ....... 33 4.3.3 FS-PM: Controlling the Generation of Insurance Objects and Transaction Data .................. 40 4.3.4 FS-PM: Integration Customizing for FS-CD ........................................................................... 43 4.3.5 FS-PM: Important Packages/Classes/BAdIs ............................................................................ 45

4.4 FI INTERFACE .................................................................................................................................... 49 4.4.1 Customizing .............................................................................................................................. 49 4.4.2 FS-PM: Important Packages/Classes/BAdIs ............................................................................ 49 4.4.3 Class Diagram / Flow Chart .................................................................................................... 52

4.5 FS-PM <-> FS-CM (CLAIMS MANAGEMENT)................................................................................... 54 4.5.1 FS-CM: CM Master Data ......................................................................................................... 56 4.5.2 FS-CM: Claims and Claim Processing .................................................................................... 61 4.5.3 FS-PM: Generating a Claim .................................................................................................... 63 4.5.4 FS-PM: Integration Customizing for Claims ........................................................................... 64 4.5.5 FS-PM: Package and Central Modules for Claims Interface .................................................. 67

4.6 FS-PM<->FS-RI (REINSURANCE) .................................................................................................... 79 4.6.1 FS-RI: Master Data / Accumulations ....................................................................................... 79 4.6.2 FS-PM: Accumulation Formation ........................................................................................... 81 4.6.3 FS-PM: Integration Customizing ............................................................................................. 86 4.6.4 FS-PM: Important Packages / Classes / BAdIs ........................................................................ 89

5 SUMMARY ............................................................................................................................................ 94

Solution Management Guide Disclaimer

April 2017 5

1 Disclaimer This guide is not part of SAP product documentation. By using this guide, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Solution Management Guide Preface

April 2017 6

2 Preface This concept guide provides additional information to the existing SAP Policy Management documentation. A knowledge of the SAP Policy Management documentation is a prerequisite for understanding this documentation. The aim of this guide is to provide further comprehensive object and process knowledge. It also aims to pass on best practices from previous SAP internal implementation projects to accelerate customer implementation projects.

This guide complements the other guides for SAP Policy Management. A basic understanding of the structure of SAP Policy Management, the way it works and its results is required.

This document focusses on connecting specific SAP operational systems to SAP Policy Management.

This document helps to answer questions such as “How do I post documents to Collections and Disbursements (FS-CD), and where can I find that?”. It also describes what you can, and must, enhance yourself.

Related FS-PM Guides:

Guide Link Description

Enhancement Guide

https://uacp2.hana.ondemand.com/doc/d5057c59a919495590659cc35e2cde2e/HowTo/en-US/SAP_FS-PM_53__Enhancement_GuideE.PDF

Description of enhancement options for existing models.

Release

https://uacp2.hana.ondemand.com/doc/85321da90f154398b09b0f8e8b5cd0fe/HowTo/en-US/SAP_FS-PM_Concepts_Release.pdf

In the release, data is supplied to the operational systems, for example.









Solution Management Guide Overview of Operational Systems

April 2017 7

3 Overview of Operational Systems

Figure 1: The guide contains information about communication with the core insurance applications and the components outlined in orange.

SAP Policy Management (FS-PM) serves as the starting point, and contains the contract-relevant information.

The insurance contract is the central object that is also used for communication between the systems. Other systems do not necessarily need to know the concept of a policy. Where possible, use the processes in FS-PM based on contract. Use cross-contract processing (keyword: policy processing indicator) only if there is no alternative.

This document starts with a short description of the basic components and which key information is exchanged here.


April 2017 8

3.1 msg.ProductManager (msg.PM) / SAP Product Lifecycle Management for Insurance (FS-PRO)

msg.PM or SAP Product Lifecycle Management for Insurance (FS-PRO) is part of the core applications for insurance.

Product Definition

In these systems, you can define the products that are used as the basis for creating templates in FS-PM (see the In-Force Business Configurator Guide).

For example, if you are using msg.PM, you can extract or convert the data from msg.PM to FS-PM database tables by means of a PSV import and a downstream In-Force Business Configurator import (IFBC import).

FS-PM does not access the product engine system to determine hierarchies, characteristics and values when it creates or changes in-force business. Instead it uses SAP buffer mechanisms (shared memory) to enable high-performance access to product knowledge that was prepared by preceding import processes. For more information about this interface, see the In-Force Business Configurator Guide.

Financial Mathematics Calculations

At runtime, the system accesses the product engine for insurance mathematics calculation purposes.

3.2 SAP Reinsurance Management (FS-RI)

FS-RI is a core application for insurance and is available as an add-on to SAP ERP.

FS-PM is connected to FS-RI by the P2R interface.

The FS-RI Basic System and FS-RI Risk Manager Non-Life are connected via this interface.

The FS-RI Basic System is used for the following:

Management of reinsurance treaties of all known treaty types for assumed and ceded

reinsured business.

Management of losses

Management of reinsurance programs

Accounting for reinsurance-relevant items

Risk Manager (RM) is an optional component of FS-RI, and adds the functions required for accumulation management and accounting to the Basic System.

FS-PM provides aggregated liability totals (accumulations) and premium information to FS-RI. As the primary insurance system, FS-PM contains the following functions for the connection to the reinsurance system FS-RI:

Accumulation Determination: When a business process is released, FS-PM looks for similar insured objects that create an accumulation. The system cumulates the object liability totals for these insured objects based on defined cumulation rules.

o When the policy is released in FS-PM, the reinsurance coverage is checked in FS-RI.

o A probable maximum loss (PML) can also be entered to define the object liability total.

Finally, the determined accumulations are transferred to FS-RI.


April 2017 9

In addition, there is a reinsurance query that displays information about the individual accumulations in various business processes.

3.3 SAP Incentive and Commission Management (FS-ICM)

FS-ICM is a core application for insurance. It is an incentives and commissions solution from SAP that is used to calculate variable remuneration.

In addition to the actual incentive and commission calculation, it also includes a portfolio assignment option to assign portfolios to the insurance sales units and to commission beneficiaries and sales employees.

SAP Policy Management generally creates commission cases that are relevant for FS-ICM. SAP Policy Management reads information from FS-ICM and the portfolio assignment (PFO). However, FS-ICM cannot access and make modifications to SAP Policy Management.

3.3.1 Commission (previously FS-CM)

Based on Customizing settings in FS-PM, commission cases are sent to ICM from FS-PM on the basis of object creations or object changes. The commission contract defines the relationship between the commission contract partner and the insurance company. Based on the data it receives, the commission case determines the amounts to be transferred:

Which participants (directly or indirectly) receive one or more commission contributions

Which commission amounts are to be paid

For which time frame the commission is paid

When the relevant amounts are paid

The commission case includes information about the participants, the required activities, and commission-relevant objects.

If possible, use “contract-based” commission case creation.

3.3.2 Portfolio Assignment (FPO)

Portfolio assignment can be considered a part of FS-ICM but it is explicitly triggered and can therefore also be regarded as a separate solution. In portfolio assignment, you manage the assignment of commission recipients to the relevant contracts (or policies). For example, if one commission recipient is replaced by another one, you can start separate processes in PFO that change the commission recipient without the need to adjust all the affected insurance portfolios.

There are two main scenarios in portfolio assignment that are relevant for FS-PM:

Portfolio assignment for commission

Portfolio assignment for organizational units

3.4 SAP Collections and Disbursements (FS-CD)

FS-CD is one of the core applications for insurance. It is used to process all collection and disbursement processes for policyholders, agencies and related third parties.

FS-CD can be triggered by FS-PM but also by the claims management system (FS-CM) or SAP Incentive and Commission Management (FS-ICM).


April 2017 10

FS-CD processes the payment transactions, monitors the settlement of open items, monitors the dunning process, and manages the postings and the display of posting data for premiums to be received.

A distinction is made in FS-CD between master data and transaction data. Before transaction data can be posted, the relevant master data must be available. A master data example is an account that corresponds to an insurance relationship. Cash flow transactions belong to transaction data, for example.

To access FS-CD correctly, FS-PM must generate both master data and transaction data based on the data that was created in the accounting component.

FS-CD can also provide SAP Policy Management with data using info containers.


April 2017 11

3.5 SAP ERP General Ledger (FI-GL) Interface

FI-GL is the general ledger of SAP ERP Financial Accounting (FI).

The main task of general ledger accounting is the overall representation of financial accounting and of the accounts. The recording and collecting of all business transactions (primary postings, settlements from internal accounting) in an integrated business software system guarantees complete and aligned account management at all times.

For this reason SAP Policy Management transfers all non cash flow documents to SAP ERP General Ledger.

3.6 SAP Claims Management (FS-CM)

SAP Claims Management is one of the core applications for insurance. The claims management component provides efficient and transparent processing of claims and claim bundles.

Claims Management is used to settle claims related to P&C, liability and personal accident insurance. To do so, it requires the contract data from Policy Management.

In cases of life insurance, Claims Management is used to pay out a capital-forming life insurance policy, for example.

3.7 SAP Business Partner

FS PM uses SAP Business Partner. The business partner is used to store information, such as address or account details. The business partner data is not mirrored in FS PM.

Performance: If you make your own customer enhancements, make sure that you consider the effects on system performance when reading data from the business partner, particularly when using background processes. Only read the data that is necessary. Measure the performance of these modules.

Note that it is very unlikely that the business partner is in the system in which FS-PM is operating. This means that you will not find business partner information in FS-PM.

Business partner data is subject to data protection rules. Note the security guidelines for FS-PM and the guidelines for the simplified archiving and deletion of personal data as of release SAP Policy Management 5.2. See also the information about the ILM solution in the next section.

This document does not contain any further information about this operational system.

3.8 Information Lifecycle Management (ILM)

This SAP solution is used for the simplified archiving and deletion of personal data.

SAP systems register with ILM and provide modules that ILM can call to query whether special data can be archived or deleted, or is still being actively used by the customer. If the business relationship between the institution and the customer has been dormant for a specific period of time, which can be set by the institution, data can be deleted from the archive automatically. See also the SAP documentation for ILM and the simplified archiving and deletion of personal data.

This document does not contain any further information about this operational system.

Solution Management Guide Concepts / Interaction / Basic Principles

April 2017 12

4 Concepts / Interaction / Basic Principles It is important to understand how the different systems process their data and how the systems communicate with each other, especially if you are developing your own interfaces.

If you want to use your own modules to write data to your own operational systems make sure that you execute this asynchronously (SAP uses the qRFC model for this purpose). This is for both system performance and data integrity reasons. In this way, data inconsistencies can be prevented, for example if one operational system has posted data but another operational system was not able to do so.

4.1 FS-PM <-> FS-ICM

4.1.1 FS-ICM: ICM Master Data

Before new business can be concluded in SAP Policy Management, the required master data (commission contract) must exist in FS-ICM.

In FS-ICM, the commission contract links the sales organization with the business partner that sold the policy products/contracts, for example.

When you create new business in FS-PM you must specify this commission contract. There may be distribution plans (rules) in place for the commission contract that determine how commissions are to be distributed for each insurance contract (based in the product or on the company, for example).


April 2017 13

4.1.2 FS-ICM: Processing a Commission Case

This guide does not explain how FS-ICM works in detail. (See also the SAP Library documentation for FS-ICM). This guide covers a basic processing option:

Commission cases can be created for a commission contract.

The commission cases in the ICM system have a business object version that must be assigned strictly in ascending order for consecutive commission cases (both in terms of date and in terms of sequential number).

The possible processing phases of a commission case are as follows:

If the sequence of the commission cases is interrupted when the commission cases are imported the system cannot process the commission case and sends it to a staging area for processing later.

If the commission case can be processed, the system determines the FS-ICM master data based on the commission case characteristics and finds the distribution plan that is to be applied. The system uses the distribution plan to determine the share of the commission to be distributed per person (also sales and distribution organization) and credit the amount to the relevant account. It is possible to start a separate process at a specified time to clear these accounts and provide data to FS-CD.

FS PM sends the sequential number of the journal to FS-ICM. This is used as the business object version in FS-ICM.


April 2017 14

4.1.3 FS-PM: Control Settings for Generating a Commission Case

The Customizing settings for the journal determine whether a commission case is created in FS-PM and transferred to FS-ICM. For more information, see Customizing for Policy Management under In-Force Business Management Basis Journal Define Journal Entries.

Here you can use the indicator in the journal entry to determine whether processing in FS-ICM is relevant.

For more information, see the documentation for the Customizing activity Define Journal Entries. The information for the following settings is particularly relevant:

Commission-Relevant Processing

Commission Agent Role

You can find these in Customizing for Policy Management under In-Force Business Management Basis Journal Define Journal Entries.

4.1.4 FS-ICM Commission Case Sequence and Consequences for FS-PM

Reminder

The commission cases in FS-ICM are in a sequence that must be assigned strictly in ascending order for consecutive commission cases. This is controlled using the business object version in FS-ICM.

In SAP Policy Management, the sequential number of the journal is assigned in ascending order during processing. The journal number is only assigned sequentially for each contract.

FS-PM sends the sequential number to FS-CM as a business object version.

In FS-PM you can differentiate between contract-based processing and policy processing. See Customizing for Policy Management under Integration Incentive and Commission Management FS-ICM Assign FS-ICM Business Object to FS-PM Product Module Group Sales Product.

When you start processing in Policy Management, the system determines the policy version for the exact date, so that the processing can begin based on this version. The inclusion of contracts in the future is not known at this point in time.

In general, both contract inclusion and changes to a premium are commission-relevant.


April 2017 15

Case 1 Contract-based processing

You have not set the Pol. Comm indicator (Commission Case Creation at Policy Level) for your product module group in Customizing for Policy Management under Integration Incentive and Commission Management FS-ICM Assign FS-ICM Business Object to FS-PM Product Module Group Sales Product. This means that the processing for this product module group is contract-based.

If changes are made retroactively in the contract-based creation of commission cases, the system resets commission cases that have already been transferred and imports them again. Since the journal numbers in FS-PM are assigned sequentially, the sequence numbers in FS-ICM are also assigned sequentially.


April 2017 16

Case 2 Policy-Based Processing

You have set the Pol. Comm indicator (Commission Case Creation at Policy Level) for your product module group in Customizing for Policy Management under Integration Incentive and Commission Management FS ICM Assign FS-ICM Business Object to FS-PM Product Module Group Sales Product. This means that the processing for this product module group is policy-based and so for all contracts.

Short description of diagram:

A policy has two contracts, numbered 4711 and 4712. The policy and contract 4711 were created on January 1. A commission case has been created for the new business in FS-ICM with business object version 2. Contract 4712 was added to the policy on June 1 and the premium was changed on July 1. There are commission cases with the business object version 8 and 12.

If a change is made retroactively for March 1, which is relevant for FS-ICM, the update process is halted as soon as a contract must be included (or a universal change is made). The future commission cases already transferred to FS-ICM are determined and sent to FS-ICM as commission cases that are to be reset. A new commission case is created for the change.

A subsequent update (see next diagram) can include contract 4712 again and then create the subsequent change together with the new commission cases. Any other procedure would violate the principle of sequential processing in FS-ICM because the sequential numbers in the chain would not longer be sorted in ascending order.


April 2017 17

4.1.5 FS PM. Integration Customizing for ICM

You will find the settings for FS-ICM in Customizing for Policy Management under Integration. The central settings for interfaces are in the Customizing activity Process Primary Settings for Interfaces to External Systems.

See also the detailed documentation for this Customizing activity. In the standard system, the logical destination for commission is assigned to class /PM0/CL_AB_INT_CS. Use class /PM0/CL_B_INT_PFO for portfolio assignment.

The following section only deals with the Customizing activities for Incentive and Commission Management (FS-ICM). We recommend you open the corresponding activities in the Customizing structure. See also the detailed documentation for the individual activities in the lower-level hierarchy nodes. This is only a short overview.

4.1.5.1 Assign FS-ICM Commission Application to Logical Destinations

You assign the following settings to a logical destination. (You define the logical destination using transaction SM59).

a) Commission System Application: A commission (system) application is the result of converting the company’s strategic goals into a data-processing construction based on a commission model. This is a technical grouping of all the elements in a commission


April 2017 18

installation that contains all the parts of the commission system generated in accordance with Customizing, for example: Business Partner Administration, Commission Contract Administration, Transactions for Commission Contract.

b) Version of Commission Application

c) Partnerships: You use this setting to define the data exchange between FS-PM and FS-ICM for partnerships. For more information about partnerships, see Customizing for FS-ICM.

d) Fill Identification Business Transaction: This setting controls the filling of the FS-ICM attribute Identification of Remunerating Business Transaction (REM_BUSCASE_ID) in the commission case header.

e) Fill Business Object Version: This setting controls the filling of the FS-ICM attribute Business Object Version (BUSOBJ_VERS) in the commission case header. In the standard system, you can fill this with the FS-PM sequence number, the FS-PM journal number (only if you are working strictly on the basis of contracts), or a string of characters comprising the FS-PM effective date and the FS-PM sequence number (recommended).

f) Use of Commission Case Buffer: You can only set this indicator if you have activated the commission case buffer in FS-ICM for the current commission application. If you set this indicator, you increase the performance of data exchange between FS-PM and FS-ICM. For more information on this function, see Customizing for FS-ICM.

4.1.5.2 Edit FS-ICM Business Object Categories

In this Customizing activity, you enter the business object categories of ICM, for subsequent use in FS-PM. The business object category specifies the unique ID for an object type in the commission system for which a commission is triggered. Each commission application can manage different object types that are defined in this attribute. The exact business objects that are available are determined by the Customizing settings for FS-ICM. This data element /PM0/ABD_CACSBUSOBJTYP_NN corresponds to the data element CACSBUSOBJTYP in FS-ICM.

4.1.5.3 Edit FS-ICM Subobject Types

In this Customizing activity, you enter the subobject types from ICM, for subsequent use in FS-PM. This identifies a subobject type that is part of an external business object for the commission system. The exact subobject types that are available are determined by the Customizing settings for FS-ICM. This data element corresponds to data element CACSOBTYID in FS-ICM.

4.1.5.4 Edit FS-ICM Business Transaction Categories

In this Customizing activity, you enter the business transaction categories from ICM, for subsequent use in FS-PM. The business transaction category specifies the unique ID for a business transaction that remunerates a commission. The business transaction categories that are available are determined by the Customizing settings for FS-ICM. The data element /PM0/ABD_CACSBUSCASTYPCOPY_NN corresponds to the data element CACSREMBUSCASTYP in FS-ICM.


April 2017 19

4.1.5.5 Edit FS-ICM-Triggering Methods

In this Customizing activity, you enter the triggering methods from FS-ICM, for subsequent use in FS-PM. The triggering method indicates the way in which a triggering object changes. The commission activity type is derived from the triggering object and the triggering method. The commission activity type describes the activity that is relevant to commission. The exact triggering methods that are available are determined by the Customizing settings for FS-ICM. The data element /PM0/ABD_CACSTRIMETH_NN corresponds to the data element CACSTRIMETH in FS-ICM.

4.1.5.6 Assign FS-ICM Business Object to FS-PM Product Module Group Sales Product

In this Customizing activity, you define:

Which business object category is to be transferred to the Commission Management system (FS-ICM) in the commission case. This is transferred in the header of the commission case in attribute BUSOBJ_TYPE. The exact business objects that are available are determined by the Customizing settings for FS-ICM.

How the commission cases for a policy are to be created (Policy Processing flag). FS-PM either creates a single commission case for each policy in the New Business business process, or separate commission cases for each contract in a policy.

You need to have processed the Customizing activity Define Product Module Groups for the group dimension INTFSCS in advance.

4.1.5.7 Process FS-PM Entities/Attributes Relevant to FS-ICM

In the Customizing activity, you map the FS-PM entities to the FS-ICM import structures. You define which attributes of the different entities of an FS-PM policy are transferred to the transfer structures for Commission Management in a commission case (attribute mapping).

You define which FS-PM entity is mapped to which ICM structure in the ICM-Relevant Entities dialog structure. For more information, see the documentation for the Customizing activity.

4.1.5.8 Assign FS-ICM Business Transaction Category to FS-PM Journal Entry

In this Customizing activity, you assign a combination of commission application, object category and FS-PM processing (for example, Change Benefit/Premium) to a business transaction category in FS-ICM. The available business transaction categories depend on Customizing for FS-ICM. The assigned business transaction categories are transferred to FS-ICM, to the Remunerating Business Transaction in Operational System attribute (REM_BUSCASE_TYP) in the header of a commission case.

4.1.5.9 Assign FS-ICM Triggering Methods to FS-PM Journal Entry

In this Customizing activity, you assign a combination of commission application, object category, subobject category, and FS-PM processing (for example, Change Benefit/Premium) to a triggering method in FS-ICM. The triggering methods available depend on Customizing for FS-ICM. The assigned triggering methods are transferred to the activity data for a commission case in FS-ICM. This determines which activity is triggered in FS-ICM.

4.1.5.10 Define Commission Posting Text

It is possible to set an FS-ICM commission case to pending from within FS-PM.

In this Customizing activity, you define the reasons that can be selected for a pending case. This text is then displayed in the commission case in FS-ICM (CASE_TXT field).


April 2017 20

4.1.5.11 Assign Function Modules to Logical Names

In this Customizing activity, you can define which function modules are used for communication with FS-ICM.

4.1.5.12 Copy Transfer Structures of FS-ICM

In this Customizing activity, you can copy the transfer structures that are required to integrate FS-ICM from an ICM system to the FS-PM system.

Reminder: In FS-ICM, individual commission applications are generated. When these are generated, the transfer structures required by the <APPL>_RFC_CASE function module to create commission cases are also generated. (<APPL> stands for the name of the commission application generated in FS-ICM.) If FS-ICM is not located in the same system as FS-PM, these transfer structures must be copied from the FS-ICM to the FS-PM system, otherwise it is not possible to create commission cases.

In this Customizing activity, you can automate the copying procedure. The structures are then automatically activated. If the structures already exist in FS-PM, when you restart this Customizing activity the existing structures are overwritten with the current structures of the ICM system. In the selection screen, choose the name of the commission application, the logical destination of the FS-ICM system, a package and (where applicable) a Workbench request. For more information, see the FI help for the input parameters in the selection screen.

4.1.5.13 BAdIs: Enhancement of ICM Interface

There are five BAdIs available. See the documentation for the relevant Customizing activities.

Adjust RFC Call

Adjust Commission Case

Adjust Commission Overview

Adjust Master Data Procurement

Adjust Dialog Gotos

4.1.6 Packages and Central Classes for the ICM Interface

The central package for the ICM interface is /PM0/ABT_CS (FS-PM Basis Integration: Commission).

The central class for the FS-PM interface to ICM is /PM0/CL_AB_INT_CS.

4.1.6.1 Class /PM0/CL_AB_INT_CS

When you look at the constructor, you will see that the data types ANY TABLE or ANY are used extensively. At this point the Customizing activity Copy Transfer Structures of FS-ICM comes into play. The data structures are generated in FS-ICM. To make the fields of the transfer structure known in Policy Management, you can use the report that is specified in this Customizing activity to copy the structures into FS-PM. These are then named as follows: <commission application>_ ACT, _BDL, _CAS, _DOCACT, _DOCDT, _DOCHD, _DOCINV, _DOCOBJ, _DOCPAR, _DOCRE, _DOCREL, _DOCSE, _DOCVA, _INV, _LIN, _OBJ (important), _PAR, _REL.

If you regenerate your structures in FS-ICM, you must also make this known to SAP Policy Management. To do this you need the version in the Customizing activity Assign FS-ICM Commission Application to Logical Destinations.

The actual mapping based on the data and fields specified is executed by the method MAP_CS_DATA. This central method is called by several methods in this class. These other


April 2017 21

methods, such as MAP_CS_DATA_POLICY or MAP_CS_DATA_POLPR, first read the data in the relevant entity to then call the module MAP_CS_DATA.

The methods BUILD <Type> TABLE generate the relevant <Type> tables in the commission case (OBJ, for example). The method MAP_CS_DATA is also called here at some point in the hierarchy.

Ultimately, most of the methods in this class call the Customizing and extract the parts that are relevant in each case. They then read the entities in Policy Management and map the necessary information to the export tables.

Moreover, the class also implements the interface /PM0/IF_AB_INT_APPROVE. A broad outline of the COMMIT method in class /PM0/CL_IM_ABB_COMMIT is presented in the SMG for Release. In this method you will find the call /PM0/IF_ABB_BPU_APPR_INT~COMMIT_CS., for example. This includes the following coding section:

DATA lr_int_approve TYPE REF TO /pm0/if_ab_int_approve.

DATA lt_int_keys TYPE /pm0/abd_interface_keys_t.

CONSTANTS:

lc_interface_name TYPE /pm0/abu_iname_id VALUE /pm0/cl_ab_int_creator

=>gc_cs.

* get FS-CS interface

lr_int_approve ?= /pm0/cl_ab_int_creator=>get_instance(

iv_interface_name = lc_interface_name ).

lt_int_keys = det_int_keys(

it_keys = it_keys

iv_interface_name = lc_interface_name ).

lr_int_approve->commit( lt_int_keys ).

This point, together with the PUT method, links the release to the interface supply for ICM. Similar cases apply for the other operational systems.

The class also implements the interface /PM0/IF_AB_INT_CS. This includes central methods such as CASE_CREATE (Create New Commission Case). At a suitable point, the method BUILD_CASE_TABLE is called, which then calls the method MAP_CS_DATA.

This class also includes method /PM0/IF_AB_INT_CS ~SET_INTERFACE_DATA, which is called in the CLOSE_TMF phase of the update, so that the operational systems can be supplied with data.


April 2017 22

4.2 FS-PM <-> PFO

Portfolio Assignment (PFO) is responsible for assigning portfolio between the FS-PM in-force business and the commission contract in FS-ICM. This document assumes that you are using FS-ICM and not a custom incentive and commission system.

4.2.1 PFO for Commission Participants

1. Before you can create a portfolio (in-force business) in FS-PM, there must be a commission contract in FS-ICM.

2. This commission contract is mirrored (copied) in PFO.

a. The system writes an assignment object (ZO) with the key of the commission contract to the database (database table PFO_ZO_0000).

b. The system writes segment objects with the key of the commission contract to database table PFO_SEG.

c. The relationship between the assignment object (ZO) and the segment object(s) is created and written to database table PFO SZO.

3. You can now create a new business in FS-PM, specifying the commission contract.

4. This is then copied to PFO when the new contract is created.

a. The business object BO for the policy (with the corresponding key for the policy) is written to database table PRO_GO_00IP. The PFO for Commission Participants scenario above only uses table PFO_GO_00IP because in the standard system commission participants are only managed at policy level.

b. The relationships are now created based on the defined roles between the segment object and the business object of the policy in PFO. They are written to database table PFO_GZO (GZO = business assignment object). Data is created for each role in the commission contract (role xy agent with z%).


April 2017 23

The following settings are required in Developer Customizing for FS-ICM:

4.2.1.1 PFO Integration Scenarios

In order to make these settings you need to have created the relevant assignment objects, segments, and their relationships in FS-ICM.

FS-PM: New Business Business Process

FS-PM first checks whether the commission contract exists in the core ICM system. If this is the case, the system first calls PFO. The master data objects business object (BO) and business assignment object (GZO) are created in PFO. FS-PM calls the core ICM system to create the commission case.

FS-PM: Inquiry Business Process

FS-PM calls PFO. It reads the current assignments and returns these to FS-PM.

FS-PM: Change Business Process (Commission-Relevant Change)

FS-PM calls PFO. It reads the current assignment. FS-PM then calls the core ICM system to create a commission case.

FS-PM: Change Business Process (Change to Commission Participant)

FS-PM calls PFO. It reads the current assignment. FS-PM calls PFO again and changes the PFO GZO assignment between the segment object and the PFO business object for the policy.

FS-ICM (in PFO)

In PFO, you can change the PFO GZO assignment between the segment object and the PFO business object for the policy in dialog mode.


April 2017 24

FS-ICM (Mass Change Portfolio Assignment)

If you want to make a mass change to portfolio assignments in FS-ICM, (for example, an insurance agent has been replaced and the new agent is taking on the former colleague’s portfolios,) the FS-ICM component Framework for Object Assignment (FOA) comes into play.

To do this, you must ensure that there are other commission contracts (for the new insurance agent, for example) to which the conversion can be made.

In this case, FOA calls PFO based on its worklist (worklist type 03Z2) and makes the changes to the assignments.

A corresponding worklist must exist in FOA:

There are three more definitions of worklists in PFO that can also be used by FS-PM (0PMP, 0PMS, and 0PMV).

4.2.1.2 FS-PM: Control Settings for the Generation of Portfolio Assignment

The implementation of the business transaction determines whether data is written in PFO. The PFO indicator in Customizing has no effect. In general, the commission case and the PFO assignment are independent, although when the commission case is processed data is read from PFO.


April 2017 25

4.2.2 PFO for Organizational Units

In addition to people, you can also assign organizational units to the commission contract (FS-OM) in PFO using the PFO segment organizational unit (type 0PMO). On the other hand, in the “PFO for Organizational Units” scenario, you can use the tables PFO_GO_00IP (policy), PFO_GO_00IV (contract), and PFO _GO_00IS (coverage) because organizational units may need to be represented at all three main axis levels in the standard system.

This means that in PFO it is possible to create PFO BOs for the policy (type 00IP) and trigger the creation of PFO BOs for the contract (type 00IV) and coverage (type 00IS) from FS-PM. Between these entities, PFO GZOs can be created for the roles 0KOE, 0VTE and 0VWE.

4.2.3 FS-PM: Integration Customizing for PFO

4.2.3.1 FS-PM: Portfolio Assignment PFO

The activities described below are in Customizing for Policy Management under Integration Portfolio Assignment PFO.

4.2.3.1.1 Define Interface to Portfolio Assignment

In this Customizing activity, you determine whether you are going to use the functions of portfolio assignment (PFO) of FS-ICM.

For more information, see the detailed documentation for the Customizing activity. You will find the documentation in Customizing for Policy Management under Integration Portfolio Assignment PFO -> Define Interface to Portfolio Assignment.


April 2017 26

Note that you also need to have activated the portfolio assignment function in FS-ICM. This automatically generates the segment and the assignment object for the commission contract in PFO.

4.2.3.1.2 Process Commission Agent Roles

In this Customizing activity, you define the various commission agent roles that you want to use in your FS-PM system. You can also define standard Customizing for display. The commission agent roles that you create here can be selected in the dialogs where you specify commission participants.

For more information, see the detailed documentation for the Customizing activity. You will find the documentation in Customizing for Policy Management under Integration Portfolio Assignment PFO -> Process Commission Agent Roles.

4.2.3.1.3 Business Add-Ins (BAdIs)

There are three BAdIs available. See the documentation for the relevant Customizing activities.

BAdI: Adjust RFC Call

This Business Add-In (BAdI) allows you to change the actual call for the RFC function module for portfolio assignment (PFO) to create and modify business objects and business object assignments.

BAdI: Determination of a Segment in PFO and BAdI: Read Accesses to PFO

You use these BAdIs to redefine read access to determine a segment from portfolio assignment.

For more information, see the detailed documentation for the BAdIs. You will find the documentation in Customizing for Policy Management under Integration Portfolio Assignment PFO -> BAdIs.

4.2.4 Packages and Central Classes for the PFO Interface

The main package for the ICM interface is /PM0/ABT_PFO (FS-PM Basis Integration; Portfolio Assignment).

The main class for the FS-PM interface to Portfolio Assignment is /PM0/CL_AB_INT_PFO. You will find these in Customizing for Policy Management under Integration Process Primary Settings for Interfaces to External Systems.


April 2017 27

4.2.4.1 Classification

Class /PM0/CL_AB_INT_PFO_SWITCH generates instances of class PM0/CL_AB_INT_PFO_FIXVAL or /PM0/CL_AB_INT_PFO, depending on Customizing.

Class /PM0/CL_AB_INT_PFO_FIXVAL is called by class /PM0/CL_AB_INT_PFO_SWITCH and returns dummy values.

Class /PM0/CL_AB_INT_PFO delegates its calls either to /PM0/CL_AB_INT_PFO_COM_ON (use of PFO) or /PM0/CL_AB_INT_PFO_COM_OFF (no use of PFO). In the case of “ON”, class /PM0/CL_AB_INT_PFO_COM_ON calls class /PM0/CL_AB_INT_PFO_REMOTE, which in turn controls the calls to Portfolio Assignment.

In the case of OFF, class /PM0/CL_AB_INT_PFO_COM_OFF is used for assigning portfolio.


April 2017 28

Summarized description of the process:

1. Business process in FS-PM (“Change” business process for example).

2. With the Change or Display Commission Participant business transactions, for example.

3. GET_COM: Get Commission Contract.

4. GET_ALL_VERSIONS: Get versions from PFO using call via interface /PM0/IF_AB_INT_PFO_COMM.

5. GET_ALL_VERSIONS from interface /PM0/IF_AB_INT_PFO_ACCESS (implemented by class /PM0/CL_AB_INT_PFO_REMOTE, for example).

6. PFO call: Various portfolio assignments are determined for a given policy.

7. -9. Return and processing in the relevant interim layer.

10. ICM call: Get available commission contracts.

12. and 13. Optional saving of application.

14. Release application {

15 COMMIT: Using /PM0/IF_AB_INT_APPROVE (implemented by class /PM0/CL_AB_INT_PFO, for example).

16. APPROVE_INTERFACE:

17.-22. GET_ALL_VERSIONS see steps 4.-9. to use GET_ALL_VERSIONS to receive all existing assignments for a policy.

23.-28. GET_SEG : Get PFO segment objects and their assignments.

29. COMMIT: Call COMMIT methods (see 15.).

30. PUT: Call relevant methods to create potential new PFO entities or specify data necessary for the update.


April 2017 29

4.2.4.2 Fixed Values

This section may be relevant in the test phase.

If it is not possible to access PFO (for example if the system is not currently available or configured completely) it may be the case that other processes or operational systems that are not involved in commission calculation are also interrupted. To avoid this and avoid hampering the test progress, you can use a dummy PFO (implemented class in FS-PM only) that returns fixed values when called. You activate this class /PM0/CL_AB_INT_PFO_FIXVAL in Customizing for Policy Management under Integration in the Customizing activity Process Primary Settings for Interfaces to External Systems.

Choose Portfolio Assignment and Assign Classes to Logical Destinations. Replace the existing interface class /PM0/CL_AB_INT_PFO with /PM0/CL_AB_INT_PFO_SWITCH. Users that want to use the regular PFO set the user parameter /PM0/ABT_PFO_SWITCH = REAL.

4.2.4.3 Class /PM0/CL_AB_INT_PFO

This class generates instances from either class ...COM_ON or ...COM_OFF depending on whether you want to use PFO. (You define whether you want to use PFO by setting the Active indicator in Customizing for Policy Management in the Customizing activity Define Interface to Portfolio Assignment under Integration Portfolio Assignment PFO.) In the constructor for class /PM0/CL_AB_INT_PFO, depending on whether the indicator is set, PFO is used (using instance for class /PM0/CL_AB_INT_PFO_OM_REMOTE and instance for class /PM0/CL_AB_INT_PFO_COM_ON), or a local portfolio assignment is used, (using the instances for the classes /PM0/CL_AB_INT_PFO_OM_LOCAL and /PM0/CL_AB_INT_PFO_COM_OFF).

Class /PM0/CL_AM_INT_PFO delegates all further queries to the relevant instances ON or OFF:

In class /PM0/CL_AB_INT_PFO_OM_REMOTE, the method WRITE-OMDATA_TO_PFO is relevant because it calls the function modules for PFO.

4.2.4.4 Database Tables

Where Table Use

FS-PM /PM0/ABDTPFOGZO Commission participants are stored in this table.

FS-PM /PM0/ABDTPFOGO Only use if PFO is OFF. Stores commission participants for a policy.

FS-ICM CACS_CTRTBU Commission contract data

PFO

PFO_ZO_0000

PFO_SZO

PFO_SEG

PFO_GZO

PFO_GO_00IP (Policy)

PFO_GO_00IV (Contract)

PFO_GO_00IS (Coverage)

See above. Only used for contracts.

Entities /PM0/ABDACOMMIS and /PM0/ABDACOMROLE are no longer relevant. These entities are both from released prior to release 5.0. The alternative commission participant is stored in /PM0/ABDACOMDIFF and does not use PFO.


April 2017 30

4.3 FS-PM <-> FS-CD (Collections/Disbursements)

FS-CD processes the payment transactions, monitors the settlement of open items, monitors the dunning process for payments in arrears, and manages the postings and the display of premiums paid.

4.3.1 FS-CD: Master Data

A contract account in FS-CD is a subledger account, to which postings from open positions are made.

An insurance object defines an object, which operational systems use as the basis for collecting or disbursing amounts. An insurance object can be an insurance contract (master data model 1 Policy Management), a policy (master data model 2 Policy Management), a commission contract (FS-ICM), a broker contract (FS-ICM), a reinsurance treaty (FS-RI) or a claim (Claims Management).

More than one business partner can be assigned to a contract account. One assignment is marked and represents the account holder.

A business partner can be assigned to more than one contract account.

A business partner can be assigned to more than one insurance object.

An insurance object can be assigned to more than one business partner.

The assignment of a business partner to an insurance object is an insurance relationship.

An insurance relationship is only assigned to a single contract account.

More than one insurance relationship can be assigned to a contract account.

Examples


April 2017 31

The examples comply with the definition above.

4.3.1.1 Mapping FS-PM <->FS CD

Both the insurance object and the business partner must be specified when postings are made. As both the contract account and the business partner are uniquely assigned to one insurance relationship the account assignment is clear.

4.3.1.1.1 Master Data Object: Contract (Master Data Model 1)

The contract number is used to define the insurance object in FS-CD:

The value “IN-contract number” is entered in the INSOBJECT_ID field in the contract /PM0/ABDAPOLPR.


April 2017 32

4.3.1.1.2 Policy Master Data Object (Master Data Model 2)

The policy number is used to define the insurance object in FS-CD:

The value “IN-policy number” is entered in the INSOBJECT_ID field in the contract /PM0/ABDAPOLPR.

The additional business partner is only set in FS-CD if the premium payer is not the same as the policyholder.


April 2017 33

4.3.2 FS-CD: Insurance Object, (Contract) Account, Cash Flows and Information Container

The insurance object and the contract account are master data in FS-CD. The cash flows for an account are described here as transaction data.

The information container enables the FS-CD system to send information to sending systems.

4.3.2.1 Insurance Object

You use transactions INSOCREATE, INSOCHANGE, and INSODISP to create, change, or display insurance objects directly in the FS-CD system.

The header database table DIMAIOB contains the insurance object number and administrative data (such as date entered, name of the user who added or changed the object, and so on) and also the external insurance object category (such as insurance contract, broker contract).

The insurance object relationship table DIMAIOBPAR contains control fields, including:

o Dunning Variant (MVARI)

o Contract Account Number (PARTNERACC)

o Invoicing Type (FAART)

o Planning Group (FDGRP)

4.3.2.2 Contract Account

You use transactions CAA1, CAA2, and CAA3 to create, change, or display contract accounts directly in the FS-CD system.

In addition to administrative data (such as date entered, name of the user who added, changed the account, and so on), the contract account header (data base table FKKVK) also contains control fields, including:

o Application Area (APPLK)

o Contract Account Category (VKTYPE with TFK002A as permitted value range)

o Account Management (KONTF)

o Clearing Variant (UVVAR)

You use the contract account category to determine whether the account is a vendor or customer account, for example. You can also define here, whether the account is a broker account, a premium account, and so on. For more information, see Customizing for FS-CD under SAP Insurance Commissions/Disbursements Basic Functions Contract Accounts Number Ranges and Contract Account Categories Configure Contract Account Categories and Assign Number Ranges.

In addition to the header data for the contract account, the table also contains item data (database table FKKVKP). Both the contract account number and the business partner number are key fields. Here you will find central data, such as:

o Company Code (STDBK)

o Incoming Payment Bank Details (EBVTY)

o Outgoing Payment Bank Details (ABVTY)

o Incoming Payment Method (EZAWE)


April 2017 34

o Dunning Procedure (MAHNV)

o Relationship of a Business Partner to a Contract Account (VKPBZ)

o Correspondence Variant (COPRC)

4.3.2.3 Cash Flows

The cash flows in FS-CD are not master data but transaction data. They represent the payment flows for an account. A distinction is made between the real payments, made by a customer and the planned payments (payment plan). If differences arise between the payment plan and the actual payments, dunning notices can be triggered. FS-PM creates and manages cash flows. These cash flows are transferred from FS-PM to FS-CD. FS-CD converts these cash flows into CD items (payment plan items, for example). FS-CD uses this information to generate its own correspondence and, in cases of payments not made, the dunning procedure.

In FS-CD the data base table for payment plan items (VVSCPOS) plays a key role here. It includes:

o Time Stamp (Key Field SCPOSNR)

o Valid-From Date for Payment Plan Item (PMTFR)

o Company Code (CCODE)

o Amount in Transaction Currency with +/- Sign (AMOUNT_TOTAL)

o Currency Key (CURR)

o Payment Plans: End Type for a Payment Plan Item (ENDTYPE)

o Document Type (BLART)

4.3.2.4 Information Container

You can use information containers to send confirmations and information from FS-CD to FS-PM. The information container is a temporary storage medium that stores information about business transactions and processes in the form of confirmations, which trigger downstream processes in other systems.

The Customizing in the FS-CD System is under SAP Insurance Collections/Disbursements Integration Information Container.

The Customizing in the FS-PM system is under Policy Management Integration Collections/ Disbursements FS-CD Information Container.

Moreover, as of Release 5.2 you can implement the BAdI: Reaction to FS-CD Information Container in Time Model Function in Customizing for Policy Management under Integration Collections/Disbursements FS-CD Business Add-Ins (BAdIs). This Business Add-In (BAdI) is used in SAP Policy Management (FS-PM) in the time model function as a reaction to the receipt of an information container from the Collections/Disbursements system. You can use this BAdI to determine whether a business transaction, and which one, should be scheduled as a reaction to a specific dunning level being reached in FS-PM. This BAdI is called during the time model function DUNLEVEL - Reaction Dunning Level (Define Dates and Time Model Functions) if the system detects an information container that has not yet been processed. With this BAdI you can determine whether a business transaction is to be scheduled, and on which effective date. Furthermore, the data required to schedule a business transaction as a BTS date has to be determined. The scheduling and execution of the BTS date is handled in the update.

The Customizing for FS-PM also contains the BAdI: Confirmation Processing for Info Container. It is used in the Financial Services Policy Management In-Force Business Management (FS-PM-IB) component. The info container interface of FS-PM processes confirmations that are sent to FS-PM by FS-CD. It calls this BAdI when a confirmation has been processed. The call is made if


April 2017 35

processing was successful or with errors. In this BAdI, it is possible to customize the consequences of processing of a confirmation. If a confirmation was not processed successfully, the default implementation sends a message to the Business Workplace of the last processor of the contract. The message contains the policy number, contract number, description of the confirmation, and reason for the error. If you want the interface to handle the processing of a confirmation differently from the default implementations, then you need to implement your own BAdI.

For more information, see the documentation for the relevant Customizing activities in the respective systems.

4.3.2.4.1 Example Usage of the Info Containers

Target Investment: An expected payment of USD 1000 on 2016-2-1 has not been made completely (only USD 900 on 2016-2-15): Depending on the settings, a dunning notice may be created in FS-CD. The insurance company may have made advance payments for an investment fund, and costs may have been incurred. It is possible that the settings in FS-CD have been made so that an information container is generated and selected using the mass run Forward Information (transaction FPINFCO1, previously VINFO1). Using the FS-PM interface to the information container, the system stores an external date for the information container in FS-PM and maps the FS-CD information container to the FS-PM information container. During the update, a corresponding time model function is executed and the corresponding data in the different FS-PM components of the accounting components or entity data is updated.

Actual Investment: The customer pays when they have the money available - > only this amount is invested. FS-CD informs FS-PM of the amount invested. If no payment is made there are no consequences. In the update, the system executes the time model function for Actual Investment.


April 2017 36


April 2017 37

4.3.2.5 Dunning Notices

Example: The following processing rules apply for the execution of a dunning procedure in accordance with §38 German insurance contract law (initial premium) for motor vehicle insurance: A reminder letter is sent to the policy holder 10 days after the due date of the initial premium. The customer is also charged a processing charge of USD 6, which is statistical and so can only be posted as relevant for the general ledger when the payment for the charge is made. All of the items due for dunning must be listed on the reminder letter. A payment form must also be printed.

A dunning procedure “Motor vehicle, initial premium” needs to be created.

This dunning procedure is assigned to the dunning procedure category “initial premium dunning procedure”. The dunning procedure category is used for insurance policies in order to display the initial premium separately from subsequent premiums on the dunning letter. This rule only applies in the context of the dunning procedure type Collective Dunning.

A dunning level 1 Reminder has been defined for the dunning procedure, which is activated 10 days after the due date of the initial premium. Enter 10 days in arrears. This dunning level has been assigned to the dunning level category Reminder.

A charge category 01 Processing charge has been created.

A charge schedule 01 CS with Charge Category 1 (Absolute/Statistical) has been created.

Charge category 01 has been assigned to charges schedule 01. Here you define that the processing charge of USD 6 is to be posted statistically.

This charge schedule has been assigned to dunning level 1 of the dunning procedure Motor Vehicle, Initial Premium.

A text module ER1 Reminder letter has been created for the reminder letter in the Information Procedure table.

Dunning level 1 has been linked to the text module in the Dunning Activities table. In addition, a checkbox has been set, indicating that a payment form is to be printed.

The dunning procedure has been linked to a dunning variant.

The dunning level in FS-PM is transient and is requested in FS-CD from FS-PM.

To execute the dunning procedure and make other settings for dunning in FS-CD, see also the documentation in FS-CD for the Customizing activities in Customizing for Policy Management under SAP Insurance Collections/Disbursements Business Transactions Dunning.


April 2017 38

4.3.2.6 FS-CD Locks

In certain business transactions, it may make sense to exclude objects such as line items from further processing until a specific condition has been met.

FS-CD locks belong to the control settings in the contract account and are defined in FS-CD in the contract account or in the insurance relationship. If the locks are defined in the insurance relationship they are then valid for the contract account involved in the relationship. (If the lock is defined in the contract account, the lock can affect more than one insurance relationship). Locks are temporary.

FS-PM always defines locks in the insurance relationship.

The following insurance relationships are affected:

o Premium relationship (policy or contract, depending on the master data model)

o Policy loan

Possible locks and their effects are as follows:

Locks Lock Category

Effects in FS-CD

Posting Lock 09 You can use this lock to define that no documents can be entered, cleared, reversed, or reset. You can also choose between a posting lock and a clearing lock. If you have set a lock, during clearing processing in the dialog mode the open items of a locked contract account are indicated with an icon and cannot be set to active.

Incoming Payment 02 A payment lock for incoming payments prevents the payment program from executing debit memos/automatic debits for this contract account - based on the business partner.

Outgoing Payment 03 A payment lock for outgoing payments prevents the payment program from making disbursements for this contract account - based on the business partner.

Invoicing 05 The lock prevents invoicing, budget billing requests and the creation of a partial invoice for the contract account.

Dunning 01 A dunning lock ensures that when the dunning program is executed, items due for dunning are not dunned or that restrictions to the dunning process apply.

Items locked for dunning are not included in the amount limit check. As long as they are locked, these items also do not change dunning level.

Dunning Correspondence 07 A dunning correspondence lock prevents incoming correspondence that is due for dunning from being dunned.

Interest Calculation 04 An interest reason lock stops interest documents that refer to items on this contract account from being posted.


April 2017 39

In FS-PM

In New Business, the system determines the locks together with the master data in the release and transfers this information to FS-CD.

In all other business processes, the system determines the lock data in the interface after leaving the dialog but only transfers to FS-CD in the release, after other master data (such as incoming payment method of premium payer) has been transferred.

You can define which lock categories and lock reasons are permitted and for which actions (create, change, delete) in Customizing for Policy Management under Integration Collections/Disbursements FS-CD FS-CD Locks Assign FS-CD Lock Reason to Lock Category. For example, it should be possible for an FS-PM processing clerk to create and change a dunning lock with the reason Receivable Disputable, but not be authorized to delete it. This Customizing is not role-dependent.

The actual logic is encapsulated in the process models for the FS-CD locks, in the Application application context for FS-CD locks and in the FS-CD interface.

The data to be displayed in the ALV grid is formatted in the process model P_B_S_ACN_LOCK_CD (overview dialog FS-CD Locks). This means that the locks that were previously in the application context and the locks that already exist in FS-CD but need to be changed are compared.

The data entered is then validated in the process models P_B_S_ACN_LOCK_CD_ADD (Add Lock) and P_B_S_ACN_LOCK_CD_DET (Change Locks) (Detailed Dialogs).

Furthermore, when locks are changed, created, and deleted, the Customizing mentioned above (FS-CD Assign Lock Reason to Lock Category) is used.

The locks are managed in the application context. The context provides methods, for creating, changing, and deleting locks. The check and validation methods are also here.

The lock data is determined, mapped, and transferred to FS-CD in the CD interface.

If a lock data change is not yet in FS-CD but is in the interface table, the data from the interface table is displayed in the CD overview. Two further tools are relevant in the context of data communication; The Session Property List (Workbench Manager: Request Stack) and the Process Context Stack (Methods for Process Layer Manager).

The latter are used for communicating between the overview dialog and the detailed dialog and between dialogs and activity classes. The application context is used to persist the lock data and to communicate with the FS-CD interface. The interface tables are used to communicate between FS-PM and FS-CD.


April 2017 40

4.3.3 FS-PM: Controlling the Generation of Insurance Objects and Transaction Data

Before you can post transaction data, the relevant master data must exist in the system. Without an insurance object and contract accounts you cannot post documents to the relevant accounts. This master data in FS-PM is transferred via the FS-CD interface to FS-CD for creation. Since there are no Customizing settings that determine when something is relevant for master data, the BAdI method /PM0/ABP_CD_BADI_473-> GET_DATA_COLLECTION_METHODS has been provided. Here you need to define when which master data (premium/loan/premium deposit) is to be created.

The contract account and the insurance object in FS-CD are created simultaneously when the initial premium is posted. The cash flow generation is transferred to FS-CD later via the interface of the accounting component. The process is illustrated in the following diagram:

FS-PM only forwards the disbursing/collecting cash flows to FS-CD. The other documents (non cash flows) are part of the data transfer to FI.

All the write modules in FS-CD are called in the standard system using qRFC. Read modules are called synchronously.


April 2017 41

4.3.3.1 Cash Flow Transfer in the Update /in the Dialog

During dialog processing, and particularly during the update, documents are written that may need to be submitted to FS-CD. Depending on the settings for the run or in Customizing, it is possible that during the update contracts are updated for the entire year as early as in January. However, you need to prevent cash flow documents from being submitted to FS-CD for the entire year because it is possible that changes will be made to the contract over the course of the year. Instead, only the current information, meaning the next period, is to be submitted to FS-CD: FS-PM provides this option. To submit documents already created in January to FS-CD monthly, you can use separate cash flow transfer transactions (or cash flow summarization runs) on the SAP Easy Access screen for Policy Management under Accounting Component Periodic Processing.

4.3.3.2 Cash Flow Summarization Run in FS-PM

The cash flow summarization run is an FPP run. It summarizes all open cash flow documents (POSTINGSTATE_CD = 1) and transfers them to FS-CD. You can use run parameters to restrict the documents that are included. At the start of the run, the system calculates a start time stamp. The run only includes the documents that were in the system up to this point in time. (MOD_TS <= calculated start time stamp).

The summarization logic ensures that the counterpart documents are not submitted to FS-CD. The method /PM0/IF_ABN_BPU_CORE~COMPARE_DOCUMENTS in the accounting component determines which documents are counterparts. Counterpart documents are set to status 4 (No Submission) and status reason (Document Has Been Summarized with Another Document). All the remaining documents are converted to payment plan items and transferred to FS-CD. The status of the transferred items is set to 2 (Posted).

Like all other FPP runs, the cash flow summarization run and the non cash flow summarization run (for transfer to FI) are separated into a preliminary run, parallel processing, and postprocessing. You can simulate both runs.

The preliminary run for the cash flow summarization sets the time stamp (using ABAP command GET TIME STAMP) that later limits the document selection.


April 2017 42

The processing status is written to the application log for FPP (/PM0/CL_FPP_BAL) using the mass logger for FPP (/PM0/CL_ABY_FPP_MASSLOGGING). This applies to both runs. In the parallel processing of the cash flow summarization run, the system reads the open documents according to the selection criteria, summarizes them as far as possible, and submits them as payment plan items to FS-CD. The policies affected are temporarily locked.

In postprocessing, the application log for FPP (/PM0/CL_FPP_BAL) is transferred to the relevant function modules. The log is then written. In postprocessing for the cash flow summarization run, only the log is written.


April 2017 43

4.3.4 FS-PM: Integration Customizing for FS-CD

Table Description Path

/PM0/ABUTACCDET

Account Determination

In this table the FS-PM posting codes are assigned to the main transactions and

subtransactions in FS-CD (once for each general ledger item and business partner item). These are required for the creation of payment plan items. The Customizing

table is part of the FS-CD interface.

Policy Management Accounting Component Define Account

Determination

/PM0/ABUALOCKR

Assignment of CD Lock Reason to CD Lock Category

Here you define for each lock category (such as Dunning Lock) and associated

lock reason (such as Receivable Disputed)) whether this lock can be

created, changed, or deleted.

Example: A processing clerk in FS-PM is to be able to create a dunning lock

(Receivable Disputed) and change it (change the period, for example) but not delete it. This should only be carried out by a clerk in FS-CD after the points in

dispute have been checked and clarified.

Policy Management IntegrationCollections/Disbursements

FS-CDFS-CD LocksAssign FS-CD Lock Reason to Lock Category

/PM0/ABUTMAPLVL

Assign Mapping Level to Sales Product

In this table you define how a sales product group is to be mapped in FS-CD.

The various master data objects only affect the premium objects - policy loans

are not affected. One effect of the different mapping levels is that a

premium payer in the policy mapping level is not created as a separate

insurance object-partner relationship in FS-CD. (This is entered as an alternative

payer in the insurance object -partner relationship for the policy holder.) This means that you cannot set up locks for the premium payer. This is considered

during data validation and when the search helps on the detailed overview are filled, meaning that the premium

payer is filtered out of the results list in the partner search help in STM2.

Policy Management IntegrationCollections/Disbursements

FS-CDFS-CD Master DataSet FS-CD Master Data Parameters (View Cluster)Prod. Module Grp Sales

Product and Mapping Level

See also the detailed documentation for the Customizing settings for the product modules, which are made in Customizing for Policy Management under In-Force Business ManagementBasisBasic SettingsDefine Product Module Groups.


April 2017 44

Most of the following tables need to be processed in the View Cluster Set FS-CD Master Data Parameters for the group dimension INTFSCD (Integration FS-CD):

Table Name Level

/PM0/ABUTCREACC Assign Account Creation Sales Product, Product

/PM0/ABUTACCDET Account Determination Sales Product, Product,

Elementary Product

/PM0/ABUTACDBAL Assign Account Determination to Balance

Categories Sales Product, Product

/PM0/ABUTCDPRD Product Module Group Assign FS-CD

Master Data Parameter Sales Product, Product

/PM0/ABUTDEFCAC Default Values for Account Creation Sales Product, Product

/PM0/ABUTMAPLVL Assign Mapping Level to Sales Product Sales Product

/PM0/ABUTPROCES Assign Processes Sales Product, Product

/PM0/ABUTROLASS Assign Roles Sales Product, Product

/PM0/ABUTTRANTY Assign Transaction Groups Sales Product, Product

/PM0/ABUTCORVARI Correspondence Variants Sales Product, Product

/PM0/ABUTCORPA Correspondence Parameters Sales Product, Product

/PM0/ABUTCORPRO Assign Correspondence Parameters to

Role Sales Product, Product


April 2017 45

4.3.5 FS-PM: Important Packages/Classes/BAdIs

4.3.5.1 Packages

Packages /PM0/ABT_CD and /PM0/ABT_AC are relevant here.

4.3.5.2 Classes

In general, we recommend that you gain an overview of the classes in the system. This section only lists the names of the important classes and their objects and actions.

The main class for the FS-PM: CD interface is /PM0/CL_AB_INT_CD.

This contains the central methods for CD locks, data transfer to FS-CD (both master data and payment plan items), dunning status, and so on.

Class /PM0/CL_AB_INT_CD_INFOCONT is for the information container.

Class /PM0/CL_DEF_INT_QRFC_CD_BADI is an SAP implementation for BAdI /PM0/ABT_QRFC_CD_BADI, which executes the actual data transfer by qRFC to FS-CD.

In the accounting component (package /PM0/ABT_AC), the class /PM0/CL_AB_INT_AC contains the method APPROVE_CF for the submission of the relevant cash flows as payment plan items to FS-CD.

4.3.5.3 BAdIs

The central BAdI for the actual transfer to FS-CD is /PM0/ABT_QRFC_CD_BADI (BAdI for qRFC).

4.3.5.3.1 Enhancement Spots

/PM0/ABP_CD_BADI BAdI Enhancement for FS-CD interface

BAdI Definition /PM0/ABP_CD_BADI_473 : BAdI Enhancement for FS-CD Interface

BAdI Definition /PM0/ABT_CD_DUNNING_BADI : Determines Dunning Status for Display

BAdI Definition /PM0/ABT_QRFC_CD_BADI : BAdI for qRFC

BAdI Definition /PM0/ABT_RFC_CD_BADI : BAdI for Encapsulating RFC Calls

/PM0/ABT_RFC_CD_GET_IO_BADI : Encapsulates Read Access to the Insurance Object

/PM0/ABP_CD_INFO_BADI_ES FS-CD Information Container Interface

4.3.5.4 Function Group Cash Flow Summarization: /PM0/ABY_FPP_CFC

Function Module Short Description

/PM0/ABY_FPP_CFC_END End of cash flow summarization in FPP

/PM0/ABY_FPP_CFC_INTERVAL Interval module for cash flow summarization in FPP

/PM0/ABY_FPP_CFC_JOBSTART Job start for cash flow summarization in FPP

/PM0/ABY_FPP_CFC_START Start of mass processing for cash flow summarization


April 2017 46

4.3.5.5 Flow Chart

4.3.5.5.1 Data Supply Process FS-CD

In the business processes, there are often phases that deal with the positioning of a policy or a contract (update phase), whereas others are responsible for releasing the data determined (release phase).

Several time model functions can be called within the positioning (see the guide for the Time Model). Within each time model function, there is a POSTPROCESSING phase and a CLOSE_TMF phase. Depending on the time model function, it is possible that cash flows are created and buffered in the accounting component during the POSTPROCESSING phase (CREATE_AND_STORE_CF). In this case, potential master data needs to be formatted and buffered in the FS-PM side of the CD interface (hereafter referred to as CD interface) in the CLOSE-TMF phase.

Several Release Execute steps are executed within the release (see the Concept Guide for Release) during which the buffer for the CD interface and the accounting component interface are also filled with data (for example in the process step SPM0026 in SAP Sample Customizing).

The data is first transferred by the CD interface to FS-CD in the release in the Commit Phase (if there are any payment plan items the CD interface is first called by the accounting component interface). The payment plan items must first be determined from the cash flows from the accounting component. Even if the methods are often named COMMIT, the actual database-COMMIT is executed later. Only then are the qRFCs also run asynchronously in the defined sequence in the operational system and the data is written asynchronously to the database in that system. When this happens physically depends on the system settings and the load on the systems in question.


April 2017 47

4.3.5.5.2 FS-CD Locks

The following flow chart explains the process within dialog processing. It focusses on the processing within the process model in connection with the Application Context (Application) for FS-CD Locks.

Note: The application context Application is generally deleted in the release; this is no longer part of FS-CD locks. You can use the help class /PM0/CL_ABB_BPU_LOCKS in this case. Note, however, that LOCKS does not refer to the FS-CD locks but to all locks (such as contract locks, and so on.)


April 2017 48

4.3.5.5.3 Cash Flow Summarization Run

1. Get Time Stamp for CF Selection

2. For each package

a. Initialize Registry

b. Aggregate Cash Flow

i. Lock Policies

ii. Determine Open Items

iii. Summarize Documents and Counterpart Documents

iv. Generate Cash Flow Plan Items

v. Transfer These to FS-CD

vi. Unlock Policies


April 2017 49

4.4 FI Interface

The non cash flow summarization run is an FPP run and generates totals documents from the document items for the non cash flow documents, which are then converted and submitted to FI-GL (the general ledger). It considers all non cash document items with a posting code that has been set as relevant for FI (/PM0/ABUNPOSCODE-FITRANSFER_FG = X). You can also use the parameters for the run to restrict the documents included.

The FS-PM interface to FI-GL submits items for the general ledger in FI.

Like most other interfaces, you can make the settings for the FI interface in Customizing for Policy Management under Integration Process Primary Settings for Interfaces to External Systems.

The actual integration of the FI-GL is encapsulated in a BAdI (/PM0/ABT_QRFC_FI_BADI). In the standard system, an active qRFC implementation is supplied as the default implementation.

See also SAP Note 1583803 ('Integration of FS-PM with FI-GL Using qRFC').

An additional BAdI (/PM0/ABT_CONVNCSDFI) is also available that you can use to further modify the general ledger items to be submitted (enrich with additional data, for example).

4.4.1 Customizing

In Customizing for Policy Management, choose Accounting Component Define Posting Transactions for G/L Transfer (PM0/ABU_PFI).

In this Customizing activity you define for each company code, which reference transaction and which document type (both from FI Customizing) are to be transferred in the interface to FI-GL. This data is required by FI-GL but is not used anywhere else in FS-PM.

In Customizing for Policy Management, choose Accounting ComponentAssign G/L Accounts to Posting Code (/PM0/ABU_PACCPOC).

In this Customizing activity, you need to enter general ledger accounts for all posting codes, for which the Transfer to FI indicator has been set in table /PM0/ABUNPOSCODE.

In Customizing for Policy Management, choose Accounting Component Define Grouping Criteria for Non Cash Flow Items (/PM0/ABUNNOCASHG).

In addition to the customer’s criteria in Customizing table /PM0/ABUNNOCASHG, the fields from structure /PM0/ABN_NOCASHSUMCRIT_FIX are also always used as separating criteria.

In Customizing for Policy Management choose Accounting Component Define Posting Code (PM0/ABU_PPOSCOD).

In this table, only the Transfer to FI indicator is relevant. The system only includes non cash flow document items for which this indicator has been set when it forms the totals documents.

4.4.2 FS-PM: Important Packages/Classes/BAdIs

The summarization of cash flow documents only operates on the tables in the accounting component, moreover the FI interface only contains accounts and only has two Customizing tables that are relevant for FS-PM. It would be incorrect to refer to this as a data model. Consequently, only the data model for the creation of totals documents is described here.


April 2017 50

4.4.2.1 Data Model: Tables for the Creation of Totals Documents

Database Table Short Description Explanation

/PM0/ABDNNOCASH Non Cash Flow Document with Item

Data in Cluster

The documents in this table are aggregated in totals documents in a multilevel procedure (first level in

parallel processing, second level in postprocessing). The totals document number is then entered in the

TOTALSREFKEY_ID field.

/PM0/ABDNNCSDIX Document item for Totals

Document (Temporary Data)

The interim data for the first summarization level (parallel processing) is saved in this table. In order to

provide a unique primary key for the data, the run number and package number are added to the item

number.

/PM0/ABDNNCSDIXP Document Item for Totals

Document (Temporary Data)

This table stores the reference from the temporary totals document items from the first summarization

level back to the original document items for the aggregated non-cash flow documents.

/PM0/ABDNNCSDH Document Header for Totals

Document

This table stores the header data record for the completed totals document. The table contains the posting status of the totals document, for example.

/PM0/ABDNNCSDI Document Item for Totals

Document This table stores the document items for the

completed totals document.

/PM0/ABDNNCSDIC Totals Document Item: Aggregated

Line Item Numbers This table stores the reference between totals document and line items in compressed form.

4.4.2.2 Packages, Classes, Rough Process Flow

Package: /PM0/ABT_FI

Classes:

/PM0/CL_AB_INT_FI: Interface to FI

/PM0/CL_DEF_INT_QRFC_FI_BADI: Default implementation of BAdI /PM0/ABT_QRFC_FI_BADI: Write access to general ledger using asynchronous qRFC

4.4.2.2.1 BAdIs for FI Interface

4.4.2.2.1.1 /PM0/ABT_QRFCFI_BADI - BAdI for qRFC

Assigned to enhancement spot /PM0/ABT_FI_BADI_ES and uses interface /PM0/IF_EX_ABT_QRFC_FI_BADI:

You can use this Business Add-In (BAdI) to change the actual call of the RFC function module from FI to forwarding non cash flow totals documents to FI.

For more information, see the detailed documentation for the BAdI. See Customizing for Policy Management under Integration Business Add-Ins (BAdIs)-> BAdI: Adjust RFC Call.


April 2017 51

4.4.2.2.1.2 /PM0/ABT_CONVNCSDFI - FI Interface: Conversion of Totals Document to FI Document

Uses the interface /PM0/IF_EX_ABT_CONVNCSDFI:

You use this BAdI to convert a non cash flow totals document from FS-PM into an FI document for FI-GL. The resulting FI document is then checked or updated in FI.

For more information, see the detailed documentation for the BAdI. See Customizing for Policy Management under Integration Business Add-Ins (BAdIs)-> BAdI: FI Interface: Conversion of Totals Document to FI Document.

4.4.2.2.2 Function Group for NC Summarization

NC summarization /PM0/ABY_FPP_NCC

Function Module Short Description

/PM0/ABY_FPP_NCC_AGGREGATE Summarization Module for NC Summarization in FPP

/PM0/ABY_FPP_NCC_END End of Non Cash Flow Summarization in FPP

/PM0/ABY_FPP_NCC_INTERVAL Interval Module for NC Summarization in FPP

/PM0/ABY_FPP_NCC_JOBSTART Job Start for NC Summarization in FPP

/PM0/ABY_FPP_NCC_JOBSTART2 Job Start for NC Summarization in FPP

/PM0/ABY_FPP_NCC_START Start of Mass Processing for Non Cash Flow Summarization


April 2017 52

4.4.3 Class Diagram / Flow Chart

The following class diagram describes the structure of the FI interface.

It explains the individual values for the interface (Fixval, Switch and actual interface), the different access strategies (NOOP, local and remote) and the individual BAdI definitions (/PM0/ABT_QRFC_FI_BADI and /PM0/ABT_CONVNCSDFI).

As for other interfaces, class /PM0/CL_AB_INT_FI_FIXVAL is useful in test scenarios when you want to receive test values without having to address any problems arising in the supply to FI. The connection to the general ledger is made using class /PM0/CL_AB_INT_FI, which in turn activates the general ledger using class /PM0/CL_AB_INT_FI_REMOTE.


April 2017 53

During parallel processing, the data is stored temporarily in a “preaggregation”. The system uses the grouping rules from the customer settings in Customizing.

After the aggregation in parallel processing, there is a final aggregation during which the totals documents are determined. These are sent to FI individually. The original documents are updated and the totals documents are also stored in FS-PM.


April 2017 54

4.5 FS-PM <-> FS-CM (Claims Management)

To begin with, this section will compare the rough object models in SAP Policy Management and Claims Management:

For information on the policy model in FS-PM, see the relevant guides.

In Claims Management, the entities policy product, coverage type and benefit type are used. In principle, Claims Management can also be used without a policy management system and has stored the information required for claims management in these entities.

You will also notice the differing object hierarchies in Policy Management and Claims Management. For example, Claims Management uses benefit type trees, for which there is no equivalent in Policy Management.

A rough outline of the mapping assignment is as follows:

• A contract (product) in FS-PM is assigned to a policy product in FS-CM.

• A coverage (elementary product) in FS-PM is assigned to a coverage type in FS-CM.

• In FS-PM there are various levels (coverage, subcoverage, limit, deductible) that can be mapped to a specific benefit type in FS-CM.

The SAP standard mapping includes mapping to

- Life Insurance

- P&C/Non-Life-Home Contents


April 2017 55

There are fundamental differences between benefit processing for the Life line of business and claims processing for P&C/Non-Life line of business:

o Life LoB:

o In this case a benefit case is very closely linked with contract processing or a change in contract. Every benefit case inevitably leads to a change in the status of the underlying insurance contract (Contract Reengineering).

o The benefit values for the benefit case are specified by the contract and can be determined by calculation.

o All the underlying product information is known to FS-PM and is sent to FS-PM.

o Therefore, the focus of the interaction between FS-PM and FS-CM, in addition to the determination of the data from the underlying contract, is the calculation of the benefit values by FS-PM and the execution of the triggered contract change (Contract Reengineering) by FS-PM.

o P&C/Non-Life LoB:

o In the P&C/Non-Life LoB, there is not the same interconnection between a claim and contract processing. The processing of a claim does not lead to changes in the underlying contract.

o A disbursement amount is usually determined by the amount of the loss incurred, reduced by limits and deductibles. The loss amount is not calculated as it is for life insurance.

o The limits and deductibles can be defined generally by the product or individually in the underlying contract.

o The product information that is only relevant for the processing of a claim and is not required for contract management is not known to FS-PM. This only exists in FS-CM and is defined by the terms and conditions of the product.

o Therefore, the focus of the interaction between FS-PM and FS-CM is the determination of data from the underlying contract. A claim does not directly lead to a contract change/contract reengineering.

o However, claims can have a long-term effect on the insurance contract. For example, the processing of a no-claims bonus (yearly upgrading /degrading in Auto insurance) or a contract cancellation due to too frequent claims or losses that are too high. Unlike for life insurance, however, these effects are not triggered directly by the processing of a claim in FS-CM and a contract reengineering in FS-PM. This type of contract changes is initiated at a later point in time by a different component, (for example the bonus-malus component in Auto insurance) (In the FS-PM Auto Add-On, this change is made by scheduling a related date, which results in a reactivation.)


April 2017 56

4.5.1 FS-CM: CM Master Data

Claims Management is used for the processing of claims (for example for P&C/Non-Life) or of benefit cases (for example for life insurance). When you create a claim or benefit case, this must have a reference to an incident type (burglary, for example) and a policy product (home contents, for example). Based on the incident type and the policy product, Claims Management determines an internal claim type that forms the basis for further processing in Claims Management.

See also the system documentation for the Customizing settings listed below.

The coverage types in Claims Management are in Customizing under SAP Insurance Claims Management Claim Product Configuration Define Coverage Types.

The incident types in Claims Management are in Customizing under SAP Insurance Claims Management Claim Product Configuration Define Incident Types.

You can assign these incident types to a policy product and assign this combination directly to an internal claim type in Customizing under SAP Insurance Claims Management Claim Product Configuration Configure Policy Products.

In this Customizing activity, you can also view which coverage types are assigned to the policy product and how you can assign coverage types to the policy product. You can also assign a benefit type tree to the coverage type in this activity.

You can define the benefit types and the benefit type tree in Customizing under SAP Insurance Claims Management Claim Product Configuration efine Benefit Types.

When you create the benefit type tree you can also define limits or deductibles for the assigned benefit types.


April 2017 57

4.5.1.1 Benefit Type Tree

You can manage the benefit types in the benefit type tree independently from the policy product and internal claim type.

Every benefit type tree has its own versioning.

You can use a benefit type tree in several policy products or in several internal claim types.

You have more flexibility by using different policy products or different internal claim types that have the same permitted benefit types.

4.5.1.1.1 Benefit Types Within the Benefit Type Tree

For each benefit type of a benefit type tree you can make the following settings:

1. Limits per permitted benefit type

2. Deductibles per permitted benefit type

3. (Permitted payment reasons, grouped into payment reason groups)

4. (Permitted object types for procurement of claim items)

Within the benefit type tree, you can also assign a benefit type to a higher level benefit type. This results in the tree-like structure.

This forms the basis for the mapping of FS-PM entities, such as contract, coverage, subcoverage, limit and deductibles, to FS-CM entities.

Assuming the benefit type LT02:02 is in the graphic above is a benefit type for valuables that have a value limit of USD 15,000. LT02_02a is a benefit type for jewelry with a limit of USD 10,000 and LT02_02b is a benefit type for cash with a limit of USD 10,000. If jewelry to the value of USD 9,000 and cash to the value of USD 14,000 is now stolen, the value of the jewelry is under the limit of USD 10,000 but the value of the cash is limited to USD 10,000 if a claim for damages is made. Together, both would generate a claim of USD 19,000 which exceeds the limit for the benefit type for valuables at USD 15,000. At this level the potential disbursement would also be limited.


April 2017 58

4.5.1.1.2 Higher-Level Benefit Type Tree

You can specify a higher-level benefit type tree for benefit type trees in the category Loss. The system then uses this higher-level benefit type tree for checking the entire subordinate hierarchy.

If you specify a higher-level benefit type tree, you store this higher-level benefit type tree representatively for all lower-level benefit type trees in the relevant policy product.

The lower-level benefit type trees are not as relevant for the actual mapping between FS-PM and FS-CM.


April 2017 59

4.5.1.2 Mapping FS-PM <-> FS-CM

The left-hand side of the diagram shows SAP Policy Management with a selection of entities. The right-hand side shows Claims Management with its possible entities. Claims Management only requires a small amount of information/entities from FS-PM: In addition to the contract, these are coverage, subcoverage, limit and deductible.

The dotted line represents the mapping between the entities.

In the SAP Insurance solution, the central entity is the contract. You map from the insurance contract in Policy Management and the policy product in Claims Management but not between the policy and the policy product.

If additional limits or deductibles are required at contract level or contract package level, for example, these must be included in the object modelling for FS-CM and FS-PM and mapped accordingly. (See the diagram above, in which special benefit types have been defined for limits at the relevant level.)


April 2017 60

The values relevant for mapping, which have been defined beforehand in FS-CM, are assigned in the product definition in FS-PM and can be viewed in In-Force Business Configurator. The mapping to Claims Management is in In-Force Business Configurator in FS-PM.

Claims Entity PM Entity IFBC Attribute Comment

Policy Product Contract EXTERNAL_PRODUCT

You need to enter the Claims

Management policy product as attribute

value here.

Coverage Type Coverage CLAIM_COVERAGE_TYPE You need to enter a

valid FS-CM coverage type here.

Benefit Type Coverage CLAIM_BENEFIT_TYPE Also possible.

Benefit Type Subcoverage CLAIM_BENEFIT_TYPE You can enter a

valid FS-CM benefit type here.

Benefit Type Limit CLAIM_BENEFIT_TYPE You can enter a


Benefit Type Deductible CLAIM_BENEFIT_TYPE You can enter a



April 2017 61

4.5.2 FS-CM: Claims and Claim Processing

The use of the term “services” in this section refers to services in general and not eSOA Services.

Claims Management requires updated policy information (policy snapshot). This means that the data determined during data retrieval also must be updated during the services in Policy Management.

The update can take a long time (see the Concept Guide for the Update). Check therefore whether a simplified update can be used for this type of data retrieval (see SAP Note 2137378). You can use this to minimize the update steps required, for example.

4.5.2.1 CREATE Phase of the Claim Process

In this phase, the actual claim is created in the Claims Management system.

Required Steps Service Module for FS-PM Short Description

Check /PM0/ABT_CM_GET_CHECK_DATA

Supplies basic information from FS-PM and is called every time the user in FS-CM enters

data on the corresponding screen and chooses RETURN.

Search Helps (Digits)

/PM0/ABT_CM_GET_POLICY_NR_DATA

/PM0/ABT_CM_GET_POLPR_NR_DATA

Used in FS-CM to generate search helps (policy number, contract number).

Get Contract Data (without

Positioning) /PM0/ABT_CM_GET_BASIC_DATA

Transfers all of the FS-PM information about a contract that FS-CM requires for the policy

snapshot to FS-CM. Better for system performance because there is no positioning.

Get Contract Data /PM0/ABT_CM_GET_CONTRACT_DATA

Transfers all of the FS-PM information about a contract that FS-CM requires for the policy snapshot to FS-CM. More time-consuming

but with actual data.

Get Policy Data /PM0/ABT_CM_GET_POLICY_DATA

Transfers all of the FS-PM information about contracts for a policy that FS-CM requires for the policy snapshot to FS-CM. If required, this can be used by the customer even if it is not

used in the standard calls (the standard system uses the function module).


April 2017 62

Calculation of Benefit Values /PM0/ALT_CM_CALCULATE_BENEFIT

Calculates benefit values (only relevant for life insurance).

Performance: SAP Policy Management uses internal buffering for a contract. If you get data for the same contract for a specific date multiple times using the service module /PM0/ABT_CM_GET_CONTRACT_DATA, SAP Policy Management accesses the buffered data. However, if you read other policies or contracts in between the buffer is emptied or displays the new contract data. In this case the contract needs to be reread completely and the contract updated again.

Once a claim has been created, the P&C line of business does not need any further data from SAP Policy Management.

4.5.2.2 EDIT Phase of Claims Process

This phase is only relevant for life insurance.

Required Steps Service Module for FS-PM Short Description

Calculation of Benefit Values /PM0/ALT_CM_CALCULATE_BENEFIT Calculates the benefit values.

Calculations for Benefits /PM0/ALT_CM_* Depending on the benefit profile,

more benefit calculations are required.

Acknowledgement of Benefit

Contract Reengineering (ACCEPT)

/PM0/ALT_CM_EXECUTE_CTR_CHG

Execution of contract reengineering in FS-PM (example: Once retirement

age has been reached, a pension insurance contract is converted and

potential pension payments are calculated).

Resume Claim (RESUME)

/PM0/ABT_CM_GET_CHECK_DATA with evaluation of time stamp

EV_LAST_AMENDMENT_TS

( /PM0/ABT_CM_GET_AMEND_PROC )

In FS-CM the user can interrupt the processing of a claim and then

resume processing at a later point in time. When processing is resumed,

the system determines whether changes have been made to the

underlying contract in FS-PM in the interim period. If this is the case, the user is informed of this fact and can retrieve the current FS-PM data by

reloading the policy snapshot.

Reset Benefit Recognition (CANCEL_ACCEPTING)

/PM0/ALT_CM_CANCEL_BNFCASE

The benefit recognition can be reset by the user in FS-CM at a later point in time. This leads to a reset of the

contract engineering.

4.5.2.3 CLOSE Phase of the Claim Process

There is no interaction between Claims Management and SAP Policy Management in this phase.


April 2017 63

4.5.3 FS-PM: Generating a Claim

Claims in Claims Management can also be generated from FS-PM:

Inquiry Business Process: The end customer would like to know the surrender value of a life insurance policy. A processing clerk can create a claim/benefit case during the calculation.

Fast Inquiry - Policy: In the Contract subscreen, you can use the Create icon to create a claim/benefit case.

Claims can be changed in Claims Management from FS-PM:

Fast Inquiry: The claims that you can change are listed on the Claims TabStrip.

Claims of Claims Management can be displayed from FS-PM:

There is a Claims node under the Overview node in the navigation tree.

There is a list of claims that can be displayed on the Claims tabstrip in the Fast Inquiry - Policy function.

Central Access: It is possible to search for claims.


April 2017 64

4.5.4 FS-PM: Integration Customizing for Claims

4.5.4.1 General Settings

You make various basic settings for an interface in the Customizing activity Process Primary Settings for Interfaces to External Systems (see also the section on other interfaces in FS-PM). This Customizing activity is under Policy Management Integration.

The documentation for this Customizing activity contains more detailed information.

The most important settings that are defined here are as follows:

o Assignment of logical destinations:

You make the assignment in the Logical Destinations view for each external operational system. The destinations entered here need to have been defined beforehand using transaction sm59. To refine the assignment of authorizations you can specify the destinations for RFC calls (destination) and for calls from dialogs (dialog destination) separately. Identical entries can be made for both destinations, however, as is the case in sample Customizing.

o ONLINE/OFFLINE supply:

You also define here whether the relevant interface is to be supplied online or offline. In the case of online supply (the default setting) the relevant interface is called as soon as the application is released. In the case of offline supply, the task is performed by a batch job that must be started specifically for this purpose. The data for the interface is parked in the relevant interface table until the batch job is executed. This concept is applied consistently for all interfaces to external systems. For the interface to CM, this refers to the trigger for the creation of (scheduled) claims/benefit cases and changes made to existing claims/benefit cases in the context of annuity disbursement.

o Assignment of classes/deactivating the interface for test purposes:

In the Assign Classes to Logical Destinations view, you enter the classes that implement the relevant interfaces. You can also define the functional scope of the relevant interface here. Moreover you can also completely deactivate the relevant interface for test purposes.

4.5.4.2 Customizing Settings for the Claims Management Interface

The specific Customizing activities for the interface to FS-CM are in Customizing for Policy Management under Integration Claims Management FS-CM.

For more information, see the documentation for the individual Customizing activities.

4.5.4.2.1 Customizing Activity “Assign FS-CM Benefit Processing Profile to Product Module Groups”

This Customizing activity is used to assign the benefit profiles defined in FS-CM to the product module groups defined in FS-PM.

Definition of benefit profile from FS-CM: A benefit profile contains attributes for process control (such as the CD specification) and defines which claim types are permitted for processing a claim for a given contract.

The benefit profiles previously defined in FS-CM must be entered with the same names in this Customizing activity. The benefit profiles are defined in FS-CM under Claims Management Claim Settings for “Claim Without Product Customizing” Scenario Interface to Policy System Interface to FS-PM Benefit Processing Profiles. The following Customizing activities are available:

• Create Benefit Processing Profiles at Product Level

• Create Benefit Processing Profiles at Elementary Product Level


April 2017 65

• Create Benefit Processing Profiles at Coverage Category Level

The product module groups in FS-PM are defined under group dimension INTFSCMBEN (Integration FS-CM: Benefit processing profile) for the product model class PRODUKT and ELEMENTARPRODUKT.

Combination of Customizing with a BAdI:

The special feature of this Customizing activity is the combination with a BAdI: If a benefit profile cannot be assigned uniquely directly to one product module group but rather the assignment is dependent on other factors, you can use a BAdI to make the assignment. See also the Customizing activity BAdI: Determination of Comparison Value to Determine Benefit Processing Profile under Policy Management Integration Claims Management FS-CM Business Add-Ins (BAdIs) General Functions for FS-CM Interface. In this case, you assign an evaluation rule to a product module group rather than a benefit profile. This evaluation rule is the filter value for the BAdI for determining the comparison value, in other words, the return value of this BAdI is a comparison value. In the second level (Assign Comparison Value to Benefit Processing Profile view), you can now uniquely assign a benefit profile to this comparison value.

The corresponding benefit processing profile (at Contract Product level) was already sent to FS-CM with function module /PM0/ABT_CM_GET_CHECK_DATA. It was also sent when the policy snapshot was read (function module /PM0/ABT_CM_GET_CONTRACT_DATA), at contract level (ES_POLPR) and coverage (ET_COV).

4.5.4.2.2 Customizing Activity “Process FS-CM Incident Types”

In this Customizing activity, you enter all the incident types that have been defined previously in FS-CM, with their long texts, using the same names that were used in FS-CM. An incident type describes the incident that triggers a claim, for example burglary or death.

The incident types are defined in FS-CM in the Customizing activity Define Incident Types, under Claims Management Claim Settings for the scenario ‘Claim Without Product Customizing’.

4.5.4.2.3 Customizing Activity “Process FS-CM Causes of Loss”

In this Customizing activity you enter all of the causes of loss that have been defined previously in FS-CM, with their long texts, using the same names that were used in FS-CM.

A cause of loss describes the exact cause of a claim and enables you to define the incident type more closely.

The exact cause (of loss) can also be relevant for the benefit amount, for example whether a death (incident type Death) has been caused by an accident (cause Accident) or suicide (cause Death).

You define the causes of loss in FS-CM in the Customizing activity Define Causes of Loss or Claim under Claims Management Claim Business Settings Origin of Loss.

4.5.4.2.4 Customizing Activity “Assign Causes of Loss to Incident Types”

This Customizing activity is used to assign the causes of loss and incident types defined in the activities mentioned above to each other. In addition to these assignments, you also assign the following characteristics to these combinations of incident type and cause of loss:

o Unit-linked processing: Here you assign special business transactions of funds management that are used to determine the possible base value date types, funds data, and cash value.

o Processing: By assigning processing activities, you define which journal entries are written when the contract is restructured (reengineered) in the event of a benefit or claim


April 2017 66

o Lock reason: The lock reason assigned here is used by default if the benefit system sets a contract lock in in-force business management.

o Reversal reason: The assigned reversal reason is used to determine the end date and the settlement variant of subsequent premium receivables. These values are determined from the Customizing of the Reversal business process

4.5.4.2.5 Customizing Activity “Check Dependencies with Claims Management System”

In this Customizing activity, you can configure whether error messages or warning messages are output if there are certain dependencies to claims. You make these settings for each business process or special action and depending on the product. If error messages are output, no further processing is possible. Special actions are replacement business, product change and sales product change (fixed values for domain /PM0/ABD_CHECKACTION_CD, no Customizing). The business processes that can be selected here are also defined as fixed values for domain /PM0/ABD_CHECKBIZPRC_CD and are not defined in Customizing. The product dependency is determined by the group dimension INTFSCMCHK (Integration FS-CM: Dependency Check) for the product model class PRODUKT.

4.5.4.2.6 Customizing Activity “Assign Time Model Functions to Loss Event Type and Cause of Loss”

This activity is in Customizing for Policy Management under In-Force Business Management Basis Update Time Model.

In this Customizing activity, you define which loss event types and causes of loss are used for time model functions that start claims/benefit cases in the Claims Management system.

When executing a time model function of this type, the system reads this Customizing table and passes on the appropriate values to the interface of the claims system.

4.5.4.2.7 Customizing Activity “Define Journal Entries”

This activity is in Customizing for Policy Management under In-Force Business Management Basis Journal.

You can set the Benefit-Relevant Processing indicator for each journal entry in the Additional Information for Processing view.

In FS-CM there is a display function for unscheduled (irregular) contract changes made in FS-PM. FS-PM provides a service for determining the relevant journal entries. Here, the system only includes or displays journal entries for which this indicator has been set.

FS-CM uses the service /PM0/ABT_CM_GET_AMEND_PROC to generate this overview. The behavior of this services can be controlled using the export parameter IF_BNF_ONLY_FG (default value is TRUE.)


April 2017 67

4.5.5 FS-PM: Package and Central Modules for Claims Interface

4.5.5.1 Packages

The benefit/claims interface in FS-PM contains both the inbound and the outbound layer. This means that packages /PM0/ABT_CM (Basis), /PM0/ALT_CM (Life) and /PM0/APT_CM (P&C/Non-Life) contain modules that access the claims system, and modules that are called by the claims system.

In Claims Management, the explicit outbound package ICLL_POLICY_OUT contains modules that call the Policy Management services.

The Claims Management explicit inbound package ICLL_CLAIM_IN contains services that are called by the modules in Policy Management.


April 2017 68

4.5.5.2 Outbound: PM calls CM

All modules from Policy Management with write access to Claims Management must be qRFC-enabled. This is because this is the only way of achieving transaction security when several components interact in this way, and for performance reasons.

Action PM Outbound Module CM Inbound Module Comment

Create Claim/Benefit Case Annuity Disbursement

BAdI Implementation

/PM0/CL_ABT_CM_CRTBNF_REM

/PM0/IF_ABT_CM_CRTBNF_REM_BADI~CREATE_BENEFIT_BACKGROUND

(Package /PM0/ABT_CM)

ICL_CL_CREAT_REQ

(qRFC in package ICLL_CLAIM_IN)

This deals with the trigger of (scheduled) claims and changes made to existing claims/benefit cases in the context of annuity disbursement. The calls from FS_CM are made together using method /PM0/IF_AB_INT_APPROVE~PUT. The actual RFC call is in a BAdI in each case. The name of the outbound queue is simply the constant CM. If an error

occurs, all further processing is stopped. .

Change Claim/Benefit Case Annuity Disbursement

BAdI Implementation

/PM0/CL_ABT_CM_CRTCHG_REM

/PM0/IF_ABT_CM_CTRCHG_REM_BADI~SEND_CTRC


ICL_CTR_BEN_CHANGE_NOTIF

(qRFC in package ICLL_CLAIM_IN)

If the deferral period for an annuity insurance is expired and an annuity is to be disbursed, FS-PM triggers the creation of a (scheduled) claim/benefit case, as described above. This claim/benefit case generates a periodic payment. However,

the amount of the pension to be disbursed can increase over time due to dividend allocation. This increase is determined by FS-PM during the update. The change to the pension

amount must be made in FS-CM. In doing so, the existing claim/benefit case in FS-CM is changed in each case.

However, the claim/benefit case is not changed explicitly. Instead, FS-CM is informed that the underlying contract in FS-PM has changed. There is a corresponding service available for this in FS-CM, namely the function module

ICL_CTR_BEN_CHANGE_NOTIF.

Further changes to the claim/benefit case are made by FS-CM independently in the background.

Jump to Claims

/PM0/CL_ABT_CM_JUMPCM_REM

/PM0/IF_ABT_CM_JUMPCM_REM_BADI~JUMP_CLAIMS


ICL_CL_CALL_EDIT

(Package ICLL_CLAIM_IN) BAdI for Encapsulation of Remote Call for jump_claims

Create Claim/Benefit Case Annuity Disbursement

Dialog

BAdI Implementation

/PM0/CL_ABT_CM_CRTBNF_REM

/PM0/IF_ABT_CM_CRTBNF_REM_BADI~CREATE_BENEFIT_DIALOG


ICL_CL_CALL_CREAT

(Package ICLL_CLAIM_IN) See above

Get Claim/Benefit Data

BAdI Implementation

/PM0/CL_ABT_CM_BNFINF_REM

/PM0/IF_ABT_CM_BNFINF_REM_BADI~GET_ALL_BENEFIT_INFO


ICL_CL_BY_ELEMENT

(Package ICLL_CLAIM_IN)

Enhancement spot /PM0/ABT_CM_CALLREMOTE_BADI_ES

In this case, the modules in the function groups /PM0/ALT_CM_FSPM2CM and /PM0/APT_CM_FSPM2CM that are not listed in the table are also relevant.


April 2017 69

4.5.5.3 Inbound: CM calls PM

All modules from Claims Management with write access to Policy Management must be qRFC -enabled. This is because this is the only way of achieving transaction security when several components interact in this way and for performance reasons.

Action CM Outbound Module/Class PM Inbound Module Fallback in FS-CM for Error

Handling/Comments

Acknowledgement of Benefit (Contract Reengineering)

CL_ICL_POLICY_RFC_OUT IF_ICL_POLICY_RFC_OUT~CTR_BEN_CALC_REQ

(Package ICLL_POLICY_OUT)

/PM0/ALT_CM_EXECUTE_CTR_CHG

(qRFC in package /PM0/ALT_CM)

ICL_CTR_BEN_CALC_CONF

(Package ICLL_POLICY_IN)

Reset Benefit Acknowledgement

CL_ICL_POLICY_RFC_OUT IF_ICL_POLICY_RFC_OUT~ALT_CM_CANCEL_BNFCASE


/PM0/ALT_CM_CANCEL_BNFCASE


ICL_CTR_CALC_CANCEL_CONF


Setting Contract Locks

CL_ICL_POLICY_RFC_OUT IF_ICL_POLICY_RFC_OUT~LOCK_CONTRACT


/PM0/ABT_CM_LOCK_CONTRACT

(qRFC in package /PM0/ABT_CM)

ICL_CTR_CL_ASSIGN_CONF


Deleting Contract Locks

CL_ICL_POLICY_RFC_OUT IF_ICL_POLICY_RFC_OUT~UNLOCK_CONTRACT


/PM0/ABT_CM_UNLOCK_CONTRACT


ICL_CTR_CL_UNASSIGN_CONF


Generate Special Risk Notification

CL_ICL_POLICY_RFC_OUT IF_ICL_POLICY_RFC_OUT~CRT_SPEC_RISK_MSG


/PM0/ABT_CM_CRT_SPEC_RISK_MSG


ICL_RISK_MSG_CREAT_CONF


Generate Provisional Funds - Orders

CL_ICL_FUND_RFC_OUT

IF_ICL_FUND_RFC_OUT~GENERATE_ORDERS

(Package ICLL_FUNDS_OUT)

/PM0/ALT_CM_GENERATE_ORDERS


ICL_FUND_ORDER_CREATE_CONF

(Package ICLL_FUND_IN)

Search Help Policy Number

CL_ICL_POLICY_RFC_OUT

IF_ICL_POLICY_RFC_OUT~CTR_BY_ELEMENT


/PM0/ABT_CM_GET_POLICY_NR_DATA


The search helps from FS-PM can be integrated when a claim is created. There is a BAdI in FS-CM for this purpose that needs to be configured.

For an example, see Customizing for Claims Management under Claims Management ClaimTechnical SettingsInterface to Policy SystemBAdI: Call of Input Help for Policy Number and Contract Number

Technical Details

o Enhancement Spot ICL_POLICY_POV

o BAdI Definition BADI_ICL_POLICY_POV (Popup for Input Help for Contract Number)

o Interface IF_EX_ICL_POLICY_POV

See Class CL_IM_ICLL_POLICY_POV_FSPM

Search Help Contract Number


IF_ICL_POLICY_RFC_OUT~CTR_BY_ELEMENT


/PM0/ABT_CM_GET_POLPR_NR_DATA

(Package /PM0/ABT_CM) See above

Determine Policy Snapshot


IF_ICL_POLICY_RFC_OUT~CTR_BY_ID


/PM0/ABT_CM_GET_CONTRACT_DATA


Supplies data for current FS-PM policy to FS-CM. Also supplies data for FS-PM Customizing

Model Calculation


IF_ICL_POLICY_RFC_OUT~EXECUTE_MODEL_CALC


/PM0/ALT_CM_EXECUTE_MODEL_CALC

(Package /PM0/ALT_CM)

Correspondence is generated as part of the processing of a claim in FS-CM. In particular, in the case of a partial surrender, changed values (maturity benefit) need to be printed in the correspondence generated. In order to retrieve these values, FS-PM has to run a model calculation (comparable to the model calculation made in FS-PM in the Calculate Maturity Benefit business transaction of the Inquiry business process).

Pro Rata Share for an Annuity


IF_ICL_POLICY_RFC_OUT~GET_PRT_PENSION


/PM0/ABT_CM_GET_PRT_PENSION


FS-CM requires exact to-the-day values for the calculation of annuities and premium exemption. For example, for an OD annuity that is paid from the first day of occupational disability and not on a monthly basis). These modules belong to the Basis functions (and not the Life LoB) because


April 2017 70

there are also accident insurance policies that cover occupational disability, for example.

Pro Rata Share of a Premium Exemption


IF_ICL_POLICY_RFC_OUT~GET_PRT_PREM_WAIV


/PM0/ABT_CM_GET_PRT_PREM_WAIV

(Package /PM0/ABT_CM) See above

Determination of Premium Receivable

CL_ICL_CD_RFC_OUT

IF_ICL_CD_RFC_OUT~GET_PREM_LOAN_DATA

(Package ICLL_CD_OUT)

/PM0/ALT_CM_GET_PREM_LOAN_DATA

(Package /PM0/ALT_CM)

The optional import parameter End Date of Premium Receivable (IV_PREMCOLLEND_DT) in this function module must not be filled by the caller (FS-CM) in this

case, because otherwise the date transferred here would overwrite the date that has been determined from

FS-PM Customizing.

When a claim/benefit case is created, FS-PM sends FS-CM the current premium balance (for each premium payer). This value is displayed as an offsetting item in FS-CM. If required, FS-CM clears a negative premium balance, meaning that any open items are taken into consideration by FS-CM and are subtracted from the disbursement amount. The clearing is performed by FS-CM automatically in FS-CM, without FS-PM. A unique feature is the case of a premium receivable. Here you need to determine up to which point in time a premium is to be requested if a contract is ended by a claim. This information is controlled by the Customizing settings in FS-PM.

• In the specific Customizing for the FS-CM interface, you can assign a reversal reason for every combination of loss incident and cause of loss.

• These reversal reasons have already been defined in the Reversal environment.

The reversal processing parameters used to determine the end date of the receivable are defined in the reversal reason.

The basic settlement variants have been defined and the individual reversal reasons have been assigned in Customizing. A settlement variant defines whether and in which form premium receivables are to be billed to the policyholder when a contract is reversed.

When the settlement variants are defined, a class is entered that implements interface /PM0/IF_ABP_BPU_CANC_VAR. This class uses the method EXECUTE_VARIANT to calculate the reversal documents. Note: GET_PREM_LOAN_DATA only simulates the generation of documents. The real receivable postings are made during contract reengineering.

Jump to Policy Summary

CL_ICL_POLICY_MAP_OUT

CTR_POLICY_JUMP


/PM0/ABT_CM_CALL_PM_DISCLOSURE


In this case, the modules in the function groups /PM0/ABT_CM_CM2FSPM, /PM0/ALT_CM_CM2FSPM, and /PM0/APT_CM_CM2FSPM that are not listed in the table are also relevant.

4.5.5.3.1 Import Parameter IF_UPDATE_TASK

Some of the write qRFC function modules mentioned above have the import parameter IF_UPDATE_TASK. This indicator can be used by the caller to decide whether the Commit task should be performed immediately, or whether the system should wait for an explicit Commit (function module BAPI_TRANSACTION_COMMIT).

The function modules for setting and deleting contract locks do not have this option.

Comments:

It does not make sense to combine this function with the qRFC call.

This explicit Commit option is not currently used by FS_CM.


April 2017 71

4.5.5.3.2 Contract Locks

During the processing of a claim/benefit case, you want to prevent “damaging” changes being made to the contract in FS-PM at the same time. Therefore, the processing of a contract in FS-PM (for example by the Change business process) is to be prevented if there is a claim/benefit case for this contract that has not executed contract reengineering. From a business point of view, this type of lock can be put in place for a longer period, for example, if a claim/benefit case is open for a period of months due to litigation. However, during this period it must be possible to carry out “non-damaging” actions in FS-PM, such as an update due to premium collection. The requirement for a contract lock can be set explicitly by the processing clerk during the processing of the claim in FS-CM. If the Customizing settings have been set up accordingly, however, FS-CM sets the lock automatically when a claim is created. This lock then prevents the contract from being processed further in FS-PM. For example, no further business processes can be started for the contract (the system issues an error message).

You can use one of the Customizing settings described below to define that certain business processes can be run despite the lock and that others are not permitted. If the Change business process is permitted it is also possible to make customer-specific adjustments to individual business transactions that can be executed, despite the lock. Only these business transactions can be selected in the context menu for the navigation tree. None of the other transactions can be started.

In the Customizing activity Assign Cause of Loss to Incident Types, you can enter a lock reason for a combination of loss incident type and cause of loss. The underlying lock reasons themselves are defined in the Policy Management Customizing activity Define Lock Reasons. This is under Policy Management In-Force Business Management Basis Business Processes Definition of Facts.

Example from Sample Customizing:

o The incident type Surrender (LBTS) is assigned to lock reason1 (Lock Due to Benefit Processing).

o This lock reason indicates that although a contract lock is in place, the business processes background processing, Update, and Change can be executed.

o In the Change business process, only the Change Beneficiary and Change Creditor business transactions are possible.

If a lock reason is entered in Customizing for the current incident type/cause of loss, this lock is set by FS-CM automatically when the claim/benefit case is first saved. The Claims processing clerk does not have to set the lock explicitly (but can do so independently of the Customizing).

Deletion of locks: The processing clerk in FS-CM can explicitly delete a lock at any time. The contract lock can be removed when contract reengineering is run. To do so, the indicator IF_UNLOCK_CONTRACT (Delete Contract Lock) must be set in function module /PM0/ALT_CM_EXECUTE_CTR_CHG. The call from FS-CM does this. An explicit deletion of the lock by the user is then no longer required. When benefit acknowledgement is reset, the status of the benefit acknowledgment in terms of possible contract locks is restored. This means, for example, that a contract lock set before contract reengineering is set again by the reset of the contract reengineering. The lock information can be transferred to the function module for resetting contract reengineering for this purpose.

Dependency Checks

Contract changes in FS-PM and claims/benefit cases in FS-CM are extremely interdependent. Parallel changes can be avoided to the largest possible extent using the locks described above but this is not sufficient from a business point of view. A dependency check has been defined to


April 2017 72

ensure consistency in processing in FS-PM and FS-CM. This check is part of the FS-CM interface. It is called at several points in FS-PM (at the start of a business process, for example) and checks whether the action is permitted from this perspective. If it is not permitted, the system generates an error message accordingly, stating that the action cannot be executed. Moreover, a warning message in FS-PM informs the user about open claims, even in cases where the action is possible in theory.

The following type of messages are created:

o Open claim/benefit case <claim number> exists for contract <number> on <date> (processor: <user>)

o Processing of contract <number> not possible due to open claim

You define which business processes can be executed for a claim/benefit case, despite the dependency recognized by the system, in the FS-PM Customizing settings for the FS-CM interface. Here you can specify whether an error message or merely a warning message is to be output if a dependency has been recognized for the Change, Universal Change, Reversal, Reset, Benefit and Background Processing business processes. If an error message is output, the user is not able to complete the action, whereas if the system outputs a warning message, the user can continue. In addition to these business processes, you can also select the special business transactions or actions Replacement Business, Product Change, and Sales Product Change. These business processes are predefined, however (fixed values for domains, not Customizing). The settings in the Sample Customizing are set restrictively, meaning that numerous actions cannot be executed and error messages are provided for these actions accordingly. This ensures, for example, that if the Reversal business process or the Replacement Business, Product Change, or Sales Product Change actions are executed on a date before the claim/benefit case has been created, the basis for an open claim/benefit case is withdrawn.

The check itself is run by method /PM0/IF_ABT_CM~CHECK_CLAIMS. The claims/benefit cases belonging to a contract are determined using service /pm0/if_abt_cm~get_all_benefit_info. It considers both claims/benefit cases that already exist in FS-CM and the claims that have been scheduled by the FS-CM interface. For example, the case may arise that FS-PM has created a (scheduled) claim as the result of an update but this has not yet been created in or transferred to FS-CM. The actual checks are made in methods /PM0/IF_ABT_CM~CHECK_EXISTING_CLAIMS and /PM0/IF_ABT_CM~CHECK_PLANNED_CLAIMS. The system checks whether open claims/benefit cases exist on the one hand and if in specific cases contract reengineering has taken place on the other. The system outputs messages accordingly. The Customizing settings determine whether the message is output as a warning or an error. For certain cases the calling application must set an indicator (IF_CHK_OPEN) to ensure explicitly that the Customizing information is used and that a warning message is not output by default.

Within method /PM0/IF_ABT_CM~CHECK_EXISTING_CLAIMS, the following methods for the same interfaces are called:

CHECK_CANCEL_CLAIM Checks the reversal of a claim/benefit case

GET_CHECKLOGIC_CUST_BP Determines the check logic for claims (business processes)

GET_CHECKLOGIC_CUST_AC Determines the check logic for claims (actions)

4.5.5.3.3 Integration of FS-PM Search Helps in Claims Management

The search helps from FS-PM can be integrated when a claim is created. There is a BAdI in FS-CM for this purpose that needs to be configured.

For example, see Customizing for Claims Management under Claim Technical Settings Interface to Policy System BAdI: Call of Input Help for Policy Number and Contract Number.

Technical Details:

o Enhancement Spot ICL_POLICY_POV


April 2017 73

o BAdI definition BADI_ICL_POLICY_POV (BAdI: Popup for Input Help for Contract Number)

o Interface IF_EX_ICL_POLICY_POV

o There are three classes that need to be implemented for this in FS-CM:

o CL_IM_ICL_POLICY_POV_DEMO

o CL_IM_ICLL_POLICY_POV_FSPM (important)

o CL_IM_ICL_POLICY_POV_FSPM

4.5.5.4 Enhanceability

4.5.5.4.1 Return Structures - Basics

All structures that return the various function modules as exporting parameters to the calling application contain identical structures. The parameter ES_POLPR (parameter to return contract data of function module /PM0/ABT_CM_GET_CONTRACT_DATA) is an example of this structure. This function module determines the FS-PM data for the policy snapshot in FS-CM.

4.5.5.4.1.1 Specific Structures for the CM Interface

Specific structures have been defined for the CM<->PM interface, in this example the structure /PM0/ABD_CM_POLPR_E (Cross-LoB Contract Structure for Benefit Interface). The existing structures in FS-PM have not been reused, for example the corresponding UBOI structure /PM0/ABWAPOLPR or the corresponding contract entity /PM0/ABDAPOLPR are not used in the example.

This means that, over time, newly added attributes from FS-PM are not automatically contained in the specific structures of the CM interface. These must be included explicitly. The attributes for these specific CM structures have the same names as the attributes in the corresponding FS-PM structures, however.

4.5.5.4.1.2 Includes

The individual attributes of the export interface structure are structured by various includes in a specific form:

Initial separation into includes for Basis, Life and P&C

In the example of the structure /PM0/ABD_CM_POLPR_E mentioned above, these are the following includes:

o /PM0/ABD_CM_POLPR (Cross-Contract Structure for CM Interface)

o /PM0/ALD_CM_POLPR (Life Contract Structure for CM Interface)

o /PM0/APD_CM_POLPR (P&C Contract Structure for CM Interface).

Separate include for enhancements for each FS-PM release

New attributes that have been added during the subsequent development period are not included in the respective LoB includes. This type of later enhancement has been created in a new separate include. The enhancements in release 4.5 are contained in the example in the include /PM0/ABD_CM_POLPR_E_FSPM45 (Component Enhancement FSPM 4.5 CM Interface).

This type of release include can contain both attributes for the basis as well as specific LoB-specific attributes for Life and P&C. It is not subdivided further.


April 2017 74

All these structures are categorized as ‘Cannot be Enhanced’. This means that you cannot attach additional customer attributes to these structures using Append technology. This restriction represents an important difference between the CM interface and the interfaces to other operational systems. It is due to the resulting additional security during upgrades.

4.5.5.4.2 Enhancement Using Parameters EXTENSIONIN and EXTENSIONOUT

However, other concepts are available for making customer enhancements and these are described below.

If you would like to transfer additional parameters to the service function modules or receive additional parameters, you can use the table parameters EXTENSIONIN and EXTENSIONOUT.

These are of the type BAPIPAREX (Reference Structure for BAPI parameters EXTENSIONIN/EXTENSIONOUT), and have the following structure:

o STRUCTURE CHAR 30 Structure name of the BAPI Table Extension

o VALUEPART1 CHAR 240 Data part for the BAPI extension parameter




It is possible to perform a generic data transfer with this SAP standard mechanism.

4.5.5.4.3 Enhancement Options for Services Using Entry and Exit BAdIs

The enhancement options using Entry and Exit BAdIs are used by the function modules that can be called by FS-CM but can also be found in some methods that are called by FS-PM.

Every function module contains an Entry and Exit BAdI, the structure of which is described below. The only exceptions are those services or function modules that only read Customizing tables from FS-PM and return this data. These services cannot be enhanced in this way.

Each of these BAdIs implement two methods: SERVICE_ENTER and SERVICE_LEAVE.

The following description has been taken from the interface or method documentation:

o SERVICE_ENTER: The method is called at the start of the service function module <name of function module> after the prerequisites have been checked. It enables you to run additional checks. The EXTENSIONIN parameters can be evaluated for this.

o SERVICE_LEAVE: This method is called at the end of the service function module <name of function module>. It lets you add further functions to the function module and adjust the output parameters. The EXTENSIONOUT parameters can be evaluated for this.

The import parameters for the underlying function module and the EXTENSIONIN structures are transferred to the call of the method SERVICE _ENTER at the start of the function module coding. The EXTENSIONOUT parameter can now be filled by the customer using changing parameters.

The procedure is similar when the SERVICE_LEAVE method is called at the end of the function module coding. Like the SERVICE_ENTER method described above, this receives the same input parameters as the underlying function module. The customer can use changing parameters here again to change all return parameters (exporting) for the actual function module. The EXTENSIONOUT parameters can also be changed here again.

In Customizing for Policy Management, there are 28 of these BAdIs under Integration Claims Management FS-CM Business Add-Ins (BAdIs) Enhancements for RFC Function Modules (Entry and Exit BAdIs).


April 2017 75

There are no sample implementations for these BAdIs; they are only used for customer-specific enhancements. One exception is the SERVICE_LEAVE method of the function module /PM0/ABT_CM_GET_AMEND_PROC. This function module provides information about changes (processing at journal level) for a transferred contract and/or the relevant policy.

This implementation of the BAdI definition /PM0/ABT_CM_GETAMDPRC_BADI is executed by class /PM0/CL_ABT_CM_GETAMNDPRC. In the standard system, journal entries that have already been reversed would also be returned. This active implementation filters these entries out.

The concept of these entry/exit BAdIs has not only been applied to function modules but also to certain class methods. However, in this case there are no EXTENSIONIN-EXTENSIONOUT parameters.

Sample code for the enhancement of the function module /PM0/ABT_CM_GET_CONTRACT_DATA. The BAdI /PM0/ABT_CM_GET_CTRDAT_BADI from enhancement spot /PM0/ABT_CM_BADI_ES has been used for this (the corresponding Customizing activity is BAdI: Data Determination for Contract Snapshot). This code implements the SERVICE_LEAVE method and concentrates on the example determination of data. The transfer of data to the calling method using EXTENSIONOUT (from type BAPIPAREX) is not shown here.

method /PM0/IF_ABT_CM_GET_CTRDAT_BADI~SERVICE_LEAVE.

DATA:

lr_ctxt TYPE REF TO /pm0/if_abt_cm_ctxt,

lr_log_handler TYPE REF TO /pm0/if_abt_cm_log_handler,

lv_apl_dt TYPE /pm0/abd_realeffectivity_dt,

ls_policy TYPE /pm0/abdapolicy,

ls_polpr_key TYPE /pm0/abvapolpr,

ls_polpr TYPE /pm0/abwapolpr,

lt_polpr TYPE /pm0/abwapolpr_t.

lr_ctxt = /pm0/cl_abt_cm_ctxt=>/pm0/if_abt_cm_ctxt~get_instance( ).

lr_log_handler = /pm0/cl_abt_cm_log_handler=>get_instance( ).

CALL METHOD /pm0/cl_abt_cm_util=>validation_policy

EXPORTING

iv_policy_nr = is_read_pm_key-policy_nr

iv_polpr_nr = is_read_pm_key-polpr_nr

if_incl_apl_fg = abap_true

IMPORTING

es_policy = ls_policy.

IF ls_policy-bo_cd = lcl_constants=>gc_bo_cd_policy.

* load policy over context

CALL METHOD lr_ctxt->get_polpr_key

EXPORTING

is_pm_cm_key = is_read_pm_key

if_disclosure_fg = if_disclosure_fg


April 2017 76

IMPORTING

es_polpr_key = ls_polpr_key

ev_apl_dt = lv_apl_dt.

ELSEIF ls_policy-bo_cd = lcl_constants=>gc_bo_cd_application.

* clear log

lr_log_handler->clear_fspm_log( ).

* load application by context

CALL METHOD lr_ctxt->get_last_polpr_key

EXPORTING

is_pm_cm_key = is_read_pm_key

IMPORTING

es_polpr_key = ls_polpr_key

ev_apl_dt = lv_apl_dt.

MESSAGE w111(/pm0/abt_cm_message)

INTO /pm0/cl_3ft_registry=>gv_message.

/pm0/cl_3ft_registry=>gr_tk_logger->new_message( ).

ENDIF.

*----------------------------------------------------------------------

* get the entity data...

*----------------------------------------------------------------------

CALL METHOD lr_ctxt->gr_egos_get_polpr->get_polpr

EXPORTING

is_sec = ls_polpr_key

IMPORTING

et_polpr = lt_polpr.

LOOP AT lt_polpr INTO LS_POLPR.

ENDLOOP.

endmethod.

4.5.5.5 Classes in the Claims Interface

Class Overview Diagram in Policy Management for Claims Interface:


April 2017 77

+cross_service1()

+cross_service2()

+cross_service3()

+...()

+...()

+cross_serviceN()

+life_service1()

+life_service2()

+life_service3()

+...()

+...()

+life_serviceN()

«interface»

/PM0/IF_ALT_CM

+cross_service1()

+cross_service2()

+cross_service3()

+...()

+...()

+cross_serviceN()

+p&c_service1()

+p&c_service2()

+p&c_service3()

+...()

+...()

+p&c_serviceN()

«interface»

/PM0/IF_APT_CM

/PM0/CL_ALT_CM /PM0/CL_APT_CM

+cross_service1()

+cross_service2()

+cross_service3()

+...()

+...()

+cross_serviceN()

«interface»

/PM0/IF_ABT_CM

/PM0/CL_ABT_CM

Implementing Classes for Interface /PM0/IF_ABT_CM

/PM0/CL_ABT_CM

Cross-Services for Claims Interface (PM->CM)

/PM0/CL_ABT_CM_NONE Dummy Class to Deactivate CM Interface

/PM0/CL_ABT_CM_FIXVAL Simulation for Cross-Services for Claims Interface

/PM0/CL_ABT_CM_SWITCH Switch for Cross-Services for Claims Interface

The classes NONE, FIXVAL, and SWITCH are used to deactivate the interface.

The Basis class /PM0/CL_ABT_CM also implements the interface /PM0/IF_AB_INT_APPROVE (interface for release procedure for interfaces to all operational systems). Some of these methods contain Entry and Exit BAdIs for individual customer enhancements. The interfaces /PM0/IF_ABT_CM and /PM0/IF_ALT_CM define which methods/services can be offered. Here it makes sense to evaluate the options currently available in the system. Note that this guide does not contain a complete list of all classes and methods.

4.5.5.5.1 General Information About BAdIs in the Claims Environment

The CM interface contains five enhancement spots:

The Basis and the Life and P&C LoBs each contain a general enhancement spot with the name XXX_CM_BADI_ES: /PM0/ABT_CM_BADI_ES for Basis, /PM0/ALT_CM_BADI_ES and /PM0/APT_CM_BADI_ES for Life and P&C. However, the enhancement spot for the P&C LoB is a dummy; it currently does not contain any P&C-specific BAdI definitions.

An additional enhancement spot for the Basis is /PM0/ABT_CM_CALLREMOTE_BADI_ES. This encapsulates all calls that are directed to a remote system.

For the Life LoB, the enhancement spot /PM0/ALT_CM_CALC_BADI is used to call insurance mathematics methods for calculations.


April 2017 78

These enhancement spots contain more than 40 BAdI definitions. However, this large figure includes several Enter and Exit BAdIs. This type of BAdI is currently part of the enhancement spots /PM0/ABT_CM_BADI_ES and /PM0/ALT_CM_BADI_ES.

In addition to the information below, see also the following sources of information:

The documentation for the associated Customizing activity

The documentation for the interface assigned in each case. This is available in some cases.

The documentation for the relevant interface method (navigate to the methods, then in the menu choose Goto Documentation for the component). This is available in most cases.

4.5.5.5.2 Customizing BAdIs for CM

Various BAdIs are available for the user (or for customer implementers) in Customizing for Policy Management under Integration Claims Management FS-CM Business Add-Ins (BAdIs).

There are four subcategories:

Enhancements for functions for in-force business management

General functions for CM interface

Remote calls to benefit system

Enhancements for RFC function modules (Entry and Exit BAdIs)

These BAdIs are not separated by lines of business, in other words Basis and LoB BAdIs are mixed here.

4.5.5.5.3 Enhancement Spots

This guide does not describe the individual BAdI definitions and implementations.

These can be found in the system for the individual enhancement spots:

o /PM0/ABT_CM_BADI_ES

o /PM0/ALT_CM_BADI_ES

o PM0/APT_CM_BADI_ES

o /PM0/ABT_CM_CALLREMOTE_BADI_ES: This encapsulates calls that are directed to a remote system.

o /PM0/ALT_CM_CALC_BADI_ES: This calls insurance mathematics methods for calculation.


April 2017 79

4.6 FS-PM<->FS-RI (Reinsurance)

Reinsurance is used by the primary insurer to reduce underwriting risk. The default risk of large loss and claims cost to the primary insurer can be minimized by reinsuring the insurance.

For this purpose, accumulations (aggregations) for values for the various coverages and contract modules/ subcoverages are formed in FS-PM. These accumulations group similar risks. The accumulations can be formed at contract level or higher, however the basis for the accumulations are the RI documents that contain selected information about the coverage or subcoverage level.

A primary insurer has insured all luxury villas at the beach of Fort Lauderdale. A hurricane could affect all the luxury villas. In this respect, it makes sense to accumulate the values of all the luxury villas from the various policies and to reinsure this value.

The object liability total is calculated from the insured objects affected, and the accumulation with the required data is provided to the reinsurance system.

For facultative reinsurance, both parties involved can freely decide about the cession and acceptance of risks. The primary insurance company can choose whether, to what extent, and to which reinsurance company it wants to cede an assumed risk. The reinsurance company can decide whether it accepts the risk offered, whether it is only prepared to assume parts of the risk, or whether it rejects the risk entirely. Unplaced risk exists if the liability of the cession group has not been fully distributed to ceded reinsurance treaties and the retention after automatic cession calculation or manual assignment of reinsurance treaties. To allocate the unplaced risk, you can either increase the retention, or assign it to a facultative reinsurance treaty. To cede the unplaced risk to a ceded reinsurance treaty, create an additional ceded participation for the group, and assign this participation to the treaty (manual cession). Check in advance when you want to use coinsurance and when reinsurance.

4.6.1 FS-RI: Master Data / Accumulations


April 2017 80

Data is sent in the form of accumulations from FS-PM to FS-RI using qRFCs. A separate call has to be made for each accumulation. The sent accumulation data can be processed as follows:

In the FS-RI Basis System

In FS-RI Risk Manager Non-Life

Not at all (because the data is not relevant)

This decision is made by the routing engine based on dynamically determined information from FS-PM.

The information is compiled in Policy Management using the structural characteristics from FS-RI: Currency, reinsurance class of business (COB), reinsurance line of business (LOB), reinsurance area, business type (TOB). The structural characteristics are used to find the portfolio sections. From there, the system can determine whether the data is to be moved to and processed in Risk Manager Non-Life, the Basis system, or not at all.

The Basis System is used for obligatory reinsurance if the total risk is relevant and only premium data is required.

In the Basis system, you will find entities such as the reinsurance treaty, business partner, and so on. This data is not relevant for the Policy Management system. A reinsurance treaty in the FS-RI system maps a relationship between two or more business partners in the reinsurance business. The treaty details the partners involved according to the type and extent of their participation and liability; it also describes the structure of the portfolio covered by the treaty. For the sake of completeness, the following describes the entities of the FS-RI Basis System:

The Header Data contains all treaty data that is independent of the period. You can branch from the treaty header to the individual periods of the treaty. Periods divide the treaty into time periods. The hierarchy below the periods contains information about the treaty specifications (for example, sections, participations, conditions, and partners involved, which may vary from period to period). You define the area of validity of the treaty under Sections by entering information such as classes of business, areas, business types, currencies, and lines of business. Under Participations, you define the share of the treaty held by the various business partners involved and linked treaties. You can enter insurance-specific conditions, such as profit commission, under Conditions.

The Risk Manager Non-Life system is used to reinsure individual risks (for buildings, for example) for which accumulation data is required. Risk Manager (RM) is an optional FS-RI component that enhances the Basis System to include functions for managing single risks (policies) and accumulations, and for processing the corresponding accounts. Risk Manager can be used only in conjunction with the Basis System. Basis System functions are required in the following cases:

o If you use Risk Manager to map participation in a policy, you assign the participation to one or more reinsurance treaties in the Basis System. You assign ceded participations to assumed master treaties in the Basis System.

o Risk Manager cannot transfer postings directly to a current account system; this is always done via the Basis system.

o To structure the Risk Manager portfolio to create cession groups, you need to use a dummy treaty from the Basis system (portfolio treaty).

FS-PM uses Risk Manager Non-Life without replication. FS-RI enables replication of optional parts of the original policy data from the primary insurer.

An accumulation in FS-PM is structured as follows (see also section 4.6.4.2. Tables):


April 2017 81

An accumulation in FS-PM consists of n coverages or subcoverages, m time periods and k premiums. The relationship between coverage and structural characteristic is 1:1.

Accumulations in RI system: Accumulations are created as cession groups in FS-PM if they are stored in Risk Manager Non-Life of FS-RI. The structure characteristics of the accumulation are used to find the correct portfolio treaty section. BAPIs from the FS-RI P2R interface are used to transfer FS-RI information about accumulations from FS-PM. A cession group can be processed automatically (using a BAPI call) or manually (by processing clerk). The reinsurance is covered automatically by obligatory RI treaties or additional facultative coverage must be purchased.

4.6.2 FS-PM: Accumulation Formation

The basis for the accumulations are the RI documents that are determined in the Accounting component (/PM0/CL_AB_INT_AC) in the business component for Non Cash Flow for P&C in class /PM0/CL_APN_BCNCC_OBJLIM, method /PM0/IF_ABN_BCNCC_MASTER~ CREATE_DOCUMENTS. The object liability total for this is determined in the update process by evaluating the date OBJLMIT, for example.

Moreover, from Release 5.3 you can use class /PM0/CL_ALN_BCNCC_OBJLIM, which creates RI documents for the long-term product (multiple LoB insurance). In addition, there are new database fields in tables /PM0/ABDAPOLPR and /PM0/ABDACOV: BPML_AM (Absolute Manual PML), BPML_VL (Relative Manual PML), BRICHECK_FG (Manual Postprocessing), and BPML_TT (Manual Field Label for Amounts).

The object liability total is calculated based on the sum insured (for example field INSAMOUNT_AM in /PM0/APDACOV) and the PML factor (Probable Maximum Loss), either as a percentage or as an absolute PML amount:


April 2017 82

The PML can be defined either at contract level or at coverage level.


April 2017 83

In FS-PM, the accumulations for P&C products are determined based on coverage and subcoverage. The following accumulations can be formed from the bottom up:

o At coverage level, the values for the coverage options (subcoverages) are aggregated in method /PM0/CL_AB_INT_RI_HELPER=>COMPUTE_COV_PML.

o At contract level, the coverage values are aggregated in method /PM0/CL_AB_INT_RI_HELPER=>COMPUTE_POLPR_PML.

o At policy level, the values for the contracts are aggregated in method /PM0/CL_AB_INT_RI_HELPER=>COMPUTE_ POLICY _PML.

o At cross-policy level, the values for the policies are aggregated in method /PM0/CL_AB_INT_RI_HELPER=>COMPUTE_ INTER _PML.

For sales products with an obligation of reinsurance, the system checks whether coverage by reinsurance exists during the release procedure synchronously. The accumulations are determined in a BAdI. If the accumulation formation in the standard system does not meet your requirements, you can develop your own algorithms. Claims Management has an independent object “coverage type” that is assigned to the coverage in Policy Management. If you need a basis for communication between FS-PM, FS-RI, and FS-CM, then use the coverage level. FS-PM can send information about coverage and subcoverage to FS-RI as sections.

When you enter the insured object, you can assign a risk group number. The risk group number groups the insured objects that have a common risk.

A fire in a semi-detached house also threatens the adjoining house.

The same risk group number can be used for all policies.


April 2017 84

Commercial Policies - Limits

In addition to the PML, you can specify a limit value for commercial policies (there is a separate entity for this: /PM0/ABDALIMIT). When the object liability total is calculated, only the limits at contract and coverage level are taken into consideration.

This diagram demonstrates that for commercial insurance, the limits at coverage level do not affect the aggregation. At coverage level the limits did take effect and limited the object liability total for coverage 1 to 300,000.


April 2017 85

4.6.2.1 Rules for Accumulation Determination

You can define rules to control accumulation determination in Customizing. The RI documents form the basis for accumulation determination. See also the section on Customizing under In-Force Business Management -> Basis -> Accumulation Determination.

The insured objects of the coverages in the following example all have the same risk grouping number and the same update period.

According to the rules and Customizing settings, in this example the reinsurance lines of business 33 and 37 are aggregated at contract level to reinsurance line of business 37. LoB here refers to the reinsurance LoB. The sample values 33 and 37 are the LoB key. FS-RI contains a mapping for the P2R interface. In this example, this is the mapping for the “class of business” (not the LoB, which is also used as a term in FS-RI). The diagram shows the policy structure and the accumulation determination process (red dotted line). If the rule or LoB key are different, a different accumulation is formed. However, you can also define in Customizing, that at higher aggregate levels values from various LoB keys can also be aggregated. Note also that sections in the form of coverages and subcoverages continue to be transferred to FS-RI. The Customizing section explains how the reinsurance key and rules are defined based on the policy data.


April 2017 86

4.6.2.2 Processes with Potential RI Participation

In the dialog:

Standard processes without manual postprocessing for FS-RI. With the exception of checks to determine whether the accumulation is in-force in FS-RI, the application is released after successful RI checks and the RI data required is transferred to RI.

Manual RI Simulation:

During the processing of an application you can execute a RI simulation. You can display simulated accumulations in an overview (the display is similar to the RI inquiry). In the manual RI simulation, the result can differ to that of the RI simulation in the release.

Processes with manual postprocessing for FS-RI, that are triggered if:

o the Manual Postprocessing indicator is set at contract or coverage level, or

o the mandatory RI treaties are not sufficient and facultative cover is applied for.

When a new accumulation is created, the accumulation is created in Risk Manager Non-Life to allow for postprocessing. The FS-PM application is saved. Only when the accumulation has been postprocessed in the relevant cession group in FS-RI and the status has been set to In-Force, can application processing be resumed in FS-PM and the application released.

Reinsurance Inquiry

4.6.3 FS-PM: Integration Customizing

4.6.3.1 Setting Up Connection to RI System


April 2017 87

In the Customizing activity for Policy Management under Integration Process Primary Settings for Interfaces to External Systems, you have to enter the RFC destination for the RI entry:

4.6.3.2 Accumulation Determination

The main Customizing settings for accumulation determination are in Customizing for Policy Management under In-Force Business Management Basis Accumulation Determination. See also the documentation for the individual activities.

You determine the products that are subject to reinsurance in the Customizing activity Define Reinsurance Obligation.

You use the Customizing activities Define Risk Group Number Assignment for Product Module Groups, Define Derivations for Risk Group Numbers and the BAdI: Determine and Search for Risk Group No. (RGN) to determine the risk group number for the insured object. You make the settings for the product module groups for FS-RI in Customizing for Policy Management under Basis Basic Settings Define Product Module Groups using the group dimension INTFSRI.


April 2017 88

A previous section referred to the use of rules for accumulation determination. You can define these rules in the Customizing activity Define Rules for Accumulation Determination. You can define the line of business key in the Customizing activity Define Line of Business Key. You link these rules to the line of business keys in the Customizing activity Define RI Features for Elementary Product Group / Subcoverage Group. These rules are defined internally for FS-PM. The line of business keys are mapped for classes of business in the Customizing for the P2R interface. In the example in the previous section, liability totals for different line of business keys were aggregated to accumulations. This type of aggregation is defined in the Customizing activity Define Line of Business Combinations.


April 2017 89

4.6.4 FS-PM: Important Packages / Classes / BAdIs

Class /PM0/CL_AB_INT_RI is referred to as the RI adapter. It administrates the communication with a RI system that can be connected to FS-PM. BAdI /PM0/ABP_CUMUL_BUILD_BADI is used for accumulation determination with the default implementation /PM0/CL_DEF_IM_CUMUL_BLD_BADI. It is important that the accumulation determination and the RI interface are strictly separated. The accumulation determination should not contain RI-specific logic. This should only be found in the RI adapter. Class /PM0/CL_AB_INT_RI_HELPER is a toolkit class that is used for the entire RI interface.

The RI documents, which are created by the accounting component, form the basis for the accumulation determination. The RI documents are read at the start of accumulation determination by method READ_DOCS_FROM_AC from class CL_DEF_IM_CUMUL_BLD_BADI, for example.

The RI documents are stored in database tables /PM0/ABDNRIDOCH (RI document header) and /PM0/ABDNRIDOCI (RI document item). Table /PM0/ABDNRIDOCI contains the field INSAMOUNT_AM (liability sum is relevant if PML is not set), and two pairs of PML fields (PML_AM and PML_VL at contract level, and COVMANPML_VL and COVMANPML_AM at coverage level) however only one pair of fields can contain values. A special feature of this table is that it contains both liability total information and premium information (AMOUNT_AM).

Note that, during single contract processing, you may have to reload RI documents for other contracts, to ensure that the object liability total is determined correctly.


April 2017 90

If you are using SAP FS-RI, the actual qRFC call to FS-RI in the standard system is made in class /PM0/CL_DEF_INT_QRFC_RI_BADI in method /PM0/IF_EX_ABT_QRFC_RI_BADI~GET_REINSURANCE. The FS-RI modules /MSG/H_PAPI_RIACC_CREATE, /MSG/H_PAPI_RIACC_CHANGE, or /MSG/H_PAPI_RIACT_CREATEMULTIP are called here.

See the current system documentation for the /MSG/BAPI modules. The descriptions listed here are only meant as Quick-Info.

Module Call Type Description

/MSG/BAPI_RIACC_GETDETAIL Synchronous This module gets key date-related information for exactly one Risk Manager Non-Life accumulation. For example,

whether the accumulation is locked in FS-RI.

/MSG/BAPI_RIACC_CHECKCOVERAGE Synchronous

Executes RI simulation with FS-PM data. Indicates where the accumulation would be saved (Basic, Non-Life, not at

all), and the status of the accumulation (is there any unplaced risk requiring facultative cover, for example).

/MSG/H_PAPI_RIACC_CHANGE Asynchronous You can use this module to adjust accumulations that are

in Non-Life.

/MSG/H_PAPI_RIACC_CREATE Asynchronous This module is used to create an accumulation on FS-RI.

/MSG/H_PAPI_RIACT_CREATEMULTIP Asynchronous FS-PM data is created at section level of FS-RI in “pre-

accounts”.

The asynchronous calls are made by qRFC.


April 2017 91

4.6.4.1 Simplified Flow Chart

The following simplified flow chart focuses on the calls of the FS-RI modules and the underlying call hierarchy, for example, is the BAdI /PM0/ABP_CUMUL_BUILD_BADI also involved in the RI simulation (which is missing from the diagram below for the sake of clarity)?

At the start phase of the process, when the application is generated, the system checks whether the accumulation is in-force in FS-RI.

At the end phase of the process (release) the system first checks whether a release is possible and determines the RI status. If appropriate, a results screen appears in the dialog, displaying the data that is to be released. Analysis or decision-making on the part of the processing clerk can delay the final release, so the system always checks again to determine whether there were additional releases in the time between the generation of the results screen and the actual time of the release, which could affect a common accumulation (it is also possible that a lock has been set in the meantime). During the communication with FS-RI, all calls are read synchronously.

In the commit part of the release, the FS-RI interface is called with write access asynchronously.

4.6.4.2 Tables

The accumulations that are transferred to FS-RI are stored in the tables of the RI interface. FS-RI expects the data in a special format that requires it to know the previous status of the data.

The following tables belong to the RI interface tables (accumulation tables):


April 2017 92

/PM0/ABDTRIDATA: Contains header data for the accumulation.

/PM0/ABDTTRALLOC: Contains sections (coverage or subcoverage - field RIREF_ID) or subcoverages that are assigned to the accumulation. An accumulation is, in simple terms, a summary of multiple coverages or subcoverages.

/PM0/ABDTTRSPLIT: Contains the structure elements for the coverages and subcoverages. The structure characteristics are used by RI to find the corresponding RI treaty for an accumulation.

/PM0/ABDTTRSEQ: This table stores the time periods and liability totals. Each accumulation is assigned a total for a specific period (the actual liability totals for FS-RI).

/PM0/ABDTTRIPREM: Premiums for the individual coverages or subcoverages.

The tables are linked on the database using the (foreign) key field TRANSACT_CD. Sections from any policies can be assigned to an accumulation.

This is achieved by storing data at different levels:

Data storage at policy level: To avoid having to search through all policies and coverages in in-force business, the data is aggregated at policy level and stored in the accumulation tables (accumulation status_cd = C). At this level, all coverages /subcoverages that can be summarized according to the rules for accumulation are aggregated within the policy. When searching for accumulations across all policies, “only” the summarized internal policy data in the accumulation tables has to be used. This reduces the relevant data to a few records.

Cross-policy data storage: In addition to the storage within the policies, data is also stored for all policies (accumulation status_cd = I). You can get cross-policy data by summarizing the relevant intra-policy data.

Class /PM0/CL_AB_INT_RI_CUMUL_LOADER encapsulates the access to the databases using the following database agents:

• /PM0/CL_ABP_DAA_ATRIDATA

• /PM0/CL_ABP_DAA_ATRALLOC

• /PM0/CL_ABP_DAA_ATRSEQ

• /PM0/CL_ABP_DAA_ATRSPLIT

• /PM0/CL_ABP_DAA_ATRIPREM

4.6.4.3 BAdIs

You can access the documentation in Customizing for Policy Management under Integration Reinsurance FS-RI Business Add-Ins (BAdIs).


April 2017 93

BAdI /PM0/ABT_RI_MODIFY_DATA_BADI: BAdI: Change to RI Transfer Data You can change the data to be sent to FS-RI once again.

BAdI /PM0/ABD_RI_INQUIRY_BADI: BAdI: Enhancement to Reinsurance Inquiry You can go to the RI system using the RI Inquiry. This BAdI permits the functionality required for this.

BAdI /PM0/ABD_RI_NOTIFY_FACREQ: BAdI: Inform RI Processor You can use a workflow to inform the relevant RI processor of manual postprocessing requirements.

BAdI /PM0/ABT_QRFC_RI_BADI: BAdI: Adjust RFC Call This is the central update BAdI for calling the RI system. The SAP fallback class is /PM0/CL_DEF_INT_QRFC_RI_BADI.

Solution Management Guide Summary

April 2017 94

5 Summary SAP Policy Management provides flexibility in the supply of data to operational systems. Read access in the operational systems is synchronous, you must wait for the results from the operational systems. Write access is made asynchronously using qRFC because the sequence of data supply to the operational systems can be critical for subsequent processing and because synchronous background data processing could lead to significant performance issues.

The central entity for communicating on the insurance landscape is the contract, with the exception of FS-RI where it is the accumulation. However, every operational system has its own separate object management.

Important Operational Systems for SAP Policy … Management Guide Disclaimer April 2017 5 1...

Documents

Transcript of Important Operational Systems for SAP Policy … Management Guide Disclaimer April 2017 5 1...