Add Auth. Object into Value list - SU24

[Former Member]

Dear,

I have created new authorization object to be checked under Tcode Me23n.

The object has been inserted into the role with certain values but it does work.

I checked su24 and added this object to the Tcode but still not working.

Any idea? Or is there a way to add my object to the field values?

Regards?

Hesham

[Former Member]

Dear,

I have created new authorization object to be checked under Tcode Me23n.

The object has been inserted into the role with certain values but it does work.

I checked su24 and added this object to the Tcode but still not working.

Any idea? Or is there a way to add my object to the field values?

Regards?

Hesham

[jurjen_heeck]

> I have created new authorization object to be checked under Tcode Me23n.

> The object has been inserted into the role with certain values but it does work.

Did you have an abaper code the actual AUTHORITY-CHECK statement for your new object into the program code behind this transaction?

[Former Member]

It is quite disturbing how often people are led into believing this...

I think the expectation comes from web apps, where everything is configurable.

[Former Member]

No, it is a SAP tcode, it is basically simple idea comes from MM consultant that I can make use of some fields like u201Ctruck nou201D and then modified it as authorization field then create authorization objects that contains this field.

I created role for tcode ME23n and by default I got Org and Purchasing Group as objects and they work fine. I then manually entered my own object but the check is not going through

If this doable what am I missing here? Can you explain further if ABAP job is required?

Thanks

[Former Member]

You need to ask yourself whether you want this custom object checked at the beginning of the transaction, or at the end of it, or everywhere all the time, and also for other transactions or not which use the same program.

That is in the coding of course. So if your object is not checked in the coding, then it is not going anywhere...

Hope that clarifies your doubts.

Cheers,

Julius

[Former Member]

Hi Hesham.

Generally a check against a users authorisation will take place when there is the ABAP statement AUTHORITY-CHECK in the code, along with the subsequent logic. Without this, you add what you like in SU24 but it won't make a difference.

If you want additional checks which are not coded in the program for your transaction then you need to modify the code. SAP provides user exits and enhancement points for this purpose - they let you put in your own validations in specific parts of programs without having to change standard code. If you want to include some additional checks then you need to speak to your functional consultant and development team to make the appropriate changes. Once these changes have been made and tested, you can update SU24.

As delivered by SAP SAP will often have some authorisation checks switched off for standard objects. You can see them in SU24 by status Do Not Check. You can often activate these checks by changing them to Check or Check Maintained (or proposal in recent versions)