Professional Documents
Culture Documents
Data Source Migration
Data Source Migration
R3TR-ISFS to R3TR-RSDS
DataSource
Datasource refers to set of fields that provide the data for a business
unit for data transfer into BI. DataSource is a set of logically-related
fields that are provided to transfer data into BI from the OLTP system/
Source system.
Datasource and 3.x Datasource
• 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 2004s.
• During emulation (displaying and using 3.x DataSources with the interfaces of the
new DataSource concept), the DataSource (R3TR RSDS) is instantiated from the
metadata tables that existed in the earlier releases (R3TR ISFS).
• 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 data flow, you can set the processes for data
transfer.
• You can display an emulated 3.x DataSource in DataSource maintenance in BI.
Changes are not possible in this display. In addition, you can use emulation to create
the data flow for a 3.x DataSource with transformations, without having to migrate the
existing data flow that is based on the 3.x DataSource.
• Emulation is recommended before migrating the DataSource to model and test the
functionality of the (new) data flow with transformations, without changing or deleting
the objects of the existing data flow.
Why Migration?
• An emulated 3.x DataSource does not
support real-time data acquisition or using
the data transfer process to access data
directly or load data directly (without using
the PSA). Hence Migration to RSDS
Datasource
Migration of Datasource
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 instead
they can be migrated by copying them in the source system.
If you are using real-time data acquisition or want to access data directly
using the data transfer process, we recommend migration.
Constraints
A DataSource cannot exist simultaneously in both object types in the same system.
The new DataSource concept cannot yet be used for transferring data from external systems (metadata
and data transfer using staging BAPIs) or for transferring hierarchies.
Transformation Process
Select your target
object and the
source of
transformation
Activate the
Transformation
Migration of Datasource
T-Code :
RSDS
Enter the
Datasource Name
and the Source
system Name
Click on this
Icon to
Migrate
Select “with export”
option to restore at
a later stage
Save the
Changes
If Old Transformation
Concept is required
then this step has to
be followed
Use
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.
Prerequisites
• You exported and archived the relevant 3.x objects when you migrated the 3.x DataSource.
• Procedure
• In the maintenance for the migrated DataSource (transaction RSDS), choose DataSource Restore.
• If required, delete the dependent transformation (R3TR TRFN) and data transfer process (R3TR DTPA) objects.
• Transport the restored 3.x DataSource (R3TR ISFS), along with its dependent objects, into the target system.
T-Code :
RSDS
Select
this
option
Select
this
option
Thank You!