sap policy management, group insurance add-on 1 · sap policy management, group insurance add-on...

Configuration Guide

Document Version: 1.1 – 2017-04-28

CUSTOMER

SAP Policy Management, group insurance add-on 1.1

2

CUSTOMER

© 2017 SAP SE or an SAP affiliate company. All rights reserved. SAP Policy Management, group insurance add-on

Typographic Conventions

Type Style Description

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

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

Textual cross-references to other documents.

Example Emphasized words or expressions.

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

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

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

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

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

database tools.

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

appear in the documentation.

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

with appropriate entries to make entries in the system.

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

SAP Policy Management, group insurance add-on

Document History

CUSTOMER

Error! Unknown switch argument. 3

Document History

Version Date Change

1.0 2017-04-28 First version of this guide

4

CUSTOMER

© 2017 SAP SE or an SAP affiliate company. All rights reserved.


Table of Contents

Table of Contents

1 Introduction .................................................................................................................................................... 7 1.1 About This Document ............................................................................................................................................. 7 1.2 Target Audience ...................................................................................................................................................... 7 1.3 Glossary .................................................................................................................................................................... 7

2 Solution Overview .......................................................................................................................................... 8

3 Implementation and Configuration ............................................................................................................. 9 3.1 Activating the Group Add-On ................................................................................................................................. 9 3.2 Enhancing Master Policy ....................................................................................................................................... 10

3.2.1 IFBC Application .................................................................................................................................... 10 3.2.2 Generic Entity for Master Policy Business Object .............................................................................. 11 3.2.3 Update Run from Master Policy ............................................................................................................ 11

3.3 Enhancement of Master Policy ............................................................................................................................ 12 3.3.1 Premium Payer Distribution ................................................................................................................ 12 3.3.2 Creditor .................................................................................................................................................. 13 3.3.3 Beneficiary ............................................................................................................................................. 14 3.3.4 Collection Types (Broker) .................................................................................................................... 15 3.3.5 Premium Per Piece ............................................................................................................................... 16 3.3.6 Commission Participant ....................................................................................................................... 17 3.3.7 Multiple Master Policy Partner ............................................................................................................ 18 3.3.8 Surcharge/Discount On Master Policy ............................................................................................... 18 3.3.9 Clauses On Master Policy ..................................................................................................................... 19 3.3.10 Valid-To Date Defaulting ......................................................................................................................20 3.3.11 Central Access For Master Policy ........................................................................................................ 22 3.3.12 Master Policy Tree ................................................................................................................................ 23 3.3.13 Distribution Plan On Master Policy ...................................................................................................... 25 3.3.14 Deductibles On Master policy .............................................................................................................. 26 3.3.15 Limits On Master policy ........................................................................................................................ 29 3.3.16 Premium Payer Distribution ................................................................................................................ 32 3.3.17 Premium Per Piece ............................................................................................................................... 34

3.4 Enhancement Of Master Policy Functionality ..................................................................................................... 36 3.4.1 Copy Of Master Policy .......................................................................................................................... 36

3.5 Enhancement Of Result Set.................................................................................................................................. 36 3.5.1 Change Document ................................................................................................................................ 36

3.6 Define Master Policy Module ID ........................................................................................................................... 36 3.6.1 Define and Maintain Master Policy Module ID .................................................................................... 36 3.6.2 Define Organizational Level Assignment Type ................................................................................... 39 3.6.3 Define Organizational Assignments on Master Policy ....................................................................... 39

3.7 Master Policy - Overview of Open Applications ................................................................................................. 40 3.7.1 Selection Options Overview Cockpit .................................................................................................. 40

3.8 External Date - Derivation of Master Policy Data ............................................................................................... 42 3.8.1 Beneficiary Derivation .......................................................................................................................... 42 3.8.2 Multiple Master Policy Partner Derivation .......................................................................................... 43


Table of Contents

CUSTOMER

Error! Unknown switch argument. 5

3.8.3 Clause Derivation ................................................................................................................................. 45 3.8.4 Coinsurance Derivation ....................................................................................................................... 46 3.8.5 Collection Type Derivation .................................................................................................................. 48 3.8.6 Creditor Derivation ............................................................................................................................... 49 3.8.7 Multiple Master Policy Partner Derivation .......................................................................................... 51

3.9 Configuration of Surcharge/Discount TMF........................................................................................................ 52 3.9.1 Business Component ‘445’ ................................................................................................................. 53 3.9.2 Maintain Standard Implementation for Business Component ........................................................ 53 3.9.3 Define Journal Entries .......................................................................................................................... 54 3.9.4 Create New Dates for Time Model Function ...................................................................................... 54 3.9.5 Configure Time Model Function in SPRO ............................................................................................55 3.9.6 Define Execution Criteria for Time Model Function ...........................................................................55

3.10 Business Process: Mass-enablement of Business Transactions ..................................................................... 56 3.10.1 Mass Exclude Coverage ....................................................................................................................... 56 3.10.2 Mass Change Beneficiary ..................................................................................................................... 57 3.10.3 Mass Change Creditor ......................................................................................................................... 58 3.10.4 Mass Change Execute Manual Rating ................................................................................................ 59 3.10.5 Mass Perform Premium Waiver .......................................................................................................... 60 3.10.6 Mass Process Premium Waiver ........................................................................................................... 61 3.10.7 Process Coinsurance ............................................................................................................................ 61 3.10.8 Change Commission Participant ........................................................................................................ 62 3.10.9 Perform Additional Payment ............................................................................................................... 63 3.10.10 Mass Enable Relocation of Policies .................................................................................................... 64 3.10.11 Mass Enable Renewal Preparation ..................................................................................................... 65 3.10.12 Mass Enable Renewal Decision ........................................................................................................... 66

3.11 Mass Processing of Open Policy Applications ....................................................................................................67 3.11.1 Mass Processing ...................................................................................................................................67

3.12 Configuration of Master Policy Template for Multiple Mass Change Locking ................................................ 68 3.12.1 Master Policy Template Configuration ............................................................................................... 68

3.13 Execute Mass Change for a Specific Mass Change ........................................................................................... 69 3.13.1 Authorization for Using the Functionality .......................................................................................... 69

3.14 Dual Control for Mass Change ............................................................................................................................. 69 3.14.1 BADI to Activate the Dual Control....................................................................................................... 69 3.14.2 Workflow Checks .................................................................................................................................. 70

3.15 Mass Change BTX New State / Update State Operation ................................................................................... 71 3.16 Group Discount Dependent on Number of Objects ............................................................................................ 72 3.17 Correspondence .................................................................................................................................................... 73

3.17.1 Correspondence Request for Master Policy ....................................................................................... 73 3.17.2 Recurring Correspondence on Master Policy ..................................................................................... 75 3.17.3 Automatic Scheduling of Correspondence at Master Policy ............................................................76

3.18 Selection of Policies Within Given Master Policy ................................................................................................ 77 3.19 Premium Simulation on Master Policy................................................................................................................. 77

3.19.1 Commission Participant Derivation .....................................................................................................78 3.20 Simulation of Mass Run ........................................................................................................................................ 80

3.20.1 BAdI /PMG/GE_ABG_MASS_SIMU_BADI: Determine package size for Mass

Simulation ............................................................................................................................................. 80 3.21 Business Process: Reversal of Mass Change ..................................................................................................... 80 3.22 Change Policy Using File Upload .......................................................................................................................... 81 3.23 Service Enablement for Master Policy and Sample Application ...................................................................... 82

3.23.1 Read Custom Master Policy Entities .................................................................................................. 83

6

CUSTOMER



Table of Contents

3.23.2 Building Web Services .......................................................................................................................... 83 3.24 Integration of Master Policy Data into BI system ............................................................................................... 86

3.24.1 BI Data Formatting ................................................................................................................................ 86 3.24.2 Data Sources ......................................................................................................................................... 86 3.24.3 SPRO Customization ............................................................................................................................ 88

3.25 Log of Changes - Master Policy ........................................................................................................................... 90 3.25.1 Customizing .......................................................................................................................................... 90 3.25.2 BAdI /PMG/GE_ABG_MX_CHN_LOG_BADI: Non Generic Custom Entities .................................. 91

3.26 Top Level Grouping ............................................................................................................................................... 91 3.26.1 BAdI: MMP Root Entity Fields Selection ............................................................................................. 92 3.26.2 BAdI: MMP Generic Entity Selection ................................................................................................... 92 3.26.3 BAdI: Copy Non-Generic Entities......................................................................................................... 93 3.26.4 BAdI: MMP Reversal ............................................................................................................................. 93 3.26.5 FPP Run .................................................................................................................................................. 94


Introduction

CUSTOMER

© 2017 SAP SE or an SAP affiliate company. All rights reserved. 7

1 Introduction

1.1 About This Document

Purpose

This document describes all activities necessary for the implementation and configuration of the software. This

configuration guide provides an overview of the Customizing activities and Business Add-Ins (BAdIs) that are

required for the configuration of the solution. For detailed documentation of the Customizing activities and

Business Add-Ins (BAdIs), see the documentation under SAP Customizing Implementation Guide → Policy

Management → Policy Management Group Enhancement.

1.2 Target Audience

This document is intended for the following target audiences:

Consultants

Partners

Customers

1.3 Glossary

Term Abbreviation Definition

Group Insurance GIA A group insurance bundles multiple risks together. It is

represented in FS-PM by a master policy.

Master Policy MP Object that packages or groups individual policies. The master

policy holds special group agreement data, group process data,

and data that is derived to the assigned policies.

Generic Entity GE An additional entity used to enhance the master policy

agreement that gives user the maintenance possibility to define

master policy dependent default values for assigned policies (for

example, for premium per piece).

8

CUSTOMER



Solution Overview

2 Solution Overview

Insurance business can be divided into individual and group business. SAP Policy Management (FS-PM) offers a

high degree of functionality for policy administration, yet the standard software leaves room for the inclusion of

additional features for group business. SAP Policy Management, group insurance add-on creates a set of functions

that allow you to extend your FS-PM usage in the area of group insurance. The extension allows you to tailor the

new functionality to meet your own business needs by providing:

Enhanced master policy functionality

Ability to preconfigure master policy templates

Enhanced mass change functionality

Enhanced correspondence concept for group business

Selection on master policy related policies

Premium payer distribution.


Implementation and Configuration

CUSTOMER


3 Implementation and Configuration

This guide contains the information you need to configure the SAP system to meet customer requirements. The

actual configuration is done in Customizing with the help of the implementation guide (IMG; transaction SPRO). It

covers all steps of the implementation process as well as the SAP standard (factory) Customizing settings and the

system configuration activities. The Customizing activities and their documentation are structured from a

functional perspective.

3.1 Activating the Group Add-On

Activate the Group Add-On within the IMG customizing.

1. Go to SPRO

2. Go to Policy Management for Group Insurance Switching Group Insurance

3. Check the flag

Caution

If the PMG namespace in PBT exists and the Group Insurance is not switched on, an error message appears at

every process.

Post-Installation

Insert the customer variant for SAP Policy Management, group insurance add-on into the Policy Based

Technology (PBT) by performing the following steps:

1. Choose /PM0/3fw_start.

2. Choose the application 00001 for FS-PM.

3. Insert the customer variant PMG to the ALV grid by entering a previous customer variant, for example, PM0.

10

CUSTOMER




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

For more information on post-installation tasks, see the SAP Note 2183602.

3.2 Number Range Objects

The intervals of the number range object /PM0/ABN15 (the number range interval for the master policy number)

and the number range object /PMG/GEMA (the number range interval for the master policy application number)

must be completely disjunctive.

For example, for /PM0/ABN15, the number range object intervals could be:

For /PMG/GEMA, the number range object intervals must be different. For example:

3.3 Enhancing Master Policy

3.3.1 IFBC Application

Overview

As with templates in SAP Policy Management (FS-PM), you preconfigure your master policy templates in the In-

Force Business Configurator (IBC). You can maintain master policy templates for every IBC-relevant entity of the

master policy business object under the master policy agreement.

Note

For more information regarding the creation of templates in the In-Force Business Configurator, see SAP

Help Portal at http://help.sap.com/insurance-pm → Application Help → Integration → In-Force Business

Configurator.

Migration Report

To enable existing master policies to use IFBC master policy templates you must assign the master policies to the

templates using the report /PMG/GE_TEMPL_ID_MP_ASSIGNMENT.

http://help.sap.com/insurance-pm



CUSTOMER


Enhancement Activities

To enhance the attribute values of a master policy template (/PM0/ABDGMPO), the structure

/PMG/GE_ABR_ATTR_MPO_S must be enhanced.

To enhance the attribute values of a generic entity template (/PMG/ABDGGEN), the structure

/PMG/GE_ABR_ATTR_GEN_S must be enhanced.

Business Add-Ins (BAdIs)

BAdI: Additional Checks for Master Policy Templates

This Business Add-In (BAdI) is used in the SAP Policy Management (FS-PM) component. You can use this BAdI to

check a template created in the master policy In-Force Business Configurator. A filter value should be used to

divide the checking mechanism. For additional information see the BAdI documentation in your system.

The BAdI name is /PMG/GE_MPE_CHECK_TMPL_BADI.

In Customizing for Policy Management, choose Policy Management Group Enhancement → Group Insurance

Management→ Basis→ In-Force Business Configurator→ Business Add-Ins (BAdIs) → BAdI: Additional Checks for

Master Policy Templates.

3.3.2 Generic Entity for Master Policy Business Object

Overview

The business object Master Policy Agreement is enhanced with an additional generic entity. This additional

generic entity allows you to define master policy dependent values. The entity is extendable and available in the

Master Policy IBC. You can add your own fields to this entity.

Customizing Activities

Define Master Policy Module ID

In Customizing for Policy Management, choose Policy Management Group Enhancement→ Group Insurance

Management→ Basis→ In-Force Business Configurator→ Define Master Policy Module ID

3.3.3 Update Run from Master Policy

An additional button has been added to Display/ Change master policy that will lead the user to Update Policies

and contracts.

From the master policy, once you have given either a master policy number or master application number, it will

transport the user and data to update run policies and contracts. This will then use the logic to generate the run Id.

From here, the master policy number will be derived from the display master policy or change master policy

regardless of the user choosing master policy number or master application number.

12

CUSTOMER




3.4 Enhancement of Master Policy

3.4.1 Premium Payer Distribution

Overview

You can maintain the Premium Payer Distribution data at the master policy level. The sections Company

Collection Data for Premium and Premium Payer Distribution are available in the Premium Payer Distribution tab of

the master policy.

Within the first section, you can maintain Company Collection data. This includes details such as Business

Partner, Inc. Payment Method, Address, Bank Details, Payment Card Number, Check Number, Collection

Account, Insurance Object, Payment Partner, Regulation Contract, Payment Policy, and Collection Type. Based

on the collection type selected, you can enter further details.

Within the second section, you can maintain Premium Payer Distribution pertaining to the current master policy

under processing. You can define the possible premium payer distributions within the customizing functionality.

The ALV picks up the possible Premium Payer Distribution IDs from this customization. The user can enter the

share percentage pertaining to the Premium Payer Distribution ID. This will be the percentage that is considered

when defaulting onto the assigned policies.

The Premium Payer Distribution data maintained at the master policy level influences and defaults to the Premium

Payer entity fields on the policy side during each of the scenarios below:

New Business under the master policy

Sales Product Change to the master policy

Creation of contract/coverage entity during the Change/Universal Change business processes.

You can change the values that have defaulted during these scenarios.

Master Policy IBC Configuration


To enable the usage of this functionality within master policies, the master policy template must include a generic

entity template with the attribute MPOL_MODULE_ID set as PREMDIST.


Define Premium Payer Distributions

This customizing functionality allows you to define your own Premium Payer distribution types.

In Customizing for Policy Management, choose →Policy Management Group Enhancement→ Group Insurance

Management→ Basis→ Master Policy Management→ Premium Payer Distribution → Define Premium Payer

Distributions.

As part of GIA delivery, two types are delivered as shown below.



CUSTOMER



The following BAdIs are provided and can be implemented as required:

BAdI Path

BAdI: Company Collection Field Modifiers within Master

Policy

BAdI name: /PMG/GE_COMP_COLL_FLD_MOD_BADI

In Customizing for Policy Management, choose

→Policy Management Group Enhancement→ Group

Insurance Management→ Basis→ Master Policy

Management→ Business Add-Ins (BAdIs) → BAdI:

Company Collection Field Modifiers within Master

Policy

BAdI: Set remaining allocation flag during Premium Payer

Dist onto Policy

BAdI name: /PMG/GE_PPD_ALLOC_REMIN_BADI





Set Remaining Allocation Flag During Premium

Payer Dist Onto Policy

BAdI: Defaulting of Customer defined Premium Payer

Distributions

BAdI name: /PMG/GE_PREM_PAYR_DST_DRV_BADI





Defaulting of Customer Defined Premium Payer

Distributions

3.4.2 Creditor

Overview

You can maintain creditor data at the master policy level. There is a Creditor section available in the Partners tab

of the master policy. You can maintain one or more creditors and their relevant data and assign this data to

product module groups. The product module IDs provide a list of all the available product modules that belong to

the policy templates that the user has added to the Templates tab.

14

CUSTOMER




The creditor data maintained at the master policy level is defaulted to the creditor fields of the assigned product

modules during each of the scenarios below:








entity template with the attribute MPOL_MODULE_ID set as Creditor.


Define Product Module Groups

To view the group dimension created for creditor (/PMG/CRDTR), see the Define Product Module Groups

Customizing activity under Policy Management → In-Force Business Management → Basis → Basic Settings.

Product module classes for the main axis elements (policy, contract, and coverage) are assigned to the new

group dimension. This can be viewed by selecting the Creditor group dimension and selecting Assign Product

Model Class to Group Dimension.

For each product module class, product module groups can be assigned by selecting the product module

class and selecting the option Product Module Groups.

Product module IDs should then be assigned to the product module groups by using the option Assignment of

Product Module ID to PBS Groups.

The creditor data defaults from the master policy to the assigned policies when you match the product module

groups in the master policy with the product module groups for the product module IDs of the main axis elements

in the assigned policies.

3.4.3 Beneficiary

Overview

You can maintain beneficiary data at the master policy level. There is a Beneficiary section available in the

Partners tab of the master policy. You can maintain one or more beneficiaries and their relevant data and assign

this data to product module groups. The product module IDs provide a list of all the available product modules

that belong to the policy templates that the user has added to the Templates tab.

The beneficiary data maintained at the master policy level is defaulted to the beneficiary fields of the assigned

product modules during each of the scenarios below:







CUSTOMER





entity template with the attribute MPOL_MODULE_ID set as Beneficiary.



To view the group dimension created for beneficiary (PMG/BNFRY), see the Define Product Module Groups



group dimension. This can be viewed by selecting the Beneficiary group dimension and selecting Assign

Product Model Class to Group Dimension.





Beneficiary data defaults from master policy to the assigned policies when you match the product module groups

in the master policy with the product module groups for the product module IDs of the main axis elements in the

assigned policies.

3.4.4 Collection Types (Broker)

Overview

You can maintain collection types and other relevant data, like broker data and third-party contract data, on the

master policy level. During New Business and Move-In with master policy, the collection type and relevant data is

defaulted from the master policy to the assigned single policies.

The standard collection types available are:

Broker Collections

Third-Party and Own Management of Contract Account

Third Party Collections

These collection types and the relevant screen sections and data processing are already maintained. You can add

new collection types and provide relevant implementations at the master policy level. This data can be defaulted

to the policy level, if required.

To default collection type data to the policy level, the new collection type value must be added to the available

Customizing activity, and all relevant screen enhancements must be made to get the required data from the user.

Master Policy IFBC configuration


To enable the usage of this functionality within master policies, the master policy template must include a

generic entity template with the attribute MPOL_MODULE_ID set as Collection Types.

16

CUSTOMER





Define Collection Type

The Customizing activity for the dropdown value of collection types is already available in the system.

You can maintain collection type ID, collection type category, and the description in the Define Collection Type

Customizing activity under Policy Management → Integration → Collections/Disbursements FS-CD → General

Settings.

3.4.5 Premium Per Piece

Overview

This functionality allows you to maintain the premium before tax for certain parameters within master policies.

You can enhance the parameters for a premium definition pursuant to your own requirements.

The parameters delivered are:

Object Category

Object Type

Validity Dates

The premium definition is derived to the manual premium based on the fulfilment of the parameters you have

maintained.

The premium per piece definitions are maintained with a version independent of the master policy version. This is

to ensure that premium definitions are not overwritten for backdated master policy changes.

The derivation logic is delivered as a sample implementation for the Building product (Template ID =

V880000S0000), using the standard Check&Derive framework. You can refer to this sample implementation

when building the premium derivation for customer landscapes and products.

Master Policy IFBC Configuration:



generic entity template with the attribute MPOL_MODULE_ID set as PPP.



To view the group dimension created for premium per piece (/PMG/PREMP), see the Define Product Module

Groups Customizing activity under Policy Management → In-Force Business Management → Basis → Basic

Settings.

Product module classes for the main axis elements for premium entity are assigned to this group dimension.

This can be viewed by selecting the Premium Per Piece group dimension and selecting Assign Product Model

Class to Group Dimension.







CUSTOMER


The relevant product module classes of main axis elements for premium entity have been assigned to this

group dimension. Product module groups can be assigned for each product module class. Product module

IDs representing the possible targets for premium derivation can be assigned to the Product module groups.


BAdI: User Data Enrichment for Premium Per Piece

The BAdI name is /PMG/GE_MPREM_CUST_ENRICH_BADI.


Management→ Basis→ Master Policy Management→ Business Add-Ins (BAdIs)→ BAdI: User Data Enrichment

for Premium Per Piece.

3.4.6 Commission Participant

Overview

You can maintain commission participant data at the master policy level. There is a new Commission tab where

you can maintain one or more commission participants for different roles. This data can be assigned to product

module groups. The product module IDs provide a list of all the available product modules that belong to the

policy templates that the user has added to the Templates tab.

To maintain the commission participant data and default this data to the assigned policies, you must enhance the

master policy with the specific commission data. The specific commission data is the standard commission

participant data and the standard related commission agent roles, similarly to policy management (see entities

/PM0/ABDACOMMIS and /PM0/ADACOMROLE).

The available commission agent roles are as follows:

Adjustment Agent

Portfolio Agent

Extension Agent

Signing Agent

The commission data maintained at the master policy level is defaulted to the commission fields of the assigned

product modules during the following scenarios:



Creation of contract/coverage entity during the Change/Universal Change business processes



BAdI: User Validations for Commission Agent in Master Policy

The BAdI name is /PMG/GE_CHK_COMMIS_BADI.

In Customizing for Policy Management, choose → Policy Management Group Enhancement → Group

Insurance Management → Basis → Master Policy Management → Business Add-Ins (BAdIs) → BAdI: User

Checks/Validations for Commission Agent in Master Policy.

18

CUSTOMER




ALV Layouts

Default ALV layouts for commission participant (0001_CPP) and commission agent role (0001_COMMAGT) are

provided.

3.4.7 Multiple Master Policy Partner

Overview

You can maintain multiple master policy partner data at the master policy level. There is a Master Policy Partner

section available in the Master Policy Data tab of the master policy. You can maintain one or more master policy

partners and their relevant data. An ALV is provided to list all the master policy partners applicable for the master

policy.




generic entity template with the attribute MPOL_MODULE_ID set as MULPART.

3.4.8 Surcharge/Discount On Master Policy

Overview

You can maintain Surcharge/Discount data at the master policy level. There is a Surcharge/Discount section

available in a separate tab of the master policy. You can maintain one or more surcharge/discounts and their

relevant data and assign this data to product module groups. The product module IDs provide a list of all the

available product modules that belong to the policy templates that the user has added to the Templates tab.

The Surcharge/Discount data maintained at the master policy level is defaulted to the surcharge/discount fields

of the assigned product modules during each of the scenarios below:








generic entity template with the attribute MPOL_MODULE_ID set as SUPDC.



CUSTOMER




To view the group dimension created for surcharge/discount (/PMG/SUPDC), see the Define Product Module

Groups Customizing activity under Policy Management → In-Force Business Management → Basis → Basic

Settings.


group dimension. This can be viewed by selecting the surcharge/discount group dimension and selecting

Assign Product Model Class to Group Dimension.





Surcharge/Discount data defaults from master policy to the assigned policies when you match the product

module groups in the master policy with the product module groups for the product module IDs of the main axis

elements in the assigned policies.

3.4.9 Clauses On Master Policy

Overview

You can maintain Clause data at the master policy level. There is a Clauses section available in a separate tab of

the master policy. You can maintain one or more clauses and their relevant data and assign this data to product

module groups. The product module IDs provide a list of all the available product modules that belong to the

policy templates that the user has added to the Templates tab.

The clauses data maintained at the master policy level is defaulted to the Clause fields of the assigned product

modules during each of the scenarios below:







20

CUSTOMER





generic entity template with the attribute MPOL_MODULE_ID set as CLAUSE.



To view the group dimension created for clause (/PMG/CLAUS), see the Define Product Module Groups



group dimension. This can be viewed by selecting the Surcharge/discount group dimension and selecting

Assign Product Model Class to Group Dimension.





Clause data defaults from master policy to the assigned policies when you match the product module groups

in the master policy with the product module groups for the product module IDs of the main axis elements in

the assigned policies.

3.4.10 Valid-To Date Defaulting

Overview:

This functionality allows for a defaulting of the Valid-To Date on a master policy. The default date is assigned

during the create event of the master policy. This date can be changed by the user if required. The defaulting is

configurable using the attribute VALID_TO_DATE on the master policy template.

Customizing Activities:

Maintain VALID_TO_DATE attribute on Master Policy template

Using the Master Policy In-Force Business Configurator transaction /PMG/GE_IBC_MPOL, assign one of the

delivered defaulting types.

1. High date, e.g. 31st Dec 9999

2. Next day, next year



CUSTOMER


3. First day, New Year


Maintain custom Valid to Date Types

Custom Valid-to Date Types can be maintained in the maintenance view /PMG/GE_PMP_VTD - Maintenance View

Master Policy Valid to Date Types. The custom logic for these new types can be implemented using Business

Add-In

/PMG/GE_MPE_DFLT_VTD_BADI - BAdI: Master Policy Default Valid to Date.

22

CUSTOMER




Documentation for both customizing activities can be found in the IMG under Policy Management → Policy

Management Group Enhancement → Group Enhancement Management → Basis → Master Policy Management →

Valid to Date Defaulting

New Business Add-Ins (BAdIs)

BAdI: Master Policy Default Valid to Date

This Business Add In can be implemented to allow for a flexible determination of the valid to date of master policy

based on custom specific requirements.

The BAdI name is /PMG/GE_MPE_DFLT_VTD_BADI.

Further documentation can be found in the Customizing for Policy Management, choose Policy Management

Group Enhancement → Group Enhancement Management → Basis → Master Policy Management → Valid to

Date Defaulting.

3.4.11 Central Access For Master Policy

Overview: Customization option for controlling generic objects settings

This functionality allows you to enable or disable generic objects to be search enabled. Also, a customer can

enable custom defined generic object to be search enabled.


Define Generic Object Settings

You can enable or disable the SAP delivered generic objects or add new custom defined generic object to be

search enabled under SAP Customizing Implementation Guide→Policy Management→Policy Management

Group Enhancement→ Group Insurance Management→ Basis→ Master Policy→Central Access→Define

Generic Object Settings

How to extend customer defined generic object

You need to follow the steps below to enable a customer defined generic object to be search enabled.

Add customer defined generic object entry in the below customization view.

SAP Customizing Implementation Guide→Policy Management→Policy Management Group Enhancement→

Group Insurance Management→ Basis→ Master Policy→Central Access→Define Generic Object Settings

How to extend the build the screen:

5. Open PBT transaction /PM0/3FW_START.

6. Select your workplace, Expand Meta Model, Expand Dialog Models.

7. Click on Subcontroller Models. In the pop-up search for Model Name /PMG/P_B_D_MPE_MCA_ENTRY

Create a new controller under /PMG/GE_MCA_GENERIC_OBJECT ( expand /PMG/P_B_D_MPE_MCA_ENTRY

then expand /PMG/GE_MPE_MCA_MD01 then /PMG/GE_MPE_MCA_SEARCH ) controller with name

<CUSTOMERNAMESPACE>GE_MCA_GEN_<YOUR_MPOL_ID>

Assign process context as /PMG/GE_MCA_GEN_OBJECT



CUSTOMER


Enter channel structure name. This should be same as channel structure you entered for your generic object

in SAP Customizing Implementation Guide→ Policy Management → Policy Management Group

Enhancement→ Group Insurance Management→ Basis→ Master Policy → Central Access → Define Generic

Object Settings

Assign the constraint class as /PMG/CL_GE_MCA_GEN_CONSTRAINT

You can build the screen based on your requirement in your custom development package and assign the screen

number, subprogram name in screen assignment. Enter class name as /PM0/CL_3F_CDM_SCR_CTRL

Save your changes and run the transaction /PMG/ABC_MPO_GCA

You should be able to see your new Generic Object in Search by Generic Objects dropdown and the screen

associated with it should load.

3.4.12 Master Policy Tree

Overview: Customization option for controlling generic objects settings

This functionality allows you to enable or disable the tree nodes on the master policy screens


Define Master Policy Tree

You can define the parent and sub nodes to show up the master policy tree heirarchy on the create, change and

display transactions of master policy: /PM0/ABC_MPO_GN, /PM0/ABC_MPO_GM and /PM0/ABC_MPO_GD

Define header nodes:


Group Insurance Management→ Basis→ Master Policy Management → Master Policy Tree → Tree Header

Nodes.

Define sub nodes:


Group Insurance Management→ Basis→ Master Policy Management → Master Policy Tree → Tree Sub nodes.



CUSTOMER


| |-Clauses

| |-Commission

| |-Premium per piece

|-Individual Policies

| |-Open Applications

| |-Where Used List

|-Cockpit

|-Overview Cockpit

|-Others

How to extend customer specific nodes:

The customer can change the sequence number with which the existing node hierarchy can be rearranged.

The customer can include their own specific nodes into the existing list of nodes by customizing changes.

It is mandatory to incorporate the constraint class: /PMG/CL_GE_GEN_MPE_BPC_DGEN on to the channel or

parent ids defined at PBT customizing.

There is a section Others meant for customer specific tabs which can be used for enhancing the tree structure.

3.4.13 Distribution Plan On Master Policy

3.4.13.1 Overview:

You can Maintain Distribution Plan data at the master policy level. There is a new Distribution Plan tab section

available in the separate tab of the master policy. You can maintain a Distribution Plan and the relevant data and

assign this data to product module groups. The product module IDs provide a list of all the available product

modules that belong to the policy templates that user has added to the templates tab.

3.4.13.2 Master Policy IBC Configuration:



entity template with the attribute MPOL_MODULE_ID set as DISTPLAN

26

CUSTOMER




3.4.13.3 Customizing Activities:

Define Product Module Groups:

A new value for the group dimension (/PMG/DCOI) is created for the Distribution Plan. To view the new group

dimension. See the Define product module groups customizing activity under Policy Management. In force

Business Management →Basis→ Basic settings.

Product module classes for the main axis elements (Product, Contract and Coverage) are assigned to the new

group dimension. This can be viewed by selecting the distribution plan group dimension and selecting Assign

Product Model Class to group Dimension.

For each Product Module class. Product module groups can be assigned by selecting the product module class

and selection the option Product Module Groups.

Product Module IDs should then be assigned to the product module groups by using the option Assignment of

product Module ID to PBS groups.

3.4.14 Deductibles On Master policy

3.4.14.1 Overview:

You can Maintain Deductibles data at the master policy level. There is a new Deductible tab section available in the

separate tab of the master policy. You can maintain one or more deductibles and their relevant data and assign

this data to product module groups. The product module IDs provide a list of all the available product modules

that belong to the policy templates that user has added to the templates tab.

The deductibles data maintained at the master policy level is defaulted to the Deductible fields of the assigned

product modules during each of the scenarios below.

New Business under the Master policy

Sales product change to the master policy


3.4.14.2 Master Policy IBC Configuration




CUSTOMER



entity template with the attribute MPOL_MODULE_ID set as DED

3.4.14.3 Customizing Activities:


A new value for the group dimension (/PMG/DED) is created for Deductible. To view the new group dimension. See

the Define product module groups customizing activity under Policy Management. In force Business Management

→ Basis→ Basic settings.


group dimension. This can be viewed by selecting the Deductibles group dimension and selecting Assign product

Model Class to group Dimension.

For each Product Module class. Product module groups can be assigned by selecting the product module class




Deductibles data defaults from the master policy to the assigned Policies. This occurs when you match the

product module groups in the master policy with the product module groups for the product module IDs in the

main axis elements in the assigned policies.

28

CUSTOMER




3.4.14.4 Deductibles Derivation -Schedule Related Dates

Overview: External date change Deductibles

This functionality allows you to derive the deductibles defined in the master policy to the child policies. For this a

Time Model Function is created and executed via Schedule related dates. The child policies must be positioned on

or after the effective date to see the deductibles information in the child policies at (contract / coverage levels).


Define new Time Model Function

A new Time Model Function was created for deductible synchronization. To view the new Time Model

Function created, see the Define Dates and Time Model Functions Customizing activity under Policy

Management → In-Force Business Management → Basis → Update→ Time Model → Define Dates and Time

Model Functions

To add the new Time Model Function to an existing product module group, see the Define Execution Criteria

for Time Model Functions Customizing activity under Policy Management → In-Force Business Management →

Basis→ Update→ Time Model → Define Execution Criteria for Time Model Functions

The Journal entry for the new Time Model Function is to be defined. To view this, see the Define Journal

Entries Customizing activity under Policy Management → In-Force Business Management → Basis→ Journal→

Define Journal Entries



CUSTOMER



BAdI: MP Sync TMF Renewal decision

You can decide not to run a certain synchronization Time Model Function during renewal via this BADI.

The BAdI name is /PMG/GE_SYNC_RNW_TMF_DESC_BADI.

In Customizing for Policy Management, choose Policy Management Group Enhancement →Business

Processes→ Business Add-Ins (BAdIs)→ Master Policy data Synchronization during Renewal → BAdI:

BAdI:Decision for the TMF call during Synchronization at Renewal.

This is a filter BAdI, so if you want to stop the scheduling of the collection time model, then create a new

implementation with the filter '/PMG/MPP_MP' and the flag ev_tmf_skip is to be set as true.

3.4.15 Limits On Master policy

3.4.15.1 Overview:

You can Maintain Limits data at the master policy level. There is a new Limits tab section available in the separate

tab of the master policy. You can maintain one or more limits and their relevant data and assign this data to

product module groups. The product module IDs provide a list of all the available product modules that belong to

the policy templates that user has added to the templates tab.

30

CUSTOMER




The limits data maintained at the master policy level is defaulted to the limits fields of the assigned product

modules during each of the scenarios below.


Sales product change to the master policy


3.4.15.2 Master Policy IBC Configuration



entity template with the attribute MPOL_MODULE_ID set as LIMIT.

3.4.15.3 Customizing Activities


A new value for the group dimension (/PMG/LIMIT) is created for Limit. To view the new group dimension. See

the Define product module groups customizing activity under Policy Management. In force Business Management

→ Basis → Basic settings.


group dimension. This can be viewed by selecting the limits group dimension and selecting Assign product Model

Class to group Dimension.

For each product module class, product module groups can be assigned by selecting the product module class






CUSTOMER


Limits data defaults from the master policy to the assigned Policies when you match he product module groups in

the master policy with the product module groups for the product module IDs the main axis elements in the

assigned policies.

3.4.15.4 Limits Derivation - Schedule Related Dates

Overview: External date change Limits

This functionality allows you to derive the limits defined in the master policy to the child policies. Create and

execute a Time Model Function via Schedule related dates. The child policies must be positioned on or after the

effective date to see the limits information in the child policies at (contract / coverage levels).



A new Time Model Function was created for Limits synchronization. To view the new Time Model Function

created, see the Define Dates and Time Model Functions Customizing activity under Policy Management → In-

Force Business Management → Basis → Update→ Time Model → Define Dates and Time Model Functions



Basis→ Update→ Time Model→Define Execution Criteria for Time Model Functions

32

CUSTOMER




The Journal entry for the new Time Model Function is to be defined. To view it, see the Define Journal Entries

Customizing activity under Policy Management → In-Force Business Management → Basis→ Journal→ Define

Journal Entries








This is a filter BAdI. If you want to stop scheduling the collection time model then a new implementation needs

to be created with the filter '/PMG/MPP_MP' and the flag ev_tmf_skip is to be set as true.

3.4.16 Premium Payer Distribution

Overview: External date change premium payer distribution

This functionality allows you to derive the premium payer distribution of the master policy to the child policies.

Create and execute a Time Model Function via Schedule related dates. The child policies must be positioned on or

after the effective date to see the PPD distribution in the child policies.



A new Time Model Function was created for premium payer distribution synchronization. To view the new

Time Model Function created, see the Define Dates and Time Model Functions Customizing activity under

Policy Management → In-Force Business Management → Basis → Update→ Time Model → Define Dates and

Time Model Functions



CUSTOMER


To assign the new Time Model Function to an existing product module group, see the Define Execution Criteria


Basis→ Update→ Time Model → Define Execution Criteria for Time Model Functions



Journal Entries








34

CUSTOMER




This is a filter BAdI, so if you want to stop the scheduling of the premium payer distribution time model, then

create a new implementation with the filter '/PMG/PREM_PAYDIST_MP' and the flag ev_tmf_skip is to be set as

true.

3.4.17 Premium Per Piece

Overview:

This functionality allows you to maintain the premium before tax for certain parameters within master policies.

You can enhance the parameters for a premium definition pursuant to your own requirements.

The parameters delivered are:

Object Category

Object Type

Validity Dates

The premium definition is derived to the manual premium based on the fulfilment of the parameters you have

maintained.

The premium per piece definitions are maintained with a version independent of the master policy version. This is

to ensure that premium definitions are not overwritten for backdated master policy changes.

The derivation logic is delivered by the RCS as a sample implementation for the Building product (Template ID =

V880000S0000) only, using the standard Check&Derive framework. You can refer to this sample

implementation when building the premium derivation for customer landscapes and products.



A new Time Model Function was created for premium per piece synchronization. To view the new Time Model

Function created, see the Define Dates and Time Model Functions Customizing activity under Policy

Management → In-Force Business Management → Basis→Update→ Time Model→Define Dates and Time

Model Functions



CUSTOMER




Basis→ Update→ Time Model→Define Execution Criteria for Time Model Functions



Journal Entries








This is a filter BAdI, so if you want to stop scheduling the premium per piece time model, then create a new

implementation with the filter '/PMG/PREM_PIECE_MP' and the flag ev_tmf_skip set as true.

36

CUSTOMER




3.5 Enhancement Of Master Policy Functionality

3.5.1 Copy Of Master Policy

Overview

The standard Copy business process is enhanced enabling copying of the data from the source master policy to

the target master policy for the new entities that have been created.


BAdI: Copying of Non-Standard Entities in Copy Business Process

The BAdI name is /PMG/GE_MPE_COPY_NW_ENTY_BADI.

In Customizing for Policy Management, choose →Policy Management Group Enhancement→ Group Insurance

Management→ Basis→ Master Policy Management→ Business Add-Ins (BAdIs) → BAdI: Copying of Non-

Standard Entities in Copy Business Process.

3.6 Enhancement Of Result Set

3.6.1 Change Document

Overview:

Change document is enabled for change result set. You can view the changes that are done in the result set can be

viewed in result set display in transaction /PMG/GE_SEL_DISP.


Change document customization of defining the change document object is SAP Delivered customization.

Launch the transaction SCDO and make sure change document object /PMG/CD_CR_SEL is present

3.7 Define Master Policy Module ID

3.7.1 Define and Maintain Master Policy Module ID

To be able to define additional roles on the master policy, the master policy module IDs for contact person and

organizational assignment need to be configured in IMG.

In Customizing, navigate to Policy Management → Policy Management Group Enhancement → Group Insurance

Management → Basis→ In-Force Business Configurator → Define Master Policy Module ID



CUSTOMER


38

CUSTOMER






CUSTOMER


3.7.2 Define Organizational Level Assignment Type

Define the organizational level type for master policy template in IMG.

Navigate to the following path in SAP IMG:

SAP Customizing Implementation Guide → Policy Management → Policy Management Group Enhancement →

Group Insurance Management → Basis → Master Policy Management → Additional Roles on Master Policy

3.7.3 Define Organizational Assignments on Master Policy

The organizational assignment data needs to be configured to be defaulted onto the master policy. The same can

be done in SAP IMG on the following path:

SAP Customizing Implementation Guide → Policy Management → Policy Management Group Enhancement →

Group Insurance Management → Basis → Master Policy Management → Additional Roles on Master Policy

40

CUSTOMER




3.8 Master Policy - Overview of Open Applications

3.8.1 Selection Options Overview Cockpit

3.8.1.1 Define and Maintain Options for Overview Cockpit

SAP Policy Management, add on for group insurance can configure additional master policy roles via the

transaction SPRO.

In Customizing navigate to Policy Management → Policy Management Group Enhancement → Group Insurance

Management → Basis→ Master Policy Management → Overview Cockpit → Define the options for Overview

Cockpit

3.8.1.2 Overview Cockpit

A new tab Overview Cockpit will be available in change and display Master Policy where the user can have an

overview of different types for the child policies of master Policy.



CUSTOMER


The ALV's for the Cockpit overview can be enhanced by the customers using the standard BADI:

/PM0/ABP_CDM_ALV_ES with their specific implementation.

3.8.1.3 Contract Journal at Master Policy

The contract journal at master policy will be displayed under the "Where Used List" tab, once the "Contract

Journal" button is pressed after selecting a single policy under the where used list tab.

The ALV's for the contract journal overview can be enhanced by the customers using the standard BADI:

/PM0/ABP_CDM_ALV_ES with their specific implementation.

42

CUSTOMER




3.9 External Date - Derivation of Master Policy Data

3.9.1 Beneficiary Derivation

Overview: External date change beneficiary

This functionality allows you to derive the beneficiary defined in the master policy to the child policies. Create and

execute a Time Model Function via Schedule related dates. The child policies must be positioned on or after the

effective date to see the beneficiary information under partner in the child policies.



Create a new Time Model Function beneficiary data synchronization. To view the new Time Model Function,

see the Define Dates and Time Model Functions Customizing activity under Policy Management → In-Force

Business Management → Basis → Update→ Time Model → Define Dates and Time Model Functions



Basis → Update → Time Model → Define Execution Criteria for Time Model Functions



CUSTOMER


The journal entry for the new Time Model Function is to be defined. To view it, see the Define Journal Entries

Customizing activity under Policy Management → In-Force Business Management → Basis → Journal→ Define

Journal Entries





In Customizing for Policy Management, choose Policy Management Group Enhancement → Business

Processes → Business Add-Ins (BAdIs)→ Master Policy data Synchronization during Renewal → BAdI:


This is a filter BAdI, so if you want to stop a scheduling of the collection time model, then create a new

implementation with the filter '/PMG/BNFCRY_MP' and the flag ev_tmf_skip is to be set as true.

3.9.2 Multiple Master Policy Partner Derivation

Overview: External date change Multiple Master policy partner

This functionality allows you to derive the policy partners defined in the master policy to the child policies. Create

and execute a Time Model Function via Schedule related dates. The child policies must be positioned on or after

the effective date to see the policy partner's information under partner in the child policies. The default policy

partner flag should be set in the master policy as a prerequisite.




Time Model Function created, see the Define Dates and Time Model Functions Customizing activity under

44

CUSTOMER




Policy Management → In-Force Business Management → Basis → Update → Time Model → Define Dates and

Time Model Functions

Add the new Time Model Function to an existing product module group. To assign it, see the Define Execution

Criteria for Time Model Functions Customizing activity under Policy Management → In-Force Business

Management → Basis→ Update → Time Model→ Define Execution Criteria for Time Model Functions

To define the journal entry for the new Time Model Function, see the Define Journal Entries Customizing

activity under Policy Management → In-Force Business Management → Basis→ Journal→ Define Journal

Entries








This is a filter BAdI, so if you want to stop a scheduling of the collection time model then a new

implementation needs to be created with the filter '/PMG/MPP_MP' and the flag ev_tmf_skip is to be set as

true.



CUSTOMER


3.9.3 Clause Derivation

Overview: External date change Clause

This functionality allows you to derive the clauses of a master policy to its child policies. For this a Time Model

Function is created and executed via Schedule Related Dates. The child policies must be positioned on or after the

effective date to see the clause data in the child policies. The child policies must exist as children of the master

before the date is scheduled or the TMF will not be listed under the child's planned processing activities.



A new Time Model Function was created for clause synchronization. To view the new Time Model Function,


Business Management → Basis → Update → Time Model → Define Dates and Time Model Functions

The new Time Model Function is to be added to an existing product module group. To assign it, see the Define

Execution Criteria for Time Model Functions Customizing activity under Policy Management → In-Force

Business Management → Basis → Update → Time Model → Define Execution Criteria for Time Model Functions

46

CUSTOMER





Customizing activity under Policy Management → In-Force Business Management → Basis → Journal →





The BAdI name is /PMG/GE_MPSYNC_RNW_TMF_BADI.


Processes → Business Add-Ins (BAdIs) → Master Policy data Synchronization during Renewal → BAdI:


This is a filter BAdI, so if you want to stop a scheduling of the clause time model then a new implementation

needs to be created with the filter '/PMG/CLAUSE_MP' and the flag EV_TMF_SKIP is to be set as true.

3.9.4 Coinsurance Derivation

Overview: External date change Coinsurance

This functionality allows you to derive the coinsurance data of a master policy to its child policies. For this a Time

Model Function is created and executed via Schedule Related Dates. The child policies must be positioned on or

after the effective date to see the coinsurance data in the child policies. The child policies must exist as children of

the master before the date is scheduled or the TMF will not be listed under the child's planned processing

activities.



A new Time Model Function was created for coinsurance synchronization. To view the new Time Model

Function, see the Define Dates and Time Model Functions Customizing activity under Policy Management →

In-Force Business Management → Basis → Update → Time Model → Define Dates and Time Model Functions



CUSTOMER





The journal entry for the new Time Model Function is to be defined. To view this, see the Define Journal Entries





48

CUSTOMER









This is a filter BAdI so if you want to stop a scheduling of the Clause time model then a new implementation

needs to be created with the filter '/PMG/CLAUSE_MP' and the flag EV_TMF_SKIP is to be set as true.

3.9.5 Collection Type Derivation

Overview: External date change collection Type

This functionality allows you to derive the collection type of master policy to the child policies. For this a Time

Model Function is created and executed via Schedule related dates. The child policies must be positioned on or

after the effective date to see the collection type under premium payer in the child policies.



A new Time Model Function was created for collection type data synchronization. To view the new Time Model

Function, see the Define Dates and Time Model Functions Customizing activity under Policy Management →

In-Force Business Management → Basis → Update → Time Model → Define Dates and Time Model Functions



Business Management → Basis→ Update→ Time Model → Define Execution Criteria for Time Model Functions



CUSTOMER




Journal Entries








This is a filter BAdI so if you want to stop a scheduling of the collection time model then a new implementation

needs to be created with the filter '/PMG/CLTYP_MP' and the flag ev_tmf_skip is to be set as true.

3.9.6 Creditor Derivation

Overview: External date change Creditor

This functionality allows you to derive the creditors of a master policy to its child policies. A Time Model Function

is created and executed via Schedule Related Dates. The child policies must be positioned on or after the effective

date to see the creditor data in the child policies. The child policies must exist as children of the master before the

date is scheduled or the TMF will not be listed under the child's planned processing activities.

50

CUSTOMER






A new Time Model Function was created for Creditor synchronization. To view the new Time Model Function,


Business Management → Basis → Update → Time Model → Define Dates and Time Model Functions









CUSTOMER









This is a filter BAdI, so if you want to stop a scheduling of the creditor time model, then a new implementation

needs to be created with the filter '/PMG/CRDITOR_MP' and the flag EV_TMF_SKIP is to be set as true.

3.9.7 Multiple Master Policy Partner Derivation

Overview: External date change Multiple Master policy partner

This functionality allows you to derive the policy partners defined in the master policy to the child policies. A Time

Model Function is created and executed via Schedule related dates. The child policies must be positioned on or

after the effective date to see the Policy partner's information under partner in the child policies. The default

policy partner flag should be set in the master policy as a prerequisite.




Time Model Function, see the Define Dates and Time Model Functions Customizing activity under Policy

Management → In-Force Business Management → Basis→Update→ Time Model→Define Dates and Time

Model Functions

52

CUSTOMER






Business Management → Basis→ Update→ Time Model→Define Execution Criteria for Time Model Functions



Journal Entries




The BAdI name is /PMG/GE_SYNC_RNW_TMF_BADI.




This is a filter BAdI so if you want to stop a scheduling of the collection time model, then a new

implementation needs to be created with the filter '/PMG/MPP_MP' and the flag ev_tmf_skip is to be set as

true.

3.10 Configuration of Surcharge/Discount TMF

Overview:

When a contract/coverage/coverage package level a surcharge/discount exists which doesn’t have the start date

of its parent, then the calculation adjustment TMF shall be scheduled for that later date.

This is achieved by creating a new Time Model Function ‘/PMG/PTSDCALC’ of type ‘TMF3’.



CUSTOMER


The following are the main elements of TMF creation:

- Creation of new Business Component

- Maintain standard implementations for Business Component

- Define journal entries

- Creation of Dates in SE43

- Configure the TMF in SPRO

- Define Execution Criteria for Time Model Functions

3.10.1 Business Component ‘445’

To create a new business component for the Time Model Function, create a new entry in the view

‘/PM0/ABU_PBCID’.

3.10.2 Maintain Standard Implementation for Business Component

Standard implementations need to be configured with respect to the business component configured in the

previous step. These implementations are simply the LoB specific TMF implementation classes.

54

CUSTOMER




3.10.3 Define Journal Entries

A journal entry ‘T_PTSDCALC’ shall be created with processing type ‘PROC_T’, in SPRO at path:

SAP Customizing Implementation Guide → Policy Management → In-Force Business Management → Basis →

Journal → Define Journal Entries

3.10.4 Create New Dates for Time Model Function

To configure a new TMF for Surcharge/Discount calculation new dates are defined in transaction ‘SE43’.

When you create an entry for new date, assign the journal entry created in the previous step to it.



CUSTOMER


The LoB specific IDs are created and the TMF execution class is assigned.

3.10.5 Configure Time Model Function in SPRO

The Time Model Function is finally configured in the IMG activities at the path:

SAP Customizing Implementation Guide → Policy Management → In-Force Business Management → Basis →

Update → Time Model → Define Dates and Time Model Functions.

3.10.6 Define Execution Criteria for Time Model Function

Configure the created Time Model Function for the LoB specific product module group. The image below depicts

the configuration for the life product module group. A similar configuration is maintained for non-life product

module groups as well.

56

CUSTOMER




3.11 Business Process: Mass-enablement of Business Transactions

3.11.1 Mass Exclude Coverage

Overview

You can change a master policy and choose the option Schedule Business Transaction to mass exclude a contract

coverage from policies that belong to a master policy. This exclude option is available for life- and fund-based

contracts with supplementary type coverages. Coverages with assigned fund assets are not permitted to be

excluded. The mass transaction is available with Bus.Trans.Exec.Level = Coverage. The coverage will be removed

from the policies from the effective date of the scheduled change. The system prompts you to choose an option to

handle the Exclusion of Supplementary Insurance. The options presented are the same as the single business

transaction for exclude coverage. The scheduled changes are released using the Update Policies/Contracts

update run.

Product Template IBC Configuration:

To enable the mass exclude coverage functionality, the product template for the coverage needs the Exclude

Coverage mass business transaction assigned on the Bus. Transactions tab under business process MA Mass

Change.


BAdI: Enhancement Spot for Exclude Coverage

You can use this BAdI to add additional checks during the scheduling of mass exclude coverage. A default

implementation exists to ensure mandatory fields are supplied. The default implementation also raises an error if

the coverage has a fund asset assigned as coverage exclusions of this type are not permitted.

The BAdI name is /PMG/GE_PROC_COV_EXC_BADI.

Sample implementation name is /PMG/GE_MBTX_COV_EXC_CHECKS.



CUSTOMER


3.11.2 Mass Change Beneficiary

Overview

You can change a master policy and choose the option Schedule Business Transaction to mass change the

partner beneficiary on policies that belong to a master policy. The mass transaction is available with

Bus.Trans.Exec.Level = Contract or Coverage. The existing beneficiary will be removed and replaced with the

newly selected one. The new beneficiary will be inserted into the policies Partner tab from the effective date of the

scheduled change. You can add a single beneficiary or multiple beneficiaries split by share percentage or share

amount. The scheduled changes are released using the Update Policies/Contracts update run.


To enable the mass change beneficiary functionality, the product template for the contract or coverage needs

the Change Beneficiary mass business transaction assigned on the Bus. Transactions tab under business

process MA Mass Change.


BAdI: Enhancement Spot for Mass Change Beneficiary

You can use this BAdI to set additional checks during the scheduling of mass change beneficiary. A default

implementation exists to ensure at least one new beneficiary line is added with mandatory fields supplied. The

default implementation also checks that the rank information is supplied in the correct sequence and that the

share percentage is not greater than 100% at each rank and sub-coverage type combination.

The BAdI name is /PMG/GE_PROC_BNY_BADI.

Sample implementation name is /PMG/GE_MBTX_BNY_CHECKS.

58

CUSTOMER




3.11.3 Mass Change Creditor

Overview

You can change a master policy and choose the option Schedule Business Transaction to mass change the

partner creditor on policies that belong to a master policy. The mass transaction is available with

Bus.Trans.Exec.Level = Contract or Coverage. The existing creditor will be removed and replaced with the newly

selected one. The new creditor will be inserted into the policies Partner tab from the effective date of the

scheduled change. You can add a single creditor or multiple creditors split by share percentage or share amount.

The scheduled changes are released using the Update Policies/Contracts update run.


To enable the mass change creditor functionality, the product template for the contract or coverage needs

the Change Creditor mass business transaction assigned on the Bus. Transactions tab under business



BAdI: Enhancement Spot for Change Creditor

You can use this BAdI to set additional checks during the scheduling of mass change creditor. A default

implementation exists to ensure at least one new creditor line is added with mandatory fields supplied. The default

implementation also checks that the rank information is supplied in the correct sequence and that the share

percentage is not greater than 100% at each rank and sub-coverage type combination.

The BAdI name is /PMG/GE_PROC_CDR_BADI.

Sample implementation name is /PMG/GE_MBTX_EI_CDR.



CUSTOMER


3.11.4 Mass Change Execute Manual Rating

Overview

The business transaction Execute Manual rating (P_B_S_MRT_XCT) is mass-enabled for use in the Mass Change

business process to perform the following changes on all or a subset of policies belonging to a Master Policy

Change the Premium data by specifying a premium rate or Absolute premium

Add an Alternate Commission participant data to all the policies of a master contract.

This functionality is executable at coverage level. When the update run is executed, the existing premium data of

the policy will be modified with the new premium based on the business transaction. This data is defaulted to the

designated assigned policies during master policy-related New Business or Move-In.


To enable the mass execute manual rating functionality, the product template for the coverage needs the

Execute Manual Rating mass business transaction assigned on the Bus. Transactions tab under business



BAdI: Enhancement Spot for Execute Manual Rating

You can use this BAdl to perform custom validations on the Execute Manual Rating mass change transaction.

The BAdI name is /PMG/GE_MBTX_MART_BADI.

Sample implementation name is /PMG/GE_MBTX_MAR_EI.

60

CUSTOMER




3.11.5 Mass Perform Premium Waiver

Overview

You can change a master policy and choose the option Schedule Business Transaction to mass enable a premium

waiver on Life policies that belong to a master policy. The mass transaction is available with Bus.Trans.Exec.Level

= Contract. The premium of the contract is waived until the end of the contract. A new commission participant for

claw back can be added via ALV. The commission case can be set to status pending. The scheduled changes are

released using the Update Policies/Contracts update run.


To enable the mass perform premium waiver functionality, the product template for the contract needs the

Perform Premium Waiver mass business transaction assigned on the Bus. Transactions tab under business



BAdI: BADI implementation of Execute Manual Rating Mass BTX

You can use this BAdI to add additional checks during the scheduling of mass perform premium waiver. A default

implementation exists to ensure mandatory fields are supplied. The default implementation also checks when one

or more different commission participants are entered the values for the direct and indirect rates add up to 100%

for all participants specified.

The BAdI name is /PMG/GE_PROC_PRW_BADI.

Sample implementation name is /PMG/GE_MBTX_PRW_CHECKS.



CUSTOMER


3.11.6 Mass Process Premium Waiver

Overview

You can change a master policy and choose the option Schedule Business Transaction to mass enable a premium

waiver on non-Life policies that belong to a master policy. The mass transaction is available with

Bus.Trans.Exec.Level = Policy, Contract and Coverage. The premium is waived until the end date that you enter.


Product Template IBC Configuration

To enable the mass process premium waiver functionality, the product template for the policy, contract or

coverage needs the Perform Premium Waiver mass business transaction assigned on the Bus. Transactions

tab under business process MA Mass Change.


BAdI: Enhancement Spot for Process Premium Waiver

You can use this BAdI to set additional checks during the scheduling of mass process premium waiver. A default

implementation exists to ensure mandatory fields are supplied.

The BAdI name is /PMG/GE_PROC_PPW_BADI.

Sample implementation name is /PMG/GE_MBTX_PPW_CHECKS.

3.11.7 Process Coinsurance

Overview

The business transaction Process Coinsurance (P_B_S_COINS_AMD) is mass-enabled to be executed in the Mass

Change business process. During the processing of the business transaction, the adding of a distribution plan

62

CUSTOMER




template only takes place on the main axes that are defined as relevant for coinsurance in the In-force Business

Configurator (IFBC).


To be able to execute process coinsurance mass change for a product, the business transaction should be added

to the set of assigned business transactions for the product:

1. Follow the path: SAP Easy Access → SAP Menu → Policy Management → In Force Management → Product

Templates → Edit Product Templates.

2. Select the product for which the Process Coinsurance business transaction should be allowed and go to the

Business Transactions tab.

3. Add the Process Coinsurance business transaction to the list of assigned business transactions.

3.11.8 Change Commission Participant

Overview

The Change Commission Participant business transaction has been mass-enabled to be executed in the Mass

Change Business Process. This allows you to change commission participant data for the Master Policy.


The following BAdIs are provided and can be implemented if required:

BAdI name Path

BAdI: User Validations for commission

participant in Master Policy

/PMG/GE_PROC_CPP_BADI

In Customizing for Policy Management, choose Policy

Management Group Enhancement → Group Insurance

Management → Basis → Master Policy Management →

Business Add-Ins (BAdIs) → BAdI: User Validations for

commission participant in Master Policy



CUSTOMER


BAdI name Path

BAdI: /PMG/GE_MBTX_EDC_STRUCT_BADI

This BAdI can be used to define the EDC

structure of the Commission and Commission

Role entity. This is a multi-use BAdI and can be

used to map the Entity with the Entity

structure.

BAdI Definition:

/PMG/GE_MBTX_EDC_STRUCT_BADI

Interface: /PMG/IF_MBTX_EDC_STRUCT

Enhancement Spot:

/PMG/GE_MBTX_EDC_STRUCT_ES

3.11.9 Perform Additional Payment

Overview

The business transactions Perform Additional Payment for benefit increase (P_L_S_CPM_IBN) and Perform

Additional Payment for shortening of policy duration are mass-enabled to be executed in the Mass Change

business process. During the processing of the business transaction, the additional payment data can be added at

the contract level.


To be able to execute perform additional payment for a product, the business transactions should be added to the

assigned set of business transactions for the product.

1. Follow the path: SAP Easy Access → SAP Menu → Policy Management → In Force Management → Product

Templates → Edit Product Templates.

2. Select the product for which the business transactions should be allowed and go to the Business Transactions

tab.

3. Add the Perform Additional Payment for benefit increase and Perform Additional Payment for shortening of

policy duration business transactions to the list of assigned business transactions.



BAdI Path

BAdI: Mass Change: Validations for Perform Additional

Payments

BAdI name: /PMG/GE_PROC_DDC_ADDPYMNT_BADI


Policy Management Group Enhancement → Group

Insurance Management → Business Process →

Business Add-Ins (BAdIs) → Mass Change→

Perform Additional Payment → BAdI: Validations for

Perform Additional Payments

64

CUSTOMER




BAdI Path

BAdI: /PMG/GE_MBTX_EDC_STRUCT_BADI

This BAdI can be used to define the EDC structure of the

additional payment, additional premium payer entity.

This is a multi-use BAdI and can be used to map the

Entity with the Entity structure.

BAdI Definition: /PMG/GE_MBTX_EDC_STRUCT_BADI

Interface: /PMG/IF_MBTX_EDC_STRUCT

Enhancement Spot:

/PMG/GE_MBTX_EDC_STRUCT_ES

Enhancement Implementation:

/PMG/GE_MBTX_ADDPYMT_EDC_EI

3.11.10 Mass Enable Relocation of Policies

Overview:

You can change a master policy and choose the option Schedule Business Transaction to mass enable the

Relocation of policies (Change of master policy assignment) on policies that belong to a master policy. The mass

transaction is available with Bus.Trans.Exec.Level = Policy.

In the input field, a new master policy number should be entered. The check boxes selection is optional. If the first

check box is selected then the derivations like (Surcharge/discount, creditor, beneficiary, limits, deductibles etc.)

will be defaulted to all the existing child policies.

If the second check box is selected, then the older derivations which are defaulted from the master policy will be

deleted.

The scheduled changes are released using the Update Policies/Contracts update run



CUSTOMER



To enable the mass change Relocation of policies functionality, the product template for the Policy Change

master policy assignment mass business transaction assigned on the Bus. Transactions tab under business


New Business Add-Ins (BAdIs):

BAdI: Enhancement Spot for Mass enablement of Relocation of policies

You can use this BAdI to set additional checks during the scheduling of mass change of Relocation of policies

(Change of Master policy assignment ). A default implementation exists to ensure mandatory fields are supplied

The BAdI name is /PMG/GE_MASS_REL_GRP_BADI.

Sample implementation name is /PMG/CL_GE_PROC_MREL_GRP_BADI.

3.11.11 Mass Enable Renewal Preparation

Overview:

You can change a master policy and choose the option Schedule Business Transaction to mass enable the renewal

preparation ( letter of invitation ) on policies that belong to a master policy. The mass transaction is available with

Bus.Trans.Exec.Level = Contract. You can either choose from one of the options (Trigger renewal or no Renewal).

If you choose the trigger renewal option, then the contract is available for renewal, and the Renewal Decision BTX

must be executed to renew the contract.


66

CUSTOMER





To enable the mass change Renewal Preparation functionality, the product template for the contract Letter of

invitation mass business transaction assigned on the Bus. Transactions tab under business process MA Mass

Change.

New Business Add-Ins (BAdIs):

BAdI: Enhancement Spot for Renewal Preparation

You can use this BAdI to set additional checks during the scheduling of mass Renewal preparation (Letter of

invitation). A default implementation exists to ensure mandatory fields are supplied

The BAdI name is /PMG/GE_PROC_RENWL_PRPTN_BADI.

Sample implementation name is /PMG/GE_MBTX_RNW_PRPTN_CHECKS.

3.11.12 Mass Enable Renewal Decision

Overview:

You can change a master policy and choose the option Schedule Business Transaction to mass enable the renewal

decision on policies that belong to a master policy. The mass transaction is available with Bus.Trans.Exec.Level =

Contract. Before executing this transaction renewal preparation Mass BTx should be executed with trigger

renewal option




CUSTOMER



To enable the mass change Renewal Preparation functionality, the product template for the contract Letter of

invitation mass business transaction assigned on the Bus. Transactions tab under business process MA Mass

Change.

3.12 Mass Processing of Open Policy Applications

3.12.1 Mass Processing

This functionality allows you to schedule mass processing of open policy applications by entering transaction

/PMG/GE_FPP_OAPPL.

An open policy application must exist in the system.

You can create policy application in Policy Management → In-Force Business Management → New Business.

68

CUSTOMER




3.13 Configuration of Master Policy Template for Multiple Mass Change Locking

Overview:

If the system configurator wants to restrict the mass change at the master policy level, he can achieve by setting

the master policy attribute ‘LOCK_MASS_CHG’.

3.13.1 Master Policy Template Configuration

The master policy template shall be enhanced with a new attribute ‘LOCK_MASS_CHG’



CUSTOMER


3.14 Execute Mass Change for a Specific Mass Change

3.14.1 Authorization for Using the Functionality

SAP Policy Management, add on for group insurance can provide the user with the authorization to a specific

activity or not.

The user will require the authorization for the

Authorization object: /PM0/FPP,

For Activity: 16

This is the same authorization that the user requires to create a FPP Run for the standard FS-PM functionality to

schedule an FPP Run if the background either immediately or with a specific date/time.

If the user is unauthorized, the button will be disabled.

3.15 Dual Control for Mass Change

3.15.1 BADI to Activate the Dual Control

SAP Policy Management, add on for group insurance can enhance, change or activate a functionality using the

BADI framework for the desired applications. This is possible where ever SAP has provided with these options by

providing BADIs to the customers which they can implement and alter the behavior of the standard system.

70

CUSTOMER




The BADI which is provided for this functionality is: /PMG/GE_MDL_DUALCTRL_ACT_BADI. This BADI is available

under the enhancement spot: /PMG/GE_MDL_DUALCTRL_ACT_ES.

This BADI is a single use BADI and there is NO default implementation from SAP. So the DUAL control will NOT be

active in the system unless the above mentioned BADI is implemented in the system.

The system configurator or a consultant can create an implementation for this BADI and decide whether DUAL

control is active for the mass change process or not. If the DUAL control is active, the BADI implementation

should provide the system name of a user who will be the approver of this mass change. This will then create a

workflow item to approve the mass change on the supplied user name from the BADI.

3.15.2 Workflow Checks

You should make sure that the agent assignment for the activity: TS 01807922 under the workflow /PMG/MDL1

should be marked as General Task like in the below Screenshot.

Make sure that the automatic workflow customization under the transaction is maintained correctly in the

transaction SWU3.



CUSTOMER


These above steps are necessary for the system to work properly for a workflow environment.

3.16 Mass Change BTX New State / Update State Operation

Overview: The new state or the update state operations for the Mass BTX are the new way of performing

operations with the BTXs. For the enablement of this functionality the system should have SAP Policy

Management, group insurance add-on 1.1 installed.

The customizations are delivered from SAP for the BTX's supported. The changes that the customer can make is

the defaulting of what type of behavior is required for the BTX's.

The customization can be maintained in the below path:

SPRO → Policy Management → Policy Management Group Enhancement → Business Processes → Mass Change

→ Set Default Action for BTX's

The customization can also be set using the transaction SM30 for the maintenance view: /PMG/GE_PMBTXACT.

Here under this customization the configurator of the system can define the default behavior of the BTX present.

From the delivery perspective, we have delivered the customization with user input, but this can be changed.

72

CUSTOMER




Note

Do not add any other BTX ID which is not delivered, as it will make the Mass change BTX behavior

unstable.

The 3 options to default are:

1. User Action: With this option the user who runs the Mass change will get a pop-up to ask if they want the New

State operation or Update State operation to be defaulted for this Mass Run for this BTX.

2. Operations (Add, Update, and Delete): With this option the system behavior will be defaulted and the end user

will get the option to Add, Update or delete the data of the single policy for which the Mass BTX is being run.

3. Operations (New state or Update State): With this option the system behavior will be defaulted and the user

will not get any options to choose the operation. And based on the BTX, it will either perform a new state

operation or an update state operation.

For reference the below BTX's are delivered with New state operation.

With the new state operation, the system will delete all the existing data for the entity for which the BTX is being

executed and then add the data the user entered during the execution of the transaction.

P_B_S_PHD_AMD: Change Policy Holder.

P_B_S_PPY_AMD: Change Premium Payer.

With the Update State operation, the system will insert the data entered by User during the execution of the

transaction if the entered data does not exist for the entity for which the BTX is being executed.

Below BTXs are delivered with Update State operation.

P_B_S_CLS_AMD: Change Clause.

P_B_S_SPMDCT_AMD: Change Surcharge/Discount.

P_B_S_DDC_AMD: Change Deductible.

P_B_S_PPD_IFR_AMD: Change Adjustment (Life, Contract).

P_B_S_COV_IFR_AMD: Change Adjustment (P&C/Non-Life, Coverage).

3.17 Group Discount Dependent on Number of Objects

Overview

In Create and Change Master Policy, you can provide a range of members to whom to apply the group discount.

In New business and Move-in, Group discount functionality is not considered.

In the Mass Change business process, you can enter a group discount in the Surcharge/discount

(P_B_S_SPMDCT_AMD) business transaction.


The following BAdI is provided and can be implemented as required:

BAdI name: /PMG/GE_NOBJ_GRP_DIS_MCHG_BADI



CUSTOMER


This BAdI can be used to define the number of objects to provide group discount during the Mass Change

business transaction Surcharge/Discount (P_B_S_SPMDCT_AMD).

Details of this BAdI are provided below:

BAdI Definition: /PMG/GE_NOBJ_GRP_DIS_MCHG_BADI

Interface: /PMG/IF_GE_NOBJ_GRP_DISC_BADI

Enhancement Spot: /PMG/GE_NOBJ_GRP_DISC_MCHG_ES

Enhancement Implementation: /PMG/GE_NOBJ_GRP_SUPDC_MCHG_EI

3.18 Correspondence

Overview

Correspondence handling is now enabled for master policy in addition to policy business processes.

The following two main parts provide the overview for the master policy functionality:

Trigger correspondence request for master policy

Retrieve relevant master policy information

3.18.1 Correspondence Request for Master Policy


A series of Customizing activities are required to enable correspondence for the master policy, as explained

below.

Custom Activity Path

Define Correspondence Types In Customizing for Cross-Application Components,

choose General Application Functions →

Correspondence → Define Correspondence Types

Define Sample Settings for Each Correspondence Type

and Role


Correspondence Management → Correspondence

Control → Define Sample Settings for Each

Correspondence Type and Role

Set FS-PM-Specific Correspondence Types In Customizing for Policy Management, choose

Correspondence Management →Correspondence

Modules → Set FS-PM-Specific Correspondence Types

Define Application Forms for Correspondence In Customizing for Cross-Application Components,

choose General Application Functions →

Correspondence → Define Application Forms for

Correspondence

Define Application Forms In Customizing for Cross-Application Components,

choose General Application Functions → Print

Workbench → Define Application Forms

74

CUSTOMER




Custom Activity Path

Manually Schedule Master Policy Correspondence In Customizing for Policy Management, choose Policy


Management → Basis → Correspondence Management

→ Schedule Master Policy Correspondence Manually

Set Technical Settings for Master Policy

Correspondence



Management →Basis → Correspondence Management

→ Set Technical Settings for Master Policy

Correspondence

Define Master Policy Correspondence Data Settings In Customizing for Policy Management, choose Policy


Management → Basis → Correspondence Management

→ Define Master Policy Correspondence Data Settings



BAdI Path

BAdI: Retrieval of Master Policy Correspondence Types

from Customizing

BAdI name: /PMG/GE_COR_MP_COR_BADI



Insurance Management → Basis → Correspondence

Management → Business Add-Ins (BAdIs) → BAdI:

Retrieval of Master Policy Correspondence Types

from Customizing

BAdI: Collection of Master Policy Data for

Correspondence

BAdI name: /PMG/GE_COR_MP_CORAP_BADI





Collection of Master Policy Data for Correspondence

BAdI: Determination of Recipient for Master Policy

Correspondence

BAdI name: /PMG/GE_COR_RECIPIENT_BADI





Determination of Recipient for Master Policy

Correspondence

BAdI: Flexible Scheduling of Master Policy

Correspondence

BAdI name: /PMG/GE_COR_CORGCPLAN_BADI





Flexible Scheduling of Master Policy Correspondence

BAdI: Check for Correctness of Correspondence

Language

BAdI name: /PMG/GE_COR_CHECK_LANG_BADI







CUSTOMER


BAdI Path

Check for Correctness of Correspondence Language

BAdI: Check for Correctness of Master Policy

Correspondence

BAdI name: /PMG/GE_COR_CHECK_BADI





Check for Correctness of Master Policy

Correspondence

3.18.2 Recurring Correspondence on Master Policy

Overview

You can schedule, view and execute periodic correspondence on a master policy. These operations consist of the

following three separate transactions:

Schedule recurring correspondence with required inputs and after scheduling view the result

View any scheduled correspondence by giving the necessary inputs

Execute the scheduled correspondence until a particular target date


To execute recurring correspondence, valid master policy correspondence types should be configured in the

system. Follow the steps as explained in section 3.18.1.

To schedule recurring correspondence based on a specific frequency, configure valid frequency types. In

Customizing for Policy Management, choose Policy Management Group Enhancement → Group Insurance

Management → Basis → Correspondence Management → Maintain recurring correspondence frequency ID

Use the BAdI Determine recurring correspondence frequency schedule to maintain the frequency identifier.


The following BAdIs are provided as part of the scheduling transaction:

BAdI name Path

BAdI: Determine recurring correspondence frequency

schedule

/PMG/GE_RCORR_FRQ_BADI



Management → Basis → Recurring Correspondence →

Business Add-Ins (BAdIs) → BAdI: Determine recurring

correspondence frequency schedule

BAdI: Additional fields for recurring correspondence

scheduling

/PMG/GE_RCORR_BADI




Business Add-Ins (BAdIs) → BAdI: Determine recurring

correspondence frequency schedule

76

CUSTOMER




BAdI name Path

BAdI: Derive transient fields for display

/PMG/GE_REC_CORR_TRANS_BADI




Business Add-Ins (BAdIs) → BAdI: Derive transient fields

for display

3.18.3 Automatic Scheduling of Correspondence at Master Policy

This functionality allows you to schedule automatic correspondence at Master Policy.


Master Policy Category for Automatic Correspondence

A new category for automatic correspondence must be created. This can be done in Master Policy Category

for Automatic Correspondence Customizing activity under Policy Management → Policy Management Group

Enhancement → Group Insurance Management → Basis → Correspondence Management → Automatic

Correspondence for Master Policy → Master Policy Category for Automatic Correspondence

Plan Automatic Correspondence for Master Policy

A new category for automatic correspondence must be created. This can be done in Plan Automatic

Correspondence for Master Policy Customizing activity under Policy Management → Policy Management

Group Enhancement → Group Insurance Management → Basis → Correspondence Management → Automatic

Correspondence for Master Policy → Plan Automatic Correspondence for Master Policy



CUSTOMER


3.19 Selection of Policies Within Given Master Policy

Overview

Selection functionality allows you to select subsets of policies that are part of a master policy. You can perform

the selection based on policy, contract, coverage, subcoverage, coverage bundle, and insured objects data. The

selection result contains all the policies which match the selection conditions together with policy, contract,

coverage, subcoverage, coverage bundle, and insured object data. The selection result set can be used to execute

mass change business processes.


Include Fields for Free Selection

The selection report has the option for the user to enter free selection criteria for main axis elements and the

corresponding objects. This customizing activity enables you to maintain the fields you want to include for

free selection.


Processes → Selection of Policies → Include Fields for Free Selection

Exit Concept for FPP

Parallel processing for Selection in background is currently set up with two parallel jobs. The number of

parallel jobs is hardcoded in class /PMG/CL_GE_GESEL_INITRUN. This class is assigned to the view Exit

Concept for FPP (FPP Exit: INIT_RUN).

This can be adjusted to meet your customer needs by implementing your own algorithm in your own class.

This class must replace the delivered class in customizing under sm30 view /PM0/ABDYFPPEXIT (for Mass

Activity /PMG/GESEL and FPP Exit INIT_RUN).

Maintenance of Interval Distribution

To create a result in the background, the object for parallelization in FPP must be maintained with a default

distribution.

This must be done in transaction /PM0/FPPOBJ → Interval Distribution → Parallel Processing Object - FPP

SELECTION.

3.20 Premium Simulation on Master Policy

Overview

Premium Simulation on Master policy enables you to simulate the premium on all the assigned policies under a

master policy as on an effective date and display simulated results in an ALV.


BAdI name: /PMG/GE_PROC_PSIM_BADI

Use this BAdI to perform customer enhancement for displaying premium simulation results.

78

CUSTOMER




3.20.1 Commission Participant Derivation

Overview: External date change Commission Participant

This functionality allows you to derive the commission participants of a master policy to its child policies. For this

a Time Model Function is created and executed via Schedule Related Dates. The child policies must be positioned

on or after the effective date to see the commission participants in the child policies. The child policies must exist

as children of the master before the date is scheduled or the TMF will not be listed under the child's planned

processing activities.



A new Time Model Function was created for commission participant synchronization. To view the new Time

Model Function created, see the Define Dates and Time Model Functions Customizing activity under Policy

Management → In-Force Business Management → Basis → Update → Time Model → Define Dates and Time

Model Functions

The new Time Model Function is to be added to an existing product module group. To do this assignment, see

the Define Execution Criteria for Time Model Functions Customizing activity under Policy Management → In-

Force Business Management → Basis → Update → Time Model → Define Execution Criteria for Time Model

Functions



CUSTOMER


The journal entry for the new Time Model Function is to be defined. To view this, see the Define Journal Entries










This is a filter BAdI so if you want to stop a scheduling of the Commission Participants time model then a new

implementation needs to be created with the filter '/PMG/COMMIS_MP' and the flag EV_TMF_SKIP is to be set

as true.

80

CUSTOMER




3.21 Simulation of Mass Run

3.21.1 BAdI /PMG/GE_ABG_MASS_SIMU_BADI: Determine package size for Mass Simulation

Overview:

A package is defined as a subset of policies for a given master policy. A package size is simply the number of

policies within a package. This BAdI determines the package size during the simulation of mass run.

During the simulation of mass run, the execution of a business transaction is performed on a master policy

and the results are displayed accordingly. If a master policy has many policies, the performance can be very

bad if the simulation is performed in one logical unit of work (LUW). Hence, for simulation we use the parallel

processing. And in each of the parallel processing tasks, simulation is performed for a certain number of

policies. The number of policies to be processed is determined from this BAdI.

The path of the configuration is:

Policy Management → Policy Management Group Enhancement → Group Insurance Management → Basis →

Master Policy Management → Simulation of Mass Run → Business Add-Ins (BAdIs) → BAdI: Determine

package size for Mass Simulation of a Business Transaction

3.22 Business Process: Reversal of Mass Change

Overview

The reversal of a mass change is done via an FPP run. Therefore, an FPP mass activity is defined with application

FS-PM and mass activity ID /PMG/MREV. The activity can be executed with the transaction /PMG/GE_RMC.

With the reversal of a mass change, you can reverse a complete mass change as well as a subset of a mass

change:

The complete mass change is considered if only a mass change name is entered in the initial screen of the

FPP run.

A subset of a mass change is considered if there are additional single policies entered or if a result set ID is

entered. In this case, the intersecting set of the entered data is determined.

In addition, the reversal of a mass change can be performed on active policies/contracts and on inactive

policies/contracts (inactive contracts can be reversed contracts or contracts with claims dependencies). For

inactive policies/contracts, the respective checkbox must be selected in the screen of the FPP run.

Note

The reversal of a mass change can be processed more than once. If all the mass changes were already

reversed by a previous run, no data will be selected regarding the selection criteria on the screen, and a

message will be displayed in the application log.



CUSTOMER


Caution

Cancellation performed by a mass change cannot be reversed by the reversal of a mass change.



BAdI Path

BAdI: Exclude reversal of a policy based on business

transaction or pending claims

BAdI name: /PMG/GE_RMC_REV

During the reversal of a mass change, inactive

contracts or contracts with dependencies to claims can

be considered.

This BAdI is provided give you the flexibility to

determine if a policy has claims dependencies or not. If

the FPP run is scheduled such that inactive contracts

are not to be considered, then the user-specified logic

will be used to check if there are any claims

dependencies for the policy. If there are any claims

dependency, then the reversal will be skipped.



Management → Basis → Master Policy Management

→ Business Add-Ins (BAdIs) → Mass Change →

Reversal BAdI: Exclude reversal of a policy based on

business transaction or pending claims

BAdI: Exclude re-implementation of a transaction in the

background

BAdI name: /PMG/GE_RMC_REDO

During the Mass Change Reversal there are scenarios

in which the changes performed on the policy after the

reversed change need to be re-implemented in the

background. In such scenarios, a BAdI has been

provided to allow you the flexibility to determine if re-

implementation of a business transaction can be

allowed in the background or not.



Management → Basis → Master Policy Management

→ Business Add-Ins (BAdIs) → Mass Change Reversal

→ BAdI: Exclude re-implementation of a transaction in

the background

3.23 Change Policy Using File Upload

Overview

This feature enables you to upload a file, extract the data from the file, process the respective business

transaction and schedule the BTS job for that business transactions based on the given target date.

The following business transaction are supported:

Change Duration: P_B_S_DRS_AMD

Create Contract: P_B_S_POLPR_CRT

Include Coverage: P_B_S_SCV_ICL

Exclude Coverage: P_L_S_SCV_EXC

A sample report has been developed which performs the operations listed above.

82

CUSTOMER





The following BAdIs are provided as part of the File Upload:

BAdI Path

BAdI: Open and Extract File for Business Transaction

Background Processing

BAdI name: /PMG/GE_FILE_EXTRACT_BADI



Insurance Management → Basis → Master Policy

Management → Business Add-Ins (BAdIs) →

Change Using File Input → BAdI: Open and Extract

File for Business Transaction Background

Processing

BAdI: Check Input Data from file to schedule BTS

BAdI name: /PMG/GE_FILE_BTX_VALIDATE_BADI



Insurance Management → Basis → Master Policy

Management → Business Add-Ins (BAdIs) →

Change Using File Input → BAdI: Check Input Data

from file to schedule BTS

3.24 Service Enablement for Master Policy and Sample Application

SAP Group Insurance Add-on provides remote function modules that you can call from a Web Service or external

application to retrieve or update the following core functional data from master policies and sample applications.

Remote

Function

Module

Function name Description

Read Master

Policy

/PMG/ABT_READ_MPOL Provides the Master Policy data. For example,

the templates, sample applications, business

partners assigned to the master policy.

Also provides a BAdI which can be used to

return custom Master Policy entities.

Create Sample

Application

Provides the number of a sample application

created from a master policy

Read Sample

Application

Metadata

/PMG/ABT_GET_SA_METADATA Provides metadata information about a

sample application. For example, the client,

the name of the sample application and the

template XML data.

Read policies

assigned to a

Master Policy

/PMG/ABT_READ_SLAVE_MPOL Provides the policies and the header data of

each policy assigned to the Master Policy for

a given effective date.



CUSTOMER


Remote

Function

Module

Function name Description

Update Master

Policy

/PMG/ABT_UPDATE_MPOL Updates individual entities within a Master

Policy. For example, you can use it to assign

additional business partners or change the

beneficiary.

3.24.1 Read Custom Master Policy Entities


BAdI: /PMG/ABT_CUST_ENT_BADI

The Read Master Policy function module also provides a BAdI which you can use to create an implementation to

read any custom entities created for the master policy.

The BAdI requires a custom implementation to retrieve the custom entities:

Importing parameters: Master Policy number and effective date.

Interface: /PMG/IF_ABT_CUST_ENT.

This implementation contains the logic to read the custom entities. The master policy number and the effective

date can be used to look up the custom entity data. The name of each entity required can be found in the changing

parameter CT_ENTITIES. Once the entity has been retrieved, remove the entity name from CT_ENTITIES.

The retrieved custom entity data needs to be appended to the changing parameter CT_RESULT. This parameter is

a generic table allowing for the use of different entities, the line type is in the form <Entity Name, Entity

Data>, where Entity Data is a structure in the form <Field Name, Field Value>.

An optional changing parameter CT_MESSAGES has been provided to transfer any required messages from the

BAdI implementation to the function module. The data from these parameters then needs to be set to their

respective exporting parameters:

Set data from CT_RESULT into ET_CUST_DATA

Set date from CT_MESSAGES into ET_MESSAGES

3.24.2 Building Web Services

1. In transaction SE80 search for the package containing the required function module.

2. Locate the function module via the path Function Groups → Function Modules.

3. Right click the function module and select Create → Enterprise Service.

The Enterprise Services Create Webservice for Function Module wizard opens to guide you through each

individual step required to create the web service.

84

CUSTOMER




4. Enter a name and description for the web service, then click Cont.

5. Select the Map Name checkbox to map the name of the function module, then click Cont.

The system completes the SOAP Application and Profile automatically.



CUSTOMER


6. Choose the required security profile for the web service, then click Cont.

7. Enter the desired package, then click Cont.

8. Click Complete.

The web service now appears in the Enterprises Services section of the chosen package.

86

CUSTOMER




3.25 Integration of Master Policy Data into BI system

The FS-PM system writes data from the following components into DELTA QUEUEs

In-Force Business Management

Object Management

Master Policy

Coinsurance

3.25.1 BI Data Formatting

Overview:

Functions involved in MASTER POLICY BI Transformation are

/PM0/ABY_FPP_BI_M

/PM0/ABY_FPP_BI_M_START

/PM0/ABY_FPP_BI_M_END

/PM0/ABY_FPP_BI_M_INTERVAL

/PM0/ABY_FPP_BI_M_JOBSTART

3.25.2 Data Sources

Data Source is an object for retrieving data. The Data Source is localized in the OLTP system. Data Sources

created for GIA tables and the corresponding Extractor’s and extract structures are as follows

Database Table Extractor (View) Data Source Extract Structure

/PMG/ABDGGEN /PMG/GE_PGEN /PMG/PM_ABDGGEN_ATTR /PMG/GE_ABT_BI_GEN_S

/PMG/ABDGGEN_EX1 /PMG/GE_PGEN_EX1 /PMG/PM_ABDGENEX1_ATTR /PMG/GE_ABT_BI_GEN_EX1_S




/PMG/GE_MPRM_GRP /PMG/GE_MPRM_V /PMG/PM_GE_MPRM_GRP_ATTR /PMG/GE_BI_MPRM_GRP_S

/PMG/GE_MPREM /PMG/GE_MPREM_V /PMG/PM_GE_MPREM_ATTR /PMG/GE_BI_MPREM_S



CUSTOMER


Transaction RSA2 for datasource

Type of extraction

88

CUSTOMER




Fields involved in the extraction are

3.25.3 SPRO Customization

Here you can enforce whether the system should format an entity in a transformation run before transferring it to

the BI system.

The following database tables are introduced with respect to GIA

/PMG/ABDGGEN

/PMG/ABDGGEN_EX1

/PMG/ABDGGEN_EX2

/PMG/ABDGGEN_EX3

/PMG/ABDGGEN_EX4

/PMG/GE_MPREM

/PMG/GE_MPRM_GRP

Make the following settings:

Table name - Name of the basis entity

Transformation Run - Indicates whether this entity should be formatted in a transformation run.

Carry forward Run - Specifies in which transformation run the entity should be formatted. There is a

transformation run for each business object. Note that the selected transformation run also belongs to the BO

model to which the entity also belongs.

Portfolio Management



CUSTOMER


Object management

Fund Management

Master policy

Coinsurance

DataSource - Name of DataSource

Extraction Structure - Name of extraction structure

Table Name Transformati

on Run

Carryforwar

d Run type

Data Source Extract Structure

/PMG/ABDGGEN Yes Master

Policy /PMG/PM_ABDGGEN_ATTR /PMG/GE_ABT_BI_GEN_S

/PMG/ABDGGEN_E

X1

Yes Master

Policy

/PMG/PM_ABDGENEX1_ATT

R

/PMG/GE_ABT_BI_GEN_EX

1_S

/PMG/ABDGGEN_E

X2

Yes Master

Policy


R


2_S

/PMG/ABDGGEN_E

X3

Yes Master

Policy


R


3_S

/PMG/ABDGGEN_E

X4

Yes Master

Policy


R


4_S

/PMG/GE_MPRM_G

RP

Yes Master

Policy

/PMG/PM_GE_MPRM_GRP_A

TTR /PMG/GE_BI_MPRM_GRP_S

/PMG/GE_MPREM Yes Master

Policy /PMG/PM_GE_MPREM_ATTR /PMG/GE_BI_MPREM_S

90

CUSTOMER




3.26 Log of Changes - Master Policy

3.26.1 Customizing

If a new custom generic entity has been developed by the customer, then to include this generic entity as a part of

log of changes, the following customizing needs to be maintained:

SPRO → Policy Management → Policy Management Group Enhancement → Group Insurance Management →

Basis → Master Policy Management → Log of Changes for Master Policy → Include Generic Entities in Log of

Changes for Master Policy

The following are the descriptions of the fields of customizing:

Field Name Description

Master Policy Module ID The field must corresponds to the entity mentioned in

SPRO:


Insurance Management → Basis → In-Force Business

Configurator → Define Master Policy Module ID

Group name The field is an alias part of channel structure of generic

entity, which is /PMG/ABCGGEN.

Table Name The DB table name in which the custom generic entity

is stored.



CUSTOMER


3.26.2 BAdI /PMG/GE_ABG_MX_CHN_LOG_BADI: Non Generic Custom Entities

Overview:

If a new custom non generic entity has been developed in master policy, then to enable its comparison, you

must implement the BAdI /PMG/GE_ABG_MX_CHN_LOG_BADI.

The following are the details of the BAdI:

The BAdI name is /PMG/GE_ABG_MX_CHN_LOG_BADI.


Management→ Basis → Master Policy Management →Log of Changes for Master Policy → Include Non

Generic Entities in Log of Changes for Master Policy

The following are the BAdI methods to be implemented:

COMPARE

This method uses parameter IR_CHNG_API to get the changed master policy data and IR_BASE_API to get

the base master policy data. After performing the comparison of non-generic custom entities, write the log to

CT_LOG and CT_LOG_ITEM. The parameter CT_LOG contains what entity instances have been created,

updated or deleted. The parameter CT_LOG_ITEM contains data of the fields before and after change. A line in

CT_LOG corresponds to one or more CT_LOG_ITEMS. And the records between CT_LOG and CT_LOG_ITEM

are linked by log ID.

3.27 Top Level Grouping

This functionality allows you to create and maintain a group of master policies. This is done by enhancing the

master policy structures with a new field to create a relationship.


Define Grouping of Master Policies

A new relationship between master policies has been created. This relationship can be defined in Define

Grouping of Master Policies Customizing activity under Policy Management → Policy Management Group

Enhancement → Group Insurance Management → Basis → Master Policy Management → Grouping of Master

Policies → Define Grouping of Master Policies

92

CUSTOMER




3.27.1 BAdI: MMP Root Entity Fields Selection

This BAdI has been provided to allow for the selective copy of fields from the MMP MPO entity to the CMP MPO

entity. It has a filter of Business Process ID, meaning that different implementations can exist in parallel for both

the 'Create CMP' and 'Change MMP of a CMP' scenarios.

BAdI Name: /PMG/GE_MPO_FIELDS_SEL_BADI

SAP Policy Management, add on for group insurance can implement BAdIs via the transaction SPRO.


Management → Basis→ Master Policy Management → Top Level Grouping → BAdI: Determine the Top Level MPO

fields to be copied to the Child MP

The following BAdI method is to be implemented:

SET_FIELDS

Available in this method is the root MPO entity data of the MMP, along with a table structure of the MMP fields

and a flag field. The MMP data can be analysed and the table of fields looped through to mark the field for

copy or not, this will feed into the copy process and mean that only the fields specified in the BAdI are

considered for copy. The default implementation is to copy all fields from MMP to CMP.

3.27.2 BAdI: MMP Generic Entity Selection

This BAdI has been provided to allow for the selective copy of generic entity data from the MMP to the CMP.

Again, like the above BAdI, there are filters available; in this BAdI they are the Business Process ID, along with the

MPol Mod ID, which is essentially the generic entity type. This means that different implementations can exist for

each generic entity, and multiple implementations can exist in parallel for the same generic entity for use in the

'Create CMP' and 'Change MMP of a CMP' scenarios



CUSTOMER


BAdI Name: /PMG/GE_MMP_ENTITY_SEL_BADI



Management → Basis→ Master Policy Management → Top Level Grouping → BAdI: Determine generic entities to

be copied from Top Level MP to Child MP


SET_ENTITY_STATUS

This method will contain the root MPO entity data of both the MMP and CMP, along with the set of generic

entity data from the MMP. This allows you to make a decision about whether the generic entity in question

should or should not be skipped during the copy process. The parameters available for change in the method

will determine whether the entity should be skipped, and whether it will not be skipped, whether the copy

process to the CMP should be an overwrite or an append (Change MMP scenario).

3.27.3 BAdI: Copy Non-Generic Entities

Overview:

A new BAdI has been provided to copy non-generic entities from the master policy to the master policy

application and vice versa.

The following are the details of the BAdI:

The BAdI name is /PMG/GE_ABG_MA_BADI.


Management→ Basis → Master Policy Management →Master Policy Application →BAdI: Copy non generic

entities.

The following are the BAdI methods to be implemented:

GET_ENTITY_DATA_SRC

Get the entity from the source master policy or application. And store the entity to be copied in the buffer.

This buffer should be created by the developer in the relevant BAdI implementation class.

SET_ENTITY_DATA_TRG

Read the buffer set in method GET_ENTITY_DATA_SRC, and set those entities in the target master policy or

application.

3.27.4 BAdI: MMP Reversal

This BAdI has been provided to allow for the execution of custom code before an attempt to reverse an MMP is

carried out. An MMP cannot be reversed if there are active Child MPs associated with it, so this BAdI call gives the

customer an opportunity to implement custom code to reverse the Child MPs and the Single Policies under them

before the MMP reversal is attempted.

94

CUSTOMER




BAdI Name: /PMG/GE_REVERSE_MP_BADI



Management → Basis→ Master Policy Management → Top Level Grouping → BAdI: Enhancement spot for Top

Level MP Reversal process


REVERSE_CHILDREN

This method will have the MP number of the MMP to be reversed available for use, and also provided a table of

log messages for export that allows the user to add the log messages created during the process for use in

determining whether the reversal process should continue.

3.27.5 FPP Run

Create a mass activity /PMG/MMPSY in View Cluster /PM0/VC_FPP_XCUST (Tx: SM34). The start of job function

module /PMG/GE_FPP_MMP_JOBSTART sets up the parallelization object. The interval module function module

/PMG/GE_FPP_MMP_INTERVAL runs on each interval set.

The generic data structure should be /PMG/GE_MMP_FPP_FIELDS_S, this holds MMP data to pass to each

interval.

The application log object is /PM0/FPP and sub-object is /PM0/SUB.

The parallel processing object is /PMG/CL_GE_MMP_FPPINT.

www.sap.com/contactsap


No part of this publication may be reproduced or transmitted in any

form or for any purpose without the express permission of SAP SE

or an SAP affiliate company.

SAP and other SAP products and services mentioned herein as well

as their respective logos are trademarks or registered trademarks of

SAP SE (or an SAP affiliate company) in Germany and other

countries. All other product and service names mentioned are the

trademarks of their respective companies. Please see

http://www.sap.com/corporate-

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

information and notices.

Material Number:

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

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

sap policy management, group insurance add-on 1 · sap policy management, group insurance add-on...

Documents