cancel
Showing results for 
Search instead for 
Did you mean: 

APO DP Unable to save negative forecast values

0 Kudos

Hi,

We are not able to generate negative statistical forecast in our system in the background or in the foreground. When the system is supposed to generate negative values, we receive the message "Forecast will be negative". Our business requirement is to allow negative values to be generated.

I am using SCM7 EHP2. All key figures allow negative values to be entered, we did manual test entering data in the data view then saving -xx in cells and it works well. When background jobs are ran, the messages that are supposed to allow negative values are checked.

Any ideas?

Thanks,

Accepted Solutions (0)

Answers (1)

Answers (1)

marianoc
Active Contributor
0 Kudos

Hello,

Be sure your key figure is enabled to containt negative values (/SAPAPO/MSDP_ADMIN). I suppose it is, because you said that you can save negatrive values.
Onve it is done, activate the negative forecast in your activity type. In the activity type used to run the forecasting model in background (/SAPAPO/MC8T), go to the button Select Messages and select: 402 Forecast values will be negative.

Kind Regards,

Mariano

0 Kudos

Thank for your answer Mariano,

Indeed, I have already maintained the KF settings and selected message 402 in my activity settings for the background job. It is not working for me.

Are you able to generate negative forecast values in your system?

Regards,

marianoc
Active Contributor
0 Kudos

Hi Maxence,

I have had a similar requirement to see negative forecast.

Anyway, it seems it is a standard DP behaviour. Take a look this note.

1745808 - Negative forecast values set to zero

According to this note, If you do not want to set negatve forecast value to zero, you have to modify the standard program to set the global parameter GV_NEGATIVE_FORECAST in class  /SAPAPO/CL_PE_FCS_SERVICE with value 'X'.

Best Regards,

Mariano

0 Kudos

Hi Mariano,

We have tried this note already in our DEV system without success, plus it seems to be only relevant for SPP.

At this point. we have logged an incident with SAP and we expect to receive correction instructions similar to the ones described in note 1745808.

thanks again,