FDT_WD_GET_OBJECT_INFO SAP Function module - Get information about a BRF+ object

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

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

Pattern for FM FDT_WD_GET_OBJECT_INFO - FDT WD GET OBJECT INFO

CALL FUNCTION 'FDT_WD_GET_OBJECT_INFO' "Get information about a BRF+ object
  EXPORTING
    iv_id =                     " fdt_uuid      FDT: Universal Unique Identifier
    iv_timestamp =              " fdt_timestamp  BRFplus Time Stamp
*   iv_url_dev_mode = ABAP_FALSE  " boole_d     Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
  IMPORTING
    ev_name =                   " fdt_name      Object Name
    ev_display_text =           " string        Object Display Text
    ev_url =                    " string        URL to workbench
  EXCEPTIONS
    INVALID_INPUT = 1           "               Invalid Input
    INTERNAL_ERROR = 2          "               Internal error
    PERMISSION_FAILURE = 3      "               Missing authorizations
    .  "  FDT_WD_GET_OBJECT_INFO

ABAP code example for Function Module FDT_WD_GET_OBJECT_INFO

The ABAP code below is a full code listing to execute function module FDT_WD_GET_OBJECT_INFO 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_name  
 
 TYPE FDT_NAME
,
ld_ev_display_text  
 
 TYPE STRING
,
ld_ev_url  
 
 TYPE STRING
.


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

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

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

CALL FUNCTION 'FDT_WD_GET_OBJECT_INFO'
  EXPORTING
    iv_id =                      ld_iv_id
    iv_timestamp =               ld_iv_timestamp
*   iv_url_dev_mode =            ld_iv_url_dev_mode
  IMPORTING
    ev_name =                    ld_ev_name
    ev_display_text =            ld_ev_display_text
    ev_url =                     ld_ev_url
  EXCEPTIONS
    INVALID_INPUT =              1
    INTERNAL_ERROR =             2
    PERMISSION_FAILURE =         3
    .  "  FDT_WD_GET_OBJECT_INFO

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_name
 
 TYPE FDT_NAME ,
ld_iv_id
 
 TYPE FDT_UUID ,
ld_ev_display_text
 
 TYPE STRING ,
ld_iv_timestamp
 
 TYPE FDT_TIMESTAMP ,
ld_ev_url
 
 TYPE STRING ,
ld_iv_url_dev_mode
 
 TYPE BOOLE_D .


ld_iv_id = 'Check type of data required'.
ld_iv_timestamp = 'Check type of data required'.
ld_iv_url_dev_mode = 'Check type of data required'.