SAP FB_SUPPORT_JOB_SCHEDULER Function Module for









FB_SUPPORT_JOB_SCHEDULER is a standard fb support job scheduler 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 fb support job scheduler FM, simply by entering the name FB_SUPPORT_JOB_SCHEDULER into the relevant SAP transaction such as SE37 or SE38.

Function Group: FB_SERVICES
Program Name: SAPLFB_SERVICES
Main Program: SAPLFB_SERVICES
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function FB_SUPPORT_JOB_SCHEDULER 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 'FB_SUPPORT_JOB_SCHEDULER'"
  EXPORTING
   ED_PROGRAM =  "
*  ED_VARIANT =  "
*  ET_RA_YEAR =  "
*  ET_RA_CCODE =  "
*  ET_RA_PERIOD =  "
*  ET_RA_DATE =  "
*  ED_PARALLEL_PROC =  "

EXCEPTIONS
   EXC_PARAMETERS = 1
.



IMPORTING Parameters details for FB_SUPPORT_JOB_SCHEDULER

ED_PROGRAM -

Data type: PROGNAME
Optional: No
Call by Reference: Yes

ED_VARIANT -

Data type: RALDB_VARI
Optional: Yes
Call by Reference: Yes

ET_RA_YEAR -

Data type: RSELOPTION
Optional: Yes
Call by Reference: Yes

ET_RA_CCODE -

Data type: RSELOPTION
Optional: Yes
Call by Reference: Yes

ET_RA_PERIOD -

Data type: RSELOPTION
Optional: Yes
Call by Reference: Yes

ET_RA_DATE -

Data type: RSELOPTION
Optional: Yes
Call by Reference: Yes

ED_PARALLEL_PROC -

Data type: NUMC3
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

EXC_PARAMETERS -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FB_SUPPORT_JOB_SCHEDULER 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_ed_program  TYPE PROGNAME, "   
lv_exc_parameters  TYPE PROGNAME, "   
lv_ed_variant  TYPE RALDB_VARI, "   
lv_et_ra_year  TYPE RSELOPTION, "   
lv_et_ra_ccode  TYPE RSELOPTION, "   
lv_et_ra_period  TYPE RSELOPTION, "   
lv_et_ra_date  TYPE RSELOPTION, "   
lv_ed_parallel_proc  TYPE NUMC3. "   

  CALL FUNCTION 'FB_SUPPORT_JOB_SCHEDULER'  "
    EXPORTING
         ED_PROGRAM = lv_ed_program
         ED_VARIANT = lv_ed_variant
         ET_RA_YEAR = lv_et_ra_year
         ET_RA_CCODE = lv_et_ra_ccode
         ET_RA_PERIOD = lv_et_ra_period
         ET_RA_DATE = lv_et_ra_date
         ED_PARALLEL_PROC = lv_ed_parallel_proc
    EXCEPTIONS
        EXC_PARAMETERS = 1
. " FB_SUPPORT_JOB_SCHEDULER




ABAP code using 7.40 inline data declarations to call FM FB_SUPPORT_JOB_SCHEDULER

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!