Loading

Performance Tuning of Loads where delta is not possible (Pseudo Delta)


Summary:
There are many standard master as well as few transactional data loads in BI which do not support the delta concept. For those load we have to go for full loads daily as the standard data-source misses the delta capability. Many times in generic data-source on tables/views delta not works. These full loads which run daily unnecessarily take a lot of time for processing data thus leading to increase in overall load times. This can be overcome with the concept of Pseudo Delta.

Pseudo Delta:
Pseudo delta can be measured as a customized delta but doing certain modifications to achieve the working concept similar to standard delta. It helps to save the loading efforts and time. This concept can also come useful for DB loads which fairly support delta concept.

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: 
1. Enter string ALL_CAPITAL_PLUS_HEX in the maintenance of allowed supplementary
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

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

Business Objects Web Intelligence is the leading end user reporting-and-analysis tool.

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