LSMW in Production

[Former Member]

Who should have access to LSMW in prod? Should developers and business analysts have it? What are the risks involved if access is allowed outside of the business analysts and developers?

Your responses are highly appreciated.

[Former Member]

LSWM can be given in PROD, But just as ABAP it should be created in DEV and then transported. Also you should have a naming convention so FI LSWW can only be run by selected FI people etc. Also be aware that users should not be allowed to run LSMW under other userid's than theri own unless secured well!!

Main issue here is that people who use LSMW in prodcution should be trusted and know very well what they do!!

[Former Member]

LSMW should only be given in production on an as needed basis only!! It is very critical that you at least control the name of the project that the person responsible can execute in production.

I would also let the data owner know ( and get approvals amongst others) if there is going to be any mass updates to data in production. As always have a process that calls out the procedures for executing LSMW in production. You never know when you can get hit with the quarter end audit gremlin...

[Former Member]

Hi,

It is right that LSMW should not be given in production

It should be given when situation needs it ans is critical.

Also you should have proper measures of control to give this access.

e.g you can give LSMW role it with validity and with appropriate approvals from management.

Also from auditors point of view itis not good.audiotrs may object on this.

[Former Member]

As an alternative to LSMW (Legacy System Migration Workbench) for doing (periodic) mass updates or processing, you might also want to look into transaction MASS and MASSOBJ.

[Former Member]

LSMW is (or will normally be) related to data migration, and will therefore necessarily have to be executed in a production system before a go-live. But this is, of course, under very strictly controlled circumstances and during tightly defined windows.

LSMW as a general ad-hoc solution for maintaining data is, at best, a dubious practise. In other words, LSMW will be granted to a very limited set of people during very specific migration phases of a project, ideally via assignment of very specific roles, and, of course, with all necessary auditing checks and controls in place.

If administered properly, you will consequently have all the necessary documents and logs signed off and ready to show your auditors when/if needed.

Regards,

Trond