Allow Users to Execute LSMW Objects Without Access to Transaction LSMW

  • by Manuel Gallardo, SAP HR System Architect
  • August 25, 2009
Learn a 3-step technique for restricting user access to LSMW to just one assigned data load. Users then can execute a data load without posing a security risk.
Key Concept

Transaction LSMW is the main transaction for accessing the Legacy System Migration Workbench (LSMW), whichis a tool used to load data into an SAP system. The LSMW transaction is used not only for loading LSMW Objects, but also for creating and maintaining them.

The Legacy System Migration Workbench (commonly known as LSMW) is a tool used to load data into an SAP system. Developers, as well as users, can access LSMW to execute a data load via transaction code LSMW. The problem with using the same transaction for customization and execution of the LSMW Objects is that some system administrators worry that users may be able to perform actions outside of their authorization level.

This means that IT teams have to find a way to allow users to execute LSMW scripts without providing them with access to transaction LSMW. A method for solving this problem is to assign the executable LSMW Object to a new transaction code that would only allow users to execute a particular data load. This method precludes the user from executing any LSMW Objects other than the one assigned to the transaction.

Manuel Gallardo

Manuel Gallardo is the director of HCM consulting at /N SPRO. He is a former SAP platinum consultant and his area of expertise is SAP HCM enterprise architecture, SuccessFactors, and enterprise mobility. Since working on his first SAP implementation in 1994, he has also worked on a wide variety of SAP HR modules, as well as SAP NetWeaver Portal and ABAP development. Manuel is the author of Configuring and Using CATS, and is a frequent conference speaker.

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.