Big4GuyWelcome to Big4Guy.com. Big4Guy is an online resource where I will share with you the latest news, insights, knowledge and some experiences as a Big 4 consultant. We will discuss some of the important issues which organisations are facing today in the areas of information security, security and controls in SAP R/3, Oracle Applications, J.D.Edwards, Peoplesoft and various other ERP's. You will also find information on latest complaince regulations like Sarbanes Oxley, Basel II and so on. Big4guy will also attempt to provide valuable resources for individuals interested in examinations the CISA, CISM, CISSP, PMP and various other security certifications considered essential for entry in any Big 4 accounting, auditing and consulting firms. You are invited to post your comments and viewpoints to posts here. I sincerely hope this online journal will be useful to everyone from a budding student to a professional in the accounting, auditing, management and consultancy professions.
|
In my post on the authorization concept in SAP R/3, I had defined an authorization object as any element in the SAP system access to which needs to be restricted. Authorization objects help in granting access privileges to users by using authorization fields. Authorization fields help in performing complex access privilges tests for users. Authorization fields help in restricting user access by performing additional access tests. Examples of authorization fields can be a company code, sales group, customer group, purchasing group etc.
Every authorization object normally has the authorization field "ACTIVITY". The "ACTIVITY" field defines the possible actions that can be perfomed on a particular authorization object. To take an example, the activity 03 indicates Display access. Thus, in case an authorization contains purchasing group and activity, and the purchasing group field is marked with a *, then the user has display access to all purchasing groups. Using transaction code SM30 and SE16, a user can display all standard activities in the SAP system by displaying table "TACT". One more important point to remember is that authorization fields are also part of the standard ABAP function Authority Check. Authorization fields can be maintained using the SAP development environment.
Related Posts
Manual Authorizations in SAP R/3
SAP R/3 Reporting Tools
User Exits in SAP FICO
SAP BW Key Figure Concept
No Comments for this post yet...
| Mon | Tue | Wed | Thu | Fri | Sat | Sun |
|---|---|---|---|---|---|---|
| << < | > >> | |||||
| 1 | ||||||
| 2 | 3 | 4 | 5 | 6 | 7 | 8 |
| 9 | 10 | 11 | 12 | 13 | 14 | 15 |
| 16 | 17 | 18 | 19 | 20 | 21 | 22 |
| 23 | 24 | 25 | 26 | 27 | 28 | 29 |
| 30 | ||||||