SAP API_SEMBPS_SEQUENCE_EXECUTE Function Module for Execute Planning Sequence
API_SEMBPS_SEQUENCE_EXECUTE is a standard api sembps sequence execute SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Execute Planning Sequence 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 api sembps sequence execute FM, simply by entering the name API_SEMBPS_SEQUENCE_EXECUTE into the relevant SAP transaction such as SE37 or SE38.
Function Group: UPC_API
Program Name: SAPLUPC_API
Main Program: SAPLUPC_API
Appliation area:
Release date: 29-Mar-2001
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function API_SEMBPS_SEQUENCE_EXECUTE 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 'API_SEMBPS_SEQUENCE_EXECUTE'"Execute Planning Sequence.
EXPORTING
I_AREA = "Planning Area
I_PLEVEL = "Planning Level
I_PACKAGE = "Planning Package
I_SEQUENCE = "Planning Sequence
IMPORTING
E_SUBRC = "Return Code
TABLES
* ETK_RETURN = "Return Parameter
IMPORTING Parameters details for API_SEMBPS_SEQUENCE_EXECUTE
I_AREA - Planning Area
Data type: UPC_AREA-AREAOptional: No
Call by Reference: No ( called with pass by value option)
I_PLEVEL - Planning Level
Data type: UPC_PLEVEL-PLEVELOptional: No
Call by Reference: No ( called with pass by value option)
I_PACKAGE - Planning Package
Data type: UPC_PACKAGE-PPACKAGEOptional: No
Call by Reference: No ( called with pass by value option)
I_SEQUENCE - Planning Sequence
Data type: UPF_BUNDLE-BUNDLEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for API_SEMBPS_SEQUENCE_EXECUTE
E_SUBRC - Return Code
Data type: SY-SUBRCOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for API_SEMBPS_SEQUENCE_EXECUTE
ETK_RETURN - Return Parameter
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for API_SEMBPS_SEQUENCE_EXECUTE 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_i_area | TYPE UPC_AREA-AREA, " | |||
| lv_e_subrc | TYPE SY-SUBRC, " | |||
| lt_etk_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_i_plevel | TYPE UPC_PLEVEL-PLEVEL, " | |||
| lv_i_package | TYPE UPC_PACKAGE-PPACKAGE, " | |||
| lv_i_sequence | TYPE UPF_BUNDLE-BUNDLE. " |
|   CALL FUNCTION 'API_SEMBPS_SEQUENCE_EXECUTE' "Execute Planning Sequence |
| EXPORTING | ||
| I_AREA | = lv_i_area | |
| I_PLEVEL | = lv_i_plevel | |
| I_PACKAGE | = lv_i_package | |
| I_SEQUENCE | = lv_i_sequence | |
| IMPORTING | ||
| E_SUBRC | = lv_e_subrc | |
| TABLES | ||
| ETK_RETURN | = lt_etk_return | |
| . " API_SEMBPS_SEQUENCE_EXECUTE | ||
ABAP code using 7.40 inline data declarations to call FM API_SEMBPS_SEQUENCE_EXECUTE
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 AREA FROM UPC_AREA INTO @DATA(ld_i_area). | ||||
| "SELECT single SUBRC FROM SY INTO @DATA(ld_e_subrc). | ||||
| "SELECT single PLEVEL FROM UPC_PLEVEL INTO @DATA(ld_i_plevel). | ||||
| "SELECT single PPACKAGE FROM UPC_PACKAGE INTO @DATA(ld_i_package). | ||||
| "SELECT single BUNDLE FROM UPF_BUNDLE INTO @DATA(ld_i_sequence). | ||||
Search for further information about these or an SAP related objects