topic Re: MM02 Authorisations issue in Application Development and Automation Discussions

MM02 Authorisations issue

Former Member — Mon, 22 Oct 2007 14:18:35 GMT

Hi guys,

Hoping you can assist me with an authorisations issue I am facing.

End-users are using a Z bespoke material upload program. In order to run the program they need full authorisations to all views in MM02 as the upload program uses this transaction in a BDC Call. However they currently have restrictions on certain views in MM02.

I need to find a way that allows them to run the program but prevents them from getting full access to all the views in MM02.

Any help would be greatly appreciated.

Thanks,

Philip Johannesen

Re: MM02 Authorisations issue

Former Member — Mon, 22 Oct 2007 14:28:10 GMT

Hi Philip,

Why can't you use your Z program in background. So that the EU will set a background job and will set user as BATCHUSER or any background user which has full authorization.

Regards,

Atish

Re: MM02 Authorisations issue

Former Member — Wed, 24 Oct 2007 12:16:44 GMT

Hi Atish,

Thanks for your response. The issue with sending it to a batch user is there are authorisations around the EU's SAP ID. These prevent the user from copying materials to certain plants. So I have to take these into account when they run the program.

Many Thanks,

Philip Johannesen

Re: MM02 Authorisations issue

former_member195698 — Wed, 24 Oct 2007 12:43:11 GMT

A wild solution ..

Create a Wrapper program with same interface as the current

program. It will do the authorization check , which you have mentioned.

To prevent the user from copying material to certain plants.

Call the Program that create the views in the material using SUBMIT VIA JOB and pass the BATCHUSER

in the submit statement.

Regards,

Abhishek Jolly

Re: MM02 Authorisations issue

Former Member — Wed, 24 Oct 2007 14:15:41 GMT

Hi Abhishek,

Thanks for your response. Yes that idea had passed through my mind. I was hoping there was a neater way to do it but I think it may be the only option left.

Many Thanks,

Philip Johannesen