Show TOC

Functions of SDATALocate this document in the navigation structure

The transfer of BW test and demo scenarios with SDATA is based on specific underlying ideas and functions, which combine flexibility - specification of transfer direction and object selection - with efficient mechanisms for extraction, creating objects and loading data.

Transfer and Transfer Path

SDATA supports the transfer of data between a source and a target. During a transfer, the transfer source extracts the data units of a test scenario and demo scenario and sends them to the transfer target. The BW metadata is created in the target and the associated data is written to the target. The source or target can be either a BW system or a local client/file system. The transfer path specifies the source and target for the transfer of a test and demo scenario, including the relevant BW objects and BW data.

Selecting and Collecting Objects

The required BW objects - such as BEx queries or InfoProviders - can be selected for the specified source. SDATA uses a simple object model, which includes the data belonging to the object and the dependent objects. SDATA processes all BW objects and BW data, which necessarily depend on the object selection.

SDATA Object Model

SDATA provides an object model that offers an abstract understanding of how BW objects and BW data represent a test and demo scenario in the context of SDATA. This object model fulfills specific requirements:

  • Accuracy

    The objects and data supplied by SDATA must be consistent and identical to the source .

  • Completeness

    Every object that is necessary for a scenario must be transferred. The same applies to the data.

  • Flexibility

    The object model can be modified in line with different object definitions and data formats, in order to integrate further BW object types in the future.

The SDATA object model has two entity types:

  • BW objects as individual entities of a BW scenario - referred to as scenario objects. Examples: BEx Query, InfoCube, InfoObject, display hierarchy
  • Data units of a scenario object - referred to as elementary objects. Examples: InfoCube requests, characteristic attributes, meta definitions of a query element

The model also has two relationship types:

  • A directional relationship between the main scenario object and the lower-level scenario objects ("based on"). Examples: query Q based on InfoCube C, or InfoObject A based on InfoObject B
  • A relation between the scenario object and the associated elementary object ("contains"). Examples: InfoCube A contains data request R, or characteristic C contains text data.

Based on this concept, BW test and demo scenarios with nested BW object dependencies can be analyzed and prepared for a fully automated transfer process.

Transfer Process

Once all objects have been collected, the transfer from the user can be started. During the transfer, all associated data objects are processed one after the other in a well-defined order. With large data packages, transaction data and master data is handled in blocks. The extraction of objects and data from a BW system is based on BW services. Creating objects and loading data is also based on BW functions. These guarantee consistent SID generation in the target system.