Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

No Authorization for Equipment Category

sank_n
Participant
0 Kudos

Hi Experts,

All users are empowered with SAP_ALL authorization in our clients Development client.

However when a user tried to change some equipment master data using TCode IE02 an error message appeared stating that ""No authorization for equipment category A". So we have check using SU53 but nothing was there. then equipment category was changed..Same error message appeared.

And we have used login details of another user with SAP_ALL authorization..but result remains the same

Then our basis admin has created a new role with IE02 and assigned to the user. but result was the same error message.

Then He has removed the SAP_ALL authorization and left only the new role with IE02. User was able to change the Equipment data. However user unable to change the equipment master data with both SAP_ALL and new role.


Appreciate your valuable inputs.

Thanks in Advance

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Some transactions are "booby trapped".

Common causes are the user type is SERVICE (not subject to license measurement, so professional user tcode functionality will not all work..) and FOR USER extentions in the authority check statement (this can happen if you do client copies to dev or if you do not use real new test data with a test user in a qas system - increasingly so since the function module AUTHORITY_CHECK gains popularity to check auths before processing.

It can be confusing, but is actually quite useful... 🙂

Cheers,

Julius

2 REPLIES 2

Former Member
0 Kudos

Some transactions are "booby trapped".

Common causes are the user type is SERVICE (not subject to license measurement, so professional user tcode functionality will not all work..) and FOR USER extentions in the authority check statement (this can happen if you do client copies to dev or if you do not use real new test data with a test user in a qas system - increasingly so since the function module AUTHORITY_CHECK gains popularity to check auths before processing.

It can be confusing, but is actually quite useful... 🙂

Cheers,

Julius

0 Kudos

Thanks for the reply.

Yes..we have found that the cause for the error was the customized authorization object.

and its sorted.