SAP DP_CONTROL_GET_STREAM Function Module for
DP_CONTROL_GET_STREAM is a standard dp control get stream 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 dp control get stream FM, simply by entering the name DP_CONTROL_GET_STREAM into the relevant SAP transaction such as SE37 or SE38.
Function Group: CNDP
Program Name: SAPLCNDP
Main Program: SAPLCNDP
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DP_CONTROL_GET_STREAM 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 'DP_CONTROL_GET_STREAM'".
EXPORTING
* H_DP = "
H_CNTL = "Control Handle
PROPERTYNAME = "Name of Property
* MEDIUM = "
* SEND_DATA_AS_STRING = "
IMPORTING
DATE = "
TIME = "
SIZE = "
DESCRIPTION = "
CHANGING
* TYPE = "
* SUBTYPE = "
TABLES
DATA = "Data Table
EXCEPTIONS
DP_ERROR_INVALID_PARAM = 1 DP_ERROR_CREATE = 2 DP_ERROR_GET_DATA = 3 DP_ERROR_GET_PROPERTY = 4
IMPORTING Parameters details for DP_CONTROL_GET_STREAM
H_DP -
Data type: CNTL_HANDLEOptional: Yes
Call by Reference: Yes
H_CNTL - Control Handle
Data type: CNTL_HANDLEOptional: No
Call by Reference: Yes
PROPERTYNAME - Name of Property
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
MEDIUM -
Data type: COptional: Yes
Call by Reference: No ( called with pass by value option)
SEND_DATA_AS_STRING -
Data type: CHAR01Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for DP_CONTROL_GET_STREAM
DATE -
Data type: SY-DATUMOptional: No
Call by Reference: No ( called with pass by value option)
TIME -
Data type: SY-UZEITOptional: No
Call by Reference: No ( called with pass by value option)
SIZE -
Data type: IOptional: No
Call by Reference: No ( called with pass by value option)
DESCRIPTION -
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for DP_CONTROL_GET_STREAM
TYPE -
Data type: COptional: Yes
Call by Reference: No ( called with pass by value option)
SUBTYPE -
Data type: COptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for DP_CONTROL_GET_STREAM
DATA - Data Table
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
DP_ERROR_INVALID_PARAM - Incorrect parameter
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DP_ERROR_CREATE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DP_ERROR_GET_DATA -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DP_ERROR_GET_PROPERTY -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for DP_CONTROL_GET_STREAM 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: | ||||
| lt_data | TYPE STANDARD TABLE OF STRING, " | |||
| lv_date | TYPE SY-DATUM, " | |||
| lv_h_dp | TYPE CNTL_HANDLE, " | |||
| lv_type | TYPE C, " | |||
| lv_dp_error_invalid_param | TYPE C, " | |||
| lv_time | TYPE SY-UZEIT, " | |||
| lv_h_cntl | TYPE CNTL_HANDLE, " | |||
| lv_subtype | TYPE C, " | |||
| lv_dp_error_create | TYPE C, " | |||
| lv_size | TYPE I, " | |||
| lv_propertyname | TYPE C, " | |||
| lv_dp_error_get_data | TYPE C, " | |||
| lv_medium | TYPE C, " | |||
| lv_description | TYPE C, " | |||
| lv_dp_error_get_property | TYPE C, " | |||
| lv_send_data_as_string | TYPE CHAR01. " |
|   CALL FUNCTION 'DP_CONTROL_GET_STREAM' " |
| EXPORTING | ||
| H_DP | = lv_h_dp | |
| H_CNTL | = lv_h_cntl | |
| PROPERTYNAME | = lv_propertyname | |
| MEDIUM | = lv_medium | |
| SEND_DATA_AS_STRING | = lv_send_data_as_string | |
| IMPORTING | ||
| DATE | = lv_date | |
| TIME | = lv_time | |
| SIZE | = lv_size | |
| DESCRIPTION | = lv_description | |
| CHANGING | ||
| TYPE | = lv_type | |
| SUBTYPE | = lv_subtype | |
| TABLES | ||
| DATA | = lt_data | |
| EXCEPTIONS | ||
| DP_ERROR_INVALID_PARAM = 1 | ||
| DP_ERROR_CREATE = 2 | ||
| DP_ERROR_GET_DATA = 3 | ||
| DP_ERROR_GET_PROPERTY = 4 | ||
| . " DP_CONTROL_GET_STREAM | ||
ABAP code using 7.40 inline data declarations to call FM DP_CONTROL_GET_STREAM
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 DATUM FROM SY INTO @DATA(ld_date). | ||||
| "SELECT single UZEIT FROM SY INTO @DATA(ld_time). | ||||
Search for further information about these or an SAP related objects