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.
|
Reports in SAP can be accessed through transactions SE38 and SA38. This is the normal way of accessing reports within SAP. Reports can also be called up indirectly using the transaction codes SE80 and SE84. To make things easier, many users prefer converting reports to transactions for easy and simple access. How does one go about doing this. There are two ways of doing this. A report in SAP can be integrated in the area menu or in a role menu.
Once this is done, the report reflects in the user menu. The structure of such report is S_ALR_XXXXXXX. The problem in this case is that there is no link between the report and the transaction name as SAP names the transactions consecutively. The alternative method of converting SAP reports to transactions is storing reports with a transaction set by the user. The report can then be called up by the user using the T-Code. It is important to use correct authorization object like S_PROGRAM to protect such reports from unauthorized access. From a user authorization audit prespective, this is important. Since access is best controlled at the authorization object level.
Related Posts
SAP R/3 Auditor Authorizations
SAP BEx Analyzer Toolbar
SAP CATT Computer Aided Test Tool
SAP Basis Transaction Codes
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 | ||||||