- SAP Community
- Groups
- Interest Groups
- Application Development
- Discussions
- Can we switch SU25 step2C and step2D?
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Can we switch SU25 step2C and step2D?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-23-2011 12:24 PM
Hello Gurus,
Once we over with step2C (including role modification) then step2D is coming in play. And now again changing the transaction require further role modification and a new set of approval as well. Can we switch these 2 step.
1. 1st change check indicator 2B
2. Change role menu 2D
3. Change role authorization 2C
Regards,
Arpan Paik
- SAP Managed Tags:
- Security
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-23-2011 8:56 PM
What is your source and target release / SP?
If you take a carefull look at what 2D suggests, then 9 times out of 10 you do not want it and it is only as good as the developer having maintained the table behind it.
I have to date not encountered a reason to use 2D within SU25 itself. Rather save yourself the hassle and wait for the funkies to request a replacement tcode (very often they will not be listed in 2D anyway).
Cheers,
Julius
ps: Concentrate on 2B and avoid the "Copy SAP file" button. Make a good job there and then well designed roles in 2C are a breeze!
- SAP Managed Tags:
- Security
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-23-2011 6:29 PM
Hi,
As per my understanding, it should be ok to perform step 2D before 2C since the latter merely introduces new check indicator values from the existing role menu transaction codes into roles (maintained via Step 2B) whereas the former is used to create a list of all roles containing transaction (in role menu) which have been replaced one or more new transactions in the newer version of SAP. You can then choose to replace the transaction in the role as needed.
Hope this helps!
Thanks,
Sandipan
- SAP Managed Tags:
- Security
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-23-2011 8:56 PM
What is your source and target release / SP?
If you take a carefull look at what 2D suggests, then 9 times out of 10 you do not want it and it is only as good as the developer having maintained the table behind it.
I have to date not encountered a reason to use 2D within SU25 itself. Rather save yourself the hassle and wait for the funkies to request a replacement tcode (very often they will not be listed in 2D anyway).
Cheers,
Julius
ps: Concentrate on 2B and avoid the "Copy SAP file" button. Make a good job there and then well designed roles in 2C are a breeze!
- SAP Managed Tags:
- Security
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-24-2011 8:48 AM
It's a upgrade from 4.6C to ECC6.
Concentrate on 2B and avoid the "Copy SAP file" button. Make a good job there and then well designed roles in 2C are a breeze! ;-).
Till today I found this very hard to convince business dicision maker. It's like do not do much work in SU24 to save the trouble in 2C. That's so naive. And instant fix which brings a greater trouble to support.
Anyway your suggestion for not to use 2D at all seems logical (not cheating ). Let the funkies come.
Regards,
Arpan Paik
- SAP Managed Tags:
- Security
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-26-2011 7:27 PM
That is sadly so.
Having a good days work in 2B every 6 months saves days in 2C and weeks in PFCG and years in audit hassles...
Step 2B should be made bonus relevant for KPIs, then they will try it and become believers ...
Cheers,
Julius
- SAP Managed Tags:
- Security
