SAP ECATT_OBJECT_F4_REQUEST Function Module for

Search SAP Function Modules

ECATT_OBJECT_F4_REQUEST is a standard ecatt object f4 request 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 object f4 request FM, simply by entering the name ECATT_OBJECT_F4_REQUEST into the relevant SAP transaction such as SE37 or SE38.

Function Group: ECATT_GUI_POPUP
Program Name: SAPLECATT_GUI_POPUP
Main Program: SAPLECATT_GUI_POPUP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function ECATT_OBJECT_F4_REQUEST 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_OBJECT_F4_REQUEST'"
  EXPORTING
   IM_OBJECT_TYPE =  "eCATT Object Type (Test Data, Script, Configuration, etc.)
*  IM_OBJECT_NAME =  "eCATT Object
*  IM_SELSCREEN_VARIANT = 'SAP&STANDARD' "Variant Name for Selection Screen
*  IM_SUPPRESS_SELECTION = ' ' "
*  IM_DISPLAY_ONLY = ' ' "Selection Only as Display, No Transfer of Selection Possible
*  IM_WITHOUT_PERSONAL_LIST = 'X' "Without Personal Value List

 IMPORTING
   EX_OBJECT_NAME =  "eCATT Object
   EX_OBJECT_VERSION =  "eCATT Object Version
   EX_ANSWER =  "

EXCEPTIONS
   OBJECT_TYPE_UNKNOWN = 1 

.

IMPORTING Parameters details for ECATT_OBJECT_F4_REQUEST

IM_OBJECT_TYPE - eCATT Object Type (Test Data, Script, Configuration, etc.)

Data type: ETOBJ_TYPE
Optional: No
Call by Reference: No ( called with pass by value option)

IM_OBJECT_NAME - eCATT Object

Data type: ETOBJ_NAME
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_SELSCREEN_VARIANT - Variant Name for Selection Screen

Data type: RALDB_VARI
Default: 'SAP&STANDARD'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_SUPPRESS_SELECTION -

Data type: ETONOFF
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_DISPLAY_ONLY - Selection Only as Display, No Transfer of Selection Possible

Data type: ETONOFF
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_WITHOUT_PERSONAL_LIST - Without Personal Value List

Data type: ETONOFF
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for ECATT_OBJECT_F4_REQUEST

EX_OBJECT_NAME - eCATT Object

Data type: ETOBJ_NAME
Optional: No
Call by Reference: No ( called with pass by value option)

EX_OBJECT_VERSION - eCATT Object Version

Data type: ETOBJ_VER
Optional: No
Call by Reference: No ( called with pass by value option)

EX_ANSWER -

Data type: CHAR1
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

OBJECT_TYPE_UNKNOWN -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ECATT_OBJECT_F4_REQUEST 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.

ABAP code using 7.40 inline data declarations to call FM ECATT_OBJECT_F4_REQUEST

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.

Search for further information about these or an SAP related objects