cancel
Showing results for 
Search instead for 
Did you mean: 

Issue in RRP3 Fcst Quantity.

Former Member
0 Kudos

Hi Guys,

I have an issue: User uploaded a  forecast for a specific product in DP Planning Book. But after we release the same from DP to SNP, there is some difference in the forecast. For Eg: If the user has uploaded - 100 Units, then after release to SNP - in the product view it is coming as 100.10 Units..

This extra ".10" is getting added to many a forecast value in different periods. In some places there is actually a deduction of "-.10" i mean, if User Fcst is 100 then in rrp3 it is showing 99.90 as Fcst.

I am not sure about the reason of this ".10" difference. I know, this is a very small difference, but still the business wants to know the reason.

Also, do note that this is reported only for 1 product location.

Do let me know in case you have seen such scenario. Thanks in advance.

Regards,

PP.

Accepted Solutions (0)

Answers (1)

Answers (1)

rajkj
Active Contributor
0 Kudos

Hi Prasad,

There might be issues with time-based disaggregation key figure setting or your periodicity in forecast release. Could you please provide some more details?

  • Have you checked at what period level the forecast is being uploaded to DP and how it disaggregated to detailed period levels in DP itself?
  • What periodicity you use in your SNP?
  • Do you use an activity to release the forecast to SNP or t.code /SAPAPO/MC90?
  • Are you providing any periodicity while releasing the forecast to SNP?

Thanks,
Rajesh

Former Member
0 Kudos

Hi Rajesh,

Thanks for your reply and sorry for the delay from my end.

1. The forecast is been uploaded at the SKU level only. So there is no disaggregation issue, I think.

2. We use MONTH as periodicity.

3. No there is no other activity.

4. No, we dont use any periodicity.

Well, this issue is been seen only for a specific material - location combination, say approx 5 Combinations. What I have observed is, there is a job - REORG of Forecast.

But this job runs only for the past period, and the issue in forecast is seen for the furture period. Not sure, if there is something wrong in this program.

Moreover, this program runs for other set of material-locations as well. And for these set, there isnt any issue.

Do let me know in case you need any further information.

Regards,

PP.

rajkj
Active Contributor
0 Kudos

Hi Prasad,

Thanks for the info. Could you please provide the details on how you are releasing forecast for the problematic location product?

Rajesh