Load from Data Stream

You can use this function to collect transaction data or master data and hierarchies from the BI system (SAP NetWeaver Business Intelligence) or from connected SAP source systems to the consolidation system (SEM-BCS).

Integration

You can use the Load from Data Stream function as an alternative or in addition to the other data collection procedures.

Within the Load from Data Stream method you can use the Business Add-In (BAdI) for data collection (UC_DATATRANSFER) to perform mapping activities that the method does not directly support - such as mapping source fields to target fields with a 1:n relationship) . For more detailed information, see the system documentation of the BAdI UC_DATATRANSFER and the documentation of its methods.

Prerequisites

To be able to load data from the BI system into the consolidation system, this data needs to be available in an InfoProvider (transaction data) or an InfoObject (master data and hierarchies). For example, first you need to have uploaded the EC‑CS data into the InfoProvider using an SAP BI upload procedure.

You need to create a source data basis to be used for loading from the data stream, and then specify that source data basis in the data basis currently in use. You specify the following data in the source data basis:

InfoProvider from which you want to load the transaction data
InfoObject catalog that contains the InfoObjects from which you want to load master data and hierarchies

Features

When you customize the Load from Data Stream method, specify the InfoProvider for the transaction data, or the InfoObject for the master data and hierarchies. Furthermore, you specify how the system is to map the characteristics and key figures of the source data to the consolidation system. Finally, you can define source and target selections by specifying the source area (with its characteristics and key figures) and the target area to be posted to in the data basis.

When the system executes the method, it writes the values to the target area of the data basis in accordance with the settings you have made in Customizing. In doing so, it derives the values for consolidation-specific characteristics (for example, the posting level and the default values for subassignments when loading transaction data).

Loading of Transaction Data

You can load the following data from an InfoProvider (for example, an InfoCube or DataStore object) into the consolidation system:

Reported financial data (posting level 00)
Documents (posting levels 01, 02, 10, 12, 20, 22, and 30)
Additional financial data

Note

The data type Sequence of Activities includes the data streams Sequence of Activities and Activity Sorting. For more information, see Automatic Data Collection of Activities.

End of the note.

Here are examples of SAP components you can load data from:

FI-GL, FI-SL, CO-PCA, and CO-PA
EC-CS
SEM-BPS

You can load data that is stored in an InfoProvider from a local or a non-local SAP BI system.

You are not restricted to accessing data that is stored directly in an InfoProvider. You can also access data which the BI system merely references, without the data being physically stored in the BI system. For example, you can specify an InfoProvider that obtains its data from a transactional SAP source system.

The structure of the InfoProvider that provides the source data may be different from the data structures of the data basis in the consolidation system.

To load transaction data, assign the Load from Data Stream method to a data collection method that you then assign to a data collection task (see Customizing for Load from Data Stream).

Loading of Documents

Whether the system can transfer the source documents 1:1 when loading documents depends on the structure of the source InfoProvider and on the mapping. The system generates a new document number for the target document in every case. If the source InfoProvider contains the Document Number characteristic and a mapping rule is defined in the Load from Data Stream method that assigns the source document numbers to the target document numbers, the system can transfer the documents 1:1. In this case, the system writes the source document number in the Reference Document Number characteristic in the target document. Otherwise, the system uses the standard rules for posting documents (see also Automatic Data Collection of Documents).

Loading of Master Data and Hierarchies

You load master data and hierarchies from individual InfoObjects. You are not restricted to accessing data that is stored directly in an InfoObject of the BI system. You can also access data which the InfoObject merely references, without the data being physically stored in the BI system (virtual InfoObject). For example, you can load the master data and hierarchies of consolidation units from a transactional SAP source system.

For additional information, see Loading of Master Data from Connected SAP Systems.

Integrated Loading of Superordinate Fields

If you choose data type Assets/Liabilities (Master Data), you can specify that, in the case of a compound of characteristics, the system is also to load independent (that is, superordinate) fields from the data stream. Using this function you can, for example, load the asset main number together with the asset subnumber from the data stream.

Example

You have a decentralized corporation in which the transactional charts of accounts of the subsidiaries (FI-GL) differ to a limited extent from the consolidation chart of accounts of corporate headquarters (SEM-BCS).

Each subsidiary runs an SAP BI upload into an InfoProvider.

In the Mapping section of the method Load from Data Stream you can map the characteristics and key figures of a subsidiary to the characteristics and key figures in SEM-BCS.

Mappings created in this way can be reused – either in part or in their entirety – for other subsidiaries.

You use a dedicated data collection task to transfer the data from the InfoProvider of the subsidiary to the consolidation area of corporate headquarters.