WFA_FORECAST_RUN_UPDATE SAP Function module - run a forecasting session

WFA_FORECAST_RUN_UPDATE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name WFA_FORECAST_RUN_UPDATE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: WFA_FORECASTING
Released Date: Not Released
Processing type: Start update immediately (start immed)

Pattern for FM WFA_FORECAST_RUN_UPDATE - WFA FORECAST RUN UPDATE

CALL FUNCTION 'WFA_FORECAST_RUN_UPDATE' "run a forecasting session
  EXPORTING
*   iv_location =               " wfa_location_type  Location Profile
*   iv_org_id =                 " hrobjid       CRM Organizational Management Org Key
    iv_start_date =             " begdatum      Start Date
    iv_end_date =               " enddatum      End Date
*   iv_phase = 0                " i             phase to start forecast at 0=beginning, -1=resume, 1=workload
*   iv_bypass_warnings = 'X'    " wfa_boolean   Boolean ( True = 'X', False = ' ')
    .  "  WFA_FORECAST_RUN_UPDATE

ABAP code example for Function Module WFA_FORECAST_RUN_UPDATE

The ABAP code below is a full code listing to execute function module WFA_FORECAST_RUN_UPDATE including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA(ld_iv_location) = 'Check type of data required'.

DATA(ld_iv_org_id) = 'Check type of data required'.

DATA(ld_iv_start_date) = 'Check type of data required'.

DATA(ld_iv_end_date) = 'Check type of data required'.

DATA(ld_iv_phase) = 'Check type of data required'.

DATA(ld_iv_bypass_warnings) = 'Check type of data required'.
.

CALL FUNCTION 'WFA_FORECAST_RUN_UPDATE'
  EXPORTING
*   iv_location =                ld_iv_location
*   iv_org_id =                  ld_iv_org_id
    iv_start_date =              ld_iv_start_date
    iv_end_date =                ld_iv_end_date
*   iv_phase =                   ld_iv_phase
*   iv_bypass_warnings =         ld_iv_bypass_warnings
    .  "  WFA_FORECAST_RUN_UPDATE

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_iv_location
 
 TYPE WFA_LOCATION_TYPE ,
ld_iv_org_id
 
 TYPE HROBJID ,
ld_iv_start_date
 
 TYPE BEGDATUM ,
ld_iv_end_date
 
 TYPE ENDDATUM ,
ld_iv_phase
 
 TYPE I ,
ld_iv_bypass_warnings
 
 TYPE WFA_BOOLEAN .


ld_iv_location = 'Check type of data required'.
ld_iv_org_id = 'Check type of data required'.
ld_iv_start_date = 'Check type of data required'.
ld_iv_end_date = 'Check type of data required'.
ld_iv_phase = 'Check type of data required'.
ld_iv_bypass_warnings = 'Check type of data required'.