SAP Policy Management 5 · 6 Software Change Management ... 6.1 Transport and Change Management ... This guide also provides references to the documentation required for these tasks,

Application Operations Guide

SAP Policy Management

Document Version: 1.0 – 2017-04-27

CUSTOMER

SAP Policy Management 5.4 Application Operations Guide

2

CUSTOMER

© 2017 SAP SE. 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. All rights reserved. 3

Document History

Version Date Change

1.0 2016-04-27 First version of this guide

4

Customer



Table of Contents

Table of Contents

1 Getting Started .............................................................................................................................. 6 1.1 About this Guide .................................................................................................................................... 6 1.2 Global Definitions................................................................................................................................... 6 1.3 Important SAP Notes ............................................................................................................................ 7

2 Technical System Landscape ...................................................................................................... 8 2.1 Scenario/Component Matrix ............................................................................................................... 8 2.2 Related Documentation ........................................................................................................................ 9

3 Monitoring of SAP Policy Management .................................................................................... 11 3.1 Alert Monitoring .................................................................................................................................... 11 3.2 Monitoring Installation and Setup ....................................................................................................... 11 3.3 Detailed Monitoring and Tools for Problem and Performance Analysis ......................................... 11

3.3.1 Workload Monitors............................................................................................................... 12 3.3.2 Interface Monitors ............................................................................................................... 12

3.4 Data Growth .......................................................................................................................................... 15 3.4.1 Data Archiving Monitors ...................................................................................................... 15 3.4.2 Information Lifecycle Management ...................................................................................16

3.5 Data Consistency ..................................................................................................................................16

4 Management of SAP Policy Management ................................................................................. 17 4.1 Starting and Stopping .......................................................................................................................... 17 4.2 Software and Technical Configuration ............................................................................................... 17 4.3 Administration Tools ............................................................................................................................18 4.4 Backup and Restore .............................................................................................................................18 4.5 System Copy ........................................................................................................................................ 20 4.6 Scheduled Periodic Tasks .................................................................................................................... 21

4.6.1 Description of Batch Runs Implemented in FPP ............................................................... 21 4.6.2 Starting Batch Runs by an External Scheduler ................................................................ 32 4.6.3 Postprocessing Errors of Mass Runs ................................................................................ 35 4.6.4 Cleanup of Interim Tables of FS-CD Interface .................................................................. 35 4.6.5 Cleanup of Table of BTS Keys Accessed By Correspondence ....................................... 36

4.7 Required Manual Periodic Tasks ........................................................................................................ 36 4.8 Load Balancing .................................................................................................................................... 37

5 High Availability .......................................................................................................................... 38

6 Software Change Management ................................................................................................. 39 6.1 Transport and Change Management ................................................................................................. 39 6.2 Support Packages and Patch Implementation ................................................................................. 40


Table of Contents

CUSTOMER


7 Troubleshooting .......................................................................................................................... 41

8 Concept for Handling Custom Development .......................................................................... 43

9 Support Desk Management ...................................................................................................... 44 9.1 Remote Support Setup ....................................................................................................................... 44 9.2 Problem Message Handover ............................................................................................................... 44 9.3 Related Information ............................................................................................................................. 44

6

CUSTOMER



Getting Started

1 Getting Started

Caution

This guide does not replace the daily operations handbook that we recommend customers to create for

their specific production operations.

1.1 About this Guide

Purpose

Designing, implementing, and running your SAP applications at peak performance 24 hours a day has never been

more vital for your business success than now.

This guide provides a starting point for managing your SAP applications, and maintaining and running them

optimally. It contains specific information for various tasks and lists the tools that you can use to implement them.

This guide also provides references to the documentation required for these tasks, so you will sometimes also

need other guides such as the Master Guide, Technical Infrastructure Guide, and SAP Library.

Target Groups

Technical Consultants

System Administrators

Solution Consultants

Business Process Owner

Support Specialist

1.2 Global Definitions

SAP Application

A SAP application is an SAP software solution that serves a specific business area like ERP, CRM, PLM, SRM, or

SCM.

Business Scenario

From a micro-economic perspective, a business scenario is a cycle, which consists of several different

interconnected logical processes in time. Typically, a business scenario includes several company departments

and involves other business partners. From a technical point of view, a business scenario needs at least one SAP

application (SAP ERP, SAP SCM, or others) for each cycle and possibly other third-party systems. A business

scenario is a unit which can be implemented separately and reflects the customer’s prospective course of

business.


Getting Started

CUSTOMER


Component

A component is the smallest individual unit considered within the Solution Development Lifecycle; components

are separately produced, delivered, installed and maintained.

1.3 Important SAP Notes

Caution

Check regularly for updates available for the Application Operations Guide.

SAP Note Number Title

1567448 Integration of FS-PM with the remote system

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

http://service.sap.com/sap/support/notes/1567448

8

CUSTOMER



Technical System Landscape

2 Technical System Landscape

2.1 Scenario/Component Matrix

Use

You can manage insurance contracts with SAP Policy Management (FS-PM). You can map the whole life cycle of a

contract, starting from the creation of an application, through policy issuance and ongoing contract maintenance,

right up to the termination of the contract.

Integration

FS-PM is embedded in the SAP for Insurance landscape and uses interfaces to communicate with other

applications such as BP (Business Partner), FS-CD (Collections/Disbursements), FS-CM (Claims Management),

FS-ICM (Incentive and Commission Management) and FS-RI (Reinsurance), and so on.

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

Policy Management -> Integration.

FS-PM

RCreate new business

Periodic upate

Information

Change / universal ChangeResetReverse

Msg.pm

RCalculate

Import data

PM data

FS-CD

Collection

Disbursements

FS-CD data

R

FS-CM

Claims

Handling

FS-CM data

R

FS-ICM

Commissions

FS-ICM data

R

FS-RI

Reinsurance

FS-RI data

R

Business

Partner

BP data

R

FI

FI data

R

FPO

FPO data

R RCalculate

Import data

FS-PRO/

FS_PWS

FS-PRO

data

R

Msg.pm data

FS-QUO

Create new business

Find Policy

Retrieve Policy

FS-QUO data

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



CUSTOMER


Components

FS-PM itself consists of several building blocks and subcomponents.

2.2 Related Documentation

The following table lists where you can find more information about the technical system landscape.

Topic Guide/Tool Quick Link to SAP Service

Marketplace

(http://service.sap.com)

SAP Policy Management Application Help SAP Policy Management ->

Application Help -> SAP Library

for SAP Policy Management ->

Integration

FPP (Framework for Parallel Processing) Application Help SAP Policy Management ->

Application Help -> SAP Library

http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000743549&



10

CUSTOMER




Topic Guide/Tool Quick Link to SAP Service

Marketplace

(http://service.sap.com)

for SAP Policy Management ->

Basic Functions -> Parallel

Processing (FPP)

msg.PM Installation Guide See msg.PM directory on system

DVD/CD for FS-PM 5.4

SAP Product and Lifecycle Management for

Insurance (FS-PRO)

Integration Guide SAP Product Lifecycle

Management for Insurance ->

Integration -> Integration Guide

Performance Performance Guide SAP Policy Management -> How-

to Guides -> Performance Guide

SAP for Insurance Master Guide SAP Policy Management ->

Installation and Upgrade ->

Master Guide

SAP NetWeaver 7.50 Technical Operations

Manual

Look for Technical

Operations Manual in SAP

NetWeaver 7.5

Security Security Guide SAP Policy Management ->

Security -> Security Guide


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

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



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




Monitoring of SAP Policy Management

CUSTOMER


3 Monitoring of SAP Policy Management

Within the management of SAP Technology, monitoring is an essential task. A section has therefore been devoted

solely to this subject.

For more information about the underlying technology, look for Technical Operations Manual in SAP

NetWeaver 7.5.

3.1 Alert Monitoring

Proactive, automated monitoring is the basis for ensuring reliable operations for your SAP system environment.

SAP provides you with the infrastructure and recommendations needed to set up your alert monitoring to

recognize critical situations for SAP Policy Management as quickly as possible.

Caution

Critical situations for FS-PM, apart from the standard ones such as the termination of batch processing:

o Availability of third-party systems, e.g. FS-CD

o Remote access exceptions of calls to third-party systems

For more information, refer to the SAP System Monitoring and Alert Management (Monitoring your SAP

NetWeaver Components).

3.2 Monitoring Installation and Setup

In order to enable the auto-alert mechanism of Computing Center Management System (CCMS), see SAP Note

617547.

3.3 Detailed Monitoring and Tools for Problem and Performance Analysis

FS-PM uses the SAP NetWeaver AS ABAP logging mechanisms. For more information, look for Auditing and

Logging in SAP NetWeaver 7.5.

For more information about performance analysis, look for Performance Trace Overview in SAP NetWeaver

7.5.



http://scn.sap.com/docs/DOC-8335?rid=/webcontent/uuid/605a899b-4038-2a10-d491-af6ba6c2506a

http://scn.sap.com/docs/DOC-8335?rid=/webcontent/uuid/605a899b-4038-2a10-d491-af6ba6c2506a

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




12

CUSTOMER




3.3.1 Workload Monitors

For more information about workload monitors, look for Global Workload Monitor in SAP NetWeaver 7.5.

3.3.2 Interface Monitors

Interface monitors are essential for analyzing problems with interfaces such as RFC, IDoc, and HTTP.

Policy processing frequently triggers activities in other domains such as SAP Collections and Disbursements for

Insurance (FS-CD), SAP Incentive and Commission Management for Insurance (FS-ICM), Portfolio Assignment

(PFO) or SAP Reinsurance Management (FS-RI). Therefore FS-PM has to provide the interfaces to such domains

with data. In order to give FS-PM customers the choice to connect SAP for Insurance solutions as well as non-SAP

systems, these interfaces are implemented in enhancement spots and BAdIs (Business Add-Ins).

The default implementations of these BAdIs delivered with FS-PM 5.4 facilitate the remote connection to the SAP

for Insurance solutions FS-CD, FS-ICM, PFO and FS-RI. In order to ensure proper communication in a productive

system landscape, these systems are called asynchronously making use of the qRFC technology (queued Remote

Function Call).

In the following sections, we describe the qRFC interfaces used in FS-PM 5.43 and how to monitor them. For more

information, see SAP-Note 1567448.

3.3.2.1 Interface to FS-CD

This interface is located in BAdI /PM0/ABT_QRFC_CD_BADI of the enhancement spot /PM0/ABP_CD_BADI. The

class containing the default implementation is /PM0/CL_DEF_INT_QRFC_CD_BADI. It includes calls of the

following RFC function modules:

Interface Function Module Detailed Description Technology used

FSCD_INSOBJECT_CREATE_BAPI Used to create insurance objects in FS-CD. qRFC

FSCD_INSOBJECT_CHANGE_BAPI Used to change existing insurance objects in FS-

CD.

qRFC

FSCD_ACCOUNT_CREATE_BAPI Used to create contract accounts in FS-CD. qRFC

FSCD_ACCOUNT_CHANGE_BAPI Used to change existing contract accounts in FS-

CD.

qRFC

ISCD_SCPOS_MAINTAIN Used to post open items to FS-CD. qRFC





CUSTOMER


3.3.2.2 Interface to FS-ICM

This interface is located in BAdI /PM0/ABT_QRFC_CS_BADI of the enhancement spot

/PM0/ABT_CS_INTEGRATION_ES. The class containing the default implementation is

/PM0/CL_DEF_INT_QRFC_CS_BADI.

The RFC-enabled function module is generated in the FS-ICM system and its name depends on the FS-ICM

application used.


<appl>_QRFC_CASE Used to create a commission case in FS-ICM1. qRFC

3.3.2.3 Interface to PFO

This interface is located in BAdI /PM0/ABT_QRFC_PFO_BADI of the enhancement spot /PM0/ABP_PFO_BADI_ES.

The class containing the default implementation is /PM0/CL_DEF_INT_QRFC_PFO_BADI. It includes calls of the

following RFC function modules:


PFO_QRFC_IMPORT_GO_00IP Used to change the lifespan of business object Policy

in PFO.

qRFC

PFO_QRFC_IMPORT_GO_00IV Used to change the lifespan of business object

Contract in PFO.

qRFC

PFO_QRFC_IMPORT_GO_00IS Used to change the lifespan of business object

Coverage in PFO.

qRFC

PFO_QRFC_PM_IMPORT_PDORG Used to change assignment data in PFO. qRFC

PFO_QRFC_PM_IMPORT_AND_ASS

IGN

Used to create and assigning policies in PFO. qRFC

PFO_QRFC_IMPORT_GZO Processing changes of business object assignments of

type GZO in PFO.

qRFC

1 For simulation purposes, a similar function module <appl>_RFC_CASE is called synchronously.

14

CUSTOMER




3.3.2.4 Interface to FS-RI

This interface is located in BAdI /PM0/ABT_QRFC_RI_BADI of the enhancement spot

/PM0/ABT_INTEGRATION_RI_ES. The class containing the fallback implementation is

/PM0/CL_DEF_INT_QRFC_RI_BADI. It includes calls of the following RFC function modules:

Interface Function Module Detailed Description Technology

used

/MSG/H_PAPI_RIACC_CREATE Used to create an accumulation in FS-RI. qRFC

/MSG/H_PAPI_RIACC_CHANGE Used to change an accumulation in FS-RI. qRFC

/MSG/H_PAPI_RIACT_CREATEMULTIP Used to create multiple preliminary accounts in

FS-RI.

qRFC

3.3.2.5 Monitor tools for qRFC interfaces

The monitor tool for all qRFC interfaces described above is the qRFC monitor for outbound queues (transaction

SMQ1). If an error occurs when executing the qRFCs, these interfaces raise an exception and the respective queue

appears with an error status (SYSFAIL) in the qRFC monitor of the FS-PM system. Therefore the system

administrator should regularly check for erroneous outbound queues in the qRFC monitor, for example by

entering the following search criteria on the entry screen.

For more information about workload monitors, look for Queued Remote Function Call (qRFC) in SAP

NetWeaver 7.5.

FS-PM uses the following queue names:

Interface Queue Name Detailed Description

FS-CD CD-<PolicyNumber> For assignment of Collections and Disbursements

FS-ICM CS-<PolicyNumber> For assignment Incentive and Commission Management

PFO OM-<PolicyNumber> For assignment of commission participants.

PFO PO-<PolicyNumber> For assignment of organizational units.

FS-RI RI-<AccumulationNumber> For assignment of Reinsurance

Because the qRFC monitor does not provide a detailed error protocol, the root cause for the failed qRFC-call

needs to be analysed in the remote system. Before raising an exception, the qRFC interfaces write an error

protocol into the application log (transaction SLG1) of the remote system.





CUSTOMER


The link between the error causing outbound queue in the FS-PM system and the log file in the remote system can

be established with help of the External ID field in the application log. This field is filled with the following data <FS-

PM System> <QueueName>, where <FS-PM System> is the logical name of the FS-PM system, for example

Q8Y(700) and <QueueName> is the queue name as listed in the table above.

With this information, the user can retrieve the error protocol in the remote system, analyze the error messages

and take the necessary steps to resolve the error.

3.4 Data Growth

3.4.1 Data Archiving Monitors

The data growth should be checked regularly with the tools provided by the database system.

SAP enables the following objects to be archived:

In-Force Business Management (policy, contract, etc.)

Object Management (insurable objects)

Master policies

Transfer objects

Correspondence

Third-party collection

Accounting component Account Balances

Accounting component Non Cash Flow Documents

Accounting component Cash Flow Documents

Data containers (input data for business transactions and business processes)

Fund ranges

Global fund orders

Fund Management

Guarantee values

Information container (for communication with Collections and Disbursements)

Coinsurance

Model calculation

Journal

Special Risk

The more important archiving objects can be displayed in the corresponding FS-PM business processes. Archived

policy versions, for example, can be displayed in the Inquiry business process.

When you start the archiving program, only those database entries are archived that fulfill the criteria for the

residence duration. You can maintain residence durations for the FS-PM archiving objects in Customizing for

Policy Management under General Settings -> Archiving.

16

CUSTOMER




The residence duration must be greater than the duration for which backdated changes are permitted. SAP

recommends the residence duration to be one year longer than the duration for backdated changes. If, for

example, backdated changes are permitted for the two previous years the residence duration should be set to 36

months.

For more information, see SAP Policy Management -> Basic Functions -> Data Archiving.

For periodic tasks required to contain data growth (that is, to reorganize temporary data), see the periodic tasks

section in this guide.

3.4.2 Information Lifecycle Management

In SAP Policy Management you can simplify the blocking and deletion of personal data by using SAP Information

Lifecycle Management (ILM).

A prerequisite for using ILM is that you need to archive business data. In SAP Policy Management, you can block

business data by using authorizations to restrict read access to archived business data.

3.5 Data Consistency

To identify inconsistencies early (for example, after a restore of a single component), you should regularly check

the application log after executing periodic processing.

The logs can be accessed by the transaction from where the periodic processing was started (for example, the

application log of the update run can be analyzed with transaction Update Policies/Contracts

(/PM0/ABY_FPP_FP_PA) or by calling the transaction Analyze Application Log (SLG1).

In specific error situations, postprocessing orders are created. These can be accessed and changed with the

transactions Display Postprocessing Order (/PM0/ABT_PPO_SHOW) and Change Postprocessing Order

(/PM0/abt_PPO_PROC).

You should also regularly check the outbound queue for qRFC (SMQ1).



Management of SAP Policy Management

CUSTOMER


4 Management of SAP Policy Management

SAP provides you with an infrastructure to help your technical support consultants and system administrators

effectively manage all SAP components and complete all tasks related to technical administration and operation.

The aims of managing SAP NetWeaverTechnology are as follows:

Provide a central interface to manage administrative tasks for middleware

Improve the process of problem resolution for the entire solution

Provide standardized administration of user profiles.

For more information about the underlying technology, look for Technical Operations Manual in SAP

NetWeaver 7.5.

4.1 Starting and Stopping

There are no specific administration tools for SAP FS-PM.

For more information, look for Starting and Stopping SAP Systems and Instances in SAP NetWeaver

7.5.

4.2 Software and Technical Configuration

This section explains which components or scenarios used by this application are configurable and which tools

are available for adjusting.

Component Configuration Tools

Component Configuration Tool(s) Description

Home Page and Worklist Program POWL_WLOAD (Refresh Active

POWL Queries)

You can use this program to update

queries.

If you schedule the program as a

background job, for example, you can

update the queries overnight. Users then

have access to the updated data when

they start work, without having to refresh

the data themselves. This is a way of

controlling the server load.

FS-PM area menu SE43 Besides the role menu, the area menu is

also shipped.

You can use transaction SE43 to add the

area menu to the standard menu.





18

CUSTOMER




The following area menus are available:

Technical Name Description

/PM0/ABRECHNUNGSKOMPONENTE Accounting Component

/PM0/BESTANDSVERWALTUNG In-Force Business Management

/PM0/BI_DATEN BI Data

/PM0/BUSINESS_TRANSACT_SCHED Business Transaction Scheduler

/PM0/CUST_INT Developer Customizing

/PM0/DRITTINKASSOVERWALTUNG Third-Party Collections Management

/PM0/FONDSVERWALTUNG Fund Management

/PM0/IBC In-Force Business Configurator

/PM0/INFOCONTAINER Information Container

/PM0/KORRESPONDENZVERWALTUNG Correspondence Management

/PM0/MIGRATION Data Migration from Legacy Systems to FS-PM

/PM0/MITVERSICHERUNG Coinsurance

/PM0/OBJEKTVERWALTUNG Object Management

/PM0/PERIODISCHE_ARBEITEN Periodic Processing

/PM0/POLICYMANAGEMENT Policy Management

/PM0/RAHMENVERTRAGSVERWALTUNG Master Policy Management

/PM0/SCHNELLERFASSUNGSVERW Fast Entry Management

/PM0/SONDERWAGNISVERWALTUNG Special Risk Management

/PM0/WERKZEUGE Tools

You can find the area menus in the package /PM0/MENUE.

4.3 Administration Tools

There are no specific administration tools for SAP FS-PM.

4.4 Backup and Restore

You need to back up your system landscape regularly to ensure that you can restore and recover it in case of

failure.

The backup and restore strategy for SAP Policy Management consists of two parts:

Backup and restore coverage for each component (see table below)



CUSTOMER


Cross-system data dependencies and handling

The backup and restore strategy for your system landscape should not only consider SAP systems but should

also be embedded in overall business requirements and incorporate your company’s entire process flow. In

addition, the backup and restore strategy must cover disaster recovery processes, such as the loss of a data

center through fire. It is most important in this context that you ensure that backup devices are not lost together

with normal data storage (separation of storage locations).

Based on the type of application data contained in a component, we have introduced a categorization scheme for

system components that can be used to analyze the backup requirements of any system component and to easily

determine an appropriate backup method for this component. The following table contains a component list for

your application and the appropriate categories.

Categories of System Components for Backup & Recovery

Category of

System

Component

Category Properties Suggested Methods for Backup and

Restore

Example

I Only software, no

configuration or

application data

No backup, new installation in case of a

recovery or

Initial software backup after

installation and upgrade

Backup of log files

BDOC modeler

II Only software and

configuration

information, no

application data

Backup after changes have been

applied or

No backup, new installation and

configuration in case of a recovery

Backup of log files

SAP Gateway

Comm. Station

SAP Business

Connector

SAP IPC (2.0C)

III Only replicated

application data,

replication time is

sufficiently small for a

recovery

Data:

No data backup needed

Backup of software, configuration, log

files

SAP

IMS/Search

Engine

SAP IPC (2.0B)

Webserver

SAP ITS

IV Only replicated

application data, backup

recommended because

replication time is too

long, data not managed

by a DBMS

Data:

Application-specific file system backup

or

Multiple instances


files

SAP

IMS/Search

Engine

Webserver

V Only replicated

application data, backup

recommended because

replication time is too

long, data managed by a

DBMS

Data:

Database and log backup or

Multiple instances


files

SAP IPC (2.0B)

Catalog Server

20

CUSTOMER




Category of

System

Component

Category Properties Suggested Methods for Backup and

Restore

Example

VI Original application data,

stand-alone system, data

not managed by a DBMS

Data:

Application-specific file system backup


files

Webserver

VII Original application data,

stand-alone system, data

managed by a DBMS, not

based on SAP WebAS

Data:

Database and log backup


files

—

VIII Original application data,

standalone system,

based on SAP WebAS

Data:

Database and log backup, application

log backup (such as job logs in file

system)


files

Standalone SAP

R/3

IX Original application data,

data exchange with other

systems, data not

managed by a DBMS

Data:

Application specific file system

backup, data consistency with other

systems must be considered


files

—

X Original application data,


systems, data managed

by a DBMS, not based on

SAP WebAS

Data:

Database and log backup, data

consistency with other systems must

be considered


files

SAP liveCache

SAP Mobile

Workbench

XI Original application data,


systems, based on SAP

WebAS

Data:

Database and log backup, application

log backup (such as job logs in file

system), data consistency with other

systems must be considered


files

SAP R/3

SAP CRM

SAP APO

SAP BW

4.5 System Copy

For more information, see the SAP Standard Procedure.



CUSTOMER


Caution

A system copy of an FS-PM productive system can affect production data of other systems or

components (for example FS-CD).

You should ensure that an FS-PM system copy does not affect production data of other systems either by

the adjustment of number ranges (see also the Installation Guide) or by creating a system copy of the

third-party systems as well.

4.6 Scheduled Periodic Tasks

This section describes all automated tasks that you are required to run periodically in order to keep the

application operating smoothly over time. Such tasks may be required on component level and are therefore

relevant in each scenario that uses the component. You can find the mapping in the section Scenario /

Component Matrix above. Other tasks may be relevant to certain business scenarios only. It is important that you

monitor the successful execution of these tasks on a regular basis.

This section includes the description of the relevant processes for performing updates in mass processing.

4.6.1 Description of Batch Runs Implemented in FPP

FS-PM uses batch runs for special business scenarios. These batch runs operate on the basis of Framework for

Parallel Processing (FPP).

The processes that have been redesigned or newly implemented to run within in FPP have their own transaction

and start dialog. However, the following settings are common to all the batch runs implemented in FPP:

Tab Field Description Sample Value

Technical

settings

ParaProcess.Obj For every run, there is a predefined

class that should be selected here.

This class is responsible for creating

the intervals for object keys that

should be processed in the current

run.

Use class

/PM0/CL_ABY_FPP_INT_POLNR

Technical

settings

Interv. Distribution This field specifies what kind of

intervals should be used in the current

run. You can create a run using N

intervals with X entries in each interval.

To set up or view the intervals, press

the button below this field.

Logs Problem class This field specifies the log level that

should be used in this run. Set this to 4

1-4

22

CUSTOMER





if you want to have the highest level of

log detail.

Maintain Parallel Processing Intervals

You must maintain parallel processing intervals, if you want to use batch runs implemented in FPP.

You maintain intervals as follows:

1. Start the transaction of the batch run for which you want to maintain the interval (for example the Update

Policies/Contracts run: /PM0/ABY_FPP_FP_PA).

2. Create a new run.

3. Select the Technical Settings tab

4. Enter the ParaProcess.Obj of your FPP Run (for example /PM0/CL_ABY_FPP_INT_POLNR for the Update

Policies/Contracts run).

5. Choose Maintain Interval Distributions and click on Automatic Interval Creation

6. Again enter the ParaProcess.Obj and a name for the Interval Distribution in the Maintenance of Interval

Distributions dialog.

7. Enter the number of intervals (for example 1).

4.6.1.1 Updating Policies/Contracts (/PM0/ABY_FPP_FP_PA)

This is an FPP implementation that uses batch-improved technology and features bulk DB loading and

processing.

When updating an insurance policy or contract, you can choose what kind of update you want to perform by

selecting a predefined update type.

Update types are defined in Customizing for Policy Management under In-Force Business Management -> Basis ->

Update -> Define Update Types. They determine the way in which the system performs the update run.

For example you can define

Whether and how internal and external components like FS-CD or Correspondence are provided with the

results of the run (for instance, you can determine that cash flow documents are not created)

What time model functions shall be excluded from the update run

The way in which the system is to respond if errors occur in specific error categories

Whether the updated application shall be stored or not

Several update types are already predefined by SAP and cannot be changed, for example:

Accounting run (BVC)

Performs balance sheet calculations within a period up to a specified target date.

Correspondence run (KOR)

Schedules correspondence up to a target date. You can create a correspondence item for the contract

versions for specific dates. The correspondence run assumes this task. This run can take place in advance.



CUSTOMER


Order planning run (ODR)

Positions a contract up to a target date and generates order planning only.

Provisional collection run (PCO)

This updates all contracts up to a target date and executes all scheduled processing. However, when the

system releases the contracts, only cash flow and specific non-cash flow transactions are saved and all other

processing is discarded. The documents are stored as temporary files. This run is executed separately from

all other runs.

Default positioning (STD)

Positions one or more contracts up to the target date and releases them. This is the default positioning for the

contract time model. If the option "Force Policy Processing" is selected, one or more policies are positioned.

Renewal (RNW)

An update with the update type RNW Renewal must be regularly scheduled for in-force contracts that participate

in renewal. We recommend doing this before processing the contract expiration date since the update by

RNW forms the basis for processing the expiration date.

Renewal correspondence (RNC)

Update with the update type RNC Renewal Correspondence must be regularly scheduled for in-force contracts

that participate in renewal. In this update, correspondence relevant for the renewal is created.

You can also create your own update types.

The process is started by the /PM0/ABY_FPP_FP_PA transaction and has the following application specific fields:


Restrictions Policy Number (optional) A selection list of policy numbers to be

processed in this run

Line of Business (optional) Selection criteria, that is to say, only

contracts of the specified line of business

are to be processed

LL

Sales Product Template ID

(optional)

Only polices of the specified sales product

are to be processed

Product Module Group

(optional)

Only contracts of the specified product

module group are to be processed

Master Policy (optional) Only contracts linked to the master policy

are to be processed

Product (optional) Only contracts of the specified product are

to be processed

Selection Date for

Update(optional)

Date to be used for defining the maximum

date for which periodic tasks are selected.

This date is only considered if the target

date is not specified

Target Date (optional) If this optional target date is supplied, it is

used for the whole run. Otherwise a target

date is internally calculated for every single

contract depending on its current state.

24

CUSTOMER





Update Type This field specifies what this run should

actually do, that is, the type of this run –

correspondence, normal update,

preliminary collections and so on. The

different variants are explained further in

the Customizing section.

Change Category of Time

Model Function End (Change

Cat. TMF End) (optional)

Only TM functions whose change category

is smaller than this value are to be executed

Fine Control Value Time Model

Function (End Date) (FC Value

TMF End) (optional)

Only TM functions whose fine control value

is smaller than this one are to be executed

Package Size Processing block size: Defines how many

business objects are selected in blocks from

the database. The number of database

requests and the CPU time on the

application server depend on this number. A

small block size increases the number of

database requests, but reduces the CPU

time on the application server.

If you want to find the number that fits best

for performance reasons, you should carry

out some performance measurements in

your own system, starting with a package

size of 25.

100

Force Policy Processing The system automatically determines the

processing level for the update. If possible,

the system updates the selected policies on

a single contract basis. If this is not possible,

the system updates at policy level.

In rare cases, the system is unable to

determine processing at policy level. If this

is so, you must enforce processing at policy

level.

Restrict Loading of Reversed

Contracts

The checkbox “Restrict Loading of Reversed

Contracts” in the transaction “Update

Policies/Contracts” indicates whether the

system is to load reversed contracts only if

their reversal date is within the set period.

If you select this checkbox, the system loads

only the reversed contract versions that

fulfill the following prerequisites:

The period between reversal date and the

first of the month of the effective date is no



CUSTOMER



longer than the period you set in

Customizing (under Policy Management ->

In-Force Business Management -> Basis ->

Business Processes -> General Settings ->

Restrict Loading of Reversed Contracts).

Note: The effective date refers to the

highest contract version of the active

contracts on the basis of which the

application is created.

If you do not select this checkbox, the

system loads all contract versions, including

all reversed contracts.

For performance reason you can use this

flag for faster processing.

Automatic Repeat of Run to Update Policies/Contracts

Runs of the Update Policy/Contracts transaction that terminate as a result of an ABAP runtime error can be

automatically repeated.

When a run is repeated, the policy that was being processed at the point of the ABAP runtime error can be

excluded from the set of policies to be updated. This is documented in the application log.

The number of repeat runs is restricted to 10. This is defined in the view cluster /PM0/VC_FPP_XCUST under Run

Control in the Maximum Number of Repeats of a Run field.

For more information, see SAP Note 1763794.

Set Threshold for Aborted Jobs in Batch Runs

When you execute a batch run in the Update Policies/Contracts or Validate Migrated Policies transaction, you can

set the threshold for the percentage of aborted jobs for a batch run. When the threshold is reached for each

current job, an ABAP runtime error is triggered and the job is stopped. When all current jobs are stopped, the

batch run restarts. For the jobs that are forced to stop, no policies are excluded from the next run.

Setting the threshold improves efficiency since a run otherwise restarts only when all jobs finish running, whether

aborted or completed successfully. This might take a long time even when most of the jobs are aborted.

Effects on Customizing:

In Developer Customizing (transaction /PM0/CUST_INT), you can define exits for the framework of parallel

processing (FPP). Proceed as follows:

1. Choose Internal Customizing -> General Settings -> Define Exits for FPP.

2. In the Customizing activity, assign FPP exit ABT_THLD and a class/interface to mass activities FP_PA and

FP_Q_POL.

A sample class /PM0/CL_ABY_FPP_INITRUN_PACK is provided. In the sample class, the threshold value is

set to 50%. You can create a similar class and modify the DEFINE_ABORT_THLD method to set a different

threshold value.


26

CUSTOMER




4.6.1.2 Transferring Cash Flow Documents (/PM0/ABY_FPP_CFC)

The update generates cash flow documents. These documents must be forwarded to FS-CD. These subprocesses

cumulate the documents that require processing and forward them to FS-CD. The prerequisite for this batch run

is that the master data for FS-CD has already been created and/or changed in the external system. This means

that the FS-CD interface must either operate in online mode or run the Transfer Offline Data batch run before this

batch run.

The process is started by the /PM0/ABY_FPP_CFC transaction and has the following application-specific fields:


Restriction Policy Number (optional) A selection list of policy numbers to be


Sales Product Template ID Only policies of the specified sales product

are to be processed

Posting Date to (optional) Specifies the last posting date for a posting

period

PostDocs Immediately Post cash flow documents immediately in

Collections and Disbursements

Post Docs Individually In case of error, post posting data

individually per policy

Switch Off Migr.Status Check During the transfer of posting data to FS-

CD, each policy is checked as to whether it

originates from the migration of in-force

business data. If this is the case, the system

checks whether the policy is released,

according to the migration status.

4.6.1.3 Aggregating and Transfering Non Cash Flow Items (/PM0/ABY_FPP_NCC)

The update generates non cash flow documents. These documents must be forwarded to FI-GL in cumulated

form. These subprocesses cumulate the documents requiring processing and forward them to FI-GL. This

process runs within FPP.

The process is started by the /PM0/ABY_FPP_NCC transaction and has the following application-specific fields:






CUSTOMER



Posting Date to (optional) Specifies the last posting date for a posting

period

4.6.1.4 Creating Correspondence for Coinsurer (/PM0/ABY_PP_CORRCOIN)

This run is responsible for creating correspondence for the coinsurance contracts. This process runs in FPP.

This process is started by the transaction /PM0/ABY_PP_CORRCOIN. It has the following application-specific

fields:




Processing Period Within this time span, there should be a

coinsurance for the corresponding policy to

be processed in this run

4.6.1.5 Printing Correspondence (/PM0/ABY_FPP_CORR)

This run is responsible for printing all queued correspondence for the coinsurance contracts. This process runs in

FPP.

The process is started by the /PM0/ABY_FPP_CORR transaction and has the following application specific fields:


General

Data

Correspondence Type Only correspondence of the specified

correspondence type will be processed

Correspondence Recipient Only correspondence that contains the

specified correspondence recipient will be

processed

Application Form Only correspondence that uses the

specified application form will be processed

Date ID Date on which the program run is planned

Identification This is used to differentiate between

program runs with the same execution date

28

CUSTOMER





User Name User name

Created On Specifies the date on which correspondence

was created

Print

Parameters

Output Device Name of an output device in the SAP

System

SAPScript Output Specifies which RDI mode is to be used

Output Format for SmartForms Controls which technical output format is to

be used

Output format for PDF-Based

Form (XFP)

Controls the output format using PDF-

based forms

Archiving mode By entering the appropriate value,

determine whether you want to

Only print the document

Only archive the document

Both print and archive the document

Default value: Only print

Output Request After Last

Document

If this function is supported by the

application and the indicator is set, an

output request is automatically created in

the spool after the last document in a print

run

Open/Close Optimization

Inactive

You can use this indicator to deactivate the

Open/Close Optimization for mass printing

processes

Actual Print Actual print

Test print Sample printout

Repeat Print Repeated print

4.6.1.6 Executing Scheduled Resetting Business Transactions (/PM0/ABY_FPP_REV)

This process executes the business transaction scheduler and executes all due activities related to the start date

shift.

The process is started by the transaction /PM0/ABY_FPP_REV and has the following application-specific fields:



CUSTOMER



General

Selection

Policy Number (optional) A selection list of policy numbers to be


Application Number (optional) A selection list of application numbers to be


Package Size Processing block size: Defines how many

business objects are selected in blocks from

the database. The number of database

requests and the CPU time on the application

server depend on this number. A small block

size increases the number of database

requests, but reduces the CPU time on the

application server.

100

4.6.1.7 Creating Global Simulation Orders (/PM0/ABY_PP_GSIM)

Simulated orders that are created with batch run Update Policies/Contracts (/PM0/ABY_FPP_FP_PA) and update

type Order Planning Run (ODR) are accumulated into global orders.

Criteria such as common fund number or effective date are used to analyze the orders and create global orders.

The process is started by the /PM0/ABY_PP_GSIM transaction and has the following application specific fields:


General

Data



4.6.1.8 BI Runs

There are four BI runs. They are needed to combine data from the entity of a business (meaning Policy

Management, Object Management, Coinsurance Management and Master Policy) with data from the

corresponding journal. A BI run writes data into the delta queue that provides this data for the extraction into the

BI system. It is needed if you want to extract data into a BI system.

Formatting BI Object Management Data (/PM0/ABY_FPP_BI_O)

The process is started by the /PM0/ABY_FPP_BI_O transaction and has the following application-specific fields:


General

Data

Insurable Object (optional) A selection list of insurable objects

30

CUSTOMER





General

Data

Package Size (optional) Processing block size

General

Data

Resetting Flag (optional) This flag indicates if the internal marker table

should be cleared

Formatting BI Master Policy Data (/PM0/ABY_FPP_BI_M)

The process is started by the /PM0/ABY_FPP_BI_M transaction and has the following application-specific fields:


General

Data

Master Policy (optional) A selection list of master policies

General

Data


General

Data


should be cleared

Formatting BI Coinsurance Data (/PM0/ABY_FPP_BI_C)

The process is started by the /PM0/ABY_FPP_BI_C transaction and has the following application-specific fields:


General

Data

Distribution Plan number

(optional)

A selection list of distribution plans

General

Data


General

Data


should be cleared

Formatting BI In-Force Business Management Data (/PM0/ABY_FPP_BI)

The process is started by the /PM0/ABY_FPP_BI transaction and has the following application-specific fields:


General

Data

Policy Number (optional) A selection list of policy numbers

General

Data


General

Data


should be cleared



CUSTOMER


Customizing

The BI runs have one Customizing that should be set up using the /PM0/ABU_PENTITY view cluster with the

following structure:

First Level: Definition

Table Name Name of the table (entity)

Execute Transfer Run Flag if this entity is BI-relevant

Carryforward with Run Defines the BI run that will handle this entity

DataSource Name of the DataSource

Extract Structure for Extraction Name of the Extract Structure

4.6.1.9 Resetting Update Runs (/PM0/ABY_FP_R)

Successfully executed update runs (transaction Update Policies/Contracts (/PM0/ABY_FPP_FP_PA) can be reset

(see also business process Reset (/PM0/ABC_R) to reset update for single policies or contracts).


Selection -

Restriction

External Run ID External identification of a mass run


External Run ID External identification of a mass run

4.6.1.10 Removing Policy Postdating (BTS) (/PM0/ABY_FPP_BTS)

If a first policy version could not be created because of postdating or a new policy version could not be created

with the business process Universal Change using this batch process you can check whether the conditions

originally causing the need for postdating still apply. If this is not the case, new or first policy versions are created

without further user interaction.


General

Data

Application Number A selection list of application numbers to be





32

CUSTOMER




4.6.2 Starting Batch Runs by an External Scheduler

FPP provides the package /PM0/FPPEXT, which allows runs to be started by external schedulers. The principle is

that one sample run is saved manually and later copied to the automatically created runs.

The following report provides an example of how to start such a run:

*&---------------------------------------------------------------------*

*& Report ZFPP_COPY_AND_START_RUN

*&

*&---------------------------------------------------------------------*

*& This report uses functionality of function group

*& /PM0/FPP_EXTERNAL_START to copy and start FPP runs from an external

*& scheduler or program

*& There are more function modules available in the function group to

*& select, stop and monitor runs. Their interface is quite simple, feel

*& free to use them

*&---------------------------------------------------------------------*

REPORT zfpp_copy_and_start_run.

PARAMETERS:

extrunid TYPE bank_dte_pp_runid_ext,

appl TYPE /pm0/fpp_appl,

mid TYPE /pm0/fpp_mid.

* SAMPLE RUN to test:

* appl = fs-pm

* mid = fp_pa

* extrunid = sample_for_copy

DATA: ls_run TYPE /pm0/fpp_runs,

ls_source_run TYPE /pm0/fpp_s_ext_run_info,

ls_new_run TYPE /pm0/fpp_s_ext_run_info,

lt_new_run TYPE /pm0/fpp_t_ext_run_info,

lv_newrun_id TYPE bank_dte_pp_runid_ext,

lt_started_run TYPE /pm0/fpp_t_ext_run_info,

ls_started_run LIKE LINE OF lt_started_run,

lt_failed_run TYPE /pm0/fpp_t_ext_run_info,

ls_failed_run LIKE LINE OF lt_failed_run.



CUSTOMER


SELECT SINGLE * FROM /pm0/fpp_runs INTO ls_run WHERE external_run_id = extrunid AND

appl = appl AND mid = mid.

MOVE-CORRESPONDING ls_run TO ls_source_run.

CONCATENATE ls_run-external_run_id '_' sy-datum '_' sy-uzeit INTO lv_newrun_id.

CALL FUNCTION '/PM0/FPP_EXT_COPY_RUN'

EXPORTING

is_source_run = ls_source_run

i_new_runid = lv_newrun_id

IMPORTING

es_copied_run = ls_new_run

EXCEPTIONS

copy_error = 1

OTHERS = 2.

IF sy-subrc <> 0.

MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno

WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.

ENDIF.

***********************************************************************

* In case you need to adjust a parameter in the new run, you

* can use the following function modules to read and set the

* run parameters

** allow to change the run

*CLEAR: ls_new_run-ext_job_start.

*/pm0/cl_fpp_services=>unmark_external_start( iv_pid = ls_new_run-pid ).

*CALL FUNCTION '/PM0/FPP_EXT_RUN_PARAMS_GET'

* EXPORTING

* iv_pid = ls_new_run-pid

** IMPORTING

** ES_STANDARD =

** EV_STANDARD_REF =

** ES_SELOPT =

** EV_SELOPT_REF =

** EV_NUMBER_OF_JOBS =

** EV_DISTRIBUTION =

** EV_PARALLEL_OBJECT =

34

CUSTOMER




** EV_INSTANCE =

** EV_EXTERNAL_RUN_ID =

** EXCEPTIONS

** READ_ERROR = 1

** OTHERS = 2

* .

*IF sy-subrc <> 0.

** MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO

** WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

*ENDIF.

*

*CALL FUNCTION '/PM0/FPP_EXT_RUN_PARAMS_SET'

** EXPORTING

** IV_PID = ls_new_run-pid

** IS_STANDARD =

** IS_SELOPT =

** IV_NUMBER_OF_JOBS =

** IV_DISTRIBUTION =

** IV_PARALLEL_OBJECT =

** IV_INSTANCE =

** IV_EXTERNAL_RUN_ID =

** EXCEPTIONS

** WRITE_ERROR = 1

** OTHERS = 2

* .

*IF sy-subrc <> 0.

** MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO

** WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

*ENDIF.

** plan the run again for external start and lock it thereby

*/pm0/cl_fpp_services=>mark_external_start( iv_pid = ls_new_run-pid ).

*ls_new_run-ext_job_start = 'E'.

***********************************************************************

APPEND ls_new_run TO lt_new_run.

CALL FUNCTION '/PM0/FPP_EXT_RUN_START_RESTART'

EXPORTING

it_runs = lt_new_run



CUSTOMER


IMPORTING

et_started_runs = lt_started_run

et_failed_runs = lt_failed_run.

LOOP AT lt_started_run INTO ls_started_run.

WRITE: 'This run is started: '.

WRITE: ls_started_run-external_run_id.

SKIP.

ENDLOOP.

LOOP AT lt_failed_run INTO ls_failed_run.

WRITE: 'This run is failed: '.

WRITE: ls_failed_run-external_run_id.

SKIP.

ENDLOOP.

4.6.3 Postprocessing Errors of Mass Runs

The postprocessing of errors is realized by the postprocessing office (PPO).

If mass runs create one or several error messages for a certain policy, one PPO order is created for subsequent

manual or automatic processing.

The transactions Display Postprocessing Order (transaction code /PM0/ABT_PPO_SHOW) and Change

Postprocessing Order (transaction code /PM0/ABT_PPO_SHOW) are tailored for the needs of orders that are

created by Policy Management. For example, they allow you to navigate directly to the business processes Inquiry

and Change, and they allow you to resume processing of an open application directly. The complete functionality

of PPO is also provided.

For general information about PPO, look for Postprocessing Office (PPO) in SAP NetWeaver 7.5.

4.6.4 Cleanup of Interim Tables of FS-CD Interface

Before FS-CD data is transferred to FS-CD, it is saved in interim tables. After the transfer to FS-CD, the data

remains in FS-PM and increases in the course of time. This may cause performance problems.

Program /PM0/ABT_CD_DEL_INTERIM_TABLES deletes data that has already been transferred from the interim

tables.

Program /PM0/ABT_CD_DEL_INTERIM_TABLES should be scheduled as a recurring job. On initial execution, the

runtime may be slightly longer.


36

CUSTOMER




4.6.5 Cleanup of Table of BTS Keys Accessed By Correspondence

Execute program /PM0/ABP_ADDDTIBTS_DELETE regularly, for example monthly.

This program requires the input of a range of valid policy numbers. It deletes all entries that are not referenced in

planned correspondence date entries.

Background: With the link to the BTS date, the Correspondence time model function can determine the

corresponding BTS date information and include the BTS date in the correspondence letter.

For business transactions that are planned as BTS instead of being directly processed, it is not possible to create

correspondence in the standard system. One scenario is that a customer who does not use SAP GUI but uses a

portal and executes a business transaction in the background. If a business transaction is not executed directly

(because the effective date is more than ten days in the future) the customer has to plan a BTS instead of creating

a postdated application.

4.7 Required Manual Periodic Tasks

This section describes all manual tasks that you are required to run periodically in order to keep the application

operating smoothly over time. Such tasks may be required on component level and are therefore relevant in each

scenario that uses the component. Other tasks may be relevant for certain business scenarios only. It is important

that you monitor the successful execution of these tasks on a regular basis.

Manual Tasks for FS-PM

Task Tool(s) Supporting

this Task

Recommended

Frequency

Description

Check application

and job log of batch

runs

For each of the

batch runs

implemented in FPP

(see 4.6.1), the logs

can be accessed by

clicking Job Logs

and Applications

Logs in the Reports

section of the

screen.

To analyze the

application log

independent of the

batch run started,

start the

transaction Analyze

Application Log

(SLG1).

After each run Description of Batch Runs Implemented

in FPP



CUSTOMER


4.8 Load Balancing

For information about load balancing of msg.PM runtime calls, see section 5.3 in the following document in the

msg.PM directory on the system DVD/CD:

\msg.PM_Connection\Documents\2_English\PM_Con_FSPM_Admin_Man.pdf

38

CUSTOMER



High Availability

5 High Availability

High availability is a technically complex area, and implementation considerations vary according to your system

setup.

For technical guidance when developing a high availability strategy or when implementing a specific product or

feature, contact the appropriate source, such as your SAP consultant or your hardware partner. For more

information about business continuity in general in SAP environments, look for SAP Business Continuity and

High Availability for Operating Systems in SAP NetWeaver 7.5.



Software Change Management

CUSTOMER


6 Software Change Management

Software Change Management standardizes and automates software distribution, maintenance, and testing

procedures for complex software landscapes and multiple software development platforms. These functions

support your project teams, development teams, and application support teams.

The goal of Software Change Management is to establish consistent, solution-wide change management that

allows for specific maintenance procedures, global rollouts (including localizations), and open integration with

third-party products.

This section provides additional information about the most important software components.

The following topics are covered:

Transport and Change Management

Enables and secures the distribution of software changes from the development environment to the quality

assurance and production environment.

Development Request and Development Release Management

Enables customer-specific maintenance procedures and open integration with third-party products.

Template Management

Enables and secures the rollout of global templates, including localizations.

Quality Management and Test Management

Reduce the time, cost, and risk associated with software changes.

Support Packages and SAP Notes Implementation

Provide standardized software distribution and maintenance procedures.

Release and Upgrade Management

Reduces the time, cost, and risk associated with upgrades.

6.1 Transport and Change Management

For general information about transport and change management, look for Change and Transport System in

SAP NetWeaver 7.5.

Component Change Management Tools

Component Solution Manager Maintenance

Optimizer Integration

Transport Management Tool

FS-PM No FS-PM uses the standard transport and change

management procedures. The patches are

available on SAP Service Marketplace.


40

CUSTOMER



Software Change Management

6.2 Support Packages and Patch Implementation

An SAP Note will be created to accommodate possible interdependencies between single components when

implementing a higher support package or patch level.

Up-to-date information on SAP Notes, support package levels, and patches is published on SAP Service

Marketplace at http://service.sap.com/swdc.


http://service.sap.com/swdc

http://service.sap.com/swdc


Troubleshooting

CUSTOMER


7 Troubleshooting

In case of errors, you should thoroughly read the information provided in the system error messages. In many

cases a suggestion is made what to do to correct the error.

If an error occurs during an update run, try to exclude the policy or contract causing the error from the selection

(using the select options for the Policy Number field in transaction /PM0/ABY_FPP_FP_PA).

If the information provided in the error message does not solve the problem, it may be useful to search for the

software coding causing that error. To do so, access the technical information of the error message, check the

message ID (if it does not start with /PM0/, the problem is very likely to be caused by customer coding), and

navigate to the coding that created the message:

42

CUSTOMER



Troubleshooting

If the coding causing the error does not belong to a class or function module starting with /PM0/, the problem is

very likely to be caused by customer coding.

Otherwise, you should search in SAP Notes for references either to the message ID or to the object causing the

error. If you find any relevant notes, carefully analyze the information provided and check whether the note might

solve the issue, and whether or not the note has already been implemented.

For more information about the support desk management, see Support Desk Management.


Concept for Handling Custom Development

CUSTOMER


8 Concept for Handling Custom Development

For information about how to enhance SAP Policy Management, see SAP Policy Management -> How-to Guides ->

Enhancement Guide.


44

CUSTOMER



Support Desk Management

9 Support Desk Management

Support Desk Management enables you to set up an efficient internal support desk for your support organization

that seamlessly integrates your end users, internal support employees, partners, and SAP Active Global Support

specialists with an efficient problem resolution procedure.

For support desk management, you need the methodology, management procedures, and tools infrastructure to

run your internal support organization efficiently.

9.1 Remote Support Setup

SAP support needs to be able to work remotely for highest efficiency and availability. Therefore all required

support tools must be remotely accessible for SAP support.

Connecting to SAP: https://support.sap.com/remoteconnection.

9.2 Problem Message Handover

Use a corresponding subcomponent of component FS-PM for Message Handling.

You can find more information about installation and configuration under SAP Policy Management -> Installation

and Upgrade -> Installation Guide.

9.3 Related Information

The following table contains links to information relating to the Application Operations Guide.

Content Quick Link to SAP Service Marketplace

Related SAP Notes notes

Released Platforms platforms

Network Security securityguide

network

Technical Infrastructure ti

SAP Solution Manager solutionmanager

https://support.sap.com/remoteconnection


http://service.sap.com/notes

http://service.sap.com/platforms

http://service.sap.com/securityguide

http://service.sap.com/network

http://service.sap.com/ti

http://service.sap.com/solutionmanager

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.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered

trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System ads, System i5, System

p, System p5, System x, System z, System z10, System z9, z10, z9,

iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS,

S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise

Server, PowerVM, Power Architecture, POWER6+, POWER6,

POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,

BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2

Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,

Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are

trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and

other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either

trademarks or registered trademarks of Adobe Systems

Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the

Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,

VideoFrame, and MultiWin are trademarks or registered trademarks

of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered

trademarks of W3C®, World Wide Web Consortium, Massachusetts

Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc.,

used under license for technology invented and implemented by

Netscape.

SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge,

ByDesign, SAP Business ByDesign, 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 in

several other countries all over the world. All other product and

service names mentioned are the trademarks of their respective

companies. Data contained in this document serves informational

purposes only. National product specifications may vary.

These materials are subject to change without notice. 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.