Problem solve Get help with specific problems with your technologies, process and projects.

Avoiding the yellow lights when adding transactions via PFCG

Are you tired of those same authorization objects showing up as yellow lights every time you enter a new transaction code?

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.
This was last published in June 2003

Dig Deeper on SAP development and programming languages

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.

-ADS BY GOOGLE

SearchERP

SearchOracle

SearchDataManagement

SearchAWS

SearchBusinessAnalytics

SearchContentManagement

SearchHRSoftware

Close