Error in Xi while calling the stored procedure

[Former Member]

Hi,

Our scenario is SAP --- XI -

---

SQL Server

We are sending material data to SQL server from SAP.

we sent the materials (say 100 numbers) from sap, The status of the messages are SYSTEM ERROR'.

below is the error.

Delivery of the message to the application using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'usp_LOAD_SAP_MATERIAL' (structure 'STMT_MATERIAL'): java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction..

and when i resent the failed messages again,they went through (success)

What may be problem,why the messages went to system error first,and when resend the failed messages they went thorogh.(success).

Regards

Srinivas

[Former Member · Accepted solution]

there can be many reason,

to find out you have to run procedure in the database environment with same data as payload.

(reason might be authorization issue,table/row lock issue or any other exception handle michanism in procedure)

[Former Member · Accepted solution]

Hi,

Thanks for all your answers

to find out you have to run procedure in the database environment with same data as payload.

reason might be authorization issue,table/row lock issue or any other exception handle michanism in procedure

But when iam pusing a material from sap to sql server,there is no issue.iam not getting any error.

Iam getting error only when iam pushing more number of materials from sap to sql server.

these are EOIO queues,and the queue id is MAT(MARA-MATNR)

Help me in resolving the issue.

Regards

Srinivas

[Former Member]

Thanks for your help,

there is issue in the store procedure

[Former Member]

Hi

Try to test the Stored Procedure from the SQL itself by giving exact record set.

Also check in stored procedure that u have used : COMMIT statement.

paste u r stored procedure, pureply its a STORED PROCEDURE problem

rgds

srini