PO Acknowledgment error

Hi Experts,
We are using EDI system to send the PO to vendor system and create sales order and after creation Acknowledgment will post to our PO.
here in some cases Ack idoc is failing with error 'Acknowledgment for PO item xxxxxxxx xxxx contains quantity variance.
this error is due to quantity difference between po and sales order.
can you please help me to allow posting of ack idoc even there is a qunatity difference.
Thanks & Regards
Gopi

the long text of the message ME794 explains what to do:
Diagnosis
The vendor has sent you an order acknowledgment relating to purchase order , item , via EDI. The acknowledged (confirmed) quantities exceed the under-/overdelivery tolerances that have been maintained in the PO item and have therefore not been adopted in the purchase order.
The total quantity confirmed amounts to <unit of measure> in comparison with the ordered quantity of <unit of measure>.
Procedure
Either change the over/underdelivery tolerances in the PO item
Change purchase order
Or get the vendor to send you a new acknowledgment with acceptable quantities.

Similar Messages

Receiving Acknowledgement error from SOAP application

Hi Everyone,
I am working on SAP-> PI -> SOAP scenario. The PI message shows Acknowledgment error
with the following error text :
"Adapter Framework caught exception: SOAP: response message contains an error
XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: javax.xml.rpc.soap.SOAPFaultException "
The message of the same scenario were processed successfully initially but today some of the message got
stucked with the Acknowledgement error from the receiver application.
I tried to resend the message from RWB but could not succeed.
Kindly guide to troubleshoot the issue.
Regards,
Robinson Thomas

Hi Robinson,
It's mean the Web Service Provider return you unknown message format. It can be due to error happening in the provider.
Youd should check with the provider what is the problem during that period.
Regards
Fernand

Give navigation to find ACKNOWLEDGEMENT ERROR in XI

give navigation to find ACKNOWLEDGEMENT ERROR in XI after resheduling the messages
send as early as possible.

Hi ,
are you able to send Idoc to XI sucessfully.
if you don't want ACK back from XI. go to transaction NOALE and mark the message type as ACK not req.
if you want the ACK back need to configure the ALE AUDIT IDoc back to R3 from XI.

How to suppress the Acknowledgement Error in IDOC to File scenario?

Hi -
I got the status in SXMB_MONI as 'Processed Successfully' for the IDOC to File scenario but the Acknoledgement status throws an error saying 'Acknowledgement not possible'.
I read one of the documents in the forums on how to suppress the acknowledgement using a table on R/3 side using IDXNOALE,
i tried that option but i still get the 'Acknowledgement not possible' error.
Is there any other way to suppress this error?
Thanks,
Tirumal

Hi Tirumal,
Receiver adapters that run on the Adapter Engine support system acknowledgments if they are requested by the sender. Acknowledgements are triggered when a message is successfully processed by the adapter or if an error occurs while it is being processed. Receiver adapters do not support application acknowledgments. The RNIF and CIDX adapters are exceptions to this rule, since they also support scenario-dependent application acknowledgments. Sender adapters of the Adapter Engine do not request any acknowledgments.
This means, JDBC adapter does only send system acks, however IDoc adapter is requesting application acks. Therefore as mentioned by the previous poster, you have to disable acks for this scenario using report IDX_NOALE.
Also go through these documents for any further help:
http://sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how to handle acknowledgments for idoc.pdf
http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
Regards,
abhy

Acknowledgment error : "No receiver could be determined" !?

HI,
This is my flow :
SAP R/3 sends idoc to a third party through XI. This idoc must be changed in flat file type CSV. This flow works fine but there is a problem in the acknowledgement : "No receiver could be determined".
What is the problem ?
Error :
<SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SystemAckRequested="false" SystemErrorAckRequested="true" ApplicationAckRequested="true" ApplicationErrorAckRequested="true" SOAP:mustUnderstand="1">
     <SAP:QualityOfService>ExactlyOnce</SAP:QualityOfService>
</SAP:ReliableMessaging>
<SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
     <SAP:TraceLevel>Information</SAP:TraceLevel>
     <SAP:Logging>Off</SAP:Logging>
</SAP:Diagnostic>
<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="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
     <SAP:P1/>
     <SAP:P2/>
     <SAP:P3/>
     <SAP:P4/>
     <SAP:AdditionalText/>
     <SAP:ApplicationFaultMessage namespace=""/>
     <SAP:Stack>No receiver could be determined</SAP:Stack>
</SAP:Error>
Thanks.
Best regards

Sorry but this error desapear. With have a new error : ATTRIBUTE_INV_SND_SERV
We use mapping conversion and CSV file channel.
Thanks

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.

Stomp: client acknowledge error message

Using OpenMQ 4.4 b04, I try to use client acknowledge.
I have found that the broker expects not only the message Id but also the subscription id.
If I use the subscription id which is in the message header and add it to the ACK Stomp frame, the broker displays these lines in the log file:
javax.jms.JMSException: Ack a message[ID:297-192.168.178.21(c1:a1:82:3f:f4:72)-1
731-1239293602031] that is not found in subscriber[{F90F7D8E-843A-4EBB-BA15-23B2
0F732060}]
        at com.sun.messaging.bridge.service.stomp.StompSubscriberSession.ack(Sto
mpSubscriberSession.java:175)
        at com.sun.messaging.bridge.service.stomp.StompProtocolHandler.onACK(Sto
mpProtocolHandler.java:643)
        at com.sun.messaging.bridge.service.stomp.StompProtocolFilter.execute(St
ompProtocolFilter.java:123)
        at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultPro
tocolChain.java:136)
        at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.jav
a:103)
        at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.jav
a:89)
        at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextT
ask.java:67)
        at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.
java:57)
        at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
        at java.util.concurrent.FutureTask.run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)Which special headers are expected by the broker in a ACK frame? If the Stomp frame does not contain a subscription header, the error log gives some hints which mention a "/subscription-to/" header:
WARNUNG: No subscription header specified, ACK all non-transacted subscription i
ds with prefix /subscription-to/ for message ID:409-192.168.178.21(b3:dd:75:42:f
:91)-1781-1239294021718
09.04.2009 18:20:30
SCHWERWIEGEND: ACK failed: Can't determine subscriber to ack message ID:409-192.
168.178.21(b3:dd:75:42:f:91)-1781-1239294021718. Please specify subscription hea
der

It's the STOMP ACK 'subscription' header. STOMP client should always specify a subscription header on ACK besides message-id header.
The exception you saw is a bug in ACK message for client ack mode. The client mode ACK problem has been fixed in build5.
MESSAGE
index:0
content-length:10
destination:/queue/q0
subscription:sub2
timestamp:1239309779559
redelivered:false
priority:4
expires:0
message-id:ID:7-10.5.81.239(80:17:42:1e:c5:e7)-55202-1239309779559
Message #0
ACK
message-id:ID:7-10.5.81.239(80:17:42:1e:c5:e7)-55202-1239309779559
subscription:sub2

IDOC Acknowledgement Error

Hi All,
I am getting "Receiver exists , No filters , No conversion , No version change" message in IDOC Status of ALEAUD. And IDOC has not been sent to XI System.
I have done the settign for Idoc acknowledgement.
What is the reason of this message.?

this is inbound message that i am getting..
<?xml version="1.0" encoding="UTF-8" ?>
- <ALEAUD01>
- <IDOC BEGIN="1">
- <EDI_DC40 SEGMENT="1">
<TABNAM>EDI_DC40</TABNAM>
<MANDT>900</MANDT>
<DOCNUM>0000000002416250</DOCNUM>
<DOCREL>620</DOCREL>
<STATUS>30</STATUS>
<DIRECT>1</DIRECT>
<OUTMOD>2</OUTMOD>
<IDOCTYP>ALEAUD01</IDOCTYP>
<MESTYP>ALEAUD</MESTYP>
<STDMES>ALEAUD</STDMES>
<SNDPOR>SAPEIT</SNDPOR>
<SNDPRT>LS</SNDPRT>
<SNDPRN>EITCLNT900</SNDPRN>
<RCVPOR>SAPXID</RCVPOR>
<RCVPRT>LS</RCVPRT>
<RCVPRN>XIDCLNT300</RCVPRN>
<CREDAT>20071105</CREDAT>
<CRETIM>190225</CRETIM>
<ARCKEY>A05D0C308BBB11DC8598001A4BA967D2 0000000000573053</ARCKEY>
<SERIAL>20071105171956</SERIAL>
</EDI_DC40>
- <E1ADHDR SEGMENT="1">
<MESTYP_LNG>Z_MLS_INBOUND_RECEIPT</MESTYP_LNG>
- <E1STATE SEGMENT="1">
<DOCNUM>0000000000573053</DOCNUM>
<STATUS>64</STATUS>
<STACOD>SAPB1999</STACOD>
<STATXT>& & & &</STATXT>
<STAPA1>Immediately processi</STAPA1>
<STAPA2>Unable to interpret</STAPA2>
<STAMQU>SAP</STAMQU>
<STAMID>B1</STAMID>
<STAMNO>999</STAMNO>
<STAPA1_LNG>Immediately processing not possible:</STAPA1_LNG>
<b><STAPA2_LNG>Unable to interpret EGOD3 as a number.</STAPA2_LNG></b> - <E1PRTOB SEGMENT="1">
<DOCNUM>0000000002416235</DOCNUM>
</E1PRTOB>
</E1STATE>
</E1ADHDR>
</IDOC>
</ALEAUD01>
In 'Ack' i am getting this message.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Ack xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Status>Error</SAP:Status>
<SAP:Category>transient</SAP:Category>
</SAP:Ack>

Acknowledgement errors in PI - JMS scenario

Hello,
We have a scenario R3 Idoc -> PI7.0 -> JMS. After the Idoc message is sent to PI, In the sxi_monitor, in acknowledgement status column, I normally see a red icon which says ack not possible. But for few JMS interfaces, I observe there is a green icon which says waiting for acknowledgement.
In the smq2 monitoring, I see queues for this acknowledgment message into error with IDOC_ADAPTER">ATTRIBUTE_INV_SND_PARTY.
Did someone face a similar scenario. Even though the messages reach the third party via JMS queue, these messages are collected in queue with sysfail error. Please help how to get rid of this.
Regards,
Swapna

If you do not want to have acknoledgement, in your sender system, run ABAP program "IDX_NOALE"
In "Maintain Partner System Acknowledgment" screen, specify your Sender Port and client
Then you can turn off following acknowledgements:
System OK
System Error
Application OK
Application Error
Regards
Liang

AckRequestNotSupported error in IDoc to file scenario

Hi,
I have a scenario from IDoc to file adatper, when i try to run this scenario, every thing is ok except there is a error in message monitor.
This error is regarding the Acknowledgment("Acknowledgment not possible"), But the ALEAUD IDoc have been sent to the orignal sender (IDoc side) with the empty content except the Header segment such as sender name, receiver name etc.
And when i tracted the detail information in message monitor, i got the following error information.
*<SAP:Status>AckRequestNotSupported</SAP:Status>*
*<SAP:Category>permanent</SAP:Category>*
I also went through some weblog and artical, i didn't got the solution.
If some body also have this error?
thanks & Best regards
Rocky
Following is My acknowledgment error information: FYI
*<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>*
*- 
- <SAP:Ack xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1" applicationAckNotSupported="true" applicationErrorAckNotSupported="true">
<SAP:Status>AckRequestNotSupported</SAP:Status>
<SAP:Category>permanent</SAP:Category>
</SAP:Ack>
Outbound Acknowledgment content:
- <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>030</SAP:MANDT>
<SAP:DOCREL>700</SAP:DOCREL>
<SAP:DOCNUM>0000000000036022</SAP:DOCNUM>
<SAP:DIRECT>2</SAP:DIRECT>
<SAP:IDOCTYP>ALEAUD01</SAP:IDOCTYP>
<SAP:CIMTYP />
<SAP:MESTYP>ALEAUD</SAP:MESTYP>
<SAP:MESCOD />
<SAP:MESFCT />
<SAP:SNDPOR>SAPO01</SAP:SNDPOR>
<SAP:SNDPRN>A01CLNT030</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
<SAP:SNDPFC />
<SAP:RCVPOR>SAPO05</SAP:RCVPOR>
<SAP:RCVPRN>A05CLNT231</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
<SAP:RCVPFC />
<SAP:TEST />
<SAP:SERIAL />
<SAP:EXPRSS />
<SAP:STD />
<SAP:STDVRS />
<SAP:STATUS>03</SAP:STATUS>
<SAP:OUTMOD />
<SAP:SNDSAD />
<SAP:SNDLAD />
<SAP:RCVSAD />
<SAP:RCVLAD />
<SAP:STDMES />
<SAP:REFINT />
<SAP:REFGRP />
<SAP:REFMES />
<SAP:CREDAT>0000-00-00</SAP:CREDAT>
<SAP:CRETIM>00:00:00</SAP:CRETIM>
<SAP:ARCKEY />
</SAP:IDocOutbound>

Hi Rocky,
Check the below links of setting up of ALEAUDUT RESPONSE:
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
Check this document on handling IDOC acknowledgements. This might give you some idea.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
Please check the above two links if u have missed anything in setting up the acknowledgement.Let me know if u need furthur information
Thanks,
Bhargav.
Note:Award points if found useful.

Error in IDoc to JDBC scenario

Hi friends,
I am configuring an IDoc to JDBC scenario in XI.When I am testing the scenario in Test Configuration then it is getting processed successfully but when I am tseting the entire configuration then in sxmb_moni the following error is showing:
"Error occurred during back-routing Error in communication channel". Please help as I am unable to understand the error.
regards
Debansu

Hi Debansu,
Please go through the link it may help to solve your problem.
JDBC Adapter / Acknowledgements
Error in back routing Error in communication channel
Regards,
Sridhar Goli
Edited by: sridhar goli on Aug 11, 2008 11:35 AM

URGENT: system error - Maual restart possible

Hi Experts,
I'm facing a problem in Xi prodoction. Both inbound and outbound are throwing system error - Maual restart possible. The user is restarting manually in order to post the invoice.
Basically this is retail project, from POS s/w to Xi to SAP R/3. The scenario is file to idoc(inbound) and idoc to file (outbound).
The error is :
<?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="PERSIST">MESSAGE_NOT_FOUND</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>XML message not found</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
The acknowledgement error is :
<?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="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert the sender service to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have gone throw the sdn post and blogs but i'm uable to trace the problem.
Kindly suggest me ASAP as this is business critical and posting have been stoped.
Regards,
Pawan

Hi,
Please find the interface determination trace. Hope this will help you to provide some suggestion.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="B" name="IDX_INBOUND_XMB" />
- 
<Trace level="1" type="T">User: XIBGUSER</Trace>
<Trace level="1" type="T">Language: E</Trace>
<Trace level="1" type="T">ALE-AUDIT-IDoc-Inbound Handling</Trace>
<Trace level="1" type="T">IDoc-Inbound-Handling</Trace>
<Trace level="2" type="T">Tunneling needed?</Trace>
<Trace level="2" type="T">Partytype = LS fallback to logical system</Trace>
<Trace level="3" type="T">Sender Interface</Trace>
<Trace level="3" type="T">WP_PLU.WP_PLU03 urn:sap-com:document:sap:idoc:messages</Trace>
<Trace level="1" type="T">Syntax-Check-Flag X</Trace>
<Trace level="1" type="T">IDoc-Tunnel-Flag</Trace>
<Trace level="1" type="T">Queueid</Trace>
- <Trace level="1" type="B" name="IDX_IDOC_TO_XML">
<Trace level="1" type="T">Get the Metadata for port SAPRT2</Trace>
<Trace level="2" type="T">----
</Trace>
<Trace level="2" type="T">IDX_STRUCTURE_GET Details</Trace>
<Trace level="2" type="T">Port : SAPRT2</Trace>
<Trace level="2" type="T">IDoctyp : WP_PLU03</Trace>
<Trace level="2" type="T">Cimtyp :</Trace>
<Trace level="2" type="T">RFCDest :</Trace>
<Trace level="2" type="T">Release : 700</Trace>
<Trace level="2" type="T">Version : 3</Trace>
<Trace level="2" type="T">Direct : 1</Trace>
<Trace level="2" type="T">SAPREL : 700</Trace>
<Trace level="2" type="T">----
</Trace>
<Trace level="1" type="T">Convert Segment-Definitions to Types</Trace>
<Trace level="1" type="T">Make Syntax check of actual Idoc</Trace>
<Trace level="2" type="T">----
</Trace>
<Trace level="2" type="T">IDX_SYNTAX_CHECK</Trace>
<Trace level="2" type="T">Port : SAPRT2</Trace>
<Trace level="2" type="T">IDoctyp : WP_PLU03</Trace>
<Trace level="2" type="T">Cimtyp :</Trace>
<Trace level="2" type="T">----
</Trace>
<Trace level="2" type="T">Create XML-Control Record</Trace>
<Trace level="2" type="T">Create XML-Data Records</Trace>
<Trace level="3" type="T">Create data Record E1WPA01</Trace>
<Trace level="3" type="T">Create data Record E1WPA02</Trace>
<Trace level="3" type="T">Create data Record E1WPA03</Trace>
<Trace level="3" type="T">Create data Record E1WPA04</Trace>
<Trace level="3" type="T">Create data Record E1WPA05</Trace>
<Trace level="3" type="T">Create data Record E1WPA01</Trace>
<Trace level="3" type="T">Create data Record E1WPA02</Trace>
<Trace level="3" type="T">Create data Record E1WPA03</Trace>
<Trace level="3" type="T">Create data Record E1WPA04</Trace>
<Trace level="3" type="T">Create data Record E1WPA05</Trace>
<Trace level="3" type="T">Create data Record E1WPA01</Trace>
<Trace level="3" type="T">Create data Record E1WPA02</Trace>
<Trace level="3" type="T">Create data Record E1WPA03</Trace>
<Trace level="3" type="T">Create data Record E1WPA04</Trace>
<Trace level="3" type="T">Create data Record E1WPA05</Trace>
<Trace level="3" type="T">Create data Record E1WPA01</Trace>
<Trace level="3" type="T">Create data Record E1WPA02</Trace>
<Trace level="3" type="T">Create data Record E1WPA03</Trace>
<Trace level="3" type="T">Create data Record E1WPA04</Trace>
<Trace level="3" type="T">Create data Record E1WPA05</Trace>
</Trace>
<Trace level="2" type="T">Partytype = LS fallback to logical system</Trace>
<Trace level="2" type="T">Set Sender Routing-object</Trace>
<Trace level="1" type="T">Set Receiver Routing-object</Trace>
<Trace level="1" type="T">Exit Function IDX_INBOUND_XMB</Trace>
<Trace level="1" type="T">COMMIT is expected by application !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>
<Trace level="3" type="T">Getting type of XMB...</Trace>
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="2" type="T">XMB kind = CENTRAL</Trace>
<Trace level="3" type="T">Start pipeline found</Trace>
<Trace level="2" type="T">Switch to external start pipeline PID = CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
<Trace level="3" type="T">No triggers found. OK.</Trace>
</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="3" type="T">system-ID = XIP</Trace>
<Trace level="3" type="T">client = 600</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIBGUSER</Trace>
<Trace level="1" type="Timestamp">2008-03-27T06:35:02Z UTC-7</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = DCFBC7EA238100F1B64A00145EDC94EF</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="3" type="T">QOS = EO</Trace>
<Trace level="3" type="T">Message-GUID = DCFBC7EA238100F1B64A00145EDC94EF</Trace>
<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="3" type="T">Generate prefixed queue name</Trace>
<Trace level="1" type="T">Queue name : XBTI0001</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0001</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="3" type="T">Setup qRFC Scheduler</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="3" type="T">Call qRFC .... MsgGuid = DCFBC7EA238100F1B64A00145EDC94EF</Trace>
<Trace level="3" type="T">Call qRFC .... Version = 000</Trace>
<Trace level="3" type="T">Call qRFC .... Pipeline = CENTRAL</Trace>
<Trace level="3" type="T">OK.</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="3" type="T">Version number = 000</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="3" type="T">Persisting message Status = 001</Trace>
<Trace level="3" type="T">Message version 000</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface WP_PLU.WP_PLU03*</Trace>
<Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:idoc:messages</Trace>
<Trace level="1" type="T">no interface found</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK.</Trace>
<Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
</Trace>
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="3" type="T">message version successfully read from persist version= 000</Trace>
<Trace level="2" type="T">Increment log sequence to 001</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="3" type="T">system-ID = XIP</Trace>
<Trace level="3" type="T">client = 600</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIBGUSER</Trace>
<Trace level="1" type="Timestamp">2008-03-27T06:35:03Z UTC-7</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline attributes</Trace>
<Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE = A</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline elements</Trace>
<Trace level="3" type="T">ELEMPOS = 0001</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0002</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0003</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0004</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0007</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0008</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0009</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="1" type="Timestamp">2008-03-27T06:35:03Z UTC-7 Begin of pipeline processing PLSRVID = CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
<Trace level="1" type="Timestamp">2008-03-27T06:35:03Z UTC-7 Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_RD_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Start without given receiver</Trace>
<Trace level="2" type="T">Classic Receiver Determination via Rules.</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
<Trace level="2" type="T">...valid Receiver w/o Condition: - e_solutionsPOS</Trace>
<Trace level="2" type="T">No Receiver found behaviour: 2</Trace>
<Trace level="2" type="T">Number of Receivers:1</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-03-27T06:35:03Z UTC-7 End of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 001</Trace>
<Trace level="3" type="T">Message version 001</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
<Trace level="1" type="Timestamp">2008-03-27T06:35:03Z UTC-7 Start of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_ID_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) e_solutionsPOS WP_PLU.WP_PLU03</Trace>
<Trace level="2" type="T">...valid InbIf without Condition: WP_PLU.WP_PLU03</Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-03-27T06:35:03Z UTC-7 End of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 002</Trace>
<Trace level="3" type="T">Message version 002</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 002</Trace>
<Trace level="3" type="T">Message version 002</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="3" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="3" type="T">Persisting message Status = 014</Trace>
<Trace level="3" type="T">Message version 002</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</SAP:Trace>
Thanks,
Pavan

Acknowledgement in XI

Hello..
If we send the data from XI to any other legacy system...and it is failed from XI-legacy.
Is it possible to re-process from XI it self?how the XI acknowledges error message and responds back to legacy?
thanks..

Hi,
Yes you can restart Messages which have failed when you send it to legacy systems. You can also get "Transport Ackowledgements" if you set it up in BPM and then you can have an exception handler for your block that will trigger the Alert.
Basically you have the ability to restart failed messages in XI when they are Asynchronous. It also depends where the Message has failed. if it is data issue then you need to correct the data and resend the Message but if it is something you can resolve in Mapping then yes you can restart the failed message.
Thanks
Ashish

Can 'Acknowledgmentcontains applic. errors' ALEAUD01 be caught by CCMS?

We are using 4.6c with XI 3.0 and SUS 3.0. If we send a purchase order to SUS and the document maps successfully in XI (XML Message Status 'successfully processed' in SXMB_MONI), but the Ack Status contains errors, we cannot generate a CCMS alert.
System errors in the XML message status column in SXMB_MONI will create an alert, but acknowledgment error will not.
We also tried setting up CCMS in the destination system (SUS 3.0 from SRM 4.0) to catch these errors but, alerts are only generated for outbound errors.
Anybody have any information that can lead us in the right direction on this?
Thanks in Advance,
Kyle

chose not to use ccms

HP Photosmart D11a is no longer online

HP Photosmart D11a was installed and operating on Windows Vista
after a while it quit working and problem seems to be with the printer itself
it is not online
light is on constantly
print order is not acknowledged
error message is printer no online

Download and run this utility: http://h20180.www2.hp.com/apps/Nav?h_pagetype=s-926&h_lang=en&h_client=s-h-e17-1&h_keyword=dg-NDU&ju...
What does it say?
Say thanks by clicking "Kudos" "thumbs up" in the post that helped you.
I am employed by HP

PO Acknowledgment error

Similar Messages

Maybe you are looking for