FDT_F4_OBJECT SAP Function module - FDT: Provides F4 help for Various object types

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

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

Pattern for FM FDT_F4_OBJECT - FDT F4 OBJECT

CALL FUNCTION 'FDT_F4_OBJECT' "FDT: Provides F4 help for Various object types
  EXPORTING
    iv_object_type =            " seu_obj       Object type
*   iv_object_name =            " sobj_name     Object Name to be checked in values
*   itr_value =                 " rseloption    Selection table for object name
*   iv_max_records = 500        " i             Max. Number of records
  IMPORTING
    et_object_list =            " fdt_t_object_value_help  FDT: table type for object value help
    ev_max_exceed =             " boole_d       Indicates whether the max records have exceeded
    .  "  FDT_F4_OBJECT

ABAP code example for Function Module FDT_F4_OBJECT

The ABAP code below is a full code listing to execute function module FDT_F4_OBJECT 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_et_object_list  
 
 TYPE FDT_T_OBJECT_VALUE_HELP
,
ld_ev_max_exceed  
 
 TYPE BOOLE_D
.


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

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

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

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

CALL FUNCTION 'FDT_F4_OBJECT'
  EXPORTING
    iv_object_type =             ld_iv_object_type
*   iv_object_name =             ld_iv_object_name
*   itr_value =                  ld_itr_value
*   iv_max_records =             ld_iv_max_records
  IMPORTING
    et_object_list =             ld_et_object_list
    ev_max_exceed =              ld_ev_max_exceed
    .  "  FDT_F4_OBJECT

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_et_object_list
 
 TYPE FDT_T_OBJECT_VALUE_HELP ,
ld_iv_object_type
 
 TYPE SEU_OBJ ,
ld_ev_max_exceed
 
 TYPE BOOLE_D ,
ld_iv_object_name
 
 TYPE SOBJ_NAME ,
ld_itr_value
 
 TYPE RSELOPTION ,
ld_iv_max_records
 
 TYPE I .


ld_iv_object_type = 'Check type of data required'.
ld_iv_object_name = 'Check type of data required'.
ld_itr_value = 'Check type of data required'.
ld_iv_max_records = 'Check type of data required'.