Ansicht
Dokumentation

SMOD_MPRO0004 - Postprocessing of forecast errors and exception messages

General Data in Customer Master   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

If the update indicator is not selected in the mass forecast, the forecast results (forecast values, forecast errors and exception messages) are not stored.

Accordingly, you have the option of checking the forecast errors with transaction MP33 and then correcting them.

Since the mass forecast can only be carried out once for a period without initialization indicator, it would make sense to first only save the forecast error for test purposes, and then to check the incorrect forecast using transaction MP33. After all errors have been corrected, the mass forecasts with a selected update indicator will start.

This method allows the forecast values and forecast errors to be stored separately from each other. If the 'FLG_PRON' flag in the Include 'ZXFCSU01' is set to True ( FLG_PRON = 'X'. ), forecast errors and exception messages are nevertheless stored, even though the update indicator was not selected.

The BAdI is not active in the standard system.

The BAdI is not filter-dependent.

The BAdI is not for multiple use.

Sample coding exists for this method.

You will find more information on the procedure in the SAP Library under Basis Components -> ABAP Workbench -> Changing the SAP Standard -> Business Add-Ins -> Implementing Business Add-Ins.

PERFORM Short Reference   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 1474 Date: 20240523 Time: 172900     sap01-206 ( 35 ms )