JDBC storedprocedure

[Former Member]

Hi Experts

I am doing the IDOC to JDBC scenario and executing stored procedure from the PI. the problem i am facing that when ever executing this scenario the pi system is executing stored procedure multiple times. how to handle this .

Regards

Upendra.V

[kkram]

You can check the audit log for the message in the adapter engine to see if indeed the adapter engine executed the stored procedure more than once for a particular message. Can you provide a screen shot of your audit log?

Thanks

KK

[Former Member]

HI KK

please find the audit log for the jdbc receiver adapter.

Audit Log for Message: 80144fe1-0cc7-1dee-aee2-d9689ff59851

Time Stamp Type Description

2009-10-17 15:15:45 Information The message was successfully received by the messaging system. Protocol: XI URL: http://xxxxxxx.kxxxx.com:5XXXXX:/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER

2009-10-17 15:15:45 Information Using connection JDBC_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.

2009-10-17 15:15:45 Information Message successfully put into the queue.

2009-10-17 15:15:45 Information The message was successfully retrieved from the receive queue.

2009-10-17 15:15:45 Information The message status was set to DLNG.

2009-10-17 15:15:45 Information Delivering to channel: HRMasterDataToSACS_JDBC_R

2009-10-17 15:15:45 Information JDBC Adapter Receiver processing started, required QoS ExactlyOnce

2009-10-17 15:15:45 Information JDBC Adapter Receiver Channel HRMasterDataToSACS_JDBC_R: processing started; party / service SACS_SQL_DEV.

2009-10-17 15:15:45 Information Database request processed successfully.

2009-10-17 15:15:45 Information Acknowledgement creation triggered for type: AckNotSupported

Time Stamp Type Description

2009-10-17 15:15:45 Information The message was successfully delivered to the application using connection JDBC_http://sap.com/xi/XI/System.

2009-10-17 15:15:45 Information The message status was set to DLVD.

2009-10-17 15:15:45 Information Acknowledgement successfully sent for type: AckNotSupported

Regards

Upendra