cancel
Showing results for 
Search instead for 
Did you mean: 

Status: To Be Delivered

Former Member
0 Kudos

Hi all,

I have sent a message through the Integration Engine and the following status remains on the message:

- To Be Delivered

What might be a reason for this message?

Cheers.

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

hi schotanus

The message to be delivered is nothing but it is delivered from adapter engine

to the integration server from here onwards u need to monitor for Integration

server messages , actually it comes in the message monitoring .

Rewards points if useful,

Regards,

Srinivas.D

Former Member
0 Kudos

OK, but when does this message usually appear???

Thanks in advance.

justin_santhanam
Active Contributor
0 Kudos

You will get this message when the message is in pipeline and haven't been delivered to the target system.

Best regards,

raj.

Former Member
0 Kudos

Hey

To_be_delivered means that the message was successfully delivered from Integration Server point of view and it states that the messages is initially handed over to the Messaging System.

TO_BE_DELIVERED occurs while the message is put into the Messaging System receive queue.

Thanx

Ahmad

justin_santhanam
Active Contributor
0 Kudos

Schotanus ,

Could you tell us wht scenario does this interface dealing with. In Message monitoring choose Adapter Engine and check for AuditLog for ur interface and check whts going on!!

Best regards,

raj.

Former Member
0 Kudos

It's a file to idoc scenario:

It delivers to the IE ok, however, after that (when it goes into BPM) it stalls.

This is the audit log for the deliverance to xi:

Time Stamp Status Description

2007-07-06 17:52:23 Success Send text file "Data_Vendor multi.xml" from FTP server "X/", size 5197 bytes with QoS EO

2007-07-06 17:52:23 Success Application attempting to send an XI message asynchronously using connection File_http://sap.com/xi/XI/System.

2007-07-06 17:52:23 Success Trying to put the message into the send queue.

2007-07-06 17:52:23 Success Message successfully put into the queue.

2007-07-06 17:52:23 Success The application sent the message asynchronously using connection File_http://sap.com/xi/XI/System. Returning to application.

2007-07-06 17:52:23 Success The message was successfully retrieved from the send queue.

2007-07-06 17:52:23 Success File "Data_Vendor multi.xml" deleted after processing

2007-07-06 17:52:23 Success The message status set to DLNG.

2007-07-06 17:52:23 Success The message was successfully transmitted to endpoint X.

2007-07-06 17:52:23 Success The message status set to DLVD.

Message was edited by:

A. Schotanus

Former Member
0 Kudos

Hey

>>after that (when it goes into BPM) it stalls.

why are you using BPM for a simple File to IDOC scenario?

also goto sxi_cache and check the return code of BPM there it must be 0,if its not then activate ur BPM there itself and resend the messages.

Thanx

Ahmad

Former Member
0 Kudos

> Hey

> >>after that (when it goes into BPM) it stalls.

> why are you using BPM for a simple File to IDOC

> scenario?

> also goto sxi_cache and check the return code of BPM

> there it must be 0,if its not then activate ur BPM

> there itself and resend the messages.

> Thanx

> Ahmad

The respective return code is 0. What's standardly goin on when this message appears?

Cheers.

Message was edited by:

A. Schotanus

Former Member
0 Kudos

Hi A. Schotanus !

Try to restart the J2EE engine.

Regards,

Matias

Former Member
0 Kudos

well return code 0 is correct,did you check sxmb_moni_bpe,see if you get any error there for your BPM

Thanx

Ahmad

Former Member
0 Kudos

also check smq1 and smq2,make sure you dont have any queues stuck there,restarting the j2ee engine might also help

Thanx

Ahmad