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

Similar Messages

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 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)

Background Processing? how schedule job for "System Error" Message .

Hello everyone,
in sap help i have read.
http://help.sap.com/saphelp_nw04/helpdata/en/5a/f72040599a8f5ce10000000a155106/frameset.htm
PCK> Monitoring>Message Monitoring-->Background Processing
you can schedule jobs for various background processing:
●     Archiving of messages processed successfully
●     Deletion of messages that are not to be archived
●     Restarting of messages with errors
●     Rescheduling of lost messages
can anyone understand this docu?
give me some introduction, how can i define and schedule these jobs ?
thx in advance!!
best regards
Yaning

Background Processing
Prerequisites
You have started the message monitor on the initial screen of the PCK and are in Background Processing.
Features
Archiving
You require two archiving sessions to archive messages:
●     One session to write the messages to the archive
●     One session to delete the persisted messages that have been archived
To do this, you schedule an archiving job, which implicitly schedules the sessions to write to the archive and delete the archived messages.
You can define one or more rules for each archiving job; these rules contain conditions that a message must meet in order to be archived by the job. At least one of the defined rules must be met for archiving to take place.
All information that is displayed for a message in message monitoring is archived, in addition to the audit log for each message.
Deleting
A standard delete job is created automatically. It runs once a day. You can schedule additional delete jobs; however, you cannot define rules for them.
Restarting
Instead of restarting messages with errors manually with message monitoring, you can schedule a job to automatically restart these messages. This is possible for all messages for which the number of defined restart attempts has been exceeded (messages with the system error status).
You can define one or more rules for each job to restart messages; these rules contain conditions that a message must meet in order to be restarted by the job. At least one of the defined rules must be met for archiving to take place.
Rescheduling
A standard job to reschedule messages is created automatically. The job runs once a day and ensures that messages lost as a result of database failure, for example, are rescheduled. You can schedule additional rescheduling jobs; however, you cannot define rules for them.
Thx Aamir.
But I mean the messages with errors in Adapter Engine , not in Intergrations Engine.
the situation is like Naveen Pandrangi's WebLog
II. Errors in Adapter Engine [XI : How to Re-Process failed XI Messages Automatically|XI : How to Re-Process failed XI Messages Automatically]
I
Till now we have seen how to resubmit/restart message that failed in Integration Engine. One a message makes it from Integration Engine to Adapter Engine, the message is flagged as checked in Integration Engine. The status of the message in Adapter engine does not effect the processed state in Integration Engine. Now if this message was asynchronous, XI will by default try to restart the message 3 times at intervals of 5 minutes before the status of the message is changed from Waiting to System Error .
*how can i schedule a job to automatically restart these messages with errors?
best regards
Yaning
Edited by: Yaning Liu on Aug 18, 2008 1:43 PM

Messages are in schedule state in adapter engine

Hi PI Gurus,
In Production system, I have a proxy to JDBC scenario (Using AAE).
From ECC messages are flowing successfully, but when I check the WRB I found no message.
When I checked the Message Monitoring I found, those messages were in schedule state. No logs are also maintained.
Any idea, what is the reason.
This scenerio is working fine in QA and Dev.
Thanks,
Krishna

Hi krishna
Monitor your JDBC communication channel in CC monitoring , if you found any error in CC , then take an action accordingly.
if CC status was gree then check JDBC Adapter Service in NetWeaver Administrator and stop and start it
otherwise can you please check the status of message in sxi_monitor and also check if it is stuck in smq2? Let us know what error you getting in sxmb_moni or the flag of message. As suggested above, check the status of communication channel of JDBC adapter and what errors you getting there if any.
check this link;/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
Edited by: haribabu.karasala on Jul 13, 2011 8:03 AM
Regards
Hari
Edited by: haribabu.karasala on Jul 13, 2011 8:04 AM

Messages are in Scheduled State

Hi
some of my messages are in scheduled state. i verified SMQ1,SMQ2 . no queues are in block state. also i executed register queues in sxmb-adm still they are same state. how can i make them as successful state. only by restarting the messages or is there any other way? also tell me why these messages went to scheduled state

Reddy,
Can you please check this threads for possible solutions:
Problem with scheduled message in SXMB_MONI
SXMB_MONI - Message scheduled on outbound side (no queues)
Regards,
---Satish

[VERY URGENT]Messages going in Scheduled State

Hi Experts,
PROD ISSUE
All of sudden in PROD scenario all the messages start moving to Scheduled state in message monitoring and the channels have stopped polling . I have checked the dispatcher status in engine status (additional data tab) and find that the maximum thread count is 1.
Is that the issue? also any idea y this issue is happening and what can be checked and done in this case ?
URGENT HELP NEEDED !!!
Thanks in Advance

Hi,
You should check your Inbound or Outbound queue in SMQ1 & SMQ2. The messages are stuck there.
Double click on message & read the error details & resolve the same.
Check SM58 also for problem.
Also Register & Activate (re-asctivate) your queues in SXMB_ADM --> Manage Queue --> Register Queue & Activate Queue.
If the messages are stuck in queue, First resolve the error in Queue & check the messages.
Go through this Link
http://www.****************/Tutorials/XI/XMLMessageQueues/Monitor.htm
Hope this help
Regards
Praveen Reddy

Exception Message 30 "Plan process according to schedule"

Dears ,
In exception Message 30 "Plan process according to schedule "
What is the action should be taken by MRP Controller
Regards
Rami

The meaning of EM 30 is as below
30: Plan process according to schedule
i.e.For one of the following reasons, the (non-firmed) order proposal could not be planned on time:
- On the basis of backward scheduling, the system calculated a start date in the past. The system automatically switched to forward scheduling and planned the order proposal in the future using the in-house production time or the delivery time
- On the basis of the planning time fence and a fixing type, the order proposals are moved to the finish date of the planning time fence. With this logic, order proposals must be correctly planned manually.
The date displayed is the date on which the receipt is to be available for materials planning. This contains the goods receipt processing time. If this is not equal to zero, the necessary goods receipt date is also displayed for information purposes.
Hence the exception is displayed in the MRP list along with the rescheduling date.Hence MRP controller need to manullay reschedule the order as per the rescheduling date given in the rescheduling column in MRP list in MD05. If you cannot reschedule practically, then you need to talk to the concern so that requirement date can be postponed to match the rescheduled dates.
Example requirement date - 30.08.2008 for 100 qty
after running MRP the planned order date given is 25.09.2008
against which system will show maessage 30 with reschdule date as 30.08.2008 as it is required on 30.08.2008.
Now how system behavious is as below
the planned delivery days for this item is say 30 days.
Hence from 30.08.2008 system does backward scheduling and reaches today i.e. 24.08.2008 and then go for forward scheduling to give the date as 24.08.2008+30 cal days i.e 25.09.2008 and displyes the EM as 30 with rescheduling date as 30.08.2008. Hence it is upto MRP controller whether he will convince purchase dept to get the material with in 30.08.2008 or ask the production people to wait till 25.09.2008.
I hope you understood, if not com beack.

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

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

OM: CLEARING THE PROCESS MESSAGES TABLES

제품 : MFG_OM
작성날짜 : 2004-10-11
OM: CLEARING THE PROCESS MESSAGES TABLES
==========================================
PURPOSE
OM 모듈을 어느 기간 사용하다 보면 process messages table -
OE_PROCESSING_MSGS_TL/OE_PROCESSING_MSGS - 에 많은 data가 쌓여 있는것을
확인할 수 있다.
이 tables의 size를 줄임으로써 system performance 향상도 기대할 수 있다.
Explanation
OE_PROCESSING_MSGS_TL table은 Order Entry concurreny problem이 실행되거
나 User interface process가 실행될때 발생하는 processing messages를
저장하는 table이다.
아래의 3가지 방법중 하나를 이용하여 process messagea tables
- OE_PROCESSING_MSGS_TL/OE_PROCESSING_MSGS -의 정보를 delete 할 수 있다.
1.SQL을 이용하여 table을 truncate
(OE_PROCESSING_MSGS_TL를 먼저 truncate 시켜야 함을 주의)
경고: 만약 truncate 방법을 선택했다면, 위 두 tables에 있는 모든 정보를
잃게 될 것이다.
2.OM application의 Process Messages form을 이용.
Delete 될 messages는 사용자의 query에 따른다.
Process Messages form에서 delete 하고자 하는 messages range를 설정하여
조회한 후, 그 query된 messages만 delete 할 수 있다.
1) Navigation: Orders, Returns>Process Messages
2) Messages source를 선택
3) Query를 원하는 Messages Request ID range를 입력
4) Query를 원하는 Messages의 Order Number range를 입력
5) Query를 원하는 Messages의 Request Date range를 입력
6) Query를 원하는 Messages의 Program Name을 선택
7) 특정한 Workflow Activity를 가지고 있는 Workflow Activity를 선택
WF activity는 Order의 actual stage를 참조한다.
8) Query를 원하는 Message의 Order Type을 선택
9) Attribute를 선택, Default는 null
10) Customer Name or Number를 선택
11) Requester를 선택
12) Find button을 선택
Process Messages window displays.
13) Query된 모든 messages를 delete 하기 위새 'Delete All' button을
click.
3.SQL을 이용하여 특정 일자전의 모든 process messages를 delete.
(OE_PROCESSING_MSGS_TL 의 data를 먼저 delete 함을 명심!!)
위 1번의 truncate option을 이용하면, SQL statement는 어떤 messages를
delete하는지 전혀 식별할 수가 없다.
만약 특정 process에 관련된 messages만을 delete하길 원하면 아래의
truncate option 2를 이용한다.
아래는 sample script이며, creation date를 근간으로 delete한다.
만약 오늘 날짜(dd-mon-yy)를 입력하면 script는 7일전의 messages만을
delete 할 것이다.
====================================================
DECLARE
l_date DATE := to_date('&delete_date');
BEGIN
Delete from oe_processing_msgs_tl
Where creation_date <= l_date - 7;
Delete from oe_processing_msgs
Where creation_date <= l_date - 7;
Exception
WHEN Others THEN
Null;
END;
After executing this script commit and exit from sqlplus.
=======================================================
Note: 꼭 기억해야 할 것은 'Delete/Truncate' 작업시 'OE_PROCESSING_MSGS'
data를 delete 전에 꼭 'OE_PROCESSING_MSGS_TL' data를 먼저 delete
해야 한다는 것이다.
Example
Reference Documents
Note 123150.1

You can include PSA's in process chain and schedule deletion periodically.
You can include process type 'Deletion of Requests from PSA / Deletion of Requests from the Change Log ' in process chain . After EHP1 upgrade you can define pattern like 2lis* or 0* it will delete all the PSA's starting with 2lis or 0 data source .
Ravi

What is process through which schedule lines are cofirmed in Sales Order

What is the process through which schedule lines are cofirmed in Sales Order

Hi,
Schedule lines get confirmed on the basis of backward or forward scheduling carried out by system based on Material Availability date.
Regards
SD
Message was edited by:
Samier Danish

How to keep waiting time between processed messages !!

Hi Folks,
I have got one scenario required waiting time between processed messages. The problem as follows !!
File --> Proxy scenario. I receive 15 messages from sender side (same messages structure) so working with one interfaces. File picking and transforming this message and split into 2 messages. messages are receiving to receiver. I am using BPM with 7,8 steps like receiving step, block , message transformation step , internal block 1 for sender 1, internal block 2 for sender 2.
All things are working fine, messages are going to receiver properly. But customer requirement is , wait step required between processed messages before sender1. I have put wait step still, PI picks all messages in one shot processing and waiting for 2 minutes, after 2 minutes sending all messages at the same time, this process is not working.
I have tried with wait step in mapping (Sarvesh) given excellent idea, still PI works the same way.
Can someone please explain a bit why the messages or not waiting message by message. I am using EOIO with Queue name and file process mode "BY NAME" and I have tried "BY TIME" as well. I have given priority to this Queue. On BPM Queue assignment : One Queue.
Please I am expecting positive answer !!
Many Thanks in Advance
San

Hi Rudolf Yaskorski ,
Not sure about your PI release and BPM model, do you create separate process instance for each file, or do you process files collecting them in one single instance? Are you using parallelization within your ccBPM ?
I am using serialization, I don't think bpm can do Parallization until PI 7.0, but PI 7.11 has got has queue assignment. But I am using one queue. This must be serialization.
To me it looks like your issue is not in ccBPM but rather more in polling files (as per your post file CC polls all 15 files in one shot). So if you wish to poll the files not at the same time some workaround is required. Possible options you could check out:
A. Either implement "wait" in your mapping based on file name or other criteria (e.g. directory name). Check out if respective BPM instances are really created at different times.
I have used wait step in mapping. These 15 messages has to go through one interface. So I am using one interface. But I have checked mapping process time in all messages on receiver system. Shows same timing, even though I put 40000 ms waiting time in mapping.
B. Try polling different files (or use different directories) with different channels and coordinate starting / stopping of your channels by scheduling availability for each CC in RWB. E.g. you poll file 1 with CC 1. You start 2 minutes later CC 2 and poll file 2. And so on.
I am not clear about this . On BPM waiting step is working and it keeps wait all messages, which are coming through one interface. Then it releases all messages at the same time.
I don't know how to resolve this. I have tried with Transport acknowledgment, but all messages are going to reciver system waiting at receiver system in priority queue and processing in EOIO, but taking so long. Rather all messages go and sits in queue, I want to stop messages by message with 2 minutes time gap. How please?
Kind Regards
San

Sending Process Message from PI Sheets without "Completing" it

Hi,
We have long running process orders in our scenarios (typically lasting 3 days).
We are planning to use PI sheets to manage our goods issue/receipts/confirmations. During the brief evaluation of characteristics based PI sheets, we found that all the GI/GR process messages are created only when the entire PI sheet is "Completed".
Since ours is a long running process, we need that the GI/GR entered by the operator is posted immediately in the system (without waiting for PI sheet completion). We can not wait till all the data is entered and the process order is completed three days later.
How do we handle this problem?
We thought of using custom function modules. However, that will mean that we will loose the benefits of the standard GUI elements of PI sheets and complications of custom development.
Any response will be highly appreciated.
Regards,
Kundan

Here is something you can try.
With the browser based sheets, try putting in a signature PI category (SAP provide "SIGN") which tends to create a message and place it in the message monitor. By scheduling the message send background job to run periodically you can pick up and send the messages. You can schedule this job to run after the event "NEW MESSAGE" but beware the system performance - every 5 mins or so tends to be almost as good with less strain on system resources!
I tend to create a table based PI category to contain each reservation plus room to add actual goods issues/receipts. Once these are entered, a signature category sends all the messages for the particular phase. Thus good structure of phases is important.
For goods receipts, you may need to have a phase for each day against which to post a confirmation and/or goods receipt and this together with signature will send the messages. Alternately, use a PI Category to call the transaction for performing goods receipt - or a bespoke transaction to "front end" the goods receipt - you can pass parameters when you call transactions so you can could pre-populate some information.
Final point on signature - you can set a simple signature that just accepts whatever the user enters on the screen - typically their initials.
Regards
Laurence

Processing messages in Scheduled state

Similar Messages

Maybe you are looking for