FB_DISPLAY_FORM SAP Function module

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

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

Pattern for FM FB_DISPLAY_FORM - FB DISPLAY FORM

CALL FUNCTION 'FB_DISPLAY_FORM' "
* EXPORTING
*   i_formname = SPACE          " tdsfname      Form
*   i_formtype = SPACE          " tdsftype
*   i_with_dialog = 'X'         " tdsfflag
  IMPORTING
    o_formname =                " tdsfname      Form
  EXCEPTIONS
    NO_NAME = 1                 "
    NO_FORM = 2                 "
    NO_ACCESS_PERMISSION = 3    "
    ILLEGAL_LANGUAGE = 4        "               Invalid language
    ILLEGAL_FORMTYPE = 5        "
    .  "  FB_DISPLAY_FORM

ABAP code example for Function Module FB_DISPLAY_FORM

The ABAP code below is a full code listing to execute function module FB_DISPLAY_FORM 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_o_formname  
 
 TYPE TDSFNAME
.


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

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

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

CALL FUNCTION 'FB_DISPLAY_FORM'
* EXPORTING
*   i_formname =                 ld_i_formname
*   i_formtype =                 ld_i_formtype
*   i_with_dialog =              ld_i_with_dialog
  IMPORTING
    o_formname =                 ld_o_formname
  EXCEPTIONS
    NO_NAME =                    1
    NO_FORM =                    2
    NO_ACCESS_PERMISSION =       3
    ILLEGAL_LANGUAGE =           4
    ILLEGAL_FORMTYPE =           5
    .  "  FB_DISPLAY_FORM

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
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 5. "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_o_formname
 
 TYPE TDSFNAME ,
ld_i_formname
 
 TYPE TDSFNAME ,
ld_i_formtype
 
 TYPE TDSFTYPE ,
ld_i_with_dialog
 
 TYPE TDSFFLAG .


ld_i_formname = 'Check type of data required'.
ld_i_formtype = 'Check type of data required'.
ld_i_with_dialog = 'Check type of data required'.