TMS_UI_SET_NEW_BUFFER_FORMAT SAP Function module

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

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

Pattern for FM TMS_UI_SET_NEW_BUFFER_FORMAT - TMS UI SET NEW BUFFER FORMAT

CALL FUNCTION 'TMS_UI_SET_NEW_BUFFER_FORMAT' "
* EXPORTING
*   iv_interactive =            " stms_flag
*   iv_inactive = 'X'           " stms_flag
*   iv_verbose =                " stms_flag
  IMPORTING
    ev_nr_of_changes =          " i
  EXCEPTIONS
    PERMISSION_DENIED = 1       "
    CANCELLED_BY_USER = 2       "
    SET_NBUFFORM_FAILED = 3     "
    .  "  TMS_UI_SET_NEW_BUFFER_FORMAT

ABAP code example for Function Module TMS_UI_SET_NEW_BUFFER_FORMAT

The ABAP code below is a full code listing to execute function module TMS_UI_SET_NEW_BUFFER_FORMAT 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_ev_nr_of_changes  
 
 TYPE I
.


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

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

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

CALL FUNCTION 'TMS_UI_SET_NEW_BUFFER_FORMAT'
* EXPORTING
*   iv_interactive =             ld_iv_interactive
*   iv_inactive =                ld_iv_inactive
*   iv_verbose =                 ld_iv_verbose
  IMPORTING
    ev_nr_of_changes =           ld_ev_nr_of_changes
  EXCEPTIONS
    PERMISSION_DENIED =          1
    CANCELLED_BY_USER =          2
    SET_NBUFFORM_FAILED =        3
    .  "  TMS_UI_SET_NEW_BUFFER_FORMAT

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
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_ev_nr_of_changes
 
 TYPE I ,
ld_iv_interactive
 
 TYPE STMS_FLAG ,
ld_iv_inactive
 
 TYPE STMS_FLAG ,
ld_iv_verbose
 
 TYPE STMS_FLAG .


ld_iv_interactive = 'Check type of data required'.
ld_iv_inactive = 'Check type of data required'.
ld_iv_verbose = 'Check type of data required'.