GCFZ_DYNAMIC_TEXT_SET SAP Function module - GBC: Set Dynamic Text

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

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

Pattern for FM GCFZ_DYNAMIC_TEXT_SET - GCFZ DYNAMIC TEXT SET

CALL FUNCTION 'GCFZ_DYNAMIC_TEXT_SET' "GBC: Set Dynamic Text
  EXPORTING
    i_dyntxt =                  " smp_dyntxt    Function Text or Menu Text
    i_flg =                     " gctp1_flg_type  Indicator: Icon
    i_icon_marked =             " icon_d        Icon for Indicator Set
    i_icon_unmarked =           " icon_d        Icon for Indicator NOT Set
  IMPORTING
    e_dyntxt =                  " smp_dyntxt    Function Text or Menu Text
  EXCEPTIONS
    ERROR = 1                   "
    .  "  GCFZ_DYNAMIC_TEXT_SET

ABAP code example for Function Module GCFZ_DYNAMIC_TEXT_SET

The ABAP code below is a full code listing to execute function module GCFZ_DYNAMIC_TEXT_SET 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_dyntxt  
 
 TYPE SMP_DYNTXT
.


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

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

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

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

CALL FUNCTION 'GCFZ_DYNAMIC_TEXT_SET'
  EXPORTING
    i_dyntxt =                   ld_i_dyntxt
    i_flg =                      ld_i_flg
    i_icon_marked =              ld_i_icon_marked
    i_icon_unmarked =            ld_i_icon_unmarked
  IMPORTING
    e_dyntxt =                   ld_e_dyntxt
  EXCEPTIONS
    ERROR =                      1
    .  "  GCFZ_DYNAMIC_TEXT_SET

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "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_e_dyntxt
 
 TYPE SMP_DYNTXT ,
ld_i_dyntxt
 
 TYPE SMP_DYNTXT ,
ld_i_flg
 
 TYPE GCTP1_FLG_TYPE ,
ld_i_icon_marked
 
 TYPE ICON_D ,
ld_i_icon_unmarked
 
 TYPE ICON_D .


ld_i_dyntxt = 'Check type of data required'.
ld_i_flg = 'Check type of data required'.
ld_i_icon_marked = 'Check type of data required'.
ld_i_icon_unmarked = 'Check type of data required'.

SAP Documentation for FM GCFZ_DYNAMIC_TEXT_SET