on 06-17-2015 3:42 PM
Dear Gurus,
We have an interface with flow from 3rd party system to PI 7.31 dual stack to SAP ECC and using SOAP over HTTPs without client authentication mode between 3rd party system and PI. For this flow, currently we are facing an issue that messages triggered by 3rd party system are reaching in PI and some messages are going to cancelled status directly with error mapping generation error and some messages are showing successfully.
We compared both Cancelled status messages and successful messages, no change in the structure and manually tested in the test tab of mapping. Executing successfully. Sender Channel level also we are able to see some error messages irrespective of success or cancelled as ''SOAP Fault''.
Is this the default behavior of message are directly going to cancelled status in PI for any particular reason..?
Kindly share your thoughts & suggestions.
Regards,
Raj.
Is this the default behavior of message are directly going to cancelled status in PI for any particular reason..?
Answer is Yes.
If it is synchrous, you would have get responce error message in SXMB_MONI of ECC system.
I think in your case SOAP service is unavailable some times, thats is the reson why few messages are going to cancelled with error status.
Check with Webservice team, ask them to change webservice configuration settings for smooth message flow.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Raj,
Is it a synchronous or asynchronous interface? It sounds like a synchronous communication.
Do you see any error message in the audit log?
Ramesh.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ramesh,
This is Asynchronous interface.
3rd party --> PI --> ECC. SOAP adapter using HTTPS without client authentication between 3rd party and PI and IDoc_AAE between PI and ECC.
In communication channel level and in logs it is showing as below.
SOAP: Call failed: com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Message 850da308-14e4-11e5-afe5-0000002f756a(OUTBOUND) expired
Regards,
Raj.
User | Count |
---|---|
85 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.