11-09-2010 5:14 PM
I have a request to add transaction LSMW on a Production role. They said, it will help them maintain records in masses.
Are there any issues/pitfalls assigning this transaction in Production system?
Thanks.
John
11-09-2010 10:15 PM
Hi,
one way how to restrict LSMW in production is to use report /SAPDMC/SAP_LSMW_INTERFACE. This report can be used to run LSMW project in background. So you can create a custom transaction with variant for each LSMW object and give access users only to this transaction. They won't be able to create new projects.
Cheers
11-09-2010 6:20 PM
As a better option (IMO) you can alternately use transaction MASS to execute such tasks based on BOR objects.
Worth looking into.
Cheers,
Julius
11-09-2010 7:25 PM
This is a question that often comes up in discussion when a user wants access to LSMW. Often the "pitfall" that comes up for discussion is "Since mass maintence /update is possible will it be catastropic" the checks and balances that are placed also are to answer this question.
Juluis -> the MASS trasaction looks wonderful ! This is teh first time I tried it..looks very versatile! Du bist "UBER GURU !
11-09-2010 7:52 PM
Hi George
From memory (addled and poor) MASS uses an auth object with many many values - if you do assign it then restrict carefully.
My previous manager (Hi Derek) pointed that out when somebody in the business asked for it - his comment was something like 'You do have a habit of requesting dangerous transactions"
Cheers
David
11-09-2010 10:15 PM
Hi,
one way how to restrict LSMW in production is to use report /SAPDMC/SAP_LSMW_INTERFACE. This report can be used to run LSMW project in background. So you can create a custom transaction with variant for each LSMW object and give access users only to this transaction. They won't be able to create new projects.
Cheers
11-09-2010 10:39 PM
> /SAPDMC/
I dont see that as a standard "Netweaver" component, so I assume that it only restricts it's own use and not any APIs.
Does LSMW respect APIs?
Cheers,
Julius
11-09-2010 10:43 PM
No, It's a standard program mentioned in [LSMW documentation|http://help.sap.com/saphelp_nw04s/helpdata/en/90/da31ba2e0411d2b43e006094b944c8/frameset.htm].
Cheers
11-17-2010 10:40 AM
Hi Martin
one way how to restrict LSMW in production is to use report /SAPDMC/SAP_LSMW_INTERFACE. This report can be used to run LSMW project in background. So you can create a custom transaction with variant for each LSMW object and give access users only to this transaction. They won't be able to create new projects.
We've just tried this in Dev - seems to work a treat by adding the report into the menu of a test role and it brings in transaction Y_DEV_66000033 (Frame program for periodic data tran) in S_TCODE which runs START_REPORT.
Thanks for the information!
Cheers
David
11-10-2010 10:39 AM
11-15-2010 4:08 PM
Thanks to all that replied to my question. The answers, suggestions and links were all very helpful. We have decided not to give access to LSMW in Production. The data that are created or changed in DEV in LSMW are all transportable.
Thanks again!