SAP EXT_SDL_JOB_DETAILS_GET Function Module for









EXT_SDL_JOB_DETAILS_GET is a standard ext sdl job details get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for ext sdl job details get FM, simply by entering the name EXT_SDL_JOB_DETAILS_GET into the relevant SAP transaction such as SE37 or SE38.

Function Group: SXBP_EXT_SDL
Program Name: SAPLSXBP_EXT_SDL
Main Program: SAPLSXBP_EXT_SDL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function EXT_SDL_JOB_DETAILS_GET pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'EXT_SDL_JOB_DETAILS_GET'"
EXPORTING
SESSION_ID = "
JOBID = "

IMPORTING
RETURN = "
START_DATE = "
RUN_DATE = "
CREATION_DATE = "
MODIFICATION_DATE = "
MODIFICATION_USER = "
CREATION_USER = "
RUNTIME = "
RETURN_CODE = "
.



IMPORTING Parameters details for EXT_SDL_JOB_DETAILS_GET

SESSION_ID -

Data type: BTC_EXT_SDL_SESSION_ID
Optional: No
Call by Reference: No ( called with pass by value option)

JOBID -

Data type: BTC_EXT_JOB_ID
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for EXT_SDL_JOB_DETAILS_GET

RETURN -

Data type: BTC_S_RETURN
Optional: No
Call by Reference: No ( called with pass by value option)

START_DATE -

Data type: TIMESTAMP
Optional: No
Call by Reference: No ( called with pass by value option)

RUN_DATE -

Data type: TIMESTAMP
Optional: No
Call by Reference: No ( called with pass by value option)

CREATION_DATE -

Data type: TIMESTAMP
Optional: No
Call by Reference: No ( called with pass by value option)

MODIFICATION_DATE -

Data type: TIMESTAMP
Optional: No
Call by Reference: No ( called with pass by value option)

MODIFICATION_USER -

Data type: BTC_EXT_SDL_USER
Optional: No
Call by Reference: No ( called with pass by value option)

CREATION_USER -

Data type: BTC_EXT_SDL_USER
Optional: No
Call by Reference: No ( called with pass by value option)

RUNTIME -

Data type: BTC_EXT_SDL_INT
Optional: No
Call by Reference: No ( called with pass by value option)

RETURN_CODE -

Data type: BTC_EXT_SDL_INT
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for EXT_SDL_JOB_DETAILS_GET Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

DATA:
lv_return  TYPE BTC_S_RETURN, "   
lv_session_id  TYPE BTC_EXT_SDL_SESSION_ID, "   
lv_jobid  TYPE BTC_EXT_JOB_ID, "   
lv_start_date  TYPE TIMESTAMP, "   
lv_run_date  TYPE TIMESTAMP, "   
lv_creation_date  TYPE TIMESTAMP, "   
lv_modification_date  TYPE TIMESTAMP, "   
lv_modification_user  TYPE BTC_EXT_SDL_USER, "   
lv_creation_user  TYPE BTC_EXT_SDL_USER, "   
lv_runtime  TYPE BTC_EXT_SDL_INT, "   
lv_return_code  TYPE BTC_EXT_SDL_INT. "   

  CALL FUNCTION 'EXT_SDL_JOB_DETAILS_GET'  "
    EXPORTING
         SESSION_ID = lv_session_id
         JOBID = lv_jobid
    IMPORTING
         RETURN = lv_return
         START_DATE = lv_start_date
         RUN_DATE = lv_run_date
         CREATION_DATE = lv_creation_date
         MODIFICATION_DATE = lv_modification_date
         MODIFICATION_USER = lv_modification_user
         CREATION_USER = lv_creation_user
         RUNTIME = lv_runtime
         RETURN_CODE = lv_return_code
. " EXT_SDL_JOB_DETAILS_GET




ABAP code using 7.40 inline data declarations to call FM EXT_SDL_JOB_DETAILS_GET

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
 
 
 
 
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!