Big4Guy

Welcome 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.

Post details: How to Implement BW Infoobject Level Security

05/17/08

Permalink 02:21:11 am, Categories: SAP R/3, SAP BW, 282 words   English (US)

How to Implement BW Infoobject Level Security

Most organisations implement BW security at the infocube level. SAP provides an option to set up security at the infoobject level. Securing at the infoobject level is much more secure. With BW infoobject level security, a user working in a particular division will have access to only to reports for that division. Lets take a look at the steps needed to setup infoobject level security in SAP business warehouse:

1) Infobject Authorization Relevant - The first step is to enable the 'authorization relevant' setting for an InfoObject in the definition in the business explorer tab.

2) Customized Authorization object for reporting - The second step is to create a new authorization object through transaction code RSSM. Since SAP BW does not come with a standard authorization object for reporting.

3) Assign Authorization Object to Role - The new reporting authorization object created in step 2 should then be allocated to a sap role so that bw users can be assigned that role.

4) Query Variables - Variables are important in query beacuse they distinguish the data that can be accessed by the query itself. Then, to secure reporting only to a division, the query must be able to restrict data by division. This is made easy by defining a variable in the system.

5) Authorization object mapping to InfoProvider - The final step in creating security at the infoobject level is to map the new authorization object created to the inforprovider. Any users attempting to query an infoprovider will only be able to do so based on the definition of the authorization object defined and assigned in their SAP roles.

Related Posts

Functional Area in SAP
Configuring Sourcelists in SAP MM
SAP PP - Bill of Material BOM
SAP SD - Basics of Sales Documents

Comments:

No Comments for this post yet...

Official Websites

Search

Google

Web Big4Guy.com

June 2008
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

Misc

Syndicate this blog XML

What is RSS?