RSWAD_WEBPUB_CALL_SERVICE SAP Function module - Liest die F4 Werte eines Attributes

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

Associated Function Group: RSWAD
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM RSWAD_WEBPUB_CALL_SERVICE - RSWAD WEBPUB CALL SERVICE

CALL FUNCTION 'RSWAD_WEBPUB_CALL_SERVICE' "Liest die F4 Werte eines Attributes
  EXPORTING
    i_action =                  " rszwobjid
*   i_tmplid =                  " rszwobjid
    i_template =                " string
    i_nodefragment =            " string
    i_contextfragment =         " string
    i_contextdescription =      " string
  IMPORTING
    e_messages =                " string
    e_result =                  " string
    e_subrc =                   " sysubrc
    e_max_message_type =        " symsgty       Message Type
* TABLES
*   e_t_message =               " bics_prov_t_message  Message Texts
    .  "  RSWAD_WEBPUB_CALL_SERVICE

ABAP code example for Function Module RSWAD_WEBPUB_CALL_SERVICE

The ABAP code below is a full code listing to execute function module RSWAD_WEBPUB_CALL_SERVICE 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_e_messages  
 
 TYPE STRING
,
ld_e_result  
 
 TYPE STRING
,
ld_e_subrc  
 
 TYPE SYSUBRC
,
ld_e_max_message_type  
 
 TYPE SYMSGTY
,
it_e_t_message  
 
 TYPE STANDARD TABLE OF BICS_PROV_T_MESSAGE,"TABLES PARAM
wa_e_t_message
 
 LIKE LINE OF it_e_t_message
.


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

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

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

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

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

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

"populate fields of struture and append to itab
append wa_e_t_message to it_e_t_message.
.

CALL FUNCTION 'RSWAD_WEBPUB_CALL_SERVICE'
  EXPORTING
    i_action =                   ld_i_action
*   i_tmplid =                   ld_i_tmplid
    i_template =                 ld_i_template
    i_nodefragment =             ld_i_nodefragment
    i_contextfragment =          ld_i_contextfragment
    i_contextdescription =       ld_i_contextdescription
  IMPORTING
    e_messages =                 ld_e_messages
    e_result =                   ld_e_result
    e_subrc =                    ld_e_subrc
    e_max_message_type =         ld_e_max_message_type
* TABLES
*   e_t_message =                it_e_t_message
    .  "  RSWAD_WEBPUB_CALL_SERVICE

IF SY-SUBRC EQ 0.
  "All OK
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_e_messages
 
 TYPE STRING ,
ld_i_action
 
 TYPE RSZWOBJID ,
it_e_t_message
 
 TYPE STANDARD TABLE OF BICS_PROV_T_MESSAGE ,
wa_e_t_message
 
 LIKE LINE OF it_e_t_message,
ld_e_result
 
 TYPE STRING ,
ld_i_tmplid
 
 TYPE RSZWOBJID ,
ld_e_subrc
 
 TYPE SYSUBRC ,
ld_i_template
 
 TYPE STRING ,
ld_e_max_message_type
 
 TYPE SYMSGTY ,
ld_i_nodefragment
 
 TYPE STRING ,
ld_i_contextfragment
 
 TYPE STRING ,
ld_i_contextdescription
 
 TYPE STRING .


ld_i_action = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_e_t_message to it_e_t_message.
ld_i_tmplid = 'Check type of data required'.
ld_i_template = 'Check type of data required'.
ld_i_nodefragment = 'Check type of data required'.
ld_i_contextfragment = 'Check type of data required'.
ld_i_contextdescription = 'Check type of data required'.