
SAP BASIS ADMINISTRATION TIPS
Avoiding the yellow lights when adding transactions via PFCG
Paul Gloede 06.27.2003
Rating: -3.39- (out of 5)




Are you tired of those same authorization objects showing up as yellow lights every time you enter a new transaction code? SAP has setup many default authorization objects for many different transactions. For example, within a Role, if you have an existing auth object(XYZ) with Activity 01, 02, 03 with Auth Group *, and you add a transaction to the Role, many times, by default, SAP will create the same auth. object XYZ with Activity 03 and Auth. Group blank. This will cause a yellow light to appear and the need to either delete it or change it to a green light before you save and generate. Now, instead of deleting the SAP delivered object, simply inactivate it (without deleting it). This will take care of the yellow light and the next time you add a transaction to this role, SAP will see that their default auth object (XYZ) already "exists" and not burden you with the dreaded yellow light. This has saved me lots of time.
 |

|
Rate this Tip
|
To rate tips, you must be a member of SearchSAP.com. Register now
to start rating these tips. Log in if you are already a member.
|

Submit a Tip
|


');
// -->
DISCLAIMER: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.
|
 |
|
|
 |
|
 |