Hi Sunny
there are still 3 std tcodes which were changed in previous release with no SAP defaults change in new release; and they did not show up in Step 2B.
They will only appear in Step 2B if both you and SAP made changes to the transaction since the last time you ran SU25
. I shall execute Su25 -> Step 3 (after i finish 2a to 2d); this step will carry complete (and not the only changes made in 2A, 2B) table data USOBX_C + USOBT_C and move to further tiers.
Step 3 is to bundle a transport of SU24. It will transport entire tables. You can complete this after Step 2B if you wish to as 2A and 2B update SU24. However, you may prefer to finish all of Step 2 incase you manually go to SU24 to make additional changes as you are fixing your roles (i.e. you may find an issue with your own build and choose to rectify it)
Step 3 transports: USOBT_C; USOBX_C; PRGN_STAT; USOBT_TSTMP; and USOBX_TSTMP. The *TSTMP tables in latest release replace the TCODE_MOD and USOB_MOD tables and are used to determine what was updated.
This will help to remove the message from QA/PRD 'If you have already used the Profile Generator in a previous Release,you should use transaction SU25 (steps 2A to 2C) to transfer the new.....'
Yes - as that setting is driven by a value in table PRGN_CUST for STAT_GRP=001 and (STEP_NR= 001 or 002) to see if either entry has the value in field RELEASE as the same value as current system release. If the RELEASE value is less the message will appear. By transporting the table in Step 3 it clears this issues across all your systems.
So is there a need to move this TR as well or Step 3 is good enough?
My solution: first do with Step 3, if correct changes are available in next tier then do not move 2B TR.
Am not quite sure why custom transaction codes appeared in SU25 - someone else might be able to offer an opinion here. However, running Step 3 just helps you create a transport. It will not change the flag settings in the tables that determine output in any of Step 2. You can come in and run Step 3 whenever you want to retransport all of SU24 across your landscape (tiers)
c. Appreciate if you can share the test phase strategy for this upgrade i.e. regression test with functional team / business performing test for all business scenarios / test cases.
This one is something you will need to discuss with your project on what they believe adequate testing is. You need to look at what roles are impacted and what the change to the access was. At the end of the day how does your site test security?
Regards
Colleen