Show TOC

InfoSourceLocate this document in the navigation structure

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.

InfoSource with Key

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 you set the Aggregation flag in the definition of the InfoSource, the incoming data will be aggregated according 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.


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.

In complex transformation scenarios, deriving a compatible key definition from the InfoSource might be different, or even impossible.

DataStore Object-Like InfoSource

With a DataStore object as the target of the transformation, you can define the InfoSource as a DataStore Object-Like InfoSource. This option is automatically selectable once the InfoSource contains InfoObject 0RECORDMODE.

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.


The following graphic shows how the InfoSource is integrated into the dataflow:

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).