InfoCube
Info Cube is structured as Star Schema (extended) where a fact table is surrounded by different dim table that are linked with DIM'ids. And the data wise, you will have aggregated data in the cubes.
Infocube contains maximum 16(3 are sap defines and 13 are customer defined) dimensions and minimum 4(3 Sap defined and 1 customer defined) dimensions with maximum 233 key figures and 248 characteristic.
The following InfoCube types exist in BI:
. InfoCubes
. VirtualProvidersThere are two subtypes of InfoCubes: Standard, and Real-Time. Although both have an extended star schema design, Real-Time InfoCubes (previously called Transactional InfoCubes) are optimized for direct update, and do not need to use the ETL process. Real-Time InfoCubes are almost exclusively used in the BI Integrated Planning tool set. All BI InfoCubes consists of a quantity of relational tables arranged together in a star schema.
Star Schema
In Star Schema model, Fact table is surrounded by dimensional tables. Fact table is usually very large, that means it contains millions to billions of records. On the other hand dimensional tables are very small. Hence they contain a few thousands to few million records. In practice, Fact table holds transactional data and dimensional table holds master data.
The dimensional tables are specific to a fact table. This means that dimensional tables are not shared to across other fact tables. When other fact table such as a product needs the same product dimension data another dimension table that is specific to a new fact table is needed.
This situation creates data management problems such as master data redundancy because the very same product is duplicated in several dimensional tables instead of sharing from one single master data table. This problem can be solved in extended star schema.
Extended star schema
In Extended Star Schema, under the BW star schema model, the dimension table does not contain master data. But it is stored externally in the master data tables (texts, attributes, hierarchies).
The characteristic in the dimensional table points to the relevant master data by the use of SID table. The SID table points to characteristics attribute texts and hierarchies.
This multistep navigational task adds extra overhead when executing a query. However the benefit of this model is that all fact tables (info cubes) share common master data tables between several info cubes.
Moreover the SID table concept allows users to implement multi languages and multi hierarchy OLAP environments. And also it supports slowly changing dimension.
Useful t-codes For SAP BI
| Used ECC side | |
| RSA2 | Used to display all the details of a DataSource |
| RSA3 | This is Extractor Checker, we can check the data of any |
| DataSource at ECC side using this tcode. | |
| RSA5 | This tcode is used to activate the Standard DataSources |
| RSA6 | By using this tcode we can see all the activated Data Sources |
| and also we can enhance the DataSource by adding new fields | |
| RSA7 | Used to display the delta Queues |
| RSO2 | Used to create and display the Custom DataSources |
| LBWE | Customize LO Datasources |
| LBWQ | Used to manage the logistic Delta queues. |
| LBWG | Used to delete the logistic setup tables. |
| SBIW | BIW in IMG for OLTP |
| SMQ1 | Used to check the queued data for delta |
| SM37 | Used to monitor the Background jobs |
| SE38 | Used to Create, edit and Display the ABAP programs |
| SE16 | Used to see the data of database tables |
| SE11 | Used to create and display Structures, Views and Tables |
| SM58 | Used to Manage the Transactional RFCs |
| SE37 | Used to create and display Function Modules. |
| SE80 | Object Navigator |
| SE10 | Transport Organizer |
| CMOD | Project management of SAP enhancements |
| SMOD | SAP enhancements for a Datasource |
| ST05 | Performance Analysis |
| Used BI Side | |
| RSA1 | Data Warehousing Workbench Modeling |
| RSKC | Used to maintenance of the permitted extra characters in BW |
| RSBBS | Maintaining BW SenderReceiver |
| RSPC | Used to create or monitor the Process Chains |
| RSPC1 | Used to Maintain Process Chain(One Chain) |
| RSZC | Use to copy the query from one InfoProvider to other InfoProvider |
| RSPCM | Used to monitor the Process Chains |
| RSRT2 | Start of the Report Monitor |
| RSANWB | Analysis Process Designer |
| RSPLAN | Modeling BI Integrated Planning |
| RSCUR | StartCurrency Translation Type |
| RSMO | Data Load Monitor Start |
| RSRV | Analysis and Repair of BW Objects |
| RSSM | Authorizations for Reporting |
| RSSMQ | Start Query with User |
| BD87 | Used for idoc |
| SBIW | BIW in IMG for OLTP |
| LISTCUBE | Used to display the content of InfoProvider |
| SE10 | Transport Organizer |
| CMOD | Project management of SAP enhancements |
| SMOD | SAP enhancements for a customer exit variables |
| SE11 | Used to create and display Structures, Views and Tables |
| SM12 | Unlock the locked Objects |
| SM59 | Configuration or RFC connections |
| SM37 | Used to monitor the Background jobs |
| DB02 | Database performanceTables & Indexes |
| ST22 | Used to check the ABAP run time error |
| AL11 | Used to Create or Display SAP Directories |
| FILE | Change view “Logical file path Definition” Overview |
| RSSMTRACE | Reporting Log Authorization |
| RSECADMIN | Used to maintain the BISecurity |
| RSZDELETE | Used to Deletion of query objects |
| RSBBS_WEB | Transaction for the RRI in the Web |
Note: The above mention T-codes are most commonly used t-codes if you want to search more t-code you may use t-code SE93.
Virtual Provider( Remote Cube)
VirtualProviders represent a logical view. Unlike Info-Cubes, data is not stored physically in BI. Only the data is taken from the Source System as query executed. You use this Virtual-Provider if you want to display data from non-BI data sources in BI without having to copy the data set into the BI structures. The data can be local or remote.
Following are the three type of Virtual Provider.
. Based on DTP for Direct Access
The Direct Access (DTP-filled) Virtual-Provider allows you to define queries
With direct access to transaction or master data in other source systems.
. Based on a BAPI
The BAPI-based option allows reporting using data from non-SAP systems.
The external system transfers the requested data to the OLAP processor
via the BAPI.
. Based on a Function Module
Function-Module-Based Virtual-Provider supplies a clean interface to
allow your custom code to be the source data. It is a very flexible way to
populate a Virtual-Provider.
 |
These options are shown in the creation GUI for Virtual-Providers |
Xcelsius Beginners Guide Part 1
This video is for how to display data from your Excel Spreadsheet in a Pie Chart.
You can use any kind of chart but for this example we are using a pie chart.
You can use any kind of chart but for this example we are using a pie chart.
Getting Started with SAP Crystal Presentation Design
SAP Crystal Presentation Design – formerly known as Xcelsius Present software – is a point-and-click data visualization software designed to create flash-based interactive data presentations from ordinary spreadsheets – and share them via Microsoft Office and Adobe PDF.
 |
Differences between Multiprovider and Infoset
Multi-ProviderMulti-Provider is used to Union two or more data-targets, so that we can run query on different data-targets. It also helps us to execute parallel queries.A Multi-Provider can consist of different combinations of the following Info-Providers: Info-Cube, Data-Store object, Info-Object, Info-Set, Virtual-Provider, and aggregation level.
Info-SetsInfo-Sets is used to joins two or more data targets. These joins only combine values that appear in both tables. In contrast to a union, joins form the intersection of the tablesA Info-Sets can consist of different combinations of the following Info-Providers: Info-Cube, Data-Store object and Info-Object.
Differeces Between DSO and InfoCube
The main difference in Reporting from Info cube and ODS/DSO is that InfoCube is meant for Multi-Dimensional reporting while ODS/DSO reporting is like 2 dimensional reporting.
There are many points which will clearly state that reporting from Info cube is far better than that from DSO.
Some major differences:DSO
- Detailed form of data
- Flat file formate structure
- Two dimentional
- Performance is less as compared to cube
- Overwrite data functionality
InfoCube
- Summerised form of data
- Star schema
- 16 dimentional
- Additive data functionality
- Performance is better as compared to ods
InfoCube is prepared to visualize aggregation data and with the star schema relational tables, the data is accessed in better ways in terms of performance.
So if you use report in DSO performance is very slow compared to performance in InfoCubes.
Also chk this link:http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/b04a79b4-bbea-2b10-da86-bf0fe933fe34&overridelayout=true
