No. of times a BEx report executed by a User

If you want a report for No. of times a BEx report executed by a User? Then here is a way to do that.

Our BW systems may have many reports. After sometime some reports lose their importance but it remains in system unnecessarily. To figure out those queries there is a work around. It’s better to create a Report for no. of times a BEx report executed by a user in a period of time. In this blog I am showing how to bring such information into BW reports.

Read more at : http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/27383

Repeat Delta Elucidate From OLTP to BW System

Repeat Delta Elucidate From OLTP to BW System

In some business process data loading will be conducted on hourly bases through Timestamp Field, are often required as delta criteria for generic delta extraction. However, in many tables such the timestamp field is not available; instead the creation/change date and time are available. Generic delta needs to function on one field. This article explains how exactly request are processed BW system to at OLPT server and what are the dependent fields are interlinked to fill the TIMESTAMP field on runtime extractor.

Read further at ...http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/26717

Dynamic Attachment using Simple Transformation

Dynamic Attachment using Simple Transformation

The main focus of this article is not about sending mails when a work item is created, currently the main focus of this article would be to creating an attachment dynamically. The attachment can be a .DOC, .XLS, .PDF, .XML.

The term dynamic here refers to the data and content that are populated during the workflow execution that can be either populated in the workflow container or work item container. This article specifically deals with creating a excel sheet and it can be extended to such an extent where you can even populate list values inside the generated excel sheet.

Ok…… let me say you how it can be done in simple 3 steps.

1. Create a Business Class by including IF_WORKFLOW interface in the class.
2. Create a Simple Transformation,to populate the values in the excel sheet call the transformation from a method created in the business class.
3. Create a Standard task and include the new business class and method name and define the proper binding and finally include this task in a workflow.

Read here further... Link : http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/26428

Program to Activate Transformation & DTP

Program to Activate Transformation & DTP

OVERVIEW

This paper provides a code which can be used to activate inactive Transformation's and DTP's. SAP has provided various programs for activating info-providers, transfer rules, etc but these two programs were missing from the standard set of programs.

Link : http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/d02513b2-7fb6-2c10-3a8b-887fc115d61b

PDF Download : http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/d02513b2-7fb6-2c10-3a8b-887fc115d61b&overridelayout=true

How to save your Listcube selction screen and the output.

How to save your Listcube selction screen and the output.

Just found an quick information in SAP BI from LISTCUBE tcode so thought of sharing the same across others because I suspect only very very few make use of this .

Have you ever thought of how to save selection screen and output fields in tcode LISTCUBE? If not below are the steps to be followed to make use of it.

Advantages:

• This will help in reusability like avoiding the LISTCUBE tcode again and again for the same selections.
• This will also helps you to reduce certain amount of your manual work.

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

How to Fetch Your Infopackage Details From R/3 System.

How to Fetch Your Infopackage Details From R/3 System.

Sharing a small piece of code which help you a lot in indentifying the BW system or Info package details at R/3 system while you write your custom code in CMOD at data source level. This code will help you in following below situations.

1) Remote Function Call: If you need to call Function Module written in BW system from R/3 system for any manual manipulation.

2) To Identify BW Load request details at CMOD code Level.

3) When a R/3 system is connected to Couple of BW system.

4) From one R/3 system when the data has to be sent differently for same data source to two different BW systems at CMOD level.

Read more at : http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/26901

The BW - HANA Relationship

The BW - HANA Relationship

With the announcement of HANA*, some customers, analysts and others have raised the question on how HANA relates to BW with a few of them even adding their own, home made answer in the sense that they speculate that HANA would succeed BW. In this blog, I like to throw in some food for thought on this.

Currently, HANA's predominant value propositions are

• (i) extremely good performance for any type of workload

• (ii) a real-time replication mechanism between an operational system (like SAP ERP) and HANA

Read more on SDN : http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/21575

Learn your BW in hard way

Useful information about BW system is spread into several tables in the system as itself.

That’s usual case. Skilled BW guy knows where to look in order to lookup information that is needed. It is common to know basic tables with IOs (RSDIOBJ), reports (RSRREPDIR), cubes (RSDCUBE), DSOs (RSDODSO), process chains (RSPCCHAIN) etc.

More technical BW guy would also know where to find information about basic BW system settings (tables RSADMINA, RSADMINS, RSBASIDOC, etc.).

To Read more : go to link below.

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

Demystifying aggregates in SAP BI 7.0

Demystifying aggregates in SAP BI 7.0

Demystifying aggregates in SAP BI 7.0

Aggregates are subsets of InfoCube data, where the data is pre-aggregated and stored in a InfoCube structure. Aggregates on an Info Cube can be considered similar to that of an Index on a database table. Creating an Aggregate on an InfoCube is one of the few ways to improve performance of SAP BW Query. Subset of an InfoCube data is stored in an Aggregate. As a result, the response time that we get out of reading the data from aggregate will be much faster than reading from an InfoCube.

Read more @ http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/26054

SAP BI Statistics Installation

SAP BI Statistics Installation

This blog shares author's personal experience during installation of "Standard BI statistics" on  BW system ; it is already provided by SAP as a standard content for analyzing performance of different cubes,reports in the system.

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

How To Collect a Variant and ABAP Program in a Transport

How To Collect a Variant and ABAP Program in a Transport (BI - Process Chain)

Business Scenario

"Sometimes, you would need to collect a variant of an ABAP program and transport across systems (D/Q/P)."

Details:

You wish to have an automatic ticketing mechanism in which each process chain failure will generate a ticket ( in our case it's Remedy) and thus the efforts are tracked. So in each of your process chain's you want to check the failure(s) and intimate to the Firefighting team.

To achieve this you have setup a custom program step (in all chains) to generate a message with complete details of failure and you would want this program to get executed with a predefined variant across all boxes (DEV/QAS/PRD).

For this to happen, you may want to transport the variant along with the program step. Variants are not automatically collected in transports as we build them, nor when we drag a process chain into transport manager (even when using the before and after setting).

To read more... go to the original blog @ http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/26516

The Diary of a BW 7.3 Ramp-Up project (Part 5)

SAP Network Blog: The Diary of a BW 7.3 Ramp-Up project (Part 5)

Part 1 : http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/23859

Part 2 : http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/24869

Part 3 : http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/25066

Part 4 : http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/25629

Part 5 : http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/26033

Link to this last part : http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/26498

ABAP on Steroids: practical use of parallel processing

SAP Network Blog: ABAP on Steroids: practical use of parallel processing

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

We've all been there, in the trenches, struggling with that long-running ABAP report that seemingly takes hours to complete. Year-end reporting, Financial analysis, Sales reports... you've exhausted the options of using alternative indexes for BSEG (BSIK, BSID, other BS* tables), the customer is screaming at the top of his lungs, but no matter what you do, that darned report just takes too long. And you haven't even released it to Q yet...

Intro

Parallel processing is not a new concept, but one that is regularly overlooked when it comes to increasing ABAP performance. Why?

Your SAP system will (normally) have more than one process available at any given time. Still, most of us insist on using just one of them. This is a bit like a manufacturer relying on only one truck to bring the products from his plant to the shopping malls, when there's a whole fleet of trucks just standing by!

Not only that, but most SAP systems spans more than one application server, each with a range of (hopefully) available processes. So, what are we waiting for?

So Read more on the blog.

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

With the advent of HANA, SAP BW is endangered species? - Part -I

With the advent of HANA, SAP BW is endangered species? - Part -I

via SAP Developer Network SAP Weblogs by Agrawal Vikash on 4/21/11

I happen to check latest 'SAP BI Platform with HANA' and found that BW is replaced by HANA. Next thought cross my mind was...With the advent of HANA, SAP BW is endangered species?

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