XIProxy:INTERFACE_REGISTRATION_ERROR

Hi Experts,
I imported a SOAP->PI->RFC sync scenario from the old PI 7.0 server to the new PI 7.1 server.
When I run the scenario for the first time in PI 7.1 I got the error XIProxy:INTERFACE_REGISTRATION_ERROR in the SOAP sender CC at RWB and "No implementing class registered for the interface" in SXMB_MONI.
Looking into to similar threads from this forum, I realease this error is related to issues in the abap proxy generation at SPROXY transaction.
In my case, I am not using proxy at receiver side, but RFC (in a first moment the project would only replicate the scenarios from old server and them do some changes in case itu2019s necessary).
I didnu2019t make any changes in the outbound Service Interface and leave it the way it was imported, as below:
Category: Outbound
Interface Pattern: Stateless (XI30-Compatible) with Point-to-Point enabled checked
Security Profile: Basic
I guess the interface pattern is wrong or maybe Point-to-Point enabled shouldnu2019t be checked, as it seems itu2019s looking for an implementation class in SPROXY.
Can anyone please help?
Thanks in advance,
Daniela

Hi Henrique, thanks for your reply.
Answering your questions:
What is maintained in SXMB_ADM -> Integration Engine Configuration as "corresponding Integration Server"?
I have here the same URL address from the Business System that represents PI in SLD, parameter "Pipeline URL":
http://<server>:<port>/sap/xi/engine?type=entry
Also, does SLDCHECK finishes successfully?
Yes, I got successfull messages in all parameters:
LCR_LIST_BUSINESS_SYSTEMS
LCR_GET_OWN_BUSINESS_SYSTEM
LCR_GET_BS_DETAILS
Summary: Connection to SLD works correctly
EXCHANGE_PROFILE_GET_PARAMETER
Summary: Connection to the XI Profile works correctly
Analysing the trace in SXMB_MONI, I found:
<Trace level="1" type="T">Hop engine name = INTEGRATION_SERVER_PID</Trace>
INTEGRATION_SERVER_PID is the name of Integration BS that was created automatically during the installation. But a different one was created (due to naming conventions) and INTEGRATION_SERVER_PID was deleted from SLD. Could this be affecting something? We performed a cache refresh after the changes.
Thanks,
Daniela

Similar Messages

HTTP Sender Adapter - INTERFACE_REGISTRATION_ERROR

Hi All,
I am getting this error when I am trying to call a synchronous interface using Plain HTTP service. The interface then calls RFC in SAP system which is returned to
The interface is defined and activated in Integration Repository and Receiver agreement has been created for the same in Integration Directory.
I am using the HTTPClient HTTP page to call the sender interface and I am getting "500 Internal Server Error" after sending the message. I doubt whether I am giving sender service correctly. What should be value for sender service? Will it be the XI system on which HTTP service is running?
Am I missing anything?
Please help.
Thanks,
Rahul.
The exact error is as below -
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">INTERFACE_REGISTRATION_ERROR</SAP:Code>
<SAP:P1>ifmmessif</SAP:P1>
<SAP:P2>HTTPOut</SAP:P2>
<SAP:P3>urn:com.xerox.esap.crm.idoc.statusupdate</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No implementing class registered for the interface (ABAP interface, request message HTTPOut, request message, namespace urn:com.xerox.esap.crm.idoc.statusupdate)</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Message was edited by: Rahul
Rahul Aurangabadkar

Hi Rahul,
Check these..
INTERFACE_REGISTRATION_ERROR:No implementing class reg'd for interface
INTERFACE_REGISTRATION_ERROR
cheers,
Prashanth
P.S Please mark helpful answers

HTTP-XI-RFC. INTERFACE_REGISTRATION_ERROR

Dear All,
HTTP<>XI<>RFC scenario is working fine with RFC connected to (Discovery system) Client.001 with role as "Integration Server" but when we try to connect RFC to Client.200 with role as "Application Server" we are getting the INTERFACE_REGISTRATION_ERROR error . We are still new to proxies, so kindly help us isolate the problem.
Below is the error from SXMB_MONI.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> 
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">INTERFACE_REGISTRATION_ERROR</SAP:Code>
<SAP:P1>ifmmessif</SAP:P1>
<SAP:P2>MI_FileName</SAP:P2>
<SAP:P3>http://sap.com/xi/XI/DataTransfer</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No implementing class registered for the interface (ABAP interface, request message MI_FileName, request message, namespace http://sap.com/xi/XI/DataTransfer)</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Below are the system(clients) used in the scenario.
- HTTP (HTTP Web Client)
- XI (Client.001) role of system in SXMB_ADM is "Integration Server".
- ERP (Client.200) role of system in SXMB_ADM is "Application Server".
In the ERP(client.200) should we have to
- activate PROXY for the interface/namespace (using trx. sproxy) ??
- trigger the PROXY with some reports ??..etc
Kindly advice the steps we need to follow..
Thanks & Regards,
Nameeth

HTTP<>XI<>RFC scenario is working fine with RFC connected to (Discovery system) Client.001 with role as "Integration Server" but when we try to connect RFC to Client.200 with role as "Application Server" we are getting the INTERFACE_REGISTRATION_ERROR error . We are still new to proxies, so kindly help us isolate the problem.
Are you using the HttpXIRFC to the news clnt 200, this is not proxy interface right...if youa re using the ABAP Proxy then
it should be Hrrp>XI-->XI Adapter( Proxy)
In the ERP(client.200) should we have to
- activate PROXY for the interface/namespace (using trx. sproxy) ?? yes you ahve to activate the Sproxy TC in the clnt 200 and select the inbound interface from the concerned namespace then genrereate the Proxy.....
in you ID you have to use the XI adapter as receiver adapter.
- trigger the PROXY with some reports ??..etc
you will get the mehtond name and the proxy Strucutre in that method you have to write your ABAP code and writ your logic....
check this links for any information:
You can start with these....
Activating ABAP proxies:
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
ABAP Proxies in XI (Client Proxy)
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
/people/siva.maranani/blog/2005/04/03/abap-server-proxies
Client Proxy - /people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
Server Proxy - /people/siva.maranani/blog/2005/04/03/abap-server-proxies

ABAP - INTERFACE_REGISTRATION_ERROR for outboud sync ABAP proxy

Hi,
I have created ABAP sync client proxy in R/3 and trying to test using abap report. I am facing following error in XI sxmb_moni.
I have created client proxy for outbound sync interface, however the error is pointing inbound sync interface (ie QAChkR3_Sync_Mimicking).
Even I tried creating proxy for given inbound interface but same error exists.
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">INTERFACE_REGISTRATION_ERROR</SAP:Code>
<SAP:P1>ifmmessif</SAP:P1>
<SAP:P2>QAChkR3_Sync_Mimicking</SAP:P2>
<SAP:P3>http://ls.att.com/Exacta/QACheck_Mimicking</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No implementing class registered for the interface (type ifmmessif, name QAChkR3_Sync_Mimicking, namespace http://ls.att.com/Exacta/QACheck_Mimicking )</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please help.
Pratibha.

Hi Krishna,
Proxy in R/3 is reactivated still the error persists.
There are few more o/b proxies which are running fine.
Even LPCONFIG txn is done properly.
I wonder why the error is for inbound proxy when I am trying to test outbound sync proxy.
I dont have sap marketplace id to check the given notes. Will you pls brief about it.
Pratibha.

ABAP.INTERFACE_REGISTRATION_ERROR while run SOAP - PI - RFC - R3 scenario.

Hi all,
My scenario is a third party send a request (through SOAP message) to PI, then PI will made RFC call to R3 system to retrieve data. (call BAPI_CUSTOMER_DISPLAY).
At IR i've created.
Namespace: http://send
1. Data type: DT_request (which include customer number )
 Data type: DT_response
2. Message type for 2 data types above.
3. Message Mapping for request: MT_request => BAPI_CUSTOMER_DISPLAY and for response: BAPI_CUSTOMER_DISPLAY.response => MT_response.
4. Service Interface: SI_BAPI_CUSTOMER_DISPLAY_REQUEST: Outbound, stateless and synchronous.
 Operator Mapping: which mapping SI_BAPI_CUSTOMER_DISPLAY_REQUEST and SI_CUSTOMER_DISPLAY_RESPONSE (please see 6).
At business system B (on R3 WS ABAP).
Namespace: http://rec
5. Importing BAPI_CUSTOMER_DISPLAY rfc.
6. Inbound Service Interface: SI_BAPI_CUSTOMER_DISPAY_RESPONSE: Inbout, statelss and synchronous (corresponding to 4.)
And then, at ID I've created:
7. SOAP communication channel (cc) for business system A. This cc is sender.
8. RFC communication channel for business system B. This cc is receiver.
9. Sender agreement, receiver determination...
10. Generate WSDL and got the ws url is: http://sapsrv:50100/sap/xi/engine?type=entry&version=3.0&Sender.Service=BVI&Interface=http%3A%2F%2Fsend%5ESI_BAPI_CUSTOMER_DISPLAY_REQUEST
Then, I tried to test with XML spy but get this error:
<s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
 <context/>
 <code>ABAP.INTERFACE_REGISTRATION_ERROR</code>
 <text>No implementing class registered for the interface (ABAP interface, request message SI_BAPI_CUSTOMER_DISPLAY_REQUEST, request message, namespace http://send)</text>
PS: - I've generated all proxy at r3 system. (via tcode Sproxy)
 - And Sxmb_adm I've set Business System is Application System.
Please help me to fix this error.
Many thanks.

>>ABAP.INTERFACE_REGISTRATION_ERROR
You did not complete proxy objects coding yet.

INTERFACE_REGISTRATION_ERROR

Hey guys,
Any answers for this error.
I am using XSLT transformation for mapping. I tested my mapping and the transformed message is the one that is expected by the IDoc.
Thank You.
Sumit.
<?xml version="1.0" encoding="utf-8" ?>
- <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
- <asx:values>
<ERROR href="#o77" />
</asx:values>
- <asx:heap xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:abap="http://www.sap.com/abapxml/types/built-in" xmlns:cls="http://www.sap.com/abapxml/classes/global" xmlns:dic="http://www.sap.com/abapxml/types/dictionary">
- <cls:CX_XMS_SYSERR_PROXY id="o77">
- <CX_ROOT>
<TEXTID>392B46E58AC0F445B64639726E2A3D85</TEXTID>
<PREVIOUS />
<KERNEL_ERRID />
- <INTERNAL_SOURCE_POS>
<PROGID>396</PROGID>
<CONTID>699</CONTID>
</INTERNAL_SOURCE_POS>
</CX_ROOT>
<CX_STATIC_CHECK />
- <CX_XMS_SYSTEM_ERROR>
<ID>INTERFACE_REGISTRATION_ERROR</ID>
<P1>ifmmessif</P1>
<P2>ZPSCD_ACCOUNT_LOADACCOUNT.ZPSCD_ACCOUNT_LOADACCOUNT01</P2>
<P3>urn:sap-com:document:sap:idoc:messages</P3>
<P4 />
<INFO />
<CATEGORY />
<AREA />
<RETRY />
</CX_XMS_SYSTEM_ERROR>
- <CX_XMS_SYSERR_PROXY>
<CO_AREA_ABAP>ABAP</CO_AREA_ABAP>
</CX_XMS_SYSERR_PROXY>
</cls:CX_XMS_SYSERR_PROXY>
</asx:heap>
</asx:abap>

Hey Sameer,
I am not using ABAP Pproxies.
The error comes when I try to test the scenario using the transaction SXI_SUPPORT.
I am sending an IDoc to the sap system. I imported the IDoc structure from the SAP system. I populate the IDoc structure using XSLT transformation from the source message.
Thank You.
Sumit.

XIProxy:PARSE_APPLICATION_DATA , error in soap sender communication channel

HI
I am having soap toABAP proxy synchronous interface , when i test from soap UI tool i am getting the below errro . can any body help me with this error
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
 <SOAP:Body>
 <SOAP:Fault>
 <faultcode>SOAP:Server</faultcode>
 <faultstring>Server Error</faultstring>
 <detail>
 <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
 <context>XIAdapter</context>
 <code>ADAPTER.JAVA_EXCEPTION</code>
 <text>com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIProxy:PARSE_APPLICATION_DATA:
 at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1178)
regards
sandeep
Edited by: pendyalas on Jul 27, 2011 5:01 PM

Hello,
can you check the message format defined in repository.
Regards
Vivek

[GRC 10.0] Erro no cenário NFB2B - XIProxy

Daniela,
No GRC 10, o paylod do NTB2B foi modificado, sendo assim você precisa converte-lo, via JavaMapping ou XSLT.
Saludos,

Henrique,
Depois de muita tentativa e erro, o cenário funcionou com o Payload Swap Bean, mas com uma configuração diferente daquela que estava nos blogs que mencionei, referente ao keyName que usei payload-name.
A aba de Module ficou assim:
Number     Module Name                               Type                Module Key
1     AF_Modules/PayloadSwapBean                    Local Enterprise Bean     swap
2     sap.com/com.sap.aii.adapter.mail.app/XIMailAdapterBean     Local Enterprise Bean     mail
Module Configuration
Module Key     Parameter Name     Parameter Value
swap          swap.keyName     payload-name
swap          swap.keyValue     MailAttachment-1
Agora eu vejo que as Notas estão nas tabelas /XNFE/INNFEHD e /XNFE/INNFHIST, embora com ACTSTAT = 03 "Technical Error in Last Process Step".
Elas ainda não estão aparecendo no monitor Fiscal Workplace - NF-e, mas acredito que pode ser algo relacionado aos objetos de autorização das novas roles NFe In. Vou dar uma investigada nesses dois pontos e qualquer coisa eu abro uma nova thread.
Obrigada,
Daniela

Problemas na postagem Eventos para entrada NFE

Olá Experts ,
FOr entrada NFE estamos usando um módulo personalizado para extrair a NFE do Mail Box .
Depois que estamos usando mapeamento XSLT para separar a mensagem para eventos NFE e NFE . Nesta etapa NFE é postado com sucesso, mas para postar eventos que estão recebendo erro como: erro ao analisar a mensagem XMB recebido.
O código XSLT é :
<? xml version = "1.0" encoding = " UTF-8" >
< xsl: stylesheet versão = "1.0" xmlns : xx = xmlns " XXXX Nome Espaço xxx" : split = " http://sap.com/xi/XI/SplitAndMerge " xmlns : xsl = " http://www.w3 .org/1999/XSL/Transform " >
<xsl:output method="xml" indent="no" omit-xml-declaration="no"/>
<xsl:template match="/split:Messages/split:Message1/bg:nfeFromSenderMasked">
<split:Messages>
<split:Message1>
<xsl:for-each select="./bg:procNFeMulti/bg:procNFeStr">
< xsl: " . " valor de selecione = disable- output -escaping = "yes" />
</ xsl: for-each >
< / split : Message1 >
<split:Message2>
<xsl:for-each select="./bg:procEventoNFeMulti/bg:procEventoNFeStr">
< xsl: " . " valor de selecione = disable- output -escaping = "yes" />
</ xsl: for-each >
< / split : Message2 >
< / split : Mensagens>
</ xsl : template>
</ xsl: stylesheet>
Depois de analisar mais em NWA i se hte seguintes logs:
Os dados de resposta HTTP é = <soap:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Header>
< / SOAP : Header >
<soap:Body>
< Soap: Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>SOAP:Client</faultcode><faultstring>Error durante a conversão de mensagem XI </ faultstring > <faultactor> http://sap.com/xi/XI/Message/30 </ faultactor > <detail> < SAP : Erro de SOAP : mustUnderstand = "1" xmlns : SAP = " http://sap.com/xi/XI/Message/30 "> <SAP:Category> XIProxy </ SAP: Category> < SAP : Code area="ABAP">INTERFACE_REGISTRATION_ERROR</SAP:Code><SAP:P1>ifmmessif</SAP:P1><SAP:P2>ETB2B_procEventoNFe_IB</SAP:P2><SAP:P3>http://sap.com/xi/NFE/006</SAP:P3><SAP:P4/><SAP:AdditionalText/><SAP:Stack>No classe de implementação registrada da interface (interface de ABAP , mensagem de pedido ETB2B_procEventoNFe_IB , mensagem de solicitação , namespace http://sap.com/xi/NFE/006 )
</ SAP: Stack > </ SAP: Error> < / detail > < / SOAP : Fault >
< / SOAP : Body>
</ Soap: Envelope >
Por favor me ajude como resolver esse erro como eventos não estão sendo postados.
obrigado

Olá.
Provavelmente o Cenário configurado está incorreto "ETB2B_procEventoNFe_IB".
Para Inbound deve ser configurado o Cenário EFB2B (Event From B2B), o ETB2B (Event To B2B) serve apenas para o Outbound.
Abraço.
Pedro Baroni

Error in FILE 2 Proxy Scenario

Hi All,
I am doing File to Proxy Scenario i am getting following error
Could any one provide the solution for this.
*<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>*
*- 
- <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>MI_Emp_Sender</SAP:P2>
<SAP:P3>Namespace</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No implementing class registered for the interface (ABAP interface, request message MI_Emp_Sender, request message, namespace )</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Thanks in Advance
Mahesh
</SAP:Error>
Edited by: Mahesh Reddy on Jul 10, 2008 12:47 PM

Hi Mahesh,
1) Use SPROXY transaction.
Menu-> Proxy -> Activate All.
2) check in the interface determination if u are using correct
inbound interface.
3) If this if fine....try deleting all proxy objects of the interface
and create new.
Regards,
Praveen K

Problem in ABAP proxy

hai all,
iam doing a abap proxy scenario in the following flow.
Flow: XI (Client 800) -
> XI (Client 001) ---> XI (Client 800)
now when iam trying to send the data from 800 client to 001 client
in 001 client sxmb_moni
it is giving one error
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">INTERFACE_REGISTRATION_ERROR</SAP:Code>
<SAP:P1>ifmmessif</SAP:P1>
<SAP:P2>mi_flietdata_OA</SAP:P2>
<SAP:P3>urn:proxytoproxy</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No implementing class registered for the interface (ABAP interface, request message mi_flietdata_OA, request message, namespace urn:proxytoproxy)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
can any one solve this problem.
regards,
Madhav Poosarla.

hai sumit,
i have generated proxy object as a local object,
previously i have created 4 levels of package
Structure Package(ZXI_PACKAGE)----
Level1
 Main Package(ZSCSLSAP)----
Level2
 Sub Package(ZSIVA_SCSLCOMP)----
Level3
 SubPackage (ZSIVA_SCSLCOMP_PROXY2PROXY)--Level4
and i have added SAI_TOOLS to
ZSIVA_SCSLCOMP_PROXY2PROXY sub package,
at that time i have tried to add SAI_TOOLS to ZXI_PACKAGE but it was not allowed.
now i will create one more package hirachy and and i will try to execute again.
now i will delete my outbound proxy and will generate it again.
yes, mi_flietdata_OA is outbound interface.
thanks & regards,
Madhav Poosarla.

Error in integration engine prosessing

Hi
I am doing proxy to fille interface for testing purpose in RWB in integration engine i test message tab i have given proper entries and send the message.In SXMB_MONI intially status of flag is green i have registered the queues in sxmb_adm then status has changed to red i opened the message it is showing as follow.
In Moni in place of receiver service interface it is showing sender service interface.But i have configured correctly
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <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>SI_PROXY_SENDER</SAP:P2>
<SAP:P3>urn:SESA:PROXY:FILE</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>No implementing class registered for the interface (ABAP interface, request message SI_PROXY_SENDER, request message, namespace urn:SESA:PROXY:FILE)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Regards
Praveen

My problem was solved my R3 RFC destination was not pointing to client of integration engine.I have corrected the same my issue was solved
Regards
Praveen

Problems in synchronous scenario

Hi,
I am woking on a synchronous SOAP- PROXY scenario. The XI outbound interface has been exposed as web service which is invoked by .NET application to send the request. The inbound interface is ABAP proxy which is retrieving the data from R3 tables based on the selection criteria in request and sending back the same as response. While testing the scenario i am getting the following error in SXMB_MONI:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">INTERFACE_REGISTRATION_ERROR</SAP:Code>
<SAP:P1>ifmmessif</SAP:P1>
<SAP:P2>MI_DSSRes_SAP_Equipment</SAP:P2>
<SAP:P3>urn://DSS_SAP_02/GetEquipment</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No implementing class registered for the interface (ABAP interface, request message MI_DSSRes_SAP_Equipment, request message, namespace urn://DSS_SAP_02/GetEquipment)</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Can you help me as I am not able to resolve this error.
Also I need the steps for IR configurations for a synchronous scenario.
Thanks in advance.

>
sriparna1 wrote:
> It has been reactivated. But still not working.
>
> We have defined the incoming message from .Net application as Inbound Interface Sync . the message received from r/3 via proxy is defined as outbound sync .We have developed A server proxy on inbound interface and the error we are getting is it is trying to search for the implementation of the outbound Interface. It should actually look for the Inbound proxy implementation as this proxy in its output parmeter sends back the output structure.
Since it is SOAP_to_PROXY .... the MI from .NET should be OUTBOUND Synchronous and that going into SAP should be INBOUND Synchronous.
Regards,
Abhishek.

Unable to send the message from XI to ECC

Hi experts,
I am having a issue whereby the message of my XI server (I have login into the XI server) is shown as below in SXMB_MONI.
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">INTERFACE_REGISTRATION_ERROR</SAP:Code>
<SAP:P1>ifmmessif</SAP:P1>
<SAP:P2>MI_ApArSource2SAP</SAP:P2>
<SAP:P3>http://com.starhub/sapapar</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No implementing class registered for the interface (ABAP interface, request message MI_ApArSource2SAP, request message, namespace http://xxx/sapxxx)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I believe it's not the problem of one of my interface, since I have tried other interface as well, all having the same error. I suspect there is something wrong with the integration server.
Pls advice. Need it desperately.
Thanks.
Cheers,
Isaac.

Hi,
Go to SXMB_ADM.
Execute Integration Engine
EDIT-> Change Global configuration data
Select the Role of Business System is Integration Server.
Regards,
Sreenivas

PO Response XML generation

Hi,
I are working EBP-SUS Extended Classic Scenario having EBP and SUS on same server SRM Server 7.0 but differenct clients.
I am tring purchase order response from SUS Supplier to SRM in ebp-sus scenario while before this PO is correctly transferred from EBP to SUS by XML communication. We are using XML communication by SRM to SUS and SUS to SRM.
When i sent POR from SUS I am having Purchase Order Response in BBP_PD by selecting BUS2232 in SUS, is it correct Object for PO Response? Or it should be BUS2209?
and None XML message triggered for PO Response (checked in sxmb_moni in sus) while number range and transaction type is maintained in SUS. Is any method or report to trouble shoot for POR?
<<Text removed>>
Hope to hear from you all using POR approval workflow in this scenario.
Thanks and Regards,
Pawan Keshwani
Edited by: Matt on Jul 30, 2011 7:11 AM

Hi,
Issue is resolved by the the help of below forum :
SUS PO confirmations.
SENT :SENT was not maintained in SUS Supplier System.
XML Messege is generating fine SXMB_MONI in SUS and XI but for *I am getting the below error at SXMB_MONI in EBP System* :
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <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>PurchaseOrderConfirmation_In</SAP:P2>
<SAP:P3>http://sap.com/xi/GovernmentProcurement</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No implementing class registered for the interface (ABAP interface, request message PurchaseOrderConfirmation_In, request message, namespace http://sap.com/xi/GovernmentProcurement)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Kindly help me guys, if you face this before.
Thanks.
Regards,
Pawan Keshwani

XIProxy:INTERFACE_REGISTRATION_ERROR

Similar Messages

Maybe you are looking for