Skip to Content

Extraction from ECC to BW fails with error "Caller 09 contains an error message"

Hello All,

Extraction from ECC to BW fails with below error message.

FYI..RFC connection is fine between ECC and BW. Jobs in both the systems are completed successfully.

This issue is happening for many data sources from last 3 weeks, after repeating the load it will be completed successfully.

Please advise me what could have caused this issue and how could we resolve.

Error message :

"Error 7 when sending an IDoc,

timeout during accept / CPIC-CALL: 'ThSAPCMRCV' : 10,

Errors in source system"

Deatiled error message:


An error occurred in the source system.

System Response

Caller 09 contains an error message.

Further analysis:

The error occurred in Service API . Refer to the error message.


How you remove the error depends on the error message.


If the source system is a Client Workstation, then it is possible that the file that you wanted to load was being edited at the time of the data request. Make sure that the file is in the specified directory, that it is not being processed at the moment, and restart the request.


Prakash K

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Apr 28, 2016 at 11:08 AM

    Hi Prakash,

    Can you check the below things if this helps

    2034087 - GW: "Timeout during accept" error message in trace file

    1285242 - CPIC-CALL: 'ThSAPCMRCV' no data received

    Also I searched in google and found that the same error occurs , When executing MDX reports against SAP BW, a non-Unicode RFC library (librfc32.dll) is required to communicate with the SAP BW application server. If the non-Unicode RFC library is not implemented on the SAP BW application server, the error message above is returned.

    So in our case is very clear that there is a problem in communication between the systems,

    Also you can make check in SM59 > R/3 Connection > TMS Communication Interface generated --> is the connection OK or NOT OK STMS --> is the transport configured properly ? or Any Upgrade happened ? or restart or server on both systems happened ? I think the below note which give appropriate answer to issue ( may be API file library missing ) you can too check with basis collegues to have a look at Note level

    1954118 - Connection Failure with RFC Desitination of Started External RFC Server and Memory Leaks with RfcAccept

    Hope I have give some thing out it OR we tired a step ahead to solution



    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Apr 28, 2016 at 02:12 PM

    Hi Prakash,

    Caller 09 Error in the source system is due Error in RFC Connection between BW and ECC.

    For reference go through the following links.



    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.