SAP ISM_SD_EVENT_TEXT_GET Function Module for Read Texts for an Event
ISM_SD_EVENT_TEXT_GET is a standard ism sd event text get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read Texts for an Event 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 ism sd event text get FM, simply by entering the name ISM_SD_EVENT_TEXT_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: JKSDQEVENTMNG
Program Name: SAPLJKSDQEVENTMNG
Main Program: SAPLJKSDQEVENTMNG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISM_SD_EVENT_TEXT_GET 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 'ISM_SD_EVENT_TEXT_GET'"Read Texts for an Event.
EXPORTING
IM_EVENT_ID = "IS-M: Event ID
IMPORTING
EX_EVENTTEXT_TAB = "IS-M: Table Type for Texts in Event Management
EXCEPTIONS
TEXT_NOT_FOUND = 1
IMPORTING Parameters details for ISM_SD_EVENT_TEXT_GET
IM_EVENT_ID - IS-M: Event ID
Data type: JEVENTIDOptional: No
Call by Reference: Yes
EXPORTING Parameters details for ISM_SD_EVENT_TEXT_GET
EX_EVENTTEXT_TAB - IS-M: Table Type for Texts in Event Management
Data type: RJKSDEVENTTEXT_TABOptional: No
Call by Reference: Yes
EXCEPTIONS details
TEXT_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISM_SD_EVENT_TEXT_GET 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_im_event_id | TYPE JEVENTID, " | |||
| lv_text_not_found | TYPE JEVENTID, " | |||
| lv_ex_eventtext_tab | TYPE RJKSDEVENTTEXT_TAB. " |
|   CALL FUNCTION 'ISM_SD_EVENT_TEXT_GET' "Read Texts for an Event |
| EXPORTING | ||
| IM_EVENT_ID | = lv_im_event_id | |
| IMPORTING | ||
| EX_EVENTTEXT_TAB | = lv_ex_eventtext_tab | |
| EXCEPTIONS | ||
| TEXT_NOT_FOUND = 1 | ||
| . " ISM_SD_EVENT_TEXT_GET | ||
ABAP code using 7.40 inline data declarations to call FM ISM_SD_EVENT_TEXT_GET
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