INFOSOURCE IN SAP BI PDF

I am little bit confuse about the use of infosource[in rsa1],because without using it we can perform extraction. Actually, it is still necessary if you want to keep your datasources as 3. In BW 7, they can be used to to structure your data flow: - making two transformations instead of one. Suppose you want to perform transformation Say T1 on data present in different data sources PSA , then you can perform transformations T1 on data present in all sources and accumulate data structure in Infosource.

Author:Vudosho Moogurr
Country:Croatia
Language:English (Spanish)
Genre:Environment
Published (Last):8 December 2008
Pages:178
PDF File Size:8.75 Mb
ePub File Size:7.2 Mb
ISBN:419-3-59664-721-7
Downloads:16653
Price:Free* [*Free Regsitration Required]
Uploader:Tesida



A structure consisting of InfoObjects without persistence for connecting two transformations. You always use an InfoSource when you want to perform two or more transformations consecutively in the data flow - without additional storage of the data. If you do not need two consecutive transformations, you can model the data flow without an InfoSource. A transformation is used to write data from the source to the target.

It might be necessary to use one or more InfoSources however due to semantic reasons or the level of complexity. For example, you can specify the format and assignment to InfoObjects in the first transformation.

The actual business rules can be performed in the next transformation. If the rules are very complex and interrelated, it might be advisable to use more than one InfoSource. More information: Recommendations on Using InfoSources. A transformation is always used to update the data in an InfoSource to an InfoProvider.

You can mark the InfoObjects of the InfoSource as keys. This function is provided for special situations. You should check whether the result really is the one you want.

The way keys are used in InfoSources depends on integration into the corresponding load scenario. If keys are used in an InfoSource, the incoming data is aggregated in relation to this key.

It is very important here for this key definition to be compatible with the load scenario by using this InfoSource. The InfoSource key must have at least the same granularity as the connected InfoProvider. It is important here to be aware of complex transformations that could change the values in the key fields. If the data target has key characteristics A and B, and characteristics A, B and C can be selected as keys in the corresponding InfoSource, at least characteristics A and B must be selected as keys in the InfoSource.

In complex transformation scenarios, deriving a compatible key definition from the InfoSource might be different, or even impossible. If this option is selcted, the corresponding transformation in the aggregration behaves in the same way as a DataStore object, in accordance with the keys in the InfoSource. If you are using an InfoSource with a key for loading to a DataStore object, you have to select this option in order to guarantee consistent processing of before, reverse and delete images during aggregation.

Create the data transfer process from the DataSource to the InfoProvider. Since the InfoSozrce is not a persistent data store, it cannot be used as a target for a data transfer process. Create each transformation on the InfoProvider as a target with the InfoSource as a source and on the InfoSource as a target with the DataSource as a source.

Example Example of a simple assignment: If the data target has key characteristics A and B, and characteristics A, B and C can be selected as keys in the corresponding InfoSource, at least characteristics A and B must be selected as keys in the InfoSource. The following graphic shows how the InfoSource is integrated into the dataflow:.

IBM R61I PDF

PowerExchange for SAP NetWeaver User Guide

They serve to stage consolidated data that can be updated into additional InfoProviders. They are always sets of logically-related InfoObjects that are available in the form of a communication structure. You can continue to create and use 3. If fields that logically belong together exist in different source systems, they can be grouped together in a single InfoSource in the BI system by assigning multiple DataSources to one InfoSource. In transfer rule maintenance , individual DataSource fields are assigned to the corresponding InfoObject of the InfoSource.

GARTNER AND HIATT COLOR TEXTBOOK OF HISTOLOGY PDF

Creating an InfoSource for Transaction Data - SAP BW

In this section,we will write a transfer rule in the ABAP language. Table lists the material per unit sales price and quantity sold. It does not provide any sales revenue data,however. To improve future query performance,it is recommended that we calculate the sales revenue and save this result in the fact table,rather than calculate the sales revenue during a query run.

AM29LV160DB DATASHEET PDF

PowerExchange for SAP NetWeaver User Guide for PowerCenter

A structure consisting of InfoObjects without persistence for connecting two transformations. You always use an InfoSource when you want to perform two or more transformations consecutively in the data flow - without additional storage of the data. If you do not need two consecutive transformations, you can model the data flow without an InfoSource. A transformation is used to write data from the source to the target. It might be necessary to use one or more InfoSources however due to semantic reasons or the level of complexity.

Related Articles