Messages in Scheduled Status

Hi all,
We have many messages in Sceduled category on the production system. The Status symbol is not as it is for a scheduled message. It reads as "Log version". Please let me know how to clear these kind of messages from SXMB_MONI.
Thank you

Hi Yashwanth,
If the messages are in scheduled state then the messages might stuck or still in the queue. Check SMQ1 and SMQ2.
Ref this thread: Program to delete the messages from XI Queue ?
Thanks,

Similar Messages

XML Messages in "Scheduled" status

Hi all,
The case is at ERP side running transaction SXMB_MONI, some XML messages from XI to ERP are found in "Scheduled" status. Around the same time, siimilar messages using same receiver interface are processed successfully. When we manual restart the "Scheduled" message, there will be an entry in READY status at inbound queue and we have to unlock the queue. After that, the message will be processed successfully.
Here are my questions:
(1) Why some messages in "Scheduled" status but similar messages are processed successfully?
(2) Is there any alert or notification mechanism that we can setup instead of running transaction SXMB_MONI manually?
(3) Is manual restart XML message a proper way to handle those scheduled message? Any way to automatically handle this message in ERP side?
Thanks in advance.

Donald,
Here are the answers to ur questions.
(1) Why some messages in "Scheduled" status but similar messages are processed successfully?
Some times the queues get stuck for various reasons. one msg will cause bottleneck for all other msgs behind it. there is no proper reason why this happens, however if it happens regularly then u will have to give it a thought.
(2) Is there any alert or notification mechanism that we can setup instead of running transaction SXMB_MONI manually?
Well, if the msgs r in the scheduled state then NO.
(3) Is manual restart XML message a proper way to handle those scheduled message? Any way to automatically handle this message in ERP side?
Manual restart is not the best way to handle msgs bcause you might loose track/ some msgs might error out together causing issues. (that has happend to us). its tough to keep track if that is the case and if its critical from business point of view.
If it is going out of R/3 then may be you can configure jobs to push the data periodically.
Regards,
Pavan

Messages in Schedule status in SXMB_MONI and going into queue in SMQ2.

Hi Experts,
All messages in XI going to schedule status in SXMB_MONI. When i check in SMQ2 to release after some time the messages are going to "SYSFAIL (Time limit exceeded)" status.
When i double click on the message in SXMB_MONI, the system is going to "Runtime Error (TIME_OUT)".
Could anyone please help me how to fix this issue.
Thanks in advance,
GRK

Hi,
my scenario is file to idoc....
I have set paraemter in SXMB_ADM as below.
Category Parameters CurrentValue DefaultValue
RUNTIME HTTP_TIMEOUT 100000 0
I have gone through as you suggested still when i double click on message in SXMB_MONI...i am getting Runtime Error (TIME_OUT).
Please do help me..
Thanks in advance.
Krish

Messag in scheduled status

Hi
I have some message in XI which are in the schduled status and are stopped becuse the que stopped . Now i want to delete these messages without processing them
Any clues how to achieve this

hi,
you can delete them from queues directly - transaction SMQ2
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

ABAP program to Cancel messages in Scheduled/Recorded status?

Hi,
Thanks for reading my post...
Can anyone tell me whether there is an ABAP program available (or a variant) that will Cancel messages that are in Scheduled (or Recorded) status?
Messages to be sent from ECC to PI were not sent and are left in Recorded status in ECC. I cannot find the documentation to explain what this status is, but I'm presuming that it's similar to the Scheduled status in PI (though there's not much documentation about that either - for example, what's the difference between the 'green flag' Scheduled and the 'green flag' Released for Processing (WS)? ). {Note to SAP: Could we have a state transition diagram please? Simple, concise and effective.}
Anyway, the 'tick-pencil' button in SXMB_MONI (aka. CTRL-F8) can be used to cancel the messages in Scheduled/Recorded status. But I'm looking for an ABAP program to do this. The documentation seems to 'suggest' that this button might do the same thing as the ABAP program RSXMB_CANCEL_MESSAGES. However, this ABAP program does not cancel messages in Scheduled status (only the messages in Error), whereas the SXMB_MONI CTRL-F8 'tick-pencil' will cancel messages in Scheduled status if they are selected.
Is there another ABAP program available to cancel messages in Scheduled status - or is it possible to create a variant of RSXMB_CANCEL_MESSAGES that will do this? (I'm not an ABAP programmer and I've never created a variant, but looking at the code, it seemed it might be possible to get the program to read messages in Scheduled status rather than Error status.)
Many thanks for any help.
Mark

Messages are in scheduled status because they still in the queue in either 'READY' status or 'EXECUTING' status (see SMQ1/SMQ2). You don't want to automatically cancel messages that are in scheduled status because that means you are also going to cancel good messages. However, in some cases, you may want to cancel such messages especially when the message in the queue has been in 'Executing' status for long time (happens in case of long running mapping program or dropped connection etc). Such cases warrant manual intervention and hence the behavior as noted by you.
If you can tell me why exactly you want to cancel messages that are in scheduled status, I can help you more.
Thanks
KK

Scheduled Status in Message Monitoring

Hi All,
We have a scenario from DB- DB using Java Proxies. The Message interfaces are defined as Asynchornously with EO mode.
Usually the sender channel picks data and tirggers Java Proxy. Proxy process all records and send the status back to sender in 5 mins.
But when I started multiple interfaces at the same time, I observe that one interface is taking 15 min and while that interface is in processing state, the other interface which started at that time are also in Scheduled status. But the sender channel picks data for every 5 mins, which is creating duplicate records.
The interfaces which are in Scheduled status are getting processed only after that interface ( taking 15 min) gets processed.
Why is this dependency on other interfaces and is there any way to avoid this dependency?
Please suggest.
Regards,
Srini

you can do queue/message prioritization.
but I suggest to use one status field in DB, when you are polling DB to select records , immidiately change staus to picked and after processing successfully change it to processed.

Proxy messages are stucked in SMQ2 as scheduled status

Hi,
I am doing File(FCC) >PI 7.0>ABAP proxy. (ECC) Scenario.
Once i pick and process the file, the resultant message is updating the table in ECC through ABAP proxy. These messages are getting stucked in queues (SMQ2) in ECC. My message is not having much data , it is very less in size.
And there is no messages in Queue.
I register all queues in SMQR in PI and ECC.
Does I need to do any activity in ECC or PI? What could be a problem. Please suggest .
Thanks
Ayub

Hi Venkata,
Thanks for very quick replay.
Are the messages stuck with any error?--> First I can see the Green Color Flag as scheduled status, I open the message I can see there is no error message.Bt when I have look at end of the message in SXMB_MONI at Q.Status , I can see Message Has error
In SMQ2 -->
Cl. Queue Name               Entries    Status   Date 1     Time 1   NxtDate           NxtTim                  Sender ID                        Wait for queue
200 XBTR0009                         1 SYSFAIL 24.02.2012 10:53:34 24.02.2012 10:53:34      R3DEVQA_RDV_01
And when I double click the XBTR009 I can see the below message :
Cl.       User                  Function Module                 Queue Name                Date        Time                       StatusText
200 ALEREMOTE    SXMS_ASYNC_EXEC                 XBTR0009                  24.02.2012 10:53:34 Screen output without connection to user.
This are status of the messages. Please help me.
Regards,
Ahmed

How to clear the message which are in scheduled Status in PI 7.3

Hi,
We want to clear/cancel the message in Message monitor which are in scheduled status in PI 7.3.
It only a JAVA Stack System , We have been trying to clear the message manually but it take more time resulting into performance issue.
Is there some other way we can clear it from Database level.
Our Database is Db2 9.7 with Fix Pack 5
Can anyone help me in clearing the message at fast speed ?
Thanks in advance
Amit Shedge

Hi,
First we check the status of Message
a) db2 => select count(*) COUNT, status from sap<sid>db.bc_msg group by status
COUNT STATUS
110        DLVD
641623   NDLV
2 record(s) selected.
Then we update the status of Message to Failed
b) UPDATE BC_MSG SET STATUS='FAIL' WHERE STATUS IN ('DLNG', 'TBDL', 'WAIT', 'HOLD', 'NDLV') AND SENT_RECV_TIME <= '2014-22-03 00:00:00'
c)
select count(*) COUNT, status from sap<sid>db.bc_msg group by status
COUNT STATUS
183      DLVD
641623 FAIL
d) Then we started the Standard deletion Job in NWA
db2 => SELECT COUNT(*), STATUS FROM SAP<sid>DB.BC_MSG GROUP BY STATUS
1 STATUS
98 DLVD
And the message got deleted.
Thanks & Regards
Amit

Send Commit to message stuck in "Message Scheduled" status

Hello,
I generated some messages using ABAP Proxy. However, the commit work never happened in the program that created the message. Now these messages are stuck in "Message Scheduled" status. How can I push the message forward. Can I trigger a commit? If so, how?
Regards
Cerish

Hi Cerish,
Are you getting this status in the XI ? If so, go to Queue Monitor and try to activate the same.
/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
Also check the SXMB_MONI of Application System(R/3) if you have a access about is proxy message is executed or not .
If the status is restart not possible, then you need to reprocess that.
Hope this helps,
regards,
moorthy

Manage Queues - Messages are in Schedule status after upgrade to ERP2004

Hi,
We upgraded SAP to version ERP2004. ABAP proxy XI messages are in schedule status even though we deregister and register & activated all queues.
When I click on the queues it is in running status.
Does anyone has any idea where should I look?
Thanks in advance!
Mrudula

Hi,
my scenario is file to idoc....
I have set paraemter in SXMB_ADM as below.
Category Parameters CurrentValue DefaultValue
RUNTIME HTTP_TIMEOUT 100000 0
I have gone through as you suggested still when i double click on message in SXMB_MONI...i am getting Runtime Error (TIME_OUT).
Please do help me..
Thanks in advance.
Krish

Messages goes into scheduled status in adapter engine

Hi all
we are doing idoc to file scenario with direct mapping. the messages are getting processed in integration engine sucessfully. the messages are getting into scheduled status in the adapter engine even when there is less load in the server.
Thiis specially happening for IDOC to file scenario only. Any help is highly appreciated
Thanks

>
> the system is quite good at the moment but the some of the messages again into scheduled status like ( 10 out of 1000 messages ) . the system is not performing at 100 % rate since some messages moves to scheduled status. Is still the performance can be improved in any other ways ?
>
This is really strange behaviour , If Communictaion channel functioning correctly then all succesfull messages should deliver to Receiver system.
Better to check payload of scheduled messages(if wrong payload obiously it goes schedule status),try to to reprocess them.
I never used XCOPY command,so no comment on that.
Regards,
Raj

Messages remain in Scheduled status in message monitoring in RWB

Hi PI experts,
I have got a situation where there are several messages showing in the Scheduled status. I followed the path RWB > Message Monitoring > Adapter Engine > Database (Overview) > Display.
QoS for these messages is EOIO, however there are no messages stuck in the queue. All other channels are running smoothly. Only with this particular channel the messages remain in Scheduled status for a long time.
I am neither able to make out the roor cause nor reprocess/resend these messages. Pleaes help.
Regards,
Dhawal

Hi Suraj,
What you said is absolutely correct. However, as I mentioned, the error message was not visible in RWB.
My problem just got resolved. What I did is this,
I followed the link http://<server>:<port>/MessagingSystem/monitor/monitor.jsp which is SAP Message Display Tool.
Here in EOIO Sequence Monitor I found the error message and it's predecessor. When I resent the erroneous message from here, all subsequent Holding messages got processed.
Thank you everyone for your help. Have a gr8 day...
Best Regards,
Dhawal

Delete Successfull Message but error or schedule status in outbound ?

Hi XI Expert,
I have problem to delete the xml message with status Processed Sucessfully but got error / schedule status in outbound message. I can cancel this type of message, so this message will be persistent forever in my database.
could you advise how to cancel this message so the deletion job will remove automatically.
Thank you and Best Regards
Fernand

Hi All,
I already set PESIST_DURATION for DELETION and also running RSXMB_DELETE_MESSAGES.
but then those message with Status = Success but having error / schedule status still in database, i can't even cancel the message.
so any idea how to cancel or delete this type of message.
Best Regards
Fernand

Proxy messgs on ECC in scheduled status - released for processing (PI 7.1)

Hi guys,
I have set up a scenario (ABAP Proxy(ECC)->(using WS adapter)PI7.1->SOAP) and the outbound messages on the ECC remain in the scheduled status (green flag) saying "Released for processing (WS)". Why? Must there be some processing be executed? Manual? Or job?
Any help on this appreciated, Olian

Hi Olian
Try applying the solution in the SAP note #1129614 SP2: WSRM sequences process only the first 3 messages.
Regards
Mark

Message in scheduled state

Hi Experts,
In our production system, messages are frequently going to 'scheduled for outbound processing" state. After the manual retry the messages are going through. We are planning to setup RSQIWKEX, RSARFCEX and RSXMB_RESTART_MESSAGES for automatic restart of the messages.
However, my question here is, why the message is going into scheduled status? When i compare a message which is in scheduled state, i find the below message in the trace.
<Trace level="1" type="T">Going to persist message + call qRFC now...</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">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="3" type="T">Persisting message Status = 012</Trace>
<Trace level="3" type="T">Message version 003</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="2" type="T">Leave pipeline processing after LR because of receiver-wise queueing</Trace>
</Trace>
After manual restart,
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="3" type="T">Persisting message Status = 012</Trace>
<Trace level="3" type="T">Message version 003</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
- 
<Trace level="3" type="T">Trace object available again now. OK.</Trace>
<Trace level="3" type="T">manual Restart Flag X</Trace>
<Trace level="3" type="T">Message Guid 64B3B5B0AA3211DFCEE100144F64B6EF</Trace>
<Trace level="3" type="T">Version 000</Trace>
<Trace level="3" type="T">Pipeline ID CENTRAL</Trace>
<Trace level="3" type="T">EOIO Force I</Trace>
<Trace level="3" type="T">Restart Trace</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="T">Error of the prevous version:</Trace>
<Trace level="3" type="T">Area</Trace>
<Trace level="3" type="T">Error ID</Trace>
<Trace level="3" type="T">Restart of Queue?</Trace>
<Trace level="1" type="T">Persisting message with status ManualRestart, version: 003</Trace>
I can find this trace message for all the scheduled messages.
<Trace level="2" type="T">Leave pipeline processing after LR because of receiver-wise queueing</Trace>
Can you guys help to understand why this is happening and what could be the root cause?
thanks in advance.
Regards,
Ravi

Hi all,
Thank you very much for the feedbacks.
Please allow me to ask few more questions.
1. How does the RSQIWKEX work? The purpose of the report is to reset the queue. If the queue is reset what will happen to the messages which are struck?
2. What is the difference between resetting the queue and restarting the messages?
3. If the message in the queue is failed due to genuine reason, if the report reset or restart the message, will it again block the queue, since the message will fail again? How this scenario will be handled by report?
4. Probably a very basic question, if a queue is retrying for a message or closed saying SYSFAIL, Will not PI automatically use another queue to process the rest of the messages since the QoS is EO? Why the messages are getting pilled up in the same queue?
Thanks in advance for your effort.
Best regards,
Ravi

Messages in Scheduled Status

Similar Messages

Maybe you are looking for