SAP ECATT_EXEC_LCP_RETRIEVE Function Module for

Search SAP Function Modules

ECATT_EXEC_LCP_RETRIEVE is a standard ecatt exec lcp retrieve 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 exec lcp retrieve FM, simply by entering the name ECATT_EXEC_LCP_RETRIEVE into the relevant SAP transaction such as SE37 or SE38.

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

Function ECATT_EXEC_LCP_RETRIEVE 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_EXEC_LCP_RETRIEVE'"
  EXPORTING
   IM_SERVICE =  "
   IS_LCP_IMPO =  "
   IM_BO_NAME =  "
   IM_BO_NODE_NAME =  "
   IT_NODE_IDS =  "
   IM_REQUESTED_IMAGE =  "
   IM_EDIT_MODE =  "
   IT_SORT_OPTIONS =  "
   IS_PROPERTY_SCOPE =  "

 IMPORTING
   ES_LCP_EXPO =  "
   ET_MESSAGES =  "
   EX_DATA =  "
   ET_FAILED_NODE_IDS =  "
   ET_LINKS =  "
   ES_PROPERTIES =  "
   E_SUTTIME =  "

.

IMPORTING Parameters details for ECATT_EXEC_LCP_RETRIEVE

IM_SERVICE -

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

IS_LCP_IMPO -

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

IM_BO_NAME -

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

IM_BO_NODE_NAME -

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

IT_NODE_IDS -

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

IM_REQUESTED_IMAGE -

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

IM_EDIT_MODE -

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

IT_SORT_OPTIONS -

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

IS_PROPERTY_SCOPE -

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

EXPORTING Parameters details for ECATT_EXEC_LCP_RETRIEVE

ES_LCP_EXPO -

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

ET_MESSAGES -

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

EX_DATA -

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

ET_FAILED_NODE_IDS -

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

ET_LINKS -

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

ES_PROPERTIES -

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

E_SUTTIME -

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

Copy and paste ABAP code example for ECATT_EXEC_LCP_RETRIEVE 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_EXEC_LCP_RETRIEVE

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