CONTROL_GET_PROPERTY 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 CONTROL_GET_PROPERTY into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
CNTL
Released Date:
Not Released
Processing type: Normal fucntion module
CALL FUNCTION 'CONTROL_GET_PROPERTY' "
EXPORTING
h_control = " cntl_handle
property = " c
* no_flush = " c
* p_count = " i
* p1 = "
* p2 = "
* p3 = "
* p4 = "
* p5 = "
* p6 = "
* p7 = "
* p8 = "
* p9 = "
* p10 = "
* p11 = "
* p12 = "
* p13 = "
* p14 = "
* p15 = "
* p16 = "
CHANGING
return = "
EXCEPTIONS
CNTL_SYSTEM_ERROR = 1 "
CNTL_ERROR = 2 "
. " CONTROL_GET_PROPERTY
The ABAP code below is a full code listing to execute function module CONTROL_GET_PROPERTY 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_return) = 'some text here'.
DATA(ld_h_control) = 'Check type of data required'.
DATA(ld_property) = 'Check type of data required'.
DATA(ld_no_flush) = 'Check type of data required'.
DATA(ld_p_count) = 'Check type of data required'.
DATA(ld_p1) = 'some text here'.
DATA(ld_p2) = 'some text here'.
DATA(ld_p3) = 'some text here'.
DATA(ld_p4) = 'some text here'.
DATA(ld_p5) = 'some text here'.
DATA(ld_p6) = 'some text here'.
DATA(ld_p7) = 'some text here'.
DATA(ld_p8) = 'some text here'.
DATA(ld_p9) = 'some text here'.
DATA(ld_p10) = 'some text here'.
DATA(ld_p11) = 'some text here'.
DATA(ld_p12) = 'some text here'.
DATA(ld_p13) = 'some text here'.
DATA(ld_p14) = 'some text here'.
DATA(ld_p15) = 'some text here'.
DATA(ld_p16) = 'some text here'. . CALL FUNCTION 'CONTROL_GET_PROPERTY' EXPORTING h_control = ld_h_control property = ld_property * no_flush = ld_no_flush * p_count = ld_p_count * p1 = ld_p1 * p2 = ld_p2 * p3 = ld_p3 * p4 = ld_p4 * p5 = ld_p5 * p6 = ld_p6 * p7 = ld_p7 * p8 = ld_p8 * p9 = ld_p9 * p10 = ld_p10 * p11 = ld_p11 * p12 = ld_p12 * p13 = ld_p13 * p14 = ld_p14 * p15 = ld_p15 * p16 = ld_p16 CHANGING return = ld_return EXCEPTIONS CNTL_SYSTEM_ERROR = 1 CNTL_ERROR = 2 . " CONTROL_GET_PROPERTY
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 ENDIF.
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_return | TYPE STRING , |
| ld_h_control | TYPE CNTL_HANDLE , |
| ld_property | TYPE C , |
| ld_no_flush | TYPE C , |
| ld_p_count | TYPE I , |
| ld_p1 | TYPE STRING , |
| ld_p2 | TYPE STRING , |
| ld_p3 | TYPE STRING , |
| ld_p4 | TYPE STRING , |
| ld_p5 | TYPE STRING , |
| ld_p6 | TYPE STRING , |
| ld_p7 | TYPE STRING , |
| ld_p8 | TYPE STRING , |
| ld_p9 | TYPE STRING , |
| ld_p10 | TYPE STRING , |
| ld_p11 | TYPE STRING , |
| ld_p12 | TYPE STRING , |
| ld_p13 | TYPE STRING , |
| ld_p14 | TYPE STRING , |
| ld_p15 | TYPE STRING , |
| ld_p16 | TYPE STRING . |
Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name CONTROL_GET_PROPERTY or its description.