Ack Status

I am passing IDocs from SAP 3.1 to 4.7 via XI and in SXMB_MONI the Ack Status shows "?" this sign and says Still waiting acknoweledgement. Can any body tell me what are the settings need to done to fix this .

HI manish,
This is because your system acknowledgement is activated but not configured.
If you do not want to receive ack, Run report IDX_NOALE and deactivate ack for the IDocs you want.
Regards
Vijaya

Similar Messages

Query on IDOC Ack (STATUS) config in XI for a specific partner comm.

Hi Experts,
Is it possible to configure the IDOC Ack (STATUS.SYSTAT01 message) in XI for a specific partner communication? We want to configure our system like ALEAUD but the message type should be STATUS.SYSTAT01 and the acknowledgment should be send to sender system for a specific partner only if XI receives any IDOC like (Orders) from that specific partner. For other partners (same sender system) we donu2019t want this acknowledgment settings and configuration. If possible please provide the configuration filters steps etc. Thanks for your valuable inputs in advance.
Thanks,
Satish
Edited by: Satish Jaiswal on Jan 8, 2009 2:55 AM

Hi Husain,
I have the document you have mentioned. Please note my requirement is to filter the Ack while creating and sending to R/3 based on Partner and Message type. The document provides info only on Message type filter but not parner specific for same sender system!!! Any help appreciated. Also note: BPM and Alert is out of scope.
Looking for some ALE configuration tricks to achieve this.
Thanks
satish
Edited by: Satish Jaiswal on Jan 9, 2009 2:40 AM

IDOC Ack status back to XI/BPM ?

Hi
i have done File to Idoc scenario, and want to get acknowledgemnents inside XI/BPM.
i hv proivded port,client,message type and selected 'Request acknowledgement' tab and executed report 'IDX_NOALE'. but im not getting any acknowledgement status in moni. please suggest hw could i get Idoc acknowledgements in XI.
1.Do i need to import ALEAUD Idoc into XI ? and Is any configuration required in ID for ALEAUD?
2.Is it possible to map Idoc status back into BPM? if yes, please explain how BPM should design?
3.once Idoc ack status received inside XI, is it possible to send same status to the back end sender system?
appreciate your help..
Regards,
Rajesh

hi
1.Do i need to import ALEAUD Idoc into XI ? and Is any configuration required in ID for ALEAUD?
By default, audit idocs will come and get tagged to the IDoc. If you want to send it to the file system, all configurations must be done for IDoc to file scenario for the audit IDoc.
2.Is it possible to map Idoc status back into BPM? if yes, please explain how BPM should design?
Yes, it can be done. But won't be reqd in ur case.
3.once Idoc ack status received inside XI, is it possible to send same status to the back end sender system?
Yes, Q1
Check this document on handling IDOC acknowledgements.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
rgds,
Arun

Ack Status - Still waiting acknoweledgement

Hi experts,
I have this Ack Status (? Still waiting acknoweledgement) in my SXMB_MONI with an IDOC -> XI -> JDBC scenario.
How can I configure Ack in order to fix this or disable this configuration in case I don't want it?
Points will be given,
Regards,
Daniela

<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe">Howto- Handle IDoc Ack</a>

IDOC Acks not working

Hi All,
I have spent hours searching SDN for this specific problem, and can see some similar threads but none with a successful answer, so I will ask again.
I have the following scenario:
R/3 system sending an IDOC to XI, then XI mapping that to a custom XML message and sending it via the HTTP Adapter to an external business partner.
We have no issues with the above and get a chequered flag in SXMB_MONI.
But we want an Acknowledgement of that transmission to go back to the initiating IDOC in the R/3 system and update the status. e.g. If there was a HTTP comms failure and the message ended up in error in SXMB_MONI then we want that status sent back as an Acknowledgement to the original IDOC so that the R/3 system is aware of the failure.
We can see that XI tries to send the Ack back, but in SXMB_MONI in the "Ack Status" column there is an error associated with the Ack which says either "Acknowledgement not possible" or "Acknowledgement contains system errors". When we look into the error message contained within the Acknowledgement it says:
Unable to convert the sender service XXXXX to an ALE logical system
The Sender Service listed in the error message is the original Receiver Service which passed on the HTTP message to the 3rd party receiver. But in this case it is the sender because it is trying to send an Ack back to the R/3 system that is now the Reveiver. Note that it is a Business Service (not in SLD), it is NOT a Business System.
My question is - where is XI looking for an ALE Logical System name? My Business Service is not in the SLD (doesn't need to be, it's a 3rd party external system and I can send to it fine). I even tried populating the Adapter Specific Identifers for this Business Service with the IDOC Logical System name and R/3 System ID and Client, but that did nothing becasue this isn't using the IDOC Adapter, it's using the HTTP Adapter.
And note that we have SXMB_ADM param RUNTIME-ACK_SYSTEM_FAILURE = 1.
And please dont post a bunch of links, I've looked at every message in SDN that refers to the above. Please only reply if you can type the exact answer and it refers to the Acks only.
Thanks,
Brendan.

Hi,
Open(Double click) the Receiver Business service in ID and goto Change mode
goto Adapter Specific Identifiers---just give the LS name as HTTP and click on Apply and save Activate.
Do SXI_Cache also
Now try to post the Idoc Again from R/3
Regards
Seshagiri

Handling Transport ack. in Abap Proxy to JDBC Scanario

HI all
I have a scanario where i have message which is being sent from an abap proxy to a SQL Server database using JDBC adapter. The scenario involves a BPM.While sending the message the message shows delivered in MDT (Message monitor for Adapter ) but the Business process is still executing and is waiting for the acknowledgement(transport) . Can anyone please tell me how do find where the exact prblem lies.And how do i delete these acknowledgements. Even though i deleted the work items the Ack Status column still shows "Still Awaiting Acknowledgement"
regards
Nilesh Taunk

Hi,
As metioned check the Send Step Properties ( mode etc)..
After changing activate the BPM and refersh the cache in SXI_CACHE and test the scenario.
also check the BPM technical details. For this go to SXMB_MONI>PE>Technical Details so that you can find the logs in the monitor.
Regards,
Moorthy

IDOC to File -Ack

I have found several posts on this but I can not find a clear answer.
I am using PI 7.1. I have a PO Idoc leaving R/3 through PI using an IDoc Adapter. When it gets to PI I am routing it to one of three possible locations.
1. SRM-SUS if it is a SUS Supplier
2. Supplier Web Services if the supplier has exposed a web service for POs
3. FTP site if the supplier is set up to get their POs from our FTP site
When the POs go to SUS or web services I get a green check in the "Ack Status" in SXMB_MONI. But when I send the PO to the FTP site using a File Adapter I get a "?" (Still awaiting acknowledgement).
I read about setting up the Adpater Specific Identifier within the Business Component but I have been unable to get this working. Is there some way I can force PI to give me a green check once the PO has been sent via File Adapter?
Thanks,
Matt

This blog describes my situation exactly:
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
Let us consider a simple scenario where in an SAP system sends an IDOC to XI and a mapping program within XI
runtime converts the IDOC structure to a simple XML structure and stores it in a file system using the file adapter. The
Sender IDOC adapter requests an acknowledgement when sending the IDOC to XI. The system acknowledgement sent
by the file adapter is converted into an ALE audit message and sent back to the sender SAP system by an IDOC ACK
channel configured in XI(an IDOC receiver adapter).
However, when the file adapter communication channel is configured under a Business Service, the sending of ALE
audit message may fail with the message "Unable to convert the sender service <Business Service Name> to an ALE l
ogical system". To avoid this error, we need to specify a Logical System for the IDOC adapter.To specify the logical
system, open Integration directory and select the Business Service that is configured as receiver for the IDOC.Switch to
Edit Mode and choose the "Service" menu and then the menu option "Adapter-specific identifiers". In the popup specify a
Logical System for the IDOC adapter.Save and activate the Business Service. Now the ALE audit message is sent back to
the SAP system without any errors.
The problem is...I am unable to get this to work using PI 7.1. I am unable to get the File Adapter to create the Ack (Green Check) as Saravana has described. Has anyone used PI 7.1 to do something like this?
Thanks,
Matt

SXMB_MONI and BPM acknowledgement status updates

Hi folks,
We have a scenario in place where we deliver an IDOC to the backend system via the 'send' step and we had acknowledgement property set to 'transport' as we believed that the IDOC adapter would at least return us with exception information when something went wrong with the delivery of the IDOC. We also added 'deadline' monitoring as well to prevent the BPM of 'waiting forever' ... In case of exceptions or deadline, an alert is thrown.
This concept worked fine during development testing - IDOCS with status 56 or even 51 got picked up and resulted in error ... ( huray )
Once tested in acceptance it didn't work at all anymore and all our BPM's ended up in the deadline branch - even for those IDOCS that were processed successfully ...
After reading SAP note 'Note 837285 - BPE TS: Acknowledgments in the BPE' we understood that the BPM does not support transient errors and as such our concept would never work as we intented it but still it did in development ... even worse it worked sometimes in acceptance as well ...
After a while we figured out that it worked when we ran transaction SXMB_MONI while the BPM was still waiting for the acknowledgement ... so basically this transaction triggered somehow the update of the acknowledgement status and as such the BPM continued as expected ...
Then we noticed as well that the transaction even updates statuses of messages of previous days ... ( the BPM for those was obviously allready completed due to deadline ... )
We are a bit 'lost' here on the whole concept ...
We read the 'How to handle Acknowledgements' PDF with ALEAUDIT but that only works for logical systems which is not our case ...
Why is the SXMB_MONI transaction updating the acknowledgement statuses ? How does it do that - what does it check ? ( we noticed that although IDOCS had status 56 we still got a positive ack status )?
In general it seems that using BPM with send step and waiting for ack with the IDOC adapter is useless due to the transient ack status ( as explained in the note ) ... is that assumption correct ?
Regards,
Steven

Hi Steven,
I can't answer your specific questions, but it occurs to me that the <a href="http://help.sap.com/saphelp_nw04/helpdata/en/44/a1b46c4c686341e10000000a114a6b/frameset.htm">new functionality in SP18</a> to turn received ALEAUDs into "normal" XI request messages may provide a workaround for your problems. The transformed ALEAUDs could be routed to your BPM by way of a correlation on the IDoc number. This way you could react to all ALEAUDs regardless of status...
Regards,
Thorsten

IDOC ack

Hi,
i have put in a production support team and the project team which implemented the project has moved out. so i cant ask any project team member now
There are nearly 3 scenarios configured for IDOC -XI-IDOC and they are driving me crazy. All are running fine. But their ack status is driving me crazy. In one scenario it is showing Waiting for ack for all msgs of this scenario.
In second scenario, there is again a scenario IDOC - XI - IDOC running in XI Prd system like System A - XI prd - System B. It is running fine. The problem is in SXMB_MONI for ack status there is a green tick coming and when i double click the msg to open it, then on double clicking this success ack msg, shows the error CO_TXT_ROUTING_BACK_ERROR saying Error occurred during back-routing Error in communication channel because the path System B to System A http://sap.com/xi/XI/Message, Acknowledgment is not found. This is leading to a lot of error messages in RWB msg monitoring at IE level in System Error status because of these ack msgs.
The third scenario is again IDOC - XI - IDOC and it is also running fine without anything in ack status column in SXMB_MONI - which is totally fine.
I have saw the complete XI prd scenarios and no where ALEAUD is configured. So the above ack in scenario 1 and 2 seems to be a transport level ack. I do not want any ack status for any scenario. How to rectify this thing so that it does not see for ack status at all? Please help.

Hello,
You can check this link http://help.sap.com/saphelp_nwpi71/helpdata/EN/ab/bdb13b00ae793be10000000a11402f/frameset.htm and then scroll down until you see section 4 and section 5. Section 4 will tell how to disable acknowledgements, but it would be best to consult with business since you are planning to disable it in production.
Hope this helps,
Mark

Scenario:SAP-XI-AS/400; Ack not possible and DB insert issues.

Hi,
I have a SAP-XI-AS/400 scenario and I have two issues with the same.
1. When I trigger an IDoc to the XI system, I get ack status(in SXMB_MONI) as: "Acknowledgement not possible". The message is : "Unable to convert the sender service to an ALE logical system"
2. While trying to do a DB insert I get the below Error and DB insert is not happening.
" Error Unable to execute statement for table or stored procedure. '<table_name>' (Structure 'Statement_<table_name>') due to java.sql.SQLException: [SQL7008] <table_name> in <lib> not valid for operation.
Error JDBC message processing failed; reason Error processing request in sax parser: Error when executing statement for table/stored proc. '<table_name>' (structure 'Statement_<table_name>'): java.sql.SQLException: [SQL7008] <table_name> in <lib> not valid for operation.
Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Error processing request in sax parser: Error when executing statement for table/stored proc. '<table_name>' (structure 'Statement_<table_name>'): java.sql.SQLException: [SQL7008] <table_name> in <lib> not valid for operation.
Error Exception caught by adapter framework: null
Error Delivery of the message to the application using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Error processing request in sax parser: Error when executing statement for table/stored proc. '<table_name>' (structure 'Statement_<table_name>'): java.sql.SQLException: [SQL7008] <table_name> in <lib> not valid for operation.. "
I have been using the same kind of query we use for other succesful dB inserts.
Can you please give me a solution and suggest possible reasons and workarounds?
Thank you
Best Regards,
Smitha

Smitha,
Go through this links....
Some Experts discussions..
Error while updating JDBD table
JDBC Error
Error when executing statement for table/stored proc DB2 - Data Truncation
Hope this info is useful to you..
Thanks,
Satya Kumar

Waiting for Acknowledge status

Hi All,
I have a scenario already running in PRD (IDOC to File).
Now there is some enhancement required to be done, based on some specific plant, the delivery is to be sent to different location.
I have done the configuation by making another Business Component using routing rule & further assingned the routing roule to
Receiver Determinaion. the scenario is running perfect. Files are being created in the target system based on Plant.
but in SXMB_MONI, the message is in success state where as there is one column, as 'Ack Status' here comes waiting for
acknowledgment with a red icon.
How to avoid this, do I have create a Business system in SLD, or just neglect this message as files are being creted at the location.
Thanks,
Krishna

Hi,
\You can disable Acknowledge by using report IDX_NOALE for your IDOc.
Refer this
IDOC - XI - File

Acknowledgement status

Hello,
When we send a Asynchornous message , say from IDOC as sender and JMS as receiver via XI.
Do we really need to worry abt the Ack Status which is in sxmb_moni. Sometimes, it shows ack in error, sometimes in null, sometimes waiting for ack.
If it is a asynchronous, what is the purpose of it.
Moreover i see lot of messages in Message monitoring regaring acknowledgment.

Hi,
Go through this Document..
Click the link and Down load that Document i.e: How to handle Ack for IDOC's
How to handle Ack for IDOC's
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
Steps: if u want IDOC Ack You have to set up the ALEAUD.
Acknowledgment IDocs are always converted to XI acknowledgments.
This function enables you to send acknowledgment IDocs (ALEAUD) as XI request messages for a sender port and client.
Procedure
1. In the ABAP Editor (transaction SE38), under Program, enter IDX_ALEREQUEST and choose Execute.
2. Enter a sender port and a client and choose Execute.
3. Enter the partner number, partner type, and partner role for the receiver and choose Insert.
The entry is added to the table.
4. To delete an entry in the table, select the entry and choose Remove Entry.
Result
In the XI request message, the original sender of the acknowledgment IDoc is no longer known.
The XI request message created is a new message. Monitoring is not able to determine which was the original message.
File Acknowldgements
/people/michal.krawczyk2/blog/2006/06/22/xi-playing-with-the-file-adapters-acknowledgments
Sending Acknowledgment IDocs as XI Request Messages
Use
Acknowledgment IDocs are always converted to XI acknowledgments.
This function enables you to send acknowledgment IDocs (ALEAUD) as XI request messages for a sender port and client.
Processing Acknowledgment Messages
An acknowledgment message informs the sender of an asynchronous message about the result of the processing of the message within SAP Exchange Infrastructure. The reported result is referred to as an asynchronous acknowledgment.
Request Messages
Within the request message you must define whether an acknowledgment message is required, and if so, what kind of acknowledgment message. The acknowledgment message can refer to two events:
● The arrival of the request message at the final receiver
● The execution of the application in the receiver system
For this purpose, the request message contains an acknowledgment tag, which specifies the event for which an acknowledgment is expected. This tag must be specified by the sender (or a sender adapter that supports acknowledgment messages).
Message processing in SAP Exchange Infrastructure ensures that the acknowledgment message follows the same route from the receiver to the sender as the request message did from the sender to the receiver. For this purpose, the request message contains a hop list that logs the route of the request message. This information is provided by all Integration Engines and Integration Servers that are involved in the processing of the request message.
Acknowledgment Message
As soon as the request message processing encounters an event that requires an acknowledgment, a corresponding acknowledgment message is created and sent to the sender.
An acknowledgment message receives a new message ID, but also has a reference to the message ID of the request message as well as the value Response in the Directory tag of the message header. The request message hop list is copied to the acknowledgment message header, thus enabling backward routing of the acknowledgment message.
If a message is branched, a separate acknowledgment message is returned for each newly created request message. These acknowledgments enable the sender to recognize that its original message has been branched.
Acknowledgment messages are processed using backward pipelines. These pipelines are defined for each pipeline involved in the processing of a request message:
Pipelines and Corresponding Backward Pipelines:
Pipeline
Backward Pipeline
SENDER
SENDER_BACK
CENTRAL
CENTRAL_BACK
RECEIVER
RECEIVER_BACK
The backward pipelines have the following main tasks:
● Transport from the receiver system to the Integration Server
The receiver system sends an acknowledgment message back to the corresponding Integration Server (RECEIVER_BACK), as defined for the local Integration Engine.
If a receiver adapter is involved in message processing, it sends the acknowledgment message back to the Integration Server, provided that the respective adapter supports this procedure. Otherwise, a final acknowledgment message is returned with a comment that an acknowledgment is not possible.
● Transport from the Integration Server to the sender system
The Integration Server sends an acknowledgment message back to the sender (CENTRAL_BACK). It uses the name of the sender system for logical and technical backward routing.
If the sender is addressed using an ABAP proxy, you must define a corresponding receiver agreement for this sender.
If a sender adapter is involved in processing the message, the Integration Server sends an acknowledgment message to the sender adapter, which is then responsible for returning the acknowledgment to the sender.
To do this, some adapter types require a corresponding receiver agreement for the sender.
Hope This Information is useful to you,
Thanks,
Satya Kumar.

Awaiting Acknowledgement status

Hi Friends,
I am doing IDOC To File scenario,
Till morning all my idocs got successfully posted in respective folders. Suddenly now all my idocs in sxmb_moni showing successfully posted with" awaiting acknowledgement status".
so none of my idocs get posted with awaiting ack status.
Could any one tell how to avoid this kind of issues.
Regards,
Vijay

Hey
you need to make an entry in table IDXNOALE for your IDOC message type to stop the IDOC ack. request.
Have a look at the section "Switching Off ALE audit messages" of the below blog
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
Thanx
Aamir

NF-e parada no passo de Assinatura após queda do PI

Olá Pessoal,
Na semana passada tivemos um problema com a máquina do PI e GRC (as duas aplicações estão na mesma instância) que ficou fora durante um periodo de 4 horas.
Ao retornar, a maioria das Notas puderam ser reinicializadas pelo proprio monitor do GRC.
Mas uma delas, permanece estagnada, nem vai pra frente, nem pra trás.
No ECC ela está em Processamento com status de "Aguardando Resposta";
No GRC está com o triângulo amarelo, "Sent to Signature Service", Process Status = 02 e não possui error status na /XNFE/NFE_HIST;
Na SXMB_MONI tanto no Aplication como no Integration a interface SIGNN_SignNFe_OB está com Ack.Status "Still awaiting acknowledgment" e a bandeira do PE está quadriculada.
Não encontrei filas paradas na SMQ1 ou SMQ2.
O que posso fazer nesse caso? Vou ter que criar uma entrada de erro na /XNFE/NFE_HIST?
Desde já agradeço,
Att,
Daniela

Olá Henrique, obrigada pelo retorno e desculpe por não responder tão prontamente.
No workflow log o Status do BPM está como completed e quando verifiquei o gráfico, ví que ele foi executado até o passo "Send response message" e depois disso foi disparado o exception "Communication Exception", passos "Create alert 2" e "Cancel process 2".
Sobre as suas perguntas:
vc tentou restartar o BPM pelas tx SWF_XI_SWPC / SWF_XI_SWPR?
Não usei essas transações e também não as conhecia. Mesmo no caso do BPM estar como completed eu precisaria utilizá-las? Se sim, como as executo?
Se nao funcionou, vc tem essa nota aplicada: 1373738?
Não temos essa nota aplicada, estamos com o SAP_BASIS 700 SP21 e as entradas mencionadas não existem na tabela.
Tem uma nota que foi criada como uma solucao workaround pra reenviar esses acks parados, a 1376946, que cria o report RSWF_XI_RESEND_ACKS, porém ela foi criada em Pilot Release apenas pra quem abriu o chamado na época. O pessoal de PI falou que ia ter uma solucao final diferente, que eu infelizmente nao acompanhei pra saber qual foi. Se nao encontrar solucao viável, sugiro abrir um chamado no componente BC-XI-IS-BPE e solicitar qual a solucao final para esse problema.
A nota 1376946 está com From/To Release 701, por isso fiquei em dúvida se deve ser aplicada ou não. Pelo que entendí ela é um complemento da 1373738. Adiantaria se aplicássemos apenas a 1373738 caso a 1376946 não seja relevante para o Release 700?
Desde já agradeço.
Att,
Daniela

Envio de XML para fornecedor

Srs,
Estamos com falha no envido do XML para o fornecedor, porém os emails enviados não estão sendo recebidos pelos forecedores.
Criei algumas NF-es de homologação e inserindo meu próprio email, sem sucesso.
Estranhamente todas as notas criadas estão sendo finalizadas com sucesso e meu email inclusive aparece no XML da nota!
Process Status: 08 (Sent to B2B)
Error Status: Vazio
Status Code: 100 (Autorizado o uso da NF-e)
ERP Error: Vazio
Em history ele segue o seguinte processo:
Overall Status - Creation Date - Creation Time
Received from Feeder System - 05.05.2010 - 11:00:20
Sent to Signature Service - 05.05.2010 - 11:00:20
Signed - 05.05.2010 - 11:00:23
Added to Batch - 05.05.2010 - 11:02:08
Result Received - 05.05.2010 - 11:04:17
Sent to B2B - 05.05.2010 - 11:06:09
Os Comunications Channels Email_Sender_CC (Incoming) e NFeXML_Mail_Receiver_CC (Outgoing), estão ativos e funcionando perfeitamente no Integrations Directory e em Comunication Channel Monitor, também não foi encontrado nenhum log de erro.
Os principais jobs ( /XNFE/PROCESS_REPORTS, /XNFE/CHECK_SRV_STATUS e /XNFE/UPDATE_ERP_STATUS), estão schedulados e sendo finalizados com sucesso.
Na MONI, todos processos são finalisados com sucesso (bandeira quadriculada) e sem erros em Ack Status.
Também não encontro nenhum log de erro em Payloads, Soap Header ou Soap Body.
Nenhum bloqueio na SMQ1, SMQ2, SM12, SM21. Chequei inclusive os logs da AL11 e não encontrei nada que pudesse me dar uma luz.
Efetuei ping nos servidores de IMAPS e SMTP, que responderam um time de 170ms em média.
Um telnet nas porta 25 (SMTP), houve um retorno de sucesso pelo comando HELO.
Porém, qdo tento conectar o telnet na porta 993 (IMAPS), não aparece nenhuma mensagem e volta à raiz (C:>) sem resposta.
Alguém já passou por algo parecido e poderia me dar um help.
Toda ajuda será bem vinda.
PS.: Estou resolvendo por nome do host e não por IP nas configurações do PI/XI, isto infuência?
Obrigado,
Ricardo

Ricardo,
sugiro que você busque na transação SXI_MONITOR por mensagens da interface de envio de B2B (NTB2B*) para o período no qual você está tendo problema.
Com isso, você encontrará todas mensagens que foram enviadas para o B2B. Através do Access Key, identifique uma que você sabe que não chegou ao destinatário e abra a mensagem.
Abra a mensagem do pipeline SENDER e procure no trace (janela do lado direito, com o xml) por uma parte chamada "Dynamic Configuration". Nessa parte deverá constar a configuração do e-mail de quem receberá a NF-e. Veja se bate com o que está no ERP.
Verifique também se a RFC que busca o e-mail está retornando corretamente os dados. Verifique também se no Message Mapping que busca o e-mail do cliente no SAP se ele está apontando para o Communication Channel correto.
[]'s

Ack Status

Similar Messages

Maybe you are looking for