Application Development Blog Posts
Learn and share on deeper, cross technology development topics such as integration and connectivity, automation, cloud extensibility, developing at scale, and security.
cancel
Showing results for 
Search instead for 
Did you mean: 
Former Member

Inconsistencies with SU21 and SU24

While working on SAP Technical Upgrade From R/3 4.7 to the higher version as ECC 6.0, I encountered with an unique issue, however I am not sure if this has already been known to you So, I wanted to have it circultaed on SCN.

During execution of the SU25 steps: 2A, it compares the SAP values and so the tables will get updated with the new propsed values. But I found for some of the authorization objects the authorization fields from SU21 and SU24 are not in sync, which should be in sync.

Ex: For Authorization object: S_CTEMPLAT, under SU21 there were only 3 authorization fields as: ACTVT, BRANCH and OBJNAME but for the same authorization object, under SU24, in addition of these 3 fields, there were another 4 fields available. Detail can be viewed in the depicted diagrams.

SU21:

SU24:

So, when I raised OSS note seeking SAP involvement in order to rectify the issue, I was provided with a solution to implement OSS:# 1539556

So, as per the instructions, I was instructed to run a standard ABAP report: SU24_AUTO_REPAIR

This report helped me in getting all such missing authorization fields available in SU21 as available in SU24. There were around 10 other authorization objects where I had noticed the discrepancies which I was finally able to correct/overwrite after runnig the report mentioned above.

5 Comments
Labels in this area