Troubleshooting
Use
Answers to the most frequently asked questions concerning data migration with the LSM Workbench.
Features
|
Problems |
Solutions |
|
Recording Fields cannot be seen in the field mapping after a recording has been created. |
Check to see whether the field names have been maintained correctly in the recording process.
|
|
Error message during/after import. |
See the object attributes to determine which import program was used, and search for documentation and notes on this import method directly. |
|
Only the data of the header structure is read after merging two files. |
All the fields with identical names are being merged. Check to see if merging of fields with identical names makes sense. For this, check the data read program generated by the LSMW by choosing . |
|
The source file contains data in one data record out of which to records are to be created after conversion. |
In step Maintain Field Mapping and Conversion Rules, choose the transfer_record function. |
|
Upon successful migration of long texts (message from direct input program), the texts cannot be displayed in the application. |
Use function module READ_TEXT to check if the texts are stored on the database. If so, check if there is an indicator in the application that shows you whether a long text exists. This indicator is not set during import of the long text, but either during conversion (by appropriate field assignments) or subsequently (by means of a user-specific ABAP program). |
|
Standard batch input/direct input: Fields are missing when creating the field mapping. |
All the fields listed in Table SXDA3 are considered to be technical fields. By default, technical fields cannot be seen. In step . The fields are displayed. |
|
Transaction LSMW cannot be started after installing the LSM Workbench. |
Transfer the authorization profiles described in the installation guide to the user master. |

