Crude Oil dashboard

To get the oil price, please enable Javascript.

Reporting Authorization in SAP BI 7.0

A BI Developer wants to limit access to a specific Data Set to the User when the user execute report the one has to put limit on the Data Access by the user which is called Reporting Authorization.

For example: A BI developer wants the user to only see the data belonging to her Controlling Area then the you can achieve this by Reporting Authorization

Implementation Steps:

Go to RSECADMIN – Authorizatino Tabl – Maintenance – Give name Hit Create
Install following Business Content:

0TCAACTVT – Activity-Read, Create,Change, Display etc.
0TCAIPROV – From which InfoProvider you want to select the data
0TCAVALID – How long this Authorization is Valid to the Particular User
0TCAKYFNM – limit the Key Figures value here

Make sure the Above  InfoProvider and all InforProvide that require Authorization as Authorizaton Relevent (0PROFIT_CTR)

Once you click Create..Start Inserting Above InfoObjects in the Characteristics/Dimension Column.
Double Click on each InfoObject and Limit the DataSet
Now Save.

Now you want to Assign this Authorization to User or a Role

In the RSECADMIN go to USER Tab – Assignments – Select User – Change – Insert the Above Create Authorizatin Object – Save.

Go to the Role Maintenance – and You can add this Authorization to a Specific Role

Transaction for BPS Front End Applicatioin

Planning Folder – UPSPM

Web Interface Builder – BPS_WB

Status and Tracking Systems (STS) Application

STS can be used to automate the workflow and monitor the status for a planning applications created using BW-BPS or BI-IP.

Bottom-up Planning: In this type of  planning scenario; the individual at the bottom level of the planning hierarchy prepares the plan data and sends the request for approval to a person above in the hierarchy.  This hierarchy can be defined in customizing section of the STS application.  This continues until the last(top) person in the hierarchy approves the plan data.

Top-Down Planning: In this case, the individual at the top level of hierarchy prepares the plan data and sends it to the person down the hierarchy.  This continues until everyone, down to the bottom hierarchy, completes the planning process.

STS Application Component:

Planning Area:  Define InfoProvider that is to be used in STS Application ( RealTime Planning InfoCube)

Subplan: Represents a specific area of Planning E.g FInancial Planning, Sales Planning, Investment Planning, Head-Count Planning, etc

Planning Session:  This represent Versions of subplans.  E.g  A planning process for Sales planning may generate different versions of data (1, 2, and 3).  The  planning process associated with each Planning session can be specified for each of these variations.  The planning sessions might be titled Plan1, Plan2 or Plan3.  Each Planning Session may correspond to a version in the planning process.

Hierarchy:  Represents the relationship of individuals involved in the planning process.

Implementations Steps for configuration of STS Application:
1.  Create a Planning Area.
2.  Create a Subplan.
3.  Create a Planning Session.
4.  Identify a Hierarchy and Planning Area for the subplan.
5.  Associate a Planning Session with a subplan.
6.  Determine the Attributes for the Planning Session.
7.  Initialize/reset the Planning Session.
8.  Define Header Characteristic for the Planning Session.
9.  Determine the Data, Person Responsible,  and Layouts.
10. Test the STS Application.

1.  Create a Planning Area
T-Code BPS0 – Planning|Planning Area|Create – Enter Technical name & Description – Select Standard – Create – Now in the Attribute Tab – Select Your Planning InfoCube for Planning Area – Save Planning Area

2.  Create a Subplan
T-Code BPS_TC ( Status and Tracking System) –

SAP BI-IP Implementation steps

With the release of SAP BI 7.0; SAP is recommending it’s user to use Intergrated Planning for their company wide Budgeting and Planning Application.

Integrated Planning – is a J2EE-web based Planning tool used to create Enterprise Planning Application.  The concept of planning remains the same for BPS and IP but IP gives a lot of flexibility to the developer to intergrate individual planning to create a consolidated web-based planning application.

Steps to create Planning Application  using BI-IP

1.  Create Real-Time InfoCube/MultiProvider that will be used to store plan data.  Developer can use a single InfoCube to store Plan & Actual data using an InfoObject “Value Type for Reporting” which will help user differentiate Plan and Actual data.  The 2nd choice could be use a MultiProvider that is created based on Two InfoCube: Plan & Actual.
Note: if you use a single InfoCube cube, make sure to change the Real-Time Load Behaviour when using it for Plan or Loading data.

2.  Goto Planning Modeler and select the above created Real-Time InfoProvider for creating Plannning Application based on this InfoProvider.

3.  Create Aggregation Level:   You can think of Aggregation Level as an User Level Planning: for example CFO, Regional Manager, Supervisor, etc.  individual Aggregation Level will have to be created respective user depending on respective user requirement.

4.  Create Filter:  This is the same concept as of Filters used in BEx Query Designer.  It will limit the scope of planning to the specific range of dataset.

5.  Planning Function:   SAP gives pre-defined planning functions that can be executed automatically using Front-End of planning Application

6.  Planning Sequence:   Here you can add the above created Planning Function to be executed sequentially in proper order.  Also,  developer can create an Input Enabled Query to enter the plan data manually in order to test his planning Application.

BEx – Query Designer

Log into the BEx Query Designer –  Create a new query – select a InfoProvider – Drag Key Figure to Column & Drag Dimensions to Row.

Free Characteristic –  If you put the dimension; the report will show overall summarize result.  You will have capability to drill down

Default Values – If you want to put restriction on Data Set coming from the Dimension when displaying Query; you can define restrict here on the respective dimension by Right Clicking on the dimension and select Restriction based on History, Single Values, Value Ranges, Variables(across InfoProvider)

SAP OLAP Cache – Reporting Agent

OLAP Cache is very important to increase query performance.  It can be done on Queries that is created using BEx Query Designer or Web Templates that is created using BEx WAD or the Queries that are published on Portal (iViews).
For executing an particular Query if the Query data is in OLAP-Cache then the performance is much better then to get the Query requested data from the database.

To access Reporting Agent or in BI 7.0 type REPORTING_AGENT
GoTo T-Code RSA1OLD | Click Reporting Agent | Click Print – This will show all the query and reports|
Drill down to a particular Report | HighLight this report | Create New Reporting Agent Setting | Give name & Description | Check Fill OLAP Cache if possible | Save and Activaate
Go Back | You will see one Reporting Agent create | Select the newly created Reporting Agent | on the Right Hand side Column | Create New Scheduling Package by clicking on Create Button | Give name and Description | SAve

Now Drag the Reporting Agent to the right Hand side the Scheduling Package Windows.Save.
Schedule Immediately.

SAP BI – Remodeling/Repartioning/ReClustering

Before the release SAP BI 7.0 in the previous version 3.x; we were not able to Re-Partition, Re-Model, Re-Cluster if the data is already loaded.  We had to delete all the data and load it again. But with this 7.0 release; we do not have to delete the data to Remodel/RePartion/ReCluster

Remodeling is a new feature: if you want to add or delete field(attribute)
Implementation for Remodeling
1. Right Click the particular INfoCube | Additional Functions | Select Remodeling.
2. Give a Remodeling Rule Name | Transfer
3. To add and Attribute | Click Add an Operation to the List
4.  You will get all the options for ReModeling and Existing InfoCube

SAP BI – Physical Partitioning

Usage Example:  If you want to further partition the InfoCube on Database level; for example if you want to further partition YEAR InfoObject into Month like Jan, Feb, March, etc.  that time you use Physical Partitioning

Implementation Steps

GoTo RSA1
Extras | DB Performance | Click Partitioning

SAP Cube Contant – Logical Partitioning

Cube constant improves query performance while reporting.  For example a Cube has a large amount of data and we have requirement to create a report only on Fiscal Year 2008; then we can create a Cube constant for this particular year so that when query is executed; it will not search each and every data in the cube but just the Cube Constant

Steps to Implement Cube Constant

Open an InfoCube in Edit mode which has data in it.
Right Click on Dimension and select “Providers-Specific InfoObject Properties”
You can specific Fiscal Year = 2008 in the Constant Column
Save

If you want to create Cube Constant for 2008, 2009, 2010 then you will have to create 3 individual InfoCube with the Respective Cube Constant

PS: whatever restrictions made in the Cube Constant should also be made at InfoPackage Level at the time of loading the data