topic Re: How to create an authorization object using abap code ? in Application Development and Automation Discussions

How to create an authorization object using abap code ?

Former Member — Fri, 06 Feb 2009 19:10:11 GMT

Hi everyone,

I need to create a program that creates an authorization object just like SU21 but throught abap´code.

I´ve tried to do a batch input/call transaction for that but it didn't work.

So , I would like to know if someone knows any FM/BAPI or any solution for this thread.

Thanks,

Best regards,

Enio.

Re: How to create an authorization object using abap code ?

Former Member — Fri, 06 Feb 2009 19:21:52 GMT

Why are you wanting to create authorization objects in mass, or "on the fly"?

If you can explain your requirement, then I am sure there are better ways of achieving this...

Cheers,

Julius

Re: How to create an authorization object using abap code ?

Former Member — Fri, 06 Feb 2009 19:26:08 GMT

This message was moderated.

Re: How to create an authorization object using abap code ?

Former Member — Sat, 07 Feb 2009 02:14:30 GMT

Hi Julius, thanks for reply!

I'm a new "abapper" , just up to my first project.

My mission is to integrade the SAP system with another ERP System developed in Brazil.

One of my tasks is create roles and authorization objects using abap code.

The Authorization Objects I need , don't require any authorization fields , I just need to create a class where I will create the authorization Object, and the authtorization object only with the name and description.

The problem is make it through abap code. I've tried using BDC but it didn't work on the transaction SU21.

Cheers!

Re: How to create an authorization object using abap code ?

Former Member — Sat, 07 Feb 2009 03:52:58 GMT

Hi,

Try out this link may be helpful

Regards,

jaya

Re: How to create an authorization object using abap code ?

Former Member — Sat, 07 Feb 2009 07:55:32 GMT

Hi Enio,

Would you like me to delete the link-farm posted by Jaya as well?

To the question: An authorization object should have at least 1 field (max 9) and at least 1 of them should be typed to a data element or domain range. I think there is even some check on this in the transport system.

Even although this is a non-SAP ERP you are integrating, it is still not a non-ERP system... so you should ideally be able to reuse the standard authorization objects if they serve the same requirement and do not interfer with any other requirement which the object is already used for.

If you want to keep it very simply, then take a look at the DUMMY keyword which you could check for in some fields without disturbing existing authorizations, but take note that your non-SAP ERP might then be able to post to any plant, or any company code, etc.

Cheers,

Julius