EFG_DB_FORM_CREATE_LINK SAP Function module

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

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

Pattern for FM EFG_DB_FORM_CREATE_LINK - EFG DB FORM CREATE LINK

CALL FUNCTION 'EFG_DB_FORM_CREATE_LINK' "
  EXPORTING
*   x_client_from = SY-MANDT    " sy-mandt      R/3 System, Client Number from Logon
    x_client_to =               " sy-mandt      R/3 System, Client Number from Logon
    x_formkey =                 " formkey       Application Form
*   x_flg_overwrite =           " c
*   ref_log = CL_EFG_LOG_NULL=>S  " if_efg_log
  IMPORTING
    y_msg =                     " efg_str_msg   System Message
  EXCEPTIONS
    NOT_QUALIFIED = 1           "
    NOT_FOUND = 2               "
    FAILED = 3                  "               Processing error
    EXISTING = 4                "
    .  "  EFG_DB_FORM_CREATE_LINK

ABAP code example for Function Module EFG_DB_FORM_CREATE_LINK

The ABAP code below is a full code listing to execute function module EFG_DB_FORM_CREATE_LINK 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_y_msg  
 
 TYPE EFG_STR_MSG
.


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

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

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

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

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

CALL FUNCTION 'EFG_DB_FORM_CREATE_LINK'
  EXPORTING
*   x_client_from =              ld_x_client_from
    x_client_to =                ld_x_client_to
    x_formkey =                  ld_x_formkey
*   x_flg_overwrite =            ld_x_flg_overwrite
*   ref_log =                    ld_ref_log
  IMPORTING
    y_msg =                      ld_y_msg
  EXCEPTIONS
    NOT_QUALIFIED =              1
    NOT_FOUND =                  2
    FAILED =                     3
    EXISTING =                   4
    .  "  EFG_DB_FORM_CREATE_LINK

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
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_y_msg
 
 TYPE EFG_STR_MSG ,
ld_x_client_from
 
 TYPE SY-MANDT ,
ld_x_client_to
 
 TYPE SY-MANDT ,
ld_x_formkey
 
 TYPE FORMKEY ,
ld_x_flg_overwrite
 
 TYPE C ,
ld_ref_log
 
 TYPE IF_EFG_LOG .


ld_x_client_from = 'Check type of data required'.
ld_x_client_to = 'Check type of data required'.
ld_x_formkey = 'Check type of data required'.
ld_x_flg_overwrite = 'Check type of data required'.
ld_ref_log = 'Check type of data required'.