Skip to Content
avatar image
Former Member

Infopackage Load taking very long time


I am trying to troubleshoot why our infopackage loads are taking so long.  The infopackage is loading to 0REFX_3, and it is real estate data.

The strange thing is that some data packages take about 5 minutes to load 16,000 records, and others take about 3 hours to load about 15,000 records.  Please see attached screenshot showing the job log in ECC.  Examining the data in the data packages, I noticed the data packages taking a longer time to load had blank values for fields RSOBART (Partner (short)) and RSPAROBVAL (Partner IO), although I'm not sure that is the problem.

There is ABAP code on the infopackage selections (see attached Screenshot).  Would this potentially slow down the load?

There also appear to be some "custom enhancements" in the job log but the names of these look like standard FM calls (e.g. BW_BTE_CALL_BW204010_E (BTE) ).  Could this be slowing down the load?  Any ideas or suggestions are welcome.

My supervisor says this has to do with our upgrade to Support Pack SAPKW73113, but again, if it relates to that, then why do some data packages load so much faster than others?  It should never take 3 hours to load 15,000 records.



ABAP_Routine.PNG (44.2 kB)
0REFX_3.PNG (28.0 kB)
Job_Log.PNG (97.5 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Oct 18, 2015 at 01:54 AM

    Hi Kevin,

    The only way is to analyze where it goes wrong. It is always wise to review the ABAP coding (which you did not share) and the BTE implementation (which you also did not share). However, I think that somewhere else it slows down. You might have to debug the extraction using t/code RSA3 to narrow down where the problem occurs.

    Please also review SAP Notes. You can search on: "0REFX_3" and "performance" with Search Method Extended Syntax.

    Best regards,


    Add comment
    10|10000 characters needed characters exceeded

    • Hello Kevin,

      as mentioned by sander u can make use of debugging.


      activate abap trace (ST05) and then execute  extraction (RSA3, then deactivate trace and check the log... u will get to know exactly which step it takes time.