DP_CONTROL_ASSIGN SAP Function module - Assignment of a data provider object to a control

DP_CONTROL_ASSIGN is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name DP_CONTROL_ASSIGN into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: CNDP
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM DP_CONTROL_ASSIGN - DP CONTROL ASSIGN

CALL FUNCTION 'DP_CONTROL_ASSIGN' "Assignment of a data provider object to a control
  EXPORTING
    h_dp =                      " cntl_handle
    h_cntl =                    " cntl_handle   Control handle
*   type =                      " c             MIME Type
*   subtype =                   " c             MIME Subtype
*   medium =                    " c             Means of Assignment
*   propertyname =              " c
  EXCEPTIONS
    DP_ERROR_INVALID_PARAM = 1  "
    DP_ERROR_ASSIGN = 2         "
    DP_ERROR_GET_DATA = 3       "
    DP_ERROR_MEDIUM_UNKNOWN = 4  "
    .  "  DP_CONTROL_ASSIGN

ABAP code example for Function Module DP_CONTROL_ASSIGN

The ABAP code below is a full code listing to execute function module DP_CONTROL_ASSIGN including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA(ld_h_dp) = 'Check type of data required'.

DATA(ld_h_cntl) = 'Check type of data required'.

DATA(ld_type) = 'Check type of data required'.

DATA(ld_subtype) = 'Check type of data required'.

DATA(ld_medium) = 'Check type of data required'.

DATA(ld_propertyname) = 'Check type of data required'.
.

CALL FUNCTION 'DP_CONTROL_ASSIGN'
  EXPORTING
    h_dp =                       ld_h_dp
    h_cntl =                     ld_h_cntl
*   type =                       ld_type
*   subtype =                    ld_subtype
*   medium =                     ld_medium
*   propertyname =               ld_propertyname
  EXCEPTIONS
    DP_ERROR_INVALID_PARAM =     1
    DP_ERROR_ASSIGN =            2
    DP_ERROR_GET_DATA =          3
    DP_ERROR_MEDIUM_UNKNOWN =    4
    .  "  DP_CONTROL_ASSIGN

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_h_dp
 
 TYPE CNTL_HANDLE ,
ld_h_cntl
 
 TYPE CNTL_HANDLE ,
ld_type
 
 TYPE C ,
ld_subtype
 
 TYPE C ,
ld_medium
 
 TYPE C ,
ld_propertyname
 
 TYPE C .


ld_h_dp = 'Check type of data required'.
ld_h_cntl = 'Check type of data required'.
ld_type = 'Check type of data required'.
ld_subtype = 'Check type of data required'.
ld_medium = 'Check type of data required'.
ld_propertyname = 'Check type of data required'.