SAP RM_SZENARIO_GETDETAIL Function Module for RiskM: Szenariodetails lesen
RM_SZENARIO_GETDETAIL is a standard rm szenario getdetail SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for RiskM: Szenariodetails lesen 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 rm szenario getdetail FM, simply by entering the name RM_SZENARIO_GETDETAIL into the relevant SAP transaction such as SE37 or SE38.
Function Group: TVSR
Program Name: SAPLTVSR
Main Program: SAPLTVSR
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RM_SZENARIO_GETDETAIL 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 'RM_SZENARIO_GETDETAIL'"RiskM: Szenariodetails lesen.
EXPORTING
SZENARIO = "Szenario
* DATABASE_READ = "
IMPORTING
SZENAME = "Szenarioname
SZE_WAERS = "Szenariowährung
SZEKUTXT = "Szenariokurztext
SZE_AUTGR = "Berechtigungsgruppe des Szenarios
EXCEPTIONS
SZENARIO_NOT_EXIST = 1
IMPORTING Parameters details for RM_SZENARIO_GETDETAIL
SZENARIO - Szenario
Data type: VTVSZKO-SZENARIOptional: No
Call by Reference: No ( called with pass by value option)
DATABASE_READ -
Data type: COptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for RM_SZENARIO_GETDETAIL
SZENAME - Szenarioname
Data type: VTVSZKO-SZNAMEOptional: No
Call by Reference: No ( called with pass by value option)
SZE_WAERS - Szenariowährung
Data type: VTVSZKO-SZE_WAEHROptional: No
Call by Reference: No ( called with pass by value option)
SZEKUTXT - Szenariokurztext
Data type: VTVSZKO-SZEKUTXTOptional: No
Call by Reference: No ( called with pass by value option)
SZE_AUTGR - Berechtigungsgruppe des Szenarios
Data type: VTVSZKO-AUTGROptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
SZENARIO_NOT_EXIST - Das gewünschte Szenario existiert nicht
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RM_SZENARIO_GETDETAIL 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_szename | TYPE VTVSZKO-SZNAME, " | |||
| lv_szenario | TYPE VTVSZKO-SZENARI, " | |||
| lv_szenario_not_exist | TYPE VTVSZKO, " | |||
| lv_sze_waers | TYPE VTVSZKO-SZE_WAEHR, " | |||
| lv_database_read | TYPE C, " | |||
| lv_szekutxt | TYPE VTVSZKO-SZEKUTXT, " | |||
| lv_sze_autgr | TYPE VTVSZKO-AUTGR. " |
|   CALL FUNCTION 'RM_SZENARIO_GETDETAIL' "RiskM: Szenariodetails lesen |
| EXPORTING | ||
| SZENARIO | = lv_szenario | |
| DATABASE_READ | = lv_database_read | |
| IMPORTING | ||
| SZENAME | = lv_szename | |
| SZE_WAERS | = lv_sze_waers | |
| SZEKUTXT | = lv_szekutxt | |
| SZE_AUTGR | = lv_sze_autgr | |
| EXCEPTIONS | ||
| SZENARIO_NOT_EXIST = 1 | ||
| . " RM_SZENARIO_GETDETAIL | ||
ABAP code using 7.40 inline data declarations to call FM RM_SZENARIO_GETDETAIL
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 SZNAME FROM VTVSZKO INTO @DATA(ld_szename). | ||||
| "SELECT single SZENARI FROM VTVSZKO INTO @DATA(ld_szenario). | ||||
| "SELECT single SZE_WAEHR FROM VTVSZKO INTO @DATA(ld_sze_waers). | ||||
| "SELECT single SZEKUTXT FROM VTVSZKO INTO @DATA(ld_szekutxt). | ||||
| "SELECT single AUTGR FROM VTVSZKO INTO @DATA(ld_sze_autgr). | ||||
Search for further information about these or an SAP related objects