CALCULE SU NIVEL DE ENDEUDAMIENTO

For each data load started with the IS Migration Workbench, a migration statistic is created.

The statistics contain the essential information about the import run and allow you to monitor the progress of a data load by displaying information, such as, number of migrated data objects, number of errors, and throughput per hour. Access to the statistics is available from the main screen of the IS Migration Workbench and from various other transactions. You can select the migration statistics to be analyzed with a selection-screen based on many criteria (see Figure 2-23).

Figure 2-23: Selection-Screen Migration Statistics

Figure 2-24 shows a list of statistics records during a migration test cycle (migration company is made anonymous with a bar for privacy reasons). The list shows a typical sequence of import runs with various errors.

Figure 2-24: Migration Statistics

The displayed symbols in the migration statistics have the following meaning:

Symbol Meaning Import finished Import active

Import started in restart mode Job was cancelled in background

Import cancelled due to a wrong order of data records Distributed import stopped by user

Distributed import finished with cancelled slave jobs Attributes of import

Figure 2-25: Meaning of the Symbols Displayed in the Migration Statistics

You can analyze a migration statistic individually by pushing the button. Figure 2-26 shows an error log of an import run with the migration object for a device installation (INST_MGMT migration object). Each error message is completed by the error message EM 100 Error during processing of legacy system key <oldkey>, showing the oldkey of the data

object for which the error occurred. Click the button to display the longtext of the selected error message.

Figure 2-26: Error Log of an Import Run

For the selected error logs, you can create a message statistic to show the error messages and the frequency of their occurrences. To analyze each of the error messages further, create new statistics based on the variable parts of the error message (message variables).

To create statistics for more than one import run, select the import runs that you want to create statistics for and push the button. This allows an efficient error analysis for many import runs of the same migration object with many import files. Figure 2-27 shows the statistics of the error log shown in Figure 2-26.

Figure 2-27: Statistics of an Error Log

There is no error log available for an analysis of a canceled import run. If neither the job log nor the short dump (transaction ST22) indicates what might have caused the cancellation, you can transfer all the error messages of the error log to the job log. The Message in Job Log user parameter on the Monitoring sub screen should be marked for

this purpose only due to the negative impact on the performance. To display the job log, select the display variant Run Log instead of Error Messages. Alternatively, push the Job Log button on the Job Data sub screen.

The load program writes only the last error message of the application to the error log even the application raised more than one error message while processing the transferred data.

Sometimes it is difficult to infer the root of the problem from a single error message. To force the load program to write all created error messages to the error log instead of only the last one, create an event as shown in Figure 2-28. The application writes now all error messages to the error log. For more information about how to create an event, see chapter 4.3.3 Code on Report Level.

The load program cannot differentiate between application internal messages and messages that are relevant for a resolution of the problem. This is why the load program writes only the last error message to the error log. After implementing the event;

many error messages can be written to the error log and need to be analysed carefully for their relevance.

Figure 2-28: Event to write all Error Messages to the Error Log

After a data migration of installation facts for an installation with INSTLN migration object you find in the error log the message AH 348 The facts are not consistent. You cannot infer the erroneous fact (or operand) from this general error message. An in-depth analysis shows that the application raised the error AH 423 Error in operand X (fact group Y, season Z) which would have allowed to identify the erroneous data in the import file.

Because this error message was the 2^nd last raised by the application it was not written to the error log.

Not all error messages in the error log help to find the error in the transferred data or Customizing. After the implementation of the event as shown above the following error messages can be found in the error log: E7 002 No contract found for Installation X, E9 014 Error in reading table ETTIFN for installation X, AH 423 Error in operand X (fact group Y, season Z), AH 348 The facts are not consistent and finally the obligatory message EM 100 Error during processing of legacy system key X. The first two error messages can be ignored because they are application internal error messages while the 3^rd error message helps to identify the erroneous data causing the problem.