8/10/2019 BI 7.0 Important Docu

http://slidepdf.com/reader/full/bi-70-important-docu 1/5

Infosources are no more mandatory with BI 7.0, below is the link to scenarios where we useinfosources:http://help.sap.com/saphelp_nw04s/helpdata/en/44/0 4!dd"ae#$0!ae#0000000a#%%!f$/content.htm

Below are the basic steps which we follow in any BI 004& system:#'(reate datasource. )ere u can set/check the &oucre &ystem fields.

'(reate *ransformation for that datasource. +no more update rules/transfer rules'.#' hile creatin- transformation for & it will ask you for data tar-et name, so ust assi-n where

u want to update ur data.

ata&ource 1 *ransformation 1 ata *ar-et

2ow if you want to load data into data tar-et from &ource &ystem atasource:#' (reate infopacka-e for that data source. If you are creatin- infopacka-e for new datasources,it will only allow you update upto 3& , all other options u can see as disabled.

'2ow (reate *3 + ata *ransfer 3rocess' for that data source.

!' 25w schdule the Infopacka-e, once the data is loaded to 3& , you can e6ecute your *3which will load data to data tar-et.

If you are loadin- data from one one data tar-et to other, no need to use 3& , you can directlye6ecute *3 in that case.

ata &ource 1 *ransformation +I3/ *3' 1 ata *ar-et# 1 *3 1 ata *ar-et

se the below link for detailed e6ample:https://www.sdn.sap.com/ir /ser8let/prt/portal/prtroot/docs/library/uuid/fc$#e# d 0a0# 00#0 ""!e fc$!ef7 9b

Difference between BW 3.5 and BW 7.0

#. ata odelin- ;low:

a. (reate ata sourceb. (reate Info sourcec. (reate *ransformations b/w data source and info source +earlier it was transfer rules'd. (reate Info 3acka-ee. (reate Info 3ro8ider +info cube or ata &tore 5b ect instead of 5 &'f. (reate *ransfer rules b/w info source and data tar-ets +instead of pdate rules'-. (reate *3 +data transfer process'. *o pull the data from Info packa-e +i.e. from 3& ' to Info3ro8ider.

. ;or elta option in customi<ed cube there is one new feature called = >;ilter no new records?which is present in *3@s of ata &tore 5b ect.

!. In Info sets now you can include Info cubes as well.

4. *he Aemodelin- transaction helps you add new key fi-ure and characteristics and handleshistorical data as well without much hassle. *his is only for info cube.

8/10/2019 BI 7.0 Important Docu

http://slidepdf.com/reader/full/bi-70-important-docu 2/5

%. *he BI accelerator +for now only for info cubes' helps in reducin- uery run time by almost afactor of #0 #00. *his BI accl is a separate bo6 and would cost more. Cendors for these wouldbe )3 or IB .

$. *he monitorin- has been impro8ed with a new portal based cockpit. hich means you wouldneed to ha8e an D3 -uy in your pro ect for implementin- the portalE :'

7. &earch functionality has impro8edEE Fou can search any ob ect. 2ot like !.%

". *ransformations are in and routines are passed E Fes, you can always re8ert to the oldtransactions too.

9. ata *ransfer 3rocess are in. It is used to pull the data from Info packa-e +i.e. from 3& ' toInfo 3ro8ider.

*ry the links -i8en below for further details :

BI 7.0 ocuments:http://help.sap.com/saphelp_erp 00%8p/helpdata/en/e#/"e%#!4#a0$0"4de#0000009b!"f"!b/frameset.htm

https://www.sdn.sap.com/ir /sdn/docsGridH/webcontent/uuid/9 "0fb d 0a0# 00#0 0f"0f!!ab%c#$0$d

(heck this for what s new in 2 004s BI:http://help.sap.com/saphelp_nw 004s/helpdata/en/a4/#be%4#f! #c7#7e#0000000a#%%#0$/content.htm

iff b/w BI 7.0 Cs !.%http://help.sap.com/saphelp_nw 004s/helpdata/en/b /e%0#!"fede0"!de#0000009b!"f"cf/frames

et.htm

ModelingPurpose*he tool you use for modelin- is the ata arehousin- orkbench. ependin- on your analysisand reportin- re uirements, different BI ob ects are a8ailable to you for inte-ratin-, transformin-,consolidatin-, cleanin- up, and storin- data. BI ob ects allow efficient e6traction of data foranalysis and interpretation purposes.

Process Flow*he followin- fi-ure outlines how BI ob ects are inte-rated into the dataflow:

8/10/2019 BI 7.0 Important Docu

http://slidepdf.com/reader/full/bi-70-important-docu 3/5

ata that lo-ically belon-s to-ether is stored in the source system as ata&ources . ata&ourcesare used for e6tractin- data from a source system and transferrin- it into the BI system.*he 3ersistent &ta-in- rea +3& ' in the BI system is the inbound stora-e area for data from thesource systems. *he re uested data is sa8ed, unchan-ed from the source system.

*he transformation specifies how the data +key fi-ures, time characteristics, characteristics' isupdated and transformed from the source, into an Info3ro8ider or Info&ource. *he transformationrules map the fields of the source to at least one Info5b ect in the tar-et. *he information ismapped in structured form usin- the Info5b ects .

Fou need to use an Info&ource if you want to e6ecute two transformations one after the other.&ubse uently, the data can be updated to further Info3ro8iders . *he Info3ro8ider pro8ides thedata that is e8aluated in ueries. Fou can also distribute data to other systems usin- the openhub destination .See also:;or more information about displayin- the data flow for BI ob ects, see ata ;low isplay section.

eco!!endations for "sing #nfoSourcesThis section outlines three scenarios for using InfoSources. The decision to use anInfoSource depends on how the effort involved in maintaining the InfoSource and any

potential changes in the scenario can be minimized.

1. Data Flow Without an InfoSource:The DataSource is connected directly to the target by means of a transformation.

8/10/2019 BI 7.0 Important Docu

http://slidepdf.com/reader/full/bi-70-important-docu 4/5

Since there is only one transformation, performance is better.However, if you want to connect multiple DataSources with the same structure to thetarget, this can result in additional maintenance effort for the transformation, since youneed to create a similar transformation for each DataSource.You can avoid this if the DataSource is the same, it ust appears in different sourcesystems. In this case, you can use source system mapping when you transport to the targetsystem so that only one transformation has to be maintained in the test system. The sametransformation is created automatically for each source system in the production system.

2. Data Flow with One InfoSourceThe DataSource is connected to the target by means of an InfoSource. There is onetransformation between the DataSource and the InfoSource and one transformation

between the InfoSource and the target.

!e recommend that you use an InfoSource if you want to connect a number of differentDataSources to a target and the different DataSources have the same business rules. In thetransformation, you can align the format of the data in DataSource with the format of thedata in the InfoSource. The re"uired business rules are applied in the subse"uenttransformation between the InfoSource and the target. You can ma#e any changes to theserules centrally in this one transformation, as re"uired.

3. Data Flow with Two InfoSources

8/10/2019 BI 7.0 Important Docu

http://slidepdf.com/reader/full/bi-70-important-docu 5/5

!e recommend that you use this type of data flow if your data flow not only contains twodifferent sources, but the data is to be written to multiple identical $or almost identical%targets. The re"uired business rules are e&ecuted in the central transformation so that youonly have to modify the one transformation in order to change the business rules. You canconnect sources and targets that are independent of this transformation.