cancel
Showing results for 
Search instead for 
Did you mean: 

How to keep past forecasts in R/3 after release from DP

Former Member
0 Kudos

Dear experts

We release forecasts from a demand planning book, data view in monthly buckets starting in current month. (now July 2011)

When the release is done, the forecasts before current month (M-1, M-2) are automatically deleted in R/3. It seems each release overwrites PIRs in the past in MD04. (also no longer visible in MD63, MD73)

How can we keep the unconsummed forecasts of the previous month when we release on current month?

Thank you

Elynn

Edited by: ELynn640 on Jul 20, 2011 11:20 AM

Edited by: ELynn640 on Jul 20, 2011 11:21 AM

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

What about the release period: From - to in repease profile in APO?

What happens to unconsumed forecasts in ERP, needs to be checked in ECC. Check in your system what happens to them. Check if there are any regular jobs planned in TX MD75 and MD76?

Regards

Aban

Former Member
0 Kudos

Hello,

Sorry I forgot to mention that we use a DP planning job to release forecast (/SAPAPO/MC8E) with an activity including a R/3 transfer profile. In that job there is no way you can specify a release period.

In R/3 no jobs are running to delete forecasts in the past (MD74, MD75, MD76)

thanks for your help!

ELynn,

Former Member
0 Kudos

Hi,

When you release forecasts from APO to SAP R/3 are you releasing to Active version ?

Is it possible to release the forecasts, first, from APO to inactive version in SAP R/3, so that active version data is not touched upon. You may then transfer from inactive version to active version for specific period.

Regards

Datta

Answers (2)

Answers (2)

former_member187488
Active Contributor
0 Kudos

Hello,

Please notice the following points when release forecast from APO to R/3:

1)The existed PIRs at R/3 side will first be cleared out, both past and future.

2)No zero forecast will be released.

To acheive your requirement, you can do the following:

1)Apply notes 446688 and 812133 to avoid clearing out the existed forecast in R/3.

2)Implement BADI /SAPAPO/SDP_RELDATA method CHANGE_RELDATA to add zero forecast values in the future.

This is used to clear the existed forecast at R/3 side in the future.

Best Regards,

Ada

Former Member
0 Kudos

Your activity has a release profile assigned to it which specifies the range you are transferring data for.

Any pre-existing values outside this range are set to zero.