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

Similar Messages

Proxy - File Adapter - "Still awaiting acknowledgment"

Hi,
I have a "Proxy -> BPM -> File" scenario and have configured acknowledgment. When the data is sent from proxy and written to file without errors I get the correct acknowledgment back to the R3 system. But when the file can't be written (FTP cant be reached) then I get an error in the BPM step but get an Wait step in R3. "Still awaiting acknowledgment"
sxmb_moni in PI:
Processed successfully@ @Still awaiting acknowledgment @ 04.08.2009 14:47:18 14:47:18 @R3System
Processed successfully@ @Acknowledgment contains system errors @ 04.08.2009 14:47:19 14:47:19 @Integration Process
In SWWL I see this status:
Waiting for event 'SEND_OK_TRANSPORT' of object type 'CL_SWF_XI_MESSAGE'
Maybe it has something to do with the "Guaranteed delivery". It retries 4 times and maybe it is waiting for an retry limit or something. I am not sure.
Any ideas on this one?

Shouldn't this be a "Acknowledgment contains system errors" ?
Are you implementing any logic once the deadline is met?
To send the NACK to R3 you need to have a Send step in your Exception/ deadline branch which will send the required message to R3.
A similar approach is shown here: /people/michal.krawczyk2/blog/2006/06/22/xi-playing-with-the-file-adapters-acknowledgments
Instead of the Control Step you need to have a Send Step.
Update:
Please note that any acknowledgement from AE will come into the BPM and will not go directly/ automatically to R3. The meaning of acknowledgement coming back to the Sender Application means ACK/ NACK to the BPM and not any other system.
Regards,
Abhishek.
Edited by: abhishek salvi on Aug 5, 2009 2:48 PM

IDOC to flat file "Still Awaiting Acknowledgement"

Hi All,
Our scenario is IDOC to flat file .
I have created User module also in receiver communication channel.... but I didn't create FCC parameters
please see the attachments, even I am getting "Still Awaiting Acknowledgement" in sxmb_moni.....
could you please tell me why I am getting that?
Thanks In Advance....
Vishnu pallamreddy

Hi Vishnu,
Check this below discussion,
Still awaiting acknowledgment
Are you sending test message from RWB or Source system, try to trigger message from Source system and see the status.

Still Awaiting Acknowledgement in SXMB_MONI - RFC Adapter

Have a scenario where we are using an RFC adapter on the reciever end to bring in data into R/3. The message in SXMB_MONI is showing successfully processed, but in column "Ack Status" - the icon states "Still Awaiting Acknowledgement". As a result of this the data is not being posted into R/3.
What is the best way to check the reason for "Still Awaiting Acknowledgement" and how to fix the problem so that the data is successfully processed in the R/3 system as well. Have already checked the adapter engine for adapter RFC and it does not show the any status - error or successful.

Hi,
RFCs usually use application acknowledgements and not system acks, and hence we shouldn't be getting that 'awaiting ack' symbol in the moni.
Try unchecking the 'maintain order at runtime' checkbox in interface determination and see if that helps.
Also make sure that the sender adapter's quality of service(QOS) is not EOIO.
Regards,
Smitha.

To remove Acknowledgement status in Async scenario.

Hi All,
I have a async scenario where in Sender is Business System and Receiver is a Business Component(Business Service).
Sender - FTP
Receiver - Http
I tested using the given payload in RWB. The message reached successfully and target confirms it.
But there is a question mark in the acknowledgement Status column in MONI saying " Still awaiting Acknowledgement".
My question is though message processing is successful and there is no issue, how would i be able to tell PI that there is no acknowledgement expected from target system and how would i be able to remove that question mark.
Thank you,
Kevin

Thanks.
When i Observe the trace I see the following message
<SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" ApplicationAckRequested="true" SOAP:mustUnderstand="1">
<SAP:QualityOfService>ExactlyOnce</SAP:QualityOfService>
How would i be able to make This : ApplicationAckRequested="FALSE"
and if i am able to do.. is this Integration specific?
Please help.
Thankyou,
Kevin

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 <i>all</i> ALEAUDs regardless of status...
Regards,
Thorsten

SRM 5.0 Confirmation in Awaiting Approval Status

We have the confirmations in "Awaiting Approval" status.
I had checked the following steps but still the status remains as-is.
1. Transaction SWUD
2. Enter workflow WS10400010, press enter
3. Execute 'Test environment'
4. Check 'Including subworkflows'
5. Execute 'Consistency check for components'
There are no errors for BUS2203 (Confirmation business object).
I have cross checked the BUS2203 for WS10400010 Active Status is both T-Codes SWETYPV and SWE2.
We had a previous issue of BUS2203 with some errors and that went away after following steps in OSS Note and SDN comments. Note 962488 - "Workflow definition '&' not in version '&' (WD 401) and SDN.
WS10400010 is No Approval Workflow for confirmations that is active and classified as General Task.
Can you please advise on this status issue?

Please analyse the Workflow log from SWI2_FREQ. I think you can check this issue in SRM forum. I think this is discussed.
Thanks
Arghadip

Buyer change the PO line items and end up with Awaiting Approval status.

Can you please help to look into this issue.
1.Buyer change the PO line items and end up with Awaiting Approval status.
2. But user claim that she got enough limit and should not route to her manager's approval. Also check with her manager and this PO do not exist his queue.
Any clue or tips on how to investigate on this issue. All your tips are appreciated,
-Rick

You cannot change these POs because their changed version has status
'Deleted'. My proposal to fix them will be the following:
You will have to set changed version as closed(DOC_CLOSED set to X)
and in active version set DOC_CLOSED to space.
__-For the above statement, Can you guys please let me know, which table DOC_CLOSED belongs to and what are the steps to do this, as i come from a functional back ground.__

Idoc- XI- Idoc - still awaiting acknowledgement

Hi guys!
We send Idoc->XI->Idoc and in sxi monitor we have a green flag - still awaiting acknowledgment. What does it mean? How can we be sure, that Idoc is received bu target application?
Thanx olian!

Hi Olian,
One way is to logon to R/3 system and use tcode WE02 or WE05 and there give your idoc type and press F8. you can see your idoc here.
Also go through it.
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
Note: IDoc technology supports its own acknowledgment technology, namely the ALE Audit. Here there are no acknowledgment requests from the sender. Instead, the receiver decides whether an acknowledgment IDoc should be sent back to the sender based on the ALE configuration. These acknowledgment IDocs are only used for monitoring on the sender side.
IDoc technology is the only technology in which positive acknowledgments from the application contain data. This data is sent by the IDoc adapter in an acknowledgment IDoc if the sender is an IDoc system. Otherwise, the data is discarded.
For the inbound IDoc adapter to be able to send an acknowledgment IDoc to the sender, a communication channel with the interface ALEAUD.ALEAUD01 must be maintained for the sender.
Regards,
Sarvesh
Message was edited by:
Sarvesh Singh

Shopping Cart in "Awaiting Approval" Status

Hi All,
There is a SC which requires an approval from one approver. The SC has gone to Approvers inbox for approval. The approver has approved the SC. After this the SC is not getting approved and its hanging in Awaiting Approval Status.
We are using N-Step BADI
When I was checking on this I was seeing entries in SM58 as below.
Caller       Function Module                Target System                    Date       Time     Status Text
XXXXXXXXX SWF_RUN_REMOTE_SERVICE         WORKFLOW_LOCAL_100               03/04/2011 06:34:01 Name or password is incorrect (repeat logon)
XXXXXXXXXX SALRT_CONFIRM                  WSCAH003SAP01_SR1_62             03/04/2011 06:34:01 Name or password is incorrect (repeat logon)
your valuable suggestions are very helpful.
Regards,
Satya.

Hi,
Thats strange because the error 'Name or password is incorrect' usually occurs when RFC destination is not appropriate.
Some quick checks
1. Automatic workflow customisation (SWU3) done? All green?
2. Remote logon working?
Also check this troubleshooting link http://www.abovesoft.com/analyzertroubleshooting.html
Regards,
Nikhil

Po in awaiting approval status in SRM 4.5

Hello Friends,
I am working on SRM 4.5,
I am facing a problem in completing the workflow of a PO. My SC is approved the PO which is created is with the status
Stats:
HEADER     E0002
HEADER     I1015          Awaiting Approval
HEADER     I1021          Created
HEADER     I1038          Complete
HEADER     I1043          Ordered
and workflow status:
Workflow Item:
Workitem-ID        000041330725
Task               WS14000145
Text               BAdI approval for Purchase order no. 2001013185, GUID 94E89401F7EF8A4EA8898F4A67A288F5
Status             STARTED
Statustext         In Process
Date               29.04.2014
Time               16:22:55
Now what should i do to complete the workflow. Is there any transaction or function module or any table with which i can complete the workflow??
Thanks in advance,
Sarnava.

Hi Sarnava,
Is your PO waiting for approval or is it struck in awaiting approval status.
Check SM58 transaction to see if there is any failures on the day of PO creation.
If there is no failure and you want to complete the PO manually go to transaction SWIA and enter the header work item id and then click on complete manually. This will complete the workflow.
Regards,
Suresh

How do we identify SC that are stuck in awaiting approval status?

All,
Extended Classic Scenario   7.01
We have Shopping Carts set up for auto approval.    From time to time some Shopping Carts get stuck in awaiting approval status and we need to manually force them to go.   We have not been able to identify a root cause for this so we would like to create an abap that would identify those SCs that are stuck then submit   BBP_REQREQ_TRANSFER   to transfer those SCs.
The problem we are having is finding the correct combination of status's that will capture those SCs that are truly awaiting approval.
We first find all those SC with status = I1015 (awaiting approval)
Then we exclude those with status i1040 (deleted) and i1129 (followon document created)
It seems in our testing that sometimes the status i1129 has an "X" in the inactive column.   Should those then be reprocessed and therefore not excluded?
Thoughts...
Sandra

Hi Sandra,
For your code logic, I1129 with inactive X should be included to get the list of SC which are in awaiting approval or may be approved but without follow on doc.
But could you check if you get any message in RZ20 after the follow on doc is created and it becomes inactive ?
may be you can check the SAP note: 1499352 - SRM Transfer: Redesign, bug fixes
Best Regards,
Anil

How to get acknowledgement status for PO

Hi!
I would like to write a program which gets the acknowledgement status from IDoc Processing for a given purchase order number.
How can I do that? In which table can I find the link between IDoc and PO? How to get the status?
Thanks in advance
Christian

EDIDS -- table
Check in the below link to update the staus and find the application objectof an idoc
http://www.sapgenie.com/sapedi/idoc_abap.htm#Getting%20IDocs%20linked%20to%20Application%20documents

Bidding Engine - Bids waiting in "Awaiting approval" status

Hello SRM Gurus,
We have SRM 5.0 bidding engine implemented. We have been using bid invitation for about 6 months now. For the last couple weeks we are having an issue where the bid invitations is stuck in "Awaiting Approval" status. We are not using any approval process.
I would appreicate it if any one could help me with resolving this issues.
Thank you very much

Thank you for your response.
No, the problem is that we are not able to even able to publish the Bid Invitation. Our buyers are creating the Bid invitation and put it in hold for adding additional information at a later time. When they come back to publish it - it says bid invitation is already in approval process and does not allow them to publish it.
Hope this info helps, Let me know if you need additional information.

Purchase order in 'awaiting approval' status but no approval required

Hi
I am using SRM 4.0 SP 13. There is a purchase order which shows that no approval is required in the approval tab, but the overall status is 'awaiting approval'. Please can you advise if this is a Support pack issue? I have checked the workflow WS14000075 which is active.
Regards
Rajeev

Hi
You would need to check if the workflow has been able to release the PO properly. Only after successful release completion by workflow, PO status gets changed to ordered from awaiting approval. Check the workflow log to see if there are any errors. Use txn-SWI1 or SWI6 to go into workflow log. Also reactive your workflow WS14000075 using txn swdd and try creating new PO.
Regards,
Sanjeev

Awaiting Acknowledgement status

Similar Messages

Maybe you are looking for