Showing results for 
Search instead for 
Did you mean: 

General Question on how DTP works

Former Member
0 Kudos

Scenario in 3.5 (old dataflow): A datasource loading data to an ODS via a infopackage (Delta).

Scenario in BI 7 (new dataflow): Created a transformation and DTP (completely migrated to BI7). Now the data has to be loaded first to the PSA (using the old infopackage) and then run DTP (Delta) to load the DSO.

Suppose the old data flow (which is in 3.5) in alreay in Production and it is up and running daily (Delta loads from R/3). Now when the dataflow is migrated to BI 7 in Development and transported to Production, when I run the infopackage (which is still delta) loads new delta records to the PSA only. So my question is when I run the DTP for the first time, Does it try to load all the data that is in PSA or just the lastest delta load happened?

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos


Usually when an IP loads the data in the PSA , it set a "time stamp" if its a delta, which marks the presence of new data, now when you run a DTP over this PSA ,Even DTP (Data transfer Process) have the option for "Extraction Mode" (Full or delta) and even an option for the "Filter criteria" , all these combination could be manipulated to extract either all of the data or only the latest one.

Usin Delta mode and the filter criteria , i guess you can pick up only the latest data and continue with your usual updation of data in the target with duplication.

Again the following update as per the release of support pack for SAP BI 7.0 will make the process much more clearer :

*Netweaver 7.0 Support Stack 13 : Get All New Data in Source Request by Request*

*In SAP NetWeaver 7.0 SPS 13, the following enhancements are available in the data transfer process (DTP) in BW which is quite helpful in loading large datasets :*

*In DTP maintenance, you can specify that a DTP request is to get only one source request. By doing this, you can prevent DTP requests from becoming too large. Until now, when this option was used, only the first source request was retrieved. To get all source requests one after the other, the DTP had to be executed manually a number of times. You can now specify in DTP maintenance that the DTP is to get all new data from the source, one request after another. This makes it easier to process mass data using process chains and helps to reduce the total cost of ownership (TCO). The function also has a positive effect on the process monitor display in the process chain log view: When a DTP retrieves all new data request by request, rather than displaying just one request, the system displays a list of DTP requests.*

Following blob provide all the info regarding the same :


Hope this will be expedite.

Vaibhave Sharma

Edited by: Vaibhave Sharma on Sep 2, 2008 9:51 PM

Edited by: Vaibhave Sharma on Sep 2, 2008 10:16 PM

Former Member
0 Kudos


It will load only the latest delta. But you don't feel confident about that, just delete all the requests in the PSA for that datasource.

To know more about migrating old data flows, check this:

For migration check this link:

For BI 2004s Modeling check this thread if it can help you:


Jorge Diogo

Former Member
0 Kudos

Thanks for the response and links.

In DTP's perspective, all the data is new in PSA right? Then my question is how would it leave out old data and just process latest request.

Former Member
0 Kudos

Either you need to delete old requests from psa before doing delta to targets or you need to use the

option 'get delta only once' in the DTP.