SAP® Documentation

Single view

/PM0/ABQ_MIGRATION_OBJ_TEST - Test Migration of Insurable Objects

TXBHW - Original Tax Base Amount in Local Currency   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

You can use this program to test the transfer of data from a legacy system to FS-PM for the Insurable Object (INBO) business object.

Integration

Prerequisites

  • Insurable objects already exist in FS-PM.
  • You have created an internal number range for the Number Range Object /PM0/ABN21 (numbers of insurable objects) to avoid errors occurring during the update of newly created insurable objects. You do this in Customizing for Policy Management under General Settings -> Number Ranges -> Object Management ->Define Number Range Intervals for Insurable Objects. Or choose the transaction SNRO.

Features

This program reads the data of an insurable object in FS-PM and formats it for data migration.

The data is formatted either as a text file or directly for the call of function module /PM0/ABQ_OBJM_MASSMIGR (mass migration interface for the insurable object).

The format of the data in the text file is compliant with that expected in Legacy System Migration Workbench (LSMW). In LSMW, the record types of the source fields must contain, as the identifying field content, the name that is found at the start of the corresponding row in the created text file. For example, if the identifying field content for the BAPI control parameter were /PM0/BAPI_ABQ_MIGRATION, then this would be /PM0/ABQINSOBJ for the insurable object header.

This program is an example only, and makes no claim to be complete.

It shows the project team how data from a legacy system needs to be formatted to enable successful migration to FS-PM.

This program simulates data migration by creating one or more copies of an existing insurable object.

Selection

  • Insurable Object
Enter the number of an insurable object created in FS-PM (preferably not one that has been migrated) that is used as a template for the new (migrated) insurable object to be created.
  • Migrate
The program reads the data of the template insurable object and converts it to the corresponding table for the call of data migration.
The program calls function module /PM0/ABQ_OBJM_MASSMIGR with the data created, and the function module saves the unchecked data to the database (raw data).
  • Create Migration File
The program reads the data of the template insurable object and downloads it to a text file. This file is used as an input file for LSMW. This is the basis for data migration from the legacy systems envisaged by SAP. LSMW transfers the data from the input file to IDOCs, which then save the data in the system using function module /PM0/ABQ_OBJM_MASSMIGR.
  • Display Data
The program reads the data of the template insurable object and converts it into migraration data structures. The resulting data is only displayed on the screen. It is not processed.
  • Separator for Migration File
The program uses the selected separator to create the migration file to separate the attributes.
  • Number of Insurable Objects to Be Created
You can specify the number of new insurable objects to be created from the template insurable object.
  • Execute Validation
  • If you select this checkbox, the validation will be started immediately after the raw data is updated to the database.

  • If you do not select this checkbox, the data is written unchecked to the database (raw data), and you must validate and release them in a second step. To execute validation and release, use transaction /PM0/ABQ_FP_Q_OBJVAL.


In live migration, you should execute the steps - posting of raw data and the validation/release - separately for performance reasons.
  • Release
  • If you select this checkbox, the program returns a successfully validated insurable object for immediate processing.

  • If you do not select this checkbox, you must release a successfully validated insurable object in a separate validation run.

This checkbox is relevant only if you have also selected the Execute Validation checkbox.

  • Display Empty Fields
If you select this checkbox, the program displays the empty fields of the migration structure (with initial value) in the output list.

Thus you display which fields are available in the migration structures.
  • Display Descriptions
  • If you select this checkbox, the program displays the corresponding ABAP Dictionary descriptions for the fields of the migration structure.

  • If you do not select this checkbox, the program displays only the migration fields and their contents without any additional description.

Standard Variants

Output

The program displays the insurable objects created together with the individual fields of the migration structure and their contents.

In a log file, the program lists any errors that occur (under Execute Migration). Successfully updated insurable objects are displayed in the output list.

Activities

To go to processing of an insurable object, select the Execute Migration radio button and click the required insurable object number in the output list.

Example

Create a local class in the program that inherits from class LCL_VISITOR, for example
CLASS ZLCL_VISITOR DEFINITION INHERITING FROM LCL_VISITOR.

Use either an implicit enhancement spot or the customer report ZPM0_LEGACY_OBJ_MIG_ICL (you need to create this as a report of the type INCLUDE) for the class definition. The Z report is integrated in the source code.

Now create the following FORM routine (in the enhancement spot or the Z report):

FORM zz_set_type_obj_visitor CHANGING CV_TYPE TYPE STRING.
CV_TYPE = 'ZLCL_VISITOR'.
ENDFORM.

This form is called from the report before the instantiation of class LCL_VISITOR. Instead of the standard class LCL_VISITOR, an instance of ZLCL_VISITIOR is now called created and called (including your redefined methods).

The same enhancement technique is also available for the local class LCL_MIGRATION. To instantiate any class you create that inherits from LCL_MIGRATION, create the following FORM routine:

FORM zz_set_type_migr CHANGING CV_TYPE TYPE STRING.
CV_TYPE = 'ZLCL_MIGRATION'.
ENDFORM.






rdisp/max_wprun_time - Maximum work process run time   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 8773 Date: 20191213 Time: 090144     sap01-206 ( 46 ms )

Our Service

Looking for Support? Questions?

The

Consolut

Callback-Service

Leave us your contact details and we will call you back. Panels marked with * are mandatory.