SATC_EXECUTE_PROJECT_VIA_BATCH SAP Function module - Project execution: Dispatcher runs within separate BTC process

SATC_EXECUTE_PROJECT_VIA_BATCH 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 SATC_EXECUTE_PROJECT_VIA_BATCH into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: SATC_EXECUTION
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM SATC_EXECUTE_PROJECT_VIA_BATCH - SATC EXECUTE PROJECT VIA BATCH

CALL FUNCTION 'SATC_EXECUTE_PROJECT_VIA_BATCH' "Project execution: Dispatcher runs within separate BTC process
  EXPORTING
    i_project =                 " if_satc_md_project  Meta Data of a Project
*   i_execution_mode = 'R'      " satc_d_execution_mode  Execution Mode (Batch or RFC)
    i_destination_type = 'S'    " satc_d_destination_type  Destination type ( "G"roup, "S"erver )
*   i_server_name = 'NONE'      " satc_d_server_name  Server Name
*   i_server_group =            " satc_d_server_group  Server Group
*   i_nbr_processes = 2         " satc_d_nbr_of_clnt_processes  Number of processes for parallel execution
*   i_hosted_data =             " satc_d_serialized_data  External Data - Not relevant to Basis Layer - Max. 255 Bytes
*   i_external_key =            " sychar08      External Key - Not relevant to Basis Layer
*   i_schedule_on_server = ' '  " btcsrvname    ' ' = get automaticaly a server with batch process
*   i_activate_trace = ' '      " abap_bool     Activate Trace
  EXCEPTIONS
    CX_SATC_ROOT = 1            "               Root of all Evil
    .  "  SATC_EXECUTE_PROJECT_VIA_BATCH

ABAP code example for Function Module SATC_EXECUTE_PROJECT_VIA_BATCH

The ABAP code below is a full code listing to execute function module SATC_EXECUTE_PROJECT_VIA_BATCH 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_i_project) = 'Check type of data required'.

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

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

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

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

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

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

DATA(ld_i_external_key) = 'some text here'.

DATA(ld_i_schedule_on_server) = 'some text here'.

DATA(ld_i_activate_trace) = 'some text here'.
.

CALL FUNCTION 'SATC_EXECUTE_PROJECT_VIA_BATCH'
  EXPORTING
    i_project =                  ld_i_project
*   i_execution_mode =           ld_i_execution_mode
    i_destination_type =         ld_i_destination_type
*   i_server_name =              ld_i_server_name
*   i_server_group =             ld_i_server_group
*   i_nbr_processes =            ld_i_nbr_processes
*   i_hosted_data =              ld_i_hosted_data
*   i_external_key =             ld_i_external_key
*   i_schedule_on_server =       ld_i_schedule_on_server
*   i_activate_trace =           ld_i_activate_trace
  EXCEPTIONS
    CX_SATC_ROOT =               1
    .  "  SATC_EXECUTE_PROJECT_VIA_BATCH

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
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_i_project
 
 TYPE IF_SATC_MD_PROJECT ,
ld_i_execution_mode
 
 TYPE SATC_D_EXECUTION_MODE ,
ld_i_destination_type
 
 TYPE SATC_D_DESTINATION_TYPE ,
ld_i_server_name
 
 TYPE SATC_D_SERVER_NAME ,
ld_i_server_group
 
 TYPE SATC_D_SERVER_GROUP ,
ld_i_nbr_processes
 
 TYPE SATC_D_NBR_OF_CLNT_PROCESSES ,
ld_i_hosted_data
 
 TYPE SATC_D_SERIALIZED_DATA ,
ld_i_external_key
 
 TYPE SYCHAR08 ,
ld_i_schedule_on_server
 
 TYPE BTCSRVNAME ,
ld_i_activate_trace
 
 TYPE ABAP_BOOL .


ld_i_project = 'some text here'.
ld_i_execution_mode = 'some text here'.
ld_i_destination_type = 'some text here'.
ld_i_server_name = 'some text here'.
ld_i_server_group = 'some text here'.
ld_i_nbr_processes = 'some text here'.
ld_i_hosted_data = 'some text here'.
ld_i_external_key = 'some text here'.
ld_i_schedule_on_server = 'some text here'.
ld_i_activate_trace = 'some text here'.