Message in scheduled st

Hi Friends,
Its a support issue. A message is in scheduled status(green flag) and when i try to restart i am getting error something like 'the message is already in scheduled state'. I heard that if we unlock the queue the issue can be resolved, Is that true? If yes then how to unlock the queue?
Thanks,
Suresh.

Hi,
Generallly, message will be in schedulate state if any messages are struck up in the queue...
from sxmb_moni, you can traverse to that queue and delete the erroe entry.
Select you message which is in schedulate state,....go to right of your window...you will find the queue starting with XBQT00001...Click on this queue..you will get the queued messages...and manually delete the entry.
Regards,
Sreeni.

Similar Messages

Messages getting scheduled in SAP ECC Box:Messages getting stuck in Inbound

The scenario is -
JDBC Sender-->> SAP PI-->> ECC Server(via ABAP proxy)
The Interface is running properly in SAP PI & then the messages are getting posted to the Inbound queues in SAP ECC Box. Generally it takes few seconds for the messages to get processed, but now all are getting scheduled in the Inbound queues(in different channels as seen in SMQ2)
We re-ran the interfaces again a few times, but all of them kept getting scheduled. Finally, after 2 hours one of the messages got processed. I suppose we won't face any problem now onwards.
Though I can see several suggestions like registering the queues & assigning dedicated queues to the interface, none of the blog suggest the probable cause of the event?
Can this be due to some issue in the server(heavy pressure of data in the server during the period/issue in the queues??)
I found the following links regarding issues like these --
XML file getting stucked in queue in ECC
Message in scheduled state
Thanks

Is the printing issue with one specific printer or across system.
What method you have configured for output device.
There should be any issue if you add spool work process to Application server.
Then you should be able to configure spool server load balancing. (Search on help.sap.com for spool load balancing)

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

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

ME84 / Messages for scheduling agreement Release

Hallo,
I wold like to create SA releases(agreement type = LPA) via ME84 separately for JIT-schedules and FRC-schedules.
I use LPH1 as message type for the FRC-schedule and LPJ1 as message type for the JIT-schedule.
The creation of JIT-schedules works fine if I select 'JITSchds Only' in ME84. The result is ONE LPJ1-message with the content of the JIT-schedule.
But I have a problem with the FRC-release, because when I select 'FRC-release Only' in ME84 I get
one LPH1-message and one LPJ1-message as well (both messages have the content of the FRC-release).
But I expect only ONE LPH1-message.
Please advise what I have to do to get only ONE LPH1-message in case of creation of FRC-release.
Thanks a lot
Olga

Hi,
Do check if any changes are carried for your schedule lines as both JIT and FRC was generated.
Do check also the below thread which was discussed for similar query which might help you.
http://scn.sap.com/thread/3352142

Error Message when Scheduling a report in Infoview

I have created a report in Crystal Report using the Universe. Report is saved to the Enterprise and set up to schedule in Infoview.
When the report is scheduled for now or any other "when" time, I receive the error message:
"Error in File C:\Program Files\Business Objects\BusinessObjects Enterprise 11.5\Data\procSched\tfcu-fics.reportjobserver\~tmp58860bbee30730.rpt: Unable to connect: incorrect log on parameters."
Currently running CR Version - 11.5.0313
BOE Version - 11.5
On my workstation - the ODBC connection, System DSN, for crystal is using the Adaptive Server Anywhere 9.00 driver - have no issues creating the report from the Universe.
On the server the ODBC connection, System DSN, for crystal is using the SQL Anywhere 10 driver. Would using the SQL Anywhere 10 driver create the error message above?
To test this I changed the workstation System DSN connection for crystal to SQL Anywhere 10 and when trying to refresh a report created from the Universe I kept receiving the ODBC Login window asking for the database password.
Is there an issue with SQL Anywhere 10 and a Universe not holding the database username or password?

Try This..
1. Open the crystal client on your local machine and import that particular report.
2. Do Database -> Verify Database. Then refresh the report on your PC and make sure that it returns data as expected.
3. Export it back to repository and try scheduling it again. You can verify through CMC for Crystal Reports under " Database Configuration" property to make sure it points to the right ODBC.
Let us know.

Warning Error message while scheduling the Process Chain

Dear All,
I have created the meta Chain, which contains 7 Local Chains. I have tested this chain in BI Development and Quality. It was working fine. I have moved this Meta Chain to production. While i am trying to schedule this chain, i got the warning message.
Too many parallel processes for chosen server BICI
Message no. RSPC118
Diagnosis
On the server TVSBICI you have chosen, there are only 0 batch processes available. The process chain has been designed in such as way that 3 processes must be processed parallel.
System Response
Only 0 processes can be processed parallel. Note also that to be able to start sub-chains, AT LEAST TWO free batch processes must be available. Otherwise a lock situation may arise.
For more information, see SAP Note 621400.
Procedure
Reduce the number of parallel processes in the chain or include sub- chains. This warning applies to all relevant processes.
Procedure for System Administration
Increase the number of batch processes available. You should note however that it makes no sense to set up more batch processes than there are CPUs on server BICI.
Pls help on this issue.
Thanks,
Siva.
Edited by: Siva Kumar on Jun 15, 2009 9:16 AM

I have Ignored this warning and now process Chain is working fine.
Thanks,
Siva.

R/3 to BW (error message when scheduling load)

Hi
I am new to BW and R/3. I have been getting this messsage when scheduling the load (transaction data) from R/3 to BW ODS.
Error when updating Idocs in Source System
Diagnosis
Errors have been reported in Source System during
IDoc update:
System response
There are IDocs with incorrect status.
Procedure
Check the IDocs in Source System . You can get here
using the BW Monitor.
Removing errors:
How you remove the errors depends on the error
message you receive.
Please advise what,how to solve this issue.
thanks

Hi Carlos,
welcome to SDN.
Run RSA1 - Source system - right click on the source system concerned - check connection.
If the source system is inactive, you need to activate or even restore.
For more details, please check:
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a618ae07211d2acb80000e829fbfe/content.htm
Lilly

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,

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

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

Processing messages in Scheduled state

hello all..
my scenarios of FTP to RFC and FTP to IDOCS are all configured but when executing it, the file is "deleted"...(since i keep the status delete)...
but in my sxmb_moni transaction it always shows me scheduled(green flag)...
and the Q-status is stopped..
any suggestions of how to deal with it..??
regards.
vishal

well arpit/sudhir...
i did try the solution provided by arpit..
but still the same error...
everthing was already activeted although i did it again..but the same problem..
infact a colleague of mine in somw other state with similar scenario is getting successfullly processed OCCASSIONALLY and scheduled otherwise...
vishal
Message was edited by: vishal prabhakar

Message Status "Scheduled", Queue Status "Queue Stopped"

Hi friends,
My scenario is from Peoplesoft -> XI -> BI
Message has reached BI, but in SXMB_MONI, its showing Message Status as "Scheduled" and Queue Status "Queue Stopped".
How to proceed further ? How can I start that queue ?
Thanks ain advance,
Neena John

Hi Neena,
Go to SXMB_ADM -> Manage Queues -> Register Queues
More on queues
XI : How to Re-Process failed XI Messages Automatically
Run the report RSXMB_REGISTER_QUEUES and register the queues
Run the report RSXMB_RESTART_MESSAGES for restarting ur messages
Refer this:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/20bb9649-e86e-2910-7aa9-88ed4972a5f6
Regards,
Vinod.

Message in Scheduled

Hello All,
Scenario is JMS to SAP ECC. The message which triggered by JMS appllication is successfully processed by SAP PI and sent to SAP ECC.
But in SAP ECC, the message is in scheduled status(with green flag).
Can you please help me here
Regards,
Moorthy

Hi,
What is your scenerio, if you are using RFC or ABAP proxies then check with the USERID used to push the data into the ECC system. If it is a dialog user then change this to Service user and you are done.
Hope this helps.
Cheers,
Jay

Message in Scheduled stage

Hi Experts,
My scenario is JDBC to Proxie . Some times the message is going into scheduled stage in ECC . Can experts know why its going into scheduled stage in Proxie.
Regards
Santosh

Hi Santosh,
It seems that your messages are getting stuck in the queue.
Check transaction SMQ1 and SMQ2. If there is any message failed overthere then reprocess it or delete it from queue. Then other messages in the queue will get processed.
Below are some link which may help you.
Messages are in schedule state
/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically

Message in scheduled st

Similar Messages

Maybe you are looking for