Upgrade issues with SU25 - information for everybody who plans an upgrade

[Bernhard_SAP]

Hi guys,

this is just an information regarding 2 issues with SU25, which have been corrected recently.....

First issue:

[SAP Note 1367325|https://service.sap.com/sap/support/notes/1367325]

-->SU25/2A is not executed automatically by DDIC anymore during the upg-XPRAs, Org.-level values are not overwritten anymore

Second issue:

[SAP Note 1360441|https://service.sap.com/sap/support/notes/1360441]

-->corrects a follow up problem (standard field values are considered as org.level.values although they aren't)

If you are facing this issue already, there is a correction report attached to that note.

Please consider the last paragraph of the notes text to avoid further inconsistencies (nevertheless developers here should know, which products are installed at their system and which org.-level definitions do not fit to their products. But opening a message at SAP support is highly recommendable if the admin is not sure....)

Good luck during your upg-project.

b.rgds, Bernhard

Edited by: Bernhard Hochreiter on Mar 15, 2010 9:49 AM

[Bernhard_SAP]

and one more....

[SAP Note 1375070|https://service.sap.com/sap/support/notes/1375070] ->you should check this before starting to update your existing roles...

[Former Member]

Hi Bernhard,

> [SAP Note 1375070|https://service.sap.com/sap/support/notes/1375070] wrote:

>> Remark: Transferring the SU22 data (which was loaded from the file) within your landscape is not required from a functional point of view. If you still require this, also select the option "Enter Data In Transport" during the upload.

I don't agree with this. There are some "No check" indicators in the file... which MUST be in sync through-out the landscape if they are to be expected to work as designed

Correction: The note is correct and also mentions:

> 3. When you have done this, start transaction SU25 and execute steps 2a and 2b with regard to adjusting the authorization default values.

> 4. Use step 3 of transaction SU25 to transport the adjusted customer-specific authorization default values to the receiving systems of your system landscape.

So... the settings will go through as SU24 data, if you have set this up correctly. The SU22 data is no longer needed to be transported.

Cheers,

Julius

Edited by: Julius Bussche on Mar 15, 2010 10:19 AM

[Michael_Chohrac]

Regarding SAP Note 1375070 - if we have already completed our enhancement pack upgrade (about a month ago), should we still follow the manual procedures outlined in the note - or is it too late?

Thanks.

[Bernhard_SAP]

Hi Michael,

that depends, if you are affected by this bproblem. You could compare the content of table usobt with usobt_c. If there is a big difference of number of entries, you should upload the missing ones as mentioned in the note. But if you were affected by this problem, you would have noticed that already in su25->2C......

b.rgds, Bernhard

[Michael_Chohrac]

Thanks Bernhard. There were several roles listed in step 2C but I made the corrections manually in each role and transported the changes through the system landscape already. So I would assume I would not need to do anything else at this point, correct?

[Bernhard_SAP]

yes. i hope you transported the su25-settings (SU25->pnt 3) as well to have it consistent in your landscape.

[Michael_Chohrac]

No, I didn't do that (I assumed the manual transports would do the same thing), but I will now. Thanks for your help - I wasn't very familiar with SU25 before this upgrade so wasn't sure what to do.

[Former Member]

Hi,

So to tag on to this thread, since I'm also unfamiliar with SU25 and want to be sure I understand it correctly, you need to execute all the steps in your DEV client where the changes to roles are made. Then transport any changes as well as transport SU25 settings in step 3. To remove the message popping up in the QA and PRD environments, you need to only run step 2a. Is this correct?

What about other DEV clients? Do any SU25 steps need to be run in them?

Regards,

Juliet

[Bernhard_SAP]

Hi Julia,

has been discussed already in this forum. No use to reexecute 2A in other systems/clients, as the transport contains all. Please read the popup text when pushing the button '3' in SU25. Don't forget to transport your updated roles as well.

b.rgds, Bernhard

[Former Member]

This message was moderated.

[Michael_Chohrac]

We recently upgraded to enahncement pack 4 for ECC6 and I ran the steps of SU25 in the Dev system only, thinking the resulting transports I created would be sufficient when the changes went to the QA and production systems. However, everytime I go into PFCG in either QA or PRD and attempt to open the authorizations, I get the pop-up saying I should run SU25 to transfer the new check indicators. So my question is, should I run SU25 in each system in the landscape? If so, will this overwrite anything that was done via transports I created when I ran SU25 in Dev system?

Thanks.

[Former Member]

You just need to run step 2a in SU25.

Regards,

Gowrinadh

[Michael_Chohrac]

Thanks Gowrinadh.

I ran step 2a in QA and PRD systems and the pop-up has gone away.

[Bernhard_SAP]

if you use SU25->3. to transport your changes, you won't need to run su25 2a in QA,PRD,...

The time stamp table for SU25 execution is contained in that transport!

b.rgds, Bernhard

And: before starting with SU25, pls always review SAP note 440231, containing the latest important corrections!