SAP BEX Toolbar - Ready Reckoner
Raj Salecha
Feb 18, 2013
Feb 11, 2013
Create an InfoCube
Create an InfoCube
via Content in SCN
Creating an InfoCubeIn BW,Customer ID,Material Number,Sales Representative ID,Unit of Measure,and Transaction Date are called characteristics. Customer Name and Customer Address are attributes of Customer ID,although they are characteristics as well. Per Unit Sales Price,Quantity Sold,and Sales Revenue are referred to as key figures. Characteristics and key figures are collectively termed InfoObjects.
A key figure can be an attribute of a characteristic. For instance,Per Unit Sales Price can be an attribute of Material Number. In our examples,Per Unit Sales Price is a fact table key figure. In the real world,such decisions are made during the data warehouse design phase. InfoCube Design provides some guidelines for making such decisions.
InfoObjects are analogous to bricks. We use these objects to build InfoCubes. An InfoCube comprises the fact table and its associated dimension tables in a star schema.
In this chapter,we will demonstrate how to create an InfoCube that implements the star schema from figure. We start from creating an InfoArea. An InfoArea is analogous to a construction site,on which we build InfoCubes.
Creating an InfoArea
In BW,InfoAreas are the branches and nodes of a tree structure. InfoCubes are listed under the branches and nodes. The relationship of InfoAreas to InfoCubes in BW resembles the relationship of directories to files in an operating system. Let's create an InfoArea first,before constructing the InfoCube.
Work Instructions
Step 1. After logging on to the BW system,run transaction RSA1,or double-click Administrator Workbench.
Step 2. In the new window,click Data targets under Modelling in the left panel. In the right panel,right-click InfoObjects and select Create InfoArea….
Note
In BW,InfoCubes and ODS Objects are collectively called data targets.
Step 3. Enter a name and a description for the InfoArea,and then
mark to continue.
Result
The InfoArea has been created.
Creating InfoObject Catalogs
Before we can create an InfoCube,we must have InfoObjects. Before we can create InfoObjects,however,we must have InfoObject Catalogs. Because characteristics and key figures are different types of objects,we organize them within their own separate folders,which are called InfoObject Catalogs. Like InfoCubes,InfoObject Catalogs are listed under InfoAreas.
Having created an InfoArea,let's now create InfoObject Catalogs to hold characteristics and key figures.
Work Instructions
Step 1. Click InfoObjects under Modelling in the left panel. In the right panel,right-click InfoArea–demo,and select Create InfoObject catalog….
Step 2. Enter a name and a description for the InfoObject Catalog,select the option Char.,and then click
to create the InfoObject Catalog.
Step 3. In the new window,click
to check the Info Object Catalog. If it is valid,click 
to activate the InfoObject Catalog. Once the activation process is finished,the status message InfoObject catalog IOC_DEMO_CH activated appears at the bottom of the screen.
Result
Click
to return to the previous screen. The newly created InfoObject Catalog will be displayed,as shown in Screen
Following the same procedure,we create an InfoObject Catalog to hold key figures. This time,make sure that the option Key figure is selected Screen.
Creating InfoObjects-Characteristics
Now we are ready to create characteristics.
Work Instructions
Step 1. Right-click InfoObject Catalog–demo: characteristics,and then select Create InfoObject….
Before we can create an InfoCube,we must have InfoObjects. Before we can create InfoObjects,however,we must have InfoObject Catalogs. Because characteristics and key figures are different types of objects,we organize them within their own separate folders,which are called InfoObject Catalogs. Like InfoCubes,InfoObject Catalogs are listed under InfoAreas.
Having created an InfoArea,let's now create InfoObject Catalogs to hold characteristics and key figures.
Work Instructions
Step 1. Click InfoObjects under Modelling in the left panel. In the right panel,right-click InfoArea–demo,and select Create InfoObject catalog….
Step 2. Enter a name and a description for the InfoObject Catalog,select the option Char.,and then click
to create the InfoObject Catalog.Step 3. In the new window,click
to check the Info Object Catalog. If it is valid,click to activate the InfoObject Catalog. Once the activation process is finished,the status message InfoObject catalog IOC_DEMO_CH activated appears at the bottom of the screen.Result
Click
to return to the previous screen. The newly created InfoObject Catalog will be displayed,as shown in ScreenFollowing the same procedure,we create an InfoObject Catalog to hold key figures. This time,make sure that the option Key figure is selected Screen.
Creating InfoObjects-Characteristics
Now we are ready to create characteristics.
Work Instructions
Step 1. Right-click InfoObject Catalog–demo: characteristics,and then select Create InfoObject….
Step 2. Enter a name and a description,and then click to continue.
to continue.
Step 3. Select CHAR as the DataType,enter 15 for the field Length,and then click the tab Attributes.
Step 4. Enter an attribute name IO_MATNM,and then click to create the attribute.
Note: Notice that IO_MATNM is underlined. In BW,the underline works like a hyperlink. After IO_MATNM is created,when you click IO_MATNM,the hyperlink will lead you to IO_MATNM's detail definition window.
Step 5. Select the option Create attribute as characteristic,and then click to continue.
Step 6. Select CHAR as the DataType,and then enter 30 for the field Length. Notice that the option Exclusively attribute is selected by default. Clickto continue.
Note: If Exclusively attribute is selected,the attribute IO_MATNM can be used only as adisplay attribute,not as a navigational attribute. "InfoCube Design Alternative I Time Dependent Navigational Attributes," discusses an example of the navigation attributes.
Selecting Exclusively attribute allows you to select Lowercase letters. If the option Lowercase letters is selected,the attribute can accept lowercase letters in data to be loaded.
If the option Lowercase letters is selected,no master data tables,text tables,or another level of attributes underneath are allowed. "BW Star Schema," describes master data tables and text tables,and explains how they relate to a characteristic.
Step 7. Click to check the characteristic. If it is valid,click to activate the characteristic.
Step 8. A window is displayed asking whether you want to activate dependent InfoObjects. In our example,the dependent InfoObject is IO_MATNM.
Clickto activate IO_MAT and IO_MATNM.
Result
You have now created the characteristic IO_MAT and its attribute IO_MATNM.
Note: Saving an InfoObject means saving its properties,or meta-data. You have not yet created its physical database objects,such as tables.
Activating an InfoObject will create the relevant database objects. After activating IO_MAT,the names of the newly created master data table and text table are displayed under the Master data/texts tab. The name of the master data table is /BIC/PIO_MAT,and the name of the text table is /BIC/TIO_MAT.
Notice the prefix /BIC/ in the database object names. BW prefixes /BI0/ to the names of database objects of Business Content objects,and it prefixes /BIC/ to the names of database objects of customer-created BW objects.
Repeat the preceding steps to create the other characteristics listed.
CHARACTERISTICS
The column "Assigned to" specifies the characteristic to which an attribute is assigned. For example,IO_MATNM is an attribute of IO_MAT.
The Material Description in Table will be treated as IO_MAT's text,as shown in Table,"Creating InfoPackages to Load Characteristic Data." We do not need to create a characteristic for it.
IO_SREG and IO_SOFF are created as independent characteristics,instead of IO_SREP's attributes. Section 3.6,"Entering the Master Data,Text,and Hierarchy Manually," explains how to link IO_SOFF and IO_SREG to IO_SREP via a sales organization hierarchy. "InfoCube Design Alternative I—Time-Dependent Navigational Attributes," discusses a new InfoCube design in which IO_SOFF and IO_SREG are IO_SREP's attributes.
BW provides characteristics for units of measure and time. We do not need to create them.From Administrator Workbench,we can verify that the characteristics in Table have been created by clicking InfoArea–demo,and then clicking InfoObject Catalog–demo: characteristics.
Creating Info Objects-Key Figures
Next,we start to create the keys.
Work Instructions
Step 1. Right-click InfoObject Catalog–demo: key figures,and then select Create InfoObject.
Step 2. Enter a name and a description,and then clickto continue.
Step 3. Select Amount in the block Type/data type,select USD as the Fixed currency in the block Currency/unit of measure,and then clickto check the key figure. If it is valid,click to activate the key figure.
Result
You have created the key figure IO_PRC. A status message All InfoObject(s) activated will appear at the bottom of Screen.
Repeat the preceding steps to create other key figures listed.
KEY FIGURES
From Administrator Workbench,we can verify that the key figures in Table have been created (Screen) by clicking InfoArea–demo,and then clicking InfoObject Catalog–demo: key figures.
Having created the necessary InfoObjects,we now continue to create the InfoCube.
Creating an InfoCube
The following steps demonstrate how to create an InfoCube,the fact table and associated dimension tables,for the sales data shown in Table
Work Instructions
Step 1. Select Data targets under Modelling in the left panel. In the right panel,right-click InfoArea–demo and then select Create InfoCube….
Step 2. Enter a name and a description,select the option Basic Cube in block InfoCube type,and then clickto create the InfoCube.
Note: An InfoCube can be a basic cube,a multi-cube,an SAP remote cube,or a general remote cube.A basic cube has a fact table and associated dimension tables,and it contains data. We are building a basic cube.
A multi-cube is a union of multiple basic cubes and/or remote cubes to allow cross-subject analysis. It does not contain data. See,Aggregates and Multi-Cubes,for an example.
A remote cube does not contain data;instead,the data reside in the source system. A remote cube is analogous to a channel,allowing users to access the data using BEx. As a consequence,querying the data leads to poor performance.
If the source system is an SAP system,we need to select the option SAP RemoteCube. Otherwise,we need to select the option Gen. Remote Cube. This book will not discuss remote cubes.
Step 3. Select IO_CUST,IO_MAT,and IO_SREP from the Template table,and move them to the Structure table by clicking
Next,click the Dimensions… button to create dimensions and assign these characteristics to the dimensions.
Step 4. Click,
and then enter a description for the dimension.
Note: BW automatically assigns technical names to each dimension with the format <InfoCube name><Number starting from 1>.
Fixed dimension <InfoCube name><P|T|U> is reserved for Data Packet,Time,and Unit. Section,"Data Load Requests," discusses the Data Packet dimension.
A dimension uses a key column in the fact table. In most databases,a table can have a maximum of 16 key columns. Therefore,BW mandates that an InfoCube can have a maximum of 16 dimensions: three are reserved for Data Packet,Time,and Unit; the remaining 13 are left for us to use.
Repeat the same procedure to create two other dimensions. Next,click the Assign tab to assign the characteristics to the dimensions.
Step 5. Select a characteristic in the Characteristics and assigned dimension block,select a dimension to which the characteristic will be assigned in the Dimensions block,and then click
to assign the characteristic to the dimension.
to create the attribute.Note: Notice that IO_MATNM is underlined. In BW,the underline works like a hyperlink. After IO_MATNM is created,when you click IO_MATNM,the hyperlink will lead you to IO_MATNM's detail definition window.
Step 5. Select the option Create attribute as characteristic,and then click
to continue.Step 6. Select CHAR as the DataType,and then enter 30 for the field Length. Notice that the option Exclusively attribute is selected by default. Click
to continue.Note: If Exclusively attribute is selected,the attribute IO_MATNM can be used only as adisplay attribute,not as a navigational attribute. "InfoCube Design Alternative I Time Dependent Navigational Attributes," discusses an example of the navigation attributes.
Selecting Exclusively attribute allows you to select Lowercase letters. If the option Lowercase letters is selected,the attribute can accept lowercase letters in data to be loaded.
If the option Lowercase letters is selected,no master data tables,text tables,or another level of attributes underneath are allowed. "BW Star Schema," describes master data tables and text tables,and explains how they relate to a characteristic.
Step 7. Click
to check the characteristic. If it is valid,click 
to activate the characteristic.Step 8. A window is displayed asking whether you want to activate dependent InfoObjects. In our example,the dependent InfoObject is IO_MATNM.
Click
to activate IO_MAT and IO_MATNM.Result
You have now created the characteristic IO_MAT and its attribute IO_MATNM.
Note: Saving an InfoObject means saving its properties,or meta-data. You have not yet created its physical database objects,such as tables.
Activating an InfoObject will create the relevant database objects. After activating IO_MAT,the names of the newly created master data table and text table are displayed under the Master data/texts tab. The name of the master data table is /BIC/PIO_MAT,and the name of the text table is /BIC/TIO_MAT.
Notice the prefix /BIC/ in the database object names. BW prefixes /BI0/ to the names of database objects of Business Content objects,and it prefixes /BIC/ to the names of database objects of customer-created BW objects.
Repeat the preceding steps to create the other characteristics listed.
CHARACTERISTICS
The column "Assigned to" specifies the characteristic to which an attribute is assigned. For example,IO_MATNM is an attribute of IO_MAT.
The Material Description in Table will be treated as IO_MAT's text,as shown in Table,"Creating InfoPackages to Load Characteristic Data." We do not need to create a characteristic for it.
IO_SREG and IO_SOFF are created as independent characteristics,instead of IO_SREP's attributes. Section 3.6,"Entering the Master Data,Text,and Hierarchy Manually," explains how to link IO_SOFF and IO_SREG to IO_SREP via a sales organization hierarchy. "InfoCube Design Alternative I—Time-Dependent Navigational Attributes," discusses a new InfoCube design in which IO_SOFF and IO_SREG are IO_SREP's attributes.
BW provides characteristics for units of measure and time. We do not need to create them.From Administrator Workbench,we can verify that the characteristics in Table have been created by clicking InfoArea–demo,and then clicking InfoObject Catalog–demo: characteristics.
Creating Info Objects-Key Figures
Next,we start to create the keys.
Work Instructions
Step 1. Right-click InfoObject Catalog–demo: key figures,and then select Create InfoObject.
Step 2. Enter a name and a description,and then click
to continue.Step 3. Select Amount in the block Type/data type,select USD as the Fixed currency in the block Currency/unit of measure,and then click
to check the key figure. If it is valid,click to activate the key figure.Result
You have created the key figure IO_PRC. A status message All InfoObject(s) activated will appear at the bottom of Screen.
Repeat the preceding steps to create other key figures listed.
KEY FIGURES
From Administrator Workbench,we can verify that the key figures in Table have been created (Screen) by clicking InfoArea–demo,and then clicking InfoObject Catalog–demo: key figures.
Having created the necessary InfoObjects,we now continue to create the InfoCube.
Creating an InfoCube
The following steps demonstrate how to create an InfoCube,the fact table and associated dimension tables,for the sales data shown in Table
Work Instructions
Step 1. Select Data targets under Modelling in the left panel. In the right panel,right-click InfoArea–demo and then select Create InfoCube….
Step 2. Enter a name and a description,select the option Basic Cube in block InfoCube type,and then click
to create the InfoCube.Note: An InfoCube can be a basic cube,a multi-cube,an SAP remote cube,or a general remote cube.A basic cube has a fact table and associated dimension tables,and it contains data. We are building a basic cube.
A multi-cube is a union of multiple basic cubes and/or remote cubes to allow cross-subject analysis. It does not contain data. See,Aggregates and Multi-Cubes,for an example.
A remote cube does not contain data;instead,the data reside in the source system. A remote cube is analogous to a channel,allowing users to access the data using BEx. As a consequence,querying the data leads to poor performance.
If the source system is an SAP system,we need to select the option SAP RemoteCube. Otherwise,we need to select the option Gen. Remote Cube. This book will not discuss remote cubes.
Step 3. Select IO_CUST,IO_MAT,and IO_SREP from the Template table,and move them to the Structure table by clicking
Next,click the Dimensions… button to create dimensions and assign these characteristics to the dimensions.
Step 4. Click,
and then enter a description for the dimension.Note: BW automatically assigns technical names to each dimension with the format <InfoCube name><Number starting from 1>.
Fixed dimension <InfoCube name><P|T|U> is reserved for Data Packet,Time,and Unit. Section,"Data Load Requests," discusses the Data Packet dimension.
A dimension uses a key column in the fact table. In most databases,a table can have a maximum of 16 key columns. Therefore,BW mandates that an InfoCube can have a maximum of 16 dimensions: three are reserved for Data Packet,Time,and Unit; the remaining 13 are left for us to use.
Repeat the same procedure to create two other dimensions. Next,click the Assign tab to assign the characteristics to the dimensions.
Step 5. Select a characteristic in the Characteristics and assigned dimension block,select a dimension to which the characteristic will be assigned in the Dimensions block,and then click
to assign the characteristic to the dimension.
Step 6. After assigning all three characteristics to their dimensions,click to continue.
to continue.
Step 7. Select the Time characteristics tab,select 0CALDAY from the Template table,and move it to the Structure table by clicking
Step 8. Select the Key figures tab,select IO_PRC,IO_QUAN,and IO_REV from the Template table and move them to the Structure table by clicking.
Next,clickto check the InfoCube. If it is valid,click to activate the InfoCube.
Result:
You have created the InfoCube IC_DEMOBC. A status message InfoCube IC_DEMOBC activated will appear at the bottom of Screen.
Summary
In this chapter,we created an InfoCube. To display its data model,you can right-click InfoCube–demo: Basic Cube,then select Display data model….
The data model appears in the right panel of Screen .
Note:
IO_SREG and IO_SOFF are not listed under IO_SREP as attributes; rather,they have been created as independent characteristics. "Entering the Master Data,Text,and Hierarchy Manually," describes how to link IO_SOFF and IO_SREG to IO_SREP via a sales organization hierarchy. "InfoCube Design Alternative I— Time-Dependent Navigational Attributes,"discusses a new InfoCube design in which IO_SOFF and IO_SREG are IO_SREP's attributes.
Next,click
to check the InfoCube. If it is valid,click to activate the InfoCube.Result:
You have created the InfoCube IC_DEMOBC. A status message InfoCube IC_DEMOBC activated will appear at the bottom of Screen.
Summary
In this chapter,we created an InfoCube. To display its data model,you can right-click InfoCube–demo: Basic Cube,then select Display data model….
The data model appears in the right panel of Screen .
Note:
IO_SREG and IO_SOFF are not listed under IO_SREP as attributes; rather,they have been created as independent characteristics. "Entering the Master Data,Text,and Hierarchy Manually," describes how to link IO_SOFF and IO_SREG to IO_SREP via a sales organization hierarchy. "InfoCube Design Alternative I— Time-Dependent Navigational Attributes,"discusses a new InfoCube design in which IO_SOFF and IO_SREG are IO_SREP's attributes.
---END---
Jan 23, 2013
SAP BusinessObjects Analysis Workbook and SAP BW
via Content in SCN
Hello Everyone!
This blog would demostrate that with SAP BusinessObjects Analysis edition for MS Office release 1.3 is possible, finally, to save workbook on SAP BW.
The previous realease of this frontend tool allowed to save workbook only on the BI platform.
The file format that you can store are: xls,xlsx, ppt and pptx and is necessary on SAP BW have an role that contain the authorization object R_RS_AO.
Then a window appear that permit to choice where save the workbook: in a Role or in the folder "My documents".
In SAP NetWeaver Business Warehouse, Analysis objects are stored with object type AAOE (for workbooks) and AAOP (for presentations).
When the user, access to SAP BW by SAP GUI, the workbook will be visible on the menu:
To launch the analysis workbook from SAP menu is necessary SAP Netweaver BW 730 SP8 (see SAP Notes 1724842).
Jan 21, 2013
Customer specific adjusting of BEx web-based variable screen
1 Introduction
The possibilities of adaptation of a web-based report dialog variables were previously restricted. About parameters of the WebTemplate and using the Web Design API that can be charged affects the behavior of Web Templates in the variables but not the layout and processing logic of the input
Figure 1.1: SAP Standard Variable Dialog
With patch NW730 BI JAVA SP08 Patch 30 (see also Note 1622306),
SAP offers a possibility the layout and processing logic for the following dialogues with respect to variable processing to adapt:
Variables
Dialogue
Filter
For customer-specific adaptation of the variables dialog, two alternative routes are available:
Customized formatting and positioning
Customer-specific layout and processing logic
The principle of implementation is the same for all kinds of adjustment. About a Web item types of Individual expansion of the BEx Web runtime, an HTML and / or JavaScript code segment (Snipplte) is passed. The BEx Web runtime replaces the standard SAP code passed by the code segments. Thus, the BEx Web runtime performs this replacement process, certain conditions must be met. I go even further down into the details of the implementation.
2 Customized formatting and positioning
The first way is to adjust the variable dialog customized, positioning to the individual elements of the variables dialog customized. For determining the positions of the individual elements can be any HTML tags are used. For the individual elements are patterns (pattern) are available which can be placed within a customized HTML text.
The following items are available:
Area variants
Areaersonalize
Eachvariable of the report
OK-Button
Check-Button
The pattern will be placed as a custom XML tags in customized HTML coding. The BEx Web runtime environment recognizes the pattern and replaces them with the necessary coding.
Figure 2.2 shows in (1) a custom dialog variables in the areas of personalization options and were just like the OK button and check positioned similar to the standard variable dialog.
The variables were divided into time-related variables, and not time-related variables. To better highlight this structure for each type, a separate group was formed.
Figure 2.1: Customer-specific formatting and positioning
Variables
Dialogue
Filter
For customer-specific adaptation of the variables dialog, two alternative routes are available:
Customized formatting and positioning
Customer-specific layout and processing logic
The principle of implementation is the same for all kinds of adjustment. About a Web item types of Individual expansion of the BEx Web runtime, an HTML and / or JavaScript code segment (Snipplte) is passed. The BEx Web runtime replaces the standard SAP code passed by the code segments. Thus, the BEx Web runtime performs this replacement process, certain conditions must be met. I go even further down into the details of the implementation.
2 Customized formatting and positioning
The first way is to adjust the variable dialog customized, positioning to the individual elements of the variables dialog customized. For determining the positions of the individual elements can be any HTML tags are used. For the individual elements are patterns (pattern) are available which can be placed within a customized HTML text.
The following items are available:
Area variants
Areaersonalize
Eachvariable of the report
OK-Button
Check-Button
The pattern will be placed as a custom XML tags in customized HTML coding. The BEx Web runtime environment recognizes the pattern and replaces them with the necessary coding.
Figure 2.2 shows in (1) a custom dialog variables in the areas of personalization options and were just like the OK button and check positioned similar to the standard variable dialog.
The variables were divided into time-related variables, and not time-related variables. To better highlight this structure for each type, a separate group was formed.
Figure 2.1: Customer-specific formatting and positioning
Adjustment in (2) illustrates the use of more complex HTML components. Here, only the time-related variables shown directly and all other variables are hidden on a tray. This allows the variable dialog for reports with a lot of variables to be made clearer and thus the ease of use increased.
The implementation of the component tray used here is purely on HTML and JavaScript, and needs no round-trip.
This representation could be achieved through a personalization that could not be controlled centrally.
3 Customer Individual Variable dialog
Another option is to adjust the variable dialog to make the layout and processing logic for each variable individually customized.
In this variant is not the SAP standard HTML coding of the entire variables dialogue replaced by customer-specific HTML coding but only the ranges for the input variable values. In the Variables dialog in Figure 3.1, the SAP standard HTML coding for the two variables CURRENT PREVIOUS YEAR PERIOD
YERA PERIOD and was replaced by customized HMTL code.
Figure 3.1: Individual customer's variables dialog
For the example implementation shown in Figure 3.1 has been deposited adjacent to the surface for the input of a very specific period still additional JavaScript code, through which a function of the two variables and PREVIOUS YEAR CURRENT PERIOD YEAR PERIOD was implemented.
Validation and adjustment of variable values
When entering a value for a period of two variables is automatically checked whether the variable value of the other period, according to custom rules, is still
valid. This is not the case; the value is adjusted according to the rules directly.
Such validation and adjustment is not possible without this extension, since it is in the customer exit in I_STEP 3 is not possible to override the values of the user.
Analogous to the implementation of a customized variables dialogue must also be replaced by a Web item types from individual extension of the SAP standard HTML code. In this variant, for each variable of a Web item types must Individual expansion in WebTemplate be deposited.
For the implementation of custom HTML code for some HTML elements are also patterns provided. For these HTML elements are patterns available:
Input Feld
Dropdown-Box
Label
The pattern is used to facilitate the creation of a portal layout compliant HTML code, but they are not to use it. Some properties of the extension can be customized via parameters from the Web item type Individual expansion in WebTemplate.
For each extension the BEx Web runtime environment add a standard variable input field automatically into the layout. About the Web item parameters, you can control whether the input field should be displayed above or below the user-defined layouts.
Standard input field
Using JavaScript, it is also possible to hide the standard input field. Important is that it is available within the HTML page. Also, the button for the F4 help can be hidden using JavaScript if it is not needed.
The aim of the implementation is to fill this field with the variable value.
Layout
In the current version you some adjustments at the layout of are necessary. This applies, for example, the width of the dialog variables; the height of the row in a customer-specific adaptation is embedded. Positioning of the standard input field for the variable value.
4 Customized F4 and filter dialogs
Another way of displaying variables is the customer-specific adaptation of the F4 and filter dialogs. Figure 4.1 shows two different implementations of an F4 input help dialog for the variable ZTK_0I0DAYS. In the above example, the values are displayed with a reference period.
Dependencies between variables
The F4 help dialog is used explicitly for a variable. In this variant, it is not possible to influence the values of another with. Technically, the dialogue contains
an extra field that contains the value of the variable. This field is closely associated with the variable. The value of this field is passed when you close the dialog via the OK button of the dialog variables for exactly that variable. The extension replaces only the HTML code within the F4 help dialog.
Figure 4.1: Individual customers F4 and filter dialog
For each dialogue has its own Web item types of Individual expansion in WebTemplate provided. Here it is possible to reuse the implementation. You want an individual F4 help dialog for variable 0I_CALMONTH (based on 0CALMONTH) Implement. At the same time you want, however, that if the user in the report a filter to the feature 0CALMONTH applying the filter dialog has the analogous behavior as the F4 help dialog. You can do this in the Web item you both use the same implementation class. It is equally possible to implement different dialogues.
5 Implementation
The implementation of all the extensions described above is always the same principle. Figure 5.1 shows the architecture of the individual extensions.
Figure 5.1: Architecture – SAP Standard
The number of implementations of the Web item types of Individual expansion may increase due to the many possible combinations quickly. To every implementation of a Web item types of Individual expansion ever heard an implementing ABAP OO class.
Using a BAdI, the different implementations to be better organized and structured. It also provides the advanced architecture of the BAdI framework
the ability to create templates that simplify the implementation costs of new implementations and greatly shorten. Additionally, a fallback implementation is stored in the event that an implementation is not available.
The implementation of the component tray used here is purely on HTML and JavaScript, and needs no round-trip.
This representation could be achieved through a personalization that could not be controlled centrally.
3 Customer Individual Variable dialog
Another option is to adjust the variable dialog to make the layout and processing logic for each variable individually customized.
In this variant is not the SAP standard HTML coding of the entire variables dialogue replaced by customer-specific HTML coding but only the ranges for the input variable values. In the Variables dialog in Figure 3.1, the SAP standard HTML coding for the two variables CURRENT PREVIOUS YEAR PERIOD
YERA PERIOD and was replaced by customized HMTL code.
Figure 3.1: Individual customer's variables dialog
For the example implementation shown in Figure 3.1 has been deposited adjacent to the surface for the input of a very specific period still additional JavaScript code, through which a function of the two variables and PREVIOUS YEAR CURRENT PERIOD YEAR PERIOD was implemented.
Validation and adjustment of variable values
When entering a value for a period of two variables is automatically checked whether the variable value of the other period, according to custom rules, is still
valid. This is not the case; the value is adjusted according to the rules directly.
Such validation and adjustment is not possible without this extension, since it is in the customer exit in I_STEP 3 is not possible to override the values of the user.
Analogous to the implementation of a customized variables dialogue must also be replaced by a Web item types from individual extension of the SAP standard HTML code. In this variant, for each variable of a Web item types must Individual expansion in WebTemplate be deposited.
For the implementation of custom HTML code for some HTML elements are also patterns provided. For these HTML elements are patterns available:
Input Feld
Dropdown-Box
Label
The pattern is used to facilitate the creation of a portal layout compliant HTML code, but they are not to use it. Some properties of the extension can be customized via parameters from the Web item type Individual expansion in WebTemplate.
For each extension the BEx Web runtime environment add a standard variable input field automatically into the layout. About the Web item parameters, you can control whether the input field should be displayed above or below the user-defined layouts.
Standard input field
Using JavaScript, it is also possible to hide the standard input field. Important is that it is available within the HTML page. Also, the button for the F4 help can be hidden using JavaScript if it is not needed.
The aim of the implementation is to fill this field with the variable value.
Layout
In the current version you some adjustments at the layout of are necessary. This applies, for example, the width of the dialog variables; the height of the row in a customer-specific adaptation is embedded. Positioning of the standard input field for the variable value.
4 Customized F4 and filter dialogs
Another way of displaying variables is the customer-specific adaptation of the F4 and filter dialogs. Figure 4.1 shows two different implementations of an F4 input help dialog for the variable ZTK_0I0DAYS. In the above example, the values are displayed with a reference period.
Dependencies between variables
The F4 help dialog is used explicitly for a variable. In this variant, it is not possible to influence the values of another with. Technically, the dialogue contains
an extra field that contains the value of the variable. This field is closely associated with the variable. The value of this field is passed when you close the dialog via the OK button of the dialog variables for exactly that variable. The extension replaces only the HTML code within the F4 help dialog.
Figure 4.1: Individual customers F4 and filter dialog
For each dialogue has its own Web item types of Individual expansion in WebTemplate provided. Here it is possible to reuse the implementation. You want an individual F4 help dialog for variable 0I_CALMONTH (based on 0CALMONTH) Implement. At the same time you want, however, that if the user in the report a filter to the feature 0CALMONTH applying the filter dialog has the analogous behavior as the F4 help dialog. You can do this in the Web item you both use the same implementation class. It is equally possible to implement different dialogues.
5 Implementation
The implementation of all the extensions described above is always the same principle. Figure 5.1 shows the architecture of the individual extensions.
Figure 5.1: Architecture – SAP Standard
The number of implementations of the Web item types of Individual expansion may increase due to the many possible combinations quickly. To every implementation of a Web item types of Individual expansion ever heard an implementing ABAP OO class.
Using a BAdI, the different implementations to be better organized and structured. It also provides the advanced architecture of the BAdI framework
the ability to create templates that simplify the implementation costs of new implementations and greatly shorten. Additionally, a fallback implementation is stored in the event that an implementation is not available.
Figure 5.2: Architecture - SAP standard with BAdI
~~~END~~~
Jan 18, 2013
Possibilities of BW projects documenting – Transformations
Possibilities of BW projects documenting – Transformations
via something about SAP by sapper
Some time ago I blogged about possibilities of BW BEx queries documenting. There are many other BW objects being developed during BW implementation that are also needed to be documented. In this post I focus on transformations. Following are the options to document transformation (TRFN) that I came across:
1. BW metadata repository: It is available in TA RSA1 which you select particular TRFN and press F1 button. It open web browser with page generated out of web dynpro RSO_METADATA_REPOSITORY. You can either save this page in HTML format or embed it into your documentation as attached file. Other possibility is to just include URL link.
2. Tabular overview: Functionality is available in TA RSA1: while you in display/change screen of TRFN choose Tabular overview from Extras menu. You get new pop up window with overview of all IOs used, Rules details, Start/End Routine. You can copy content of this window to your documentation via clipboard.
3. Save as picture: From display/change screen in TA RSA1 you have Save as picture functionality available. You can afterwards include this picture into your documentation.
Read Further at source : http://sapport.blogspot.com/2012/10/possibilities-of-bw-projects.html
Jan 17, 2013
Five Factors for a Successful SAP HANA Implementation
via Content in SCN
The ability to manage "big data" in real time has revolutionized the way businesses analyze and manage performance. The revolution, though, lies in more than just quick data processing – instead, new database technology from SAP radically changes how and when businesses use the information they receive, regardless of its volume and complexity.
With SAP® NetWeaver® Business Warehouse (BW) running on SAP HANA, SAP has changed how organizations think about data management technologies, construct applications, and consume the results. Businesses that adopt new technology can sharpen their competitive edge by dramatically accelerating the speed of not only data queries but fundamental business processes.
You can benefit from this new database model in one of two ways:
1. Upgrade your existing installation to deploy SAP NetWeaver BW powered by SAP HANA, ending up with a single instance of SAP NetWeaver Data Warehouse
2. Install a new instance of SAP NetWeaver BW 7.3, running a parallel landscape
(To find out which implementation option is right for you, see this article by Tom Kurtz.)
Whatever option you choose, five major factors affect the success of your implementation:
1. Up-front assessment : Before you begin, it helps to understand the requirements and scope of a SAP HANA implementation. Assess your overall architecture, database platform, business applications, and current SAP NetWeaver BW footprint. You also need a clear understanding of the technical elements of your implementation. Do you need to upgrade to SAP NetWeaver BW 7.3? If so, which version will you be upgrading from – 7.x or 3.5? What about requirements such as authorization migration and Unicode migration?
Before SAP HANA, SAP BW consultants routinely followed a Layered, Scalable Architecture (LSA) methodology for building and structuring the business warehouse. The LSA methodology helped create a standardized approach that organized data by functional area, geography, and other key dimensions. With SAP HANA, the new LSA++ methodology takes advantage of in-memory capabilities to deliver simplified data models, increasing flexibility and optimizing enterprise performance management. Using LSA++, which is a fundamentally different approach to data modeling, requires careful upfront planning to optimize your SAP NetWeaver BW solution powered by SAP HANA.
Performing an upfront assessment will align the HANA platform with the strategic solution landscape. Accurate scoping and a clearly defined architecture and design will help you stay on schedule, meet financial budgets, and identify necessary skills and personnel.
2. Data quality and sizing: With a SAP NetWeaver BW on SAP HANA implementation, as with any data solution, the results are only as good as the data you start with. Take the time to analyze existing data, clearly define which data should be migrated, and specify the volume of data to be stored, and you'll be more likely to accurately size the required HANA hardware – and limit unexpected changes during the implementation.
Also consider the data to be stored in the SAP HANA system. You must understand both the frequency of data loads and which elements and volumes need to be loaded. SAP BW Data Store Object (DSO) improvements provide significant data load performance benefits and directly take advantage of SAP HANA's column-based data processing. However to ensure optimal performance and a robust and scalable solution, you'll want to clearly architect the data elements and points of integration.
Data management must be an ongoing consideration, and your final data optimization exercise should be performed after migration. To take full advantage of SAP HANA in-memory capabilities, deploy SAP HANA as the database for the SAP NetWeaver BW instance following the principles for LSA++.
Also consider the data to be stored in the SAP HANA system. You must understand both the frequency of data loads and which elements and volumes need to be loaded. SAP BW Data Store Object (DSO) improvements provide significant data load performance benefits and directly take advantage of SAP HANA's column-based data processing. However to ensure optimal performance and a robust and scalable solution, you'll want to clearly architect the data elements and points of integration.
Data management must be an ongoing consideration, and your final data optimization exercise should be performed after migration. To take full advantage of SAP HANA in-memory capabilities, deploy SAP HANA as the database for the SAP NetWeaver BW instance following the principles for LSA++.
3. Related project components : An SAP NetWeaver BW on HANA migration is likely to interact with a number of other systems and applications; consider how the interplay among them will affect the project. For example, SAP BusinessObjects™ Business Intelligence (BI) solutions are often used for SAP HANA solution output. Ensure best practices for business intelligence implementation, and ask the project team to consider data output formats.
Also consider how data gets into SAP HANA. It may seem straightforward to load SAP ERP data into SAP HANA, but what about the ETL approach for data from non-SAP sources? Mismanaged data can lead to project escalations and delays.
Increasingly SAP NetWeaver BW on SAP HANA projects are not just for reporting and analytics purposes. SAP solutions are also taking advantage of SAP NetWeaver BW on SAP HANA as a platform. For example, SAP Business Planning and Consolidation (BPC), SAP Business Warehouse Integrated Planning (BW-IP), and SAP Strategic Enterprise Management (SEM) products all have the capability to take direct advantage of SAP HANA in-memory and high performance capabilities. If your project contains one of these solutions, you should ensure it includes the specific, related SAP HANA functionality.
4. Project management : There is no single timeline for an SAP HANA project. Each project is different; each has distinctive contributing factors, characteristics, and objectives. Use a standard project methodology, such as the SAP ASAP implementation methodology, to ensure that a project addresses all critical activities, phases, and deliverables necessary for success. The SAP ASAP methodology has been updated to incorporate SAP HANA activities required for a standard in-memory project. Accelerators, best practices, and implementation tools have also been updated or developed to shorten project timelines and reduce risk. Methodology, timelines, and key activities will vary based on your technical landscape, expectations for in-memory functionality, and use case.
Of course, with complex SAP HANA projects the need for robust project management only increases. Strong project management can provide visibility while ensuring the best possible outcome for each project.
5. Skills and experience : SAP HANA is a new technology – the success of any implementation depends in large part on your ability to find experts with needed skills. Critical resources will also vary depending on how you leverage the SAP HANA in-memory solution and the use case you choose.
Consultants at SAP Services HANA Center of Excellence (COE) have in-depth skills and knowledge that come from having performed a multitude of complex implementations. Based on extensive experience with numerous successful SAP NetWeaver BW on HANA implementations, the SAP Services HANA COE can advise you of the best approach and alert you to common pitfalls. With a large pool of certified talent, SAP Services HANA COE can help ensure the success of your SAP HANA implementation while speeding timelines and managing the return on investment.
Learn More
Let SAP HANA Services help you optimize your SAP NetWeaver BW on SAP HANA implementation. We can help with assessment, data sizing, and quality issues; solution considerations; project management; and more. Whether you need initial advisory design or a complete implementation, SAP's expert planning and installation services can help you streamline and accelerate your migration plan for maximum benefit.
To learn more about how SAP can help you deliver maximum business benefits, go to ww.sap.com/services.
Increasingly SAP NetWeaver BW on SAP HANA projects are not just for reporting and analytics purposes. SAP solutions are also taking advantage of SAP NetWeaver BW on SAP HANA as a platform. For example, SAP Business Planning and Consolidation (BPC), SAP Business Warehouse Integrated Planning (BW-IP), and SAP Strategic Enterprise Management (SEM) products all have the capability to take direct advantage of SAP HANA in-memory and high performance capabilities. If your project contains one of these solutions, you should ensure it includes the specific, related SAP HANA functionality.
4. Project management : There is no single timeline for an SAP HANA project. Each project is different; each has distinctive contributing factors, characteristics, and objectives. Use a standard project methodology, such as the SAP ASAP implementation methodology, to ensure that a project addresses all critical activities, phases, and deliverables necessary for success. The SAP ASAP methodology has been updated to incorporate SAP HANA activities required for a standard in-memory project. Accelerators, best practices, and implementation tools have also been updated or developed to shorten project timelines and reduce risk. Methodology, timelines, and key activities will vary based on your technical landscape, expectations for in-memory functionality, and use case.
Of course, with complex SAP HANA projects the need for robust project management only increases. Strong project management can provide visibility while ensuring the best possible outcome for each project.
5. Skills and experience : SAP HANA is a new technology – the success of any implementation depends in large part on your ability to find experts with needed skills. Critical resources will also vary depending on how you leverage the SAP HANA in-memory solution and the use case you choose.
Consultants at SAP Services HANA Center of Excellence (COE) have in-depth skills and knowledge that come from having performed a multitude of complex implementations. Based on extensive experience with numerous successful SAP NetWeaver BW on HANA implementations, the SAP Services HANA COE can advise you of the best approach and alert you to common pitfalls. With a large pool of certified talent, SAP Services HANA COE can help ensure the success of your SAP HANA implementation while speeding timelines and managing the return on investment.
Learn More
Let SAP HANA Services help you optimize your SAP NetWeaver BW on SAP HANA implementation. We can help with assessment, data sizing, and quality issues; solution considerations; project management; and more. Whether you need initial advisory design or a complete implementation, SAP's expert planning and installation services can help you streamline and accelerate your migration plan for maximum benefit.
To learn more about how SAP can help you deliver maximum business benefits, go to ww.sap.com/services.
On the perils of using SAP HANA
via Content in SCN
Being an advocate of SAP HANA makes me somewhat idiosyncratic. I tend to see the advantages of implementing SAP HANA for BW systems, but I am not involved in the "other side" of the BW administrators. Recently I discussed the implementation of SAP HANA for my favorite BW landscape. Speaking with the responsible BW administrators was somewhat of an eye-opener for me. Even if such issues like hardware selection/sizing and overall project funding are clarified, then there remain four obstacles or let's better say challenges:
1. Encryption
I was asked whether the current version of SAP HANA supports data encryption. I had to say no, and this clearly violated the corporate policy. So no HANA implementation is possible right away. Life can be hard. There is this ideal landscape - THE landscape why SAP developed HANA in the first place, and it cannot be implemented due to the security policy! I was flabbergasted. I just hoped that SAP would provide encryption in a future release to alleviate this problem. Luckily the "what's new" of HANA 1.0 SPS05 was right on the spot. This obstacle was fixed really fast, thanks SAP!
2. Resources
BW data loading can be really complicated. There are some old and obsolete BW instances which cannot easily be dumped due to some complex data loading configurations. Unfortunately, such old instances bind resources, and this can hinder the implementation of new technologies like SAP HANA. It doesn't really matter if you have some old reference systems which cannot be shut down due to legal reasons, but using obsolete BW releases (on obsolete HW/OS/DB) for reporting is getting more and more critical. Of course this is well known among the BW administrators, but not being able to support such an obsolescence process in any way goes against my grain as being a support engineer.
3. Capacity Planning
BW systems can be very demanding and tend to be very important for a company, therefore better use good hardware. The hardware should neither be under nor over utilized. Either way you'll get complaints. So you need a good capacity planning process. BW systems are "work in progress" with different projects running concurrently and new subprojects going live all the time. If you have finally found a working solution so that the CPU-, memory- and IO-demands can be met in an economic way, you can be pretty sure a game changer like SAP HANA will void that process. I would not call that a real obstacle because the SAP HANA scale-out solution together with the "pay-per-use" software license should reduce the pressure from capacity planning and move it to performance + resource consumption reporting. However, if I say capacity planning is no problem, that could be only marketing speak as long as there is no verification in real life.
4. Data Issues
OK, so now for the straight talk. There was one issue which I really didn't anticipate and could cause some subsequent problems: I was told that implementing HANA would enable the end users to see all the data, because certain queries wouldn't time-out any more. So end users could complain that in certain areas only mockup data is loaded, not the real data. This of course means some more follow-up work on the data loading side to provide the real data. You better plan such tasks as part of the migration project if you don't want to enter reactive mode. HANA will raise the data quality because it will really make it possible to check all the data. Have you ever wondered what to do with the people who are currently struggling with performance troubleshooting? This is the answer what they will be doing after the migration to HANA.
Conclusion
My expressed thoughts are of course my very own opinion. Nevertheless I expect HANA to reveal some more strange intricacies which are not related to software bugs or architecture issues.
SAP BI Infocube
SAP BI Infocube
Source :
SCN
Note:
A) Standard Info Cube: Stores data, used for historical reporting These are called as Info providers.
B) Virtual Info cube: Doesn't store data, Used for online reporting
a. These are divided into three types
i. Based on DTP direct access
ii. Based on BAPI's
iii. Based on Function Module
c) Real Time Inco Cube:These are used for actual and planned comparison
Standard Info Cube:Steps to create Info Cube: (Standard Info Cube)
- Go to RSA1
- Go to Info provider section
- Right click on Info Area
- Select 'Create Info cube'
- Give some technical name, description
- Select type of info cube (standard)
- Click on Create
- Right click on 'Dimension' folder
- Create new dimensions and give description
- Select option Info object catalog
- Select Characteristic Info object catalog and drag necessary info objects into dimensions
- Select Key Figure Info object catalog and drag and drop them into key figure folder
- Click on 'Activate'
Note: Navigational attribute has to be activated at Info object level and Info provider level
Virtual Info cube: We go for this info cube if the data is less and the number of users executing the query is less.
- Direct access to data in BI system without extraction is available using virtual info cube or virtual providers.
- Virtual providers are info providers with transaction data that is not stored in the object itself but which is read directly in reporting
- The relevant data can be from BI system or SAP system or non-SAP system
- Virtual Provider is of three types. They are :
Virtual Providers based on DTP (with Direct Access):
- This type of virtual provider is based on data source or an info provider and takes its characteristics and key figures.
- Unlike other virtual providers we do not need to program interfaces in the source system.
- We use the same extractor to select the data in source system and replicate the data in BI system.
- We use the virtual provider when we need up to date data from SAP source system, when we are accessing small amount of data from time to time, or when few users execute the query simultaneously on database
Virtual provider with BAPI's: We use this virtual provider to carry out reporting on data in external system without having to physically store data in BI system
Virtual provider with Function module: We use this virtual provider if we want to display data from non BI data sources in BI without having to copy the data set into BI structures
Steps to create virtual providers:
- Create info objects
- Right click on 'Info Area' in Info Provider section
- Select create virtual provider
- Give info cube technical name
- Give description
- Select virtual provider option
- Click on 'Create'
- Create dimension tables
- Assign characteristics to necessary dimensions
- Drag and drop necessary key figures
- Click on activate
- Right click on info cube (virtual provider)
- Select Activate Direct Access option
- Click on Save
- Go to source system
- Right click on source system
- Select 'Display data source tree'
- Create Application component
- Right click on application component and create data source
- In Extraction tab, select direct access allowed (other steps are similar to flat file extraction)
- Activate data source
- Right click on data source, select 'Create Transformations'
- Select target object type
- Give technical name of object
- Click on continue and activate the transformation
- Right click on data source, select data transfer process, create Direct Access DTP
- Click on Activate
- Right click on virtual provider
- Select display data
- Go to fields selection for output
- Select necessary characteristics and key figures
- Click on execute twice
SAP BI Infocube
Source :
SCN
Info cubes are of three types. They are:
a.
Standard Info cube
b.
Virtual Info cube
c.
Real time info cube
Note:
The difference between standard info cube and virtual info cube is that the standard info cube holds data but the virtual info cube doesn't hold/ store data. Standard Info cube is used for historical reporting and the Virtual Info cube is used for online reporting.A) Standard Info Cube: Stores data, used for historical reporting These are called as Info providers.
B) Virtual Info cube: Doesn't store data, Used for online reporting
a. These are divided into three types
i. Based on DTP direct access
ii. Based on BAPI's
iii. Based on Function Module
c) Real Time Inco Cube:These are used for actual and planned comparison
Standard Info Cube:Steps to create Info Cube: (Standard Info Cube)
Necessary info objects are to be created and follow the below
steps
- Go to RSA1
- Go to Info provider section
- Right click on Info Area
- Select 'Create Info cube'
- Give some technical name, description
- Select type of info cube (standard)
- Click on Create
- Right click on 'Dimension' folder
- Create new dimensions and give description
- Select option Info object catalog
- Select Characteristic Info object catalog and drag necessary info objects into dimensions
- Select Key Figure Info object catalog and drag and drop them into key figure folder
- Click on 'Activate'
- Direct access to data in BI system without extraction is available using virtual info cube or virtual providers.
- Virtual providers are info providers with transaction data that is not stored in the object itself but which is read directly in reporting
- The relevant data can be from BI system or SAP system or non-SAP system
- Virtual Provider is of three types. They are :
- This type of virtual provider is based on data source or an info provider and takes its characteristics and key figures.
- Unlike other virtual providers we do not need to program interfaces in the source system.
- We use the same extractor to select the data in source system and replicate the data in BI system.
- We use the virtual provider when we need up to date data from SAP source system, when we are accessing small amount of data from time to time, or when few users execute the query simultaneously on database
Virtual provider with Function module: We use this virtual provider if we want to display data from non BI data sources in BI without having to copy the data set into BI structures
- Create info objects
- Right click on 'Info Area' in Info Provider section
- Select create virtual provider
- Give info cube technical name
- Give description
- Select virtual provider option
- Click on 'Create'
- Create dimension tables
- Assign characteristics to necessary dimensions
- Drag and drop necessary key figures
- Click on activate
- Right click on info cube (virtual provider)
- Select Activate Direct Access option
- Click on Save
- Go to source system
- Right click on source system
- Select 'Display data source tree'
- Create Application component
- Right click on application component and create data source
- In Extraction tab, select direct access allowed (other steps are similar to flat file extraction)
- Activate data source
- Right click on data source, select 'Create Transformations'
- Select target object type
- Give technical name of object
- Click on continue and activate the transformation
- Right click on data source, select data transfer process, create Direct Access DTP
- Click on Activate
- Right click on virtual provider
- Select display data
- Go to fields selection for output
- Select necessary characteristics and key figures
- Click on execute twice
Sep 22, 2012
Authorization in BI 7 - Part 1
Authorization in BI 7 - Part 1
via Content in SCN by Priyanka Joshi on 5/22/12
This blog will give the information related to Authorization concept available in SAP BW. Also, steps are given to maintain report related authorization.
Why is Authorization required in SAP BW?
Authorization in SAP BW 3.x
What's new in SAP BI 7 for Authorization?
Prerequisites for authorization
Steps to create authorization object for SAP BI 7
- To avoid the unwanted access to various objects as well as data in SAP BW system.
- To assign restricted access of data to report users.
- BW 3.x required Infoprovider Check to activate or deactivate authorization on the given reports.
- Analysis authorization
- New standard authorization objects have been added.
- Decide for which all reports an authorization is required.
- Make list of infoobjects which will act as authorization specific infoobjects in reports.
- Check whether all the required infoobjects are Authorization Relevant or not, if not marked then activate the flag.
- Now check the Authorization Mode in SPRO
- For SAP BW 3.x - Obsolete concept with RSR authorization objects.
- For SAP BI 7 or above - Current procedure with analysis authorizations.
- SPRO path
- SAP Customizing Implementation Guide
- SAP NetWeaver
- Business Intelligence
- Settings for Reporting and Analysis
- General Settings for Reporting and Analysis
- Analysis Authorizations: Select Concept
- General Settings for Reporting and Analysis
- Settings for Reporting and Analysis
- Business Intelligence
- SAP NetWeaver
- SAP Customizing Implementation Guide
- If you want to use any navigational attribute in authorization then it has to be authorization relevant in master data infoobject as shown in following screen.
- Go to t-code RSECADMIN
- Select Maintenance button
- Maintain Authorization : Initial Screen will appear.
- Enter the technical name of authorization object to be created.
- Click on Create Authorization (F5)
- Maintain Authorizations : Create screen will appear with message in status bar 'Special Characteristics Missing'.
- Why these special chars are required, see what SAP has to say about it
- Fill up short, medium & long text fields.
- Click on the button 'Insert Special Charact.' as shown below.
- Following objects with default selection will get added.
- Further, get the list of all the 'Infoproviders' you want to add in this authorization object.
- Each infoprovider has set of 'Authorization Relevant Infoobjects', all of them have to be added.
- Check one by one infoprovider for the 'Authorization Relevant Infoobjects' as shown below.
- New window will pop-up for Infocube Authorizations.
- You can specify required infoprovider's name directly or can use F4 help to get the name of infoprovider from the list.
- As per the reporting requirement user either
- Insert Aggregation Authorizations: For the Totals in report, aggregation authorization ':' is used.
- Insert Full Authorizations: It will assign '*'.
- Once you specify the name of infoprovider and hit enter, list of all authorization relevant infoobjects, from the given cube/DSO will appear.
- Select all the infoobjects from the list using Select All (F7) and hit enter.
- All the selected objects will get added as shown below.
- Repeat the procedure for all the infoproviders.
- As shown in the above screen shot, all infoobjects have value (*) in the intervals field. If you want to change value for any of the infoobjects, use following steps.
- Use Details button to go to the maintenance screen OR
- Double click the infoobject to reach the maintenance screen.
- In the maintenance screen, 2 options are given.
- Value Authorizations: You can specify single, multiple single or range of values.
- Hierarchy Authorizations: Hierarchy node values can be assigned.
- Value Authrozations.
- 1st column - Including/Excluding : Specify either I or E to include of exclude the assigned value.
- 2nd column - Operator : Specify value from the given list as per your requirement.
- 3rd & 4th column - Technical Character : Here you have to mention values which are required for the authorization.
- Value (*) can be mentioned to assign Full Authorization.
- Use Add/ Delete Rows option to add more single values.
- Whenever single, multiple single or range values are maintained add ( : ) as 1 more row to avoid the summary calculation related errors at runtime.
- Once you are done by assigning all the required values, click on Save button and exit.
- If you make changes in the existing authorization object, on saving it pops up following message
- Select Yes and new changes with old definition will be saved.
- Hierarchy Based Authorization
- To assign hierarchy node go to Hierarchy Authorizations in details of particular infoobject.
- Click on Create button to assign hierarchy node.
- Following window will pop up where you can select the required hierarchy and particular node.
- Click on Select Hierarchy button to open the hierarchy variant screen.
- New window will show the available variants of hierarchy.
- Double click on the required variant and Hierarchy variant name will get populated.
- Now, detail node needs to be selected. Click on Select Node option.
- Select the required node from the list given
- Once the values for Hierarchy & Nodes are selected, you have to set Type of Authorization.
- For Type of Authorization following 4 options are given
- 0 - Only the selected nodes
- 1 - Subtree below nodes
- 2 - Subtree below nodes to Level ( Incl. )
- 3 - Complete hierarchy
- 4 - Subtree below nodes to ( and Incl. ) Level ( Relative )
- Now hit enter and main screen will appear where you can see Hierarchy Node value with type of authorization maintained.
- When you are maintaining hierarchy node value then in the Value Authorizations only ( : ) value needs to be maintained to avoid the error at runtime.
- Save the authorization object.
Subscribe to:
Posts (Atom)