SAP EXIT_SAPMM61W_004 Function Module for Postprocessing of forecast errors and exception messages
EXIT_SAPMM61W_004 is a standard exit sapmm61w 004 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Postprocessing of forecast errors and exception messages 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 exit sapmm61w 004 FM, simply by entering the name EXIT_SAPMM61W_004 into the relevant SAP transaction such as SE37 or SE38.
Function Group: XFCS
Program Name: SAPLXFCS
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function EXIT_SAPMM61W_004 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 'EXIT_SAPMM61W_004'"Postprocessing of forecast errors and exception messages.
IMPORTING
FLG_PRON = "Postprocess Forecast Errors
TABLES
FORECAST_MESSAGES = "Forecast Messages
EXPORTING Parameters details for EXIT_SAPMM61W_004
FLG_PRON - Postprocess Forecast Errors
Data type: RM61W-UPDTEOptional: No
Call by Reference: Yes
TABLES Parameters details for EXIT_SAPMM61W_004
FORECAST_MESSAGES - Forecast Messages
Data type: PMELDOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for EXIT_SAPMM61W_004 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_flg_pron | TYPE RM61W-UPDTE, " | |||
lt_forecast_messages | TYPE STANDARD TABLE OF PMELD. " |
  CALL FUNCTION 'EXIT_SAPMM61W_004' "Postprocessing of forecast errors and exception messages |
IMPORTING | ||
FLG_PRON | = lv_flg_pron | |
TABLES | ||
FORECAST_MESSAGES | = lt_forecast_messages | |
. " EXIT_SAPMM61W_004 |
ABAP code using 7.40 inline data declarations to call FM EXIT_SAPMM61W_004
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 UPDTE FROM RM61W INTO @DATA(ld_flg_pron). | ||||
Search for further information about these or an SAP related objects