RosettaNet ack error

Hello All,
We are on patch 7652646. We send a 3A4R to our TP. They send back the ack. However, the ack processing fails. The error we are getting is "_Document Exchange protocol name "RosettaNet" in message is different from document exchange protocol name "Generic" in agreement_" even though the TP is set up with RosetteNet protocol and there is no Generic document capability set up. The agreement contains only RosettaNet transactions. The 3A4C from the TP fails with the same error. Any suggestions on what can be worng?
Thanks!
Edited by: b2buser.. on May 8, 2009 8:55 AM

Hi,
Please verify the business protocol used by the trading partner. This indicates the sender has used a different document exchange protocol. i.e generic instead of RosettaNet.
Regards,
Dheeraj

Similar Messages

RosettaNet Protocol error

Hi All,
Here is the scenario. Trading Partner (TP) A is sending a RosettaNet business
message (PIP3A2) to TP B. When the weblogic Integration server for TP B receives
this message, I get the following error message,
####<Dec 4, 2001 4:00:33 PM PST> <Error> <B2B> <erpsystem> <myserver> <ExecuteThread:
'9' for queue: 'default'> <> <19:c285badb981bb8b8> <000000> <<RN-Protocol> ERROR:
Cannot locate CA for URI http://localhost:7001/Quantum, Business Identifier 987654321,
Role Product Supplier, in Coversation 3A2, version 1.3.>
It is referring to Conversation 3A2 eventough it has been deleted and should be
using the Conversation called PIP3A2. Can anyone tell me where and how this conversation
is referenced and how it can be fixed?
--Krish.

Hi All,
Here is the scenario. Trading Partner (TP) A is sending a RosettaNet business
message (PIP3A2) to TP B. When the weblogic Integration server for TP B receives
this message, I get the following error message,
####<Dec 4, 2001 4:00:33 PM PST> <Error> <B2B> <erpsystem> <myserver> <ExecuteThread:
'9' for queue: 'default'> <> <19:c285badb981bb8b8> <000000> <<RN-Protocol> ERROR:
Cannot locate CA for URI http://localhost:7001/Quantum, Business Identifier 987654321,
Role Product Supplier, in Coversation 3A2, version 1.3.>
It is referring to Conversation 3A2 eventough it has been deleted and should be
using the Conversation called PIP3A2. Can anyone tell me where and how this conversation
is referenced and how it can be fixed?
--Krish.

ACE duplicate ack and tcp out-of-order errors

Hi,
I have just performed a capture using a NAM in my 6500 on the port attached to my ACE appliance.
What i have noticed in the capture is a lot of duplicate ack errors and tcp out-of-sync errors.
The reason we found this was becuase the link utilisation per session seems higher than we expected, hence are the errors adding to this and is there any way to remedy them?
Thanks
Scott

Hi Scott,
I'm not sure why you would see duplicate packets, although when you use SPAN, I know you can see them when you configure it to capture both directions on a VLAN. This is because you see each packet as it enters and leaves the VLAN. I don't know if that would apply to a NAM.
One thing you could do is use the ACE 4710's built-in capture utility to see if you see the same symptoms from an alternative source. This is covered in the Capturing Packet Information section of the configuration guides.
Hope this helps,
Sean

Mail adapter error: Unsupported protocol: linsmtp [null "null"]

Hi,
Idoc to Mail adapter. First time working with mail adapter.
When I tried to send messages from transaction "SO00", i'm able to receive the mail which means the connection is fine from XI to mail server.
But when I try to send the file using mail adapter, it is failing in adapter engine with the error below.
Success Mail: calling the adpter for processing
Error Mail: call failed; com.sap.aii.messaging.srt.BubbleException: Unsupported protocol: linsmtp [null "null"]
Success Mail: sending a delivery error ack ...
Success Mail: sent a delivery error ack
Error Mail: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: com.sap.aii.messaging.srt.BubbleException: Unsupported protocol: linsmtp [null "null"]
Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: com.sap.aii.messaging.srt.BubbleException: Unsupported protocol: linsmtp [null "null"]
2010-11-12 14:12:02 Error Exception caught by adapter framework: com.sap.aii.messaging.srt.BubbleException: Unsupported protocol: linsmtp [null "null"]
2010-11-12 14:12:02 Error Delivery of the message to the application using connection Mail_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: com.sap.aii.messaging.srt.BubbleException: Unsupported protocol: linsmtp [null "null"].
Checked SMICM -- GOTO-->Services --> SMTP is active with green tick.
Receiver adapter:
Transport Protocol = SMTP
Message Protocol = XIPAYLOAD or XI ALL
URL = SMTP:linsmtp.sap.com
Not using User Authentication
User/ Password given - No userid/pwd
From, To = mail id
Content Encoding = try with none or base64*
Is there any setting which I need to do? how to connect and send message to mail server?
Thanks
Deepthi.

Hi,
My connection is working now when I downloaded the xsd and executed in the mapping as described in the blog.
/people/michal.krawczyk2/blog/2005/03/07/mail-adapter-xi--how-to-implement-dynamic-mail-address
Connection is working fine now, but im getting the below payload.
<?xml version="1.0" encoding="UTF-8" ?>
- <ns1:Mail xmlns:ns1="http://sap.com/xi/XI/Mail/30">
<Subject>TESTING</Subject>
<From>deepthi at testing.com</From>
<To>deepthi at testing.com</To>
<Content>Testing purpose</Content>
</ns1:Mail>
The question is how to get my actual message which looks like below. this is the Idoc to file map and the resultant output file looks like below
<?xml version="1.0" encoding="UTF-8"?>
<ns0:order xmlns:ns0="http://testing/xi/OrderProcessing">
 <document_type>ZU</document_type>
 <vendor_number>200000</vendor_number>
 <vendor_email_address/>
 <vendor_address_line_1>XXXXXX</vendor_address_line_1>
 <vendor_address_line_2>XXXXXXXXX</vendor_address_line_2>
 <vendor_address_line_3>123242343244566</vendor_address_line_3>
 <vendor_address_line_4>US</vendor_address_line_4>
 <delivery_address_line_1>1433</delivery_address_line_1>
 <delivery_address_line_2>test</delivery_address_line_2>
</ns0:order>
How to send this file as email attachment using mail adapter. Do I need to use 2 maps?
looks like Mail adapter is working only when we use the xsd which is given above and by providing the required details.
Kindly help me if anyone worked on mail adapters.
Thanks
Deepthi,

Error in Adapter engine of receiver soap adapter

Hi All,
There is one production issue i am currently facing in receiver SOAP adapter while interacting with third party web service(Asynchronous call).
Below is the description i am getting in audit logs.
Success SOAP: completed the processing
Error SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Invalid Session ID or Session Expired
Success SOAP: sending a delivery error ack ...
Success SOAP: sent a delivery error ack
Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Invalid Session ID or Session Expired
Error Exception caught by adapter framework: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Invalid Session ID or Session Expired
Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Invalid Session ID or Session Expired.
Error The message status set to NDLV.
Moreover this is a production issue and interface was running fine till last friday.
Has someone ever faced this issue ?
Please provide your valuable inputs on this.
Thanks
Anku

Hi,
Search in sdn with your error message string,you will find ton of links.
HTTP401 error occurs for many reasons.
still no solution let us know..
Regards,
Raj

BPM Acknowledgment error

Guys,
I have one BPM of type rfc (sync) -> soap (async)
I execute rfc and wait to execute soap for after response my rfc go back.
My i have one problem, i need to know if soap executed with success or error.
If i use tranport acknowledgment, the soap send return timeout and my process return error (but system error, then i cant catch in exception).
If i use application acknowledment, the soap send return ack error.
I whould like catch the return of application acknowledgment and use in one SWITCH.
How can i to do this?

Hi,
you can not dirrectly access the content of the ACK, however the BPM shows different behaviours based on the ACK status. E.g. if the ACK contains a success message the BPM will continue in its normal process, if the ACK contains a permanent error, it will either stop or go through an exception branch (provided such a branch has been defined). Have a look at the documentation: http://help.sap.com/saphelp_nw04/helpdata/en/43/65ce41ae343e2be10000000a1553f6/content.htm It doesnt"t state the above mentioned behaviour in detail but says that you need to define an exception branch.
The trickiest part is always to find out, when you will get a transient vs. as permanent error ack. If you are using ACKs with Proxies refer also to this link http://help.sap.com/saphelp_nw04/helpdata/en/29/345d3b7c32a527e10000000a114084/content.htm and this http://help.sap.com/saphelp_nw04/helpdata/en/f4/8620c6b58c422c960c53f3ed71b432/content.htm
Thanks,
Vijaya.

JDBC Ack Issue: CO_TXT_ROUTING_BACK_ERROR

Dear Experts,
I have a SAP>XI>DB scenario.
The record is succesfully inserted into the DB; but in RWB I am getting additional entries which failed. It seems to be some sort of Ack, which is not supported right now by my XI system. In SXMB_MONI; I am getting ACK error and it says: "Ack not possible"
This seems to be the message I am getting from the DB:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>SystemAck</SAP:MessageClass>
<SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>
<SAP:MessageId>09771B91-43A1-11DE-97FD-005056955D0F</SAP:MessageId>
<SAP:RefToMessageId>DE43A103-2435-DAF1-AD25-005056955D0F</SAP:RefToMessageId>
<SAP:TimeSent>2009-05-18T11:42:59Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Service>"MY RX SERVICE"</SAP:Service>
<SAP:Interface namespace="NAMESPACE">"INTERFACE"</SAP:Interface>
</SAP:Sender>
- <SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>"BS"</SAP:Service>
<SAP:Interface namespace="" />
</SAP:Receiver>
<SAP:Interface namespace="NAMESPACE">"INTERFACE"</SAP:Interface>
</SAP:Main>
And this seems to be the Error that I am getting 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="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="OUTBINDING">CO_TXT_ROUTING_BACK_ERROR</SAP:Code>
<SAP:P1>,"MY JDBC SERVICE"</SAP:P1>
<SAP:P2>,"MY BUS. SYS",,</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error occurred during back-routing Error in communication channel</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
My interface is asynchronous.
I want to eliminate the double entries in RWB and Ack Error in SXMB_MONI. Please help.....

<SAP:Stack>Error occurred during back-routing Error in communication channel</SAP:Stack>
i think there is some configuration done to receive Acknowledgement from the end system and send back to your SAP system...this part is giving an error....check what configuration is missing for IDOC acknowledgement.....
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
Also since yours is an SAP --XI -- JDBC scenario...there is one blog which takes the same flow in configuring the acknowledgements...just make a search you will get it.
my earlier reply was not intended for you....
Regards,
Abhishek.

NFE Produção - Código Status 204 Rejeição

Olá, Boa tarde!
Estamos com uma NFE da Produção parada, pois não estamos conseguindo atualizar o status dela.
No monitor de GRC a NFE aparece da seguinte forma:
Status NFE (bolinha vermelha): 05 resultado recebido
Status de Erro: 90 erro de sistema PI
Código Status: 204 Rejeição: Duplicidade NFE
A opção "Consulta do Status" está disponível, porém já tentamos várias vezes, aparece a mensagem: O processo de consulta status NFE foi inicializado. Atualizar a exibição NFE.
Atualizamos a página, porém não muda nenhum status.
No monitor J1BNFE a NFE está aguardando o retorno do GRC.
Não sei se tem algo a ver, mas recentemente fizemos a atualização da Versão para 2.0.
Antes o procedimento funcionava normal... agora as NFES estão paradas...
Aguardo comentários.
Obrigada.
Adriana

Bom dia,
Estou com esse mesmo erro, e não sei como resolver...
Ao clicar em consultar status(Monitor GRC) da NFE em questão, o status não é atualizado(consultamos no SEFAZ e a NFe Está aprovada)..
Verifiquei as msg na MONI e temos uma com o ACK NEG, porém desconheço o erro...segue os xml que consegui verificar na mensagem:
XML INBOUND:
<?xml version="1.0" encoding="utf-8" ?>
- <n0:nfeConsultaNF2 xmlns:n0="http://sap.com/xi/NFE/006" xmlns:prx="urn:sap.com:proxy:PIP:/1SAI/TASB4840BC26BF382F75BE8:700:2009/02/10" xmlns:n1="http://www.portalfiscal.inf.br/nfe">
<n0:cUF>41</n0:cUF>
<n0:tpEmis>1</n0:tpEmis>
<n0:tpAmb>1</n0:tpAmb>
<n0:type>1</n0:type>
<n0:versNum>001</n0:versNum>
<n0:mode>I</n0:mode>
- <n0:nfeDadosMsg>
- <n1:consSitNFe versao="2.00">
<n1:tpAmb>1</n1:tpAmb>
<n1:xServ>CONSULTAR</n1:xServ>
<n1:chNFe>41110300606549000124550000000231711903353574</n1:chNFe>
</n1:consSitNFe>
</n0:nfeDadosMsg>
</n0:nfeConsultaNF2>
XML RESPONSE:
<?xml version="1.0" encoding="utf-8" ?>
- <n0:nfeConsultaNF2 xmlns:n0="http://sap.com/xi/NFE/006" xmlns:prx="urn:sap.com:proxy:PIP:/1SAI/TASB4840BC26BF382F75BE8:700:2009/02/10" xmlns:n1="http://www.portalfiscal.inf.br/nfe">
<n0:cUF>41</n0:cUF>
<n0:tpEmis>1</n0:tpEmis>
<n0:tpAmb>1</n0:tpAmb>
<n0:type>1</n0:type>
<n0:versNum>001</n0:versNum>
<n0:mode>I</n0:mode>
- <n0:nfeDadosMsg>
- <n1:consSitNFe versao="2.00">
<n1:tpAmb>1</n1:tpAmb>
<n1:xServ>CONSULTAR</n1:xServ>
<n1:chNFe>41110300606549000124550000000231711903353574</n1:chNFe>
</n1:consSitNFe>
</n0:nfeDadosMsg>
</n0:nfeConsultaNF2>
XML ACK ERROR:
<?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">NEGATIVE_ACKNOWLEDGEMENT</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Negative acknowledgment triggered by a process</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Alguém teria alguma dica?
Edited by: João Luis da Silva Dovigo on Mar 16, 2011 6:20 PM

Application/UNKNOWN/APPLICATION_ERROR

Hi Experts,
 I am facing the an issue in production. The scenario is FILE -> XI ->SOAP, asynchronous. The message in the integration engine is successful. But I am able to see the error in the SOAP receiver communication channel. Please find below the audit log and kindly help resolve the issue. Thanks.

Message Data
Attribute Value
Status System Error
Repeatable Yes
Cancelable Yes
Error Category XI_J2EE_ADAPTER_SOAP
Error Code GENERAL_ERROR
Audit Log
Success Processing child message of multi-message with message ID ddcf1970-486b-11dc-995c-001a64092f70
Success Using connection SOAP_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
Success Message successfully put into the queue.
Success The message was successfully retrieved from the receive queue.
Success The message status set to DLNG.
Success Delivering to channel: CC_UpdateOperationProcInfo_SOAP_Receiver
Success MP: entering
Success MP: processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
Success SOAP: request message entering the adapter with user J2EE_GUEST
Success SOAP: completed the processing
Success SOAP: continuing to response message bc9d1030-486c-11dc-bd74-001a64092f70
Error SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault
Success SOAP: sending a delivery error ack ...
Success SOAP: sent a delivery error ack
Error MP: exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault
Error Exception caught by adapter framework: SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault
Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault.
Success The asynchronous message was successfully scheduled to be delivered at Sun Aug 12 08:43:17 SGT 2007.
Success The message status set to WAIT.
Success Retrying to deliver message to the application. Retry: 1
Success The message was successfully retrieved from the receive queue.
Success The message status set to DLNG.
Success Delivering to channel: CC_UpdateOperationProcInfo_SOAP_Receiver
Success MP: entering
Success MP: processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
Success SOAP: request message entering the adapter with user J2EE_GUEST
Success SOAP: completed the processing
Success SOAP: continuing to response message 04513be2-486d-11dc-c461-001a64092f70
Error SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault
Success SOAP: sending a delivery error ack ...

Hi All,
Today I faced the same issue. My scenario is File->PI->SOAP asynchronous communication.
Initially I did not provide user authentication information in my SOAP receiver communication channel where as the web service was with basic HTTP authentication. So I was getting error 'Application/UNKNOWN/APPLICATION_ERROR'.
Once I provided the user and password information in the receiver communication channel the scenario is working fine.
This is strange to me. If the problem is due to authentication then I would expect to get 'unauthorized' kind of error.
Anyway, hope this will help others who face same issue.
Regards,
Prasad

Idoc Acknowledgements - Logical System Name

All,
Stuck with a few issues with Idoc Acknowledgments which I hope SDN can help me with. For ease of understanding the problem, am splitting this into 2 Scenarios ,
Scenario 1
SAP R3 (Idoc ) - XI - File ( Business Service)
R3 Triggers Idoc to XI and XI sends this as a File to the target Application. AleAdudits can be sent back to the R3 system as shown in <a href="/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc">this</a> blog by Saravana by adding the Logical System Name to the Business Service.
Issue :
R3 has configured Partner Profile with respect to XI and this cannot be changed. To send the Idoc Ack's back to R3 we need to add the Corresponding Logical System Name to the Business Service.
The problem is - what if the Idoc is to be sent to 2 Different Business Service / Systems. The R3 expects an Acknowledgment with XI as the sender partner but we cannot share the same logical system across different Business Systems / services . The easiest solution seems to be to create different partner profiles in R3, one for each Business System / Service. But this is not possible currently.
Scenario 2: 
R3 - XI - BPM - Target
Idoc triggered from R3, are sent to a BPM and then from the BPM to a file. Everything works fine.
But, the problem lies that when the Ack needs to be sent back to R3, The ack errors out because no Logical System Name is associated with the BPM.
We do not want to add another logical system name to the BPM and thereby create another partner profile and the problem is similar to Scenario 1.
Solutions Explored
1. In the ACK_IDOCAdapter , I tried to select option Take Sender From Payload and Take Receiver from Payload.
But this does not seem to help. I can see the trace in MONI saying the ACK_IDOC adapter is choosen to send the ack back to R3 , but it does not take the Partner Names from the payload of the AleAdudit and errors out with error Unable to convert..
2. As this AleAduit is sent from XI back to R3 and is not a R3 (AleAduit) - XI - R3 (aleaduit) case, adding a entry as shown in Section 6 in
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb">this</a> document will not help.
Has anyone tried something of this sort. Any known solutions?
I hope the description of the problem made sense, if no, do let me know.
Regards
Bhavesh

Bhavesh,
Your problem as i understand -> The problem is - what if the Idoc is to be sent to 2 Different Business Service / Systems. The R3 expects an Acknowledgment with XI as the sender partner but we cannot share the same logical system across different Business Systems / services . The easiest solution seems to be to create different partner profiles in R3, one for each Business System / Service. But this is not possible currently.

If the IDOC is sent to 2 different business services/systems/Integration Processes, then it is very logical that an ALEAUDIT be sent for each of these business systems/services. Ideally, you SHOULD NOT look at sending a common ALEAUDIT for different recievers in XI, the reason being, failures could happen only for one receiver and NOT for others. Failure could be in the mapping/content conversion. I am assuming here that you are configuring XI to send back "ALEAUDITs" only for System Error Acks(hoping it is possible, since i see 3 XXXs in the IDXNOALE table).
So, it is logical that you configure a different LS in R/3 for each reciever system/service/IP, all these LS's will have one entry for ALEAUDIT in the Inbound params entered in WE20.
If your intention is to send ALEAUDITs back only in case of errors, it makes sense to create an entry for each receiver in R/3. If not, then it is a limitation.
Regards
Saravana

PI 7.4 java stack only, Acknowledgement creation not triggered

Hello everyone
I have one IDoc-To-File scenario working fine, including acknowledgements (ALEAUD) being sent back to the sending system. The message log in such cases looks like this:
But I have another IDoc-To-HTTP scenario for which the acknowledgement (ALEAUD) creation is not being triggered, thus the system that originally sends IDocs doesn't get back any acknowledgements. In the message details I can see this:
I believe that it is because of QOS = EO (async) and the http adapter continues (and fails) without waiting for a http status code coming back from the receiver.
Just to try it out I would like to set QOS to BE (best effort). How and where to achieve this?
Thanks anyone for some help!
Kind regards
Renaud

ok, in the message log I found this:
So this is clearly an error coming back from receiver system... sorry, didn't realize it somehow.
But still... why is no acknowledgement (ALEAUD) being triggered?
This is how I configured it in the Integration Builder and NWA:
Business System A with a sender communication channel B of adapter type IDoc_AAE
RFC Parameters = From NWA
Resource Adapter Name = A_RA
Ack Connection Factory Name (reuse NWA configuration) = A_CF
On the Ack Settings Tab I checked "System Ack Ok Requested" and "System Ack Error Requested" and "ALEAUD Special Handling Needed"
Connection from PI -> SAP ERP System A
In NWA I created a new Destination of type RFC called ACLNT<CLIENT> pointing to sender ERP system (A)
Connection Test (ping) is successful
Connection from SAP ERP System A to PI
In NWA I created a new Resource Adapter called A_RA and configured its properties like this:
Binding Key = PI_AAE_IDOC
destinationName = ACLNT<CLIENT>
gatewayServer = <IP of ERP system>
gatewayService = sapgw<instance n° of ERP system>
local = false
MaxReaderThreadCount = 5
multiRepository =
ProgramID = PI_4_A<CLIENT>
In SAP ERP system in SM59 I created a new RFC destination, type = T, as registered server program with same ProgramID (PI_4_A<CLIENT>)
Connection test (in SM59) is successful
To enable / allow acknowledgements...
I set the persistance parameter to true in the JavaIdocAdapter
I created a JCA Connection Factory on the outboundRA Resource Adapter. Within this JCA Connection Factory I put in Configuration Properties the destinationName = ACLNT<CLIENT> (the RFC Destination Name created earlier and pointing to the sending SAP ERP System A which should receive acknowledgement ALEAUD Idocs).
I did the same for the IDoc-2-File scenario mentionend in my 1st post... there acknowledgment messages are working fine.
Best regards
Renaud

Receiver AAE IDoc adapter

Hi All,
I have a doubt regarding receiver AAE Idoc adapter. There are three options available in java IDoc adapter namely Default, Manual and From NWA. In Default option, we just need to configure a RFC Destination in NWA but in From NWA option, we need to configure RFC Destination as well as Resource Adapter(JCA Connection Factory). So, I just want to know what is the benefits of using From NWA option over Deafult and what is purpose of configuring Resource Adapter in NWA?

Hi,
see the below link.
http://help.sap.com/saphelp_nw73/helpdata/en/bc/0341dd385945d49eb809c084cf3dea/content.htm
as per this link i should check the checkbox.
Configuring Acknowledgements for a Sender IDoc Adapter (AAE) Locate this document in the navigation structure
Procedure
    Choose the sender communication channel on which you want to enable acknowledgement settings.
    Choose the Parameters tab and then, choose the Ack Settings tab.
    On the Acknowledgement Parameters area, enter the following settings:
        System Ack Ok Requested
        Choose this option to receive XI system acks.
        System Ack Error Requested
        Choose this option to receive XI system error acks.
        Application Ack Ok Requested
        Choose this option to receive XI application acks.
        Application Ack Error Requested
        Choose this option to receive XI application error acks.
        ALEAUD Special Handling Needed
        Choose this option to enable the sender Java IDoc adapter to apply special handling to the incoming ALEAUD message. The adapter replaces the IDoc number of the ALEAUD message with the original IDoc number.
        Initially, the receiver Java IDoc adapter generates a unique IDoc number, which replaces the original IDoc number of the outbound message. This IDoc unique number is referred by the ALEAUD message. However, the ALEAUD message is not converted to an XI Ack message in this case.

USB CAN 8473 goes crazy

Hi, guys, my CAN USB8473 goes crazy.
I use CVI 8.5 to communicate with USB 8473. The software done by using CVI works all right before, when i use another USB 8473.
However, now, when i just try to initialise the CAN0, i find that the USB CAN is keeping sending CAN frames, then i open the NI-Spy, there is no action observed in spy,which means my soft doesnt give the order to send messages, but the CAN port just keep sending messages(i use a very good scope to get the active can activity). When i call the function to reset the CAN, it stop sending frames, but after i try to send just another frame, it starts sending frames endless which always goes with ACK error.
from what could i know if is my hardware problem? I dont want to believe the problem is my hardware, because it is a quite new USB 8473.
What is wrong?

Hi,
If you send a Frame and there is no receiver connected acknowledging the frame the can controller would transmit the frame over and over again until it becomes acknowledged or the driver closes the handle for the port.
The re-transmit ishandled by the can controller onboard automatically and it doesn't require api call, thus it doesn't show up in NI-SPY.
But you should be able to stop this, by closing the handle.
DirkW

B2B RosettaNet Rcpt Ack and Excp throws error "Unable to read the preamble"

Hello All,
We have configured a 2 way PIP Config and we are able to succesfully transfer the paload to the TP.
But when receiving the Ackowledgement and Exception, we are getting error "B2B-51705 Unable to read the preamble"
Can anyone help me on this
Thanks,
Sunil

Hi Anuj,
Just want to confirm one more thing
Below given the xsd used for Exception and Acknowledgement
Can you please confirm the format of the same
AcknowledgeMent
===========
<?xml version = "1.0" encoding = "UTF-8"?>









<xsd:schema xmlns:xsd = "http://www.w3.org/2001/XMLSchema">
<xsd:annotation>
 <xsd:documentation>
RosettaNet XML Message Schema
AcknowledgmentOfReceipt_MS_V02_00.dtd
This document has been prepared by Edifecs (http://www.edifecs.com/)
based On the Business Collaboration Framework from requirements
in conformance with the RosettaNet methodology.
 </xsd:documentation>
</xsd:annotation>
 <xsd:element name = "ReceiptAcknowledgment">
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element ref = "NonRepudiationInformation" minOccurs = "0"/>
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>
 <xsd:element name = "NonRepudiationInformation">
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element ref = "OriginalMessageDigest"/>
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>
 <xsd:element name = "OriginalMessageDigest" type = "xsd:string"/>
</xsd:schema>
Exception
=====
<?xml version="1.0" encoding="UTF-8" standalone="no"?>


<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified">
 <xs:import namespace="http://www.w3.org/XML/1998/namespace"/>
 <xs:element name="Exception">
 <xs:complexType>
 <xs:sequence>
 <xs:element ref="ExceptionDescription"/>
 <xs:element ref="GlobalExceptionTypeCode"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 <xs:element name="ExceptionDescription">
 <xs:complexType>
 <xs:sequence>
 <xs:element ref="errorClassification"/>
 <xs:element ref="errorDescription"/>
 <xs:element ref="offendingMessageComponent" minOccurs="0"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 <xs:element name="errorClassification">
 <xs:complexType>
 <xs:sequence>
 <xs:element ref="GlobalMessageExceptionCode"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 <xs:element name="GlobalMessageExceptionCode">
 <xs:complexType mixed="true"/>
 </xs:element>
 <xs:element name="errorDescription">
 <xs:complexType>
 <xs:sequence>
 <xs:element ref="FreeFormText"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 <xs:element name="FreeFormText">
 <xs:complexType mixed="true">
 <xs:attribute ref="xml:lang"/>
 </xs:complexType>
 </xs:element>
 <xs:element name="offendingMessageComponent">
 <xs:complexType>
 <xs:sequence>
 <xs:element ref="GlobalMessageComponentCode"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 <xs:element name="GlobalMessageComponentCode">
 <xs:complexType mixed="true"/>
 </xs:element>
 <xs:element name="GlobalExceptionTypeCode">
 <xs:complexType mixed="true"/>
 </xs:element>
</xs:schema>
Pleace correct me if I am wrong in these xsd's
Thanks,
Sunil

Getting error while getting ACK back from TP

Hi,
When my TP is sending ack back to me I am getting following error -
2008.12.24 at 11:06:19:672: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.RepoDataAccessor:getDocumentDefinition() given docTypeName: Pip3A4PurchaseOrderRequest given docTypeRev: V02.00
2008.12.24 at 11:06:19:674: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.RepoDataAccessor:getDocumentDefinition() given docTypeName: Pip3A4PurchaseOrderRequest given docTypeRev: V02.00
2008.12.24 at 11:06:19:674: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.RepoDataAccessor:getDocumentDefinition() reposDocTypeName: Pip3A4PurchaseOrderRequest reposDocTypeRev : V02.03.00
2008.12.24 at 11:06:19:674: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.RepoDataAccessor:getDocumentDefinition() reposDocTypeName: Pip3A4PurchaseOrderConfirmation reposDocTypeRev : V02.03.00
2008.12.24 at 11:06:19:675: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.RepoDataAccessor:getAgreementData() End..
2008.12.24 at 11:06:19:675: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.RepoDataAccessor:getAgreementDetails() ..End
2008.12.24 at 11:06:19:675: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.MessageModifier:updateDeliveryChannel() Updating DeliveryChannel information..
2008.12.24 at 11:06:19:675: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.MessageValidator:validateCollaborationInfo()
2008.12.24 at 11:06:19:676: Thread-10: B2B - (ERROR) Error -: AIP-50515: Collaboration revision "V02.03.00" in message is different from collaboration revision "V02.00" in agreement
at oracle.tip.adapter.b2b.tpa.MessageValidator.validateCollabInfo(MessageValidator.java:298)
at oracle.tip.adapter.b2b.tpa.MessageValidator.validateMessage(MessageValidator.java:123)
at oracle.tip.adapter.b2b.tpa.TPAProcessor.processTPA(TPAProcessor.java:664)
at oracle.tip.adapter.b2b.tpa.TPAProcessor.processIncomingTPA(TPAProcessor.java:196)
at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1810)
at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2554)
at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2424)
at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2379)
at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:527)
at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:374)
at java.lang.Thread.run(Thread.java:534)
2008.12.24 at 11:06:19:677: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: processIncomingMessage B2BDE
2008.12.24 at 11:06:19:677: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleExceptionBeforeIncomingTPA Enter
2008.12.24 at 11:06:19:677: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException
Our Trading Partner is using BizTalk B2B and we are using RosettaNet V02.00 as document exchange protocol. PIP Version we are using is V02.03.00
Please help.
Thanks & Regards,
Anuj Dwivedi

Hi Ramesh,
Thanks for your prompt response.
I am using the Document Type Pip3A4PurchaseOrderConfirmation with revision v02.03.00
But still we are getting the same error. My trading partner is sending an Exception to us in Service Conent. Actually he is sending messages in four parts-
=====
Preamble
Delivery Header
Service Header
Service Contents
======
In which part he should provide the required properties(docTypeName and docTypeRivision) to find the right Collaboration by Oracle B2B at our side?
Thanks.
Warm Regards,
Anuj Dwivedi

RosettaNet ack error

Similar Messages

Maybe you are looking for