InfoSources in the LSA

Concept

InfoSources have a decisive role in the LSA. The bigger a BW system is or becomes, the more important it is to use InfoSources to make administration of data flows better and more flexible.

InfoSources are actually not essential any more in connection with transformations. With separation into domains by semantic partitioning, a large number of transformation rules are created that all need to be changed whenever changes are made to the semantically partitioned object. Using an inbound InfoSource before the InfoProvider and an outbound InfoSource after the InfoProvider, the logic is bundled. The transformation logic is then between the outbound InfoSource of the uptream InfoProvider and the inbound InfoSource of the downstream InfoProvider.

This graphic shows the position of the transformation logic in the data flow:

Note that there are not transformations between Inbound InfoSource and InfoProvider and between InfoProvider and outbound InfoSource. This data flow logic is automatically implemented in this way if you use semantically partitioned objects.