Time limit for a load

[Former Member]

Hi,

I would like to know if someone has faced a problem like the one we do now.

We're required to stop our data loads at a specific time even if they didn't conclude, to be sure that at that time system won't be overloaded.

My question is: is it possible on SAP to establish a time limit for a job that generates its own cancellation? (like, for instance, filling in the setup tables on R/3 LIS extractors).

Any workarounds? Please, consider usual ways of loading on BW (for instance, a process chain, an infopackage...)

Thanks and best regards,

David.

[Former Member · Accepted solution]

Hi David,

Consider if you are loading by using processchains..

So you know the start time of this process chain..So that maintain any ZTABLE ,with the proposed end timings...

Submit your process chain by using ABAP program..Find out the status of the chain at the specified time in ZTABLE for that.If chain is still running stage..Just kill that chain or process..

It is one sort of work around..

Don't forget to assign points ,If it is somewhat useful..

Furture discussions always welcome...

[Former Member · Accepted solution]

Hi,

Thanks for your replies guys, but I need some clarification:

Pradeep: I don't understand "Find out the status of the chain at the specified time". You mean that at the specified time you start an ABAP program that checks the status and then kills the load?

Sounds ok, but loading processes have a problem: it is difficult to know which process belongs to your process chain. I mean, every load is executed by aleremote, so I could kill jobs that don't belong to my chain or loads.

Dinesh: that option only changes load traffic light, am I right? I believe it doesn't stop your load if it is running.

I was looking for something that would make the generated jobs to kill themselves, but I guess that option doesn't exist...

Thanks anyway. Regards,

David.

[Former Member · Accepted solution]

Hi David,

When the extraction process is started from BW, the jobs run on the BW server but it makes an RFC connection to R/3 to get the data.

In Basis there are system profile settings that can be maintained for RFC connections to time-out after a certain time frame. when the 'child' RFC connection is killed by R/3, its upto the parent process , i.e. the job in BW to handle it by changing the status to 'cancelled', which is what we want !

Basis experts in your project can suggest if it is possible to apply these restrictions only to the 'ALEREMOTE' user !

Thats more of an insight than an answer I feel

Cheers, Ashu.

[Former Member]

Hi David,

The default wait time is stored in Transaction RSCUSTV2.

But this is a global setting for all loads.

Perhaps somebody has a better suggestion.

Bye

Dinesh