SAP ISM_WL_CALL_FORECAST_RUN Function Module for IS-M: Execute Branch from Media Issue Worklist to Sales Forecast
ISM_WL_CALL_FORECAST_RUN is a standard ism wl call forecast run SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-M: Execute Branch from Media Issue Worklist to Sales Forecast 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 ism wl call forecast run FM, simply by entering the name ISM_WL_CALL_FORECAST_RUN into the relevant SAP transaction such as SE37 or SE38.
Function Group: JKSD13
Program Name: SAPLJKSD13
Main Program: SAPLJKSD13
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISM_WL_CALL_FORECAST_RUN 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 'ISM_WL_CALL_FORECAST_RUN'"IS-M: Execute Branch from Media Issue Worklist to Sales Forecast.
EXPORTING
* IN_CHANGE_MODE = ' ' "
IN_ISSUE = "
IMPORTING Parameters details for ISM_WL_CALL_FORECAST_RUN
IN_CHANGE_MODE -
Data type: XFELDDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
IN_ISSUE -
Data type: ISMMATNR_ISSUEOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISM_WL_CALL_FORECAST_RUN 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_in_change_mode | TYPE XFELD, " ' ' | |||
| lv_in_issue | TYPE ISMMATNR_ISSUE. " |
|   CALL FUNCTION 'ISM_WL_CALL_FORECAST_RUN' "IS-M: Execute Branch from Media Issue Worklist to Sales Forecast |
| EXPORTING | ||
| IN_CHANGE_MODE | = lv_in_change_mode | |
| IN_ISSUE | = lv_in_issue | |
| . " ISM_WL_CALL_FORECAST_RUN | ||
ABAP code using 7.40 inline data declarations to call FM ISM_WL_CALL_FORECAST_RUN
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.| DATA(ld_in_change_mode) | = ' '. | |||
Search for further information about these or an SAP related objects