Kontakt

Ansicht
Dokumentation

/MVA/AMQ_MIGRATION_RS_TEST - FS-PM Auto: Test Migration of Registration Messages

/MVA/AMQ_MIGRATION_RS_TEST - FS-PM Auto: Test Migration of Registration Messages

Vendor Master (General Section)   BAL_S_LOG - Application Log: Log header data  
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 for registration management.

Prerequisites

Registration messages exist in FS-PM Auto.

An external number range has been created for the number range object /MVA/AMN05 (message ID for registration management) in transaction SNRO and has been entered in Customizing.

Features

This report reads the data of a registration message 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 /MVA/AMQ_RS_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 text file. For example, if the identifying field content for the administrative data for Austria is /MVA/AMQRSAADM, then this would be /MVA/AMQRSAHEADER for the header data for Austria.

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.

This report simulates data migration by creating one or more copies of an existing registration message.

Selection

  • Austria/Germany
Select the country-specific registration management.
  • Message ID/Sequence Number
Enter a message ID created in FS-PM Auto (preferably not a migrated registration message) that is used as a template or reference for the new (migrated) registration message to be created.
  • Migrate
The system reads the template message data and translates it into the corresponding tables for the data migration call.
Function module /MVA/AMQ_RS_MASSMIGR is called with the created data and the data is migrated.
  • Create Migration File
The system reads the data of the template message and downloads it as 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. The data is transferred from the input file to IDocs, which save the data in the system using function module /MVA/AMQ_RS_MASSMIGR.
  • Display Data
The system reads the data of the template message and converts it to migration data. The resulting data is displayed on the screen only. It is not processed.
  • Number of Messages to Be Created
1 to n new registration messages can be created from the template message.
  • Replace Data
If you select this checkbox, the system replaces the policy numbers, contract numbers, and insurable object numbers in the migrated registration message. Two additional fields are displayed for each criterion. To ensure that data is replaced correctly, you must enter values in both fields.
1) Policies to Be Replaced: If you want to replace one policy, enter the policy number of the policy being replaced in this field. If you want to replace more than one policy, enter the numbers separated by a ";". If you enter values in this field (multiple values separated by a ";"), you must enter the same number of values in the Replace Withfield.
2) Replace With: If you want to replace one policy, enter the policy number of the replaced policy in this field. If you want to replace more than one policy, enter the numbers separated by a ";". If you enter values in this field (multiple values separated by a ";"), you must enter the same number of values in the Policies to Be Replacedfield. The corresponding policy number replaces the policy number in the same position in the Policies to Be Replacedfield.
3) Contracts to Be Replaced: If you want to replace one contract, enter the contract number of the contract being replaced in this field. If you want to replace more than one contract, enter the contract numbers separated by a ";". If you enter values in this field (multiple values separated by a ";"), you must enter the same number of values in the Replace Withfield.
4) Replace With: If you want to replace one contract, enter the contract number of the replaced contract in this field. If you want to replace more than one contract, enter the contract numbers separated by a ";". If you enter values in this field (multiple values separated by a ";"), you must enter the same number of values in the Contracts to Be Replacedfield. The corresponding contract number replaces the contract number in the same position in the Contracts to Be Replaced field.
5) Insurable Objects to Be Replaced: If you want to replace one insurable object, enter the number of the insurable object being replaced in this field. If you want to replace more than one insurable object, enter the numbers separated by a ";". If you enter values in this field (multiple values separated by a ";"), you must enter the same number of values in the Replace Withfield.
6) Replace With: If you want to replace one insurable object, enter the number of the replaced insurable object in this field. If you want to replace more than one insurable object, enter the numbers separated by a ";". If you enter values in this field (multiple values separated by a ";"), you must enter the same number of values in the Insurable Objects to Be Replacedfield. The corresponding insurable object number replaces the insurable object number in the same position in the Insurable Objects to Be Replacedfield.
  • Display Empty Fields
If this checkbox is set, the system displays the empty migration structure fields (with initial value) in the output list.
You select this checkbox, for example, to see which migration structure fields are available.
  • Display Descriptions
If this checkbox is selected, the system displays the corresponding ABAP Dictionary descriptions for the migration structure fields.
If this checkbox is not selected, the system displays only the migration fields and their contents without any additional description.

Output

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

Any errors that occur are listed in a log file (Migrateradio button). Successfully updated registration messages are displayed in the output list.






BAL_S_LOG - Application Log: Log header data   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 8247 Date: 20240419 Time: 174440     sap01-206 ( 135 ms )