CIF Queue gettign stuck in 'ready' state

Hi,
I am facing a problem in using CIF functionality while transferrting Master data and transaction data from R/3 to APO.
I have selected inbound queue processing for APO system and have also registered the queue in APO.
But when I actually CIF any data, it gets stuck in the outbound queue of the R/3 system in 'Ready' state.
Then I always need to manually activate the queue in SMQ1 to transfer the data to APO.
The same thing happens during online transfer of transaction data.
I want the data to be transferred automatically rather tahn activating the CIF queue each time.
Please help.
Thanks,
Ameet

Hi Ameet
Please following setting.
1. User setting
-R/3 T-CD CFC2 (For debuf Area, please check whether your user has "R" or not)
-APO T-CD /SAPAPO/C4 (For debug, please check whether your user has "R : debug on" or not)
2. Queue scheduler setting in both system
Inbound scheduler
T-CD SMQR please make sure whether you have inbound scheduler setting.
If there is not, you can create it by hitting Registration button.
"Registration" => Queue Name CF*, and lest of it can be leave as default.
Outbound scheduler
T-CD SMQS
Please make sure you have entry to your SCM system.
Type should be "R". If it is not R, outbound scheduler is not activated.
So please select entry and and hit registration button again. Then type will change
to "R".
I hope this help your problem.
Keiji Mishima

Similar Messages

Risk Analysis Batch Job Stuck in Ready State

Hi,
I am not able to schedule Risk Analysis Batch job in RAR.The job is getting stuck on READY state(for unlimited period) and not performing any actions.
Nothing is displayed under job history or job logs with job ID.I have check background job demaon ,connectors and other miscell. options but not abl to find any clue.
Even i am executing risk analysis for single user,it's not happening.
Rgds,
Mukesh

For your problem, of job not getting schedule....it seems Deamon is not running.
To delete status of job which are in hung status
change VIRSA_CC_SCHEDULER job id should with status five will show job aborted.
are you using connection type 'Adaptive RFC', don't use it, use SAP JCO.
and restart your GRC box.
Regards,
Surpreet
please do check backend system, for VIRSANH is installed or not.
Edited by: Surpreet Singh Bal on Jan 28, 2011 10:32 AM

CIF Ques Stuck in READY State on R3 Inbound for no Reason

Hi,
Question pertains to CIF Processing and Ques waiting in READY State from R3 to SCM-APO for no Apparent Reason.
Our Orders (PRs, STOs) generated via APO are being sent to R3 correctly, getting generated in R/3 but not coming back with the PR/STO Number back to APO. Stuck in R3 inbound.
I've read a couple of articles on SDN on this.
Apart from the Standard CIF Configuration, and Settings in SMQR and SMQS (Qin & Qout Scheduler) for retrying Stuck Ques to be processed, is there anything else that can be looked at ? Any Consulting Notes on this Topic ?
SCM-APO version 4.0 on latest Support Pack.
R3 4.6c and Plugin compatible. Not on most latest SP.
Thanks,
Ambrish Mathur

Hai,
Yes our Problem is resolved now. The Solution was Technical in Nature and not functional (as you can logically expect).
Assuming your Basis Team has properly setup the QIN and QOUT Scheduler on BOTH sides (APO and R3) ...
Also in QIN and QOUT the Time to RETRY a Que is set to something low as every 5 minutes and retry 10 times.
(However this was not the main issue for us).
We found in our Case since the R3's Support Pack and Plug-In were not upgraded due to many depandancies to other Projects ... we found that the QRFC Versions on the R3 side were a few sub versions behind the APO QRFC Version since APO was on Latest Support Pack on SCM 4.
The BASIS Group downloaded and Installed the Latest QRFC version and the Problem was subsequently resolved.
QRFC Version can be found in Transaction SMQ1 / SMQ2 -> Menu Path Information -> Version.
We are now at QRFC ver. 6.30.060, Supplement # 11.
Hope you find this usefull and it resolves your issue. Do revert back if it does.
Regards,
Ambrish Mathur

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;

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.

Many CIF queues in READY status

Hello Experts,
We have currently 30,000 CIF queues in our production system in READY status and those are stuck since long.I tried program RSQOWKEX to process queues.Its working for one queue at a time but not many at one shot if i give CIF*.
Please please suggest.
BR,
Nisha

Nisha,
I will assume you are talking about outbound queues. Sounds like the schedular.is not running, or else you may have a communication or resource problem.
If your queue(s) are unregistered, you can register them using SMQS. Look for a missing destination, or a destination with a 'U' (unregistered) in the first column. Also, it can't hurt to 'Activate'. Don't be alarmed if in a few moments the status reverts to 'inactive', this just means that the scheduler is temporarily idle, and has decided that it has nothing to do. More info at
http://help.sap.com/saphelp_scm70/helpdata/EN/4c/cf5c3c3b067331e10000000a114084/frameset.htm
You can mass process 'Ready' queues in APO using /SAPAPO/CQ. Deselect 'only blocked' select Expand Node, enter all the possible source/destination systems, execute. In the resulting list, look for anything other than the green check, double click. The list of 'ready' queues will appear on the right. Select all, hit the activate Icon (matchstick). Wait. 30K queues may take a day, depending on the content.
Best Regards,
DB49

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

CIF Queues lie with ready or sunning status.

Hi Experts,
We are experiencing that CIF queus are lieing in ready or running status for some of the order types - not all.
We use inbound setting. Inbound to SCM sales orders and deliveries lieing like this. And inbound to ECC production orders are lieing like this.
What could be the reason?
Thanks and regards,
Sushant

Hi Sushant,
Please check the following,
1) Orders are maintianed in distribution definition in APO
2) Queues are maintained for reprocessing in SMQR both in ECC and APO
regards,
biplab

Queues in READY State

Dear Friends,
This is regarding the queues in DOE being in READY state for a long time.
When we trigger delta download, we see some queues in READY state for a long time ( > 2 minutes ).
Example :
DOEBWA_00G_007_0_13FL.
We have executed the transaction sdoe_activate_q in the middleware for all the queue name ( sdoe* , mmw* , et al).
Are we missing something?
Thanks in Advance.
Suresh BJ

I don't know about this report, but the place to check for your problem is the transaction SMQR.
1. If the queues are clearing up after some time, then its not a problem of registration. So you should see your corresponding queue patterns 'R'egistered here.
2. Look at the 'Scheduler Status'. Is it 'Waiting'? If yes, then it means your scheduler (the guy who distributes queue entries to dialog work processes for processing) is waiting for a work process to get free. => Then the problem is with having too few dialog work processes.
Cheers

Queue goes into 'READY' state

Hi All,
I'm using the 'TRFC_SET_QIN_PROPERTIES' function module with the qin_name parameter.
The problem I'm facing is that, most of the times, my function module entry goes into the queue - but the queue is in 'READY' state. I have to manually go to SMQ2 and make a change to put the queue into 'RUNNING' state.
Is there a way to automatically set the queue to 'RUNNNING' state when i insert an entry into the queue? Or, is there a seperate API that can do this task for me?
Regards,
Ram

Hello Jeff, the agents on an active call will not count for the Not Ready state. When receiving the call (ringing) they will be placed in Reserved state; while the call is connected they will be in Talking state and after the call ends they could be placed in Work state for a while.
HTH
Pablo

Ucce cad agent stuck in reserved state

Dears,
It is a UCCE system with CVP and CAD version 9.0
The issue is that when the call is to be delivered to an agent, the CAD is stuck in the reserved state for around 20 seconds then it goes to the Ready state and the caller gets disconnected since I'm not configuring a queue yet.
Has someone faced a similar issue?
Your help is greatly appreciated.
Thank you in advance.
Lara

Actually it turned out to be a call manager issue. The partition of the agent's extension was misconfigured.
Regards.

Issue - CIF queue for activation of IM requiring manual activation.

Hi,
For inbound setting, the CIF queue for activation of IM is getting stuck with ready status. Consequently the background job getting failed with time limit exceed status.
The same queue when activated manually, gets cleared. Thus requirng manual intevetion.
Please suggest solution to get rid of this manual intervention.
Thanks and regards,
Sushant

Hi Sushant,
If you use inbound queues check QIN scheduler on SCM side - transaction SMQR.
From help:
Call transaction SMQR and choose Registration.
Enter the queue name CF* and make the required settings.
EXEMODE: Execution mode (D - Dialog work process; B - Batch work process)
MAXTIME: Maximum runtime that the QIN scheduler uses for activating a destination;
default value: 60 seconds
USERDEST: RFC destination with LOGON data. Specification of a logical destination
with its own language on the local
system. This means that the burden of integration can be distributed to a server group.
NRETRY: Number of repetitions for failed calls, default value: 30
RDELAY: Wait time between individual calls, default value: 300
Regards,
Alexander

UCCx 8 Callback when agent is in Ready State

To all,
I am stuck. Here is the basic logic for my callback caller script when agent is in Ready state. After the Get Digit String step, what should I do to terminate the call and keep the script running?
Select Resource (--Triggering Contct--from CSQ)
          Connected
          Queued
               Menu
                    CallbackNumber = Get Digit String (--Triggering Contact--)
                              succesful
                                   If(stat_ReadyResources_OF_CSQ > 0) then
                                            True
                                               outcallToCaller = Place Call (to callbackNumber)
                                                      successful
                                                             Call Redirect (--Triggering Contact--to Overflow Q)
* OverflowQ is another script.
Thanks,
Nelson

Set the contact as still being active, even though no one is there. You will not be able to play any prompts or anything to that contact though, that will result in errors, unless you catch the error. You can of course redirect playback to the contact that you call.
ErrorReason = Get Trigger Info (Aborting Reason)
On Exception (ContactInactiveException) Goto Begin
Delay 2 sec
Accept(--Triggering Contact--)
Delay 4 sec     <---Hang up before these 4 seconds are done.
Begin:
Clear Exception (ContactInactiveException)
Set Contact Info (--Triggering Contact--)
     Language: strLanguage (I have a Language varible named this with the value L[en_US] )
     Handled:
     Session: strSession (I have a Session varible named this with the value null )
I edited this to add the delay and accept steps, so you would know the proper order for them to be in. I have a script that calls customers and asks if it is ok to fax them documents to that line in the next 5 minutes. So they know to let the call go to their fax.

When the agent is in ready state, call has to go to voice mail incase the call is not answered

I need to create a script for helpdesk setup. When call hits the CSQ, if agents are free the call will get connect to an agent, else it will be queued. Till here i am clear. The step where i have stuck is , when the agent is in ready state and when the call gets connect to that agent, due to some reasons if agent, do not answer the call, it has to get transfer to voice mail . Can someone help me with this please... We are using UCCX 8.5...

Not sure the logic that Anthony used in some of the prior solutions but try following Logic in the ScreenShot and let me know how it works out for you..
As Jeff mentioned (and I overlooked) If there is a Ring No Answer and there is another Agent Ready then the first Step in the Failed Output Branch will not Evaluate..the Script Logic takes the "caller" back to the Select RSRC Step..so I'm doing an IF check to ensure that wasn't the case..and if it was then I will Dequeue the call and perform the necessary transfer..(after the Successful Transfer you probably should Goto a Terminate Step)..Cheers

Billing Document queues are stuck in CRM Outbound

Hi All,
In our system there are huge number of CSA_BEACRMB_BD* Queues generating in CRM Outbound (SMQ1) and getting into "Ready" state with RFC destination as "NONE". These queues are of no use. Please guide me how to stop generating this Queues. FM used for this queues is /1BEA/CRMB_BD_MWC_O_VALIDATE.
Regards,
Das

Hello,
I would check the customizing in SPRO. It seems that your System is customized to distribute billing numbers.
My guess is
Customer Relationship Management
Billing
Country-Specific Functions
Official Document Numbering
Transfer Official Document Numbers to Accounting Documents
Check whether there is an entry somewhere there forcing the System to behave the way it does.
Lutz

CIF Queue gettign stuck in 'ready' state

Similar Messages

Maybe you are looking for