Mass forecasting in SOP in Background Mode


Please find bellow the procedure in order to perform mass forecasting in background when doing SOP, either standard or flexible (The example described here is on standard SOP).

  1. Define background activity (transaction MC8T)

Here, we define the planning type we are going to use (SOPKAPAM, since we are interested in the individual material itself), the activity (PROGNOSE = forecasting), the forecast profile we are going to use (ZAP – my customized forecasting profile), and the name of the entity field we want to forecast (ABSAT = SALES).

  1. Create the background job (transaction MC8D)

Press Execute

We enter the name of the infostructure and the specific version we are going to use (here, since we are using standard SOP we will be using S076).

Press Execute and choose (by double-click) SOPKAPAM as our planning type

In the next screen, press cancel on the already existing variables in order to create a new one for this specific background job

Enter a name and press “Create”

In the next screen, choose “For all selection screens” and press “Continue”

Please note that you can re-use any of the variables you have already created, if it serves your needs. However, the purpose of this example was to illustrate how to define a new variable.

Here, we enter the material we want to forecast, the corresponding plant, the planning activity we are going to use (the one we created earlier in transaction MV8T), and we also set “Plant” as our aggregation level

We press on “Attributes”, and we are getting the following message:

We are getting this message, because version 005 for this material and this planning type has not been created. This means that the forecasting program cannot find where to store its result. For this reason, we terminate the creation of the background job, and we go to MC87 to create version 005 of material 071774406:

We press Enter. In the following table we enter nothing, we just press Save.

Now, we start again the procedure of creating the background job, as it was shown earlier. Now, when we reach the point where we previously had the message “No data exist for chosen selection”, we see that now, when we press “Attributes”, everything is OK

We enter a name for our variant and we press SAVE. We get the message that our variant is saved.

  1. Schedule the background job (transaction MC8G)

For the purpose of our example, we choose “Immediate”

Using transaction MC8J we can check of what happened to our background job

We press execute and we see that our job has run successfully

We can further check (that our forecasting has successfully run and created results) by checking version 005 of material 071774406 for plant 1002

You can use this process for any combination of materials, plants and planning activities you wish. However, in order to perform this procedure, you will first have:

  • to create the corresponding plans for the combination of material-plant-version, as we shown earlier in this document. You can do this easily by using an LSMW. In any case, please double-check that the plan/version has been successfully created and saved, otherwise you will continue getting the message “No data exist for chosen selection”, and
  • to set specific materials into material filed of the background variable (as we did with material 071774406 earlier). If you do not put any material in this filed in the background variable, the program by default excludes all materials and therefore it produces no result.

Best regards,

Dr. Nikos Giannopoulos

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply