SAP GRMG_PROPAGATE_SCENARIO_FAILED Function Module for GRMG: Write received data in monitoring tree
GRMG_PROPAGATE_SCENARIO_FAILED is a standard grmg propagate scenario failed SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for GRMG: Write received data in monitoring tree 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 grmg propagate scenario failed FM, simply by entering the name GRMG_PROPAGATE_SCENARIO_FAILED into the relevant SAP transaction such as SE37 or SE38.
Function Group: GRMG
Program Name: SAPLGRMG
Main Program: SAPLGRMG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function GRMG_PROPAGATE_SCENARIO_FAILED 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 'GRMG_PROPAGATE_SCENARIO_FAILED'"GRMG: Write received data in monitoring tree.
EXPORTING
FM_IN_SCENARIO_WA = "GRMG: Table for scenario descriptions
FM_IN_SCEN_ERROR = "GRMG: Type for type
FM_IN_CLEAR_ERROR_BRANCH = "Single-character flag
IMPORTING
FM_OUT_ERROR = "General flag
TABLES
FM_CHG_ERROR_ITAB = "GRMG: Table type for error log
IMPORTING Parameters details for GRMG_PROPAGATE_SCENARIO_FAILED
FM_IN_SCENARIO_WA - GRMG: Table for scenario descriptions
Data type: GRMG_SCENARIOSOptional: No
Call by Reference: Yes
FM_IN_SCEN_ERROR - GRMG: Type for type
Data type: GRMG_TYPE_TYPEOptional: No
Call by Reference: Yes
FM_IN_CLEAR_ERROR_BRANCH - Single-character flag
Data type: FLAGOptional: No
Call by Reference: Yes
EXPORTING Parameters details for GRMG_PROPAGATE_SCENARIO_FAILED
FM_OUT_ERROR - General flag
Data type: FLAGOptional: No
Call by Reference: Yes
TABLES Parameters details for GRMG_PROPAGATE_SCENARIO_FAILED
FM_CHG_ERROR_ITAB - GRMG: Table type for error log
Data type: GRMG_ERROR_ITABOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for GRMG_PROPAGATE_SCENARIO_FAILED 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_fm_out_error | TYPE FLAG, " | |||
| lt_fm_chg_error_itab | TYPE STANDARD TABLE OF GRMG_ERROR_ITAB, " | |||
| lv_fm_in_scenario_wa | TYPE GRMG_SCENARIOS, " | |||
| lv_fm_in_scen_error | TYPE GRMG_TYPE_TYPE, " | |||
| lv_fm_in_clear_error_branch | TYPE FLAG. " |
|   CALL FUNCTION 'GRMG_PROPAGATE_SCENARIO_FAILED' "GRMG: Write received data in monitoring tree |
| EXPORTING | ||
| FM_IN_SCENARIO_WA | = lv_fm_in_scenario_wa | |
| FM_IN_SCEN_ERROR | = lv_fm_in_scen_error | |
| FM_IN_CLEAR_ERROR_BRANCH | = lv_fm_in_clear_error_branch | |
| IMPORTING | ||
| FM_OUT_ERROR | = lv_fm_out_error | |
| TABLES | ||
| FM_CHG_ERROR_ITAB | = lt_fm_chg_error_itab | |
| . " GRMG_PROPAGATE_SCENARIO_FAILED | ||
ABAP code using 7.40 inline data declarations to call FM GRMG_PROPAGATE_SCENARIO_FAILED
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