Forecast horizon in deployment

Dear All,
We have requirement deployment run should not consider the forecast horizon maintained in APO material master whereas SAP Std behaviour will consider it.  (it will not be considered only in deployment optimizer as per std).  We are planning for a custom development to meet this requirement.  Need your inputs on way to forward for various strategies on custom development to achieve this scenario.
Appreciate your support, thanks in advance
Regards
R. Senthil Mareeswaran.

Hi Senthil,
I guess I didnt get the issue here. I mean you maintain forecast horizon to plan only based on confirmed customer orders or any dependent demand in the short term. So, you dont consider forecast as a part of your total demand by maintaining a forecast horizon.
Eventually SNP heuristic/Optimizer will not plan any supply (distribution receipt) for the forecast demand inside this horizon. So, deployment will not create any supply confirmation for this forecast as well.
Now if you dont want this to happen, then simply remove the forecast horizon from the loc-product master! Am I missing something?
Anyway some thought here-
you can define a new custom macro to calculate the total demand as per your requirement. Or you can use a custom macro to calculate your total ATD receipt or ATD issue quantity as per your client's needs (considering/not considering the forecast horizon).
Finally take your deployment run.
Thanks,
Satyajit

Similar Messages

  • SAP GRC 10.0 Risk Management - Forecasting Horizon Scoring Analysis Mode

    Hi everyone,
    In SAP GRC 10.0 Risk Management Support Package 7, we need to assess a corporate risk by performing an automatic analysis aggregation based on a scoring analysis profile.
    The problem is that corporate risks must be created based on a forecasting horizon.
    So, can we create forecasting horizons with scoring analysis mode? How? Must be enabled through customizing or applying a SAP note?
    Best Regards,
    Chema Traveso

    Hi,
    I think this is still user-specific, as it was in 5.X. I have checked the new GRC authorisation object parameters delivered within the roles and also tried to see if a Admin user was able to see all the variants created by the different users, but so far I have not found a solution.
    It may be worthwhile to raise this in "IdeaPlace", hoping it gets enough votes and SAP's attention for implementing in a future Support Pack delivery.

  • Forecast horizon values are not being considered in Total demand row

    Hello Experts,
    We are in SCM 4.1 Version.
    I have a question regarding Forecast horizon consderation in Planning book.
    We have a weekly data view In our  Planning book,and in that planning data view "Total demand" row is not calculating correctly for the products with Forecast horizon .
    The entire Forecast is counted in Total demand without considering forecast horizon value for that Product.
    But this is working fine for Daily data view.
    I have also noticed that, Total demand values are calculating correcly in weekly view ( Forecast horizon value from the Product master is taken into account ) only when the Forecast horizon value crossing that week bucket.(i.e >7 days).
    But usually we will have a Forecast  horizon value of 3 days for all our products,.
    What should we do to get the Total demand values correctly?
    Thanks in advance..
    SAPLOUIS.
    Edited by: saplouis on Dec 5, 2010 6:42 AM

    Check the macros on data view
    Regards
    Aban

  • Forecast Horizon issue

    Dear Experts,
    Please share your experience in using the Forecast Horizon field under SNP2 tab in product master (MAT1) in APO. Apparently in our case, the Forecast (FA) covered by the defined forecast horizon is being deleted. Questions are:
    1. What is the triggering point of the deletion of the forecast? Upon SNP heuristics, or CIFed sales order - forecast consumption or other else?
    2. Impact of this behavior in SNP point of view?
    Looking at help (F1) of Forecast Horizon, it's not being explicitly being said the after effect/result in the Forecast key figure and only the Total Demand is being explained.
    Looking forward for your usual help on this.
    Thanks and best regards,
    AA

    Hi,
    well this is done via macros in SNP dataview. The forecast horizon is a period for which forecasts should not be considered hence SNP heuristic will not plan this demand for the forecast horizon.
    Also the /SAPAPO/OM_REORG_DAILY report will consider them as consumed and will change the forecast with a quantity of 0. You might still see this orders in product view if you display orders with 0 quantity.
    Best regards,
    Cyrille.

  • Use of Forecast Horizon in CTM Run

    Hello all,
    Our requirement is - CTM Run should consider 'Forecast Horizon' (as mentioned in Product Master) while creating PReqs from Demands (FC - Planned Independent Requirements).
    As this functionality is not provided in standard SAP, we need to implement some BADI.
    Please provide the soultion - if anyone has already implemented the same - i.e. which BADI is usefull and how to go with that.
    Thanks a lot in advance.
    Best Regards,

    Moderator message -
    When closing old threads, there is no need to add a comment. Adding a pasted answer like "Thanks" only brings old threads to the top of the forum list and pushes current ones down. If you do add a comment, please indicate just how the problem was resolved.
    Rob

  • Deployment after CTM or SNP

    Dear Gurus:
            We perform CTM run based a prioritized demand. For example: Fulfill sales order first then safty stock request. So, after CTM, system will try to fulfill sales order first and generate related SNP PR.
            If we wanna use deployment when there is a supply shortage. But we wanna deployment stock transfer order to fulfill sales order first, not evenly distributed based on fair share rule.
    Ex:
    Required Qty of Destination Loc--
    LOC A 100PC(Sales order)  LOC B 100PC(Safety stock)
    Supply Qty of Source Loc--
    LOC C 50PC
    Is this possible to let system generate a deployment order 50 PC to LOC A only because it's sales order request. Not evenlt distributed 50 to LOC A and 50 to LOCB. Is this possible in SAP APO?
    Thanks Anyway!
    Scott Chen

    Well. not really. I was just wondering that if you want to do deployment for sales order driven demands, you may have to do some lite development. The way I would envision your requirement can be done is using the Forecast Horizon field in SNP 2 tab of Location Product. You can set it to a specific value, say 2 months. You may then then run CTM and deployment (in regenerative mode) subsequently.
    Then programmatically remove the forecast horizon, run CTM and deployment (both in net-change mode) subsequently. This will ensure that the first pass of CTM and deployment does take care of sales order driven demands first. The second pass will try to plan for other kind of demands if supply is still available. Let me know how it works.

  • Auto Model 2 - Constant forecast 1 historical period

    I have a composite forecast (100% each) consisting of 5 univariate models that should select the best model based on MAD.  I have a product that has only 1 historical period of actuals in the last 36 months.  I would have expected the Auto Model 2 to forecast "zero" but it has recommended a constant forecast of the same value as the 1 historical period for the next 24 months. 
    Is there a parameter that should be modified in order to improve the forecast.  Any help on optimizing the parameters would also be very helpful.  I have yet to hear of a great success story with Auto Model 2. 
    Thank you.

    Hi,
    You need at least 3 historical periods and 2 seasonal cycles (if valid) to initiate the model. Since the model is not initialized, the procedure used copy history model i.e. historical data used as forecast data for the entire forecast horizon.
    Thanks,
    Rajesh

  • Mixed periodicities in a forecast are not allowed ???

    Hi All,
    When I try to run the forecast in DP in BACKGROUND then I see following message "mixed periodicities in a forecast are not allowed", but when I execute the forecast in foreground it works completely fine with that forecast profile and everything same.
    Can anyone suggest the way to handle this???
    Best Regards,
    Chandan Dubey

    Hi Chandan,
    This is the standard design in the background.
    If you run your forecast in batch you can only use one periodicity and
    not mixed periodicities. Per design it is not allowed to             
    use different periodicities for forecast in mass processing.         
    In interactive demand planning, the forecast key figure and other key   
    figures, such as the adjusted past within the past and forecast horizon 
    are saved independently of the planning horizon of the planning book or 
    planning view. This means in particular that the forecast also saves    
    results outside of the planning horizon for the planning book or        
    planning view.For performance reasons, however, the horizon of the      
    planning book must be greater than the horizons in the forecast profile 
    in the background processing.It is sufficient therefore if the horizon  
    of the planning book in greater than or equal to the forecast horizon.In
    this case, the forecast results are saved but the adjusted past or the  
    expost forecast cannot be saved.Therefore, a warning message indicating 
    that the horizon of the planning book does not contain the past period  
    for the forecast is issued here.In addition, note that for performance  
    reasons the period units of the planning book and forecast profile must 
    be identical in the background processing.This is directly due to the   
    fact that you are not allowed to you use planning books with mixed      
    period units in the background processing.These restrictions do not     
    exist in the interactive planning.      
    I hope this helps.
    Regards,
    Tibor                                                                               
    Furthermore, note that data is not saved in lines or areas that are not 
    ready for input in the background processing.Therefore if, for example, 
    you want to save the adjusted past, then the past horizon for the       
    planning book must be ready for input.

  • APO DP - use of forecast strategy 60 (copy history)

    I am using APO DP V5.
    I need to understand how forecast strategy 60 (copy history) works.
    Suppose I have a three year forecast horizon.
    Can I use this to copy from last year's history into <u>each</u> of these 3 years?
    Thanks,
    Bob Austin, Atos Origin

    Hi Bob.
    The answer to your question is no. 12 months of history will only generate 12 months of forecast.
    I would suggest that if this was a requirement then a macro could be used to generate such a forecast.
    Hope this helps.
    Mark

  • Unable to maintain forecast

    Hi All,
    While running the Fcst interactively through Transaction SDP94 and clicking on the Univariate Forecast icon there is an error coming
    " Incorrect shift entry found and deleted" this error is coming when in the Horizon tab the date in Forecast Horizon (From date) is put. System is not doing any calculation of the Fcst.
    Can anyone assist
    Thanks,
    Harsh

    Harsh,
    Please check your univariate profile. Is it in active status?..I mean is it in saved condition? (I hope you were trying in display mode). If not saved then you need to save your Fc profile.
    Thanks,
    Satyajit

  • Moving average forecast does not work correctly

    Hello,
    I have a forecast model with the strategy moving average 6 months. When I checked the forecast values in the planning book, I recognized that there is a mismatch with the calculation of the forecast:
    There is a drift of 2 months when showing the values in the appendant buckets. The first bucket which is filled with forecast values (bucket: current month + 1) contains the moving average value from month - 8 until month - 2.
    Example: forecast value for Feb 12 is calculated as follows:
    (Nov 11 + Oct 11 + Sep 11 + Aug 11 + Jul 11 + Jun 11) / 6
    It is the same procedure for all other following months.
    The right calculation should be as follows:
    (Jan 12 + Dez 11 + Nov 11 + Oct 11 + Sep 11 + Aug 11) / 6
    I checked several settings in the activity and job creation and in the setting of the forecast profiles. I expected that an offset of 2 months is set, but there is nothing.
    So, I do not know how to explain this system behaviour....
    Hope anybody can help!
    Thanks and kind regards
    Heinz

    Hello Heinz,
    The only place to check is the forecast profile. Let me assume that you are not talking with reference to SPP. Also, that the period indicator in your master profile is Months. So, this would mean that you have maintained forecast profile as follows:
    You need to cross-check that the offset in the section history horizon of the master profile should have value +1, since you are running the forecasting during January, and you want January history to be considered in average calculation. Periods in history horizon should be 6.
    Similarly, in the forecast horizon in the master profile, you should have an offset of +1, since you are running the forecast in Jan, but you want the forecast to happen from the month of Feb onwards.
    Also, check in the univariate profile tab that you are checking for the right KF for history values, when you look in the planning view. 
    There is nothing more to standard forecasting apart from few things like 'like profile' or 'phase-in, phase-out' profile. Other option for changes is some custom logic, but it doesn't seem that there is a need for it if calculation is for simple moving average.
    So, if the above points don't explain your situation, then better to raise OSS for SAP, to see if there could be some bug.
    Thanks - Pawan

  • Statistical Forecasting - Directing Forecast Results to Spool

    hi,
    We are executing planning jobs ( /n/sapapo/mc8g) for Statistical Forecasting. The planning jobs have been set up through /n/sapapo/mc8e with the required parameters and forecast profiles attached.
    Post successful completion of the planning jobs, we get the results in the following manner :
    1. Forecast Results are getting stored in the specified key figure in the interactive planning book
    2. Job execution messages and information on parameters such as MAPE, MAD etc are directed to the spool.
    Is there anyway in which we can also direct the forecast results to the spool ?
    regards,
    Anirudha

    hi Luiz,
    Basically I wanted the forecasting run results to be directed to the spool to be viewed at a later point of time.
    What we are currently doing is trying out the various models for statistical forecasting ( using Univariate profiles ). SInce we are having to execute a large number of runs, it is pretty time consuming as we have to execute it for a specific brand, note down the forecasted numbers ( populated in the interactive planning book for the forecast horizon ) and then move on to the next model / brand.
    To simplify and speed up the process, we wanted to try out the following :
    1) Create the required number of univariate profiles with various models and parameters
    2) Create Planning Activities ( with the corresponding profile attached ) and Planning Jobs
    3) Execute the planning jobs through mc8g
    4) View the job output in the job spool at one go
    The issue we are facing is that the forecast results are getting written only to the interactive planning book. And not directed to the spool. I have listed the sample spool output of the planning run job below. If you observe the spool, only run related info and MAPE, MSE etc are listed.
    How do we write the forecast results ( for the forecast horizon ) to the spool also ?
    Sample Spool
    10.03.2010              Run planning job in the background                                                                               
    Charact. Combination(1 Frm 1):                                       
    DELM ADV                                                                  
    Following forecast profile selected: Mil_Forecasting                      
    Required Time for Forecast in Seconds: 0.007                              
    Univariate forecast successfully executed                                 
    Seasonal test called                                                      
    Number of periods: 12 , Autocorrelation: 0.359 , Limit: 0.30              
    Season test is positive                                                   
    MAPE: 49.78 MSE: 787878.39 RMSE: 887.63 MPE: 28.64-                       
    MAD: 485.02 Error total: 1895.38                                          
    Data saved successfully                                                                               
    regards,
    Anirudha

  • Interactive Forecasting terminates because of perios definition

    Dear All,
    Currently in SCM 5.0, when we execute a forecast interactively ( in posting periods), we are getting an error that the period for a particular data (01.01.2013) cannot be determined.
    The basic settings are as follows:
    1. Fiscal year variant defined till 31st December 2012
    2. Planning area initialized till 2009
    3. Planning calendar (time stream defined) till 2009
    4. In master forecast profile, we are using posting periods and have defined the fiscal year variant
    Please let me know if anyone of you has encountered a similar error before.
    Regards,
    Kedar

    Hi Kedar,
    It is probably that the problem is on your planning book/data view periods definition. Try changing also the forecast horizon at the forecast profile to 2009 at least.
    Best regards,
    Carlos Rodriguez.

  • Horizon FLEX 1.1 - Question on Encryption Password

    Hi all,
    For my Horizon FLEX deployment, VMware Workstation 11 is used to create source VM. When the source VM is assigned to multiple users, it seems that the power-on passphrase (encryption password) will be the same for those users. Other than creating multiple source VMs with different encryption password, is there another workaround to achieve a similar result (different power-on passphrase for different users)?
    Any idea, workaround and suggestion are welcome.
    Thanks and regards,
    Tony Yeung

    Hello at the moment the only option is to force the user to change the password after the first logon. Check the entitlement for that setting The tick box under the restrictions.
    Keep in mind that you can upload a template only ones as an image.

  • Horizons

    Hello
    A very basic question, if you guys can pleas advice me on this:
    Can you tell me whats the recommended length of below horizons, or factors to define these horizons:
    PPDS Horizon
    SNP production horizon
    Extended horizon
    Deployment horizon
    Pull Horizon
    Push Horizon
    Stock Transfer Horizon
    Is there a relation between PPDS horizon and Deployment horizon. Even in case it makes logical sense please let me know the factors to define them to see the whole picture
    Thanks in advance
    -Rahul

    Hi Rahul,
    There are a lot of factors which will influence the PPDS horizon...
    1. You need to look at the cumulative lead time, right from starting the execution of planned order at the lowest level to the FG planned order leadtimes...
    2. How different are your SNP & PPDS PPMs if they are almost similar then your SNP run itself would have created planned orders / preqs for all products and planned capacities also. If they are very different and the components present in PPDS PPM but not in SNP have significant lead time, you have to consider their procurement and production lead times as well in your PPDS horizon.
    3. Some plants have a larger PPDS horizon to have sufficient planned orders even in future to enable rescheduling. if there is a shortage towards todays planned order and all componets are avaialble for an order planned for next week, they might want to reschedule the next weeks order and produce today to ensure capacity is not lost...
    Similarly there could be many other considerations which would depend on the actual business reqmts and the flexibility required...
    To answer your question if cumulative lead time is 2 days and SNP/PPDS PPMs are similar 1 week PPDS horizon should be sufficient. PLease remember PPDs horizon includes your planning time fence as well. so your time fence should be less than a week say 2-3 days.
    There is no issue as such with the overlap of the SNP & PPDS horizon. SNP orders in PPDS horizon will be replanned by PPDS. But is there is no specific requrement, you can match the SNP prodn horizon to PPDS horizon, so that PPDS plans inside it and SNP outside it...
    Regards,
    Ashok

Maybe you are looking for