SAP ISU_S_TRIGGER_DISPLAY Function Module for INTERNAL: Display Billing Order
ISU_S_TRIGGER_DISPLAY is a standard isu s trigger display SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for INTERNAL: Display Billing Order 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 isu s trigger display FM, simply by entering the name ISU_S_TRIGGER_DISPLAY into the relevant SAP transaction such as SE37 or SE38.
Function Group: EL45
Program Name: SAPLEL45
Main Program: SAPLEL45
Appliation area: E
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_S_TRIGGER_DISPLAY 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 'ISU_S_TRIGGER_DISPLAY'"INTERNAL: Display Billing Order.
EXPORTING
X_ANLAGE = "Object key 1
X_ABRDATS = "Object key 2
X_ABRVORG = "Object key 3
* X_UPD_ONLINE = "Indicator: Update Online
* X_NO_CHANGE = "
* X_NO_OTHER = "Indicator: 'Other object' not permitted
IMPORTING
Y_DB_UPDATE = "Indicator: data change
Y_EXIT_TYPE = "Return Mode (EXIT, BACK, CANC)
Y_NEW_ETRG = "
EXCEPTIONS
NOT_FOUND = 1 GENERAL_FAULT = 2
IMPORTING Parameters details for ISU_S_TRIGGER_DISPLAY
X_ANLAGE - Object key 1
Data type: ETRG-ANLAGEOptional: No
Call by Reference: No ( called with pass by value option)
X_ABRDATS - Object key 2
Data type: ETRG-ABRDATSOptional: No
Call by Reference: No ( called with pass by value option)
X_ABRVORG - Object key 3
Data type: ETRG-ABRVORGOptional: No
Call by Reference: No ( called with pass by value option)
X_UPD_ONLINE - Indicator: Update Online
Data type: REGEN-UPD_ONLINEOptional: Yes
Call by Reference: No ( called with pass by value option)
X_NO_CHANGE -
Data type: REGEN-NO_CHANGEOptional: Yes
Call by Reference: No ( called with pass by value option)
X_NO_OTHER - Indicator: 'Other object' not permitted
Data type: REGEN-NO_OTHEROptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ISU_S_TRIGGER_DISPLAY
Y_DB_UPDATE - Indicator: data change
Data type: REGEN-DB_UPDATEOptional: No
Call by Reference: No ( called with pass by value option)
Y_EXIT_TYPE - Return Mode (EXIT, BACK, CANC)
Data type: REGEN-EXIT_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
Y_NEW_ETRG -
Data type: ETRGOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_FOUND - Object Not Found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
GENERAL_FAULT - General Error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISU_S_TRIGGER_DISPLAY 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_x_anlage | TYPE ETRG-ANLAGE, " | |||
| lv_not_found | TYPE ETRG, " | |||
| lv_y_db_update | TYPE REGEN-DB_UPDATE, " | |||
| lv_x_abrdats | TYPE ETRG-ABRDATS, " | |||
| lv_y_exit_type | TYPE REGEN-EXIT_TYPE, " | |||
| lv_general_fault | TYPE REGEN, " | |||
| lv_x_abrvorg | TYPE ETRG-ABRVORG, " | |||
| lv_y_new_etrg | TYPE ETRG, " | |||
| lv_x_upd_online | TYPE REGEN-UPD_ONLINE, " | |||
| lv_x_no_change | TYPE REGEN-NO_CHANGE, " | |||
| lv_x_no_other | TYPE REGEN-NO_OTHER. " |
|   CALL FUNCTION 'ISU_S_TRIGGER_DISPLAY' "INTERNAL: Display Billing Order |
| EXPORTING | ||
| X_ANLAGE | = lv_x_anlage | |
| X_ABRDATS | = lv_x_abrdats | |
| X_ABRVORG | = lv_x_abrvorg | |
| X_UPD_ONLINE | = lv_x_upd_online | |
| X_NO_CHANGE | = lv_x_no_change | |
| X_NO_OTHER | = lv_x_no_other | |
| IMPORTING | ||
| Y_DB_UPDATE | = lv_y_db_update | |
| Y_EXIT_TYPE | = lv_y_exit_type | |
| Y_NEW_ETRG | = lv_y_new_etrg | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| GENERAL_FAULT = 2 | ||
| . " ISU_S_TRIGGER_DISPLAY | ||
ABAP code using 7.40 inline data declarations to call FM ISU_S_TRIGGER_DISPLAY
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 ANLAGE FROM ETRG INTO @DATA(ld_x_anlage). | ||||
| "SELECT single DB_UPDATE FROM REGEN INTO @DATA(ld_y_db_update). | ||||
| "SELECT single ABRDATS FROM ETRG INTO @DATA(ld_x_abrdats). | ||||
| "SELECT single EXIT_TYPE FROM REGEN INTO @DATA(ld_y_exit_type). | ||||
| "SELECT single ABRVORG FROM ETRG INTO @DATA(ld_x_abrvorg). | ||||
| "SELECT single UPD_ONLINE FROM REGEN INTO @DATA(ld_x_upd_online). | ||||
| "SELECT single NO_CHANGE FROM REGEN INTO @DATA(ld_x_no_change). | ||||
| "SELECT single NO_OTHER FROM REGEN INTO @DATA(ld_x_no_other). | ||||
Search for further information about these or an SAP related objects