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.

Similar Messages

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.

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

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.

NFE Boas discussões - Leia antes de postar

EM DESENVOLVIMENTO - SUGESTÕES DE ADIÇÃO E REMOÇÃO SÃO BEM VINDAS ***
Bom dia Pessoal,
Segue abaixo uma compilação de threads de NF-e. Observação: Estas threads estão respondidas, caso tenha algo "parecido" SEMPRE crie uma nova thread, pode até referenciar a thread que você olhou, mas lembre-se de descrever seu problema, versão de SP, background...
ERP Saída:
Aplicação de Notas --> como procurar notas
Criação de NF a partir de documento de devolução - BAdI alteração tipo categoria NFe
Inutilização OK porém Status DOc. Aguardando Resposta
Como fazer entrada no SAP de NFe´s que foram inputadas diretamente na SEFAZ
Dúvidas entre TAXBRA e TAXBRJ
Emissão em congingência por local de negócio e por região NFE 2.0
Erro ao criar BAdI da Nota 1370016
Escolha do tipo de formulario de contingencia (FS x FS-DA)
"212 - Rejeicao: Data de emissao NF-e posterior a data de recebimento" --> timezone
Decouple elimina GAP de numeração?
Relacionamento entre CallRFC do Decouple com J_1BNFECHECKNUMBERRANGES
Performance/Funcionamento J_1BNFECHECKNUMBERRANGES
J_1BNFECHECKNUMBERRANGES - Gap Monitor
Funcao J_1BNFE_CALL_RSNAST00
Dúvida - Job /XNFE/UPDATE_ERP_STATUS
Impressão automática da DANFE
J_1BNFE_CALL_RSNAST00: erro ao ser executada em IN BACKGROUND TASK
ERP Saída - Preenchimento tags:
NF-e Bloco Y dados da Cobrança
Preencher Bloco Y dados da Cobrança na BADI CL_NFE_PRINT
TAG IPI não informada no XML
Dúvida sobre preenchimento de PIS/COFINS
NFE 2.0 - XML_ADI - XML_IMP
Validation error: Field IT_NFE_IMP: V12 (Field NDI)
NFE V2.0 - Tags dSaiEnt & hSaiEnt
Nota de Importação em SP para realizar Desembaraço Aduaneiro. Dicas?
ERP Entrada:
Atualizar dados NFe 2.0 na Miro
Tipo de emissão de NF-e de entrada (XML 2.00)
NFE 10.0:
Blog sobre SAP NFE 10.0 New
Componente Java SLL-NFE-JWS para SLL NFe 10 New
GRC NFE:
Instalação GRC independente do NetWeaver atual
Nao SAP X GRC
Teste dos Cenários de Comunicação com a SEFAZ
Rejeição: 218 x 420
Rejeição por erro 539 Duplicidade de NF-e, com diferença na Chave de Acesso
Problemas ao entrar em Contingência SCAN
Loop programa /XNFE/PROCESS_REPORTS
/XNFE/CORE_KPRO_XML_READ - Problemas com download de documentos XML
Validation error: Field (INFADPROD) -> Varios espaços "000 00 00000 "
GRC versão 7.1
Diagnóstico -unable to create a socket- Represando lotes
NT 2011.002 Hot --> sugestão de código para mascarar dados do destinatário em Homologação
CC-e "MESSAGE_NOT_USED" New
GRC NFE - B2B:
Cadastro de CNPJ para interface NFB2B_procNFe_OB --> sugestão automatização por email
Falha no Envio B2B
B2B Entrada
B2B Versão 2.0
B2B NFE 2.0 - Erro Envio de e-mail dinâmico
Múltiplas NFes de entrada em um email
Texto dinâmico no corpo do e-mail B2B Outbound
GRC NFE - Certificado:
Quebra linha SignatureValue & X509Certificate - Visualizador NF-e
Problema com certificado
HSM e certificados para SSL
GRC NFE - Tunning e outros:
SWF_INB_CONF (2)
SWF_INB_CONF
GRC: Batch com status Request Sent parados --> como criar o alerta do GRC
SAP NFE v2 namespace 006
Business System não aparece Integration Builder
Configuração GRC - NF-e-Main menu
INTERFACE_REGISTRATION_ERROR
SPED:
e-PIS/Cofins

Aproveitando essa thread sobre Nfe.
Um dos grandes problemas relacionados a nfe são as rejeições de nota. Não se encontra em lugar algum descrições mais elaboradas sobre as rejeições, muito menos as formas de solução para cada uma delas. Visando ajudar desenvolvedores e usuários que emitem notas em qualquer sistema, foi criado um "forum" para descrever cada uma das possíveis rejeições de nota, assim como suas possíveis causas e soluções.
Qualquer um pode dar sua contribuição, no entando, como não existe cadastro no site, a resposta precisa ser aprovada pelo moderador.
O "fórum" acabou de entrar no ar e ainda está incompleto. Conto com a ajuda de todos para melhorá-lo. Seque o link:
EDITADO PELA MODERAÇÃO
Obrigado a todos,
Edited by: Henrique Pinto on Sep 2, 2011 10:09 PM

ERRO DE COMUNICAÇÃO COM SEFAZ

Bom dia!
Ao tentarmos enviar uma verificação de status à SEFAZ, ocorre o seguinte erro em PI:
<SAP:Code area="ABAP">INTERFACE_REGISTRATION_ERROR</SAP:Code>
<SAP:Stack>No implementing class registered for the interface (ABAP interface, request message SRVSC_nfeStatusServicoNF_SYNC_OB, request message, namespace http://sap.com/xi/NFE/005a)</SAP:Stack>
Entendemos que seja um problema com a instalação, pois não tivemos erro nos ambientes de D (desenvolvimento) nem no Q (testes).
Verificamos a configuração de integração e o servidor de aplicação no sxmb_adm.
As proxies parecem estar registradas.
Nunca funcionou no ambiente de Produção.
Alguém pode ajudar?
Obrigada,
Fabiana

Fabiana,
A partir de hoje eu e outros usuários estamos recebendo um erro justamente nesse WS:
SRVSC_nfeStatusServicoNF_SYNC_OB
estava funcionando normalmente até sexta-feira, no meu caso no ambiente de homologação, estamos suspeitando que seja algo referente a certificado.
Abs,
Marco

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

ECC = SNC ReplenishmentOrderNotification custom message through SAP PI

Helllo,
I have one issue during proxy call in SNC. We are implementing SNC system with our ECC 6.0 system for PO processing, PO Confirmation Processing. The interfaces used is the standard SNC PI package from SAP through SAP PI; however, we have extended PO IDOCs in ECC for some Z-fields and created a new message type in SAP PI and mapped them properly. The problem, when it reached SNC, I checked the XML message and it was as expected with the new Z-fields but when the inbound proxy is called, I got the following error:
Error during proxy processing An exception with the type CX_SY_DYN_CALL_ILLEGAL_TYPE occurred, but was neither handled locally, nor declared in a RAISING clause The function call of /SCA/BIF_REPLORD_BO failed; a field may have been assigned to the parameter IS_REPLORD_NOTIF whose type is not compatible with this parameter
it seems that the newly generated service interface is not reconginzing the new ReplenishmentOrderNotification message structure with the Z-fields
How can we resolve this issue and make the inbound proxy reconginze the new message stucture?
By the way, I found this Badi: BAdI for ReplenishmentOrderNotification_In? and I have no clue how it works if we need to implement it?
Thank you,

Hi Alan,
Please check below threads.
1. INTERFACE_REGISTRATION_ERROR (inbound ABAP proxy)
2. ABAP ->INTERFACE_REGISTRATION_ERROR for outboud sync ABAP proxy
3. INTERFACE_REGISTRATION_ERROR using File-to-File method
Regards,
Deepak

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

Howto bapi calls

Hello,
I am working on a scenario in which a client (abap proxy) sends a message to the integration server, which dispatches the messages to an rfc-adapter, an bapi call.
Therefore I have read the tutorial, which can be found on this site, but unfortunately I have run into problems. Maybe someone can help me at this point. This is what I did:
1.I have imported the BAPI_FLIGHT_CHECKAVAILABILITY as suggested in the tutorial.
2. I created an Message interface named: U2_BAPI_IF
3. For the output message I have chosen: BAPI_FLIGHT_CHECKAVAILABILITY and for the input:
BAPI_FLIGHT_CHECKAVAILABILITY.Response. I have left the fault message field empty.
4. I did no message mapping, since I want to work with the BAPI Response structure in the abap proxy.
5. The Message interface is defined as outbound synchron.
6.In the Integration Directory I created a Receiver Determination with a Service as a sender, the message interface is U2_BAPI_IF. Additionally I configured a "configured receiver" the client with the BAPI.
7.I created a Interface Determination, for the sender the same entries as above and for the configured Inbound Interface I have chosen BAPI_FLIGHT_CHECKAVAILABILITY and the receiver client
8.I created a receiver agreement.
9. Saved the change list.
10. I have generated the abap proxy for the message interface U2_BAPI_IF, without problems
11. I created the following abap program:
data: lv_msg_raus TYPE ZU2_BAPI_IF_BAPI_FLIGHT_CHECK1,
 lo_proxy TYPE REF TO ZCO_U2_BAPI_IF,
 lv_msg_rein TYPE ZU2_BAPI_IF_BAPI_FLIGHT_CHECKA.
 lv_msg_raus-AIRLINEID = 'AA'.
 lv_msg_raus-CONNECTIONID = '0017'.
 lv_msg_raus-FLIGHTDATE = '20040801'.
 create object lo_proxy.
 call method lo_proxy->execute_synchronous
 exporting
 OUTPUT = lv_msg_raus
 importing
 INPUT = lv_msg_rein.
12. I execute the program and I receive the following error:INTERFACE_REGISTRATION_ERROR, the SAP Stack says:
<SAP:Stack>No implementing class registered for the interface (type ifmmessif, name BAPI_FLIGHT_CHECKAVAILIBILITY, namespace urn:sap-com:document:sap:rfc:functions )</SAP:Stack>
So now my question, do I have to implement a class (proxy) on the receiver side to receive the message and pass it then via bapi call myself, or did I something totally wrong?
I hope somebody can help me,
Thanks
Oliver

Hi Oliver,
I was wondering if you finally got this scenario to work, if Yes. Could you explain how did yo manage to (solve your problem)setup your scenario as described in your earlier note?
Thanks,
Rob.

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.

INTERFACE_REGISTRATION_ERROR

Similar Messages

Maybe you are looking for