SAP EUP_GENERATE_INTERACTIVE_FORM Function Module for Generate interactive form.
EUP_GENERATE_INTERACTIVE_FORM is a standard eup generate interactive form SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Generate interactive form. 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 generate interactive form FM, simply by entering the name EUP_GENERATE_INTERACTIVE_FORM 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_GENERATE_INTERACTIVE_FORM 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_GENERATE_INTERACTIVE_FORM'"Generate interactive form..
EXPORTING
IV_TEMPLATE_ID = "GUID in 'CHAR' Format in Uppercase
* IV_MESSAGE_FORM_FILE_NAME = "
* IV_MESSAGE_ATTACHMENT_ONE = "Hold an attachment to be sent along with an Interactive Form
* IV_MESSAGE_ATTACHMENT_TWO = "Hold an attachment to be sent along with an Interactive Form
IV_SYSTEM_ID = "Name of SAP R/3 System
IV_GLOBAL_VERSION = "Natural number
IV_LOCAL_VERSION = "Natural number
* IV_INPUT_DATA = "
IV_EXECUTOR = "User Name
IV_ACCEPT_BY = "Field of type DATS
IV_ANONYMOS = "Single-Character Flag
* IV_DELIVERY_CHANNEL = "
* IV_RECIPIENT_ADDRESS = "
IMPORTING
EV_MIME_TYPE = "
EV_FORM_DATA = "
EV_TASK_ID = "GUID in 'CHAR' Format in Uppercase
TABLES
* IT_MESSAGE_TEMPLATE_FIELDS = "Name, value pairs used for generating interactive forms.
EXCEPTIONS
ENGINE_EXCEPTION = 1 INVOCATION_EXCEPTION = 2
IMPORTING Parameters details for EUP_GENERATE_INTERACTIVE_FORM
IV_TEMPLATE_ID - GUID in 'CHAR' Format in Uppercase
Data type: GUID_32Optional: No
Call by Reference: No ( called with pass by value option)
IV_MESSAGE_FORM_FILE_NAME -
Data type: STRINGOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_MESSAGE_ATTACHMENT_ONE - Hold an attachment to be sent along with an Interactive Form
Data type: EUP_FORM_ATTACHMENTOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_MESSAGE_ATTACHMENT_TWO - Hold an attachment to be sent along with an Interactive Form
Data type: EUP_FORM_ATTACHMENTOptional: Yes
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)
IV_GLOBAL_VERSION - Natural number
Data type: INT4Optional: No
Call by Reference: No ( called with pass by value option)
IV_LOCAL_VERSION - Natural number
Data type: INT4Optional: No
Call by Reference: No ( called with pass by value option)
IV_INPUT_DATA -
Data type: STRINGOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_EXECUTOR - User Name
Data type: SY-UNAMEOptional: No
Call by Reference: No ( called with pass by value option)
IV_ACCEPT_BY - Field of type DATS
Data type: DATSOptional: No
Call by Reference: No ( called with pass by value option)
IV_ANONYMOS - Single-Character Flag
Data type: CHAR1Optional: No
Call by Reference: No ( called with pass by value option)
IV_DELIVERY_CHANNEL -
Data type: STRINGOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_RECIPIENT_ADDRESS -
Data type: STRINGOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for EUP_GENERATE_INTERACTIVE_FORM
EV_MIME_TYPE -
Data type: STRINGOptional: No
Call by Reference: No ( called with pass by value option)
EV_FORM_DATA -
Data type: XSTRINGOptional: No
Call by Reference: No ( called with pass by value option)
EV_TASK_ID - GUID in 'CHAR' Format in Uppercase
Data type: GUID_32Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for EUP_GENERATE_INTERACTIVE_FORM
IT_MESSAGE_TEMPLATE_FIELDS - Name, value pairs used for generating interactive forms.
Data type: EUP_MESSAGE_TEMPLATE_FIELDSOptional: 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_GENERATE_INTERACTIVE_FORM 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_ev_mime_type | TYPE STRING, " | |||
| lv_iv_template_id | TYPE GUID_32, " | |||
| lv_engine_exception | TYPE GUID_32, " | |||
| lt_it_message_template_fields | TYPE STANDARD TABLE OF EUP_MESSAGE_TEMPLATE_FIELDS, " | |||
| lv_iv_message_form_file_name | TYPE STRING, " | |||
| lv_iv_message_attachment_one | TYPE EUP_FORM_ATTACHMENT, " | |||
| lv_iv_message_attachment_two | TYPE EUP_FORM_ATTACHMENT, " | |||
| lv_iv_system_id | TYPE SY-SYSID, " | |||
| lv_ev_form_data | TYPE XSTRING, " | |||
| lv_iv_global_version | TYPE INT4, " | |||
| lv_invocation_exception | TYPE INT4, " | |||
| lv_ev_task_id | TYPE GUID_32, " | |||
| lv_iv_local_version | TYPE INT4, " | |||
| lv_iv_input_data | TYPE STRING, " | |||
| lv_iv_executor | TYPE SY-UNAME, " | |||
| lv_iv_accept_by | TYPE DATS, " | |||
| lv_iv_anonymos | TYPE CHAR1, " | |||
| lv_iv_delivery_channel | TYPE STRING, " | |||
| lv_iv_recipient_address | TYPE STRING. " |
|   CALL FUNCTION 'EUP_GENERATE_INTERACTIVE_FORM' "Generate interactive form. |
| EXPORTING | ||
| IV_TEMPLATE_ID | = lv_iv_template_id | |
| IV_MESSAGE_FORM_FILE_NAME | = lv_iv_message_form_file_name | |
| IV_MESSAGE_ATTACHMENT_ONE | = lv_iv_message_attachment_one | |
| IV_MESSAGE_ATTACHMENT_TWO | = lv_iv_message_attachment_two | |
| IV_SYSTEM_ID | = lv_iv_system_id | |
| IV_GLOBAL_VERSION | = lv_iv_global_version | |
| IV_LOCAL_VERSION | = lv_iv_local_version | |
| IV_INPUT_DATA | = lv_iv_input_data | |
| IV_EXECUTOR | = lv_iv_executor | |
| IV_ACCEPT_BY | = lv_iv_accept_by | |
| IV_ANONYMOS | = lv_iv_anonymos | |
| IV_DELIVERY_CHANNEL | = lv_iv_delivery_channel | |
| IV_RECIPIENT_ADDRESS | = lv_iv_recipient_address | |
| IMPORTING | ||
| EV_MIME_TYPE | = lv_ev_mime_type | |
| EV_FORM_DATA | = lv_ev_form_data | |
| EV_TASK_ID | = lv_ev_task_id | |
| TABLES | ||
| IT_MESSAGE_TEMPLATE_FIELDS | = lt_it_message_template_fields | |
| EXCEPTIONS | ||
| ENGINE_EXCEPTION = 1 | ||
| INVOCATION_EXCEPTION = 2 | ||
| . " EUP_GENERATE_INTERACTIVE_FORM | ||
ABAP code using 7.40 inline data declarations to call FM EUP_GENERATE_INTERACTIVE_FORM
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 SYSID FROM SY INTO @DATA(ld_iv_system_id). | ||||
| "SELECT single UNAME FROM SY INTO @DATA(ld_iv_executor). | ||||
Search for further information about these or an SAP related objects