0% found this document useful (0 votes)
151 views2 pages

What Is InfoProvider in BW

Infoproviders are objects that provide information to other objects in SAP BW. There are three main types of infoproviders: InfoObjects which are basic building blocks, DSOs which store granular data, and InfoCubes which store aggregated data. Infosources are intermediate layers between a source and destination that don't store data themselves, but are used to join transformations when loading data sequentially without storing it again or for complexity reasons.

Uploaded by

Qassam_Best
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
151 views2 pages

What Is InfoProvider in BW

Infoproviders are objects that provide information to other objects in SAP BW. There are three main types of infoproviders: InfoObjects which are basic building blocks, DSOs which store granular data, and InfoCubes which store aggregated data. Infosources are intermediate layers between a source and destination that don't store data themselves, but are used to join transformations when loading data sequentially without storing it again or for complexity reasons.

Uploaded by

Qassam_Best
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

What is InfoProvider in BW?

Info Provider is a general term used to denote the data targets into which the data is loaded
physically or virtually in SAP BW.

There are different type of Info Providers in SAP BW -

1. Info Cube
Types : a. Standard Info cube and b. Real Time Info Cube store the data physically.
c. Virtual Info cube holds the data virtually and data is not loaded physically.

2. DSO (Data Store Objects)


Types : a. Standard b. Write- optimized c. Direct update DSOs hold the data physically and
used in different scenarios.

3. Info object as Info providers


Info objects are small entities and it is like a fields in the ABAP table.
If an Info object has its attributes, its a Master data. The Master data is loaded to the table
physically and so the Info object here is a Info provider.

Info Provider essentially means which provides Information. Basically there are
three types of Info Provider in BW which hold data physically

1. InfoObjects - Basic building block


2. DSO - Store granular data
3. Cube - To store aggregated data

Infoproviders are nothing but the the objects which provide information to next level
objects. These infoproviders in BW can be Infocubes, DSO(Write-Optimised &
Standard), infoset, multiproviders. We use DTP and transformations to transfer the
data.
What is infosource in SAP BW?

A non-persistent structure consisting of InfoObjects for joining two transformations.

You can use InfoSources to run two or more sequential transformations in the data
flow without storing the data again.

If you do not have transformations that run sequentially, you can model the data flow
without InfoSources. In this case, the data is written straight to the target from the
source using a transformation.

However, it may be necessary to use one or more InfoSources for semantic or


complexity reasons.

Infosource is just an intermediate layer between a source and a destination. It doesnt


hold data. It is used in 3.X flows. It’s optional from 7.0 onward and i have never
created them during development except in scenarios when i have activated standard
BI content and infosource exists in the flow.

It is also used if you want to apply same logic to more than 1 target extracting data
from same datasource.

For example. You have a infoobject XYZ in datasource and you have multiple DSO’s
getting data from this datasource and you have requirement of deriving a perticular
value for Field PQR present in those DSO’s, which depends on value of XYZ then you
will create a infosource and then create a transformation between the infosource and
datasource. In that transformation you will write a start routine or some other
routine as per requirement to derive the value of PQR.

Then you will create transformations between the infosource and DSO.with direct
mapping between PQR of infosource and dso.
So you dont have to write the routine n number of times instead writing only once
will suffice and also may contribute in improving performance of data load.

You might also like