SAP SATC_EXECUTE_PROJECT_VIA_BATCH Function Module for Project execution: Dispatcher runs within separate BTC process

Search SAP Function Modules

SATC_EXECUTE_PROJECT_VIA_BATCH is a standard satc execute project via batch SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Project execution: Dispatcher runs within separate BTC process processing and below is the pattern details for this FM, 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 satc execute project via batch FM, simply by entering the name SATC_EXECUTE_PROJECT_VIA_BATCH into the relevant SAP transaction such as SE37 or SE38.

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

Function SATC_EXECUTE_PROJECT_VIA_BATCH 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 'SATC_EXECUTE_PROJECT_VIA_BATCH'"Project execution: Dispatcher runs within separate BTC process
  EXPORTING
   I_PROJECT =  "Meta Data of a Project
*  I_ACTIVATE_TRACE = ' ' "Activate Trace
*  I_EXECUTION_MODE = 'R' "Execution Mode (Batch or RFC)
*  I_DESTINATION_TYPE = 'S' "Destination type ( 'G'roup, 'S'erver )
*  I_SERVER_NAME = 'NONE' "Server Name
*  I_SERVER_GROUP =  "Server Group
*  I_NBR_PROCESSES = 2 "Number of processes for parallel execution
*  I_HOSTED_DATA =  "External Data - Not relevant to Basis Layer - Max. 255 Bytes
*  I_EXTERNAL_KEY =  "External Key - Not relevant to Basis Layer
*  I_SCHEDULE_ON_SERVER = ' ' "' ' = get automaticaly a server with batch process

EXCEPTIONS
   CX_SATC_ROOT = 1 

.

IMPORTING Parameters details for SATC_EXECUTE_PROJECT_VIA_BATCH

I_PROJECT - Meta Data of a Project

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

I_ACTIVATE_TRACE - Activate Trace

Data type: ABAP_BOOL
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_EXECUTION_MODE - Execution Mode (Batch or RFC)

Data type: SATC_D_EXECUTION_MODE
Default: 'R'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_DESTINATION_TYPE - Destination type ( 'G'roup, 'S'erver )

Data type: SATC_D_DESTINATION_TYPE
Default: 'S'
Optional: No
Call by Reference: Yes

I_SERVER_NAME - Server Name

Data type: SATC_D_SERVER_NAME
Default: 'NONE'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_SERVER_GROUP - Server Group

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

I_NBR_PROCESSES - Number of processes for parallel execution

Data type: SATC_D_NBR_OF_CLNT_PROCESSES
Default: 2
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_HOSTED_DATA - External Data - Not relevant to Basis Layer - Max. 255 Bytes

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

I_EXTERNAL_KEY - External Key - Not relevant to Basis Layer

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

I_SCHEDULE_ON_SERVER - ' ' = get automaticaly a server with batch process

Data type: BTCSRVNAME
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

CX_SATC_ROOT - Root of all Evil

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SATC_EXECUTE_PROJECT_VIA_BATCH 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.

ABAP code using 7.40 inline data declarations to call FM SATC_EXECUTE_PROJECT_VIA_BATCH

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