public budget formulation: how-to-guide for analysis

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BA - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 1

Public Budget Formulation:

How-To-Guide for Analysis

Authorization in SAP BW

Applies to:

SAP Public Budget Formulation (All releases).

Summary

This how-to guide focuses on setting up restrictions to the users and limiting their access to Info Objects and their characteristic values for Public Budget Formulation. This guide can be particularly useful if you want to restrict the values users get in their F4/value helps.

Authors: Chintan Mota and Rajesh K S

Company: SAP

Created on: 17 November 2011

Author Bio

Chintan Mota is a Solution Developer, working with SAP America (Newtown Square) for over a year. Chintan has worked on various SAP BW & ABAP – implementation projects and currently working on SAP Public Budget Formulation project.

Rajesh K S is a BI Consultant, working with SAP Labs India PVT Ltd for over 15 months. Rajesh has worked on various SAP BW & ABAP – implementation projects and currently working on SAP Public Budget Formulation project.

Public Budget Formulation: How-To-Guide for Analysis Authorization in SAP BW


© 2011 SAP AG 2

Table of Contents

PBF Authorizations & Restrictions ...................................................................................................................... 3

EXAMPLE 1 – FUNDS CENTER (/PBFBI/FUND_CT) ....................................................................................... 3

Setting Up Combo Edit Rules ......................................................................................................................... 3

Characteristics/Dimensions with Hierarchies .................................................................................................. 5 Setting up Authorization in RSECADMIN ..................................................................................................................... 5

EXAMPLE 2 – STAGE (/PBFBI/STAGE) ........................................................................................................... 7

Stage Maintenance ......................................................................................................................................... 7

Setting up BI authorizations for Stage ............................................................................................................ 7

Other topics......................................................................................................................................................... 9

Assigning authorizations to users ................................................................................................................... 9

Setting InfoObject as Authorization Relevant ................................................................................................. 9

Related Content ................................................................................................................................................ 12

Copyright........................................................................................................................................................... 13



© 2011 SAP AG 3

PBF Authorizations & Restrictions

This how-to guide focuses on setting up restrictions user access to Info Objects and their characteristic values for Public Budget Formulation. This guide can be particularly useful if you want to restrict the values users get in their F4/value helps.

As an example, we will consider two PBF characteristics – Fund Center and Stage.

EXAMPLE 1 – FUNDS CENTER (/PBFBI/FUND_CT)

Let’s say that the requirement is to restrict the values displayed in the F4/value help of Fund Center field while creating a new Budget Form as shown in the screen capture below.

This can be done at two levels –

1. Combo edit rules

2. BI analytics authorizations

Consider Combo Edits feature as one that applies first level filtering. These restrictions on values can be even further fine tuned by using BI analytics authorizations.

Following section explains how to restrict values using combo edits feature.

Setting Up Combo Edit Rules

1. To setup combo edit rules first navigate to PBF Administration > Budget Forms > Combo Edit

2. Create a new rule as shown in the screen capture below (e.g. for Fund Center).

3. Select values for the mandatory fields.

Header Level: Hierarchies are organized as a nested list of values. Thus we have data values

at multiple levels. Use this option to select the base level.

Header Selector: The selector options can be used to specify the depth of nesting. For

example, if you select Header Level as 2, you may want all the values selected from level 2

up to the lowest level of nesting, or you may what to select only values included in level 2.

This restriction can be applied via Header selector.



© 2011 SAP AG 4

4. Next is to add a Form Mapping. This can be done by selection the Form Mapping tab as shown in

the screen capture below.

5. Click Add button to add the Form Name to which this combo edit rule should be applied to.

6. Refer the PBF documentation for further explanation on what each of the fields on this screen can

be used for.

Following sections explain how further restrictions can be applied to Funds Center by setting up BI Analytics authorizations.



© 2011 SAP AG 5

Characteristics/Dimensions with Hierarchies

Consider an example where FUND CENTER is to be restricted only to Public Safety and Community Dev and its hierarchy as indicated in screen captures below.

Setting up Authorization in RSECADMIN

First step is to create an authorization.

1. Go to transaction code RSECADMIN, Authorizations tab and click Ind. Maint.

2. Enter 0BI_ALL in Authorization field and hit Copy button.

3. When prompted for Copy to, enter the name of the new authorization that you would like to

create.

4. Enter a description or a short text for the newly created authorization.

Note: This new object has all the BI authorizations in the system. You might want to restrict these authorizations and discard characteristics/dimensions that are not related to PBF.



© 2011 SAP AG 6

5. Select Fund Center (/PBFBI/FUND_CT) and click the Details button.

6. Update Value Authorizations as per requirement and then move on to Hierarchy Authorizations

tab.

7. In Hierarchy Authorizations tab select Hierarchy, Nodes and Type of Authorization. Click OK when

done.

8. Save and return to previous screen. Click Save on main authorization screen and make sure you hit

activate button.



© 2011 SAP AG 7

EXAMPLE 2 – STAGE (/PBFBI/STAGE)

Following sections describe how stage values can be restricted. This can be done in two steps:

1. By assigning stages to a form (Stage Maintenance)

2. By setting up BI authorizations

Stage Maintenance

Refer to the following link that to learn how stages can be assigned to forms.

http://help.sap.com/saphelp_pbf71/helpdata/EN/c4/31203d87ff4dcbaf732c0d3217cfbd/frameset.htm

Setting up BI authorizations for Stage

Here we will explain how authorizations can be maintained for restricting users to specific stages.

Although stages 001 to 005 are assigned to the form in the Form Maintenance screen as shown in the screen capture above, we can further restrict the user to specific stages by using BI authorization.

Following are the steps that describe how this authorization can be set up in the back end.

http://help.sap.com/saphelp_pbf71/helpdata/EN/c4/31203d87ff4dcbaf732c0d3217cfbd/frameset.htm



© 2011 SAP AG 8

1. Select /PBFBI/SAUTH on the maintain authorization screen.

2. Enter the values of technical characteristics in Value Authorizations tab. In the screen capture

above the Stages for this authorization are restricted to values between 1 and 10 as an example.

3. Click Save and return to the Maintain Authorization screen. Activate the changes if not already

active.



© 2011 SAP AG 9

Other topics

Assigning authorizations to users

Authorizations, for example one that we created above, can be assigned to users via RSECADMIN itself.

1. Go to the User tab in RSECADMIN and select Indvl Assignment button.

2. Enter the user to which authorization has to be assigned on the next screen and hit change.

3. Select Manual or Generated tab, enter the newly created authorization and select insert. Save and

return.

Setting InfoObject as Authorization Relevant

It is important to note that authorizations can only be set for InfoObjects that are authorization relevant. Here is a brief guide on how to set InfoObjects as authorization relevant.

1. Go to transaction code RSD1 and enter the name of InfoObject. Click maintain.



© 2011 SAP AG 10

2. Navigate to the Business Explorer tab and set the AuthorizationRelevant check box as checked.

3. After you save and activate the respective object gets added to 0BI_ALL automatically. However, it

will not add itself to any other custom authorization you may have created. Follow these steps to

manually add it.

4. Go to transaction RSECADMIN. Select Authorizations tab and click Ind. Maint.

5. Enter the name of custom authorization where the InfoObject has to be added and click Maintain.



© 2011 SAP AG 11

6. Click the Create button as highlighted in screen capture above. Enter name of the InfoObject and

restrict values as per previous guide.

7. Click Save and Activate when done.



© 2011 SAP AG 12

Related Content

http://wiki.sdn.sap.com/wiki/display/BI/Analysis+Authorizations+in+BI+7.0

http://help.sap.com/saphelp_nw70ehp1/helpdata/en/80/1a6859e07211d2acb80000e829fbfe/frameset.htm

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/659fa0a2-0a01-0010-b39c-8f92b19fbfea?QuickLink=events&overridelayout=true

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/101fb4f5-eb7c-2c10-5daa-b479c47f0a14?QuickLink=index&overridelayout=true

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/9000928e-dd3d-2e10-9ca1-a00f249305b7?QuickLink=index&overridelayout=true

For more information, visit the Business Intelligence Homepage

http://wiki.sdn.sap.com/wiki/display/BI/Analysis+Authorizations+in+BI+7.0

http://help.sap.com/saphelp_nw70ehp1/helpdata/en/80/1a6859e07211d2acb80000e829fbfe/frameset.htm







http://www.sdn.sap.com/irj/sdn/edw



© 2011 SAP AG 13

Copyright

© Copyright 2012 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Oracle Corporation.

JavaScript is a registered trademark of Oracle Corporation, used under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

public budget formulation: how-to-guide for analysis

Documents