on 07-05-2007 7:46 AM
Hi,
I have some issues with ABAP proxies.
The situation I have is the following:
I'm sending data from an ECC 6.0 system to XI 7.0. I trigger and send the data. It leaves the ECC system ok, and comes into XI with the following error:
<i> <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Inbound Proxy
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">INTERFACE_REGISTRATION_ERROR</SAP:Code>
<SAP:P1>ifmmessif</SAP:P1>
<SAP:P2>CreditCommitmentNotification_Out</SAP:P2>
<SAP:P3>http://sap.com/xi/PI/FIN/Operational/Global</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No implementing class registered for the interface (ABAP interface, request message CreditCommitmentNotification_Out, request message, namespace http://sap.com/xi/PI/FIN/Operational/Global)</SAP:Stack>;
<SAP:Retry>M</SAP:Retry>
</SAP:Error></i>
I activated/generated the proxy on ECC side.
One thing to know is that we have in the SLD XI client 001 defined as integration server and client 100 as application server as you can have only 1 integration server.
Thanks for the help!
Where do you get this error? Client 001 or 100?
If Client 100, then you have not created a proxy (using transaction SPROXY) in client 100.
If client 001, then go to transaction SXMB_ADM -->Integration Engine Configuration --> Make the role as "Integration Server".
Regards,
Jai Shankar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Bart,
>>Do I have to create proxies on XI side?
No. You are correct. Proxies always have to be created in Application system.
What is your end to end scenario here?
ECC - XI - ???
I assumed it is ECC - XI(001) - 100. Hence asked to create proxy in client 100.
Make sure, in client 001 in tcode SXMB_ADM, the role has been maintained as Integration Server.
Regards,
Jai Shankar
That will be the issue I think.
I did not (yet) create the proxy on the XI side --> on the application server which is XI client 100.
The only problem now is that I cannot see the software component (SAP APPL) on XI side (client 100) to activate the corresponding proxy.
Any idea how to get this software component visible in transaction SPROXY?
It's an outbound proxy.
Situation now:
ECC system (defined as Application Server in SLD)
--> Message Interface OUTBOUND CreditCommitmentNotification_Out (SAP APPL)
--> Generated and activated!
XI system 100 (defined as Application Server in SLD)
--> nothing defined yet (SAP APPL not found as Software Component in transaction SPROXY)
This is done.
When I do the check in transaction SXMB_ADM I get the following:
<i>Current Configuration (local):
Role of Business System: Application System
Client 001 is Integration Server
Corresponding Integration Server: http://<our_host>:8000/sap/xi/engine?type=entry
System Landscape:
Role of Business System: Application System
http://<our_host>:8000/sap/xi/engine?type=entry
Comparison of Current Configuration with System Landscape
Role of Business System: Current Configuration = System Landscape
Corresponding Integration Server: Current Configuration = System Landscape </i>
The error is situated in the Inbound Proxy. The Inbound Message is ok (green) at XI side (client 100 - Application System). "Call Inbound Proxy" is not ok (red).
This means I have to activate/generate the Inbound Proxy on XI side (100).
The only thing missing now is the Software Component in transaction SPROXY!!!
How is this possible?
Message was edited by:
Bart Bauwmans
Ur ABAP Proxy class is not generated.
Try generating it.
Regards,
Prateek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
79 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.