Emulation, Migration, and Restoring
DataSources
Emulation
3.x DataSources (object type R3TR ISFS) exist in the BI database in the metadata tables that were available in releases prior to SAP NetWeaver 7.0.
The emulation permits you to display and use the DataSource 3.x using the interfaces of the new DataSource concept. The DataSource (R3TR RSDS) is instantiated from the metadata tables of the DataSource 3.x.
You can display a 3.x DataSource as an emulated DataSource in DataSource maintenance in BI. You can also model the data flow with transformations for an emulated DataSource if there are already active transfer rules and a transfer structure and a PSA for the 3.x DataSource. Once you have defined the objects of the data flow, you can set the processes for data transfer (loading process using InfoPackage and data transfer process), along with other data processing processes in BI. We recommend that you use process chains.
Emulation and definition of the objects and processes of the data flow that are based on the emulation in accordance with the new concept are a preparatory step in migrating the DataSource.
If you use an emulated DataSource 3.x, note that the InfoPackage does not use all of the settings defined in the 3.x data flow because in the new data flow it only loads the data into the PSA. To prevent problems arising from misunderstandings about using the InfoPackage, we recommend that you only use the emulation in development and test systems.
More Information:
Using Emulated 3.x DataSources
Migration
You can migrate a 3.x DataSource that transfers data into BI from an SAP source system or a file or uses DB Connect to transfer data into a DataSource. 3.x XML DataSources and 3.x DataSources that use UD Connect to transfer data cannot be migrated directly. However, you can use the 3.x versions as a copy template for a Web service or UD Connect DataSource.
You cannot migrate hierarchy DataSources, DataSources that use the IDoc transfer method, export DataSources (namespace 8* or /*/8*) or DataSources from BAPI source systems.
Migration (SAP Source Systems, File, DB Connect)
If the 3.x DataSource already exists in a data flow based on the old concept, you use emulation first to model the data flow with transformations and data transfer processes and then test it. During migration you can delete the data flow you were using before, along with the metadata objects.
If you are using real-time data acquisition or want to access data directly using the data transfer process, we recommend migration. Emulation does not support this.
When you migrate a 3.x DataSource (R3TR ISFS) in an original system, the system generates a DataSource (R3TR RSDS) with a transport connection. The 3.x DataSource is deleted, along with the 3.x metadata object mapping (R3TR ISMP) and transfer structure (R3TR ISTS), which are dependent on it. If a PSA and InfoPackages (R3TR ISIP) already exist for the 3.x DataSource, they are transferred to the migrated DataSource, along with the requests that have already been loaded. After migration, only the specifications about how data is loaded into the PSA are used in the InfoPackage.
You can export the 3.x objects, 3.x DataSource, mapping and transfer structure during the migration so that these objects can be restored. The collected and serialized objects are stored in a local table (RSDSEXPORT).
You can now transport the migration into the target system.
When you import the transport into the target system in the after-import, the system migrates the 3.x DataSource (R3TR ISFS) (as long as it is available in the target system) to a local DataSource (R3TR RSDS), without exporting the objects that are to be deleted. The 3.x DataSource, mapping (R3TR ISMP) and transfer structure (R3TR ISTS) objects are deleted and the related InfoPackages are migrated. The data in the DataSource (R3TR RSDS) is transferred to the PSA.
More Information:
Migrating by Copying
You cannot migrate in the way described above
● If you are transferring data into BI using a Web service and have previously used XML DataSources that were created on the basis of a file DataSource.
● If you are transferring data into BI using UD Connect and have previously used a UD Connect DataSource that was generated using an InfoSource.
3.x XML DataSource à Web Service DataSource
You can make a copy of a generated 3.x XML DataSource in a source system of type Web Service. When you activate the DataSource, the system generates a function module and a Web service. On your interface, these are different to the 3.x objects. The 3.x objects (3.x DataSource, mapping, transfer rules and generated function module and Web service) are therefore obsolete and can be deleted manually.
3.x UD Connect DataSource à UD Connect DataSource
For a 3.x UD Connect DataSource, you can make a copy in a source system of type UD Connect. The 3.x objects (3.x DataSources, mapping, transfer rules and the generated function module) are obsolete after they have been copied and can be deleted manually.
More Information:
Migrating 3.x DataSources (UD Connect, Web Service)
Restoring
You can restore a DataSource 3.x from the DataSource (R3TR RSDS) for SAP source systems, files, and DB Connect. The 3.x metadata objects must also be exported and archived with the migration of the DataSource 3.x into the original system for files and DB Connect. The system reproduces the 3.x DataSource (R3TR ISFS), mapping (R3TR ISMP), and transfer structure (R3TR ISTS) objects with their pre-migration status.
Only use this function if unexpected problems occur with the new data flow after migration and these problems can only be solved by restoring the data flow used previously.
When you restore, the 3.x DataSource (R3TR ISFS), mapping (R3TR ISMP) and transfer structure (R3TR ISTS) objects that were exported are generated with a transport connection in the original system. The DataSource (R3TR RSDS) is deleted. The system tries to retain the PSA. This is only possible if a PSA existed for the 3.x DataSource before migration. This may not be the case if an active transfer structure did not exist for the 3.x DataSource or if the data for the DataSource was loaded using an IDoc. The InfoPackage (R3TR ISIP) for the DataSource is retained in the system. Available targets are displayed in the InfoPackage (this also applies to InfoPackages that were created after migration). However, in InfoPackage maintenance, you have to reselect the targets into which you want to update data.
The transformation (R3TR TRFN) and data transfer process (R3TR DTPA) objects that are dependent on the DataSource (R3TR RSDS) are retained and can be deleted manually, as required. You can no longer use data transfer processes for direct access or real-time data acquisition.
You can now transport the restored 3.x DataSource and the dependent transfer structure and mapping objects into the target system.
When you transport the restored 3.x DataSource into the target system, the DataSource (R3TR RSDS) is deleted in the after-import. The PSA and InfoPackages are retained. If a transfer structure (R3TR ISTS) is transported with the restore process, the system tries to transfer the PSA for this transfer structure. This is not possible if no transfer structure exists when you restore the 3.x DataSource or if IDoc is specified as the transfer method for the 3.x DataSource. The PSA is retained in the target system but is not assigned to a DataSource/3.x DataSource or to a transfer structure.
You can also use the restoration function to correct replication errors. If a DataSource was inadvertently replicated in the object type R3TR RSDS, you can change the object type of the DataSource in R3TR ISFS by restoring it.