SAP EUP_CO_EXECUTE_WITH_FIELDS Function Module for Execute callable object with fields.
EUP_CO_EXECUTE_WITH_FIELDS is a standard eup co execute with fields SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Execute callable object with fields. processing and below is the pattern details for this FM, 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 eup co execute with fields FM, simply by entering the name EUP_CO_EXECUTE_WITH_FIELDS into the relevant SAP transaction such as SE37 or SE38.
Function Group: GP_PROCESS_RUNTIME
Program Name: SAPLGP_PROCESS_RUNTIME
Main Program: SAPLGP_PROCESS_RUNTIME
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function EUP_CO_EXECUTE_WITH_FIELDS 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 'EUP_CO_EXECUTE_WITH_FIELDS'"Execute callable object with fields..
EXPORTING
IV_CO_ID = "The id of the callable object to execute.
IV_GLOBAL_VERSION = "The version of the callable object to execute - global version.
IV_LOCAL_VERSION = "The version of the callable object to execute - local version.
IV_ACCEPT_BY = "The time stamp for asynchronous execution
IV_ANONYMOS = "Whether or not the item is anonymous.
IV_EXECUTOR = "The executor.
IV_SYSTEM_ID = "Name of SAP R/3 System
IMPORTING
EV_RESULT = "The result information about the callable object execution.
TABLES
* IT_FIELDS = "Callable object fields table.
EXCEPTIONS
ENGINE_EXCEPTION = 1 INVOCATION_EXCEPTION = 2
IMPORTING Parameters details for EUP_CO_EXECUTE_WITH_FIELDS
IV_CO_ID - The id of the callable object to execute.
Data type: GUID_32Optional: No
Call by Reference: No ( called with pass by value option)
IV_GLOBAL_VERSION - The version of the callable object to execute - global version.
Data type: INT4Optional: No
Call by Reference: No ( called with pass by value option)
IV_LOCAL_VERSION - The version of the callable object to execute - local version.
Data type: INT4Optional: No
Call by Reference: No ( called with pass by value option)
IV_ACCEPT_BY - The time stamp for asynchronous execution
Data type: DATSOptional: No
Call by Reference: No ( called with pass by value option)
IV_ANONYMOS - Whether or not the item is anonymous.
Data type: CHAR1Optional: No
Call by Reference: No ( called with pass by value option)
IV_EXECUTOR - The executor.
Data type: SY-UNAMEOptional: No
Call by Reference: No ( called with pass by value option)
IV_SYSTEM_ID - Name of SAP R/3 System
Data type: SY-SYSIDOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for EUP_CO_EXECUTE_WITH_FIELDS
EV_RESULT - The result information about the callable object execution.
Data type: EUP_ST_CO_EXECUTION_STATEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for EUP_CO_EXECUTE_WITH_FIELDS
IT_FIELDS - Callable object fields table.
Data type: EUP_ST_CO_FIELD_TABLEOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
ENGINE_EXCEPTION -
Data type:Optional: No
Call by Reference: Yes
INVOCATION_EXCEPTION -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for EUP_CO_EXECUTE_WITH_FIELDS 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_iv_co_id | TYPE GUID_32, " | |||
| lv_ev_result | TYPE EUP_ST_CO_EXECUTION_STATE, " | |||
| lt_it_fields | TYPE STANDARD TABLE OF EUP_ST_CO_FIELD_TABLE, " | |||
| lv_engine_exception | TYPE EUP_ST_CO_FIELD_TABLE, " | |||
| lv_iv_global_version | TYPE INT4, " | |||
| lv_invocation_exception | TYPE INT4, " | |||
| lv_iv_local_version | TYPE INT4, " | |||
| lv_iv_accept_by | TYPE DATS, " | |||
| lv_iv_anonymos | TYPE CHAR1, " | |||
| lv_iv_executor | TYPE SY-UNAME, " | |||
| lv_iv_system_id | TYPE SY-SYSID. " |
|   CALL FUNCTION 'EUP_CO_EXECUTE_WITH_FIELDS' "Execute callable object with fields. |
| EXPORTING | ||
| IV_CO_ID | = lv_iv_co_id | |
| IV_GLOBAL_VERSION | = lv_iv_global_version | |
| IV_LOCAL_VERSION | = lv_iv_local_version | |
| IV_ACCEPT_BY | = lv_iv_accept_by | |
| IV_ANONYMOS | = lv_iv_anonymos | |
| IV_EXECUTOR | = lv_iv_executor | |
| IV_SYSTEM_ID | = lv_iv_system_id | |
| IMPORTING | ||
| EV_RESULT | = lv_ev_result | |
| TABLES | ||
| IT_FIELDS | = lt_it_fields | |
| EXCEPTIONS | ||
| ENGINE_EXCEPTION = 1 | ||
| INVOCATION_EXCEPTION = 2 | ||
| . " EUP_CO_EXECUTE_WITH_FIELDS | ||
ABAP code using 7.40 inline data declarations to call FM EUP_CO_EXECUTE_WITH_FIELDS
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.| "SELECT single UNAME FROM SY INTO @DATA(ld_iv_executor). | ||||
| "SELECT single SYSID FROM SY INTO @DATA(ld_iv_system_id). | ||||
Search for further information about these or an SAP related objects