SAP ISU_IDE_SCENARIO Function Module for
ISU_IDE_SCENARIO is a standard isu ide scenario 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 isu ide scenario FM, simply by entering the name ISU_IDE_SCENARIO into the relevant SAP transaction such as SE37 or SE38.
Function Group: EIDESCENARIO
Program Name: SAPLEIDESCENARIO
Main Program: SAPLEIDESCENARIO
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_IDE_SCENARIO 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_IDE_SCENARIO'".
EXPORTING
* X_CONTRACT = "
* X_ANLAGE = "
* X_EXT_POD = "
* X_INT_POD = "
* X_KEYDATE = SY-DATUM "
IMPORTING
Y_EXT_POD = "
Y_INT_POD = "
Y_SPARTE = "
CHANGING
* T_IDE_SCENARIO = "
TABLES
* T_ALL_SERVICES = "
* T_IDE_SERVICE = "
EXCEPTIONS
NOT_FOUND = 1 SERVPROV_NOT_FOUND = 2 PROGRAMMING_ERROR = 3 GENERAL_FAULT = 4 NOT_CONSISTENT = 5 SYSTEM_ERROR = 6
IMPORTING Parameters details for ISU_IDE_SCENARIO
X_CONTRACT -
Data type: EVER-VERTRAGOptional: Yes
Call by Reference: Yes
X_ANLAGE -
Data type: EANL-ANLAGEOptional: Yes
Call by Reference: Yes
X_EXT_POD -
Data type: EUITRANS-EXT_UIOptional: Yes
Call by Reference: No ( called with pass by value option)
X_INT_POD -
Data type: EUITRANS-INT_UIOptional: Yes
Call by Reference: No ( called with pass by value option)
X_KEYDATE -
Data type: DATUMDefault: SY-DATUM
Optional: No
Call by Reference: Yes
EXPORTING Parameters details for ISU_IDE_SCENARIO
Y_EXT_POD -
Data type: EUITRANS-EXT_UIOptional: No
Call by Reference: No ( called with pass by value option)
Y_INT_POD -
Data type: EUITRANS-INT_UIOptional: No
Call by Reference: No ( called with pass by value option)
Y_SPARTE -
Data type: SPARTEOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for ISU_IDE_SCENARIO
T_IDE_SCENARIO -
Data type: IIDESCENARIOOptional: Yes
Call by Reference: Yes
TABLES Parameters details for ISU_IDE_SCENARIO
T_ALL_SERVICES -
Data type: IALLSERVICESOptional: Yes
Call by Reference: Yes
T_IDE_SERVICE -
Data type: IIDESERVICEOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
SERVPROV_NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
PROGRAMMING_ERROR -
Data type:Optional: No
Call by Reference: Yes
GENERAL_FAULT -
Data type:Optional: No
Call by Reference: Yes
NOT_CONSISTENT -
Data type:Optional: No
Call by Reference: Yes
SYSTEM_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISU_IDE_SCENARIO 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_not_found | TYPE STRING, " | |||
| lv_y_ext_pod | TYPE EUITRANS-EXT_UI, " | |||
| lv_x_contract | TYPE EVER-VERTRAG, " | |||
| lt_t_all_services | TYPE STANDARD TABLE OF IALLSERVICES, " | |||
| lv_t_ide_scenario | TYPE IIDESCENARIO, " | |||
| lv_x_anlage | TYPE EANL-ANLAGE, " | |||
| lv_y_int_pod | TYPE EUITRANS-INT_UI, " | |||
| lt_t_ide_service | TYPE STANDARD TABLE OF IIDESERVICE, " | |||
| lv_servprov_not_found | TYPE IIDESERVICE, " | |||
| lv_y_sparte | TYPE SPARTE, " | |||
| lv_x_ext_pod | TYPE EUITRANS-EXT_UI, " | |||
| lv_programming_error | TYPE EUITRANS, " | |||
| lv_x_int_pod | TYPE EUITRANS-INT_UI, " | |||
| lv_general_fault | TYPE EUITRANS, " | |||
| lv_x_keydate | TYPE DATUM, " SY-DATUM | |||
| lv_not_consistent | TYPE DATUM, " | |||
| lv_system_error | TYPE DATUM. " |
|   CALL FUNCTION 'ISU_IDE_SCENARIO' " |
| EXPORTING | ||
| X_CONTRACT | = lv_x_contract | |
| X_ANLAGE | = lv_x_anlage | |
| X_EXT_POD | = lv_x_ext_pod | |
| X_INT_POD | = lv_x_int_pod | |
| X_KEYDATE | = lv_x_keydate | |
| IMPORTING | ||
| Y_EXT_POD | = lv_y_ext_pod | |
| Y_INT_POD | = lv_y_int_pod | |
| Y_SPARTE | = lv_y_sparte | |
| CHANGING | ||
| T_IDE_SCENARIO | = lv_t_ide_scenario | |
| TABLES | ||
| T_ALL_SERVICES | = lt_t_all_services | |
| T_IDE_SERVICE | = lt_t_ide_service | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| SERVPROV_NOT_FOUND = 2 | ||
| PROGRAMMING_ERROR = 3 | ||
| GENERAL_FAULT = 4 | ||
| NOT_CONSISTENT = 5 | ||
| SYSTEM_ERROR = 6 | ||
| . " ISU_IDE_SCENARIO | ||
ABAP code using 7.40 inline data declarations to call FM ISU_IDE_SCENARIO
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 EXT_UI FROM EUITRANS INTO @DATA(ld_y_ext_pod). | ||||
| "SELECT single VERTRAG FROM EVER INTO @DATA(ld_x_contract). | ||||
| "SELECT single ANLAGE FROM EANL INTO @DATA(ld_x_anlage). | ||||
| "SELECT single INT_UI FROM EUITRANS INTO @DATA(ld_y_int_pod). | ||||
| "SELECT single EXT_UI FROM EUITRANS INTO @DATA(ld_x_ext_pod). | ||||
| "SELECT single INT_UI FROM EUITRANS INTO @DATA(ld_x_int_pod). | ||||
| DATA(ld_x_keydate) | = SY-DATUM. | |||
Search for further information about these or an SAP related objects