JDBC Sender

[Former Member]

Hello,

I do have a unique problem. We use a sender JDBC to select records and update immediately.

Unfortunately, for every record picked by JDBC, two IDOCS are getting created at receiver side.

I had checked the connections, advanced mode etc., but couldnt find the real problem.

Can abyone share a light on this.

It was working fine in development, but seems to be a problem in Test Environment. The Sender system has ensured that it triggered only one record.

What are all the possible causes that it might replicate in SAP. Is there anything to do with Transaction Isolation level or polling interval.

Cos i can see the adapter module giving 2 rows updated.

[Former Member · Accepted solution]

hi

problem could be with the DB only.

Are you mapping 1row to 1 Idoc ??

>>see the adapter module giving 2 rows updated

I beleive your update operates on the selected items.

So 2 updates means ..two rows are selected. can you check query return the message ie before mapping to idoc.

Check whether there are two rows.

rgds

Arun

[Former Member · Accepted solution]

Hi,

I did check it and the audit log shows just query executed. It was not showing the number of rows returned.

[Former Member · Accepted solution]

hi

you can check the payload in the sxi_monitor before the mapping pipeline step.

rgds,

Arun

[Former Member]

Hi Anandha,

In advanced JDBC configuration use the parameter ""LogSQLstatement" and value "true" by this way you will be able to see the no. of records passing through JDBC sender adapter in RWB.

Regards,

[Former Member]

Hi,

In Partner ProfileInbound Idoc's section-double click on your Idoc

And make sure that you have the Idoc Pack size as 1

REgards

Seshagiri