on 07-23-2008 6:46 PM
We have quite a few interfaces that use an inbound proxy, but we're running into a problem we haven't seen before.
We have an inbound interface that requires quite a bit of processing time, and it is now timing out.
Is there any way to force the proxy to use a background process, instead of a dialog process, to avoid the dialog process time out?
I had always assumed that these proxies used background processes, and just discovered today this isn't the case.
You can do something like this.
This is more of a ABAP solution.
write the actual code in a separate report program and call that program in background mode.
submit <report> in background...
Regards,
Ravi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
you can do like this:
CALL FUNCTION 'JOB_OPEN'
EXPORTING
JOBNAME = JOB_NAME "Some name
IMPORTING
JOBCOUNT = JOB_NR
EXCEPTIONS
CANT_CREATE_JOB = 1
INVALID_JOB_DATA = 2
JOBNAME_MISSING = 3
OTHERS = 4.
IF SY-SUBRC NE 0.
MESSAGE I162(00) WITH
'An error occured while creating the background job.'.
STOP.
ENDIF.
EXPORT itab
TO MEMORY ID 'table'.
SUBMIT <Report name> USER SY-UNAME
VIA JOB JOB_NAME NUMBER JOB_NR
AND RETURN.
*Inside the report program import the internal table using the code:*
*IMPORT itab TO jtab FROM MEMORY ID 'table'.*
*close the job...
CALL FUNCTION 'JOB_CLOSE'
EXPORTING
JOBCOUNT = JOB_NR
JOBNAME = JOB_NAME
STRTIMMED = 'X'
IMPORTING
JOB_WAS_RELEASED = JOB_RELEASED
EXCEPTIONS
CANT_START_IMMEDIATE = 1
INVALID_STARTDATE = 2
JOBNAME_MISSING = 3
JOB_CLOSE_FAILED = 4
JOB_NOSTEPS = 5
JOB_NOTEX = 6
LOCK_FAILED = 7
OTHERS = 8.
IF SY-SUBRC <> 0.
MESSAGE I162(00) WITH
'An error occured while closing the background job.'.
STOP.
ENDIF.
User | Count |
---|---|
83 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.