sap fs345 en col95_part_nw_arani

FS345SAP Policy Management -Implementation Scenarios

SAP for Industries - SAP for Insurance

Date

Training Center

Instructors

Education Website

Participant HandbookCourse Version: 95Course Duration: 5 Day(s)Material Number: 50101106

An SAP course - use it to learn, reference it for work

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.sapcertified.com OR Contact Via Email Directly At : [email protected]


For any SAP Online Training Email: [email protected] or visit : www.araniconsulting.com


Copyright

Copyright © 2011 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP AG. The information contained herein may be changedwithout prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software vendors.

Trademarks

• Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® areregistered trademarks of Microsoft Corporation.

• IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®,S/390®, AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation.

• ORACLE® is a registered trademark of ORACLE Corporation.• INFORMIX®-OnLine for SAP and INFORMIX® Dynamic ServerTM are registered

trademarks of Informix Software Incorporated.• UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.• Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®,

VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarksof Citrix Systems, Inc.

• HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, WorldWide 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, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP

EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.comare trademarks or registered trademarks of SAP AG in Germany and in several other countriesall over the world. All other products mentioned are trademarks or registered trademarks oftheir respective companies.

Disclaimer

THESEMATERIALS ARE PROVIDED BY SAP ON AN "AS IS" BASIS, AND SAP EXPRESSLYDISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR APPLIED, INCLUDINGWITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY AND FITNESS FOR APARTICULAR PURPOSE, WITH RESPECT TO THESE MATERIALS AND THE SERVICE,INFORMATION, TEXT, GRAPHICS, LINKS, OR ANY OTHER MATERIALS AND PRODUCTSCONTAINED HEREIN. IN NO EVENT SHALL SAP BE LIABLE FOR ANY DIRECT,INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES OF ANYKIND WHATSOEVER, INCLUDING WITHOUT LIMITATION LOST REVENUES OR LOSTPROFITS, WHICH MAY RESULT FROM THE USE OF THESE MATERIALS OR INCLUDEDSOFTWARE COMPONENTS.

g2011112252951





About This HandbookThis handbook is intended to complement the instructor-led presentation of thiscourse, and serve as a source of reference. It is not suitable for self-study.

Typographic ConventionsAmerican English is the standard used in this handbook. The followingtypographic conventions are also used.

Type Style Description

Example text Words or characters that appear on the screen. Theseinclude field names, screen titles, pushbuttons as wellas menu names, paths, and options.

Also used for cross-references to other documentationboth internal and external.

Example text Emphasized words or phrases in body text, titles ofgraphics, and tables

EXAMPLE TEXT Names of elements in the system. These includereport names, program names, transaction codes, tablenames, and individual key words of a programminglanguage, when surrounded by body text, for exampleSELECT and INCLUDE.

Example text Screen output. This includes file and directory namesand their paths, messages, names of variables andparameters, and passages of the source text of aprogram.

Example text Exact user entry. These are words and characters thatyou enter in the system exactly as they appear in thedocumentation.

<Example text> Variable user entry. Pointed brackets indicate that youreplace these words and characters with appropriateentries.

2011 © 2011 SAP AG. All rights reserved. iii





About This Handbook FS345

Icons in Body TextThe following icons are used in this handbook.

Icon Meaning

For more information, tips, or background

Note or further explanation of previous point

Exception or caution

Procedures

Indicates that the item is displayed in the instructor'spresentation.

iv © 2011 SAP AG. All rights reserved. 2011





ContentsCourse Overview ......................................................... vii

Course Goals .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viiCourse Objectives ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii

Unit 1: PBT & IFBC ........................................................ 1PBT Workplace... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2In-Force Business Configurator .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Unit 2: C&D BADI ........................................................ 77Check and Derive BAdIs .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Unit 3: PMG, Journal & TMF.......................................... 101Product Module Groups... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102Journal in FSPM .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Time Model Framework ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124

Unit 4: Release Machine and Business Functions.............. 129Release Machine and Business Functions ... . . . . . . . . . . . . . . . . . . . .130

Unit 5: Object Management........................................... 141Object Wizard ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142

2011 © 2011 SAP AG. All rights reserved. v





Contents FS345

vi © 2011 SAP AG. All rights reserved. 2011





Course OverviewTarget AudienceThis course is intended for the following audiences:

• SAP Technical Consultants• SAP Application Consultant• Partner Consultants• Customer Implementation Team

Course PrerequisitesRequired Knowledge

• ABAP programming techniques and object oriented programming in R/3• ABAP Dictionary

Recommended Knowledge

• [Enter recommended knowledge or delete if none.]

Course GoalsThis course will prepare you to:

• Learn how to configure and customize FSPM in order to meet some of thetypical customers’ requirements the FSPM implementation team has to dealwith

Course ObjectivesAfter completing this course, you will be able to:

• Understand the technical background of the FSPM• Understand how to use the FSPM framework to generate new objects• Learn how to customize and configure FSPM• Create customer-specific classes and methods and write FSPM-specific

coding• Learn how to reuse standard FSPM functionalities

2011 © 2011 SAP AG. All rights reserved. vii





Course Overview FS345

viii © 2011 SAP AG. All rights reserved. 2011





Unit 1PBT & IFBC

Unit Overview[Enter a brief overview of the unit.]

Unit ObjectivesAfter completing this unit, you will be able to:

• Understand what the PBT (policy-based technology) is: developmentframework of FSPM

• See the benefits of the layer architecture of FSPM and understand each layer• Get familiar with the workplace• Learn how to extend existing entities of the FSPM data model with

customer-specific fields• Understand the main usage of IFBC (In-Force Business Configurator):

handling of product information for FS-PM• Understand the main benefits of the IFBC• Learn which steps have to be taken when introducing a new characteristic• Learn which steps have to be taken when introducing a new attribute

influencing in-force business• Realize the benefits of the “write protection status” for characteristics

property set

Unit ContentsLesson: PBT Workplace ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2

Exercise 1: PBT Workplace & IFBC ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Lesson: In-Force Business Configurator .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Exercise 2: IFBC ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

2011 © 2011 SAP AG. All rights reserved. 1





Unit 1: PBT & IFBC FS345

Lesson: PBT Workplace

Lesson Overview[Enter a brief overview of the lesson.]

Lesson ObjectivesAfter completing this lesson, you will be able to:

• Understand what the PBT (policy-based technology) is: developmentframework of FSPM

• See the benefits of the layer architecture of FSPM and understand each layer• Get familiar with the workplace• Learn how to extend existing entities of the FSPM data model with

customer-specific fields

Business ExampleBusiness analysts from the Blue Sky Insurance Company have identified two newcustomer-specific fields, which need to be stored in the policy administrationsystem.

Sara and John need to create these fields in FSPM.

PBT– Layer Architecture Overview

Figure 1: PBT Workplace – Introduction

• FS-PM has been implemented by using PBT.• PBT itself has been implemented by using PBT.






FS345 Lesson: PBT Workplace

Figure 2: PBT Workplace – Introduction

Figure 3: PBT Workplace – How to Start?

• Start transaction SPRO and choose the SAP Reference IMG button to goto the Customizing.

• Alternatively, open the PBT workplace using transaction code/N/3FW_START.







Figure 4: PBT Workplace – How to Start?

• Open the navigation tree as shown and push the button.• First, an application number has to be selected. The standard application

number for FS-PM is 0001.• We recommend that you do not change this standard application in an

implementation project.







Figure 5: PBT Workplace – Layout Elements

• The PBT workplace layout shows a standard SAP Application Bar, aNavigation Tree, Detail Screen (displays different properties with respect tothe selected node in the navigation tree), Model Screen (graphical design ofnode hierarchies in the selected node category), and an Application Logger(place where the interaction output is provided to the users).







Figure 6: Navigation Tree Elements

• The navigation tree on the left side can be used to navigate through thePBT workplace.

• On the right-hand side, the detail screen can be found. The informationdisplayed here depends on the activated navigation node.

• When an application is opened, the initial detail screen for every applicationis shown. It contains the basic properties (for example, development classes,transactions) for the application by default.

The FS-PM solution is based on the PBT Framework. The PBT Frameworkdifferentiates between the following layers: business object layer (including entityand persistence layer), the process layer, and the dialog layer.

• The channel layer is used as the communication structure between thedifferent layers.

• PM is built in a very centralistic way: The main element is the businessobject policy that contains policy, contract, and coverage information.Additionally. information can be added at each level by using lateral objects.

• The process layer handles the manipulation of the business object policy inactivities, dialog, and subprocesses.

• The user executes business processes that are developed on the process layer.







Figure 7: PBT– Overview of the Layer Architecture

Database access layer (DAL):

• Manages all entities (database tables) of the DDIC

Business object layer (BOL):

• Manages and supplies single entities from the database.• Groups entities of a business object (= entities relationship management).

Process Layer (PL):

• Has two functionalities:

– Handles activities and processes (business processes)– Monitors the channel layer (process and abstraction respectively)

Channel Layer (CL):

• Displays data in the user interface by using dynpros or BAPIs• Transfers data that is entered by the user to the subordinated layers







Figure 8: PBT – Overview of the Layer Architecture

The layer architecture is based on the client/server concept (superior layers arethe clients of the subordinated layers. The subordinated layers are the server forthe superior layers – for example, the database layer is the subordinated layer forthe business object layer and therefore used as server.) Recalls to superior layersare not allowed by definition of the layer architecture.

The data exchange between the different layers occurs in both directions. Whendata is exchanged, the data is copied to the receiving layer, the data is not gettingreferenced. This is necessary, because each layer has its own context. This meansthat the data is managed by the layer itself and the data gets released by the layeras well. There are no references to the context of a different layer. If the data werereferenced between layers, the principle of capsulation would be annulled and thelayer manager would not have the release control.

Each layer within the PBT workplace has its own layer manager. The layermanager is responsible for the communication between vicinal layers.

Application Programming Interface (API)

• Represents the developed application logic• Replaces or completes the different layers (except for the channel layer)

For example, the API can be used to communicate with surrounding IT systemsby implementing their process and application logic. The data generated bythe API can be transferred to the correct layer. In the case of “communication







with surrounding IT systems”, the API will replace the process layer. On theother hand, the application logic can be encapsulated within the API to work asa communicator between two layers.

Since of the exchangeability of the single layers within the architecture, the APIcan replace each functionality (except for the functionality of the channel layer).The flexibility of the framework regarding the possible insertion is enhancedthrough the API functionality.

Channel Layer

Figure 9: Channel Layer Components

The channel layer is made up of two main components:

• Channel manager• Channel manager control model







Channel structure:

• The used channel structures are defined in channel models within the PBT.Within the channel model, the name and the package of a channel structurewill be mentioned.

• In addition to that, the data includes and data excludes structures, thetransient objects structure and the field modification structures will bedefined in the channel structure as well. The field modification structurescontain information for each attribute of the channel structure. For instance:if the attribute is an output attribute or the user can enter data to it.

• The channel structure represents the central element to transfer and transportdata between application, user interface, and database. The applicationattributes, which can be used within the user interface, are defined withinthe channel structure. The channel structure is used as a global structuretemplate for layer-comprehensive exchange of entity attributes. A channelstructure and a channel model has to be defined for each database table thatwill be used in the application.

• The channel structure never contains any application data.• This application data is managed by the database within the appropriate

operational data table.

Data include structure:

• Describes the source of the attributes. The source can be either the name of astructure or a database table. This depends on the type of the source withinthe data dictionary. (Data structure can contain values as well).

• The data include defines which attributes are part of the channel structure.Unlike the transient attributes, the attributes mentioned in the data includewill be generated directly in the channel structure and are not availableduring run-time only.

Data exclude structure:

• The idea of a data exclude is similar to that of a data include. The onlydifference is that the attributes within the assigned data structure or databasetable cannot be used in the application (exclusion of certain attributes).







Figure 10: Channel Layer – Channel structure

Submodel:

• Submodels are used to built up a hierarchical structure and enable the reuseof predefined channel structures.

Transient Attributes:

• Transient attributes describe the non-persistent attributes. Non-persistentattributes are not stored permanently. These attributes are only availableat run-time.

• Transient attributes are used for calculated values within the meta model.• Attributes from check tables can be part of the channel structure as well.

Key-Include:

• By activating this flag, the key attributes will be included in the channelstructure and can be used in the application.

OID-fields (Object-ID fields):

• Determine if the channel structure is to contain the attribute for OID or not.







Figure 11: Channel Layer – Communication

Controller Model:

• Has a hierarchical structure and represents an abstract model of the UserInterface (GUI).

• Each node represents a certain section of the user interface.• Every section is assigned to a different controller (for example, images,

tab strips).

The channel manager manages the controller model and is responsible for thecommunication to the process layer.







Figure 12: Channel Model

Channel Model PBT Representation

Process Layer

Figure 13: Process Layer – Components







Figure 14: Process Layer – Process Model

There are three different types of models:

• Linear• Hierarchical• Ramifications/cycles

Figure 15: Process Model

Process Model PBT representation







Figure 16: Process Model – Process Node

Process Node

Figure 17: Process Layer – Subcontroller Model

Subcontroller model







Figure 18: Process Layer – Subcontroller Model

Each node of the subcontroller model represents a section of the user interface(GUI). In general, the start node represents a carrier dynpro.

Figure 19: Subcontroller Model – Node Attributes

Subcontroller model PBT representation







Figure 20: Subcontroller Model – Screen Assignment

Subcontroller model PBT dynpro assignment to load on display







Figure 21: Process Layer – Communication with Channel Layer

• The communication between the process layer and the channel layercomprises:

• The handling and storage of data are represented by the channel controllersand executed by subcontrollers. Subcontrollers are implemented within theprocess layer.

• The subcontroller handles the data of a screen section assigned to a channelcontroller. This subcontroller provides and saves the data in case of request.

• For example: If data is sent to a dynpro (to be displayed on the screen),the data is provided by a subcontroller. If data is read from a dynpro, it issent to a subcontroller.

• A subcontroller itself communicates with the underlying business objectlayer by using the channel manager to read or write data.

• To correct/rephrase: Each screen section including and the related channelcontroller is assigned to a subcontroller; the structure of the channelcontroller model is the same as the subcontroller model. The relationshipof both controllers is ensured by the same naming convention of bothcomponents.

Example: get_attributes

• The channel manager calls the method get_attributes within the PBO ofdynpro (process before output event).

• This communicates with the process layer.







Business Object Layer

Figure 22: Business Object Layer – Components

The business object layer framework consists of four modules. Each of thesehas its own access interface.

Figure 23: Business Object Layer – Business Object Manager

• The business object manager has access to business objects and can traversethe hierarchical structure of the business object.

• In addition to the first functionality, the business object manager is theinterface to the database access layer and manages the database transactions.

• This means the business object manager initiates the correct execution (ofopening and closing a database transaction) of transactions on database leveland manages the writing and reading of data.







Figure 24: Business Object Layer – Business Object Model

The business object model is a summarization of entities by different relevantbusiness aspects.

The following business object models exist:

• Correspondence• Distribution Plan• Third-Party Management• Funds, Funds Range• Funds Price• Global Funds Order• Funds Order• Object Management• In-force Business Management• Master Policy Management• Case Facts Management







The most important business object is the in-force business management(FS_PM_POLICY_MANAGEMENT). You can differ several entities along themain axis:

• Policy: (/MSG/ABDAPOLICY),• Contract: (/MSG/ABDAPOLPR),• Coverage Bundle: (/MSG/ABDACOVPAC),• Coverage: (/MSG/ABDACOV),• Subcoverage: (/MSG/ABDACOVCP),• Insured Object: (/MSG/ABDASUBJCT)

There are more entities, for instance, the lateral objects.

Figure 25: Business Object Tree – Structure

A business object is the summary of multiple entities from various business pointsof view.

The business object in SAP Policy Management is hierarchically structured (has atree form) and consists of many nodes.







Each node has 2 components:

• BOE(or C) Class – Is used by the process layer to read or write data froman entity.

• The system differentiates between BOE (Business Object Element) and BOC(Business Object Composition).

– A BOE is a node that can have no children “to correct: (for instance,a line of business node, because the child nodes are always under thebasis node)”.

– BOE nodes do not support a navigation functionality (parent nodescannot be accessed, nor child nodes since they do not exist).

– BOC supports this functionality.• Loader – This is also called load strategy. The loader is responsible for

loading data into the BO and for saving data from the BO. A BO node (orBOE(C)) can have multiple loaders, defined in Customizing. The systemdecides which one to use at runtime. It is theoretically possible to load datafrom a database table or from an XML file. This has not yet been used inPolicy Management.

The BO model defines which persistence service (DA model) the loader is to use.

“to correct: Each entity can have a basis part and a savings part”. If an entityhas both parts, it has two nodes in the BO tree that contain the basis and LoBattributes. Nodes of this sort then have a sibling relationship, meaning that theLoB node is only linked to the basis node and cannot have child nodes.

The LoB node an example of a BOE node.

The loader and BOE(C) classes are generated from template classes with thePBT Workplace.

The BO Manager manages the business object. Transactions such as loading,saving, or generating new BO nodes are done using the BO Manager.







Figure 26: Business Object Layer – Business Object Model

• A business object consists of single business objects elements.• A business object composition (short: BOC) is represented by the single

notes of a tree-structured BO, which can have children or enhancements.BOC have general attributes, besides the tree-specific attributes. The generalattributes are the same for all different versions of the assigned businessobjects.

• Business Object Elements are the enhancements of a business objectscomposition. The attributes of a BOE are valid for the specific element only.

• From that point, a BOC is always a BOE, because a part of the attributesis node-specific.

• This implies that a BOC can be viewed by two different aspects: As acomposition the focus is set on the whole tree (including children andenhancements), as an element the focus is set on the node as itself.

Figure 27: Business Object Layer – Business Object Element Loader (BOL)

Business object element loader







Figure 28: Business Object Model

Business Object Model PBT representation

Figure 29: Business Object Model

Business object model PBT representation of loader







Figure 30: Entity Model

Entity Model PBT representation

Figure 31: Entity Model – Entity







Database Access Layer

Figure 32: Database Access Layer – Components/Services

Figure 33: Communication: BO Layer – DA Layer

The figure above represents the communication scenario by showing thecorresponding call of methods, which are processed during the load of a businessobject :

• The business object manager calls the BO loader to find data.• The BO loader calls the database agent to read data.• If a set of data was found, the information is given back to the business

object manager.

The business object manager is also responsible to create a BOC/BOE objectinstance with respect to the current retrieved set of data.







Figure 34: Persistence Model

Persistence Model PBT representation







Exercise 1: PBT Workplace & IFBC

Exercise ObjectivesAfter completing this exercise, you will be able to:• Learn how to extend existing entities of the FSPM data model with


Business Example• Business analysts from the Blue Sky Insurance Company have identified

two new customer-specific fields that need to be stored in the Policyadministration system.

• Sara and John have to create these fields in FSPM.

Task:1. Create custom data element and domain

2. Create/Edit Append Structure

3. Add a custom field in append structure

4. Synchronize Channel Model

5. Set Channel Model attribute characteristics

6. Create Function Group for screens

7. Edit Main Program and Top Include of Function Group

8. Create a custom screen

9. Edit subcontroller model

10. Assign custom screen to dialog model node (CVIEW or Enhancement)







Solution 1: PBT Workplace & IFBCTask:1. Create custom data element and domain

a) Create a customer variant to be used in the business scenarios along thecourse – general approach:

• Type in /n/pm0/3fw_start transaction

Figure 35: SAP Easy Access

• Double-click on the workplace icon

Continued on next page







Figure 36: Workplace

• Choose the FS-PM application and choose execute.









• Select the standard customer variant and choose execute.


• Right-click the 00001 application subnode under the workplace andselect the customer variant option.








Figure 39: Application Data

• Click the create customer variant button to add a new variant.

Figure 40: Customer Variant Maintenance

• Enter the name and the previous customer variant to override andclick save.









• Choose a corresponding transport request – if none is available, thencreate one.


• Go back to the customer variant maintenance screen. Deactivate thestandard PM0 customer variant and activate the one that you created inthe previous steps. Save the changes.









• Select the new customer variant. Stop the /pm0/3fw_start transactionand restart it, by selecting the corresponding customer variant for thefspm application.

2. Create/Edit Append Structure

a) Create custom data element and domain

• Type in the SE11 transaction and type the name of the new dataelement into the data type field.

Figure 44: ABAP Dictionary: Initial Screen

• Hit create, then choose data element.








Figure 45: SAP

• Fill in the short description, the domain field, and the field label tab.

Figure 46: Dictionary: Change Data Element









• Save and choose a corresponding package.









• If you entered a custom domain, double-click it to create it.

Figure 49: SAP

• Enter the short description and data type with number of characters ifrequired. Save into the same package and activate the domain.

Figure 50: Dictionary: Change Domain

• After the domain is active, go back to the data element and activate itas well.









3. Add a custom field in append structure

a) Settle for a level and tab where you want to add the fields – policy, contract, coverage, etc. – for instance policy level. (instructor note:when you settle for a level or tab detail to add a new field, you actuallysettle for a different business transaction. Usually channel structureschanges from one business transaction to another)

4. Synchronize Channel Model

a) Identify the channel structure by using f1 f9 technique (instructor note:easiest way) on the desired screen

• Identify the channel structure by using f1 f9 technique (instructornote: easiest way) on the desired screen.








Figure 52: New Business: Process Policy

• Or by using the &showtech command get the subcontroller model andgo to the PBT workplace with /n/pm0/3fw_start .


• Search the identified subcontroller model and navigate in the dialognode (p_b_mdia01) to the corresponding tab in p_b_tab01. Selectingthe tab will present you with the channel structure.









• There is also the case when the channel structure does not appear inthe form of a dictionary structure, but an internal table for example. Inthis case, you can choose the process context by double-clicking it.Take a look in the attrib field, because it has the channel model. Afterthis, search for the indentified channel model in the corresponding nodeand you find the channel structure











5. Set Channel Model attribute characteristics

a) After the channel structure is known (/pm0/abcapolicy in our case), addthe custom field using a custom include.








• Open the se11 transaction and fill in the indentified channel structure.


• Choose the collapse all button to have a better picture of the includestructures.

Figure 59: Dictionary: Display Structure

• Double-click on the persistent include to navigate to it – persistence itgiven by the group name – here: BAPOLICY_PE. (ba*_pe or ba*_tr fortransient). In this include, scroll to the last line to find the enhancementstructure. Double-click on it to navigate to its context. In this includethe customer include resides that we need to edit, CI_ABAAPOLICY.










• Double-click the CI_ABAAPOLICY customer include. If this is notcreated, a popup will be displayed in order to create it. Otherwise, thecontext of the include will be displayed normal.








Figure 62: SAP

• Fill in the required data and add the new field by using the dataelement created previously.

Figure 63: Dictionary: Change Structure

• Go to extras→ enhancement category and choose the enhancementcategory.








Figure 64: Dictionary: Change Structure

• Save and activate. Use the previously defined package.

6. Create Function Group for screens

a) Synchronize the channel model. PBT will automatically adjust thedifferences introduced by the new field in the channel structure.

• Go to PBT, search for the corresponding channel model, in our case/PM0/ABDAPOLICY, change to edit mode, right-click the channelmodel and synchronize.









• A popup appears asking if you want to save. The answer is “yes”.Then, you must choose a customizing transport request. You can usethe one previously defined in our example. Finally, a popup with thefields for comparison is displayed. You have to pick your field fromhere and click synchronize.


• Extend the attribute properties of the channel model and scroll downin order to newly added field. This is in pink since it is not saved.Double-click it to edit its properties and save.









7. Edit Main Program and Top Include of Function Group

a) Create a function group for screen using se80.

Figure 68: Object Navigator








• Go to the main program and paste the following code.

Figure 69: ABAP Editor: Change FunctionPool

• Go to the top include and paste the following code.

Figure 70: ABAP Editor: Change Include

• Create a custom screen as shown








Figure 71: Screen Painter: Change Screen

• Put the new field from the channel structure on the screen layout.

Figure 72: Screen painter: Change Input/Output Field

• Draw the border box. Save and activate the dynpro.








Figure 73: Screen painter: Change Box

• Go to the screens flow logic and paste the following code.

Figure 74: Screen Painter: Change Screen

• Save and activate the whole function group








Figure 75: Screen Painter: Display FunctionPool

8. Create a custom screen

a) Edit subcontroller model

• Go to PBT and search for the corresponding subcontroller model (canbe indentified with &showtech – described in a previous step). In ourcase, this is p_b_d_pol on policy level.









• Extend the p_b_tab1 node within the dialog node mdia.









• We are going to add the new field to the policy data tab. To do this,we extend the p_b_scrn01 node.


• Double-click the Extension policy node. You can also choose differentsubnodes for life, p&c, and so on. Note that it has the enhanceablefeature on. Click on the screen assignment tab in order to link it tothe newly created subscreen from your function group. Paste here thefunction group name in the subprogram name field, screen numberin the view id field, and based on what the screen holds, choose thecorresponding class name (to be discussed further in the course).









• Now go to the Attributes tab and check the process context,channel structure variable, constraint class (handles the display ofthe subcontroller model subnode, /PM0/CL_3FM_FALSE returns bydefault false so you must erase it) and controller attribute (will beexplained further in the course).









• Save the changes and start the new business transaction. The newfield should be on policy level under the general policy data box andright before the TCN as the subnode configuration in pbt shows. To seeif the data is correctly passed to the channel structure: put somethingin the custom field and choose enter. If the text remains, then the datais passed correctly to the channel structure and the configuration ofthe subnode is valid.


9. Edit subcontroller model

a) Run inquiry transaction on a newly released policy to see if the changehas been propagated correctly in the database. You might notice thateven if all the fields are for display yours is ready for input. To maintainthe same default behavior across the existing business transactions, youwould have to maintain the field modifier structure by adding your fieldproperty to it. This structure can be identified in pbt, if you go to thechannel model and read the field modifier value. In our case, this is/PM0/ABFAPOLICY .









• Open the structure with se11


• Add your new field with component type /PM0/3FJ_FIELDMOD-IFIER to the current field modifier structure by using the appendstructure technique.








Figure 84: Dictionary: Change Append Structure

• Save and activate. Now you can test again by running inquiry.


10. Assign custom screen to dialog model node (CVIEW or Enhancement)

a)







Lesson Summary

You should now be able to:• Understand what the PBT (policy-based technology) is: development

framework of FSPM• See the benefits of the layer architecture of FSPM and understand each layer• Get familiar with the workplace• Learn how to extend existing entities of the FSPM data model with


Related Information

• [Enter an optional eference using the URL or CrossReference tag toadditional information that learner may find useful. Examples includewebsites or whitepapers. Delete if not used.]







Lesson: In-Force Business Configurator



• Understand the main usage of IFBC (In-Force Business Configurator):handling of product information for FS-PM

• Understand the main benefits of the IFBC• Learn which steps have to be taken when introducing a new characteristic• Learn which steps have to be taken when introducing a new attribute


property set

Business ExampleSara and John need to customize the appearance of the newly created fields on theSAP GUI screens for different templates.

• The In-Force Business Configurator is a key tool that is used to ease thecollaboration between product engine and policy administration.

• The In-Force Business Configurator uses policy templates that are subsets ofall product possibilities the product engine permits

• The structure information (lateral objects and cardinalities) and the attributesthat influence in-force business will be held in the policy templates of theIn-Force Business Configurator.

• Policy templates control the graphical user interface of the application (forexample, mandatory fields, optional fields, display fields).

• The default field values and the value ranges will be set through policytemplates.

• Every policy within the system is based on a policy template, created bythe In-Force Business Configurator.






FS345 Lesson: In-Force Business Configurator

Figure 86: Product data and insurance mathematics at runtime – BEFOREFS-PM Release 4.5

Figure 87: Product data and insurance mathematics at runtime – SINCEFS-PM Release 4.5







Figure 88: Role of the In-Force Business Configurator

Figure 89: Role of the In-Force Business Configurator







Figure 90: In-force Business Configurator – Basic Access

In–force Business Configurator Policy Templates

Policy templates are the heart of the In-Force Business Configurator. They are partof the individual Customizing.

Policy templates control the behavior of the objects (sales product, product,premium…) at the time of operation runtime).

Policy templates have the following information:

• Name• Product assignment• Behavior of the characteristics of the entities

– Field modification– Default values– Value Ranges

• Instances of the entities that influence in-force business attributes• Assignment of subordinated templates including cardinalities







Figure 91: In-Force Business Configurator: Operative Use

Figure 92: In-Force Business Configurator: Worklist

Figure 93: In-Force Business Configurator: Write Protection Flags







Characteristic Write Protection (Flag A) is responsible for protecting the followingsettings against overwriting with import:

• Field modifier (mandatory/recommended/optional field, displayed/hidden)• Initial value permitted• Field relevant for template

Default value write protection (Flag B) is responsible for protecting default valuesetting against update within product data import. It does not affect the List ID.

Table ID Write Protection (Flag C) is responsible for protecting the List ID againstimport.

Relevancy (Flag D) determines whether this characteristic is relevant for thisparticular template or not. This should not be mistaken with the flag set in channelmodel (in PBT) which determines whether the attribute is IBC relevant in general(for all templates). After the import the IBC automatically tries to determinewhich attributes are relevant for every template, which does not necessarily meanthat the setting should remain.

Figure 94: In-Force Business Configurator: Product Data Import

Figure 95: In-Force Business Configurator: Mass Import







Figure 96: In-force Business Configurator – Extensibility

Management summary

The In-Force Business Configurator manages and edits policy-relevant data bythe means of policy templates.

A policy template describes the runtime behavior of a contractual object inin-force business.

To configure a policy template, data about interface control and the structureinformation have to be entered.

Every policy within the system is based on a policy template, created by thein-force business configurator.







Exercise 2: IFBC

Exercise ObjectivesAfter completing this exercise, you will be able to:• Customize the appearance for different templates of the newly created fields

in the FS-PM system

Business Example• Sara and John have to customize the appearance for different templates of

the newly created fields in the FS-PM system.

Task:1. Copy the 92H0000S0000 life product template

2. Release and fix the errors of the new template.

3. Add the characteristic for the new create field on the chars tab of the newtemplate.

4. Customize the characteristic in order not to display the field.

5. Save and release the new template.

6. Create 2 policies: one to see that the field is displayed (using the originalproduct template ); the other one to check if the field has been suppressed (byusing the copy template, recently created)







Solution 2: IFBCTask:1. Copy the 92H0000S0000 life product template

a) Copy the 92H0000S0000 life template into a new template in IFBC– select and right click → copy – it should be presented in FS340 indetail.– step already completed using the Excel sheet for generatingIDs. Release the templates and fix the errors.

• Go to the character tab of a product template copy in change modeand choose the compare button. Your field will be added to thecharacteristics table. From here, you can adjust its value to appear ornot to appear within a product template.

Figure 97:

• Go to the characteristics tab in the product template and modify thenewly added field characteristic to hidden. Uncheck the used property(only this one counts, the hidden status is automatically assumed ifthe used property is unchecked and the template is saved) from thecharacteristics tab belonging to your new field characteristic. Saveand release the template.








Figure 98: In-Force Business Configurator

• Create a new policy based on newly copied product template to checkif the added field has disappeared.

Figure 99: Start New Business









• Use the standard product template to create a policy with the newlyadded field on the policy data tab.

Figure 101: Start New Business









2. Release and fix the errors of the new template.

a)

3. Add the characteristic for the new create field on the chars tab of the newtemplate.

a)

4. Customize the characteristic in order not to display the field.

a)

5. Save and release the new template.

a)

6. Create 2 policies: one to see that the field is displayed (using the originalproduct template ); the other one to check if the field has been suppressed (byusing the copy template, recently created)

a)







Lesson Summary

You should now be able to:• Understand the main usage of IFBC (In-Force Business Configurator):



property set

Related Information







FS345 Unit Summary

Unit SummaryYou should now be able to:• Understand what the PBT (policy-based technology) is: development

framework of FSPM• See the benefits of the layer architecture of FSPM and understand each layer• Get familiar with the workplace• Learn how to extend existing entities of the FSPM data model with

customer-specific fields• Understand the main usage of IFBC (In-Force Business Configurator):



property set

Related Information

• [Enter an optional reference using the URL to additional information thatlearner may find useful. Examples include websites or whitepapers. Deleteif not used.]






Unit Summary FS345






FS345 Test Your Knowledge

Test Your Knowledge

1.

2.






Test Your Knowledge FS345

Answers

1.

Answer:

2.

Answer:






Unit 2C&D BADI

Unit Overview


• Explain the purpose and usability of Business Rules• Understand the Check&Derive concept of performing input checks and field

(values) derivations• List the most relevant BAdIs that can be used in the implementation project

to perform customer-specific checks and derivations

Unit ContentsLesson: Check and Derive BAdIs .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Exercise 3: Check and Derive BAdIs .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95






Unit 2: C&D BADI FS345

Lesson: Check and Derive BAdIs



• Explain the purpose and usability of Business Rules• Understand the Check&Derive concept of performing input checks and field



Business ExampleSara and John attended a workshop with the Blue Sky Insurance team andidentified a couple of business rules related to the newly created customer-specificfields.

The first rule is: The newly created fields must have an initial value set.

The second rule: If the insurance start date is in the past (compared to the systemdate), the first field must have one value. Else, if the insurance start date is in thefuture, then the field value is different.

The third rule: The value of the second field has to be derived based on the valueof the first field.

Figure 103: Overview






FS345 Lesson: Check and Derive BAdIs

Issues with Business Rules Concept

Priority: Event CHANGED + Derivation of duration

• Recursive cycles:

– Each set_attributes cannot activate a chain of derivatives→ Missing control execution→ Debugging is extremely challenging→ Maintenance is very hard

General issue:

• Dialog processing→ not available in mass processing

• Finding a particular Business Rule can be a very complex task

Figure 104: (Old) Business Rules

• Default Values: predefined fields/attributes values• Derivations: derivation of the fields/attributes values based on the values of

other fields or combination of the fields and certain rules• Checks: Execution of input checks







Figure 105: Default Values

Figure 106: Derivations and Checks







Figure 107: Business Rules Triggers

• Business Rules triggered by business object-related events should ensure aconsistent BO at any point in time.

• Business Rules triggered by process-related events should ensure thecorrectness of the process.








In case of the business transaction handling the Check&Derive are executed atcertain activities. For example, in class /PM0/CL_ABP_BPP_BTX_A_CAC_XCTin method /PM0/IF_3F_BPP_ACTIVITY~EXECUTE, you will find

• ...• * update premiums• CALL METHOD lr_btxconc_srvc->update_premium_diffs•• is_policy_key = ls_abvapolicy• iv_btx_id = lv_btx_id• iv_effective_dt = lv_effective_dt• iv_lob_cd = lv_lob_cd• ir_btx_api = lr_btx_api.• & Do derivations for display ... PAI was too early• /pm0/cl_abp_check_and_derive=>check_and_derive_uboi(• iv_bo_id = ls_abvapolicy-bo_id• iv_secpol_id = ls_abvapolicy-secpol_id ).

The Class itself is called from process node P_B_P_CHECK_AND_CALC inprocess model P_B_S_BTX_A_XCT.

An example of a BT-specific BR check is in class/PM0/CL_ABP_BPP_BTX_N_XCT_PROD called from process nodeP_B_P_PRODCHANGE_XCT of the same process model. The execute methodof the class calls super->/pm0/if_3f_bpp_activity~execute, which executes theBusiness Rule (GC_END).







Figure 109: Business Rules Customizing

Figure 110: Business Rules Customizing







Define Business Rules and Events

• Use• Business rules define checks, derivations, and default values for business

objects. They are mapped in the system in the form of classes.• In this IMG activity, you define the following for the individual business

rules:• Which business process, which activity group, and which activity• For which entity• For which event• The business rules are executed.• For the Customizing of a new business rule, it is first necessary to determine

an event such as “business transaction conclusion for the policy level”,“calculation of the policy”, or “release of the application” for each purpose.This event is either already available in Customizing, or you have to create it.

• New events are created in a maintenance view that is not visible in the IMG.The creation of new events represents a modification and must be handledexclusively by experienced ABAP developers.

• The following entries are required for the creation of a new execution event:• Mandatory: business process ID (for example, N for new business, C for

change)• Optional: activity ID; the specified rules are then executed at the time of

execution for the activity• Optional: activity group ID (same effect as for activity ID)• Optional: entity (the business object element for which the specified rule

classes are to be executed)• Mandatory: the time of execution for the business rule (predefined values

that can be customized).• If you have defined or selected a time of execution, you can maintain the

actual business rule classes that contain logic for this time of execution. Youalso have to specify the sequence. It determines the sequence in which therule classes are processed.

• Standard settings• To run FS-PM without receiving errors, it is strongly recommended

that you copy the sample Customizing for this Customizing activity.Customer-specific extensions are possible. However, they need to complywith existing business rules, as they can result in unwanted reciprocity.







Figure 111: Implementation

Check&Derive

• Check&Derive is a new concept of the implementation of business rules.• It was introduced in FS-PM 4.1.• It is intended that Check&Derive concept fully replaces (old) business rules.• Standard and custom-specific checks and derivations are (to be) implemented

following the Check&Derive concept.• Call takes place with each call of PAI_END.

Class: /PM0/CL_3F_CDM_MAIN_CTRL

Method: /PM0/IF_3F_CC_EVENT~PAI_END

• Change of the source field in field modification structures: /PM0/A*FAENTITand AUMLT (= input memory)

• Steps:

– Possibility to skip check by customer– Lock memory against changes (avoid dead loops)– Do input checks, first standard fields, then customer appends– Do persistent derivations, first simple, then complex; first standard

fields then customer appends– Do transient derivations, first simple, then complex; first standard fields

then customer appends– Release memory

• Transaction to switch on/off C&D: /PM0/AB_SWITCH_CND







Figure 112: Concept Check&Derive – Schema

What is covered by Check&Derive?

Intention of Check&Derive

• Execute checks• Execute derivations

Business Object specific events

• CREATE (Creation of an entity)• CHANGED (Changing of an entity)• BEFORE_DELETE (Before deletion of an entity)

Process-specific events

• INIT (Access Business Transaction (BTX))• EXECUTE (During a BTX)• END (End of a BTX)

What is NOT covered by Check&Derive?

Business object-specific events

• INITIALIZE (Loading of an entity)

→ Business rules of this event will not be replaced by C&D.







Process-specific events

• CHECK + CALCULATE

→ Enhancement for partners and customers via C&D process BAdIs

• APPROVE

→ Release process is one big BAdI

• PARTNER_REFRESH

→ After return from another system – BP and insurable object management

msg.PM events

• Enhancement for partners and customers via BAdI

In the C&D concept (new business rule concept), the processdefines a certain point in time when the business rules for theevent CHANGE have to be applied (check&derive time nor-mally after each PAI – process after input). See class/method/PM0/CL_3F_CDM_MAIN_CTRL–>/PM0/IF_3F_CC_EVENT~PAI_END

The key issue for the derivation of the event CHANGED is to identify the fieldsthat have changed and accordingly process the checks and derivations basedon theses changes. The source fields of these changes are stored in the fieldmodification structures (input memory) /PM0/A*FA<ENTITY> (for example,/PM0/ABFAPOLPR for the contract). Due to the memory input (field modificationstructures) technique multiple or dependent derivations are avoided. Only thechanges that take place between the last and the actual execution of the C&Dare stored. As for the old business rules, there is a visitor concept for the dialogprocessing (but this one works differently, because one entity is only visited once).

You can find the constants for the process-specific points in time in the attributesof class /PM0/CL_AB_BPU_RULES (GC_INIT, …).

Useful Terms

Term

• Source field = Trigger for a derivation• Target field = Field that is affected by the derivation







Classification of derivations

• Transient Derivation

– All derivations with a transient field as target field– Simple transient: Source field(s) and transient target field belong to

same entity– Complex transient: Source field(s) and transient target field belong

to different entities• Persistent Derivations

– All derivations with a persistent field as target field– Simple persistent: Source field(s) and persistent target field belong

to same entity– Complex persistent: Source field(s) and persistent target field belong

to several different entities


Check&Derive Triggers

At what points in time are checks or derivations (C&D) needed?







Business object-specific points in time

• CREATE (creation of an entity)• INITIALIZE (loading of an entity) – (comment: here, business rules are

not replaced by C&D.)• CHANGED (changing of an entity)• BEFORE_DELETE (before deletion of an entity)

Process-specific points in time

• INIT (access business transaction (BTX))• EXECUTE (during a BTX)• END (end of a BTX)

Check and Derive Changed

Intention of the event:

• Check and/or Derive for one field that is changed

However, if necessary information within the business object is not complete,do the checks at point in time END.

Activation of coding

• Name of filter BAdI: /PM0/ABP_BCA_DERIVE_BADI• Filter: entity

Sequence of method calls of the interface /PM0/IF_ABP_BCA_DERIVE_BADI

• DO_INPUT_CHECKS• RUN_PERSISTENT_DERIV• SET_TRANS_EASY• SET_TRANS_COMP

For the other points in time, an old concept is used (business rules), which will beexchanged step by step.

Derivations normally means that due to some source fields one or more targetfields are “derived”.

Dialog processing

• Event is automatically triggered within PAI

Background processing

• No derivation of transient target fields (performance)• Explicit call of event: /PM0/CL_ABP_CHECK_AND_DE-

RIVE=>CHECK_DERIVE_BTX_UBOI







How to find out which field has changed?

• Input memory within the BAdI (type /PM0/A<LoB>FA<Entity>)• Check whether field is TRUE (= ‘X’) or FALSE (= ‘ ’)

BAdI: Check and Derive for entities (CHANGED)

Use

• You can use this Business Add-In (BAdI) in SAP Policy Management(FS-PM) for partner/customer- specific checks and derivations for the Policybusiness object.

• The checks and derivations are called when individual data fields arechanged in a business object.

• The BAdI considers different lines of business for the Policy business object.

Standard settings

• This BAdI definition does not contain any active BAdI implementation.• The BAdI is filter-dependent:• IV_ENTITY: Entity name for which the checks and derivations are to be

performed• IV_LOB_CD: Line of business• The BAdI is designed for multiple use.

Activities

• Information about the implementation of BAdIs in the context of theenhancement concept is available in the SAP Library for SAP NetWeaverunder BAdIs – Embedding in the Enhancement Framework.

Example

If you want to execute derivations at the time that the Clause entity is changed,define the coding for the derivation in the corresponding BAdI implementation.

• This BAdI uses the /PM0/IF_ABP_BCA_ENTITY_BADI2 interface. Formore information, display the interface in the Class Builder.

Check & Derive – Create / Before_Delete


• Check and/or Derive when an entity is created (for example, dynamic defaultvalues)

• or before it is deleted (for example, deleting dependent entities)


• Name of filter BAdI: /PM0/ABP_CREATE_DERIVE_BADI• Filter: entity







Sequence of method calls of the interface /PM0/IF_ABP_CREATE_DE-RIVE_BADI at CREATE

• DO_DERIV_PERS_CREATE• DO_DERIV_TRANS_CREATE• DO_CHECKS_CREATE

Sequence of method calls of the interface /PM0/IF_ABP_CREATE_DE-RIVE_BADI at BEFORE_DELETE

• DO_CHECKS_BEFORE_DELETE• DO_DERIV_PERS_BEFORE_DELETE• DO_DERIV_TRANS_BEFORE_DELETE

BAdI: Derivations/Checks When Creating/Deleting Entities

Use

• This Business Add-In (BAdI) is used in SAP Policy Management (FS-PM)in the CHECK&DERIVE area.

• You can use this BAdI to execute checks and derivations at the time ofcreation (CREATE) and before deletion (BEFORE_DELETE) of an entity.

• While the system executes these checks and derivations, the Policy businessobject is completely readable. Write access is only given to the customerinclude of the corresponding entity.

Requirements

• You use the UBOI factory to create entities.

Standard settings

• This BAdI definition does not contain any active BAdI implementationdefined by SAP.

• The BAdI is filter-dependent. The entity name of an entity in the Policybusiness object is the filter for the BadI.

• The BAdI is designed for multiple use.

Activities

• Information about the implementation of BAdIs in the context of theenhancement concept is available in the SAP Library for SAP NetWeaverunder “BAdIs – Embedding in the Enhancement Framework”.

Example

• If you want to execute derivations at the time that the Clause entity iscreated, define the coding for the derivation in the corresponding BAdIimplementation.







See also

• This BAdI uses the interface /PM0/IF_ABP_CRDLDRV_CUSTBADI.

Check&Derive – Init/Execute/End


• INIT – Checks and transient derivations when entering a business transaction• EXECUTE – Checks, persistent and transient derivations when executing a

business transaction• END – Checks, persistent and transient derivations when completing a

business transaction


• Name of filter BAdI: /PM0/ABP_PROC_DERIVE_BADI• Filter: Business Process ID and Business Transaction ID

Sequence of method calls of the interface /PM0/IF_ABP_PROC_DERIVE_BADIat INIT

• DO_CHECKS_INIT• DO_DERIV_TRANS_INIT

Sequence of method calls of the interface /PM0/IF_ABP_PROC_DERIVE_BADIat EXECUTE

• DO_CHECKS_EXEC• DO_DERIV_PERS_EXEC• DO_DERIV_TRANS_EXEC

Sequence of method calls of the interface /PM0/IF_ABP_PROC_DERIVE_BADIat END

• DO_CHECKS_END• DO_DERIV_PERS_END• DO_DERIV_TRANS_END

Event has to be triggered manually within business transaction

• /PM0/CL_ABP_CHECK_AND_DERIVE=>CHECK_AND_DE-RIVE_PRCINIT

• /PM0/CL_ABP_CHECK_AND_DERIVE=>CHECK_AND_DE-RIVE_PRCEXEC

• /PM0/CL_ABP_CHECK_AND_DERIVE=>CHECK_AND_DE-RIVE_PRCEND

Check&Derive







Within all checks and derivations, there are three levels:

• Level 1: SAP Standard• Level 2: Partner – for example, LoB add-ons like FS-PMAuto• Level 3: Customer

Technical realization via filter BAdIs

• Standard = SAP internal use only• Partner/Customer = multiple use or different BAdIs

However, partners and customers have no write access to the fields of thestandard… ... but …

Figure 114: Check&Derive

Figure 115: Check&Derive







Exercise 3: Check and Derive BAdIs

Exercise ObjectivesAfter completing this exercise, you will be able to:• Learn how to use BAdIs to check and derive values on different fields

Business Example• Sara and John need to customize the appearance for different templates of the

newly created fields in FS-PM system. Sara and John attended a workshopwith the Blue Sky Insurance team and they identified a couple of businessrules related to the newly created customer-specific fields.

• The first rule is:The newly created fields must have an initial value set.• The second rule: If the insurance start date is in the past (compared to the

system date), the first field must have one value. Else, if the insurance startdate is in the future, then the field value is different.

• The third rule: The value of the second field has to be derived based on thevalue of the first field.

Task:1. IMG Customizing for BAdi : Check and Derivation of Entities

2. 2. Enhancement and BAdI implementation







Solution 3: Check and Derive BAdIsTask:1. IMG Customizing for BAdi : Check and Derivation of Entities

a) Navigate to the corresponding IMG Activity within the ImplementationGuide (IMG):

Choose Policy Management –> In–Force Business Management –>Basis –> Business Processes –> Business Rules

2. 2. Enhancement and BAdI implementation

a) Select customizing activity: BAdI: Check and Derivation of Entities

b) Create an enhancement implementation ZPM_CD_ENTITY 12

c) Create a BADI implementation ZPM_CD_POLPR_IMPL 2 for theBAdI: /PM0/ABP_BCA_ENTITY_BADI – default settings/checking/derivation of entities

d) Specify Implementation Class ZPM_CL_POLPR 3

e) Create filter for an entity /PM0/ABDAPOLPR 4

Steps 1 to 6 are to be executed once. Once they are completed, differentchecks and derivations are to be implemented by implementingcorresponding methods of the class ZPM_CL_POLPR.

f) Navigate to the implementation class ZPM_CL_POLPR. Double-clickimplementing class node.

The first rule is: The newly created fields must have an initial value set.

• Implement the Set_Default_Attributes method. Use this code:

METHOD /PM0/IF_ABP_BCA_ENTITY_BADI~SET_DE-FAULT_ATTRIBUTES. DATA : LS_POLPR TYPE /PM0/AB-WAPOLPR. FIELD-SYMBOLS : TYPE ANY. " heretype any can be replaced with the exacttype of the field - see DDIC BREAK-POINT'I047813'. " breaks onlyfor your user name LS_POLPR = CS_BASIS.ASSIGN COMPONENT 'ZZFIELD1' OF STRUCTURECS_BASIS TO IF IS ASSIGNED = '1'." default value is set ENDIF. ENDMETHOD.








The second rule: if the insurance start date is in the past (comparedto the system date), the first field must have one value. Else,if the insurance start date is in the future, then the field value isdifferent. The third rule: The value of the second field has to bederived based on the value of the first field.

• Implement the Set_Pers_Attributes method. Use the followingcode:

METHOD /PM0/IF_ABP_BCA_EN-TITY_BADI~SET_PERS_ATTRIBUTES. DATA : LS_POLPRTYPE /PM0/ABWAPOLPR. FIELD-SYMBOLS TYPE ANY.FIELD-SYMBOLS TYPE ANY. BREAK-POINT'I047813'. LS_POLPR = IS_BASIS. ASSIGNCOMPONENT 'ZZFIELD1' OF STRUCTURECS_BASIS_CI TO . IF IS ASSIGNED. IF (LS_POLPR-POLPRODBEG_DT < SY-DATUM ). " mayrequire conversion = '1'. ELSE. " >=sy-datum = '2'. ENDIF. ENDIF.ASSIGN COMPONENT 'ZZFIELD2' OF STRUCTURECS_BASIS_CI TO . IF IS ASSIGNED.IF IS ASSIGNED. IF > 3 AND( < 8 ). ='0'. " inside open interval ELSE.= '1'. " outside closed intervalENDIF. ENDIF. ENDIF.ENDMETHOD.







Lesson Summary

You should now be able to:• Explain the purpose and usability of Business Rules• Understand the Check&Derive concept of performing input checks and field








FS345 Unit Summary

Unit SummaryYou should now be able to:• Explain the purpose and usability of Business Rules• Understand the Check&Derive concept of performing input checks and field








Unit Summary FS345






Unit 3PMG, Journal & TMF

Unit Overview


• Understand the three aspects in the product module group Customizing:Product Model Classes, Product Model Groups, and Dimensions

• Realize the benefits of grouping the product modules: avoid Customizingfor each individual product module

• Tell where the Journal Management is located in the architecture• Describe the difference between the business object and the Journal• Understand at which business object level journal process takes place• Make the appropriate IMG settings• Understand the time model functionality within FS-PM• Explain the difference between scheduled and unscheduled changes• Define the necessary steps to implement the time model function• Make the appropriate IMG settings

Unit ContentsLesson: Product Module Groups ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102

Exercise 4: Product Module Groups ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107Lesson: Journal in FSPM .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113Lesson: Time Model Framework... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124






Unit 3: PMG, Journal & TMF FS345

Lesson: Product Module Groups



• Understand the three aspects in the product module group Customizing:Product Model Classes, Product Model Groups, and Dimensions

• Realize the benefits of grouping the product modules: avoid Customizingfor each individual product module

Business ExampleSara and John attended a workshop with the business analysts from the Blue SkyInsurance and they have identified the following business requirement: Policyrenewal has to be scheduled on the insurance end date and a new correspondencetype has to be created to produce a renewal notice.

Product Management – Communication Between Product and ContractManagement

Communication from the product manager and in-force business management isclearly structured and packaged. Data exchange takes place in two directions:

• The reference model describes the properties of contract management andis imported to the product manager. The SAP data categories are mappedto the msg.PM data categories, such as ACCP Integer, CHAR String (max.255 characters).

• Data is imported to PM from contract management, to allow calculations tobe performed there and to enable the reconciliation process with the referencemodel. The reference model cannot be edited in the product manager.

• Data is exported from the product manager to contract manager – staticproduct data and calculation results. In contract management, the systemadministrator uses Extension Services for enhancements.

Access to Insurance Mathematics Methods






FS345 Lesson: Product Module Groups

The new interface to the insurance mathematics is set up as follows (from thepoint of in-force business management):

• Definition of one interface per line of business• One interface method exists per insurance mathematics method.• No hooking of BO reference; Objects are hooked in a structural form

as input and output parameters• Return and hooking parameter should be reduced to a minimum.• Existing root parameters will be hooked as single parameters to the interface.• Data that is needed from the old application status (old state) is directly

forwarded (within the interface).

Figure 116: Summary Advantages/Disadvantages

Figure 117: Overview – Customizing until Release 3.0







Figure 118: Overview – Customizing as of Release 3.1

Figure 119: Overview – Reasons for Developing Product Module Customizing

Figure 120: General Information – Define Product Module Groups







Figure 121: General Information – Define Product Module Groups

Figure 122: General Information – Group Dimensions







Figure 123: General Information – Group Dimensions







Exercise 4: Product Module Groups

Exercise ObjectivesAfter completing this exercise, you will be able to:• Navigate to the relevant Customizing activities in IMG• Define Dates for customer-specific time model functions• Define customer specific time model functions• Define execution criteria for customer-specific time model functions• Implement customer-specific time model function• Create customer-specific correspondence type

Business ExampleTo link customer-specific correspondence type/standard correspondence type tocustomer specific date

• Sara and John attended a workshop with the business analysts from the BlueSky Insurance and they have identified the following business requirement:

– Policy renewal has to be scheduled on the insurance end date and a newcorrespondence type has to be created to produce a renewal notice.

Task:In almost all customer implementations there are business requirements to

• Perform customer-specific policy/contract/coverage scheduling

• Create customer-specific correspondence on a specific date or for a specific period

In this exercise, you will implement a date and time model function to schedule arenewal notice on policy end date 1 .

1. You will also implement a new correspondence type to produce a renewalnotice. And finally,

2. You will attach this new correspondence type to already created date andtime model functions.







Solution 4: Product Module GroupsTask:In almost all customer implementations there are business requirements to

• Perform customer-specific policy/contract/coverage scheduling

• Create customer-specific correspondence on a specific date or for a specific period

In this exercise, you will implement a date and time model function to schedule arenewal notice on policy end date 1 .

1. You will also implement a new correspondence type to produce a renewalnotice. And finally,

a) Navigate to the corresponding customizing activity within IMG(Implementation Guide 1 )

Policy Management → In-Force Business Management → Basis →Update → Time Model

2. You will attach this new correspondence type to already created date andtime model functions.

a) Additional control parameters for the implementation of a date or timemodel function are displayed here for information. You can onlychange these parameters in developer Customizing (/PM0/CUST_INT)in the activity Internal Customizing→ Update/Time Model → DefineDates and Time Model Functions

b) Define customer-specific date and time model functionZPM_TMF_RENEWAL as copy of already existing RNWLNVTN

c) Using transaction code SE24, copy class/PM0/CL_ABZ_BPU_TMF7_RNWLNVTN into ZCL_TMF_RE-NEWAL. Determine_Dates_AUA method is already implemented – byredefinition. Get_Next_Date method must be redefined, next (samecode of Determine_dates_aua):

METHOD DETERMINE_DATES_AUA.

DATA:

lt_cor_dates TYPE /pm0/abducordt_t

.

BREAK-POINT 'I047813'.

mr_tc_cordt->get_cordt_by_id(

EXPORTING








is_polpr_key = is_tmfctrl-polpr_key

iv_date_id = /pm0/if_abz_bpu_tmf_public~mv_date_cd

IMPORTING

et_cordts = lt_cor_dates ).

IF lines( lt_cor_dates ) = 0.

ev_next_dt = lcl_constants=>gc_hidate.

ELSE.

ev_next_dt = is_polpr-polprodend_dt.

ENDIF.

ENDMETHOD.

d) In time model function Customizing for ZPM_TMF_RENEWAL, useZCL_TMF_RENEWAL Class instead of the one filled in by the copyoperation. (Check the tree to see if the entries are consistent.)

e) After defining the date and the time model function, we have to definethe execution criteria for the time model function : Select the productmodule group to which you want to assign it to, and then double-clickon it, in order to assign it to the product module group tree entry. Setits change cat to 75 – planned time based processing after unplannedchange.

f) Release a policy and do an inquiry – contract journal on section date(last). – after successful release of policy fs pm schedules a date asdescribed in the redefinition of mentioned methods.

g) Correspondence: In our example for RNWLNVTN date has the BM06correspondence – this is standard and can be reused accordingly(tocheck; or to test) in all the settings described in the following steps. Justmake sure that under correspondence management → correspondencecontrol → automatically schedule correspondence→ date control(in force business img entry), you assign your date to the bm06correspondence – only needed for the correspondence part to quicklycustomize instead of going through the rest of the steps.

• Navigate to the corresponding customizing activity within IMG(Implementation Guide)Policy Management → CorrespondenceManagement → Edit Basic Setting for General Correspondence.Unlike other IMG activities, you have to click the IMG ActivityDocumentation symbol.

• You can use either the existing form class or create a new onedepending on business requirements. Click Define Form Classes.Click Define Form Classes Customizing activity. Copy standard








form class /PM0/ABC_POLICY to ZABC_POLICY and library/PM0/ABC_POLICY_INCL to ZABC_POLICY_INCL 2. Aftercompletion of this activity, choose the change button to proceed.To finish this activity, you have to generate the DDIC types, whichare needed. Verify system generated logs to ensure this activity iscompleted successfully. Activate the new form class.

• Now you will create a new application form. This isnecessary to define customer-specific interfaces (to retrievedata) and output forms (an be Adobe forms or Smartforms).Copy standard Application form /PM0/ABC_PDF_POLICYto ZPM0ABC_PDF_POLICY and standard interface/PM0/ABC_PDF_POLICY to ZPM0ABC_PDF_POLICY 3

• Now you will create a customer-specific Correspondence Typefor Renewal Notice ZR00 4 . Go to correspondence → DefineCorrenspondence types under IMG. Create correspondence typeZR00.

• Next, you will assign the form class created in b. to the newcorrespondence type created in the previous step. Go to definestandard form classes for correspondence under correspondenceentry in img.

• Next, you will assign the application form created in c. to newcorrespondence type created in d. Go to define application formsfor correspondence under correspondence entry in IMG

• Navigate to the corresponding customizing activity within IMG(Implementation Guide)Policy Management → CorrespondenceManagement → Correspondence Control → AutomaticallySchedule Correspondence. Date is ZPM_RENEWAL and Corrtype ZR00.

• Click the Automatically Schedule Correspondence customizingactivity. Here, you can schedule the correspondence type for bothDialog Control and Date Control. Click Date Control. Assign thecorrespondence type already created to Date.

• Navigate to the Customizing activity Policy Management →Correspondence Management → Correspondence Modules →Set FS–PM Specific Correspondence Types. In this activity, youdefine relevant attributes for Additional Attachment Allowed ornot, the application status needs to be calculated for a successfulrelease of this correspondence, and the correspondence typeis Coinsurance Relevant or not. Corr type is ZR00, Correspname is Policy, Corr plan type APPROVE, Disp control PMPR,Coinsurance rel is checheck.








• After the successful release of policy go to the contractjournal to see the defined correspondence date. The resultof the correspondence can be seen under the correspondencecontainer/history; by navigating in the easy menu to thecorrespondence node.







Lesson Summary

You should now be able to:• Understand the three aspects in the product module group Customizing:

Product Model Classes, Product Model Groups, and Dimensions• Realize the benefits of grouping the product modules: avoid Customizing

for each individual product module






FS345 Lesson: Journal in FSPM

Lesson: Journal in FSPM



• Tell where the Journal Management is located in the architecture• Describe the difference between the business object and the Journal• Understand at which business object level journal process takes place• Make the appropriate IMG settings

Business ExampleSara and John attended a workshop with the business analysts from the Blue SkyInsurance and they have identified the following business requirement:

Policy renewal has to be scheduled on the insurance end date and a newcorrespondence type has to be created to produce a renewal notice.

Figure 124: Contract Management: Journal Management







FS-PM stores the history of a contract in two different Journals. The applicationjournal and the contract journal. Journalization means a versioning of all executedchanges of the contract and allows the user to work on a current state or any otherhistorical state of the policy contract. The Journal works on the complete Policyand supports the technical and juristic period administration.

The contract journal stores all changes that have been executed for apolicy/contract. The contract journal administrates the released or publishedcontract states.

The application journal stores all information that is addressed to a policy/contract.The application journal contains the changes that have yet been not released orpublished (sort of 'working' area). If a change to a contract has to be done, thenfirst the journal is read to get the current state of the contract at the effectivedate. This contract state is copied into the application journal. All changes areperformed using this application journal entry. After the changes of the policyhave been completed (application journal now has all information of the change),the current application journal entry is copied to the contract journal and a newversion of the contract is written to the contract journal.

Background processing means that contract changes are executed in thebackground with mass processing and without dialogs (for example, popups). Theupdate of in-force business can be done at any point in time.

General facts about the Journal

Journal entries are created in the background and cannot be changed or createdmanually by a user.

Application, change option, and contract objects have different journals.

Journal entries give an overview of the sequence of performed business processes.

Journal entries are only written for completed processing (for example, afterexecution of a time model function).

Journal management is performed at policy and contract levels.

• Changes to a contract do not affect other contracts.• The journal number is created per policy and independent of the contract.

Versioning







FS-PM distinguishes 2 kinds of versioning (one-dimensional versioning andtwo-dimensional versioning)

1. Dimensional Versioning

Due to changes to objects, new versions are created on the business objects.A new version is directly valid (from key date of change). Changes in thepast or future are not possible.

2. Dimensional Versioning

Due to changes to objects, new versions are created on the business objects.New versions get valid on an effective date, which is independent of the keydate of the change. During the reactivation of an old version, the subsequentversions are not deleted. They are stored on the database with a reversal sign.Changes that are valid for the past or future are possible.

Tasks Journal & Time Model

Journal

The journal keeps track of all executed changes by adding new versions into thejournal. By doing this, the journal is able to reproduce a historical state of a policyor the current state of the policy. The journal controls the creation of an application(request), versions, and releasing of versions. The journal does not call the timemodel and time model function. The journal is valid for all layers of the PBT tool.

Time Model

In FS-PM, planned activities have to be done automatically without actions ofusers. Unplanned activities can happen at every time (in the past or future) andare normally entries done by users. The system has to handle both types ofactivities using time model. The determined contract state often does not matchthe wished effective date. The time model is capable of positioning a request(which is provided by the journal) on an effective date. The time model doesexecute all planned actions. The time model functions are valid for the processlayer of the PBT.

Journal Time model BusinessFunctions

Start Phase 1. CreateApplication(Request)

2. Update at targetdate

Execution Phase 2. Create Version 1. Do changes

End Phase 2. ReleaseApplication(Request)

1. Update







Journal process

• Policies must be changeable for the past and for the future.• The change must be effective on a date that may be different from the date

of the change itself.• The changes must be able to pass a legally required audit (revision). This

means that during a reactivation no contract status are allowed to be deleted.

Status of a Policy

The status of a policy is the set of all valid datasets of a business object until aneffective date. The effective date of a policy status is available in a journal entry.

Contract Status Application Status Change Option Status

Business ObjectContract

Business ObjectApplication

Business Object ChangeOption

Contract Journal Application Journal Change Option Journal

Figure 125: New Business: Sequence







Figure 126: New Business: Technical Sequence

There was no object before => the first entry that can be made is in the applicationjournal.

1. First the process New Business creates the first Application Journal entryand Object Entity version. The object entity version is the last and has nofollowing entity => “99999” as postprocessor entity is fixed. The objectentity obtains the status “A”.

2. The Update Process (1.1.04) creates the next application journal entry andnext entity version. The first entity version now has a postprocessor entityversion => “2” as postprocessor entity is fixed for first version. The secondentity version receives “99999”. The status of the new entity is “A”.

3. The next update process (1.1.05) creates the next application journalentry and next entity version. => “3” as postprocessor entity is fixed forsecond entity version. Third entity version receives “99999” as it has nopostprocessing entity. The status of the new entity is “A”

The changes become approved (Released).

1. All application journal entries are copied into the contract journal.2. The entity versions are “published” => the statuses of all entities are changed

to “P”.







Figure 127: Change: Sequence

Change

Request is created (for the change, a new request valid for the desired effectivedate is created from the valid contract version at the effective date)

Update : If no state at the desired date was found, make the update until thedesired date.

Change: Make the changes on the request object (for example, increase suminsured)

Release: All contract-relevant versions of the business object “Request” arecopied to the business object “Contract”.







Figure 128: Change: Technical Sequence

There was an object before => the last valid entry of the contract journal (“3”) iscopied into the application journal (as “4”)

1. First the process update (1.1.06) changes the application journal entry “4”and creates an object entity version “4”. The object entity version is the lastand has no following entity => “99999” as postprocessor entity is fixed. Theobject entity before is not yet adjusted because this version is published! Thenew object entity gets the status “A”

2. The business transaction “Increase Sum insured” (1.6.06) creates the nextapplication Journal entry and next entity version. The fourth entity versionnow has a postprocessor entity version => “5” as postprocessor entity isfixed for fourth version. Status of new entity is “A”

The changes become approved (Released).

1. All application journal entries are copied into the contract journal.2. The postprocessor number of object entity “3” gets adjusted from “99999” to

“4”.3. The entity versions are “published” => the status of all entities are changed

to “P”.

Reactivation







Reactivation means

• That an old state (historical state) of a business object becomes valid oractive again.

• All versions after the effective date become invalid and are canceled• The reversal occurs in the contract journal• Reversals become relevant when the release of an application happens• Backdated changes are changes with an effective date earlier than the actual

key date

Figure 129: Reactivation: Sequence







Figure 130: Reactivation: Sequence

Figure 131: Reactivation: Technical Sequence







The Journal realizes that the business transaction operates on an older version =>Journal calculates historical contract status and copies the last valid version of thecontract journal (“2”) to the application journal (as “6”)

1. First the process update (1.1.05) updates the Application Journal entry “6”and creates an object entity version “6”. The object entity version is the lastand has no following entity => “99999” as postprocessor entity is fixed. Theobject entity before is not yet adjusted because this version is published! Thenew object entity gets the status “A”

2. The process “Change” (1.6.05) creates the next application journal entry andnext entity version. The sixth entity version now has a postprocessor entityversion => “7” as postprocessor entity is fixed for sixth version. The statusof new entity is “A”

3. The process “Update after change” (1.1.06) creates the next applicationjournal entry and the next entity version. The seventh entity version now hasa postprocessor entity version => “8” as postprocessor entity is fixed forseventh version. The status of the new entity is “A”.

The changes become approved (released).

1. All application journal entries are copied to the contract journal.2. Postprocessor number of object entity “2” gets adjusted from “3” to “6”.3. The contract journal entries and object entities “3”, “4” and “5” get a

cancelation flag4. The entity versions are “published” => the status of all entities are changed

to “P”.

Interface methods for Journals

An application journal (request journal) entry is created by one of thefollowing methods and can be addressed via UBOI (EGOS) – see interface/PM0/IF_ABJ_JOURNAL_UBOI:

/PM0/IF_ABJ_0_PRC_DISPATCHER~CREATE_AMN

/PM0/IF_ABJ_0_PRC_DISPATCHER~CREATE_APL_BY_APL_ENTRIES

/PM0/IF_ABJ_0_PRC_DISPATCHER~CREATE_APL_BY_DATE

/PM0/IF_ABJ_0_PRC_DISPATCHER~CREATE_APL_BY_HIGHEST_VERS

/PM0/IF_ABJ_0_PRC_DISPATCHER~CREATE_APL_BY_POL_ENTRIES

/PM0/IF_ABJ_0_PRC_DISPATCHER~CREATE_APL_BY_POL_ENTRY

/PM0/IF_ABJ_0_PRC_DISPATCHER~CREATE_APL_BY_PRODUCT

An application journal entry often leads to a contract journal entry. An applicationis stored using one of the following methods:

/PM0/IF_ABJ_0_PRC_DISPATCHER~APPROVE_APL







Lesson Summary

You should now be able to:• Tell where the Journal Management is located in the architecture• Describe the difference between the business object and the Journal• Understand at which business object level journal process takes place• Make the appropriate IMG settings

Related Information








Lesson: Time Model Framework



• Understand the time model functionality within FS-PM• Explain the difference between scheduled and unscheduled changes• Define the necessary steps to implement the time model function• Make the appropriate IMG settings

Business Example[Enter a business example that helps the learner understand the practical businessuse of this lesson.]






FS345 Lesson: Time Model Framework

Lesson Summary

You should now be able to:• Understand the time model functionality within FS-PM• Explain the difference between scheduled and unscheduled changes• Define the necessary steps to implement the time model function• Make the appropriate IMG settings

Related Information







Unit Summary FS345

Unit SummaryYou should now be able to:• Understand the three aspects in the product module group Customizing:

Product Model Classes, Product Model Groups, and Dimensions• Realize the benefits of grouping the product modules: avoid Customizing

for each individual product module• Tell where the Journal Management is located in the architecture• Describe the difference between the business object and the Journal• Understand at which business object level journal process takes place• Make the appropriate IMG settings• Understand the time model functionality within FS-PM• Explain the difference between scheduled and unscheduled changes• Define the necessary steps to implement the time model function• Make the appropriate IMG settings







Test Your Knowledge

1.

2.







Answers

1.

Answer:

2.

Answer:






Unit 4Release Machine and Business

Functions

Unit Overview


• Describe how to influence the standard flow of the release machine• Understand how to assign one or more process step types to a process type• Understand the basic idea of encapsulation of the business logic in the

business functions• Describe the principles of the Façade pattern: determining the implementation

based on the filter values and delegating to the implementation

Unit ContentsLesson: Release Machine and Business Functions... . . . . . . . . . . . . . . . . . . . . .130






Unit 4: Release Machine and Business Functions FS345

Lesson: Release Machine and Business Functions



• Describe how to influence the standard flow of the release machine• Understand how to assign one or more process step types to a process type• Understand the basic idea of encapsulation of the business logic in the



Business ExampleSara and John had a meeting with FSPM functional experts.

Together, they concluded that the values of the newly created custom fields haveto be stored in a customer-specific table in the moment when the new policy isbeing released. It is also important that values are increased by 10% in case of aLife Insurance Policy, or by 5% in case of a P & C insurance.

Figure 132: Release Machine and Business Functions






FS345 Lesson: Release Machine and Business Functions










To do this, go to spro policy management → nforce Business Management →asis → usiness Transactions, Actions, and Process Steps → efine Process Typesand Assign Process Step Types.









Different code can be inserted in this method to meet the necessary requirementsof the business case; use other implementations to get an overview of how togather the policy data, get policy method, and then use this data in the necessaryderivations before setting the policy data – set policy method.








Lesson Summary

You should now be able to:• Describe how to influence the standard flow of the release machine• Understand how to assign one or more process step types to a process type• Understand the basic idea of encapsulation of the business logic in the








Unit Summary FS345

Unit SummaryYou should now be able to:• Describe how to influence the standard flow of the release machine• Understand how to assign one or more process step types to a process type• Understand the basic idea of encapsulation of the business logic in the









Test Your Knowledge

1.







Answers

1.

Answer:






Unit 5Object Management

Unit Overview


• Understand the difference between the insurable and insured objects• Learn how to use the object wizard for creating new object categories and

object types for insurable and insured objects within Policy Management

Unit ContentsLesson: Object Wizard ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142

Exercise 5: Business Transactions ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153






Unit 5: Object Management FS345

Lesson: Object Wizard



• Understand the difference between the insurable and insured objects• Learn how to use the object wizard for creating new object categories and


Business ExampleBusiness analysts from the Blue Sky Insurance company have identified newobjects that they want to insure on the market.

Since this kind of an insurance object does not exist in the sample content ofFSPM, Sara and John have to create new objects that can be insured.

Object Wizard

General Comments on the Object Wizard

• From the technical side, the object wizard provided by policy management isbased on the Easy Enhancement Workbench (EEW) of SAP NetWeaver.

• Inside the wizard, all relevant attributes of the object category and/or objecttype are collected. Based on these attributes, several structures are generated,and the complete PBT Customizing and most of the other Customizingsettings are done.

• The object wizard does not change any database table – this has to be donemanually!

• As long as database tables have not been changed, the object wizard can becalled several times for the same object category or object type. Therefore itis not required to specify all attributes in the first run. For a large numberof new attributes an iterative approach can be followed until the generatedstructures are complete.

• For additional tasks, like extending the database table, post processing tasksare generated, which contain the information, what has to be done manuallyafter the generation of the object type.






FS345 Lesson: Object Wizard

Slide Object Wizard – Understanding the Object Wizard Functionality

• The EEW provides the functionality to delete an extension. The deletionwill stop, if:

– A generated structure is already used by a database– An object category that is to be deleted is still used in the object type

Customizing.• In this case, the relevant extension task will write the relevant information

in the protocol.• In this state, it is not possible to start the object wizard again. It is just

possible to eliminate the error situation (that is, remove the relevant structurefrom the database), and to start the deletion process again.

In addition, be aware that the status Created of one task means that the deletionprocess of this task has not started at all.

The deletion of the first task stops, because one structure was still included in adatabase. In this case, the first task will get the status Created with Errors.

The second task will not start at all and will get the status Created. In this case,the protocol section is empty, but this does not mean that all objects are alreadydeleted!

Information about enhancing existing object categories or object types will notbe covered in this document.







Figure 144: Object Wizard – Understanding the Object Wizard Functionality

• Consider the following information/structure, with the correspondingattributes to understand the steps of the object wizard process for creatingnew object categories and object types for insurable and insured objectswithin policy management by the customer or a partner.

• Explain the difference between insured and insurable object:• SAP FS PM differentiates between insurable objects (INBO) oObjects and

items that can be insured in policies) and insured objects (IO) (objects anditems that are being insured in policies and for which risk coverage exists).

– An object potentially to be insured in policies– These are entered and saved centrally in object management and are

described by the characteristics specified

Insured Object

– An insurable object linked to a contract– Objects and items that are insured in policies and for which risk

coverage exists







Figure 145: Object Wizard – Understanding the Object Wizard Functionality

• Consider the following information/structure, with the correspondingattributes to understand the steps of the object wizard process for creatingnew object categories and object types for insurable and insured objectswithin policy management by the customer or a partner.

• The field “Prize of snake” will use the field “CURRENCY_ID” of thetable “/PM0/ABDOINSOBJ”, or “/PM0/ABDASUBJCT”, respectively, asreference field.

• The field “Size of snake” is of type “CHAR”. No reference field necessary.However, if it were of type “QUAN”, then an additional field wouldbe added as reference field. This field will be of the data element“/PM0/INSOBJ_EEW_DEFAULTUNIT_UT” and can be changed manually.

• The name will be created from the original name + UT. If this new namehas more than 16 characters, the suffix UT will be attached after the 14thcharacter. Here: /BOHR/SNAKE_PRUT. This new field will be used asreference field.

Object Wizard – Understanding the Object Wizard Functionality

How to Use the Object Wizard for Creating a new Object Category

The following will describe step by step how to use the object wizard to generatean object category.

First Step: Starting the Object Wizard

The object wizard is started using the SAP transaction EEWB (stands for “EasyEnhancement Workbench””).







In addition, the “EEWB” can also be started via Customizing–IMG (SPRO)Policy–Management → Object Management → Start Object Wizard.

Second Step: Creating a new Project in the EEW

A new project has to be created. For this, choose the button “Create Project” in themenu bar on the top of the screen. (for example, PM_OBJECT_<SUFFIX>). orright-click the folder with your name/User.

Several attributes have to be given:

• Package• Transport requests (only, if the package is not $TMP)• Used namespace• The short namespace is not used within the object wizard

Third step: Creating a new Extension for Creating a new Object Category

For creating a new extension, right-click the project and click “CreateEnhancement” in the context menu. Give it a new name (for example,PM_CAT_<SUFFIX>) and a description.

To create a new object category, choose the EEW Business Object“/PM0/OBJECT_CATEGORY” and choose the extension type“/PM0/CREATE_OBJECT_CAT”

After having chosen all relevant attributes, the wizards starts automatically.

Fourth step: Start the Wizard

First step

On the first screen, the object wizard is described shortly.

Second step

On the second screen, the header data of the object category has to be specified:

• ID of the Object Category. This ID has to be unique.• Name: The name of the object category.• Suffix: The suffix also has to be unique. It is used for the generation of

the structures.

Third step

In the given ALV, the fields of the object category have to be inserted.







Per Field four attributes have to be filled:

1. Field Label: The name of the field2. Field Name: The technical name of the field for the database (not more

than 16 characters)3. Data Element: The data element of the field (The data element must exist

beforehand.)4. IO–Relevant: Flag that marks if the field will be part of the insured or

insurable object.

No recommendation can be given either a field should be part of the insured orinsurable object. Normally, product-specific risk-relevant fields should be in theinsured object. Common data should be in the insurable object.

Fourth step

Additional attributes for the fields have to be captured.

1. Persistent: Marks if the field will be stored on the database or not2. Field Modifier: PBT Customizing “field modifier”3. IFBC-Relevant: Field is relevant for the IFBC. (Mostly, all fields of the

object category)4. PM-Relevant?: Marks if this field is relevant for the PRODUCT ENGINE

(msg.PM)5. PM Attribute Name: Name of the attribute in the PRODUCT ENGINE

(msg.PM)

Due to technical reasons, at least four fields have to exist/be created, two forinsured object, one persistent and one transient, and two for insurable object, onepersistent and one transient. So maybe “DUMMY” fields have to be inserted.Remember that these also have to be unique.

After having finished this step, the generation starts. The successful generationcan be checked in the protocol of the enhancement. The generated objects can beseen in the tasks.

Persistent fields of the insurable object will automatically be used as transientfields for the insured object.

Fifth step: Performing the Postprocessing task

After the generation, post-processing tasks will occur. These describe theadditional manual steps that have to be performed to get the object category run.

With a double-click the post processing tasks, the description is shown. It isdescribed what has to be done. With a right-click on the post-processing task àexecute the system jumps directly to the relevant transaction, where the manualtask has to be done.







The following a short description of the post-processing tasks:

• /PM0/OBJECT_IBC: Note for the activities in the IFBC.

– Will occur once per extension– Will occur every time– Every time a new object category (or object type) was generated, it may

be necessary to adjust the relevant templates.– If at least one field was marked as “PM relevant”, you have to set the

indicators for this new field, to use this field (and its possible values).• /PM0/OBJECT_DB_OIO: Enhancement of the database table

– Will occur once per extension.– Will occur if at least one field for the insurable object was marked as

persistent.– The database tables “/PM0/ABDOINSOBJ1” or “/PM0/ABDOIN-

SOBJ2” are to be enhanced with the persistent fields of the insurableobject of the object category. Use the customer includes for enhancingthe database.

– The generated database include that is to be used (see example:“/BOHR/ABAOIOC_DECINCLREPTIL”) will be specified in thesection general data.

• /PM0/OBJECT_DB_ASB: Enhancement of the database table

– Will occur once per extension– Will occur if at least one field for the insured object was marked as

persistent.– The database tables “/PM0/ABDASUBJ1” or “/PM0/ABDASUBJ2”

are to be enhanced with the persistent fields of the insured object of theobject category. Use the customer includes for enhancing the database.

– The generated database include that is to be used (see example:“/BOHR/ABAASBC_DECINCLREPTIL”) will be specified in thesection general data.

• /PM0/OBJECT_DB_OIO_BACKG: Enhancement of the database table“/PM0/ABCYSUBJCT”

The INCLUDE that is to be used is described in the description.

– Will occur once per extension– Will occur for the insurable object– The structure “/PM0/ABCYSUBJCT_TR” is to be enhanced with the

persistent fields of the insurable object of the object category. Use thecustomer includes for enhancing the structure.

– The generated database include that is to be used (see example:“/BOHR/ABAOIOC_DECINCLREPTIL”) will be specified in thesection general data.







• /PM0/OBJECT_NRI: Allocation of a number range interval to the newobject category.

– Will occur once per extension– Will occur only for the object category of the insurable object– Assign a number range in the corresponding IMG activity (you get

there using transaction “SPRO”→ F5 → Policy Management →Object Management → Assign Number Range to Object Category)to the new object category. If desired, create a new number range inthe relevant IMG activity (Policy Management → General Settings→ Number Ranges → Object Management → Define Number RangeIntervals for Insurable Objects).

• /PM0/OBJECT_VIEW_OBJ_EXTEND: The view /PM0/ABD_INS hasto be extended by the new fields

– Will occur once per extension.– Will occur for the insurable object– The database view “/PM0/ABD_INS” is to be enhanced by the

persistent fields of the new category. To do so, create a new appendview for this database view (use transaction “SE11”→ choose Databaseview → Goto → Append View) and include the fields of the databaseinclude here (see example: “/BOHR/ABAOIOC_DECINCLREPTIL”).The name of the include was specified in the post processing task“/PM0/OBJECT_DB_OIO”.

• /PM0/OBJECT_VIEW_SBJ_EXTEND: The view “/PM0/ABD_SBJ”has to be extended by the new fields

– Will occur once per extension.– Will occur for the insured object– The database view “/PM0/ABD_SBJ” is to be enhanced by the

persistent fields of the new category. To do so, create a new appendview for this database view (use transaction “SE11”→ Database view→ Goto → Append View) and include the fields of the database includehere (see example: “/BOHR/ABAASBC_DECINCLREPTIL”).The name of the include was specified in the post-processing task“/PM0/OBJECT_DB_ASB”.

• /PM0/OBJECT_PM: Note for the activities in the PRODUCT ENGINE(msg.PM).

– Will occur once per extension.– Will occur if at least one field was marked as “PM relevant”.– See also post-processing task “/PM0/OBJECT_IBC”.– To create new insured objects in msg.PM, proceed as follows:

Start msg.PM Designer and choose the appropriate Product Workspace.







Create a new product module of the type VersichertesObjektTyp; ifnecessary, create at first a new product template where you then createthe product module from this template.

Assign the default values for the new product module for the attributes“Objekttyp” ( FS-PM: OBJCAT_CD) and “Objektart“” (FS-PM:OBJTYP_CD) with the values you assigned in FS-PM to the newinsured Object.

Restrict the range of the two attributes “Objekttyp” and “Objektart” tothe default values, no other values are allowed.

Define the new attributes for the insured object.

Define a relationship to the new product module of type“VersichertesObjektTyp” from a product, elementary product bundle,or elementary product,

Create rating rules if necessary.

Export the compilation and perform a PSV import into FS-PM,

Perform an import of product data in the In-Force Business Configuratorin FS-PM.

How to Use the Object Wizard for Creating a new Object Type

For creating a new object type almost the same steps have to be performed asfor creating an object category. In the following, only the differences will bedescribed.

First Step: Starting the Object Wizard

The Object Wizard is started using the SAP transaction EEWB (Easy EnhancementWorkbench).

Second Step: Creating a new Project in the EEW

A project, formerly created for the associated object category, can be reused forthe object type. Otherwise ,a new project can be created.

Third step: Creating a new Extension for Creating a new Object Type

For the creation of an object type, an enhancement with the EEWBusiness Object “/PM0/OBJECT_TYPE” and the extension type“/PM0/CREATE_OBJECT_TYPE” has to be created.

Fourth step: Start the Wizard







There are only differences in the second step within the wizard. The remainingsteps are identical to the creation of an object category. In the second step, theheader data of the object type has to be specified:

• Number (ID) of associated object category• Number (ID) of the object type. This number has to be unique.• Name: The name of the object type• Suffix: The suffix also has to be unique. It is used for the generating

structures to be unique.

Fifth step: Performing the post-processing task

The post-processing tasks are the same with the ones described during the objectcategory creation.

Next, explain the objects that are generated automatically for the object type.

For this operation, consider replacing object category reptil with vessel and objecttype snake with uss enterprise in the previous example and execute the necessarysteps (of course – vessel-relevant properties will be mentioned instead.)

Enter object management (insurable object access) and choose object categoryVessel, object type USS Enterprise. Enter the insurable object information andsave the insurable object.







Exercise 5: Business Transactions

Exercise ObjectivesAfter completing this exercise, you will be able to:• How to customize a business transaction.• How to create an application-wide command.• How to customize a new journal entry.• How to create a new process model.

Business Example• Sara and John were told that every change of the newly created customer

specific fields has to be journalized for all active policies in FSPM.• This is very important for the auditing trial in the Blue Sky Insurance

Company as every change on a policy has to be tracked and documented andclerks have to know what exactly has been changed.

Task:1. In order to start and create a business transaction we have to have a businessprocess in place. Usually this exercise is done by encapsulating the newly addedfields into a custom business process. What we’ll do is to copy an already existingbusiness process in order to show it in a business transaction. So the focus of thismaterial is not in regard to the business process but to the business transactionfunctionality and customizing.

2. You’ll have to create a new process model(by copy and old one) andan application wide command first. Start the PBT Workplace transaction/n/pm0/3fw_start .

Navigate on the level Process Models then choose the already exiting processmodel : P_B_S_PHD_AMD. The name of the new process model has to beZPMT_B_PHD_AMDXX. – use copy object from the right click menu

Enter a description for your process node: Process Model UserXX.

Command on Entry command is already define : CMD_M_ON_ENTRY.

3. The Dialog Model which is called in the process model is the standard one. Thetrainer should explain here the link between these nodes and also show where thescreen is assign with different container classes.

4. After you added a new process model you have to add a new application-widecommand for this process model. Therefore, choose the entry Cross-app.command -> Create on process level.








Command name: ZPMT_A_USERXX

Description: Appl.-wide Command for UserXX

Sequence: 0

Model Name: ZPMT_B_PHD_AMDXX

5. After you added the process model and defined an application-wide commandyou can assign them in the business transaction customizing.

6. Enhance the existing business transaction customizing with the new processmodel. Start the Implementation Guide by using transactions SPRO. Navigateinto the node Policy Management -> In-Force Business Management ->Basis ->Business Transactions, Actions, and Process Steps

7. Enter the new process model (ZPMT_B_PHD_AMDXX) in the customizingactivity Define Business Transactions in the Business Transaction field. Choosethe application-wide command ZPMT_A_USERXX. Transaction is not relevantfor updating. Enter the command ID of the application-wide command. EnterBus. Trans. Name and short name. Caution: The table is cross-client. The nameof the technical business transaction has to be the same like the name of theprocess model.

As of SAP Policy Management 5.1, in the Customizing activity Define BusinessTransactions you can change the following control parameters of a businesstransaction modification-free:

• Executable Between Contract End and Technical End

• Executable on Expiry Date

• One-Time Execution (in a business process

Additional control parameters for the implementation of a business transactionare displayed here for information. These parameters can only be changed indeveloper Customizing (/PM0/CUST_INT) under Internal Customizing ->Control Parameters for Business Transactions. Use Se43 tr code and then displayto access it. In the Customizing activity Define Business Transactions, youcan only process or add business transactions that were previously created indeveloper Customizing. Customers can only reset the one-time execution of abusiness transaction modification-free if One-Time Execution (SAP) allows formultiple execution. As of Release 5.1, you can no longer edit the Update-Relevantfield in the Customizing activity of the standard delivery. You can still edit thefield in developer Customizing, but it is only evaluated in a partner or customerimplementation.








8. As of SAP Policy Management 5.1, the Customizing activity Process BusinessTransaction Groups (/PM0/ABU_CBTXGR) was deleted. Additionally, the groupdimension Business Transaction was deleted in the Customizing activity DefineProduct Module Groups. You now assign business transactions in the In-ForceBusiness Configurator.

9. As of SAP Policy Management 5.1, you can assign business transactionsto a main axis template in the In-Force Business Configurator on the BusinessTransactions tab page. To do so, you select the required business process forwhich you want to assign business transactions under Business Process. You cando this for the following business processes:

• Change

• Application

• Inquiry

• Scroll in Journal

• Mass Change

• Sample Application

• New Business

• Reset

• Reset - Initial Dialog

• Reversal

• Universal Change

In the Business Transactions group box under Assigned Business Transactions,you can display the defined business transaction folders and the assigned businesstransactions. Under Available Business Transactions, the system displays thecurrently unassigned business transactions that are still available for assignment.

In developer Customizing, under Internal Customizing→ Control Parameters forBusiness Transactions, you define which business transactions are available inwhich business process, at which level, and for which lines of business.

You define the business transaction folders in the Customizing activity DefineBusiness Transaction Folders.

You assign the defined business transaction folders to business processes in theCustomizing activity Assign Business Transaction Folders to Business Processes.

10. Test it :







Solution 5: Business TransactionsTask:1. In order to start and create a business transaction we have to have a businessprocess in place. Usually this exercise is done by encapsulating the newly addedfields into a custom business process. What we’ll do is to copy an already existingbusiness process in order to show it in a business transaction. So the focus of thismaterial is not in regard to the business process but to the business transactionfunctionality and customizing.

2. You’ll have to create a new process model(by copy and old one) andan application wide command first. Start the PBT Workplace transaction/n/pm0/3fw_start .

Navigate on the level Process Models then choose the already exiting processmodel : P_B_S_PHD_AMD. The name of the new process model has to beZPMT_B_PHD_AMDXX. – use copy object from the right click menu

Enter a description for your process node: Process Model UserXX.

Command on Entry command is already define : CMD_M_ON_ENTRY.

3. The Dialog Model which is called in the process model is the standard one. Thetrainer should explain here the link between these nodes and also show where thescreen is assign with different container classes.

4. After you added a new process model you have to add a new application-widecommand for this process model. Therefore, choose the entry Cross-app.command -> Create on process level.

Command name: ZPMT_A_USERXX

Description: Appl.-wide Command for UserXX

Sequence: 0

Model Name: ZPMT_B_PHD_AMDXX

5. After you added the process model and defined an application-wide commandyou can assign them in the business transaction customizing.

6. Enhance the existing business transaction customizing with the new processmodel. Start the Implementation Guide by using transactions SPRO. Navigateinto the node Policy Management -> In-Force Business Management ->Basis ->Business Transactions, Actions, and Process Steps

7. Enter the new process model (ZPMT_B_PHD_AMDXX) in the customizingactivity Define Business Transactions in the Business Transaction field. Choosethe application-wide command ZPMT_A_USERXX. Transaction is not relevantfor updating. Enter the command ID of the application-wide command. Enter








Bus. Trans. Name and short name. Caution: The table is cross-client. The nameof the technical business transaction has to be the same like the name of theprocess model.

As of SAP Policy Management 5.1, in the Customizing activity Define BusinessTransactions you can change the following control parameters of a businesstransaction modification-free:

• Executable Between Contract End and Technical End

• Executable on Expiry Date

• One-Time Execution (in a business process

Additional control parameters for the implementation of a business transactionare displayed here for information. These parameters can only be changed indeveloper Customizing (/PM0/CUST_INT) under Internal Customizing ->Control Parameters for Business Transactions. Use Se43 tr code and then displayto access it. In the Customizing activity Define Business Transactions, youcan only process or add business transactions that were previously created indeveloper Customizing. Customers can only reset the one-time execution of abusiness transaction modification-free if One-Time Execution (SAP) allows formultiple execution. As of Release 5.1, you can no longer edit the Update-Relevantfield in the Customizing activity of the standard delivery. You can still edit thefield in developer Customizing, but it is only evaluated in a partner or customerimplementation.

8. As of SAP Policy Management 5.1, the Customizing activity Process BusinessTransaction Groups (/PM0/ABU_CBTXGR) was deleted. Additionally, the groupdimension Business Transaction was deleted in the Customizing activity DefineProduct Module Groups. You now assign business transactions in the In-ForceBusiness Configurator.

9. As of SAP Policy Management 5.1, you can assign business transactionsto a main axis template in the In-Force Business Configurator on the BusinessTransactions tab page. To do so, you select the required business process forwhich you want to assign business transactions under Business Process. You cando this for the following business processes:

• Change

• Application

• Inquiry

• Scroll in Journal

• Mass Change

• Sample Application

• New Business








• Reset

• Reset - Initial Dialog

• Reversal

• Universal Change

In the Business Transactions group box under Assigned Business Transactions,you can display the defined business transaction folders and the assigned businesstransactions. Under Available Business Transactions, the system displays thecurrently unassigned business transactions that are still available for assignment.

In developer Customizing, under Internal Customizing→ Control Parameters forBusiness Transactions, you define which business transactions are available inwhich business process, at which level, and for which lines of business.

You define the business transaction folders in the Customizing activity DefineBusiness Transaction Folders.

You assign the defined business transaction folders to business processes in theCustomizing activity Assign Business Transaction Folders to Business Processes.

10. Test it :







Lesson Summary

You should now be able to:• Understand the difference between the insurable and insured objects• Learn how to use the object wizard for creating new object categories and







Unit Summary FS345

Unit SummaryYou should now be able to:• Understand the difference between the insurable and insured objects• Learn how to use the object wizard for creating new object categories and







FS345 Course Summary

Course SummaryYou should now be able to:

• Understand the technical background of the FSPM• Understand how to use the FSPM framework to generate new objects• Learn how to customize and configure FSPM• Create customer-specific classes and methods and write FSPM-specific

coding• Learn how to reuse standard FSPM functionalities

Related Information

• [Enter an optional reference using the URL to additional information thatlearner may find useful. Examples include websites or whitepapers. Deleteif not used.]






Course Summary FS345






FeedbackSAP AG has made every effort in the preparation of this course to ensure theaccuracy and completeness of the materials. If you have any corrections orsuggestions for improvement, please record them in the appropriate place in thecourse evaluation.




