based on fault message ABAP coding required.

[svalluri23]

Dear Experts,

I design a scenario with Proxy to JDBC Synchronous interface, in that i kept fault message to catch the technical errors which are throwing by Oracle system like " unique constaint violated, can't insert value into a particular field ". This type of error messages we can able to get in sxmb_moni of PI system as below shown, but we need the same message in SAP system. For that what we have to do in ABAP as well as PI sides. Below highlighted error message wants in SAP Screen.

Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

<SAP:Category>XIAdapterFramework</SAP:Category>

<SAP:Code area="MESSAGE">GENERAL</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'PDI_PIPE' (structure 'Statement'): com.microsoft.sqlserver.jdbc.SQLServerException: Violation of PRIMARY KEY constraint 'PK_PDI_PIPE'. Cannot insert duplicate key in object 'dbo.PDI_PIPE'.</SAP:AdditionalText>

<SAP:Stack />

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

Kindly suggest me.

Thanks & Regards,

Srihari.

[rajasekhar_reddy14]

Hi,

We can easily implement fault message coding in ABAP server proxies, but in case of JDBC not sure you can implement this.

one sulution is write a stored procedure in receiver side and you can have a flexibility to send error message as a response(in vaid exml format).

using standard insert statement/anyother data base operation without stored procedure not posible to capture these kind of errors in to falut messages and sending back to ECC may be not possible.

regards,

Raj