SAP ECATT_EXISTENCE_CHECK Function Module for
ECATT_EXISTENCE_CHECK is a standard ecatt existence check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for ecatt existence check FM, simply by entering the name ECATT_EXISTENCE_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: ECATT_MAIN
Program Name: SAPLECATT_MAIN
Main Program: SAPLECATT_MAIN
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function ECATT_EXISTENCE_CHECK pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'ECATT_EXISTENCE_CHECK'".
EXPORTING
IM_OBJECT_NAME = "eCATT Object
* IM_OBJECT_VERSION = 1 "eCATT Object Version
* IM_OBJECT_TYPE = 'ECSC' "eCATT Object Type (Test Data, Script, Configuration, etc.)
* IM_EXISTS_ANY_VERSION = ' ' "
* IM_VARIANT_ID = "
* IM_TOOL_NAME = "
* IM_TARGET_SYS = "
IMPORTING
EX_EXISTS = "'X' - Object Exists, ' ' - Object Does Not Exist
EXCEPTIONS
OBJECT_TYPE_UNKNOWN = 1 OPERATION_NOT_SUPPORTED = 2 OBJECT_NOT_FOUND_FOR_VARIANT = 3 OBJECT_EXISTS_FOR_ANOTHER_TOOL = 4 OBJECT_NOT_FOUND_FOR_TARGETSYS = 5 NOT_VARIANT_AND_TARGETSYS = 6
IMPORTING Parameters details for ECATT_EXISTENCE_CHECK
IM_OBJECT_NAME - eCATT Object
Data type: ETOBJ_NAMEOptional: No
Call by Reference: No ( called with pass by value option)
IM_OBJECT_VERSION - eCATT Object Version
Data type: ETOBJ_VERDefault: 1
Optional: Yes
Call by Reference: No ( called with pass by value option)
IM_OBJECT_TYPE - eCATT Object Type (Test Data, Script, Configuration, etc.)
Data type: ETOBJ_TYPEDefault: 'ECSC'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IM_EXISTS_ANY_VERSION -
Data type: ETONOFFDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
IM_VARIANT_ID -
Data type: ETVAR_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_TOOL_NAME -
Data type: ETTOOLNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_TARGET_SYS -
Data type: ETCMP_CMPOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ECATT_EXISTENCE_CHECK
EX_EXISTS - 'X' - Object Exists, ' ' - Object Does Not Exist
Data type: ETONOFFOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
OBJECT_TYPE_UNKNOWN -
Data type:Optional: No
Call by Reference: Yes
OPERATION_NOT_SUPPORTED -
Data type:Optional: No
Call by Reference: Yes
OBJECT_NOT_FOUND_FOR_VARIANT -
Data type:Optional: No
Call by Reference: Yes
OBJECT_EXISTS_FOR_ANOTHER_TOOL -
Data type:Optional: No
Call by Reference: Yes
OBJECT_NOT_FOUND_FOR_TARGETSYS -
Data type:Optional: No
Call by Reference: Yes
NOT_VARIANT_AND_TARGETSYS -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ECATT_EXISTENCE_CHECK Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_ex_exists | TYPE ETONOFF, " | |||
| lv_im_object_name | TYPE ETOBJ_NAME, " | |||
| lv_object_type_unknown | TYPE ETOBJ_NAME, " | |||
| lv_im_object_version | TYPE ETOBJ_VER, " 1 | |||
| lv_operation_not_supported | TYPE ETOBJ_VER, " | |||
| lv_im_object_type | TYPE ETOBJ_TYPE, " 'ECSC' | |||
| lv_object_not_found_for_variant | TYPE ETOBJ_TYPE, " | |||
| lv_im_exists_any_version | TYPE ETONOFF, " SPACE | |||
| lv_object_exists_for_another_tool | TYPE ETONOFF, " | |||
| lv_im_variant_id | TYPE ETVAR_ID, " | |||
| lv_object_not_found_for_targetsys | TYPE ETVAR_ID, " | |||
| lv_im_tool_name | TYPE ETTOOLNAME, " | |||
| lv_not_variant_and_targetsys | TYPE ETTOOLNAME, " | |||
| lv_im_target_sys | TYPE ETCMP_CMP. " |
|   CALL FUNCTION 'ECATT_EXISTENCE_CHECK' " |
| EXPORTING | ||
| IM_OBJECT_NAME | = lv_im_object_name | |
| IM_OBJECT_VERSION | = lv_im_object_version | |
| IM_OBJECT_TYPE | = lv_im_object_type | |
| IM_EXISTS_ANY_VERSION | = lv_im_exists_any_version | |
| IM_VARIANT_ID | = lv_im_variant_id | |
| IM_TOOL_NAME | = lv_im_tool_name | |
| IM_TARGET_SYS | = lv_im_target_sys | |
| IMPORTING | ||
| EX_EXISTS | = lv_ex_exists | |
| EXCEPTIONS | ||
| OBJECT_TYPE_UNKNOWN = 1 | ||
| OPERATION_NOT_SUPPORTED = 2 | ||
| OBJECT_NOT_FOUND_FOR_VARIANT = 3 | ||
| OBJECT_EXISTS_FOR_ANOTHER_TOOL = 4 | ||
| OBJECT_NOT_FOUND_FOR_TARGETSYS = 5 | ||
| NOT_VARIANT_AND_TARGETSYS = 6 | ||
| . " ECATT_EXISTENCE_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM ECATT_EXISTENCE_CHECK
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.| DATA(ld_im_object_version) | = 1. | |||
| DATA(ld_im_object_type) | = 'ECSC'. | |||
| DATA(ld_im_exists_any_version) | = ' '. | |||
Search for further information about these or an SAP related objects