SAP BW 7.30 : Performance Improvements in Master-Data related scenarios and DTP Processing

SAP BW 7.30 : Performance Improvements in Master-Data related scenarios and DTP Processing

Girish V Kulkarni / Company: SAP / Enterprise Data Warehousing/Business Warehouse

With Data Warehouses around the world growing rapidly every day, the ability of a Data Warehousing solution to handle mass-data, thus allowing for the ever-shrinking time-windows for data loads is fundamental to most systems.

BW 7.3 recognizes the “need of the hour” with several performance related features and in this blog, I will discuss the performance features related to data loads in SAP BW 7.3, focusing mainly on Master Data Loads and DTP Processing.

Here is the list of features discussed addressed in this blog -


Master Data

1. Mass Lookups during Master Data Loads
2. The “Insert-Only” flag for Master Data Loads.
3. The new Master Data Deletion
4. SID Handling
5. Use of Navigational Attributes as source fields in Transformations.

DTP Processing

1. Repackaging small packages into optimal sizes.

Read Full article at link :

SAP Network Blog: SAP BW 7.30 : Performance Improvements in Master-Data related scenarios and DTP Processing

Permanent Link

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

BW 7.3: Troubleshooting Real-Time Data Acquisition

BW 7.3: Troubleshooting Real-Time Data Acquisition Tobias Kuefner / Company: SAP AG Posted in Enterprise Data Warehousing/Business Warehouse

The main advantage of real-time data acquisition (RDA) is that new data is reflected in your BI reports just a few minutes after being entered in your operational systems. RDA therefore supports your business users to make their tactical decisions on a day-by-day basis. The drawback however is that these business users notice much faster when one of their BI reports is not up to date. They might call you then and ask why the document posted 5 minutes ago is not visible yet in reporting. And what do you do now? I’ll show you how BW 7.3 helps you to resolve problems with real-time data acquisition faster than ever before.

First, let’s have a look at what else is new to RDA in BW 7.3. The most powerful extension is definitely the HybridProvider. By using RDA to transfer transactional data into a HybridProvider, you can easily combine the low data latency of RDA with the fast response times of an InfoCube or a BWA index, even for large amounts of data. You’ll find more information about this combination in a separate blog. Additionally. BW 7.3 allows for real-timemaster data acquisition. This means that you can transfer delta records to InfoObject attributes and texts at a frequency of one per minute. And just like RDA directly activates data transferred to a DataStore object, master data transferred to an InfoObject becomes available for BI reporting immediately.

Link

SAP Network Blog: BW 7.3: Troubleshooting Real-Time Data Acquisition

Permanent Link

SAP Network Blog: The new SAP NetWeaver BW 7.30 hierarchy framework

The new SAP NetWeaver BW 7.30 hierarchy framework

Serge Daniel Knapp / Company: SAP Deutschland AG & Co. KG

Introduction

If you remember older releases of SAP NetWeaver BW hierarchies could only be loaded through the old 3.x data flow. In this case you needed the so called direct update functionality of the corresponding InfoSource for uploading the hierarchy. This InfoSource 3.x was connected to an 3.x DataSource through update rules.

Limitations of 3.x data flow for hierarchies

This data flow has to be used in SAP NetWeaver BW 7.x, too, and could not be migrated to the new data flow. Consequently you always had to deal with two types of data flows in your system. Besides the heterogeneous aspect the 3.x data flow for hierarchies had a lot of disadvantages:

First, hierarchy DataSources were available only for flatfile and SAP source systems. Besides, end users could only create own hierarchy DataSources for the flat file system.

Second you could not take full advantage of the new data flow, even some old data flow features (e.g. the start routine) could not be used. Furthermore, to change the structure of hierarchies during runtime you had to implement complex scenarios (e.g. with the help of the analysis process designer APD). The direct update functionality didn't allow you to load the hierarchy to a DSO or an other arbitrary object and manipulate it according to the end users' needs.

Third, monitoring was often unclear because the framework was not optimal for segments.

The new BW 7.30 hierarchy framework

With SAP NetWeaver BW 7.30 the hierarchy framework has been improved, you could now use the 7.x data flow with all its advantages.

First you are able to use any BW object as source for a hierarchy, you are not limited to a DataSource for hierarchies. This leads to simpler scenarios if you want to transform your hierarchy according to your needs. You just have to connect your hierarchy through a transformation and a data transfer process.

Within this transformation you are able to use all features of a transformation, for example start, end or expert routines. You are not limited as you were in the 3.x data flow.

You can use any DataSource as a source for your hierarchy, you are not restricted to hierarchy DataSources any more. This makes hierarchy extraction of SAP source systems possible, too.

Last but not least you are now able to take full advantage of all capabilities of the new data flow. You can distribute the data loaded from one DataSource to several hierarchies and you can use an arbitrary number of InfoSources in between the DataSource and your hierarchy. A very useful feature is the automatic filling of the fields CHILDID, NEXTID and LEVEL through the framework if they are not filled by the source (e.g. if only the PARENTID is provided).

Read the full article here

SAP Network Blog: The new SAP NetWeaver BW 7.30 hierarchy framework

Permanent Link : http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/22167

Maintaining Data Quality in BW using Error Stack

Maintaining Data Quality in BW using Error Stack

via Enterprise Data Warehouse on 8/24/10

This Article explains the different ways in which the incorrect data records can be moved to error stack when the data record is processed in the routines(Start, End, Characteristic or Expert Routines) of Transformation (In this case a data record is marked as incorrect based on Customer-specific requirements or Conditions).

Link to Article : http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/20ebeb43-9e8a-2d10-b28e-825c0142ad4f


Link to PDF: http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/20ebeb43-9e8a-2d10-b28e-825c0142ad4f&overridelayout=true

~~~~~~~~~~~~~~~~~~~~~~~~~~

SAP Network Blog: BW 7.30: Simple supervision of process chains

BW 7.30: Simple supervision of process chains
Thomas Rinneberg / Company: SAP AG
~~~~~~~~~~~~~~~~
There has been some moaning about the built-in capabilities to monitor BW process chains. Clicking one chain after the other to see recent status is just too much effort and transaction RSPCM listing the last execution is lacking supervision with regards to timely execution. In fact for those of you who do not want to use the administrator cockpit, there is no time supervision at all (except the insider tip of transaction ST13 – which however is not contained in standard, but an add-on by SAP active global support).

~~~~~~~~~~~~~~~~
However with release 7.30 BW development has finally catched up – Read the article below.

SAP Network Blog: BW 7.30: Simple supervision of process chains

Permanent Link : http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/20934
~~~~~~~~~~~~~~~~

SAP Network Blog: Performance Improvements for DataStore Objects

Performance Improvements for DataStore Objects
Klaus Kuehnle / Company: SAP AG / Posted on Jan. 19, 2011 03:43 AM / in Enterprise Data Warehousing/Business Warehouse
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
A lot of time and effort has been invested in SAP BW 7.30 to improve the performance of operations on DataStore Objects, such as request activation. The most important improvements are:

database partitioning for DataStore Objects
mass lookups in activation of requests in DataStore Objects
dynamic flag “unique data records”
faster request activation in DataStore Objects on databases with massively parallel processing architecture
lookup into DataStore Objects in transformation

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The following link describe these points in more detail.

SAP Network Blog: Performance Improvements for DataStore Objects

Functional Module Based Delta Enabled Generic Datasource

OVERVIEW
This document explains the process to create Delta enabled Generic Datasource based on Function Module. Here I explained the steps required to use RSAX_BIW_GET_DATA_SIMPLE to create Delta enable Extractor. . Articles explain everything right from the creation of the dummy transparent table to that of enabling Delta of a Datasource. It also describes auxiliary steps like creation of Table Maintenance and TCode creation for direct data entry. If you are looking for the entire steps involved in the creation of Delta Enabled Generic Datasource based on Function Module, this paper will definitely help you doing that.


Functional Module Based Delta Enabled Generic Datasource

Debjit Singha (L & T Infotech) Article (PDF 747 KB) 08 July 2011