Delay into the inbound qRFC queue

Hi:
I am sending a pack of idocs with an xml message through an idoc channel from XI to R/3.
Can I do a delay between the sending of each idoc?
Thanks

Hi,
It is very simple.
If you use BPM,
See first you need to collect IDocs as you mensioned pack of Idocs,this can
be done by the following way
- first import Idoc into IR,
- export the IDoc structure file WSDL and change max occur as 0..unbounded.
- again import into IR under external def
After this collect Idocs and MM,IM target as unbounded msg.
In BPM Use steps
Receive - receive msgs and maitain loop upto satisfying your business requirement condition
maitain the block with foreach mode and put wait step whatever you want to delay
each mesg od IDoc can be send to target by transformation step which will send each record as IDoc sending to target by send step
Try..
Please let me know you got it clear or not.
Regards
Chilla...

Similar Messages

Delay in the Inbound Idoc Posting Process

Dear Friends,
We have an scenario in the Inbound Idoc Posting Process, when we process the Idocs through the standard Inbound Program - RBDAPP01, we face the delay of 3hrs to 12 hrs, approx.
When we try to re-process the same through the manual process, we could successfully post the Idocs, immediately.
When the same happens, through the background job - the delay is happening.
As we see, there is no problem with the program - RBDAPP01, but can't able to trace the delay in the process.
Any suggestions / advises are welcome.
Thanks in advance.

Hi Prasanna,
The update will happen only if a value already exists with the same unit of measure in the system. If the quantity is left blank in the system and if you are trying to update, the update might not happen. Even if the value is Zero in the system, provide the same unit of measure as the data used in the BAPI.
Regards,
Yogesh

Messages getting stuck in QRFC Queue

Hi,
Today I noticed that a message had gotten stuck with the status "Sheduled for Outbound Processing" (scenario IDOC->XI->File), XI 3.0 SP11.
This in turn had the effect that the whole QRFC queue got stuck, and all following messages got stuck with status "Sheduled".
I had to remove the first message from the queue manually so that XI could start to purge the other messages from the queue.
What could be the reason for the first messages getting stuck with this status ("Sheduled for Outbound Processing")?
The message was very small, just a couple of lines. One thing that comes into mind, is that XI received 4 IDOCS for the same interface, within one second. These 4 messages were assigned to different queues, but one of them got stuck. Could there be problems with XI when several messages arrive on the same interface within a very short time?
Is it possible to use Alerts to detect this kind of problem in the future? As I have understood, Alerts only handle XI "errors", but according to XI, this message did not have an "error status", it just had the status "Sheduled for Outbound processing"..
Thanks for any help,
Hans

Hi,
If the message got struck in Queue, you try to activate the queues in smq2 to reprocess the data instead of deleting it. This is the final solution. But you should able to see a dump in ST22 for this problem.
thanks,
sasi

Setting QRFC Queue Status to STOP

Hello
We will be scheduling reports in Prod to auto restart stopped outbound and inbound QRFC queues. But before implementing these changes we need to know if these reports are working fine TEST environemnt. Can anyone recommend us a way of setting the Status of QRFC queues to STOP.
Thanks.
Kiran

Thanks everyone !!
We executed a simple scenario where we selected the Sender SOAP of the type EOIO which enabled us to define a specific queue e.g. TEST_QUEUE. In the Receiver SOAP we entered incorrect usrr id which caused the messages to be blocked in the queues. Once that was done we again reset the password to the correct values and ran our reports to restart QRFC inbound queues which helped us verify the auto restart of queues.
Best Regards,
Kiran

Monitoring the manual recovery queue

Recently we have had a large number of transactions going into the manual recovery queue on our produbion BPEL app server. I have tuend the thread performance and this has helped.
However we would like to setup a notification when we get something in the manaul recovery queue. Is there a way to monitor the manual recovery queue for certain processes, and if so, how?

You could write a BPEL process that wraps a databse adapter that monitors rows in the hydration store, or use Java Embedding and the API;s to monitor the messages ending on the queue. The API guide has some details on how to do this.
Pete

Can't drag files into the queue window on some computers

For some reason, on my new desktop and my laptop. I cannot drag files into the Queue window in Media encoder. I have tried dragging avi's, wav, and mp4. As the files I am dragging hover over the queue window, my mouse turns into the "circle with a line through it" pointer and I cannot add the files that way. I can click the plus sign and then browse to its location to add. I just want to have my drag n drop feature working again... Any ideas why i can on some computers and not others?
I did try running media encoder as administrator. All my computers are running windows 8.1.

do you have source patching turned on for audio?

Messages still stuck in the Inbound queue SMQ2

Hello XI Gurus,
All my messages with "READY" status are still stuck in the inbound queue (smq2) for the last 2 hours...there was no SYSFAIL error messages or scheduled background running. I have to manually go in and executed each of those messages, instead of automatically process it. Could someone please tell me how to troubleshoot this?
Thanks so much in advanced,
Dng

Implement SAP note 758677 for this. This exactly deals with your issue.
This Basically speaks about scheduling 'RSQIWKEX' for inbound and 'RSQOWKEX' for outbound queues.
Also, you need to set the parameter 'QRFC_Restart_ALLOWED' to '1' in the transaction 'SXMB_ADM' -> Integration engine. Its in the runtime dropdown menu.
Note : without this parameter being set this will not work.
Thanks,
Karthik
Edited by: Karthik Rangaraju on Oct 1, 2008 2:13 PM

How do i clear the qRFC queue in a R/3 sandbox

Hi All,
I just built a R/3 4.7B sandbox and we are going to perform an upgrade on it. But before we do that we need to clear the qRFC queue. Can anyone please let me know as to how i go about in clearing the qRFC queue.
Thanks
Anil

Open the infopackage that loads deltas from this infosource.Use option delta and run the infopackage.Do a monitor on this infopackage and check that it has gone GREEN and pulled records.
then go to tcode rsa7 in the source system and highlight the datasource,then click on the 'detail'(lens) button.
In next screen choose radio button delta update and check that it lists 0 records(shows as 0 from 0 records).
Will also probably show 0 LUW's in the delta queue screen beside the datasource tech name.
This confirms that queue is cleared.
cheers,
Vishvesh

Inbound Stuck Queue in the SMQ2

Hi,
One of the Q got stuck in the Inbound of the CRM system.
It is showing the system status as "Running".IT has been in this staus for the past 2 days.
When I try to activate it is giving Message"The queue is registered and therefore cannot be activated"
The Q is giving Dump Error "Exception condition DELETE_ERROR raised
When I chekced the Bdoc SMW01 the BDOC is in "Yellow Status".
How can i process this queue.

Implement SAP note 758677 for this. This exactly deals with your issue.
This Basically speaks about scheduling 'RSQIWKEX' for inbound and 'RSQOWKEX' for outbound queues.
Also, you need to set the parameter 'QRFC_Restart_ALLOWED' to '1' in the transaction 'SXMB_ADM' -> Integration engine. Its in the runtime dropdown menu.
Note : without this parameter being set this will not work.
Thanks,
Karthik
Edited by: Karthik Rangaraju on Oct 1, 2008 2:13 PM

Sending BUPA_MAIN into the RFC queue

Hello,
I would like to send BDoc <b>BUPA_MAIN</b> into the RFC queue
(must be default for Business Partner), for selected BP from my report.
I know how to send bupa_main direct to the site, but it is not the same.
Can anyone help me with this ?
Regards, Robert

Hi Vikash,
thanks for the answer.
Unfortunately this tx has sent BP <b>direct to the site</b> not to the queue.
Flow context (smw01) shows MO4 (mBDoc Direct Send) for Bupa_Main.
And for test I stopped all queues in tx: SMQ2.
And maybe there is a problem with the RFC configuration ?
In transaction after BP is selected new window "SELECT SITE" shows,
and what I can see is one line where :
RFC Destination = NONE
#          = empty
Log.System     = empty
Site Type ID      = CDB
Site ID           = some guid
What do you think ?
Best Regards,
Robert

Wiring constants into the queue in a queued, event driven state machine

I'm creating a queued state machine. Every time I change the queue control options to create a new event I have to recreate a constant in each queued event. Is there a way around this? I'm up to 27 events and changing them all is cumbersome. And I'm sure there are more to folow.

Are you using enums for your constants? If so, make a control from one, right click on it and under "advanced" select "customize" and when in the control editor change the pulldown from "Control" to "Type def." Save it with a useful name, and then in the vi in which you originally created it, use it to create a new constant. You will be able to select the different constant values were you need them and now when you want to add or subtract a "named" value you just click on the closest copy of the type def, either control or diagram constant, and choose customize (or double click into the tool editor if you made that choice in the options in the Tool pulldown at the top of the screen). Any changes you make will automatically be replicated everywhere you have used the typedef, whether a control, indicator or constant. Using enums also allows having case statements that have cases with the same names at the "named" value.
Hope this helps and is what you were refering too.
Putnam Monroe
Certified LabVIEW Developer
Putnam
Certified LabVIEW Developer
Senior Test Engineer
Currently using LV 6.1-LabVIEW 2012, RT8.5
LabVIEW Champion

EWM- serialnumbers posting goods recipt, error in qRFC queue.

Hello
We have a problem and dont know where to look at the moment. The problem is we make a purchaseorder, for a serialized material, we make an inbounddelivery in vl31n where we specify the serialnumbers. This delivery is transferd to SCM system and made into a warehouserequest, which we make into an order and then a task and we confirm the task. Then we can see the serialnumbers in the bin and the availible stock. But R3 is not updated with the GR. In the qRFC queue outbound SCM we get the error message "Document incomplete : You cannot save the delivery"
There is obvious something wrong with how r3 is updated, probably something with the inbound delivery, if we delete the line with the error in the outbound queue the inbound delivery is confirmed with 0. That means that there is created a difference between the warehouse and the IM system.
Does anyone have any suggestions to what we have missed, we are not using HU.
Regards
Ivar

We ended up with using standard WM since EWM seemd at that time not to be a complete stable solution.

Inbound Idocs: Queue Processing (non-stop queue?)

Hi everyone!
I have an issue with a File to Idoc interface. The customer would want the IDocs arriving to R3 to be in the same order they were sent from the legacy. From the File Adapter there isn't any problem using the EOIO QoS, and in the IDoc Receiver Adapter I checked the "Queue Processing".
There is something in the R3 side that the customer doesn't like much and it's about the stop of queue when an IDoc gets in error status: all the subsequent IDocs stay in status 75 ("IDoc received via qRFC").
I can change the status of the wrong IDoc and then release the stopped queue but: Is there a way to process serialized inbound IDocs avoiding the stop of the queue if an error occurs?
I'm using PI 7.0 SP30.
Thank you in advance!

First, this is not serialization, it's the queuing design EOIO... they are not the same.
So, since you activated EOIO in the Sender CC it's normal to have such behave (i.e. 75 status)...
Basically the serialization is not a good fit for these requirements.
Here is one solution:
1- Use dynamic queue name (via UDF) to create more parallelism since I dont think you have to queue all the IDOCs in one single queue.
2- Copy the IDOCs with 75 status to a new IDOCS with 64 (You must have very few)
3- Use RC1_IDOC_SET_STATUS to change the status of the IDOCS from 75 to something 73
4- There is standard report that you have to schedule and restart the queues
5- Reprocess the IDOCs from steps 2
The enemy of EOIO design is the user locks in the target system...
Cheers,
Fouad

Activation of qRFC-Queue inside CRM

Hi! Can anybody tell me, how the qRFC-Queue inside the CRM-System for Delta-Extraction is opened/created so that changes to specified objects are locked? I guess, once the queue would be opened, it would be filled by SMOX-Functions, but can´t find out, how to trigger them to start to work and put data into the Queue. SMOG_TRANS seems to play a role, but I can´t find the proper way. BWA7 e.g. shows, that the extractor is in delta-mode and also shows, that the queue is not open. Tricky thing.

Hi Bernhard!
I am also facing the same problem, can you please post the solution if you are able to solve it.
with regards
ashwin

SXMB_MONI only getting the Inbound Message ( CENTRAL ) not other steps

Hi All,
I am doing a File to proxy scenerios. I am posting the file using file content cnversion. When ever i am checking the scenerios throught tool-->Test
Its working perfectly fine.
But when i am sending the file and checking the SXMB_MONI.
Its only showing the Inbound Message ( CENTRAL ) step. After that its not showing any receiver messages steps. What is the problem? Is there any services not activated? Can you help me on this?
Thanks
Manas

HI Ravi,
i have check the trace lavel this is 1. I have given the trace lavel below.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">Party normalization: sender</Trace>
<Trace level="1" type="T">Sender scheme external = XIParty</Trace>
<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
<Trace level="1" type="T">Sender party external =</Trace>
<Trace level="1" type="T">Sender party normalized =</Trace>
<Trace level="1" type="T">Party normalization: receiver</Trace>
<Trace level="1" type="T">Receiver scheme external =</Trace>
<Trace level="1" type="T">Receiver agency external =</Trace>
<Trace level="1" type="T">Receiver party external =</Trace>
<Trace level="1" type="T">Receiver party normalized =</Trace>
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- 
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = PID</Trace>
<Trace level="1" type="T">client = 100</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PIAFUSER</Trace>
<Trace level="1" type="Timestamp">2008-07-08T11:24:07Z PST</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = 04B466276FDB48713ABDB7E5A31732C5</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="1" type="T">Queue name : XBTI0006</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0006</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</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">- Exit CALL_PIPELINE_ASYNC</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="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface MIOA_MT_GLEmpExp*</Trace>
<Trace level="1" type="T">select interface namespace http://omnicell.com/FIN</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface *</Trace>
<Trace level="1" type="T">select interface namespace</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
</SAP:Trace>

Delay into the inbound qRFC queue

Similar Messages

Maybe you are looking for