SAP® Documentation

Single view

/MVA/AMQ_MIGRATION_TEST - FS-PM Auto: Test Policy Migration

RFUMSV00 - Advance Return for Tax on Sales/Purchases   BAL Application Log Documentation  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

You can use this report to test the transfer of data from a legacy system to FS-PM Auto.

This report is for illustrative purposes 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 Auto.

Integration

Prerequisites

  • Auto policies exist in FS-PM Auto.
  • You used the SNRO transaction to create an external number range for each of the /PM0/ABN08 (policy number) number range objects. This prevents errors from occurring when the newly generated policies are updated.
  • For number range object /MVA/AMN01 (bonus/malus ID), you used transaction SNRO to create an external number range.
  • You stored the number range interval for this number range in Customizing activity Policy Management >General Settings >Number Ranges>Choose General Number Range Intervals, in the NRI for Bonus/Malus (External) field (/PM0/ABU_PNRIVS-NRRANGEEXP_ID).

Features

This report simulates data migration by creating one or more copies of an auto policy.

This report reads the data of an auto policy plan in FS-PM Auto 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_POL_MASSMIGR.

The format of the data in the text file is compliant with that expected in Legacy System Migration Workbench (transaction 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/ABQAPOLICY for the policy header.

Selection

  • Policy Number
Enter a policy number created in FS-PM Auto (preferably not a migrated policy), which is to be used as a template for the new (migrated) policy to be created.
  • Migrate
The system reads the template policy and translates it into the corresponding tables for the data migration call.
Function module /PM0/ABQ_POL_MASSMIGR is called with the created data and the unchecked data is saved in the database (raw data).
  • Create Migration File
The system reads the data of the template policy and downloads it as a text file. This file is used as an input file for LSMW. It serves as the basis for data migration from the legacy systems. The report transfers the data from the input file to IDOCs, which then save the data in the system using function module /PM0/ABQ_POL_MASSMIGR.
  • Display Data
The system reads the data of the template policy and converts it into migration data. The system displays the generated data on the screen only. It is not processed.
  • No. of Policies to be Created
1 to n new policies can be created from the template policy.
  • Replace Data
If you select this indicator, the system replaces the numbers of insurable objects (INBOs) in the migrated policy. The system displays two additional fields:
  • INBOs to be Replaced: If you want to replace an insurable object, you must enter the number of the insurable object to be replaced in this field. If you want to replace more than one insurable object, you separate their numbers using ";". If you enter values in this field (several values separated by ";"), then you must enter the same number of values in the Replace by field.

  • Replace by: If you want to replace an insurable object, you must enter the number of the replacement insurable object in this field. If you want to replace more than one insurable object, you separate their numbers using ";". The number of values entered in both the INBOs to be Replaced and Replace by field must be identical. The corresponding INBO number replaces INBO number in INBO to be Replaced field, which is in the same position.

To ensure that the numbers of the insurable objects are replaced successfully, you must enter values in all other fields.
  • Migrate Reversal
Any reversal executed in the template policy is not converted as a policy version, rather it is extracted as a BTS date and converted as such into the corresponding migration structure.
  • Migrate Distribution Plan
The distribution plan stored for the policy is also migrated.
  • Apply Defaults
The system reads and applies the defaults stored in In-Force Business Configurator (Check&Derive logic for the time of initialization of the business object).
  • Execute Validation
If you set this indicator, the system starts validation immediately after updating the raw data in the database. In live migration, you should execute posting of raw data and the validation/release separately for performance reasons.
If you do not set this indicator, the data is written unchecked to the database (raw data) and must then be validated and released in a second step.
To execute validation and release, use transaction /PM0/ABQ_FP_Q_POLVAL.
  • Release
If you select this indicator, the system releases a successfully validated policy for immediate processing.
If you do not select this indicator, you must release successfully validated policies separately in a subsequent validation run.
This indicator is relevant only if you have also selected the Execute Validation indicator.
  • Delete Temporary Data
For policy migration, temporary policy versions are stored in the database tables of FS-PM/FS-PM Auto. After successful validation, the system must delete this data from the database, otherwise it is not possible to process the migrated policies.
This indicator is relevant only if you have also selected the Execute Validation indicator.
If the program is not to delete the data directly, a separate run of the /PM0/ABQ_DEL_TEMPDATA(transaction /PM0/ABQ_DEL_TMPDATA) report is required to delete the temporary data.
  • Display Empty Fields
If this checkbox is set, the system displays the empty migration structure fields (with initial value) in the output list.
For example, if you select this indicator, you can see which fields are available in the migration structures.
  • Display Descriptions
If you select this checkbox, the system displays the corresponding ABAP Dictionary descriptions for the migration structure fields.
If you do not select this indicator, the system displays only the migration fields and their contents without any additional description.

Standard Variants

Output

The system displays the policies created together with the individual migration structure fields and their contents.

In a log file, the system list any errors that occurred (under Execute Migration). The system displays successfully processed policies directly in the output list.

Activities

If you select the Execute Migration indicator, if you choose a generated policy number in the output list, you can access the policy as follows:

  • If the Execute Validation indicator is set, you go to the Change process.
  • If the Execute Validation indicator is not set, you go to the Inquiry process.

In policy validation, you use control parameters in the /PM0/ABQ_VALIDATION_CNTRL structure to define whether specific steps are to be executed and, if so, how they are to be executed.

In test environments, you use the following three parameters to define how test migration is to be executed:

  • /MVA/AMQ_VALCNTRL1TO: Defines the date up to which versions are to be validated according to the settings for /MVA/AMQ_VALCNTRL1.
  • /MVA/AMQ_VALCNTRL1: Defines the validation steps that are to be executed for versions that are before /MVA/AMQ_VALCNTRL1TO (inclusive). If you enter a "X" in position n, this defines that step n is to be executed. If you enter a "-" in position n, this defines that step n is not to be executed.
  • /MVA/AMQ_VALCNTRL2: Defines the validation steps that are to be executed for versions that are after /MVA/AMQ_VALCNTRL1TO (exclusive). If you enter a "X" in position n, this defines that step n is to be executed. If you enter a "-" in position n, this defines that step n is not to be executed.

The system evaluates parameters /MVA/AMQ_VALCNTRL1 and /MVA/AMQ_VALCNTRL2 only if parameter /MVA/AMQ_VALCNTRL1TO contains a date.

For more information about the parameter, see the documentation of the BAdI /PM0/ABQ_POL_VAL_CNTRL_BADI.






ABAP Short Reference   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 12473 Date: 20191206 Time: 065018     sap01-206 ( 53 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.