SAP DPSPP_RFC_DOC_SAVE Function Module for Dealer Portal Spare Parts: Save and Close Document RFC
DPSPP_RFC_DOC_SAVE is a standard dpspp rfc doc 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 Dealer Portal Spare Parts: Save and Close Document RFC 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 dpspp rfc doc save FM, simply by entering the name DPSPP_RFC_DOC_SAVE into the relevant SAP transaction such as SE37 or SE38.
Function Group: DP_SPP_RFC
Program Name: SAPLDP_SPP_RFC
Main Program: SAPLDP_SPP_RFC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function DPSPP_RFC_DOC_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 'DPSPP_RFC_DOC_SAVE'"Dealer Portal Spare Parts: Save and Close Document RFC.
IMPORTING
ET_MESSAGE = "Return parameter table
EV_VBELN_SAVED = "Saved document number
EXPORTING Parameters details for DPSPP_RFC_DOC_SAVE
ET_MESSAGE - Return parameter table
Data type: BAPIRET2_TOptional: No
Call by Reference: No ( called with pass by value option)
EV_VBELN_SAVED - Saved document number
Data type: VBELN_VAOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for DPSPP_RFC_DOC_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_et_message | TYPE BAPIRET2_T, " | |||
| lv_ev_vbeln_saved | TYPE VBELN_VA. " |
|   CALL FUNCTION 'DPSPP_RFC_DOC_SAVE' "Dealer Portal Spare Parts: Save and Close Document RFC |
| IMPORTING | ||
| ET_MESSAGE | = lv_et_message | |
| EV_VBELN_SAVED | = lv_ev_vbeln_saved | |
| . " DPSPP_RFC_DOC_SAVE | ||
ABAP code using 7.40 inline data declarations to call FM DPSPP_RFC_DOC_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.Search for further information about these or an SAP related objects