ECATT_GET_UI_ATTACH_OBJECT SAP Function module - Function module for return the UI object of attachments

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

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

Pattern for FM ECATT_GET_UI_ATTACH_OBJECT - ECATT GET UI ATTACH OBJECT

CALL FUNCTION 'ECATT_GET_UI_ATTACH_OBJECT' "Function module for return the UI object of attachments
  EXPORTING
    iv_obj_name =               " etobj_name    eCATT Object
    iv_obj_type =               " etobj_type    eCATT Object Type (Test Data, Script, Configuration, etc.)
*   iv_obj_version = 1          " etobj_ver     eCATT Object Version
*   iv_attach_count = SPACE     " etonoff       eCATT Switch On/Off
  IMPORTING
    ex_ui_att =                 " cl_ecatt_ui_attachment  UI for Attachment
    ex_attach_exists =          " etonoff       eCATT Switch On/Off
  EXCEPTIONS
    OBJECT_NOT_FOUND = 1        "               Error during Object creation
    .  "  ECATT_GET_UI_ATTACH_OBJECT

ABAP code example for Function Module ECATT_GET_UI_ATTACH_OBJECT

The ABAP code below is a full code listing to execute function module ECATT_GET_UI_ATTACH_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_ex_ui_att  
 
 TYPE CL_ECATT_UI_ATTACHMENT
,
ld_ex_attach_exists  
 
 TYPE ETONOFF
.


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

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

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

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

CALL FUNCTION 'ECATT_GET_UI_ATTACH_OBJECT'
  EXPORTING
    iv_obj_name =                ld_iv_obj_name
    iv_obj_type =                ld_iv_obj_type
*   iv_obj_version =             ld_iv_obj_version
*   iv_attach_count =            ld_iv_attach_count
  IMPORTING
    ex_ui_att =                  ld_ex_ui_att
    ex_attach_exists =           ld_ex_attach_exists
  EXCEPTIONS
    OBJECT_NOT_FOUND =           1
    .  "  ECATT_GET_UI_ATTACH_OBJECT

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "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_ex_ui_att
 
 TYPE CL_ECATT_UI_ATTACHMENT ,
ld_iv_obj_name
 
 TYPE ETOBJ_NAME ,
ld_ex_attach_exists
 
 TYPE ETONOFF ,
ld_iv_obj_type
 
 TYPE ETOBJ_TYPE ,
ld_iv_obj_version
 
 TYPE ETOBJ_VER ,
ld_iv_attach_count
 
 TYPE ETONOFF .


ld_iv_obj_name = 'Check type of data required'.
ld_iv_obj_type = 'Check type of data required'.
ld_iv_obj_version = 'Check type of data required'.
ld_iv_attach_count = 'Check type of data required'.