Blocked queue

The queue in my deskjet 1660 continually clogs. I have uninstalled and reinstalled the latest updates, followed dirctions to clear the print spooler, used the diagnostic untility to fix the problem but nothing works. Can anyone help????

Hi Torsten Engel,
In your post, you have explained as "after executing, the corresponding queue is blocked".
Lets do this way.
Goto session maneger -> SXMB_ADM
At Integration Engine [administration] select the manage queues.
In Action tab select the "Activate Queues" and execute action.
You can view all the queues at the monitor.
Hope this may solve your problem.
Cheers,
Vinod V
*Reward me, if found useful.

Similar Messages

Best way to implement a shared Blocking Queue?

What's the best way to implement a shared Blocking Queue that multiple JVMs can enqueue objects in and multiple JVM's can dequeue from simultaneously?
Also, I see references on the web to com.tangosol.coherence.component.util.queue.ConcurrentQueue but I don't see it in the current API docs...
Thanks

Hi snidely_whiplash,
snidely_whiplash wrote:
What's the best way to implement a shared Blocking Queue that multiple JVMs can enqueue objects in and multiple JVM's can dequeue from simultaneously?
Also, I see references on the web to com.tangosol.coherence.component.util.queue.ConcurrentQueue but I don't see it in the current API docs...
ThanksThat class is an internal class, AFAIK.
As for implementing a queue, you might want to look at Ashish Srivastava's ezMQ component for some ideas:
http://ezsaid.blogspot.com/2009/01/implementing-jms-queue-on-top-of-oracle.html
Best regards,
Robert

Out of order when put /take packages in/from a blocking queue

Hello all:
I put multiple packages in a blocking queue in one thread, and take them out from another thread. The in sequence is 1-2-3, the out sequence becomes 3-2-1. This is NOT a FILO pattern, there is no pattern: it could be 3-1-2, etc.
The question is: can out-of-order issue even take place when put()/take() operations impose on a blocking queue? If it's not possible, which I believe, I'll look elsewhere for the cause. Otherwise, why and how to fix it.
Thanks,
John

Please provide an [url http://sscce.org]SSCCE that demonstrates this.
Unless you're using a PriorityQueue or some other specialized implementation, it should be a FIFO order. Check the docs for the implementation you're using.
Edited by: jverd on Nov 22, 2011 4:41 PM

Publishing PReq to R3 gets location_not_found error in blocked queue

Hi,
While trying to publish Purchase Req to R3 i get a <location_not_found> error in the blocked queue.
I have checked my settings including forms of address, publication, integration models but it still happens!
When i try to create the PR within R3 it works fine.
Maybe i am missing something.
Would appreciate any assistance.
Thanks,
CY

I have the masterdata in APO as the PR is created in APO with a valid source of supply which is a purchase info record from R3.
As for messages, i checked all the queues in apo and r3 and the appl log but still the only msg was location_not_found!
I can even create the PR in R3 if i don't plan it in apo which means the r3 data is also ok!
Thanks for the reply.

Blocking queue

Hi there,
I have a project to develop blocking queue for poolthread application.
basically, there are 4 parameters :
1. number_thread initiated
2. max_thread in the pool
3. min_thread in the pool
4. idle_time for inactive thread so i could destroy it after certain interval time.
i have found how to create blocking queue, now for the min thread and idle time : any one have a suggestion ?
should i put counter in blocking queue ..?
sorry i'm confused in java thread programming
any information i'll be appreciated
cheers
reve

Thanks fuchssa for the reply
In fact, i had to create blocking queue and the thread pool. But since the programs are already existe, i just have to add some parameters which are : min active thread in the pool and idle time for idle thread.
So, that's why i'm confused since those are not my programs and i thought that there are certain ways to put the parameter (wether in the blocking or in the pool). I think most likely that i should just add it in the constructor threadpool.
How about if we put the in the blocking queue? is it possible?
here are the code :
import java.util.*;
import java.lang.*;
import BlockingQueue;
public class ThreadPool
private BlockingQueue file;
MyThread[] tab;
int taille ;
int nbThreads;
public ThreadPool(int nbTh, int t)
taille=t;
nbThreads=nbTh;
file = new BlockingQueue();
createThreads();
void createThreads()
tab = new MyThread[taille];
for( int i = 0; i < nbThreads; i++)
tab[i] = new MyThread(file);
tab.start();
public void execute(Runnable th ) throws BlockingQueue.ClosedException
file.enqueue( th);
if ((file.size()>0 ) && (nbThreads<taille)) {
nbThreads++;
tab[nbThreads-1] = new MyThread(file);
tab[nbThreads-1].start();
class MyThread extends Thread // inner class my thread
private BlockingQueue file ;
public MyThread(BlockingQueue q)
file = q;
public void run()
while(true)
try
((Runnable)file.dequeue()).run();
catch(BlockingQueue.ClosedException e)
catch(InterruptedException es)

Time-Out for Process with Correlation - Avoiding blocked Queues

Hello,
I have the following requirement, it would be great if you could share your opinions and knowledge on it:
If have an integration process which opens a correlation and sends out an asynchronous request message. The response normally arrives after 10 minutes and is correlated to the process using a correlationID that has been activated by the request message. Additionally there is a deadline branch which terminates the process after 1 hour.
So far this works fine.
However there might be some very rare cases where a response is delayed (e.g. if there is maintenace work on partner side). So it could be the case that a response arrives a day later when the process instance is already terminated:
My questions are now:
1. How can I avoid that the inbound queue is blocked with the response message that cannot find an active correlation?
2. Best thing would be to store the response message on the file system in case no more active correlations are open.
So basically the logic could be:
If message arrives, check whether process instance with corresponding correlation is active, if yes then send to process, if no send to file receiver.
Is this possible?

Thread closed - no solution so far.

Queuing - Action Blocks (Queue Get, Queue Put , Queue List, Queue Delete)

Does any one know how to use Queue Get, Queue Put, Queue List, Queue Delete
action blocks?
There is neither any help documentation nor any previous queries in the forum for this.
Thanks and Regards
Khaleel Badeghar

Hi Khaleelurrehman,
1. Put something in your Queue:
   Name: MyQueue
   ID:      4711
   Example:
   - Make a ForNextLoop and use the Link Editor to fill the Queue with 10 entries.
   - Use a Local XML Variable as Message and a Assignment to set the
     Message text. So your Message will be:
     "a Message with the ID " & For_Next_Loop_0.CurrentItem
   - Put the Message and the ID in your Queue using the Link Editor
     ID: 4700 + For_Next_Loop_0.CurrentItem
2. Replace something in your Queue:
   Just refere to Queue-Name and Queue-ID to replace a Message with the
   Queue-Put-Action.
3. Get one entry of your Queue:
   Just refere to Queue-Name and Queue-ID to get the Message out of the Queue
   with the Queue-Get-Action.
4. Get a List of entries from your Queue:
   - Use the Queue-List-Action which will return a xMII-XML Structure with
     DATE and ID.
   - Use a Repeater to loop over the Output of Queue-List-Action.
   - Use a Queue-Get-Action and assign the ID of the Repeater-Output to get the
     Message for the ID.
5. Delete one Message in your Queue:
   Use the Queue-Delete-Action to delete a Message with a specific ID from
   your Queue.
6. Delete the whole Queue (or all Messages)
   Use Queue-List-Action + Repeater to loop + Queue-Delete-Action
Hope this helps.
Ciao
Martin

Notification for the Blocked Queues

Hi,
My environment is PI 7.0 and in my monitoring transaction (SXMB_MONI) getting the messages has Scheduled for Outbound Processing (The Icon is like (>) ).
I checked my SMQ2 of my XI/PI system and I can see some of the messages got blocked in the Queue. The Queue message is XBT0*******. Manually unlocked the messages and activated my Queues and refreshed the queue cleared in couple of mins.
The problem was caused by the PI**USER got locked and unlocked the user few days back.
I want to know is their any possible way to get a notification for the Scheduled for Outbound Processing messages (>).
Other then Scheduled for Outbound Processing (>) messages we can get the notifications. We can get for notification for the Red Flag, Green Flag, and White Flag). What about the Scheduled for Outbound Processing messages (>) Flag????
Give your ideas to monitor this kind of errors by notification.
Thanks,
GM.

Hi, GM:
This can be achieved by setting CCMS alert to monitor the status of the queue, please check the link:
http://help.sap.com/saphelp_nw70/helpdata/en/f0/02a63b9bb3e035e10000000a114084/frameset.htm
Also check the How-To guide:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/0b4580be-0601-0010-d3ad-bd6ce51ae916
Liang

Blocking Queues

When playing with the new BlockingQueues (ArrayBlockingQueue, LinkedBlockingQueue) I was stumped by the abysmal performance they offered. Later I discovered that a simple optimization improved the execution time of said toy program by roughly one order of magnitude: Explicitly transferring the control to another thread by calling Thread.yield():
if (q.size() == max)
    Thread.yield();
q.put(...);
if (q.size() == 0)
   Thread.yield();
q.take(...);instead of q.put(...) and q.take(). I am surprised that this isn't the default behavior of put and take, since the threads will block under these circumstances anyway.
Am I missing something obvious, or is this a bug in the implementation?

For what it's worth, here's the code of a simplified version. Half a second for threading 100000 ints is still a long time...
import java.util.concurrent.ArrayBlockingQueue;
import java.util.concurrent.BlockingQueue;
class Queues {
public static void main(String[] args) throws InterruptedException {
    final int max = 64;
    final BlockingQueue<Integer> q = new ArrayBlockingQueue<Integer>(max);
    new Thread() {
      public void run() {
        try {
          for (int i = 100000; i >= 0; --i) {
            if (q.size() == max)
              Thread.yield();
            q.put(i);
        } catch (Exception e) {                                                                                 System.err.println(e);
    }.start();
    int sum = 0;
    int last = 1;
    while (last != 0) {
      if (q.size() == 0)
        Thread.yield();
      last = q.take();
      sum += last;
    System.out.println(sum);
}

SMQ2 Inbound Blocked Queues Due to UoM.

Dear Experts,
We sustain a number of materials in ECC with order unit TN (Tonnes) and are really causing issues because as the particular supplier delivers in KG's.
I.e....
•We order 0.100 TN (100kgs) of a Metal Sheet from a supplier
•They deliver us 100.123kgs
•Stock is receipted in EWM as 100.123kgs
•PO in ECC only allows 3 decimal places with Unit of Measure TN, so we can only have the PO as 0.100 TN, not 0.100123 that it should be...
•Receipt of the stock from EWM to ECC is then stuck in a queue because of this issue
•Stock cannot get booked in from EWM to ECC
•Stock cannot be backflushed when consumed in production
We need to raise PO's need in KGs. Contracts have been set up in Tonnes and will not allow us to select KGs as a UOM in the PO.
What best practices do you recommend here please?
ADP.

Hello Andriko,
It is always recommended to have same Unit of Measurement both in ECC and EWM.
Can you try maintaining Conversion in your Material master and try reprocess the queue in ECC.
Regards,
Sathish

Losing unprocessed records when blocking queue entries are serialized

Hi,
I am developing a batch framework using the Java 1.5 thread APIs. We have a requirement to save the state of the batch processes when it terminates abnormally or when it is killed for any reason. I have implemented this functionality using shutdown hooks.
I have initialized the thread pool with two thread instances. Now, while things are behaving as expected, I am losing upto 2 records when I kill the batch process. These are those 2 records which were being processed by the threadpool threads when the kill signal was sent.
Is there a mechanism to prevent the batch job from exiting before these two threads have processed finishing or maybe keep these 2 threadpool tasks in the pool till they have completed gracefully. I.e. remove these tasks from the threadpool task queue when have they have finished execution
Regards,
Hitesh

ExecutorService.shutdown()
ExecutorService.awaitTermination()
One would expect the jobs that are currently executing to have been already removed from the queue.

Queues indound blocked

I wanted to ask what can I check on my XI, because I often block queues indound, blocking the process of my interfaces.
thanks
umberto

Hi,
check in RWB and Message Monitoring for specific interface.
or
check in TCode SMQ2 for Inbound Queue monitoring
http://help.sap.com/saphelp_nw70/helpdata/EN/76/e12041c877f623e10000000a155106/frameset.htm
Queue Status in SMQ1 and Table ARFCRSTATE
Use
Depending on the way a Logical Unit of Work (LUW) is processed, an inbound queue, outbound queue or table ARFCRSTATE (status table of the LUWs in the tRFC/qRFC target system) can have different statuses.
Outbound Queue
The following statuses may be displayed in transaction SMQ1:
READY
·        The queue is ready for transmission. This status should only be a temporary status. However, in the following case this status can also be permanent: A queue has been locked manually via transaction SMQ1 or via a program, and then unlocked without being activated at the same time. This queue must be activated explicitly.
RUNNING
·        The first LUW of this queue is currently being processed. If a queue in this status hangs for more than 30 minutes, this may mean that the work process responsible for sending this LUW has been terminated. In this case you can activate this queue again.
Note that activating a queue in status RUNNING may cause a LUW to be executed several times if this LUW is still being processed in the target system at that time. We therefore recommend a waiting time of at least 30 minutes before you reactivate the queue.
EXECUTED
·        The first LUW of this queue has been processed. The system waits for a qRFC-internal confirmation from the target system before processing further LUWs. If a queue in this status hangs for more than 30 minutes, this may mean that the work process responsible for sending this LUW has been terminated. In contrast to status RUNNING, this current LUW has definitely been executed successfully. You can reactivate this queue without any problems. The qRFC Manager will automatically delete the LUW already executed and send the next LUW.
SYSFAIL
·        A serious error occurred in the target system while the first LUW of this queue was executed. The execution was interrupted. When you double-click on this status, the system displays an error text. For more information on this error, see the corresponding short dump in the target system (ST22). No background job is scheduled for a retry and the queue is no longer processed. To solve the problem, information from the affected application is required. See note 335162 for the special error text "connection closed".
CPICERR
·        During transmission or processing of the first LUW in the target system, a network or communication error occurred. When you double-click on this status, the system displays an error text. For more information on this error, see the syslog (SM21), the trace files dev_rd or dev_rfc*. Depending on the definition in transaction SM59 for the destination used, a batch job is scheduled for subsequent sending. Status CPICERR may also exist in the following cases although no communication error occurred: A qRFC application finds out that a LUW cannot be processed any further due to a temporary error in the application and therefore calls the RESTART_OF_BACKGROUNDTASK function module to prompt the qRFC Manager to cancel the execution of this LUW and to repeat this LUW later in accordance with the specification in transaction SM59. In this case, qRFC simulates a communication error with the text "Command to tRFC/qRFC: Execute LUW once again." If this error occurs very often, you must contact the corresponding application.
STOP
·        On this queue or a generic queue (for example BASIS_*) a lock was set explicitly (SMQ1 or programs). Note that the processing of qRFC never locks a queue. After having informed the corresponding application, you can unlock and activate this queue using transaction SMQ1.
WAITSTOP
·        The first LUW of this queue has dependencies to other queues, and at least one of these queues is currently still locked.
WAITING
·        The first LUW of this queue has dependencies to other queues, and at least one of these queues currently still contains other LUWs with higher priorities.
NOSEND
·        LUWs of this queue are never sent but retrieved by a special application. These queues are only used internally at SAP (BW or CRM during communication with Mobile Clients). Even if a LUW has been read by the corresponding application (BW, CRM), this status does not change. This LUW is only deleted from the queue if this application confirms collection (collective confirmation possible). Under no circumstances should this status be reset using transaction SMQ1 and the queue activated.
NOSENDS
·        During the qRFC call, the application determines at the same time that the current LUW is not sent immediately. This is used to debug the execution of an LUW via transaction SMQ1.
WAITUPDA
·        This status is set if qRFC is called within a transaction that also contains one or more update functions. As a result of this status, the LUW and thus the queue is blocked until the update has been completed successfully. If this status takes longer than a few minutes, check the status of the update or the update requests using transaction SM13. After a successful retroactive update, the blocked LUW is sent automatically. You can reset this status in the qRFC Monitor SMQ1, and reactivate the queue. Note that this can lead to possible inconsistencies in the application data between the two systems.
If you are using Releases 4.0x, 4.5x, 4.6A or 4.6B, and an update function with the "collective run" type exists in a LUW, an error in the kernel may cause this status. The queue also hangs in this case. This error has already been corrected with a kernel patch (see note 333878).
ARETRY
·        During LUW execution the application has diagnosed a temporary problem and has prompted the qRFC Manager in the sending system via a specific qRFC call to schedule a batch job for a repetition based on the definition in transaction SM59.
ANORETRY
·        During the LUW execution, the application has found a serious error and prompted the qRFC Manager via a specific qRFC call to cancel processing of this LUW. Information from the affected application is required to solve the problem. To solve the problem, information from the affected application is required.
MODIFY
·        Processing of this queue is locked temporarily because the LUW data is being modified.
Table ARFCRSTATE
You can use transaction SE16 to display the status:
EXECUTED
·        The related LUW is completely executed in the target system. The system waits for an internal tRFC/qRFC confirmation from the sending system before this entry is deleted.
HOLD
·        The corresponding application has processed this LUW in parts and wants this LUW to not be repeated in the case of subsequent network or communication errors (see SAP Note 366869 if there are many entries with this status).
WCONFIRM
·        During a LUW execution the application has prompted the tRFC/qRFC Manager to set status HOLD. If the LUW execution has already been completed but this application has not yet signaled the logical LUW end and if the tRFC/qRFC-internal confirmation from the sending system has been received, then this LUW receives status WCONFIRM.
If the respective application informs the tRFC/qRFC Manager about the logical LUW end, then this entry is deleted (see also SAP Note 366869 for more details).
Queue Status in SMQ2 and Table ARFCRSTATE
Use
Depending on the way a Logical Unit of Work (LUW) is processed, an inbound queue or the table ARFCRSTATE (status table of the LUWs in the tRFC/qRFC target system) can have different statuses.
Inbound Queue
The following statuses may be displayed in transaction SMQ2:
·        READY
The queue is ready for processing. This status should only be a temporary status. However, in the following case this status can also be permanent: A queue has been locked manually using transaction SMQ2 or using a program, and then unlocked without being activated at the same time. This queue must be activated explicitly.
·        RUNNING
The first LUW of this queue is currently being processed. If a queue in this status hangs for more than 30 minutes, this may mean that the work process responsible for processing this LUW has been terminated. In this case you can activate this queue again. Note that activating a queue in status RUNNING may cause a LUW to be executed several times if this LUW is still being processed in the target system at that time. We therefore recommend a waiting time of at least 30 minutes before you reactivate the queue.
·        SYSFAIL
A serious error occurred while the first LUW of this queue was being executed. The execution was interrupted. When you double-click on this status, the system displays an error text. For more information on this error, see the corresponding short dump in the target system (transaction ST22). No background job is scheduled for a retry and the queue is no longer processed. To solve the problem, information from the affected application is required. See SAP Note 335162 for the error text "connection closed".
·        CPICERR
A network or communication error occurred while the first LUW was being executed. When you double-click on this status, the system displays an error text. For more information on this error, see the syslog (transaction SM21) or the trace files dev_rd and dev_rfc*. Depending on the registration of this queue (SMQR), a background job is scheduled for a retry. See SAP Note 369524 for the error text u201CLogon failed". Status CPICERR may also exist in the following cases although no communication error occurred: A qRFC application finds out that a LUW cannot be processed any further due to a temporary error in the application and therefore calls the RESTART_OF_BACKGROUNDTASK function module to prompt the qRFC Manager to cancel the execution of this LUW and to repeat this LUW later in accordance with the specification in transaction SM59. In this case, qRFC simulates a communication error with the text "Command to tRFC/qRFC: Execute LUW once again." If this error occurs very often, you must contact the corresponding application.
·        STOP
On this queue or a generic queue (for example BASIS_*) a lock was set explicitly (SMQ2 or programs). Note that the processing of qRFC never locks a queue. After having informed the corresponding application, you can unlock this queue using transaction SMQ2.
·        WAITSTOP
The first LUW of this queue has dependencies to other queues, and at least one of these queues is currently still locked.
·        WAITING
The first LUW of this queue has dependencies to other queues, and at least one of these queues currently still contains other LUWs with higher priorities.
·        ARETRY
When the LUW was processed, the application diagnosed a temporary problem and has prompted the qRFC Manager with a specific qRFC call to schedule a background job for a retry, based on the registration in SMQR.
·        ANORETRY
When the LUW was processed, the application diagnosed a serious error and has prompted the qRFC Manager with a specific qRFC call to stop processing this LUW. To solve the problem, information from the affected application is required.
·        MODIFY
Processing of this queue is locked temporarily because the LUW data is being modified.
Table ARFCRSTATE
You can use transaction SE16 to display the status:
·        EXECUTED
The related LUW is completely executed in the target system. The system waits for an internal tRFC/qRFC confirmation from the sending system before this entry is deleted.
·        HOLD
The corresponding application has processed this LUW in parts and wants this LUW to not be repeated in the case of subsequent network or communication errors (see SAP Note 366869 if there are many entries with this status).
·        WCONFIRM
During a LUW execution the application has prompted the tRFC/qRFC Manager to set status HOLD. If the LUW execution has already been completed but this application has not yet signaled the logical LUW end and if the tRFC/qRFC-internal confirmation from the sending system has been received, then this LUW receives status WCONFIRM.
If the respective application informs the tRFC/qRFC Manager about the logical LUW end, then this entry is deleted (see also SAP Note 366869 for more details).
PS reward me if usefull
reg,
suresh

SMQ1 & SMQ2 Alerts: Please help set up Queue blocking alterts

Hi ALL
We have been experiencing problems with Queue Failures / Blocked Queue in PROS.
However, we do NOT get this notification as part of Alerts we have set up in ALRTCATDEF.
Can you please, help us with any links on documentation on how to set up SMQ1 & SMQ2 alerts.So, that we get notified via whenever a queue is blocked.
Your help is greatly appreciated!!
Regards,
Patrick

Hi ,
For runtime errors , you can trigger an alert.
I don't think so, it is possible to trigger an alert when message is stuck in Queue, but if you get any error either system error or application error then you can trigger an alert.
For more-
http://help.sap.com/saphelp_nw2004s/helpdata/en/80/942f3ffed33d67e10000000a114084/frameset.htm
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step
If you have got any errors like communication errors because of Queue error, then you can think of configuring CCMS alerts.(i.e alerts for Components)
/people/aravindh.prasanna/blog/2005/12/23/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part--1
also see:
http://help.sap.com/saphelp_nw04s/helpdata/en/b1/ca6c3c32ac8754e10000000a114084/frameset.htm
Re: Event Queue related- events not geting delivered
Regards

Blocked inbound queue RETRY status

Hi everybody
Sometimes I get this alert in the CCMS-> Transactional RFC and Queued RFC -> Inbound Queues->Int. Server Outbound Messages (XBQ0*)->Blocked queues:
Blocked inbound queue XBQ0$PE_W.... status RETRY...........
I can not get the isssue because it happend when nobody is monitoring the XI system. I want to see what happen at this time but I do not how to do it. When I see the inbound queues in the SMQ2 is empty. Could tell me someboy how to get the issue in a trace or log file?
The system works fine normally but it happens sometimes.
thanks in advanced.

Hi Gerardo Mondragon
this issue is not very strange when some queue has very heavy load then for time being messages are queued in the queue and it throws exception and ccms alert is generated. after some time when the queue gets processed all the messsages you will not find any error
if you find error RETRY status in SMQ2 then right click in the last column and execute LUW
it will get processed and queues will be fine
then in RZ 20 you can complete alert
thanks
Sandeep Shrama
PS; if helpful reward points

Monitoring of remote system's Transactional RFC and Queued RFC

Hello,
In our production system, in rz20- CCMS monitor templates- Communication-Transactional RFC and Queued RFc- outbound queues- Queues otherwise not monitored we can see blocked queues for each client.
System is connected to solution manager and we wish the central auto reaction is implemented in solution manager
However i am unable to find Transactional RFC and Queued RFC for the remote system, they exist only for solution manager itself
Tell me how can i do the central monitoring

Hello,
First you need to check with your Landscape in solman in order to monitor any kind of activities to do so pls follow these steps.
Go to SMSY in solman under Landscape components>Product systemsselect you satellite system example SAP ECC.
On the main screen you will find client for which you have generated RFC connection. Please check though connection are working fine, Go to edit mode and try to click on generate button there will be a pop-up, which gives a clear picture of RFC connection which already exists, and you can also re-generate this RFC connection by clean it up when you re-generate pls select under Actions after generation assign RFC dest for system monitoring.
But make sure there is no project impact on this RFC, like they are not using any logical components and already have some projects running on this RFC connection.
I would advise you to first you the option of assign and check RFC button which is next to generate icon.
Regards
JUDE

Blocked queue

Similar Messages

Maybe you are looking for