DataSource 

Definition

Amount of fields that provide the data for a business unit for data transfer to BI. From a technical viewpoint, the DataSource includes a quantity of fields that logically belong together that are offered for data transfer into BI in a flat structure (the extraction structure), or for hierarchies they are offered in multiple flat structures.

There are four types of DataSources:

●     DataSources for transaction data

●     DataSources for master data

○     DataSources for attributes

○     DataSources for texts

○     DataSources for hierarchies

Use

DataSources supply the metadata description of source data. They are used for extracting data from a source system and for transferring data into BI.

The following image illustrates the role of the DataSource in the BI data flow:

The data is loaded from any source in the DataSource structure into BI, using an InfoPackage. You determine the target into which the data from the DataSource is to be updated in the transformation. You also assign fields for the DataSource to InfoObjects from the target object in BI.

Scope of DataSource Versus DataSource 3.x

DataSource 3.x

Until now DataSources have been known as DataSource replicates (object type R3TR ISFS) in the BI system. Transfer of data from this type of DataSource, called DataSources 3.x below, is only possible when the DataSource 3.x is assigned to an InfoSource 3.x and the fields of the DataSource 3.x in the transfer structure maintenance InfoObjects are assigned to InfoSource 3.x. When the transfer rules 3.x are activated, and thus the transfer structure 3.x, a PSA table is generated into which the data can be loaded.

If your dataflow is modeled with objects based on the old concept (InfoSource 3.x, transfer rules 3.x, update rules 3.x) and the process design is based on these objects, you can continue to work with DataSources 3.x to transfer data into BI from a source system.

DataSource

As of SAP NetWeaver 2004s, a new object concept is available for DataSources. It is used in conjunction with the changed objects concepts in data flow and process design (transformation, InfoPackage for loading to the PSA, data transfer process for data distribution within BI). The object type for a DataSource from the new concept - called DataSource in the following - is R3TR RSDS.

In BI in the DataSource maintenance, you determine which DataSource fields contain the information that is relevant for decision making for a business process and should be transferred. Upon activation of the DataSource, a PSA table is generated in the input layer of BI and data can then be loaded. In the transformation, you determine what the assignment of fields from the DataSource to InfoObjects from BI should look like. Data transfer processes facilitate the further distribution of the data from the PSA to other targets. The rules that you set in the transformation apply here.

Overview of Object Types

For a particular DataSource it is not possible for both object types to simultaneously exist in the same system. The following table provides you with an overview of the (transport-relevant) metadata object types. The table also includes the object types for DataSources in SAP source systems:

DataSource Type	BI: Object Type of A or M Version	BI: Object Type of Shadow Version (Source System Independent)	SAP Source System: Object Type of A Version	SAP Source System: Object Type of D Version
DataSource	R3TR RSDS	R3TR SHDS (Shadow object delivered in its own table with release and version)	R3TR OSOD	R3TR OSOA
DataSource 3.x	R3TR ISFS	R3TR SHFS for non-replicating source systems SHMP for replicating source systems, that is SAP source systems (shadow object delivered in its own table with source system key)	R3TR OSOD	R3TR OSOA

Restriction

The new DataSource concept cannot yet be used for data transfer from external systems or for transferring hierarchies.

Recommendation

We recommend that you adapt the data flow for the DataSource as well as the process design to the new concepts. To do this you need to use an emulated DataSource. Then you can migrate the DataSource 3.x into a DataSource and use the advantages of the new concepts for your scenario.