on 01-13-2016 3:44 PM
Hello,
I am Facing problem while exutiong the Scenario : SAP ECC-->PI ( ABAP proxy). : ABAP proxy to File.We are finalizing the upgrade PI 7.40
And ther I have this message :
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30"xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
</SAP:Error>
My configuration wich was working fine in SAP PI 7.10 is :
Any Idia Please ?
Hello Mou,
As per Trace log, it seems that there is some problem with the binding (inbound with respect to PI) between ECC and PI system.
I am sure if there is a problem with inbound binding, there must be a problem with outbound binding as well.
So in ECC system, please run the t-code SLDCHECK, and verify whether there is any error or not.
If it does, then it will mean that the technical systems (ECC is not placed properly in SLD).
On the other hand, if it is placed, you can run the t-code RZ10 in PI and place the ECC system.
Regards,
Souvik
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Mou,
Please try the below.
1. In SXMB_MONI of ECC system, open the message and double click on the Trace File & search for "PLSRV_CALL_INTEGRATION_SERVER". You will see something like URL=dest://XXX. The destination XXX should be of type G created in ECC to your PI system.
2. In the Integration Directory of your XXX(PI system), make sure you have ICO configured for the combination of Business System, Interface and Namespace showing in the error.
3. If the above 2 steps are fine, then make dummy changes to your ICO and reactivate it.
4. Make sure the Cache is in Green after reactivating the ICO.
5. Restart the Proxy Sender channel and try to reprocess the failed Asynchronous message from ECC.
Regards,
Priyanka
Hello,
Thank you so much for this response.Indeed I verified all these points. I find a problem in SXI_CACHE:
I folowed this link Create Destinations on the ABAP Server - Configuring Process Integration (PI) After Installation - S... to check the missing RFC destination , but I have 403 error, even if the user PIISUSERis not locked.
Any idea please ?
As per the Error Screenshot, it looks the exchange Profile parameters are not configured correctly.
Go to Administration-->Directory-->ExchangeProfile-->Under connections-->set the value of the parameter "com.sap.aii.connect.directory.name" to full qualified server name of your PI system.
---Priyanka
Hello Mou,
Other than the upgrade of PI, you additionally need to assign client to logical system and also connect ECC with PI (current version) system in SALE t-code in my opinion with respect to PI 7.4.
Regards,
Souvik
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mou,
As explained in your earlier thread :
The Configuration screenshot which you have put is of 7.1 but when it comes to 7.4 we need to create a ICO with all required configuration details , configuration in 7.1 and 7.4 is not same
7.1 includes : ID ,RD ,RA ,RC.
7.4 includes : ICO ( which is nothing but combination of ID,RD.SA,RA)
and in 7.4 you need to create sender soap channel with SOAP adapter and message protocol 7.4
Br,
Manoj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Mou ,
Check this document on how to create ICO in PI .
And for the required configuration in ECC check the one which raghu shared.
Br,
Manoj
Hi Mou,
Can you please check in ERP SXMB_ADM transaction the below configuration is pointing to integration engine or adapter engine??
I think based on your error it is pointing to adapter engine, if your PI 7.4 is dual stack installation you can change the above configuration pointing to integration engine then your previous classical configuration works.
Regards,
Praveen.
Hello Mou,
Can you check the RFC destination used in SXMB_ADM?
Is it of connection type G? Also the URL used in the RFC destination must be as below -
/XISOAPAdapter/MessageServlet?ximessage=true
And the SAP_PROXY_ESR must be created and SPROXY tcode must be working.
The error says that, message is not being received in the target system. Hence the error must be with the RFC destination.
Regards,
Nitin
User | Count |
---|---|
84 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
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.