SAP API_SEMBPS_POST Function Module for Save Plan Data in the Database
API_SEMBPS_POST is a standard api sembps post SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Save Plan Data in the Database 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 post FM, simply by entering the name API_SEMBPS_POST 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_POST 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_POST'"Save Plan Data in the Database.
IMPORTING
E_SUBRC = "Return Code
ES_RETURN = "Return Parameter
EXPORTING Parameters details for API_SEMBPS_POST
E_SUBRC - Return Code
Data type: SY-SUBRCOptional: No
Call by Reference: No ( called with pass by value option)
ES_RETURN - Return Parameter
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for API_SEMBPS_POST 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_subrc | TYPE SY-SUBRC, " | |||
| lv_es_return | TYPE BAPIRET2. " |
|   CALL FUNCTION 'API_SEMBPS_POST' "Save Plan Data in the Database |
| IMPORTING | ||
| E_SUBRC | = lv_e_subrc | |
| ES_RETURN | = lv_es_return | |
| . " API_SEMBPS_POST | ||
ABAP code using 7.40 inline data declarations to call FM API_SEMBPS_POST
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 SUBRC FROM SY INTO @DATA(ld_e_subrc). | ||||
Search for further information about these or an SAP related objects