SAP BI - What are the Setup Tables?
The Setup Tables are the objects from which the Business Warehouse system is going to extract data for Full loads and Initialization on LO DataSources.
When a Full extraction or a Delta Initialization is going to be performed, the Setup Tables need to be filled with all the historical data to be loaded to the Business Warehouse system. This ensures the extractors won't need to access the always busy application tables (like EKKO or VBAK).
Their content can be deleted any time, without affecting the R/3 transaction data. In fact, after the full/Init load has been performed, it is highly likely that the information contained in the Setup Tables is already not up-to-date anymore. Therefore, it would be no harm at all to delete their content. You may think of it as a "PSA" on the R/3 side.
If the load performed was an Initialization, the next records to be extracted will be sent to the Delta Queues.
Customizing Cockpit: Managing delta queues when structure changes
Overview
As we know the Logistics Customizing Cockpit enables you to enhance the Datasources of the logistics listed there from a pool of predefined fields and before changing the extract structures in Customizing cockpit (transaction LBWE).
We must carry out several tasks to avoid inconsistencies into the system because when you change a DataSource or their extract structure, the data that is saved in the old form of the structure is no longer interpreted correctly.
This guide will give you some steps to help you to avoid inconsistencies problems.
http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/18676
What is the difference between outer join and inner join ?
You use INNER JOIN to return all rows from both tables where there is a match. i.e. in the resulting table all the rows and columns will have values.
In OUTER JOIN the resulting table may have empty columns. Outer join may be either LEFT or RIGHT
LEFT OUTER JOIN returns all the rows from the first table, even if there are no matches in the second table.
RIGHT OUTER JOIN returns all the rows from the second table, even if there are no matches in the first table.
Your comments and experiences about the contents are very welcome.
Maintenance of Characteristic contains invalid data (Special Character or Hexadecimal Character)
It happens many times that data load to BI objects got failed due bad data issue. We can resolved it temporarily by modifying the data at PSA and upload the same upward. But it is not a good practice and we can not have the authorization in production system to modify PSA so here are some permanent fix to overcome this issue.
Problem Statement:
When checking valid characters while loading data in BI objects, the system does not determine whether characters HEX00 to HEX1F are contained after you specify string ALL_CAPITAL as the valid character, while Data loading processes may terminate if the invalid characters HEX00 to HEX1F are used in the loaded keys. The system issues error messages BRAIN 060 "Value '&1' (hex.’&3') of characteristic &2 contains invalid characters" or BRAIN 290 "Error while writing master record "&1" of characteristic &2".
Solution:
Problem Statement:
When checking valid characters while loading data in BI objects, the system does not determine whether characters HEX00 to HEX1F are contained after you specify string ALL_CAPITAL as the valid character, while Data loading processes may terminate if the invalid characters HEX00 to HEX1F are used in the loaded keys. The system issues error messages BRAIN 060 "Value '&1' (hex.’&3') of characteristic &2 contains invalid characters" or BRAIN 290 "Error while writing master record "&1" of characteristic &2".
Solution:
1. Enter string ALL_CAPITAL_PLUS_HEX in the maintenance of allowed supplementary
characters.
characters.
2. If above solution does not resolve the problem
Enter the special character in RSKC
3. If both of the above solutions do not resolve the problem write a cleansing routine in the
transformation for these characteristics.
Sample cleansing routine:
DATA : l_allow_char TYPE rsallowedchar-allowchar.
data: l_length type I,
l_act type i.
data l_txz01(40) type c.
if l_allow_char is initial.
CALL FUNCTION 'RSKC_ALLOWED_CHAR_GET'
IMPORTING
e_allowed_char = l_allow_char
EXCEPTIONS
OTHERS = 1.
endif.
l_txz01 = SOURCE_FIELDS-text. “In place of text use the Source Field from which object is mapping
DATA : l_allow_char TYPE rsallowedchar-allowchar.
data: l_length type I,
l_act type i.
data l_txz01(40) type c.
if l_allow_char is initial.
CALL FUNCTION 'RSKC_ALLOWED_CHAR_GET'
IMPORTING
e_allowed_char = l_allow_char
EXCEPTIONS
OTHERS = 1.
endif.
l_txz01 = SOURCE_FIELDS-text. “In place of text use the Source Field from which object is mapping
TRANSLATE l_txz01 TO UPPER CASE.
if l_txz01 co l_allow_char.
RESULT = l_txz01.
Condense RESULT.
else.
l_length = strlen( l_txz01 ).
l_act = 0.
do l_length times.
if l_txz01+l_act(1) na l_allow_char.
l_txz01+l_act(1) = space.
endif.
l_act = l_act + 1.
enddo.
RESULT = l_txz01.
condense RESULT.
endif.
This code will capture all the Special Character maintained into RSKC. It will check whether the
character is available into RSKC if it not matched then it will replace all special or invalid
character with space.
Your comments and experiences about the contents are very welcome.
Download SAP Crystal Presentation Design 2008
CNET Editor's Note: SAP Crystal Presentation Design 2008 (a $195 value) is completely free when activated before 12/31/2010.
Publisher's description
From SAP:SAP Crystal Presentation Design--formerly known as Xcelsius Present software--is a point-and-click data visualization software solution designed to create flash-based interactive data presentations from ordinary spreadsheets and share them via Microsoft Office and Adobe PDF. Product benefits: Create professional-looking presentations in just a few minutes; transform rows of data into interactive charts, maps; make informed decisions by exploring what-if scenarios; engage, inform, and persuade your audience with stunning visualizations. Get started instantly with more than 50 pre-built analytics and an assortment of layout templates.
SAP Business Objects - Xcelsius Dashboard Samples
Xcelcius Dashboard
 |
| Click on Image to see the Xcelcius Dashboard Samples |
By clicking on the above image it will show the SAP Business Objects - Xcelcius Dashboard samples from Inverra (external link) . For looking the preview of sample you have to select any one sample and click on the launch .
Business Objects Voyager
Voyager is a web-based OLAP client with and advanced & highly intuitive user interface based on WEB 2.0 (Ajax) technology
Where can Voyager add value?
- Multiple connections to multiple OLAP Servers (NetWeaver
BI/BW, MSAS, Essbase, IBM DB2)
- Multiple pages in a workspace
- Capable of standard OLAP navigation
- Business calculations: % diff, % cont, variance…
- Advanced charting engine with new chart capabilities especially designed for OLAP analysis
- Time based calculations: Prior Period, YTD, QTD, MA…
- Filter, sort, ranking – top / bottom, by value by %
Why it is required?
- Tool designed for business analysts analyzing OLAP data & end users reviewing OLAP data
- Open data Access
- Access and analyze multiple OLAP sources in the one workspace
- Multiple views of the same OLAP cube in the one workspace
- Tight integration into MS PowerPoint & Word
SAP Connectivity
- Direct Access to SAP NetWeaver BI Queries & InfoCubes via XMLA
Business Objects Web Intelligence
Where can Web Intelligence add value?
- In the area of ad-hoc reporting
- Easy-to-use interface for end user reporting
- Powerful query features
- Leverage business friendly ‘semantic layer’ to hide complexity
Why it is required?
- Self-service reporting and analysis, autonomy from IT
- Simple user interface, designed for the masses
- Combine data from SAP and non-SAP data in a single report
- Rich feature set
Connectivity to SAP
- Sits on top of Business Objects Enterprise Universes
- Universes connect to SAP NetWeaver BI via OLAP BAPI
- Access objects: BEx Queries & SAP BI InfoCubes
Live Office – MS Office Integration
Live Office allows the deployment and access of BI reports & dashboards within Microsoft Office PowerPoint , Word & Excel
Where can Live Office add value?
- Live Office integrates refreshable BI data within documents,
spreadsheets, and presentations.
- The result is an Office document you can share with others
for secure, collaborative decision- making.
- Using intuitive wizards and toolbars, easily connect to and
select data from a Crystal Report or Web Intelligence doc.
- Once the data is placed into your MS document, you can
format, reorganize, and perform calculations—all while using
familiar features in Microsoft Word, PowerPoint, and Excel.
Why it is required?
- Seamless integration of BI into Microsoft Office
- Easy self-service & sharing of BI data embedded into
Advanced Data Visualization with Xcelsius
Xcelsius is an environment to design and consume highly interactive, flash-based dashboards in PDF, documents, presentations and NetWeaver Portal , PDF, documents, and presentations
- In the area of data visualization
- Intuitive design environment, enabling you to easily create
professional -looking models quickly using skins, maps,
charts, gauges, and selectors.
- Add visualization to Crystal Reports
- End user personalization
Why it is required?
- Fast to deploy dashboards on SAP and/or non-SAP data
- Empower Business Users who are not savvy using analysis tools
- Simplify BI information with innovative & intuitive visuals
SAP Connectivity
- Via Live Office Crystal Reports can be connected to Xcelsius
- Via Query as a Web Service (QaaWS) which leverages Business Objects Universes
Enterprise Reporting with Crystal Reports
Where does Crystal Reports add value?
- In the area of highly formatted reporting
- Such as management reports or legal reports - It enables the creation & modification of formatted reports:
- On top of SAP NetWeaver BI
- Leveraging the solid data warehousing foundation
- Report off of all sources of information in your organization
Why it is Required?
- Highly formatted management reports
- Professional report layout (one-to-many approach)
- Operational and tactical applications with low interaction rate (view static & parameterized reports)
- Professional report layout (one-to-many approach)
- Operational and tactical applications with low interaction rate (view static & parameterized reports)
- Form-based, print-optimized reports
- Develop powerful data mash-ups
Connectivity to SAP Applications and NetWeaver BI
- InfoSet/ABAP Query Driver – Access SAP BI InfoSets.
- Open SQL Driver - Access ODS Objects
- NetWeaver BI OLAP Kit
- Connect to multidimensional SAP NetWeaver BI InfoCubes & BEx Queries.
- Develop powerful data mash-ups
Connectivity to SAP Applications and NetWeaver BI
- InfoSet/ABAP Query Driver – Access SAP BI InfoSets.
- Open SQL Driver - Access ODS Objects
- NetWeaver BI OLAP Kit
- Connect to multidimensional SAP NetWeaver BI InfoCubes & BEx Queries.
MultiProvider
A MultiProvider is a special InfoProvider that combines data from several InfoProviders, providing it for reporting. The MultiProvider itself (InfoSets and VirtualProviders) does not contain any data. Its data comes exclusively from the InfoProviders on which it is based. A MultiProvider can be made up of various combinations of the following InfoProviders:
. InfoCubes
. DataStore objects
. InfoObjects
. InfoSets
. Aggregation levels (slices of a InfoCube to support BI Integrated Planning)
Use
A BEx query can only be written against a single InfoProvider. A MultiProvider is a single InfoProvider to a query but through it, multiple providers can be indirectly accessed.
Data Store Objects
Since a DataStore object is designed like a table, it contains key fields (document number and item, for example) and data fields. Data fields can not only be key figures but also character fields (order status, customer, or time, for example). You can use a delta update to update DataStore object data into connected InfoCubes or into additional DataStore objects or master data tables (attributes or texts) in the same system or in different systems. In contrast to multidimensional DataStores for InfoCubes, data in DataStore objects is stored in flat, transparent database tables. Fact and dimension tables are not created.
With DataStore objects, you can not only update key figures cumulatively, as with InfoCubes, but also overwrite data fields. This is especially important for transaction-level documents that change in the source system. Here, document changes not only involve numerical fields, such as order quantities, but also non-numerical ones such as ship-to parties, delivery date, and status. Since the OLTP system overwrites these records when changes occur, DataStore objects must often be moceled to overwrite the corresponding fields and update to the current value in BI.
DS Oject Types
SAP BI distinguishes between three DataStore object types: Standard, Write Optimized, and Direct Update. These three flavors of DataStore Objects are shown in the following figure.
1. The Standard DataStore Object consists of three tables (activation queue, active data table, and change log). It is completely integrated in the staging process. In other words, data can be loaded into and out of the DataStore Objects during the staging process. Using a change log means that all changes are also written and are available as delta uploads for connected data targets.
Architecture and Functions of Standard DataStore Objects
Architecture and Functions of Standard DataStore Objects
Standard DataStore objects consist of three tables:
Active Data table
This is where the current status of the data is stored. This table contains a semantic (business-related) key that can be defined by the modeler (order number, item, or schedule line, for example). It is very important that the key be correctly defined by the modeler, as a match on the key initiates special delta processing during the activation phase (discussed later). Also, reporting via the BEx uses this table.
Change Log table
During the activation run, changes are stored in the change log. Here, you can find the complete history of the changes, since the content of the change log is not automatically deleted. The connected targets are updated from the change log if they are supplied with data from the DataStore object in the delta method. The change log is a PSA table and can also be maintained in the PSA tree of the Data Warehousing Workbench. The change log has a technical key consisting of a request, data package, and data record number.
Activation Queue table
During the DTP, the records are first written to this table. This step is necessary due to the complex logic that is then required by the activation process.
Schema for a Standard DataStore Objects
2. Write optimized is a new kind of DataStore Object . It is targeted for the warehouse level of the architecture, and has the advantage of quicker loads.
3. A direct update DataStore object (previous 3.x transactional ODS) has only the table with active data. This means it is not as easily integrated in the staging process. Instead, this DataStore object type is filled using APIs and can be read via a BAPI.
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
What is Xcelsius
Xcelsius bridges the gap between data analysis and data presentation, converting spreadsheet tables into interactive dashboards.
It is a data visualization design tool that displays summary-level business data in a visually rich and intuitive format that allows users to analyze and interact with their data in order to make better business decisions
