SAP SATC_EXECUTE_PROJECT Function Module for Project execution: Dispatcher runs in same dialog process
SATC_EXECUTE_PROJECT is a standard satc execute project 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 in same dialog 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 FM, simply by entering the name SATC_EXECUTE_PROJECT 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 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'"Project execution: Dispatcher runs in same dialog 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_PROGRESS_LISTENER = "Progress Reporting
* I_HOSTED_DATA = "External Data - Not relevant to Basis Layer
* I_EXTERNAL_KEY = "External Key - Not relevant to Basis Layer
IMPORTING
E_EXEC_ID = "Execution ID
E_SUCCESS = "Success
EXCEPTIONS
CX_SATC_ROOT = 1
IMPORTING Parameters details for SATC_EXECUTE_PROJECT
I_PROJECT - Meta Data of a Project
Data type: IF_SATC_MD_PROJECTOptional: No
Call by Reference: No ( called with pass by value option)
I_ACTIVATE_TRACE - Activate Trace
Data type: ABAP_BOOLDefault: ' '
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_MODEDefault: '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_TYPEDefault: 'S'
Optional: Yes
Call by Reference: Yes
I_SERVER_NAME - Server Name
Data type: SATC_D_SERVER_NAMEDefault: 'NONE'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_SERVER_GROUP - Server Group
Data type: SATC_D_SERVER_GROUPOptional: 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_PROCESSESDefault: 2
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_PROGRESS_LISTENER - Progress Reporting
Data type: IF_SATC_PROGRESS_LISTENEROptional: Yes
Call by Reference: No ( called with pass by value option)
I_HOSTED_DATA - External Data - Not relevant to Basis Layer
Data type: SATC_D_SERIALIZED_DATAOptional: Yes
Call by Reference: Yes
I_EXTERNAL_KEY - External Key - Not relevant to Basis Layer
Data type: SYCHAR08Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SATC_EXECUTE_PROJECT
E_EXEC_ID - Execution ID
Data type: SATC_D_EXEC_IDOptional: No
Call by Reference: Yes
E_SUCCESS - Success
Data type: ABAP_BOOLOptional: No
Call by Reference: Yes
EXCEPTIONS details
CX_SATC_ROOT - Failed
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SATC_EXECUTE_PROJECT 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_e_exec_id | TYPE SATC_D_EXEC_ID, " | |||
| lv_i_project | TYPE IF_SATC_MD_PROJECT, " | |||
| lv_cx_satc_root | TYPE IF_SATC_MD_PROJECT, " | |||
| lv_i_activate_trace | TYPE ABAP_BOOL, " ' ' | |||
| lv_e_success | TYPE ABAP_BOOL, " | |||
| lv_i_execution_mode | TYPE SATC_D_EXECUTION_MODE, " 'R' | |||
| lv_i_destination_type | TYPE SATC_D_DESTINATION_TYPE, " 'S' | |||
| lv_i_server_name | TYPE SATC_D_SERVER_NAME, " 'NONE' | |||
| lv_i_server_group | TYPE SATC_D_SERVER_GROUP, " | |||
| lv_i_nbr_processes | TYPE SATC_D_NBR_OF_CLNT_PROCESSES, " 2 | |||
| lv_i_progress_listener | TYPE IF_SATC_PROGRESS_LISTENER, " | |||
| lv_i_hosted_data | TYPE SATC_D_SERIALIZED_DATA, " | |||
| lv_i_external_key | TYPE SYCHAR08. " |
|   CALL FUNCTION 'SATC_EXECUTE_PROJECT' "Project execution: Dispatcher runs in same dialog process |
| EXPORTING | ||
| I_PROJECT | = lv_i_project | |
| I_ACTIVATE_TRACE | = lv_i_activate_trace | |
| I_EXECUTION_MODE | = lv_i_execution_mode | |
| I_DESTINATION_TYPE | = lv_i_destination_type | |
| I_SERVER_NAME | = lv_i_server_name | |
| I_SERVER_GROUP | = lv_i_server_group | |
| I_NBR_PROCESSES | = lv_i_nbr_processes | |
| I_PROGRESS_LISTENER | = lv_i_progress_listener | |
| I_HOSTED_DATA | = lv_i_hosted_data | |
| I_EXTERNAL_KEY | = lv_i_external_key | |
| IMPORTING | ||
| E_EXEC_ID | = lv_e_exec_id | |
| E_SUCCESS | = lv_e_success | |
| EXCEPTIONS | ||
| CX_SATC_ROOT = 1 | ||
| . " SATC_EXECUTE_PROJECT | ||
ABAP code using 7.40 inline data declarations to call FM SATC_EXECUTE_PROJECT
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.| DATA(ld_i_activate_trace) | = ' '. | |||
| DATA(ld_i_execution_mode) | = 'R'. | |||
| DATA(ld_i_destination_type) | = 'S'. | |||
| DATA(ld_i_server_name) | = 'NONE'. | |||
| DATA(ld_i_nbr_processes) | = 2. | |||
Search for further information about these or an SAP related objects