HTMLCNTL_GET_EVENT_POSTDATA SAP Function module

HTMLCNTL_GET_EVENT_POSTDATA 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 HTMLCNTL_GET_EVENT_POSTDATA into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM HTMLCNTL_GET_EVENT_POSTDATA - HTMLCNTL GET EVENT POSTDATA

CALL FUNCTION 'HTMLCNTL_GET_EVENT_POSTDATA' "
  EXPORTING
    h_control =                 " cntl_handle
*   clear_trail_bytes = 'X'     " c
*   is_char_data = 'X'          " c
  IMPORTING
    size =                      " i
  TABLES
    post_data =                 "               Post data
* CHANGING
*   type = ' '                  " c
*   subtype = ' '               " c
  EXCEPTIONS
    CNTL_ERROR = 1              "
    CNTL_SYSTEM_ERROR = 2       "
    .  "  HTMLCNTL_GET_EVENT_POSTDATA

ABAP code example for Function Module HTMLCNTL_GET_EVENT_POSTDATA

The ABAP code below is a full code listing to execute function module HTMLCNTL_GET_EVENT_POSTDATA 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_size  
 
 TYPE I
,
it_post_data  
 
 TYPE STANDARD TABLE OF STRING,"TABLES PARAM
wa_post_data
 
 LIKE LINE OF it_post_data
.


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

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

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

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

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

"populate fields of struture and append to itab
append wa_post_data to it_post_data.
.

CALL FUNCTION 'HTMLCNTL_GET_EVENT_POSTDATA'
  EXPORTING
    h_control =                  ld_h_control
*   clear_trail_bytes =          ld_clear_trail_bytes
*   is_char_data =               ld_is_char_data
  IMPORTING
    size =                       ld_size
  TABLES
    post_data =                  it_post_data
* CHANGING
*   type =                       ld_type
*   subtype =                    ld_subtype
  EXCEPTIONS
    CNTL_ERROR =                 1
    CNTL_SYSTEM_ERROR =          2
    .  "  HTMLCNTL_GET_EVENT_POSTDATA

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.

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_type
 
 TYPE C ,
ld_size
 
 TYPE I ,
ld_h_control
 
 TYPE CNTL_HANDLE ,
it_post_data
 
 TYPE STANDARD TABLE OF STRING ,
wa_post_data
 
 LIKE LINE OF it_post_data,
ld_subtype
 
 TYPE C ,
ld_clear_trail_bytes
 
 TYPE C ,
ld_is_char_data
 
 TYPE C .


ld_type = 'Check type of data required'.
ld_h_control = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_post_data to it_post_data.
ld_subtype = 'Check type of data required'.
ld_clear_trail_bytes = 'Check type of data required'.
ld_is_char_data = 'Check type of data required'.