Delay the outbound queue

[Former Member]

Hello Sap Experts ,

I am working on queue RFC and my requirement is to delay the outbound queue for specific time and date .is there is any function module which i can used for this requirement.

I want to delay the outbound queue .

Kindly revert of share some view points or suggestions for this issue.

Thanks,

Varun Walia

Cont :+91-7838651000

[Former Member]

Hi Ryan ,

This is also i communicate to business but the requirement is to delay tor schedulele the queue rfc at outbound level for date and time ..and then again need to execute for the date and time ..

let's see we initiate the data through rfc interface and client on friday and client required to pass the data to other system on monday as we have the large amount of interfaces and memory issue at server level and business want to transfer the data when the system doesn't have load on it .

In that case , we need to delay the outbound queue for particular date and time.

is this would be possible by through ABAP level to achieve this goal ?

Thanks for the reply !

Varun

[paul_bakker2]

One way to do it is using workflow (you can pass the date / time to it and use conditions or deadline handling to trigger the update).

But maybe it's not really required. Can you give more details on what you are trying to  do - for instance, why the update has to be delayed? What's the business scenario?

[Former Member]

Hello Paul ,

Thanks for the reply .I have the requirement that I'm sending the data from one sap system to other sap system by though the queue RFC.

I used the custom program which calls the 'BAPI_USER_CREATE' or create the user to other system by through Queue RFC.Now when i executed the program the data is sent to outbound

Queue and after few seconds it goes to inbound queue and we can see the data is there once we execute or process the data at other system .once the queue is executed in transaction code smq2 at other sap system then the user is created and updated successfully.

Now my requirement is when i send the data to outbound queue in same system in which my custom program is , need to schedule  the data or to send the data to other system by particular time and date .

Now I need the delay at the outbound queue exist for the transaction code smq1.

Please confirm if we can manage this by through sap standard function module to delay the data for particular time and date.

Thanks,

Varun Walia

[paul_bakker2]

What's the business reason for the update to be delayed?

[Former Member]

Hi Paul ,

The Business required scheduling the interfaces as we have hundreds of interfaces exist for the system and we want to send the data to other systems by though queue RFC and the business required to check which  are the interfaces at the outbound in the primary system in transaction code SMQ1   and those interfaces should schedule and send as per required when needed at particular time and date.

Thanks,

[Jelena_Perfiljeva]

I feel you are trying to reinvent the wheel since the user data exchange is possible in standard SAP by using IDocs. Better yet, use SolMan and central user management.

In any case, we can't really "schedule" RFC transmission, AFAIK scheduling is only possible for the background jobs. Talk to your Basis admin.

[Former Member]

Hi Jelena ,

Thanks for the Reply ..I know that we can schedule or send the data by though idocs and we can delay by this .Even we have batch job in system where we can schedule the standard program or any interface.But my requirement is we need to use delay or schedule by through queue RFC not by idocs or by batch jobs.

Now going further , just need to know or is this possible if i can schedule the queue by through ABAP level not by Basis administration.

let me know if anything required from my side,

Thanks

Varun Walia

[former_member202771]

Hi Varun,

wait statement might help. But not preferred to run the execution for such a long time.

Thanks,

Anil

[Former Member]

Hi Anil ,

Thanks for the reply !

Right , we can use the wait statement in ABAP i.e for either 5 seconds for more than that .But we need the delay or to schedule at particular time and date.

Thanks,

[Ryan-Crosby]

Hi Varun,

Why would the business care whether it is IDoc or qRFC or background job to achieve the requirement of communication at a specific date and time?  Those are technical tools at your disposal to achieve the goal - the only thing they should be concerned with is if you can make the communication happen from end to end such that the necessary data is posted to the system.

Regards,

Ryan Crosby

[Former Member]

Hi Ryan ,

This is also i communicate to business but the requirement is to delay tor schedulele the queue rfc at outbound level for date and time ..and then again need to execute for the date and time ..

let's see we initiate the data through rfc interface and client on friday and client required to pass the data to other system on monday as we have the large amount of interfaces and memory issue at server level and business want to transfer the data when the system doesn't have load on it .

In that case , we need to delay the outbound queue for particular date and time.

is this would be possible by through ABAP level to achieve this goal ?

Thanks for the reply !

Varun

[Jelena_Perfiljeva]

the requirement is to delay tor schedulele the queue rfc at outbound level for date and time

Do they also have a requirement to draw 5 red lines but some of them in green ink and some in transparent? As already mentioned, there is no way to schedule an RFC transmission ("schedule" is not exactly the same as "delay", you might want to stick with just one to avoid confusion). But it's kind of a no-brainer that probably you can schedule the execution of whatever program is triggering RFC. That's about the only option imaginable.

To be honest, based on your description, I feel this customer has a lot more serious problem. If they have such performance issues then either the system was not sized correctly to begin with or there is a technical problem that they really should resolve or they simply shot themselves in the foot by dictating such poorly thought through "requirements" like this one.

Instead of spending time on this interface I'd suggest to them to address performance first. And then look into implementing standard interface.

Sorry, but I can't participate in this travesty anymore, so that's the best advice I can offer.