All about Data Transfer Process (DTP) – SAP BW 7


DTP determines the method for switch of knowledge between two persistent/non persistent objects inside BI.

As of SAP NetWeaver 7.0, InfoPackage masses information from a Supply System solely as much as PSA. It’s DTP that determines the additional loading of knowledge thereafter.


  • Loading information from PSA to InfoProvider(s).
  • Switch of knowledge from one InfoProvider to a different inside BI.
  • Knowledge distribution to a goal exterior the BI system; e.g. Open HUBs, and so on.

Within the means of transferring information inside BI, the Transformations outline mapping and logic of knowledge updating to the information targets whereas, the Extraction mode and Replace mode are decided utilizing a DTP.

NOTE: DTP is used to load information inside BI system solely; besides when they’re used within the eventualities of Digital InfoProviders the place DTP can be utilized to find out a direct information fetch from the supply system at run time.

Key Advantages of utilizing a DTP over typical IP loading

  1. DTP follows one to 1 mechanism between a supply and a Goal i.e. one DTP sources information to just one information goal whereas, IP masses information to all information targets without delay. This is without doubt one of the main benefits over the InfoPackage methodology because it helps in attaining loads of different advantages.
  2. Isolation of Knowledge loading from Supply to BI system (PSA) and inside BI system. This helps in scheduling information masses to InfoProviders at any time after loading information from the supply.
  3. Higher Error dealing with mechanism with using Non permanent storage space, Semantic Keys and Error Stack.


There are two forms of Extraction modes for a DTP – Full and Delta.


Replace mode full is identical as that in an InfoPackage.

It selects all the information out there within the supply primarily based on the Filter situations talked about within the DTP.

When the supply of knowledge is anyone from the beneath InfoProviders, solely FULL Extraction Mode is offered.

  • InfoObjects
  • InfoSets
  • DataStore Objects for Direct Replace

Delta shouldn’t be doable when the supply is anybody of the above.


In contrast to InfoPackage, delta switch utilizing a DTP doesn’t require an specific initialization. When DTP is executed with Extraction mode Delta for the primary time, all present request until then are retrieved from the supply and the delta is routinely initialized.Delta.jpg

The beneath 3 choices can be found for a DTP with Extraction Mode: Delta.

  • Solely Get Delta As soon as.
  • Get All New Knowledge Request By Request.
  • Retrieve Till No Extra New Knowledge.


     I      Solely get delta as soon as:

If this indicator is about, a snapshot state of affairs is constructed. The Knowledge out there within the Goal is an actual reproduction of the Supply Knowledge.


Allow us to contemplate a state of affairs whereby Knowledge is transferred from a Flat File to an InfoCube. The Goal must comprise the information from the most recent Flat File information load solely. Every time a brand new Request is loaded, the earlier request must be deleted from the Goal. For each new information load, any earlier Request loaded with the identical choice standards is to be faraway from the InfoCube routinely. That is essential, every time the supply delivers solely the final standing of the important thing figures, much like a Snap Shot of the Supply Knowledge.

Resolution – Solely Get Delta As soon as

A DTP with a Full load ought to suffice the requirement. Nonetheless, it’s not beneficial to make use of a Full DTP; the reason is, a full DTP masses all of the requests from the PSA no matter whether or not these have been loaded beforehand or not. So, so as to keep away from the duplication of knowledge resulting from full masses, we’ve to all the time schedule PSA deletion each time earlier than a full DTP is triggered once more.

‘Solely Get Delta As soon as’ does this job in a a lot environment friendly method; because it masses solely the most recent request (Delta) from a PSA to a Knowledge goal.

      1. Delete the earlier Request from the information goal.
      2. Load information as much as PSA utilizing a Full InfoPackage.
      3. Execute DTP in Extraction Mode: Delta with ‘Solely Get Delta As soon as’ checked.

The above 3 steps may be included in a Course of Chain which avoids any guide intervention.

     II     Get all new information request by request:

For those who set this indicator together with ‘Retrieve Till No Extra New Knowledge’, a DTP will get information from one request within the supply. When it completes processing, the DTP checks whether or not the supply incorporates any additional new requests. If the supply incorporates extra requests, a brand new DTP request is routinely generated and processed.

NOTE: If ‘Retrieve Till No Extra New Knowledge’ is unchecked, the above possibility routinely modifications to ‘Get One Request Solely’. This is able to in flip get just one request from the supply.

Additionally, as soon as DTP is activated, the choice ‘Retrieve Till No Extra New Knowledge’ no extra seems within the DTP upkeep.

Bundle Dimension

The variety of Knowledge information contained in a single particular person Knowledge package deal is set right here.

Default worth is 50,000.



The choice Standards for fetching the information from the supply is set / restricted by filter.

We now have following choices to limit a worth / vary of values:

   A number of choices

   OLAP variable

   ABAP Routine

A on the fitting of the Filter button signifies the Filter choices exist for the DTP.

Semantic Teams

Select Semantic Teams to specify the way you need to construct the information packages which might be learn from the supply (DataSource or InfoProvider). To do that, outline key fields. Knowledge information which have the identical key are mixed in a single information package deal.

This setting is simply related for DataStore objects with information fields which might be overwritten. This setting additionally defines the important thing fields for the error stack. By defining the important thing for the error stack, you make sure that the information may be up to date within the goal within the right order as soon as the wrong information information have been corrected.

A the fitting aspect of the ‘Semantic Teams’ button signifies the Semantic keys exist for the DTP.



Error Dealing with

If an error happens, the error is reported on the package deal degree and never on the information document degree.

The wrong information will not be written to the error stack because the request is terminated and needs to be up to date once more in its entirety.

This leads to quicker processing.

If errors happen, the system terminates the replace of your entire information package deal. The request shouldn’t be launched for reporting. The wrong document is highlighted in order that the error may be assigned to the information document.

The wrong information will not be written to the error stack because the request is terminated and needs to be up to date once more in its entirety.

  • Legitimate Data Replace, No Reporting (Request Pink):

This feature means that you can replace legitimate information. This information is simply launched for reporting after the administrator checks the wrong information that aren’t up to date and manually releases the request (by a QM motion, that’s, setting the general standing on the Standing tab web page within the monitor).

The wrong information are written to a separate error stack through which the information are edited and may be up to date manually utilizing an error DTP.

  • Legitimate Data Replace, Reporting Attainable (Request Inexperienced):

Legitimate information may be reported instantly. Computerized follow-up actions, equivalent to adjusting the aggregates, are additionally carried out.

The wrong information are written to a separate error stack through which the information are edited and may be up to date manually utilizing an error DTP.

Error DTP

Faulty information in a DTP load are written to a stack referred to as Error Stack.

Error Stack is a request-based desk (PSA desk) into which inaccurate information information from a knowledge switch course of (DTP) are written. The error stack relies on the information supply (PSA, DSO or Information Dice), that’s, information from the supply are written to the error stack.

In an effort to add information to the Knowledge Goal, we have to right the information information within the Error Stack and manually run the Error DTP.



Processing Mode

Serial Extraction, Fast Parallel Processing:

A request is processed in a background course of when a DTP is began in a course of chain or manually.


Serial in dialog course of (for debugging):

A request is processed in a dialog course of when it’s began in debug mode from DTP upkeep.
This mode is good for simulating the DTP execution in Debugging mode. When this mode is chosen, we’ve the choice to activate or deactivate the session Break Factors at varied phases like – Extraction, Knowledge Filtering, Error Dealing with, Transformation and Knowledge Goal updating.

You can’t begin requests for real-time information acquisition in debug mode.

Debugging Tip:

While you need to debug the DTP, you can not set a session breakpoint within the editor the place you write the ABAP code (e.g. DTP Filter). You could set a session break level(s) within the Generated program as proven beneath:


No information switch; delta standing in supply: fetched:

This processing is offered solely when DTP is operated in Delta Mode. It’s much like Delta Initialization with out information switch as in an InfoPackage.

On this mode, the DTP executes instantly in Dialog. The request generated would mark the information discovered from the supply as fetched, however doesn’t truly load any information to the goal.

We are able to select this mode even when the information has already been transferred beforehand utilizing the DTP.


Delta DTP on a DSO

There are particular information switch choices when the Knowledge is sourced from a DTP to different Knowledge Goal.


  • Lively Desk (with Archive)

       The information is learn from the DSO energetic desk and from the archived information.

  • Lively Desk (With out Archive)
    The information is simply learn from the energetic desk of a DSO. If there’s information within the archive or in near-line storage on the time of extraction, this information shouldn’t be extracted.
  • Archive (Full Extraction Solely)
    The information is simply learn from the archive information retailer. Knowledge shouldn’t be extracted from the energetic desk.
  • Change Log
    The information is learn from the change log and never the energetic desk of the DSO.
NOTE : Please do not copy -
See also  What Has Changed, and by How Much

Leave a Reply