2016 Mar 30 6:42 PM
I have a program that calls a FM in background task but times out in 30 mins. Is there any way to have this not time out? Or should I use the SUBMIT command?
IN BACKGROUND TASK
Submit
2016 Mar 31 12:44 AM
The better way is to use a submit program. Using Job open FM, submit command and then job close FM. The background task in a function module will be used with a RFC, and the time out is configurable by basis team, but for a general rule the time is not much time.
The better way is to use a submit program. Using Job open FM, submit command and then job close FM. The background task in a function module will be used with a RFC, and the time out is configurable by basis team, but for a general rule the time is not much time.
2016 Mar 30 7:16 PM
According to my understanding you have to find out the root cause of poor performance. You can use ST05 for performance analysis.
2016 Mar 30 8:15 PM
And there is always the option to work in several smaller packages of data to prevent the function module timing out.
2016 Mar 31 12:44 AM
The better way is to use a submit program. Using Job open FM, submit command and then job close FM. The background task in a function module will be used with a RFC, and the time out is configurable by basis team, but for a general rule the time is not much time.
2016 Mar 31 12:35 PM
Create a background job ans use submit, the IN BACKGROUND TASK are executed in interactive process so get the same TIME OUT than transactions.
Regards,
Raymond
| User | Count |
|---|---|
| 3 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |