Commit error while transferring Sales order Document to GTS

Question

Hello,
We faced a transfer error while transferring sales order document to GTS.
When I debugged the code function /SAPSLL/API_6800_SYNCH is called. In this function, /SAPSLL/CUHD_MAINTAIN_SINGLE is called with parameter lv_no_commit = 'X'. When I checked why its value is 'X', I saw that if the RFC destination and the current system are the same, then lv_no_commit = 'X', (means if the R3 and the GTS are in the same server, same client.) In debug mode I set the value of lv_no_commit to space, and then it works. It creates the GTS document.
We are also transferring billing documents and it works fine. When I checked what is the difference between transferring sales order document and transferring Billing document, I saw that in the transferring billing document there is another function is called /SAPSLL/API_6800_CSD_SYNCH, and it's calling parameters(in background, as seperate unit) are different from calling parameters of /SAPSLL/API_6800_SYNCH. You can see the difference below.
For sales document transfer :
    CALL FUNCTION '/SAPSLL/API_6800_SYNCH'
      DESTINATION cs_transfer-rfc_dest
For billing document transfer :
    CALL FUNCTION '/SAPSLL/API_6800_CSD_SYNCH'
      IN BACKGROUND TASK
      DESTINATION cs_transfer-rfc_dest
      AS SEPARATE UNIT
So my question is, do you think is it a sap standard program error, or is there any suitable settings in the customizing or SM59 to fix this error?
Thanks in advance
Serhat
Edited by: Serhat Dirihan on Jan 22, 2009 11:46 AM

Answer 1

Dear Serhat,
I don't think this is an RFC problem or an error. But you wrote:
When I checked why its value is 'X', I saw that if the RFC destination and the current system are the same, then lv_no_commit = 'X', (means if the R3 and the GTS are in the same server, same client.)
It is impossible to have GTS and R/3 on the same system and same client. At least the client should be different. So try to check why the call is performed like that.
Balazs