SAP SCCM_SCHEDULE_BATCH_JOB Function Module for
SCCM_SCHEDULE_BATCH_JOB is a standard sccm schedule batch job 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 sccm schedule batch job FM, simply by entering the name SCCM_SCHEDULE_BATCH_JOB into the relevant SAP transaction such as SE37 or SE38.
Function Group: SCCM
Program Name: SAPLSCCM
Main Program: SAPLSCCM
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function SCCM_SCHEDULE_BATCH_JOB 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 'SCCM_SCHEDULE_BATCH_JOB'".
EXPORTING
PROFILE = "Client copy profiles
BATCH_FLAG = "Program running in background
CCMODUS = "Mode for client transport
CCSUPCOPY = "Test run without database update
CCCOMFILE = "Request/Task
CCRESTART = "Client Copy: Restart Mode
PROF_PARM = "Source entries for profiles
PROCESS = "Process number
CCCFLOW_CURR = "Client Copy Control Flow
NR_PROCESSES = "Internal tables, current number of lines
TABLES
START_PROC = "
IMPORTING Parameters details for SCCM_SCHEDULE_BATCH_JOB
PROFILE - Client copy profiles
Data type: CCPROFOptional: No
Call by Reference: No ( called with pass by value option)
BATCH_FLAG - Program running in background
Data type: SY-BATCHOptional: No
Call by Reference: No ( called with pass by value option)
CCMODUS - Mode for client transport
Data type: STRMPAR-CCMODUSOptional: No
Call by Reference: No ( called with pass by value option)
CCSUPCOPY - Test run without database update
Data type: STRMPAR-CCTESTRUNOptional: No
Call by Reference: No ( called with pass by value option)
CCCOMFILE - Request/Task
Data type: E070-TRKORROptional: No
Call by Reference: No ( called with pass by value option)
CCRESTART - Client Copy: Restart Mode
Data type: STRMPAR-CCRESTARTOptional: No
Call by Reference: No ( called with pass by value option)
PROF_PARM - Source entries for profiles
Data type: CCPROFSROptional: No
Call by Reference: No ( called with pass by value option)
PROCESS - Process number
Data type: CCPROCTAB-PROCESSOptional: No
Call by Reference: No ( called with pass by value option)
CCCFLOW_CURR - Client Copy Control Flow
Data type: CCCFLOWOptional: No
Call by Reference: No ( called with pass by value option)
NR_PROCESSES - Internal tables, current number of lines
Data type: SY-TFILLOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SCCM_SCHEDULE_BATCH_JOB
START_PROC -
Data type: CCPROCTABOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SCCM_SCHEDULE_BATCH_JOB 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_profile | TYPE CCPROF, " | |||
lt_start_proc | TYPE STANDARD TABLE OF CCPROCTAB, " | |||
lv_batch_flag | TYPE SY-BATCH, " | |||
lv_ccmodus | TYPE STRMPAR-CCMODUS, " | |||
lv_ccsupcopy | TYPE STRMPAR-CCTESTRUN, " | |||
lv_cccomfile | TYPE E070-TRKORR, " | |||
lv_ccrestart | TYPE STRMPAR-CCRESTART, " | |||
lv_prof_parm | TYPE CCPROFSR, " | |||
lv_process | TYPE CCPROCTAB-PROCESS, " | |||
lv_cccflow_curr | TYPE CCCFLOW, " | |||
lv_nr_processes | TYPE SY-TFILL. " |
  CALL FUNCTION 'SCCM_SCHEDULE_BATCH_JOB' " |
EXPORTING | ||
PROFILE | = lv_profile | |
BATCH_FLAG | = lv_batch_flag | |
CCMODUS | = lv_ccmodus | |
CCSUPCOPY | = lv_ccsupcopy | |
CCCOMFILE | = lv_cccomfile | |
CCRESTART | = lv_ccrestart | |
PROF_PARM | = lv_prof_parm | |
PROCESS | = lv_process | |
CCCFLOW_CURR | = lv_cccflow_curr | |
NR_PROCESSES | = lv_nr_processes | |
TABLES | ||
START_PROC | = lt_start_proc | |
. " SCCM_SCHEDULE_BATCH_JOB |
ABAP code using 7.40 inline data declarations to call FM SCCM_SCHEDULE_BATCH_JOB
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."SELECT single BATCH FROM SY INTO @DATA(ld_batch_flag). | ||||
"SELECT single CCMODUS FROM STRMPAR INTO @DATA(ld_ccmodus). | ||||
"SELECT single CCTESTRUN FROM STRMPAR INTO @DATA(ld_ccsupcopy). | ||||
"SELECT single TRKORR FROM E070 INTO @DATA(ld_cccomfile). | ||||
"SELECT single CCRESTART FROM STRMPAR INTO @DATA(ld_ccrestart). | ||||
"SELECT single PROCESS FROM CCPROCTAB INTO @DATA(ld_process). | ||||
"SELECT single TFILL FROM SY INTO @DATA(ld_nr_processes). | ||||
Search for further information about these or an SAP related objects