Question:
Hi
I apologize if this entry is so long but it is necessary to explain the problem effectively.
Our Basis team are currently implementing extension set 2.00
The upgrade has so far been carried out on 2 separate QA clients as a test. These are clients which normally receive transports from Dev for role changes.
The behaviour in SU25 is as expected in these 2 clients:
The first upgrade was carried. In step 2B all transactions which have authorizations affected by the upgrade correctly showed in pink as Status PENDING REVIEW
345 transactions were affected. Double clicking into them enabled us to review and retain our old values or accept the new sap defaults
All transactions were maintained as an exercise and are now Status green – MAINTAINED
Step 2C correctly highlights the roles for review. No roles appear to have any issues.
The second upgrade was carried to the next client. In step 2B all transactions which have authorizations affected by the upgrade correctly show in pink as Status PENDING REVIEW
345 transactions again are affected and they are the same identical transactions as the first client upgraded. We have maintained only a few samples, but the procedure seems to work fine
The upgrade has now been carried out to our development client 205 and in step 2B things are not correct.
The Status of all transactions is immediately green and all are showing as CHECKED
Only 126 transactions are listed, not 345
If we take an example transaction which is green and CHECKED, and display the authorization values in SU25 e.g. transaction F110, we can see that despite the Status CHECKED, there are in fact authorisation value differences which should be reviewed.
Additionally, when we look at the change history, the changes last made were 16/1/2001. If we look at the same transaction in step 2B in the QA client, it is correctly in status pink PENDING REVIEW, it has the same new authorisation value changes proposed and it has the same last change history.
We do not understand:
1) why in development there are only 126 transactions listed not 345
2) why the status is immediately green and CHECKED and not PENDING REVIEW when they clearly should be PENDING REVIEW
We would expect development to be identical to the 2 qa clients.
I have searched OSS and sapfans but cannot yet find anything relevant.
Does anybody have any ideas please?
Thanks all
Answer:
Hi,
The similar situation I am facing while security upgrade trial from 4.6C to ECC 5.0 but mine is a bit different issue.
While I ran SU25 Step 2A and 2B, I got a list of tcodes which needs to be adjusted the SU24 settings in new version. Initially the status is Pending Review. Then I check all these tcodes in 4.6C and made same in ECC 5.0 and manually checked. My requirement is all these SU24 settings in new version must be same as in old version.
After this when I go to couple of roles to modify it in expert mode with option 3 Read old status and merge new data, I am getting new and old status authorizations. Here the question is: For some, the old status objects are not reflecting the old values but it is showing new SU24 default values. This is a problem because if I am not sure the old status is not reflecting in all the cases, then I need to check all authorizations irrespective of old and new statuses, which is nothing but rebuilding the roles almost.
My question is Is the old and new version SAP delivered default values for sU24 settings are same?