SAP SPOOL_DPO_TRANSFER Function Module for
SPOOL_DPO_TRANSFER is a standard spool dpo transfer SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 spool dpo transfer FM, simply by entering the name SPOOL_DPO_TRANSFER into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_BS_DPO
Program Name: SAPLBBP_BS_DPO
Main Program: SAPLBBP_BS_DPO
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SPOOL_DPO_TRANSFER 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 'SPOOL_DPO_TRANSFER'".
EXPORTING
IV_GUID = "
IV_TARGETAPPL_TYPE = "
TABLES
* ET_CONTROL_RECORD = "
EXCEPTIONS
INTERNAL_ERROR = 1
IMPORTING Parameters details for SPOOL_DPO_TRANSFER
IV_GUID -
Data type: BBP_PDS_PO_HEADER_D-GUIDOptional: No
Call by Reference: No ( called with pass by value option)
IV_TARGETAPPL_TYPE -
Data type: BBP_TARGETAPPL_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SPOOL_DPO_TRANSFER
ET_CONTROL_RECORD -
Data type: BBP_CONTROL_RECORDOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
INTERNAL_ERROR - Internal Error
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SPOOL_DPO_TRANSFER 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_guid | TYPE BBP_PDS_PO_HEADER_D-GUID, " | |||
| lv_internal_error | TYPE BBP_PDS_PO_HEADER_D, " | |||
| lt_et_control_record | TYPE STANDARD TABLE OF BBP_CONTROL_RECORD, " | |||
| lv_iv_targetappl_type | TYPE BBP_TARGETAPPL_TYPE. " |
|   CALL FUNCTION 'SPOOL_DPO_TRANSFER' " |
| EXPORTING | ||
| IV_GUID | = lv_iv_guid | |
| IV_TARGETAPPL_TYPE | = lv_iv_targetappl_type | |
| TABLES | ||
| ET_CONTROL_RECORD | = lt_et_control_record | |
| EXCEPTIONS | ||
| INTERNAL_ERROR = 1 | ||
| . " SPOOL_DPO_TRANSFER | ||
ABAP code using 7.40 inline data declarations to call FM SPOOL_DPO_TRANSFER
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 GUID FROM BBP_PDS_PO_HEADER_D INTO @DATA(ld_iv_guid). | ||||
Search for further information about these or an SAP related objects