EXT_SDL_JOB_OUTPUT_GET SAP Function module

EXT_SDL_JOB_OUTPUT_GET is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name EXT_SDL_JOB_OUTPUT_GET into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: SXBP_EXT_SDL
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM EXT_SDL_JOB_OUTPUT_GET - EXT SDL JOB OUTPUT GET

CALL FUNCTION 'EXT_SDL_JOB_OUTPUT_GET' "
  EXPORTING
    session_id =                " btc_ext_sdl_session_id
    jobid =                     " btc_ext_job_id
    doc_id =                    " btc_ext_job_output_id
*   mime_type =                 " btc_ext_doc_mime_type
    continue =                  " boolean
    portion =                   " btc_ext_sdl_int
  IMPORTING
    return =                    " btc_s_return
    output =                    " btc_bindata
    output_mime_type =          " btc_ext_doc_mime_type
    more =                      " boolean
    .  "  EXT_SDL_JOB_OUTPUT_GET

ABAP code example for Function Module EXT_SDL_JOB_OUTPUT_GET

The ABAP code below is a full code listing to execute function module EXT_SDL_JOB_OUTPUT_GET including all data declarations. The code uses the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the original method of declaring data variables up front. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8).

DATA:
ld_return  
 
 TYPE BTC_S_RETURN
,
ld_output  
 
 TYPE BTC_BINDATA
,
ld_output_mime_type  
 
 TYPE BTC_EXT_DOC_MIME_TYPE
,
ld_more  
 
 TYPE BOOLEAN
.


DATA(ld_session_id) = 'Check type of data required'.

DATA(ld_jobid) = 'Check type of data required'.

DATA(ld_doc_id) = 'Check type of data required'.

DATA(ld_mime_type) = 'Check type of data required'.

DATA(ld_continue) = 'Check type of data required'.

DATA(ld_portion) = 'Check type of data required'.
.

CALL FUNCTION 'EXT_SDL_JOB_OUTPUT_GET'
  EXPORTING
    session_id =                 ld_session_id
    jobid =                      ld_jobid
    doc_id =                     ld_doc_id
*   mime_type =                  ld_mime_type
    continue =                   ld_continue
    portion =                    ld_portion
  IMPORTING
    return =                     ld_return
    output =                     ld_output
    output_mime_type =           ld_output_mime_type
    more =                       ld_more
    .  "  EXT_SDL_JOB_OUTPUT_GET

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_return
 
 TYPE BTC_S_RETURN ,
ld_session_id
 
 TYPE BTC_EXT_SDL_SESSION_ID ,
ld_output
 
 TYPE BTC_BINDATA ,
ld_jobid
 
 TYPE BTC_EXT_JOB_ID ,
ld_output_mime_type
 
 TYPE BTC_EXT_DOC_MIME_TYPE ,
ld_doc_id
 
 TYPE BTC_EXT_JOB_OUTPUT_ID ,
ld_more
 
 TYPE BOOLEAN ,
ld_mime_type
 
 TYPE BTC_EXT_DOC_MIME_TYPE ,
ld_continue
 
 TYPE BOOLEAN ,
ld_portion
 
 TYPE BTC_EXT_SDL_INT .


ld_session_id = 'Check type of data required'.
ld_jobid = 'Check type of data required'.
ld_doc_id = 'Check type of data required'.
ld_mime_type = 'Check type of data required'.
ld_continue = 'Check type of data required'.
ld_portion = 'Check type of data required'.