SAP RSPLAPI_PLFCT_SAVE Function Module for Save Planning Functions
RSPLAPI_PLFCT_SAVE is a standard rsplapi plfct save 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 Planning Functions 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 rsplapi plfct save FM, simply by entering the name RSPLAPI_PLFCT_SAVE into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSPLAPI_PLFCT
Program Name: SAPLRSPLAPI_PLFCT
Main Program: SAPLRSPLAPI_PLFCT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function RSPLAPI_PLFCT_SAVE 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 'RSPLAPI_PLFCT_SAVE'"Save Planning Functions.
EXPORTING
I_T_PLANFUNCT = "List of Names of Planning Functions
IMPORTING
E_T_SRV_BAPIRET2 = "
E_SUBRC = "Return Value
IMPORTING Parameters details for RSPLAPI_PLFCT_SAVE
I_T_PLANFUNCT - List of Names of Planning Functions
Data type: RSPLAPI_T_PLFCTOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RSPLAPI_PLFCT_SAVE
E_T_SRV_BAPIRET2 -
Data type: RSPLFB_T_SRV_BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
E_SUBRC - Return Value
Data type: SYST-SUBRCOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RSPLAPI_PLFCT_SAVE 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_t_planfunct | TYPE RSPLAPI_T_PLFCT, " | |||
lv_e_t_srv_bapiret2 | TYPE RSPLFB_T_SRV_BAPIRET2, " | |||
lv_e_subrc | TYPE SYST-SUBRC. " |
  CALL FUNCTION 'RSPLAPI_PLFCT_SAVE' "Save Planning Functions |
EXPORTING | ||
I_T_PLANFUNCT | = lv_i_t_planfunct | |
IMPORTING | ||
E_T_SRV_BAPIRET2 | = lv_e_t_srv_bapiret2 | |
E_SUBRC | = lv_e_subrc | |
. " RSPLAPI_PLFCT_SAVE |
ABAP code using 7.40 inline data declarations to call FM RSPLAPI_PLFCT_SAVE
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 SYST INTO @DATA(ld_e_subrc). | ||||
Search for further information about these or an SAP related objects