Messages in READY state

Hi ,
I have three scenarios from third party to ISU. These are simple file to proxy scenarios.
The problem us whenever I am running the interfaces all the messages going into READY state in ISU what I can track from SMQ2.
Is there any suggestion to solve this .
I have checked multiple blogs for this and tried to run the ready made report of SAP to clear the scheduled message but nothing was helpful .'
Please help.

Hi Apu,
Are the queues registered in ECC SMQR?
Regards,
Mark

Similar Messages

Messages in Ready state are not dequeuing.

Messages are being left in a "Ready" state. Everything was working fine in 10g. However there was an upgrade to 11g and now queues have stop working. It is a multiconsumer queue with one subscriber. I can manually dequeue messages but the subscriber call back does not seem to function.
-- Create and start queues and queue_table
BEGIN
     DBMS_AQADM.CREATE_QUEUE_TABLE (
          queue_table => 'muse.m_en_queue_table',
          queue_payload_type => 'muse.eu_logid_type',
          multiple_consumers => TRUE
     DBMS_AQADM.CREATE_QUEUE (
          queue_name => 'xxxxx.m_en_queue',
          queue_table => 'xxxxx.m_en_queue_table'
     DBMS_AQADM.START_QUEUE('xxxxx.m_en_queue');
     --Start Default Exception Queue
     DBMS_AQADM.START_QUEUE('xxxxx.AQ$_M_EN_QUEUE_TABLE_E', enqueue => FALSE, dequeue => TRUE);
     DBMS_AQADM.ALTER_QUEUE (
          queue_name => 'xxxxx.m_en_queue',
          max_retries => 2,
retry_delay => 10);
END;
--Procedure to dequeue messages and try to resend to the notification service
CREATE OR REPLACE PROCEDURE muse.m_en_queue_callback_procedure(
     context RAW,
reginfo SYS.AQ$_REG_INFO,
descr SYS.AQ$_DESCRIPTOR,
payload RAW,
payloadl NUMBER
) AS
     dequeue_options      dbms_aq.dequeue_options_t;
     message_properties      dbms_aq.message_properties_t;
     message_handle           RAW(16);
     o_payload      muse.eu_logid_type;
     change_rec           muse.eocd_update%rowtype;
BEGIN
dequeue_options.WAIT := DBMS_AQ.no_wait;
dequeue_options.msgid := descr.msg_id;
dequeue_options.consumer_name := descr.consumer_name;
DBMS_AQ.DEQUEUE(
queue_name => descr.queue_name,
dequeue_options => dequeue_options,
message_properties => message_properties,
payload => o_payload,
msgid => message_handle
END;
--Subscribed to queue
BEGIN
DBMS_AQADM.ADD_SUBSCRIBER (
queue_name => 'xxxxx.m_en_queue',
subscriber => SYS.AQ$_AGENT(
'muse_en_queue_subscriber',
NULL,
NULL )
DBMS_AQ.REGISTER (
SYS.AQ$_REG_INFO_LIST(
SYS.AQ$_REG_INFO(
'xxxxx.M_EN_QUEUE:MUSE_EN_QUEUE_SUBSCRIBER',
DBMS_AQ.NAMESPACE_AQ,
'plsql://xxxxx.m_en_queue_callback_procedure',
HEXTORAW('FF')
1
END;
/

Hi,
What version specifically of 11g did you upgrade to?
Did you review the following MOS notes?
Event Monitor Process: Architecture and Known Issues (Doc ID 105067.1)
AQ PL/SQL Notification No Longer Work Due To "register_driver()" Jobs Not Terminating (Doc ID 331372.1)
Thanks
Paul

Messages are in READY state in QUEUE TABLE but in AQ$ QUEUE TABLE messages are in PROCESSED State

HI All,
   We create a brand new oracle multi-consumer queue. We have en-queued the messages into the queue and are processed successfully.
   But when we checked the STATE Column of the messages in the queue table it was showing as "0". But it is showing as "PROCESSED" in the
   AQ$<QUEUE_TABLE> msg_state column.
We are unable to figure out why there is a mismatch. Can any one help us ?
Regards,
Hari P.

Hello,
the column value AQ$<QUEUE_TABLE>.MSG_STATE = 'PROCESSED' corresponds to column value <QUEUE_TABLE>.STATE = 2
(see definition of view AQ$<QUEUE_TABLE for the DECODE statement).
In your case you see a value of STATE = 0 instead of STATE = 2. Is this correct ? The value 0 corresponds to a state "READY" (the delay
is gone and the message is ready for dequeuing).
The AQ documentation says: "After the specified delay, the message is in the READY state and available for dequeuing."
Normally, you cannot see the processed data in your AQ because the enqueued data will be deleted after
successful dequeuing. You wrote that they were processed successfully.
Kind regards,
WoG

Why are messages not dequeuing and stuck in the ready state?

Messages are successfully enqueueing but not dequeuing and are stuck in ready state (STATE = 0). The ENQ_TIME is 5 hours ahead of system time. In one environment, AQ is working (10g 10.2.0.4.0). In the other environment, it is not working (11g 11.2.0.3.0).
I just did the following:
1. Purged queue table
2. Stopped queues
3. Dropped queues
4. Dropped queue table
5. Created queue table
6. Created queues
7. Started queues
I tested once and a record was inserted in the queue table:
MSGID      <msgid>
CORRID
PRIORITY      1
STATE      0
DELAY
EXPIRATION
TIME_MANAGER_INFO
LOCAL_ORDER_NO      0
CHAIN_NO      0
CSCN      0
DSCN      0
ENQ_TIME      12/23/2014 4:33:43.338902 PM
ENQ_UID      <enq_uid>
ENQ_TID      <enq_tid>
DEQ_TIME
DEQ_UID
DEQ_TID
RETRY_COUNT      0
EXCEPTION_QSCHEMA
EXCEPTION_QUEUE
STEP_NO      0
RECIPIENT_KEY      0
DEQUEUE_MSGID
SENDER_NAME
SENDER_ADDRESS
SENDER_PROTOCOL
USER_DATA      <user_data>
USER_PROP
Notice the RETRY_COUNT is 0. The ENQ_TIME is 5 hours ahead. In the procedures to enqueue and dequeue, there are no errors.
Following is the plsql to enqueue:
CREATE OR REPLACE PACKAGE BODY
pkg_2
AS
    FUNCTION queue_create_thing ( <parameters> )
        RETURN NUMBER
    IS
        enqueue_options     dbms_aq.enqueue_options_t;
        message_properties dbms_aq.message_properties_t;
        message_handle      RAW(16);
        v_message           msg_type;
        v_thing_id          things.id%TYPE;
    BEGIN
        v_message := msg_type( <parameters> );
        dbms_aq.enqueue(queue_name => '<queue name>',
                        enqueue_options => enqueue_options,
                        message_properties => message_properties,
                        payload => v_message,
                        msgid => message_handle);
        RETURN v_thing_id;
    EXCEPTION
        WHEN OTHERS
        THEN
           errpkg.record_and_stop (SQLCODE);
    END queue_create_thing;
    PROCEDURE queue_delete_thing( <parameters> )
    IS
        enqueue_options     dbms_aq.enqueue_options_t;
        message_properties dbms_aq.message_properties_t;
        message_handle      RAW(16);
        v_message           msg_type;
    BEGIN
        v_message := msg_type( <parameters> );
        dbms_aq.enqueue(queue_name => '<queue name>',
                        enqueue_options => enqueue_options,
                        message_properties => message_properties,
                        payload => v_message,
                        msgid => message_handle);
    END;
END pkg_2;
Following is the code to dequeue:
CREATE OR REPLACE PACKAGE BODY
pkg_1
AS
    PROCEDURE create_thing ( context IN RAW,
                                reginfo IN sys.aq$_reg_info,
                                descr IN sys.aq$_descriptor,
                                payload IN RAW,
                                payloadl IN NUMBER )
    IS
        dequeue_options dbms_aq.dequeue_options_t;
        message_properties dbms_aq.message_properties_t;
        message_handle RAW(16);
        message msg_type;
    BEGIN
        dequeue_options.msgid := descr.msg_id;
        dequeue_options.consumer_name := descr.consumer_name;
        DBMS_AQ.DEQUEUE(queue_name => descr.queue_name,
                        dequeue_options => dequeue_options,
                        message_properties => message_properties,
                        payload => message,
                        msgid => message_handle);
        pkg_2.create_thing( p_thing_id => message.thing_id );
        UPDATE table t
           SET creation_complete = 1
         WHERE id = message.thing_id;
        COMMIT;
    EXCEPTION
        WHEN OTHERS
        THEN
            ROLLBACK;
            plog.error(SQLERRM);
            plog.full_call_stack;
    END create_thing;
    PROCEDURE delete_thing ( context IN RAW,
                                reginfo IN sys.aq$_reg_info,
                                descr IN sys.aq$_descriptor,
                                payload IN RAW,
                                payloadl IN NUMBER )
    IS
        dequeue_options dbms_aq.dequeue_options_t;
        message_properties dbms_aq.message_properties_t;
        message_handle RAW(16);
        message msg_type;
    BEGIN
        dequeue_options.msgid := descr.msg_id;
        dequeue_options.consumer_name := descr.consumer_name;
        DBMS_AQ.DEQUEUE(queue_name => descr.queue_name,
                        dequeue_options => dequeue_options,
                        message_properties => message_properties,
                        payload => message,
                        msgid => message_handle);
        pkg_2.delete_thing( p_thing_id => message.thing_id );
        COMMIT;
    EXCEPTION
        WHEN OTHERS
        THEN
            ROLLBACK;
            plog.error(SQLERRM);
            plog.full_call_stack;
    END delete_thing;
END pkg_1;

Following is the code to create the queue:
BEGIN
SYS.DBMS_AQADM.STOP_QUEUE ( QUEUE_NAME => '<queue name>');
SYS.DBMS_AQADM.DROP_QUEUE ( QUEUE_NAME => '<queue name>');
END;
BEGIN
SYS.DBMS_AQADM.CREATE_QUEUE
    QUEUE_NAME          =>   '<queue name>'
   ,QUEUE_TABLE         =>   '<queue table>'
   ,QUEUE_TYPE          =>   SYS.DBMS_AQADM.NORMAL_QUEUE
   ,MAX_RETRIES         =>   5
   ,RETRY_DELAY         =>   0
   ,RETENTION_TIME      =>   0
   ,COMMENT             =>   'Queue for processing creation of things'
END;
BEGIN
SYS.DBMS_AQADM.START_QUEUE
    QUEUE_NAME => '<queue name>'
   ,ENQUEUE => TRUE
   ,DEQUEUE => TRUE
END;

UCCE 7.5(8) CAD 7.5.1.59 got blocked in Working Ready state

Hi all,
We're using UCCE 7.5(8) with CAD 7.5.1.59. From time to time, we remarked some CAD get blocked in the Working Ready state after ending a call.
Our wrap up time is currently configured to 2 hours (as requested by client) so the CAD wont turn back to Ready state automatically.
The CAD can be unblocked by an internal call (no UCCE)
Anyone experiences the same problem?
Thanks in advance.
Best regards,

@Geoff:
Thank you for all the good sugesstions, however unfortunately none of them is possible to me
I would try this using the CTIOS client on your test machine, just to eliminate CAD a little. From the trace, it doesn't appear to matter, since you are looking at the pure CTIOS trace messages, and they are the issue - but I like CTIOS for this sort of debugging.
--> We are using CAD and do not have CTIOS client installed. Does the soft actually come with the UCCE installation package? Can you please tell me where I can find it?
@Geoff and Ed
Dissociate and re-associate the device with JTAPI and retest.
--> Good point, I did the same actually but the phone still didn't work.
Nevertheless, I really think we have a network problem (which was observed time to time before)
I will update this thread as soon as I can do some further tests.
Thanks,
Regards,

Agent going to ready state after login

Hi guys,
I have UCCX 5.0(2) and I would like to force agent to go to state ready after login. There were some posts on this topic and they suggested to play with workflow:
1. add add action agent ready at startup - for this I get: "Error on Startup Event. Error Message: An Agent State Action may only be used on Answered and Dropped Events."
2. add macro - record putting agent in ready state (keystroke Ctrl +W). This I can do, but agent gets error during login: " Could not execute Macro Action. Unable to playback to windows program."
Did you have similar problems? Did you solve it and how? Or maybe you have some other idea how to force agent to go in ready state after login?
BR,
Jelena

Hi,
Problem An agent using Windows XP was able to start Agent Desktop, but was
not able to enter an active state.
Solution Windows XP can be configured so that the Internet Connection Firewall
(ICF) is active. ICF acts by keeping track of all traffic to and from the
computer; it will only allow information through that has originated from
that particular computer. If a message originates from outside the
computer, it will be discarded.
To solve this problem, either turn off ICF (requires someone with
administrator rights to the computer) or override the defaults to include
known “good” connections like the CAD servers.
And also, is it by any chance happening during a failover or failback scenario in a High Availability (HA) setup?
If its a HA setup, did you install this CAD after the HA setup is made i.e. the CAD has the entries for the ip address of the both the nodes.
Hope it helps,
Anand

Agent cannot go to ready state after lunch or break without loggin out and back in.

UCCX 8.5
I have a small contact center group. One of the agents I just recently setup is having an issue. She is telling me that when she selects work offline and then goes to lunch or break or something and comes back, it will not let her log back into the ready state. She actually has to log out of Agent and then back in. A screenshot of the error is attached. Any ideas?
Thanks guys.

Hi,
Problem An agent using Windows XP was able to start Agent Desktop, but was
not able to enter an active state.
Solution Windows XP can be configured so that the Internet Connection Firewall
(ICF) is active. ICF acts by keeping track of all traffic to and from the
computer; it will only allow information through that has originated from
that particular computer. If a message originates from outside the
computer, it will be discarded.
To solve this problem, either turn off ICF (requires someone with
administrator rights to the computer) or override the defaults to include
known “good” connections like the CAD servers.
And also, is it by any chance happening during a failover or failback scenario in a High Availability (HA) setup?
If its a HA setup, did you install this CAD after the HA setup is made i.e. the CAD has the entries for the ip address of the both the nodes.
Hope it helps,
Anand

Message in WAIT state after DELAY_TIMESTAMP is in the past

The queue's view DELAY_TIMESTAMP column appears to have the correct time, but when compared to SYSTIMESTAMP, there's an unexpected five hour difference. After the message should have gone to the READY state, it is still in the WAIT state.
For example, a message is enqueued using DBMS_AQ.ENQUEUE with delay of 60 seconds. I wait till well after the message should be dequeued. The message is still in the queue despite attempting to dequeue it with DBMS_AQ.DEQUEUE. Here is what the query looks like.
select delay_timestamp, systimestamp , delay_timestamp - systimestamp
from AQ$THE_QUEUE;
DELAY_TIMESTAMP = 7/1/2009 8:23:05.769546 PM
SYSTIMESTAMP = 7/1/2009 9:06:23.944861 PM +00:00
DELAY_TIMESTAMP-SYSTIMESTAMP +00 04:16:41.824685
The difference should be negative because the time should have expired. However, it's positive, 5 hours less the time since it was enqueued.
This code worked fine until it was re-installed as part of dropping and creating the Oracle user. It works fine on Oracle XE and other Oracle EE databases. The problem is consistent with some change having been done either in Oracle or the Unix operating system. I don't have control over those systems and the administrator says nothing changed. Oracle has been stopped and started since the problem was noticed. The queue table was then dropped and recreated.
Do you have any idea as to what could cause the difference? It looks like a difference between GMT and CDT time zones. It may be related to the session time zone, but when I set my session time zone to +00:00 to match the server, it becomes a one-hour difference instead of a five-hour difference.
It is Oracle 10g 10.2.0.4.0.
Thank you...

Thanks for the reply.
Yes, the five hour difference seems too coincidental. An offset in seconds is supplied to ENQUEUE, not a date, but I suppose AQ could calculate a due date based on the session timezone, but why? I'd think session time zone would be for display purposes. The fact that it's behavior changed without changes to the client environments (both JCBC java clients and PL/SQL clients on different machines) with identical PL/SQL code suggests AQ is responding to some kind of server parameter, either Oracle or Unix. I just don't know what.

When trying to download firefox 3.6.18 which is compatabile with my school I get a 403 message at that states mozilla is forbidden on this server, how do i correct e problem

when trying to download firefox 3.6.18 which is compatabile with my school I get a 403 message at that states mozilla is forbidden on this server, how do i correct the problem

Reload web page(s) and bypass the cache.
* Press and hold Shift and left-click the Reload button.
* Press "Ctrl + F5" or press "Ctrl + Shift + R" (Windows,Linux)
* Press "Cmd + Shift + R" (MAC)
Clear the cache and the cookies from sites that cause problems.
"Clear the Cache":
* Tools > Options > Advanced > Network > Offline Storage (Cache): "Clear Now"
"Remove Cookies" from sites causing problems:
* Tools > Options > Privacy > Cookies: "Show Cookies"

Agents in not ready state too long drops calls.

Using CRS 4.0(3) with agent desktop.
Issue is that when agents go to lunch they go into the not-ready state until they come back from lunch. Upon coming back from lunch, they proceed to go ready and then they start dropping calls as they come into the que.
If you log out completely and close the application when you leave for lunch versus going not ready for an extended period of time the issue does not appear when you log back in.
Any ideas?

Update on this. I looked at the control center and saw that my server was in partial service. I verified the service was the JTAPI subsystem.
I ran the JTAPI update client tool from this link
http://www.cisco.com/en/US/products/sw/custcosw/ps1846/products_tech_note09186a00801c8316.shtml
and saw the version of JTAPI between the CCM and the IPCC server were off. I updated both IPCC servers to the same version of call manager and will now hold to do some testing.

Jobs are in ready state

Hi,
Kernel Release-701
OS-Linux
Patch level-117
dev_disp
ERROR => DpWPCheck: W55 (pid 7299) died (severity=0, status=11) [dpxxdisp.c   15884]
child (pid=7299) killed with signal 11
ERROR => DpWPCheck: W56 (pid 7523) died (severity=0, status=11) [dpxxdisp.c   15884]
child (pid=7523) killed with signal 11
ERROR => DpWPCheck: W57 (pid 23473) died (severity=0, status=11) [dpxxdisp.c   15884]
child (pid=23473) killed with signal 11
ERROR => DpWPCheck: W58 (pid 7526) died (severity=0, status=11) [dpxxdisp.c   15884]
child (pid=7526) killed with signal 11
ERROR => DpWPCheck: W60 (pid 7528) died (severity=0, status=11) [dpxxdisp.c   15884]
child (pid=7528) killed with signal 11
SM21 logs
08:00:05 BTC 055 000 SAPSYS                  EC F Failed to create log for job /
08:00:05 BTC 055 000 SAPSYS                  EA Y Failed to read status entry for job
08:00:05 BTC 055 000 SAPSYS                  EB C > Job
08:00:05 BTC 055 000 SAPSYS                  F2 0 Calling program reports invalid handle for TemSe object (magic==X'NULL-ptr')
08:00:05 BTC 057 000 SAPSYS                  EC F Failed to create log for job /
08:00:05 BTC 057 000 SAPSYS                  EA Y Failed to read status entry for job
08:00:05 BTC 057 000 SAPSYS                  EB C > Job
08:00:05 BTC 057 000 SAPSYS                  F2 0 Calling program reports invalid handle for TemSe object (magic==X'NULL-ptr')
08:00:06 BTC 060 000 SAPSYS                  EC F Failed to create log for job /
08:00:06 BTC 060 000 SAPSYS                  EA Y Failed to read status entry for job
08:00:06 BTC 060 000 SAPSYS                  EB C > Job
08:00:06 BTC 060 000 SAPSYS                  F2 0 Calling program reports invalid handle for TemSe object (magic==X'NULL-ptr')
08:00:06 BTC 056 000 SAPSYS                  EC F Failed to create log for job /
08:00:06 BTC 056 000 SAPSYS                  EA Y Failed to read status entry for job
08:00:06 BTC 056 000 SAPSYS                  EB C > Job
08:00:06 BTC 056 000 SAPSYS                  F2 0 Calling program reports invalid handle for TemSe object (magic==X'NULL-ptr')
08:00:06 BTC 058 000 SAPSYS                  EC F Failed to create log for job /
08:00:06 BTC 058 000 SAPSYS                  EA Y Failed to read status entry for job
Some jobs are going in ready state
If i check them then job execute successfully.

Hi,
As per my personnel experience, there are lot of errors in kernel support pack 117 of 701 release. Try to use patch level 111 which is good.
Also, run TEMSE consistency check to check any inconsistency.
Thanks
Sunny

Cancel and keep workitem in ready state in user decision step

Hi,
In a user decision step,there is a default option 'Cancel and keep the work item'.
Now clicking on this option, the workitem goes into "Inprogress state"
whereas i want to keep the workitem in "ready state" after i click on the option 'Cancel and keep the work item'.
I am trying to modify the Process method of Decision Object type to incorporate this funcationality by using FM "SAP_WAPI_PUT_BACK_WORKITEM.
but im getting the error that this FM cannot be used at runtime.
Place where im trying to call this FM:
After the FM'SWU_PROCESS_MANUEL_DECISION'
I am getting the value of RESULT.
If result is SPACE or sy-subrc is not 00 then i am calling this Fm which takes Wi_id of the userdecision as input.
Kindly help
Regards

Hi,
Let me ask you this. Why you need to have this in "Ready" state, Not in "IN PROCESS" state. Anyway, the witem is still there in the user's inbox, and if you have any deadline monitoring, then this is also taken care with "Cancel and keep xxxx". So, i think, functionally you'll still be better with the existing functionality.
And, with all this, if you are still trying to change, then i think it's NOT possible. If i understand correctly, you are trying to use the FM "SAP_WAPI_PUT_BACK_WORKITEM" within the PROCESS method. And, if you understood the functionality of how this works, you are trying to set the status of the SAME witem for which you are executing the PROCESS method.
THe way i understand the behind-the-scenes process, once you make a decision and save, this method is the one which in turn sets the witem status. And within that, you CANNOT capture the status as it is yet to be posted to the Witem tables.
Probably, after this decision step, use a different background task with the above FM to set the witem status to "Ready", BUT NOT IN THE SAME METHOD of PROCESS.
Also, it's not advisable to change this std. method.
Hope this helps you. Reply,if you need more info.
venu

Send Mail step in ready state

Hello Experts,
I am a workflow novice, just starting out.
I have copied the standard PO release workflow - WS20000075 and inserted a send mail step before activity "Release of purchase order". This was because I would like to send the PO as a PDF attachment to the approver.
The send mail step works fine (i have custom object and method to attach and send mail), it sends out the mail with the attachment correctly, but the work item is in "ready state" and needs to be manually "completed" for the workflow to proceed. After this, the workflow proceeds perfectly.
The send mail is marked as a background task and synchronous object method.
What do i need to do for the "Release of purchase order" to happen as soon as the email has been sent out?
Thanks a lot for the help.
Regards,
Parag.

Hello Ravi,
Thanks for the prompt reply, there are no erros in the workflow log.
SWU3 was definitely done, standard PO Release workflow works fine and so do other ones. Its just that I copied the standard and inserted a new step.
Do I somehow need to "terminate" the send mail step for the workflow to move over to the next activity ?
Regards,
Parag.

Transaction/Report to process background work items which r in READY state

HI,
Can somebody kindly tell me the transaction/report program to process background work items which are in ready state. SM59 configuration was missing and hence, workflows failed to execute after being started successfully. Now, I want to comeplete these operations.
Thanks a lot,
Max

Hi Max,
Did you check transaction SWPC? If the workflows are in there you can start them through in a proper way.
Regards,
Martin

Solaris 8 branded zone not booting after server reboot hangs at ready state

Hi,
For ipchange/hostname change we rebooted the physical server...once rebooting the Solaris brand 8 zone stucks at ready state.
I have run the truss with zoneadm in the log process sleep and wait
Will post the log soon..any help to troubleshoot the issue
Both global zone and Ng zone having same hostid..
dmesg::
Apr 30 13:08:50 xyz zoneadmd[992]: [ID 702911 daemon.error] [zone 'abc'] WARNING: console /devices//pseudo/zconsnex@1/zcons@0 found, but it could not be removed.: I/O error
bash-3.00# ps -ef|grep -i abc
root 1441 1429 0 13:10:56 ? 0:00 /bin/ksh -p /usr/lib/brand/solaris8/s8_boot abc /abc
root 1429 1 0 13:10:55 ? 0:00 zoneadmd -z abc
root 1427 1397 0 13:10:54 pts/3 0:00 zoneadm -z abc boot -f -s
root 1542 1441 0 13:10:56 ? 0:00 /bin/ksh -p /usr/lib/brand/solaris8/s8_boot abc /abc
zoneadm list -cv
2 abc ready /abc solaris8 shared
Thanks
Edited by: muvvas on Apr 30, 2012 2:25 PM

moved the solaris 8 branded zone to other server.their its working fine.sorry for late reply.

Messages in READY state

Similar Messages

Maybe you are looking for