SAP Policy Management 5 - SAP Help Portal part of the documentation provides details about the planning for an upgrade of SAP Policy Management from FS-PM 5.3 to ... of FS-PM 5.4 is

Upgrade Guide

SAP Policy Management

Document Version: 1.0 – 2017-04-27

CUSTOMER

SAP Policy Management 5.4 Component Upgrade Guide

2

Customer

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

SAP Policy Management 5.4

Typographic Conventions

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 .


Document History

CUSTOMER

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

Document History

Version Date Change

1.0 2017-04-27 First version of this guide

4

CUSTOMER



Table of Contents

Table of Contents

1 Introduction ............................................................................................................................. 6 1.1 About this Document ...................................................................................................................... 6 1.2 Before You Start .............................................................................................................................. 7

1.2.1 Naming Conventions ....................................................................................................... 7 1.2.2 SAP Notes for the Upgrade ............................................................................................. 8

2 Quick Guide ............................................................................................................................ 10

3 Planning .................................................................................................................................. 12 3.1 Required Documentation ...............................................................................................................12

3.1.1 Release Notes .................................................................................................................12 3.1.2 Operational System ........................................................................................................12 3.1.3 Documentation about Product Engine msg.PM .............................................................12

3.2 Upgrade Schedule ......................................................................................................................... 13 3.3 Upgrade in a System Landscape ................................................................................................... 13 3.4 Modifications ................................................................................................................................. 13 3.5 Checking Software and Hardware Requirements......................................................................... 14

3.5.1 Software Requirements ................................................................................................. 14 3.5.2 Hardware Requirements ............................................................................................... 14

3.6 Importing Additional Languages ................................................................................................... 14 3.7 msg.PM Upgrade Schedule ............................................................................................................15

3.7.1 Introduction ....................................................................................................................15 3.7.2 Required Documentation ...............................................................................................15 3.7.3 Software and Hardware Requirements ..........................................................................15

3.8 Data Migration Planning .................................................................................................................15 3.8.1 XPRAs ............................................................................................................................ 16 3.8.2 Migration Programs ....................................................................................................... 16

4 Upgrade Process .................................................................................................................... 17 4.1 Important SAP Note 2601538 ........................................................................................................ 17

5 Follow-Up Activities ............................................................................................................... 19 5.1 Upgrade and Adjustments to msg.PM .......................................................................................... 19

5.1.1 Installation of msg.PM Designer Rel. 3.4.13.0 ............................................................... 19 5.1.2 Updating the Customer Content ................................................................................... 19 5.1.3 Updating the Reference Model ...................................................................................... 20 5.1.4 Creating the Compilate ...................................................................................................21 5.1.5 Updating the msg.PM Connection .................................................................................21

5.2 Data Migration - XPRAs ................................................................................................................. 22 5.3 Steps before Live Operation .......................................................................................................... 23

5.3.1 Field Modifier Checks in Change RFCs .......................................................................... 23 5.3.2 Starting Customizing Activity Optimize Serialization Runtime .................................... 23 5.3.3 Customizing Comparison .............................................................................................. 24 5.3.4 Modification Comparison .............................................................................................. 25


Table of Contents

CUSTOMER


5.3.5 Business Partner Integration ......................................................................................... 25 5.3.6 Conversions in RFMs ..................................................................................................... 25

5.4 Steps during Live Operation .......................................................................................................... 26 5.4.1 Generating Authorization Profile ................................................................................... 26 5.4.2 Testing the Application .................................................................................................. 26

6 Troubleshooting .....................................................................................................................28 6.1 Support .......................................................................................................................................... 28

6.1.1 SAP Policy Management Support ................................................................................. 28 6.1.2 Further Information ....................................................................................................... 28

6.2 Uninstalling SAP Policy Management 5.4 ..................................................................................... 29

7 Appendix ................................................................................................................................ 30 7.1 Program /PM0/ABP_MIG_53_54_003 ........................................................................................ 30 7.2 Program /PM0/ABP_MIG_53_54_002 ........................................................................................ 30

6

CUSTOMER



Introduction

1 Introduction

1.1 About this Document

Caution

Before you start, make sure that you have the latest version of this document. You can find the latest

version of the Upgrade Guide at SAP Policy Management -> Installation and Upgrade -> Upgrade Guide.

Purpose

This documentation describes the upgrade procedure from SAP Policy Management 5.3 to 5.4 and also provides

you with additional information concerning the upgrade.

The information contained in this documentation is targeted toward SAP system administrators with knowledge

of the operating system, database and the SAP basis.

The four sections below explain the procedure for upgrading to FS-PM 5.4. These sections give you an overview of

the steps required before, during, and after the upgrade.

The Quick Guide section gives you an overview of the required activities listed in these sections.

In the Troubleshooting section you will find supplementary information about the support or correction of known

problems.

Integration

For more information about the prerequisites of the upgrade from SAP Policy Management from 5.3 to 5.4, see

see SAP Note 2412645

You define the insurance products in an external product engine. These insurance products serve as the basis for

the use of the in-force business management system, SAP Policy Management. If you use msg.PM as product

engine, you must also upgrade the design component (msg.Designer), the runtime environment (msg.TOMATOS)

and the sample content. The required steps are described below.

If you use SAP Product Lifecycle Management for Insurance (FS-PRO) or a different product engine, you can skip

these sections.

Constraints

This documentation applies only to the upgrade of an SAP Policy Management 5.3 system to a 5.4 system.

In addition to this documentation, you will also require information, such as the release information, the SAP

Implementation Guide (IMG), specific notes for this upgrade and other documents. References are made to this

documentation where necessary.

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

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


Introduction

CUSTOMER


This guide does not provide:

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

• Installation and Customizing information for the product engine FS-PRO

• Configuration information for the Print Workbench

• Installation and Customizing information for SAP Policy Management

1.2 Before You Start

1.2.1 Naming Conventions

Terminology

Term Description


(Abbreviation: FS-PM)

Official product name for SAP Policy Management

FSPM Name of the software component, for use in the

namespace

SAPK-540XXINFSPM Names the component and the version for searching

for notes on installation in SAPNET.

For notes about Support Packages, the characters

XX are replaced by the number for the Support

Package, for example search for notes on Support

Package 01 ->

SAPK-54001INFSPM.

Other search terms • Upgrade

• Release strategy

• Release planning

• Overview note

• Release

• End of support/maintenance

Variables

Variables Description

<SAPSID> SAP system ID in uppercase letters

8

CUSTOMER



Introduction

Variables Description

<sapsid> SAP system ID in lowercase letters

<DBSID> Database system ID in uppercase letters

<dbsid> Database system ID in lowercase letters

<SAINT_INSTDIR> Installation directory for the SAP installation tool

SAINT

<INSTDIR> Installation directory for the SAP system

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

<OS> Operating system name within a path

The following examples show how the variables are used:

Example

Log on as user <sapsid>adm and change to the directory /usr/sap/<SAPSID>.

If your SAP system ID is C11, log on as user c11adm and change to the directory /usr/sap/C11.

1.2.2 SAP Notes for the Upgrade

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

information on the upgrade, as well as corrections to the upgrade documentation.

Make sure that you have the up-to-date version of each SAP Note, which you can find on SAP Support Portal at

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

Important additional information for the SAP Policy Management 5.4 delivery

SAP Note Number Title

2412645 Release strategy for ABAP add-on FSPM 540

2428681 Release Information Note (RIN) for FSPM 540

2513585 Potential DDIC objects and data loss during upgrades

to NetWeaver 7.50 or higher

2601538 Correction for XPRA /PM0/ABP_MIG_53_54_003

https://support.sap.com/notes




https://launchpad.support.sap.com/#/notes/2601538


Introduction

CUSTOMER


Notes about installation of and connecting to msg.PM Product Engine


718815 msg.PM connection: Permitted combinations of FS-

PM and msg.PM (Release/SP)

2151449 Release strategy for ABAP add-on MSGPMCON

2435410 Download msg.PM from SAP Service Marketplace for

FS-PM 5.4

Official SAP notes about add-ons


33040 Options in exchange upgrade with Add-On

70228 Add-Ons: General conditions

160168 Support Packages for SAP Add-Ons







10

CUSTOMER



Quick Guide

2 Quick Guide

You use the tables in the following sections as checklists to navigate through the configuration after an upgrade of

your SAP system.

Use the links to the general descriptions of the actions and to any additional information to help you perform the

actions. This prevents you missing important information.

This section includes all activities necessary for planning, preparing, performing, and following up the upgrade. It

is not intended to replace the Component Upgrade Guide SAP Policy Management, since it does not include all the

information relevant to the upgrade.

Planning

Careful planning is a prerequisite for the successful upgrade of the system.

✓ Activity

Required Documentation

Upgrade Schedule

Upgrade in a System Landscape

Modifications

Checking Software and Hardware Requirements

Importing Additional Languages

msg.PM Upgrade Schedule

Data Migration Planning

Preparation

You can find the required activities in the Upgrade Master Guide for SAP NetWeaver 7.5, SP06 (or higher). For

more information about the SAP NetWeaver upgrade, see SAP NetWeaver 7.5 -> Installation and Upgrade ->

Upgrade and update guides for SAP NetWeaver 7.5.

Upgrade Process

✓ Activity

SAP Policy Management Upgrade

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

https://help.sap.com/viewer/disclaimer-for-links?q=http%3A%2F%2Fservice.sap.com%2F~sapidb%2F012002523100015877482015E


Quick Guide

CUSTOMER


Follow-Up Activities

✓ Activity

Upgrade and Adjustments to msg.PM

Data Migration

Error! Reference source not found.

Steps during Live Operation

12

CUSTOMER



Planning

3 Planning

This part of the documentation provides details about the planning for an upgrade of SAP Policy Management

from FS-PM 5.3 to FS-PM 5.4. Before you can start the upgrade, you need to have carried out careful planning. It

is absolutely vital that you read the following notes.

A successful upgrade relies heavily on exact planning. The following information will help you avoid loss of data

and avoid manual adjustments to the system after the upgrade is complete, resulting in the most effective

configuration possible.

Caution

Make sure that there are no users logged on to the system during the upgrade.

If users are logged on during the upgrade, data inconsistencies or longer runtimes could result.

3.1 Required Documentation

3.1.1 Release Notes

The release notes for SAP Policy Management 5.4 describe the new scope of features provided by this release.

They also contain information regarding Customizing or other adjustments that are required to enable the new

range of features. For more information, see SAP Policy Management -> What's New.

3.1.2 Operational System

The SAP Policy Management upgrade requires an integrated upgrade of the operational system. The prerequisite

of FS-PM 5.4 is SAP ERP 6.0, enhancement package 7, SP12 (or higher).

3.1.3 Documentation about Product Engine msg.PM

You require the following documents to prepare and execute the installation of Product Engine (msg.PM) and

connecting it to FS-PM. Technical Customizing is also described.

• Documentation msg.ProductManager User Guide

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

• Documentation msg.ProductManager Technical Overview



Planning

CUSTOMER


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

• Documentation msg.ProductManager Installation Guide

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

• Documentation msg.ProductManagerAdministration Guide

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

• Documentation Product Management System msg.PM (TomatosX)

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

• Documentation Remote Administration of TomatosX

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

Note

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

msgPM\Documents\

3.2 Upgrade Schedule

A written schedule should be available so that the upgrade can be performed successfully and on time. You need

to define in advance which objectives you want to pursue for the upgrade, for example, minimizing the required

resources or downtime.

Note

You can find a detailed description about the procedure for the creation of a schedule (with key issues to

consider and examples) in the Upgrade Master Guide for SAP NetWeaver 7.5.

When creating a schedule, you also need to consider the upgrade of the product engine.

3.3 Upgrade in a System Landscape

If more than one SAP system is affected by the upgrade, for example, a live system and a development system,

you need to consider the entire system landscape. You should carry out the upgrade of your systems in the same

way as you carry out the transport for modifications.

Note

You can find notes regarding an upgrade in a system landscape in the Upgrade Master Guide for SAP

NetWeaver 7.5.

3.4 Modifications

If the upgrade affects a modified system, we suggest that you first test the upgrade on a test system with identical

configuration (installation and modifications).

14

CUSTOMER



Planning

When you perform the upgrade, all modifications you have made to the objects in the SAP name space that are

inconsistent with changes for SAP are lost. The SAP objects in the standard system are overwritten with the new

functions included in the upgrade. The modification adjustment allows you to enter the modifications in the

relevant new upgrade objects.

If you have modified SAP objects that you want to keep, you first need to adjust the test system and perform the

upgrade of the live system afterwards. A complete record of the changes exists only in the version management

of the SAP system in which the modifications were performed, that is to say in the development system. Only this

SAP system optimally supports an adjustment of the modifications. The adjustments made there after the

upgrade can be automatically transferred to your other SAP systems. You do not have to perform a time-

intensive manual adjustment to the live system if you follow this procedure.

Note

For more information, look for Changing the SAP Standard (BC) under SAP NetWeaver 7.5.

3.5 Checking Software and Hardware Requirements

3.5.1 Software Requirements

The requirements for FS-PM are listed in SAP Note 2412645.

3.5.2 Hardware Requirements

The hardware requirements for the upgrade of SAP Policy Management can be found in the Upgrade Master

Guide for SAP NetWeaver 7.5.

3.6 Importing Additional Languages

During the upgrade process, you can only update existing languages. You cannot install new languages as part of

the upgrade. However, you can define new languages before you perform the upgrade in the system (transaction

SMLT) so that they too are imported during the upgrade.

For more detailed information regarding this procedure, see SAP Note 322982 and the Upgrade Master Guide for

SAP NetWeaver 7.5.





Planning

CUSTOMER


3.7 msg.PM Upgrade Schedule

3.7.1 Introduction

You develop insurance products outside the policy management system in a product engine. The product data

defined here (contents, structures, rules, calculations and processes used to describe the products) represents

the product knowledge that is used to manage the contracts that are based on the products.

The sample products that are delivered with SAP Policy Management 5.4 were developed using msg.PM Product

Engine.

3.7.2 Required Documentation

See the documents listed in Documentation about Product Engine msg.PM (see Documentation about Product

Engine msg.PM)

3.7.3 Software and Hardware Requirements

Use the current situation, as described in SAP Note 718815, to clarify which combination of SAP Policy

Management Release/SP and msg.PM Product Engine you want to install.

Ensure that you use the currently valid version of msg.PM and the Compile plug-in respectively.

If you require an updated version of msg.PM Product Engine, you can download the required version from SAP

Service Marketplace. See SAP Note 2435410 for details.

3.8 Data Migration Planning

The programs for the data adjustment are differentiated according to their requirements for execution. The ability

to execute programs automatically as part of the upgrade is known as XPRAS (EXecution of PRogram After

Import). If a program requires you to perform activities manually before execution, which effectively requires a

manual start, it is known as a migration program.

Caution

Archived data is not migrated.



16

CUSTOMER



Planning

3.8.1 XPRAs

Name Tables Affected Description

/PM0/ABP_MIG_53_54_003 /PM0/ABUCIBCATTR For more information, see Program

/PM0/ABP_MIG_53_54_003.

Caution: See also chapter

Important SAP Note 2601538.

Note

See the appendix for more detailed documentation of the above XPRAs.

3.8.2 Migration Programs

Name Tables Affected Description

/PM0/ABP_MIG_53_54_002 /PM0/ABDTTRANS For more information, see Program

/PM0/ABP_MIG_53_54_002.


Upgrade Process

CUSTOMER


4 Upgrade Process

SAP Policy Management Upgrade

The SAP Policy Management upgrade requires an integrated upgrade of the operational system. The prerequisite

of FS-PM 5.4 is SAP ERP 6.0, enhancement package 7, SP12 (or higher).

You can find all details regarding the upgrade of the basis components in the Upgrade Master Guide for SAP

NetWeaver 7.5.

Consult the notes mentioned in the SAP Notes for the Upgrade section for the different upgrade phases,

especially for the upgrade of SAP Policy Management.

UPLOAD_REQUEST Phase

The UPLOAD_REQUEST phase prompts you to provide all required upgrade packages for the add-on upgrade in the

appropriate folder.

The following activities are required for SAP Policy Management:

No. Key Word Action

1. Make SAP Policy Management available Insert and mount (on Unix) the Add-On Upgrade CD.

2. Log on as Admin Log on as user <SAPSID>ADM.

3. Switch to transport folder Go to directory <CD>\FSPM\UPGR.

4. Unpack archive Unpack the SAR archive IFSPM500.SAR on the DVD with

the following command:

SAPCAR -xvf /<DVD_DIR>/DATA/ K-

500BGINFSPM.SAR (in UNIX).

5. Check unpacked archive Check whether the unpacked Add-On is in the EPS inbox of

your transport directory

(\usr\sap\trans\EPS\in).

4.1 Important SAP Note 2601538

Caution

The following paragraph only applies if you upgrade to FS-PM 5.4, SP00 or FS-PM 5.4, SP01.

The XPRA /PM0/ABP_MIG_53_54_003 contains an error and does not run correctly in the upgrade

process.

Due to that you must implement the SAP Note 2601538 during the upgrade process. If you do not know

how to do this we strongly recommend to contact SAP.


18

CUSTOMER



Upgrade Process

If you implement the SAP Note 2601538 during the upgrade process the XPRA will be executed and the

data will be transferred correctly. We strongly recommend to perform the upgrade process only this way.

In case you have already performed the upgrade, you must follow the instructions in the SAP Note

2601538. If you have any doubts contact SAP.





CUSTOMER


5 Follow-Up Activities

5.1 Upgrade and Adjustments to msg.PM

5.1.1 Installation of msg.PM Designer Rel. 3.4.13.0

First, stop all msg.PM Designer Server services on the system on which you want to install msg.PM Designer

3.4.13.0. You do this by starting the msg.PM Designer Server monitor application and choosing Stop on the Server

Settings tab. Close the application after you receive the message to stop the services.

Copy the installation files for msg.PM Rel. 3.4.13.0 from the installation folder of your SAP Policy Management 5.4

CD to the hard drive that has been providing the version of msg.PM Designer that you use.

Note

For a thorough description of the msg.PM Designer upgrade procedure, consult the msg.ProductManager

Installation Guide, section 7 Upgrade Installation and section 8 Update Installation. (see Documentation

about Product Engine msg.PM3.1.3).

After you have migrated the msg.PM Designer application, we recommend that you save the databases for

msg.PM Designer with the sample content for FS-PM 5.3 and with the product definitions before you perform the

update of the sample content for FS-PM 5.4.

5.1.2 Updating the Customer Content

Step 1: Updating the Sample Content

Again, to update the sample content from FS-PM 5.3 to FS-PM 5.4, we recommend that you first save the

database(s) for msg.PM Designer with the sample content from FS-PM 5.3 and the associated product

definitions.

✓ Activity

Stop all msg.PM Designer services using msg.PM Designer.Server.Monitor.

Copy msg.PM Designer installation file on the msg.PM Designer server.

Save msg.PM Designer databases.

Install msg.PM Designer server Release 3.4.13.0.

Import sample content 5.4 compilate to a workspace (including reference model).

20

CUSTOMER




✓ Activity

Import sample content 5.4 compilate to a new workspace (including reference model).

Note

To do this, consult the documents included with the DBMS you use and the instructions for saving a

database.

The procedure for creating an import to msg.PM Designer and for importing a compilate to the workspace

is described in the msg.ProductManager User Guide, section 6.2 Imports (see Documentation about

Product Engine msg.PM).

Step 2: Updating the Customer Content

Using the sample content imported in step one, refer to the task IDs to see which changes were made in the

sample content in 5.4. The technical changes mentioned there have to be done manually in the customer content.

Refer also to the sample content release notes to find out which other changes need to be done.

✓ Activity

Refer to the Release Notes and make any required changes to the customer content.

Refer to the task IDs and make at least all changes marked as “technical” to the customer content.

Fill out reference model in SAP Policy Management.

Import of reference model from SAP Policy Management in msg.PM Designer.

Export of workspace/compilate creation.

5.1.3 Updating the Reference Model

After you have successfully performed the upgrade of your content, you need to update the reference model.

Here you are required to first fill out the reference model tables.

Using the toolkit for the msg.PM connection (transaction /PM0/ABR_TOOLKIT), you transport meta information

to the reference model tables /MSG/4_APPL, /MSG/4_APPLT, /MSG/4_TABLE and /MSG/4_TABLEFLD.

You start filling out the data by choosing Fill Reference Model Tables.

Input data:

• Name of application

• Name of model

The transaction is triggered when you choose Start Filling of Reference Model Tables.

You can access the functionality for the reference model export also using the toolkit for the msg.PM connection

(transaction /PM0/ABR_TOOLKIT).

You trigger the export by choosing Export Reference Model.



CUSTOMER


Note

Ensure that you read the documentation for the reference model export in the msg.ProductManager

Administration Guide, section 3.3 Reference Model Export (see Documentation about Product Engine

msg.PM).

5.1.4 Creating the Compilate

If applicable, create a distribution of your development workspace and ensure that the workspace contains the

reference model that was imported earlier. Then create an export object and define the target folder to which you

want to save the compilate. Optionally, you can make settings to also create an optimized runtime compilate.

Note

For more information regarding the creation of an export object and the export of a workspace, see the

msg.ProductManager User Guide, section 6.1 Exports (see Documentation about Product Engine

msg.PM).

5.1.5 Updating the msg.PM Connection

After the update of the msg.PM Designer application has been completed successfully, as well as the SAP Policy

Management sample content, you need to update the connection to the Product Engine.

The following activities are required to do this:

✓ Activity

Determine Language for Call of Product Engine

Upgrade of runtime environment

Customizing Activities

You determine the language for the product engine in Customizing for SAP Policy Management under Policy

Management → Integration → Product Engine → Connection with msg.PM → Determine English Language for Call

of Product Engine (msg.PM)

Note

You can find a detailed description of the runtime environment in the msg.ProductManager

Administration Guide (see Documentation about Product Engine msg.PM).

22

CUSTOMER




5.1.5.1 Upgrade of Runtime Environment

Before you perform the upgrade, you must first stop the msg.PM runtime server PM.TOMATOSX. Otherwise the

compilate files will still be in use, making it impossible to perform the replacement.

If you left the live XML configuration file and the start file (batch file) for the configuration of the runtime with the

original name for the example data (delivered with the installation of msg.PM runtime environment), save these

files before you perform the upgrade. Otherwise these files may be overwritten. These files must be copied after

the update to the folder from which they were taken.

Now extract the version 3.4.13.0 of the runtime from the provided zip file to a temporary folder. Copy the new files

from the temporary folder to the folder in which the previously used runtime environment was saved and confirm

the overwriting of the existing files.

If necessary, change the file names of the configuration files and/or start files. Make sure that the configuration

accesses the new start file for the runtime environment.

5.2 Data Migration - XPRAs

This XPRA program (see Documentation about Product Engine msg.PM3.8.1 ) is executed automatically during

the upgrade process. After the upgrade, you need to check the contents of the status table /PM0/ABTMSTATE

(status for migration programs). Each XPRA records the success or status of the migration run in this table.

Explanation of status in the table /PM0MSG/ABTMSTATE:

• S = The migration was executed successfully. You are not able to run the program again.

• W = Warning: the migration was not performed due to warnings. The program must be executed again

manually. Check the logs that are output from the respective manual execution.

If a program returns a warning, you need to check and resolve the messages in the logs. Furthermore, if

applicable, you need to check the data in the table you want to migrate. You can start the program again

manually.

Note

Before executing the XPRAs, see also the related documentation in the appendix.



CUSTOMER


5.3 Steps before Live Operation

5.3.1 Field Modifier Checks in Change RFCs

The system runs checks when it uses remote function modules (RFM Function Group /PM0/*SVC_CHANGE) to

execute business transactions from the Change business process. These checks are run to ensure that fields are

not changed if the same fields are not input enabled in the corresponding business transaction on the SAP GUI.

These checks are based on the current status of the application and the static and dynamic settings. To achieve

this, anything in FS-PM that influences the field control of a business transaction field is considered. Examples of

what could influence the field control:

o IFBC settings

o Logic implemented in Subcontroller classes

All activities to ensure field modifier checks for Change RFCs are described in the How-to Guide Guide for

Implementing Business Transactions, under the chapter Field Modifier Checks (see SAP Policy Management ->

How-to Guides -> Guide for Implementing Business Transactions).

If you have changed the field control of a business transaction in your installation or if you have implemented

additional remote-enabled business transactions, you need to follow the procedures in the How-to guide to

ensure that customer-specific field control from dialog are executed in change RFMs also.

If your changes to the field control in the business transaction are not made according to the description in the

How-to guide, the customer-specific logic cannot be considered during the RFM execution and invalid input data

cannot be identified.

If you followed the procedure for the field modifier checks according to the How-to guide, the execution of the

change RFMs may now return error messages that were not returned before you upgraded to SAP Policy

Management 5.4. In this case, and when you execute unchanged RFMs provided by SAP, you need to correct the

input data of the change RFM.

5.3.2 Starting Customizing Activity Optimize Serialization Runtime

In Customizing for SAP Policy Management, choose Policy Management -> Integration -> Product Engine ->

Connection with msg.PM -> Optimize Serialization Runtime.

You use this Customizing activity to generate the class ZCL_ALH_PM_CALCULATION_GEN in the customer

namespace. This class evaluates the data in the product management system more quickly,

which significantly improves the runtime of all calls in the product management system.

You execute this report after you have filled the reference model tables in the Customizing for Policy Management

(see Updating the Reference Model).

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

24

CUSTOMER




5.3.3 Customizing Comparison

5.3.3.1 Copy of Sample Customizing to Customer Clients

The sample Customizing delivered with SAP Policy Management 5.4 is imported during the upgrade only to client

000.

In most cases, it is recommended that the sample Customizing is copied to the live clients.

See SAP Note 337623 for further information.

Caution

If you want to copy the complete sample Customizing, the names of the individual RFM connections are

overwritten in the Customizing activity Policy Management → Integration → Process Primary Settings for

Interfaces to External Systems. If applicable, change the name of the RFM connection after you have

copied the sample Customizing.

5.3.3.2 Manual Comparison of Sample Customizing

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

modifications or enhancements are overwritten when copying the Customizing entries.

If you want to copy the sample Customizing for FS-PM 5.4, you must first compare the sample Customizing from

client 000 with the Customizing for the customer client. You can do this with the Customizing Cross-System

Viewer.

You access the Customizing Cross-System Viewer using transaction SCU0, or from SAP Easy Access screen under

Tools → Customizing → Customizing Cross-System Viewer.

5.3.3.3 Maintenance of Number Range Intervals

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

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

Caution

There are no new number range objects in FS-PM 5.4.

You must maintain all other required number range intervals in the source system. You can find a list of all

number range intervals relevant for FS-PM 5.4 in the Installation Guide for SAP Policy Management at

SAP Policy Management -> Installation and Upgrade -> Installation Guide (chapter 3.2.6).





CUSTOMER


5.3.4 Modification Comparison

If the upgrade involves a modified system, you may need to reestablish the modifications that you want to keep by

using the modification comparison.

Note

For more information, look for Changing the SAP Standard (BC) in the documentation of SAP

NetWeaver at SAP NetWeaver 7.5.

5.3.5 Business Partner Integration

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

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

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

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

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

BUPA_SEARCH selects business partners by address data only. To ensure that the search help takes the relevant

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

search help that is no longer required.

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

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

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

remote system that contains the FS-BP component. Then, open transaction SM30 in the remote system. Select

the table BAPIF4T and define an authorization module for the following values:

Object Type Verb Data element Function name

BUS1006 <customer module>

BUS1006 GETDETAIL <customer module>

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

module>). This function module provides the interface. Copy this function module.

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

5.3.6 Conversions in RFMs

SAP Policy Management provides conversion exits for only the application number parameter of remote-enabled

function modules (RFMs) in the standard system. However, the following RFMs previously had conversion exits


26

CUSTOMER




for other parameters (e.g. Insurable Object Number, External Object Number). To be consistent, the conversion

exits have been removed. If needed you may create conversion exits for these RFMs.

• Create Insurable Object (/PM0/ABT_SVC_IO_CREATE)

• Read Insurable Object (/PM0/ABT_SVC_IO_READ)

• Find Master Policy (/PM0/ABT_SVC_MPO_FIND)

• Retrieve Insurance Policy (/PM0/ABT_SVC_POL_READ)

• Execute Sales Product Change (/PM0/ABT_SVC_SALESPC)

• Read Change Request for an Insurance Policy (/PM0/ABT_SVC_CHGREQ_RTRV)

In addition, SAP Policy Management will not provide the conversion function to convert the currency-dependent

field from internal format to external format in RFMs. Currency format conversion has been removed from the

following RFMs:

• Read Change Requests (/PM0/ABT_SVC_CHGREQ_RTRV)

• Read Insurance Policy (/PM0/ABT_SVC_POL_READ)

• Execute Sales Product Change (/PM0/ABT_SVC_SALESPC)

• Create Change Request (/PM0/ABT_SVC_CHGREQ_CRT)

If you need to create conversion exits for these RFMs, see SAP Note 2407968 for more information.

5.4 Steps during Live Operation

5.4.1 Generating Authorization Profile

You may need to regenerate the authorization profile of the existing roles after the upgrade. You can use the mass

generation of the role maintenance (transaction PFCG) to do this.

Note

For information about the mass generation of authorization profiles, execute transaction PFCG and

choose Help → Application Help.

5.4.2 Testing the Application

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

Management.

2. Select the New Business process.

3. Enter a new business, including the release.

Note

If you require information about the procedure, see SAP Policy Management -> Application Help -> SAP

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

Business Business Process.





CUSTOMER


4. Define your own test cases, and run them after the upgrade.

28

CUSTOMER



Troubleshooting

6 Troubleshooting

Note that the sample Customizing for SAP Policy Management must be copied completely, or it must be replaced

by appropriate customer-specific adjustments. Otherwise the entire system does not work.

SAP Policy Management will not run without the runtime component for the msg.PM Product Engine.

6.1 Support

6.1.1 SAP Policy Management Support

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

core components. Likewise, the SAP Policy Management 5.4 Support Packages are imported with the patch

manager SPAM.

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

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

For an overview of the available SAP Policy Management 5.4 Support Packages, see SAP Note 2412645.

Note

To view the Support Packages, follow the following path:

https://support.sap.com/patches → Support Packages and Patches → Entry by Application Group →

SAP Industry-Specific Components → SAP Insurance FS-PM → SAP Insurance FS-PM 5.4 → FSPM 540.

Caution

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

comparison for the SAP Policy Management tables using the transaction SCU0.

6.1.2 Further Information

For more information about Support Packages for FS-PM, see SAP Note 2412645

Caution

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




https://support.sap.com/patches



Troubleshooting

CUSTOMER


6.2 Uninstalling SAP Policy Management 5.4

It is not possible to uninstall SAP Policy Management 5.4.

30

CUSTOMER



Appendix

7 Appendix

7.1 Program /PM0/ABP_MIG_53_54_003

Short description:

The introduction of the new Used property for in-force-business-controlling attributes of product templates in

In-Force Business Configurator for the Policy application requires the Used property to be set for all these

attributes to TRUE, in order to retain compatibility. The current program executes this step automatically

during the upgrade, by setting the field ATTR_IS_USED_FG in table /PM0/ABUCIBCATTR for the

corresponding attributes to X (= TRUE).

Requirements

Identification of Used Attributes in In-Force Business Configurator

Program category

XPRA

Background

The Used checkbox has been added to the attributes in In-Force Business Configurator. You can use this

checkbox to identify an attribute in the product template as being used or not used. If you do not use an

attribute in the product template because, say, the attribute is not relevant for the line of business in question,

you remove the selection in the Used checkbox. The attribute will then be ignored in the product template, and

thus the value does not need to be defined.

In Used Attributes selection mode, only the attributes that are identified as being used are displayed, which

improves clarity; the attributes that are not used are not displayed. However they are visible in the Unused

Attributes and All Attributes selection modes. This simplifies manual changes in templates. An import lock for

the Used checkbox is also available. You set the import lock when you have manually changed the Used

checkbox for attributes in In-Force Business Configurator (in other words, you have set or removed

attributes), in order to prevent this change being overwritten by an import to In-Force Business Configurator.

If you do not set the import lock, then the selection of Used checkboxes may change after an IFBC import.

Effects on existing data

If you have upgraded from an older release (before SAP Policy Management 5.4), this migration report is

available to ensure that the values of the use checkboxes are set.

7.2 Program /PM0/ABP_MIG_53_54_002

Short description

BI (BI Content) enables better performance when processing the status table /PM0/ABDTTRANS

Requirements

Faster processing of BI FPP (Framework for Parallel Processing) runs


Appendix

CUSTOMER


Program category

Manual step

Background

Table /PM0/ABDTTRANS contains the history of which journal version of a policy or contract has already been

transferred to BI. For new policies and contracts, an initial entry with journal number Zero is expected.

This entry was added at the start of the BI FPP run. For performance reasons, the initial entry is created in the

release.

For policies and contracts that were created after the last FPP and before initialization in the release, this

program inserts the initial entry afterwards in table /PM0/ABDTTRANS.

Effects on existing data

No effects

www.sap.com/contactsap

Material Number


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

form or for any purpose without the express permission of SAP AG.

The information contained herein may be changed without prior

notice.

Some software products marketed by SAP AG and its distributors

contain proprietary software components of other software

vendors.

National product specifications may vary.

These materials are provided by SAP AG and its affiliated

companies (“SAP Group”) for informational purposes only, without

representation or warranty of any kind, and SAP Group shall not be

liable for errors or omissions with respect to the materials. The only

warranties for SAP Group products and services are those that are

set forth in the express warranty statements accompanying such

products and services, if any. Nothing herein should be construed as

constituting an additional warranty.

SAP and other SAP products and services mentioned herein as well

as their respective logos are trademarks or registered trademarks of

SAP AG in Germany and other countries. Please see

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

for additional trademark information and notices. Field Code Changed

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