The system will prompt you to enter descriptions for each type. To create a new LSMW, type in a unique name for the project, subproject, and object(s) and hit Shift + F1 or click the “create” button. Beneath the subproject level is the object, a unique name given to data which corresponds to business objects. For example, an SAP SD project can have subprojects like O2C, Billing, AR, etc. While the project is the high-level category, you can create subprojects beneath it. You can use an existing project or create a new one. To configure LSMW, go to transaction code LSMW. As long as the data that needs to be converted can be downloaded in a file format accepted by LSMW, you should be good to go. LSMW is primarily used for mass data conversion, data modification (such as changing email addresses en masse, which will be the focus of this post), and data upload and can be used in data conversions from non-SAP to SAP systems as well as SAP to SAP systems. This is a strong tool for functional and technical consultants to have in their armor. This blog post will introduce the Legacy System Migration Workbench (LSMW). For SAP projects that do not have a dedicated data team involved, it is the responsibility of consultants to handle the data load and data modification.
0 Comments
Leave a Reply. |