Skip to Content
author's profile photo Former Member
Former Member

How to Improve Performance of DTP in SAP BI 7.3 further


we have migrated SAP Bi 7.0 to 7.3x flow .So currently i am looking to improve the performance of DTP. i have applied following solution ,able to reduce data load time

1. Increased No. of parallel process

2 Used Semantic group.

3. upgraded process priority.

4 Code optimization

Is any other way to improve the performance of DTP further in 7.3x flow

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Posted on Jul 25, 2012 at 11:28 AM


    - Increase the datapacket size.

    - In code optimization

    - Try to reduce the SELECT queries and pull data into internal table and use READ statement.

    - Try to use SORTED table or HASHED table.

    - Try to use BINARY SEARCH




    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jul 31, 2012 at 01:25 AM

    Hi Nadeem,

    (1) Review the granularity of the DataProvider versus the Data Target. Is your transformation dropping records that are not allowed in the DataTarget? When only a sub-set is allowed to make it through then you can put that selection criteria in the DTP itself. This will decrease the overall load time because you never pull the data from the DataProvider that you are always dropping.

    (2) When using a SELECT and READ technique for external lookups to be added to the records, go to the effort of manually defining a very thin internal table that only contains what you are actually using in the transformation. This way you avoid retrieving the entire width of the characteristic source table.

    (3) Review the logic of the transformation routine and see if the internal loop processing will benefit from adding EXIT statements. If you have to sequentially loop and you found what you are looking for then do not bother looping through the rest of the internal table.

    (4) Are all the InfoObjects coming from the DataProvider used in the DataTarget? No, then consider adding an InfoSource into the ETL flow right after the Export DataMart that is the DataProvider. This will allow you to trim the width of the records being processed. This is a lower memory footprint. Keep in mind that the removal of 10 or 20 InfoObjects from the memory footprint is worth the effort, especially when you consider that loading of millions of records through that ETL flow.

    (5) Do you really need to use the Semantic grouping? Turn it off if you do not have some explicit reason to use it. This will remove the complex data sort (GROUPBY this, that, this, that and that) from the ETL flow in preparing the record to come from the DataProvider. When you use semantic grouping the database server must first make a temporary copy of the data to be extracted, sort it and the create the DataPackets in the order to be delivered. When you do not use semantic grouping (because you have no need too in your business logic) then the extraction of data from the DataProvider will be faster as the only sorting is kept to a minimum (GROUPBY request, DataPacket, record number).

    If you would like a private/confidential code review done then please contact me via the business card.

    Hope this helps.

    Kind regards,


    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jul 31, 2012 at 03:42 AM


    check below blog

    see if u can implement RDA concept..

    Thanks and regards


    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.