Error in SXI_MONITOR

HI all, im havving a problem.
XI server in runnig, my problems is becuase there no data in sevice,manespace,interface in transaction SXI_MONITOR, nether log any message, wherever SLDCHECK has no any kind of error(all green.)
what can i do?
Rgds
RP

yes, PI is not logging any message.and i can get access to data from services,interface name and interface namespaces in the filter section
the log of SLD is next
Exchange Infrastructure: Test LCR Connection
Properties of RFC destination SAPSLDAPI
RFC host:
%%RFCSERVER%%
program id:      SAPSLDAPI_XD0
gateway host:
gateway service:
Testing the RFC connection to the SLD java client...
RFC ping was successful
SLD server access settings:
host name:   <server>
port number: 50100
user       : yp00877
Use transaction SLDAPICUST if you wish to maintain the SLD server access data
Launching the SLD GUI in a separate browser window...
=> Verify in the browser GUI that the SLD is in a healthy running state!
Calling function LCR_LIST_BUSINESS_SYSTEMS
Retrieving data from the SLD server...
Function call terminated sucessfully
List of business systems maintained in the SLD:
BI
AS400
TBIT40_LEGACY_BS_01
XI_Customer_System
suarbuldsdd01_ZB0
LD0ARG100
SAABA01
(...more...)
Calling function LCR_GET_OWN_BUSINESS_SYSTEM
Retrieving data from the SLD server...
Function call terminated sucessfully
Details of own business system BS_XD0ARG200
caption = BS_XD0ARG200
product =
IS-URL = http://server:8001/sap/xi/engine?type=entry
Summary: Connection to SLD works correctly
Now checking access to the XI Profile
Properties of RFC destination LCRSAPRFC
RFC host:
%%RFCSERVER%%
program id:      LCRSAPRFC_XD0
gateway host:
<server>
gateway service: sapgw01
Testing the RFC connection to the SLD java client...
RFC ping was successful
Calling function EXCHANGE_PROFILE_GET_PARAMETER
Retrieving data from the XI Profile...
Function call terminated sucessfully
Retrieved value of
section   = Connections
parameter = com.sap.aii.ib.server.connect.webas.r3.ashost
-> value =
Summary: Connection to the XI Profile works correctly
null

Similar Messages

Adapter.soap_exception (parsing error) in sxi_monitor

Hello everyone.
I am getting the next error in the TC sxi_monitor when Im sending an Idoc:
soap fault: Server did not recognize the value of HTTP Header SOAPAction: http://wsceresdes/WSCeres/AsientoInsert/Servicio.asmx
I have changed the *.asmx file (external definition) that this interface uses, because they add one node in the xml receiver, and then I mapped it.
This idoc goes from Sap to non sap system.
I cheked the mapping result and there isnt any error, its all working fine.
What am I missing? Where is the problem?
Edited by: Claudio Carrer on Oct 8, 2008 8:32 PM

You have a SOAP receiver channel and you have put a parameter SOAPAction which is not valid.
Figure out, which SOAPAction you really need and put that value. You find the SOAP action in the WSDL in an attribute with same name.
Regards
Stefan

Technical error in sxi_monitor

Hello everybody.
I'm getting this error in TC sxi_monitor:
<SAP:Code area="PARSING">ADAPTER.SOAP_EXCEPTION</SAP:Code>
<SAP:AdditionalText>soap fault: Server was unable to process request. --> There is an error in XML document (0, 0). --> The data at the root level is invalid. Line 1, position 1.</SAP:AdditionalText>
I'm sending an Idoc from SAP system to NON-SAP system.
A strange thing: I'm sending anything, with lots of data or without data, and the error is the same.
I can't understand why is this happening, because I'd check the xml and it's fine (the non sap system is waiting that kind of xml structure).
And I got one doubt: who is giving me this message? The web service? Or the non sap system?

I'm importing a .wsdl from the URL that the WS is providing me.
I havent got any message type or data type in here (just message interface) because Im importing this in the external definition.
The only data types existing in this interface are the default's one (exchangeFaultData and ExchangeLogData).
All my interfaces are working ok and they are like this one, that is the misterious thing...
I review all step by step 2 times, and I havent found errors or difference with others similar to this one.

BPM Mapping error in SXI_MONITOR Message scheduled on outbound side.

When I try to process this message i get an error.
Message scheduled on outbound side.
I am using a BPM.
MI_Source -> MI_Receive_BPM -> MI_TRANS1_BPM -> MI_TRANS2_BPM -> MI_TARGET
Using EOIO in the send step Queue Name: cases
If I remove MI_TRANS2_BPM the message reaches the bpm, but with both transformation in the BPM the message gets an error in the queue where I get a green flag 'Message Scheduled on the outbound side"
This BPM was working on Friday but hasn't worked since. There have been no changes to the my development XI environment.
Some things that i have tried: Clearing the Queues (smq2), Redoing the entire scenario, clearing cpa cache.
Please help.
Thanks
Chirag

Hi,
MI_Source -> MI_Receive_BPM -> MI_TRANS1_BPM -> MI_TRANS2_BPM -> MI_TARGET
Any specific need to have the above design pattern....you can also try:
MI_Receive_BPM -> MI_TRANS_BPM -> MI_TARGET
You can use the message that you initially receive and apply all the necessary transformation on it and the map it to the target structure....
As you mentioned that if you remove MI_TRANS2_BPM your message is executed successfully...it means that the BPM transformation 2 is waiting for some event / Message....
If you need to go by the same design then you can follow the below steps to resolve the problem:
1) Check the return code of BPM in SXI_CACHE...it should be 0
2) Check for any errored instance of your BPM in SWWL (as mentioned in above posts)
3) Open the corresponding Queue and see for the messages stuck in the Queue....your Queue may be blocked....your BPM will be using a particular Queue and if any message is stuck in the Queue then all the messages that follow will get stuck in the Queue....
Now if it is only your BPM that is using this particular Queue then Delete the Queue (applicable to development environment....do not try in QA or Production environment)
4) In SXMB_MONI click on "PE" and open the Graphic Flow to see where actually your BPM has failed (possible only if the message has entered the BPM.
Regards,
Abhishek.

Error status on outbound side

Hi experts,
I am in JDBC to IDOC scenario and right now i face following error in SXI_MONITOR (black and white flag in status field BUT Red flag in outbound status):
"Message has error status on outbound side"
This is a heavy interface (up to 8MB) but, in the past, we did not receive this error. I saw that there is an entry in SM58 from the PIAFUSER that says "Lock table overflow"
Thus, I set the parameter enque/tablesize up to 8192 MB but after restarting the system it did not work either, a new entry in SM58 is shown.
If i analyse the runtime tab of the response of the message i can see
<SAP:AdapterStatus>007</SAP:AdapterStatus> --> for an erroneous interface execution (payload=7,2MB)
<SAP:AdapterStatus>006</SAP:AdapterStatus> --> for a successful execution (payload 6.5 MB)
Can anyone plz, help me on this?
I cannot explain why we did not face this in the past.
Can you please explain how the lock table works? and what does the overflow means?
Thanks a lot in advance and best regards,
David

Hi Sai,
Ive checked what you mentioned but cannot see the point there. Maybe you can help me:
Enqueue Operations     847
rejected     17
Error occured     0
Dequeue Operations     604
Error occured     0
Dequeue All Operations     661
Cleanup Operations     0
Backup Operations     1
Read Operations     21
Compress Operations     0
Verify Operations     0
Records written     58408
to the backup file     2
Maximum Number of Lock Owners     58406
Maximum Fill level     4
Current Fill Level     0
Maximum Number of Lock Arguments     58406
Maximum Fill level     14
Current Fill Level     0
Maximum Number of Lock Entries     58406
Maximum Fill level     14
Current Fill Level     0
Update; Fill Level at Maximum     1
Current Fill Level     0
Time in Lock Table /Seconds     0.073970s
Wait for Lock Table /Seconds     1.691441s
Time in Lock Server /Seconds     0.000000s
Besides, i dont think it is gonna be a matter of disk spaces as all of them have, at least, 3.0 Gb of free space.
Any other clue? I increased the enque/table_size up to 65 MB and the lock table overflow in SM58 still remains!!!
Thanks a lot and best regards,
David

Acknowledge Contains System Errors

Dear Friends,
I am sending the MATMAS idoc from ECC6.0 to LocalSystem using XI.
I got the error in SXI_MONITOR i.e
Acknowledge contains system errors.
R/3 side :
1.created RFC destination for XI
2.PORT For XI
3.Partnerprofile For XI
4.Distribution model view For XI
XI side:
1.created RFC destination For R/3
2.PORT For R/3
In I.D i created Business service for Local System and Business System for R/3 system.
I did this , I am Facing this problem(Acknowledgement contains system errors).
Next What Should I do.
How to resolve this issue.
Friends suggest me please.
Regards,
Shalini Shah.

Hi
Check it out IDX2 - IDoc Meta Data and IDX5 - Idoc Messages received in XI.
I guess Your message have been processed successfully(Black & White Flag).But acknowledge ment contains the system errors.
Go through the below link
http://help.sap.com/saphelp_nw04/helpdata/en/44/932e8896b610bbe10000000a422035/frameset.htm -- Configuring Acknowledgment Requests and follow the steps under Procedure.
You will able to solve u r problem.
Cheers
Veera

Erro B2B de entrada

Olá Pessoal,
Não sou PI, e não tenho um aqui disponível no momento... por isso preciso da ajuda de um...rsrs
Estou com um erro no recebimento de NF-e via e-mail, meu B2B está configurado para receber e-mails com vários anexos, porém ele lê o PRIMEIRO XML válido e descarta o restante dos arquivos.
Está configurado para se comportar desta forma...
Porém, tenho um e-mail com três arquivos:
41110178956968002712550050000071344110034264-nfeProc.xml
41110178956968002712550050000071344110034264.xml
41110178956968002712550050000071344110034264.pdf
O que meu sistema deveria fazer era ler o primeiro XML válido e descartar o restante dos arquivos, porém ele não lê nenhum e na SXI_MONITOR ele dá um log de erro, porém como não so PI não consigo interpretá-lo:

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="IF_DETERMINATION">NO_IIF_CASE_ASYNC</SAP:Code>
<SAP:P1></SAP:P1>
<SAP:P2></SAP:P2>
<SAP:P3></SAP:P3>
<SAP:P4></SAP:P4>
<SAP:AdditionalText></SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace=""></SAP:ApplicationFaultMessage>
<SAP:Stack>Unable to find an inbound interface</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Na SXI_MONITOR:
Na coluna "Error Category" está a seguinte informação: IF_DETERMINATION
Na coluna "Error ID" está a seguinte informação: NO_IIF_CASE_ASYNC
Alguém poderia me ajudar por favor?
Muitíssimo obrigado,
Mateus.
Edited by: MATEUS PARREIRA GUIMARÃES on Feb 7, 2011 7:05 PM
Edited by: MATEUS PARREIRA GUIMARÃES on Feb 7, 2011 7:05 PM

Então Henrique,
Não sei, achei estranho por isso, não tem nada indicando...
Para ver se consigo ajudar a identificar vou lhe falar as pastas que tenho:
Interface Determination (Bandeirinha vermelha com erro: Sistem Error - Manual Restart Possible)
      SOAP Header
            Main
            ReliableMessaging
            Error
            HopList
            RunTime
            PerformanceHeader
            Diagnostic
            Trace
      SOAP Body
            Manifest
      Payloads
            MailMessage ( multipart/alternative;boundary="----=_NextPart_001_0004_01CBC
            MailAttachment-1 ( text/xml;name="41110178956968002712550050000071344110034
            MailAttachment-2 ( application/pdf;name="4111017895696800271255005000007134
            MailAttachment-3 ( text/xml;name="41110178956968002712550050000071344110034
Qual conteúdo você quer que eu envie?
Abs.
Mateus.

CC-e: Etapa não está em ordem

Olá pessoal,
Estamos implementando a CC-e, e realizamos todas as configurações no ECC, e estamos no SP20 do GRC.
No ECC a CC-e é criada normalmente e enviada ao GRC, porém a mesma fica no monitor GRC e não é enviada à SEFAZ...
Quando checamos a aba de "síntese de status" do monitor de evento da CC-e, a mesma fica com DUAS linhas conforme abaixo:
Status     Atividade     Ctg.proc.     Descrição do status     Texto info
Assinar evento          Criação          Etapa não está em ordem     Em branco
Criar CC-e          Criação          Etapa em ordem
Quando checamos a aba de "Histórico", a mesma fica com TRÊS linhas conforme abaixo:
Atividade     Ctg.proc.     Descrição do status     Texto info                                                            Data de execução     Usuário     Status
Assinar evento     Criação          Etapa não está em ordem     SAP NetWeaver PI notifica erro ao assinar o evento.                                   13.12.2011 16:44     PISUPER     Etapa não está em ordem
Assinar evento     Criação          Etapa em ordem          Em Branco                                                            13.12.2011 16:44     PISUPER     Etapa em ordem
Criar CC-e     Criação          Etapa em ordem          Evento do tipo 110110 para 31111220146676000367550010000658121905067763 é criado com o nº sequencial 01     13.12.2011 16:44     PISUPER     Etapa em ordem
Na grid com informações gerais sobre a CC-e, as colunas que são preenchidas ficam descritas conforme abaixo:
Coluna Status global: incorreto
Coluna Zugriffsschlüssel: 31111220146676000367550010000658121905067763
Coluna Tipo de um evento: 110110
Coluna Nº sequencial de um evento: 1 (para todas as CC-es fica 1)
Coluna Momento da emissão: 13.12.2011 15:16
Coluna Momento do registro: 13.12.2011 15:16
Coluna Nº sequencial de um evento: 1
Coluna Region des Ausstellers: 31
Coluna Ausstellungsart: 1
Coluna Systemumgebung SEFAZ: 2
Coluna Nº ID fiscal (CNPJ): 20146676000367
Coluna Momento da emissão: 2011-12-13T15:16:39-02:00
Coluna Status: 02
Coluna Booleano: X
Coluna Registro da hora: 13.12.2011 17:16:52,2310000
Coluna Eventos: ctg.proc.: ISSUING
Coluna Eventos: etapa proc.: EVENTSIN
Coluna Status: 02
Coluna GUID: 00000000000000000000000000000000
Coluna Registro da hora: 13.12.2011 17:16:39,8000000
Coluna Registro da hora: *00.00.0000 00:00:00,000000
Coluna Tipo de um evento (texto): CC-e
Na SXI_MONITOR (SOAP-Header / Error), fica com erro conforme abaixo:
<?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>XIAdapter</SAP:Category>
<SAP:Code area="BPE_ADAPTER">MESSAGE_NOT_USED</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Message interface is not used by this process</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Na SXI_MONITOR (Payloads / MainDocument ( application/xml )), fica com erro conforme abaixo:
<?xml version="1.0" encoding="utf-8" ?>
- <n0:SignEvent xmlns:n0="http://sap.com/xi/NFE/006" xmlns:prx="urn:sap.com:proxy:PID:/1SAI/TAS80E97F9FB00E4B4CED3E:701:2011/06/16" xmlns:n1="http://www.portalfiscal.inf.br/nfe" xmlns:n2="http://www.w3.org/2000/09/xmldsig#">
<n0:KeyStoreView>CERTIFICADO</n0:KeyStoreView>
<n0:KeyStoreEntry>CERTIFICADO</n0:KeyStoreEntry>
<n0:EventID>E125BA771517E9F19D6100155D001537</n0:EventID>
- <n1:evento versao="1.00">
- <n1:infEvento Id="ID1101103111122014667600036755001000065812190506776301">
<n1:cOrgao>31</n1:cOrgao>
<n1:tpAmb>2</n1:tpAmb>
<n1:CNPJ>20146676000367</n1:CNPJ>
<n1:chNFe>31111220146676000367550010000658121905067763</n1:chNFe>
<n1:dhEvento>2011-12-13T16:44:17-02:00</n1:dhEvento>
<n1:tpEvento>110110</n1:tpEvento>
<n1:nSeqEvento>1</n1:nSeqEvento>
<n1:verEvento>1.00</n1:verEvento>
- <n1:detEvento versao="1.00">
<n1:descEvento>Carta de Correcao</n1:descEvento>
<n1:xCorrecao>teste de criacao da carta de correcao eletronica</n1:xCorrecao>
<n1:xCondUso>A Carta de Correcao e disciplinada pelo paragrafo 1o-A do art. 7o do Convenio S/N, de 15 de dezembro de 1970 e pode ser utilizada para regularizacao de erro ocorrido na emissao de documento fiscal, desde que o erro nao esteja relacionado com: I - as variaveis que determinam o valor do imposto tais como: base de calculo, aliquota, diferenca de preco, quantidade, valor da operacao ou da prestacao; II - a correcao de dados cadastrais que implique mudanca do remetente ou do destinatario; III - a data de emissao ou de saida.</n1:xCondUso>
</n1:detEvento>
</n1:infEvento>
- <n2:Signature>
- <n2:SignedInfo>
<n2:CanonicalizationMethod Algorithm="" />
<n2:SignatureMethod Algorithm="" />
- <n2:Reference URI="">
<n2:Transforms />
<n2:DigestMethod Algorithm="" />
<n2:DigestValue />
</n2:Reference>
</n2:SignedInfo>
<n2:SignatureValue />
- <n2:KeyInfo>
- <n2:X509Data>
<n2:X509Certificate />
</n2:X509Data>
</n2:KeyInfo>
</n2:Signature>
</n1:evento>
</n0:SignEvent>
Alguém poderia nos auxiliar?
Obrigado e abraços.
Mateus.

Pessoal, resolvi editar e inserir a primeira postagem pois ficou desconfigurada... segue abaixo:
Estamos implementando a CC-e, e realizamos todas as configurações no ECC, e estamos no SP20 do GRC.
No ECC a CC-e é criada normalmente e enviada ao GRC, porém a mesma fica no monitor GRC e não é enviada à SEFAZ...
Quando checamos a aba de "síntese de status" do monitor de evento da CC-e, a mesma fica com DUAS linhas conforme abaixo:
>>>>>>> LINHA 1:
Status: Assinar evento
Atividade: Criação
Ctg.proc.: Etapa não está em ordem
>>>>>>> LINHA 2:
Status: Criar CC-e
Atividade: Criação
Ctg.proc.: Etapa em ordem
Quando checamos a aba de "Histórico", a mesma fica com TRÊS linhas conforme abaixo:
>>>>>>> LINHA 1:
Atividade: Assinar evento
Ctg.proc.: Criação
Descrição do status: Etapa não está em ordem
Texto info: SAP NetWeaver PI notifica erro ao assinar o evento.
Satus: Etapa não está em ordem
>>>>>>> LINHA 2:
Atividade: Assinar evento
Ctg.proc.: Criação
Descrição do status: Etapa em ordem
Texto info: Em Branco
Satus: Etapa em ordem
>>>>>>> LINHA 3:
Atividade: Criar CC-e
Ctg.proc.: Criação
Descrição do status: Etapa em ordem
Texto info: Evento do tipo 110110 para 31111220146676000367550010000658121905067763 é criado com o nº sequencial 01
Satus: Etapa em ordem
Na grid com informações gerais sobre a CC-e, as colunas que são preenchidas ficam descritas conforme abaixo:
Coluna Status global: incorreto
Coluna Zugriffsschlüssel: 31111220146676000367550010000658121905067763
Coluna Tipo de um evento: 110110
Coluna Nº sequencial de um evento: 1 (para todas as CC-es fica 1)
Coluna Momento da emissão: 13.12.2011 15:16
Coluna Momento do registro: 13.12.2011 15:16
Coluna Nº sequencial de um evento: 1
Coluna Region des Ausstellers: 31
Coluna Ausstellungsart: 1
Coluna Systemumgebung SEFAZ: 2
Coluna Nº ID fiscal (CNPJ): 20146676000367
Coluna Momento da emissão: 2011-12-13T15:16:39-02:00
Coluna Status: 02
Coluna Booleano: X
Coluna Registro da hora: 13.12.2011 17:16:52,2310000
Coluna Eventos: ctg.proc.: ISSUING
Coluna Eventos: etapa proc.: EVENTSIN
Coluna Status: 02
Coluna GUID: 00000000000000000000000000000000
Coluna Registro da hora: 13.12.2011 17:16:39,8000000
Coluna Registro da hora: *00.00.0000 00:00:00,000000
Coluna Tipo de um evento (texto): CC-e
Na SXI_MONITOR (SOAP-Header / Error), vejam algums descritivos:
<SAP:Code area="BPE_ADAPTER">MESSAGE_NOT_USED</SAP:Code>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Message interface is not used by this process</SAP:Stack>
Alguém poderia nos auxiliar?
Muito obrigado e abraços.
Mateus.

Receiver Mail Adapter

Hi All,
I am using Receiver Mail Adapter to send mails.
When i choose Message Protocol the mail goes. But when i change it to XIPAYLOAD the mail doesnt go.
I cannot find any errors in SXI_MONITOR or in adapter monitoring.
My file is in this format..
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:Mail xmlns:ns0="http://sap.com/xi/XI/Mail/30">
<Subject>Mail From XI new</Subject>
<From>kmadmin</From>
<To>[email protected]</To>
<Content_Type>text/plain</Content_Type>
<Date>2006/08/24</Date>
<Content>Test mail from XI</Content>
</ns0:Mail>
Tried both ways..
XIPAYLOAD without Mail Package
XIPAYLOAD with Mail Package
Can anyone temme where im going wrong..or any settings which i need to do.

Bhavesh
<i>Am not sure which SP onwards this is applicable. But , did you select and try with MAIL PACAKGE also selcted.</i>
Tried using both wayz..
You dont need to create ,http://sap.com/xi/XI/Mail/30 namespace in IR.
The mail is going now..
just disabled
Content_type, Date in Mapping.
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:Mail xmlns:ns0="http://sap.com/xi/XI/Mail/30">
<Subject>Mail ALert XI</Subject>
<From>kmadmin</From>
<To>[email protected]</To>
<Date>2006/08/24</Date>
<Content>SQL Server Is Not Working</Content>
</ns0:Mail>
Thanks
SUmit

Problem in Idoc Receiver

Hi guys.
I have a FILE to IDOC scenario.
The original idoc have only 1 ocurrence but I've changed the ocurrence with an external definition based on idoc xsd with ocurrence 0..N.
When any idoc is generated in mapping Im getting the next erro in moni:
Error: MSGGUID 901EF81123CC4D131091DF1F61EB83B4: Tag found instead of tag IDOC BEGIN=
Why Im getting this error in sxi_monitor if I've especified my cardinality to 0..N??
Thanks a lot.
Regards.

>> Error: MSGGUID 901EF81123CC4D131091DF1F61EB83B4: Tag found instead of tag IDOC BEGIN=
First export the idoc locally and change the occurence of idoc tag from 1 to 0 to unbounded. Check in the mapping you specify the modified idoc. Also acivate the objects and update cache.
Tips
a) Use your modified idoc in the message mapping target side
b) Operation mapping - Specify original idoc as target message in the inbound side. (you might get some warning during activation.. please ignore it)
c) In the interface determination check you specify operation mapping and inbound interface as original idoc....
If you do all the above steps, You should not get this error. Hope this helps.
Edited by: Baskar Gopal on Feb 24, 2011 9:30 AM

SOAP Exception from XI to R/3 via RFC

Hello,
We have a scenario where we are mapping SOAP Exception to RFC Exception.
Message status is application error in SXI_MONITOR and in payload,it shows correctly mapped RFC Exception (SOAP_EXCEPTION) with name and message.
But this message doesn't reach R/3.
Configuration is done as a registered server program in XI using a TCP/IP connection in R/3.
Can anybody please let us know what could be wrong over here?
Thanks.
Regards,
Shweta

Hi Swarup,
There is no error in RFC communication channel.
The conditions are
sy-subrc 1 for Communication failure
2 for system failure
3 for SOAP_EXCEPTION (passed in name field from XI)
but when I execute the report and this RFC is called,sy-subrc is always 0.
What could be the reason for this?
Thanks for the help.
Regards,
Shweta

Messages don't reach XI from ABAP client proxy

All messages in SAP System have "Recorded" status and don't reach XI. Could you help me what is wrong?
SXMB_ADM
Role of Business System: Application System
Corresponding Integ. Server: dest://MY_XI
When I test MY_XI destination it returns 500 status:
<SAP:ApplicationFaultMes
sage namespace=""/><SAP:Stack>Empty HTTP query received. No message proc
essing possible##</SAP:Stack></SAP:Error></detail></SOAP:Fault>#</SOAP:B
ody>#</SOAP:Envelope>#

hi,
did you do ALL steps <b>EXACTLY AS</b> from the config guide?
https://websmp205.sap-ag.de/~sapidb/011000358700001697502004E.PDF
to connect your BS with XI ?
point:
8 Connecting Business Systems with an Integration Engine to the Central Integration
BTW
do you see any error in SXI_MONITOR
on the R3 or only recorded?
also:
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
Regards,
michal

Exception handling in receiver sync SOAP comm channel

Hi experts,
We are developing following synchronous scenario: sRFC to SOAP.
In this, XI sends some data to an application and the application sends back the response. No problem so far.
However, this application can throw exceptions that we want to send back to SAP, these exceptions are not part of a message and we can only see them AS AN ERROR IN SXI_MONITOR in the receiver SOAP header, in the error tab, they look like:
"com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault:
Questions:
Is there any way to get these exceptions from the application and send them back to SAP as if they were the SOAP.response message??
What if we select Keep headers in the receiver SOAP channel?
do we need to create a fault message type and assign it in ID?
Any ideas?
Best regards,
David

check for the possibility of raising an alert which has SXMS_TO_ADAPTER_ERRTXT as the Container variable....so if there is an error this alert variable will get populated and you will receive an alert....applicable only for adapter engine alert...
for more information: http://help.sap.com/saphelp_nw70/helpdata/EN/d0/d4b54020c6792ae10000000a155106/frameset.htm
Regards,
Abhishek.

User Decision Step in BPM - PI 7.1

Hi All,
I have posted a wiki for User Decision step in BPM in PI 7.1, Please go through it and post your queries, suggestions and comments here.
The link for same is under:
Part1 - https://www.sdn.sap.com/irj/scn/wiki?path=/display/xi/userDecisionstepinSAPPI7.1-Part+I
Part2 - https://www.sdn.sap.com/irj/scn/wiki?path=/display/xi/userDecisionstepinSAPPI7.1-Part+II
Regards,
Sachin

Hi Sachin,
Nice job,
During my practice on this scenario. I have got an error please kindly guide me on this, may this error also clear for the others
*I got an error on SXI_MONITOR as:*
<?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>XIAdapter</SAP:Category>
<SAP:Code area="BPE_ADAPTER">UNKNOWN_MESSAGE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>No object type found for the message. Check that the corresponding process is activated</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
The trace of the error as:
<Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_BPE-ENTER_PLSRV">
<Trace level="1" type="T">could not create BPE proxy for message, no XML object definition found for message 72485F6BFC78416A29EEE3EE10D09BCE</Trace>
</Trace>
</Trace>
<Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
Please kindly guide me on this, Is the message has to validate at sender agreement? if not where is the error I am doing?

IDOCType PORDCR101 : XML IDoc conversion: No known segments identified

Hello all,
I'm strugling with the mapping to the IDOC create puchase order PORDCR1.PORDCR101.
The source structure for the moment is exactly the same as the target strcuture i.e. our IDOC.
So I would not expect to much problems with this one.
However, when sending the message we get the following error in SXI_MONITOR:
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
<SAP:P1>XML IDoc conversion: No known segments identified</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: XML IDoc conversion: No known segments identified</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
I also augmented the trace lvl to 3 and got the following in the Trace-part of TC SXI_MONITOR and
suspect it starts to get wrong already in the beginning
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">---- Outbound IDoc-Adapter -
</Trace>
<Trace level="1" type="T">----
</Trace>
Trace level="1" type="T">Convert one IDoc</Trace> .
<Trace level="2" type="T">Convert Control Record</Trace>
<Trace level="2" type="T">Convert Data Records</Trace>
<Trace level="3" type="T">Segment= E1BPMEPOHEADER</Trace>
<Trace level="2" type="T">Ignore unknown Segment E1BPMEPOHEADER</Trace>
<Trace level="2" type="T">Ignore segment field: COMP_CODE</Trace>
<Trace level="3" type="T">Segment= E1BPMEPOHEADERX</Trace>
<Trace level="2" type="T">Ignore unknown Segment E1BPMEPOHEADERX</Trace>
<Trace level="3" type="T">Segment= E1BPMEPOADDRVENDOR</Trace>
<Trace level="2" type="T">Ignore unknown Segment E1BPMEPOADDRVENDOR
I already found the four or so other threads on the SDN website about this error and in the mean-time tried them (delete and reload the structure with IDX2, set the begin and segment-attribute to 1, make sure that the segments-names self are also mappend) but to no avail.
We just implemented two other IDOC's (DELVRY03 and WMMBID02) and they arrive at SAP without problmens.
Hope you have form ideas to get me out of this one.
Tnx and best regards.
Bart.

Hi Bart,
We had a similar problem.... It took us 2 days to find out what the problem was... Nothing on SDN was helpfull so far... First we incremented the trace level of XI to see the debug messages... Then we saw that certain segments could not be identified and are ignored, others not...
So further investigation in IDX2 to the specific IDoc with problems showed us a list with all used segments and their versions. Some segments had only 1, others had more versions....
So we could identify the problem as a segment version problem. It seemed that our IDoc Communication Channel took not the most recent version. So we changed the "Segment Version" to the most recent one and the problem was solved!
Please reward points if this was usefull to you...
cheers!
Pedro

Error in SXI_MONITOR

Similar Messages

Maybe you are looking for