SAP EXECUTE_PRESEL_STEP Function Module for .
EXECUTE_PRESEL_STEP is a standard execute presel step SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for . 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 execute presel step FM, simply by entering the name EXECUTE_PRESEL_STEP into the relevant SAP transaction such as SE37 or SE38.
Function Group: EXECUTE_PRESEL_STEP
Program Name: SAPLEXECUTE_PRESEL_STEP
Main Program: SAPLEXECUTE_PRESEL_STEP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function EXECUTE_PRESEL_STEP 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 'EXECUTE_PRESEL_STEP'"..
EXPORTING
IV_TS_GUID = "LTR: GUID of a Transformation Solution
IV_STEP_KEY = "Step Key
IT_RELATED_PACKAGES = "LTR: Maps Predecessor Steps to Preselection Packages
IV_PCL_PACKAGE_ID = "Package Number to Specify CMIS and TDMS Packages
IV_NAME' ' = "SLO COT Namespace
IV_REAL = "Single-Character Flag
IMPORTING
ET_PACKAGES = "LTR: Table of Object GUIDs
ET_PROTOCOL = "Protocol
IMPORTING Parameters details for EXECUTE_PRESEL_STEP
IV_TS_GUID - LTR: GUID of a Transformation Solution
Data type: LTR_TS_GUIDOptional: No
Call by Reference: No ( called with pass by value option)
IV_STEP_KEY - Step Key
Data type: LTR_STEP_KEYOptional: No
Call by Reference: No ( called with pass by value option)
IT_RELATED_PACKAGES - LTR: Maps Predecessor Steps to Preselection Packages
Data type: LTR_STEP_PACKAGE_TABOptional: No
Call by Reference: No ( called with pass by value option)
IV_PCL_PACKAGE_ID - Package Number to Specify CMIS and TDMS Packages
Data type: CNV_MBT_PACKIDOptional: No
Call by Reference: No ( called with pass by value option)
IV_NAMESPACE - SLO COT Namespace
Data type: LTR_ANY-NAMESPACEOptional: No
Call by Reference: No ( called with pass by value option)
IV_REAL - Single-Character Flag
Data type: CHAR1Optional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for EXECUTE_PRESEL_STEP
ET_PACKAGES - LTR: Table of Object GUIDs
Data type: LTR_GUID_TABOptional: No
Call by Reference: No ( called with pass by value option)
ET_PROTOCOL - Protocol
Data type: LTR_PROTOCOLOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EXECUTE_PRESEL_STEP 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_iv_ts_guid | TYPE LTR_TS_GUID, " | |||
| lv_et_packages | TYPE LTR_GUID_TAB, " | |||
| lv_et_protocol | TYPE LTR_PROTOCOL, " | |||
| lv_iv_step_key | TYPE LTR_STEP_KEY, " | |||
| lv_it_related_packages | TYPE LTR_STEP_PACKAGE_TAB, " | |||
| lv_iv_pcl_package_id | TYPE CNV_MBT_PACKID, " | |||
| lv_iv_namespace | TYPE LTR_ANY-NAMESPACE, " | |||
| lv_iv_real | TYPE CHAR1. " |
|   CALL FUNCTION 'EXECUTE_PRESEL_STEP' ". |
| EXPORTING | ||
| IV_TS_GUID | = lv_iv_ts_guid | |
| IV_STEP_KEY | = lv_iv_step_key | |
| IT_RELATED_PACKAGES | = lv_it_related_packages | |
| IV_PCL_PACKAGE_ID | = lv_iv_pcl_package_id | |
| IV_NAMESPACE | = lv_iv_namespace | |
| IV_REAL | = lv_iv_real | |
| IMPORTING | ||
| ET_PACKAGES | = lv_et_packages | |
| ET_PROTOCOL | = lv_et_protocol | |
| . " EXECUTE_PRESEL_STEP | ||
ABAP code using 7.40 inline data declarations to call FM EXECUTE_PRESEL_STEP
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 NAMESPACE FROM LTR_ANY INTO @DATA(ld_iv_namespace). | ||||
Search for further information about these or an SAP related objects