RFC to JDBC(Insert) async scenario

[Former Member]

Hi Experts,

In RFC to JDBC(Insert) async scenario we are getting the the response from JDBC as <insert_count>1</insert_count> after inserting in to DB . Is there any way to stop getting response?

Regards,

Raj

[former_member200962]

<insert_count>1</insert_count>

Firstly this is not an error but an acknowledgement from the JDBC that the Insert for the corresponding Statement node is successful. The count 1 represents that you have made just one Insert-Statement call to the JDBC......had there been no Insert in the DB then you could have got 0 insetad of 1.

Normally happens when the sender requests for an acknowledgement. Don have knowledge on the ABAP-front so cant comment on the blog given by Prateek, but seems that because of the sync nature of RFC you are getting this ack from JDBC...

Regards,

Abhishek.

[prateek]

Abhishek, just to correct, the "insert_count" received is a Response and not an Ack.

Regards,

Prateek

[former_member200962]

Thanks for the information.

Thanks,

Abhishek.

[Former Member]

Did you set your message interface has inbound asynchronous right ?

make sure that is async

Rajesh

[Former Member]

Thanks for ur reply..

The Inbound Interface in Asyn only.Is there any way to stop receiving the response from JDBC adapter?

Regards,

raj

[Former Member]

Hi Rajesh,

If you have the inbound interface as asynchronous then you will not get the response. Please reverify once again and check the interface mapping whether do you have any response mapping?

Also check the receiver and interface determination whether you are using the same interface or not.

Regards,

---Satish

[Former Member]

Hi Satish,

I checked it was fine in Interface Deter and receiver agrmnt.but still i am getting the response.Is there any way around?

Regards,

Raj

[Former Member]

check the receiver JDBC communication channel..... is Qua;ity of service is configured as Best effort?

[former_member187339]

Hi Rajesh,

Are you getting an error message in moni for response?

Also check your sender Communication channel.. it shoudl have QoS as Exactly once or once in order

Regards

Suraj

[prateek]

The problem in your scenario is that the RFC sender QOS is Sync by default. Therefore when you use your interface, it will always send a response. In case you need to avoid this, you need to make an explicit async RFC call as shown in the blog

/people/swaroopa.vishwanath/blog/2006/12/28/send-rfc-to-sap-xi-150-asynchronous

Regards,

Prateek