Forecast - basics

What are the steps for best practice Forecasting?
I am not talking of SOP but what are the steps to calculate Forecast based on History of say last 60 periods using say Forecast profiles.
What are the config/ master data setup and transactional data setup.
Any links/ documents will help.
Also, is there a particular info-structure in the S001-S499 range which can be used?
Thnx!
Edited by: Abhi Patra on Feb 18, 2008 10:58 PM

Hi,
Please go through following Link
Click on PDF Index. From the List get Document related to Forecasting.
[http://help.sap.com/printdocu/core/Print46c/en/Data/htm/english.htm]
Regards,
Krishna Mohan

Similar Messages

Forecasting in SOP

hi
I want to know about the calculation in forecasting in SOP
Mean absolute deviation, Ex post Forecast,Basic value , alpha beta factor
How these values r calculated?
Amit

1.SAP - has forecast profile.
inside the forecast profile we have the forecast model
Each mode has it own calcualation..All the belwo mentioned values are used for calcluation in arrriving at the forecasted value at the end of the forecast run
2. i have explained little on the few elements
Basic value:It is used in arrving the first order exponential smoothign value.
These below 2 values help you to calculate the forecast:
alpha :The system uses the alpha factor to smooth the basic value
beta:The system uses the beta factor to smooth the trend value
How these values r calculated?
The below link should help and answer all your questions.
http://help.sap.com/saphelp_47x200/helpdata/en/a5/632f3b43a211d189410000e829fbbd/frameset.htm
Also do get into some statstical sites which will explain you in details
reg
Dsk

Security Filter fails when level has only one member

Hi.
This is Essbase version 9.3. I have a forecast app\db to allow users enter\modify the forecast of the different products. The Product Dimension has the following hierarchy.
All Products
Planner 1
Supplier A
Product_A1
Product_A2Supplier B
Product_B1
Product is the lowest level, level 0, or Gen 4.
I need to allow the "Planner 1" to write only to his products, where the member is "My Scenario" from Scenario Dimension, and where the UDA's for the month is Forecast. The same planner can't write to the "All Products", "Planner" and "Supplier" levels.
I have created the following filter:
None: "All Products"
Read: @IDESCENDANTS("Planner 1")
Write: @REMOVE(@LIST(@DESCENDANTS("Planner 1")),@LIST(@LEVMBRS ("Planner 1", 1))), "My Scenario",@UDA("Time","FORECAST")
Basically, this is the portion most relevant of the filter: @REMOVE(@LIST(@DESCENDANTS("Planner 1")),@LIST(@LEVMBRS ("Planner 1", 1)))
where
@LIST(@DESCENDANTS("Planner 1") = List of descendants members from Planner 1, excluding Planner 1. = "FIRST LIST"
@LIST(@LEVMBRS ("Planner 1", 1)) = List of level 1 members from Product Dimension. = "SECOND LIST"
@REMOVE will remove values or members in the "SECOND LIST" from the "FIRST LIST".
This filter works perfectly but it has a little\big exception...
Based on the example, the filter works fine for Supllier A. Meaning that the user can modifiy the forecast for the products under Supplier A (Product_A1 and Product_A2), and the user can't modify the upper levels, "Supplier A", "Planner 1", "All Products". This is GOOD!
Now. For Supplier B, Essbase will allow write back to the Product_B1, OK. But will also allow write back to Supplier B, the upper level.
So. When the supplier has only one product, Essbase presents this exception that allows write to the upper level. This happens everywhere a supplier has only one product. When there are more than one product per supplier, the filter works as expected.
Is there a missing piece in my filter? Is there a different, better approach to accomplish this?
Thanks.

It's probably an implied share problem. That is, because Supplier B has only one child it is treated as a shared member. You can use the "never share" storage property setting to avoid that problem.

Strategy for dependent requirements.

Hi Experts,
I am working in a MTS scenario,where 'X' is the Header Material & 'Y' its Assembly(with small sub-assemblies inside).
Now 'X' is produced on order as well as some std.ratings forecasted.Basically strategy '40' (Planning with final assembly).
Assembly 'Y' is produced for stock(in anticipation of incomind orders for 'X') as well as sold.
Planning is done basically for 'X' as well as 'Y' in the PIR Planning table.
My question is :Header material 'X' is given strategy '40'.What about 'Y' ? since it is also being sold & kept in stock for 'Y'.
My concern is when i plan individually for 'Y' its dependent requirements should get generated.
So what should be the startegy for 'Y'.
Please advise.
Points assured.
Best Regards
Afroz

Usually in this scenario we use strategy 70 for Y
What is the advantage of 70 is,
You can plan 70 weel in advance, example- let us say you planned 100 TO for Y, Run MRP and start producing Y,
Now let us say there is any dependent requirement from X, let us say 75 TO, then the PIR will be come 100-75 ie 25 TO. Hence you have
PIR = 25 TO
Dep req from X = 75 To
Total requirement still is still 100 TO.
coam back if you need more help

CALC SCRIPT - HELP PLEASE!!! URGENT

I am trying to write a Calc Script for the Outline below -
AP_Related
Trade_AP +
2200 + (Alias – A/P Trade related Party)
2210 + (Alias – A/P Trade I/P)
2215 +
AP_Corporate +
2240 + (Alias – Brazil Fees)
2250 + (Alias – Corporate Chargebacks)
2260 + (Alias – Service Fees)
2270 + (Alias – Fusion Fees)
2280 + (Alias – Tech Fees)
AP_Corp_IP + (UDA – Input_Accs)
I want to put the values in 2240 and 2250 into AP_Corporate and the values of 2260,2270 and 2280 into 2210.
I am trying to add the code to the existing code.
/*Fix on members to copy Actual data to Forecast - */
FIX(&ActMonthEnd,&ForecastYear,"Final",@RELATIVE("Product Groups",0),@RELATIVE("Departments",0),
@RELATIVE("ICP",0),@RELATIVE("TOT_USG",0),@RELATIVE("Accounts",0))
"Actual"(
@CALCMODE(bottomup);
IF(@ISUDA("Accounts","INPUT_ACCS"))
"Basic"->"Forecast"->&ForecastYear=@SUM(@REMOVE(@RELATIVE(@PARENT(@CURRMBR("Accounts")),0),
@REMOVE(@RELATIVE(@PARENT(@CURRMBR("Accounts")),0),
@UDA("Accounts","SUMMED_ACCS"))))-@CURRMBR("Accounts");
     IF(@ISMBR("Tot_I/P_Mat_Costs_Roll Prod_INP"))
          "Basic"->"Forecast"->&ForecastYear->"Tot_I/P_Mat_Costs_Roll Prod_INP"=#Missing;
     ENDIF
     IF(@ISMBR("Metal_Costs_3rd_Party_INP"))
          "Basic"->"Forecast"->&ForecastYear->"Metal_Costs_3rd_Party_INP"=#Missing;
     ENDIF
     ELSEIF(@ISMBR("Oth_Exp_Misc_Inp"))
          "Basic"->"Forecast"->&ForecastYear->"Oth_Exp_Misc_Inp"="40110100"+"40079000"-"30100200";
     ELSEIF(@ISMBR("TOT_ALLOW_INP"))
          "Basic"->"Forecast"->&ForecastYear->"TOT_ALLOW_INP"="12005000"+"12005100";
Edited by: user11300497 on Jun 24, 2009 12:00 PM

Thanks for the response,but the Original script I sent is based on UDA's.I am sending the script and the modified Outline with the UDA's.Any help is greatly appreciated.
The members are from Account dimension.
AP_Related
Trade_AP +
2200 + (Alias – A/P Trade related Party)
2210 + (Alias – A/P Trade I/P)
2215 +
AP_Corporate +
2240 + (Alias – Brazil Fees) (UDA's:Summed_ACS)
2250 + (Alias – Corporate Chargebacks)(UDA's:Summed_ACS)
2260 + (Alias – Service Fees)(UDA's:Summed_ACS)
2270 + (Alias – Fusion Fees)(UDA's:Summed_ACS)
2280 + (Alias – Tech Fees)(UDA's:Summed_ACS)
AP_Corp_IP + (UDA – Input_Accs)
/* Purpose to copy a single month of actuals to the working forecast replacing a month of forecast.
Run monthly to update the current Forecast */
/* Assumptions.
The substitution variables for
ActMonthEnd = Is set to the month containing the Actuals to be copied.
ActualYear = Is set to the year containing the Actuals to be copied.
ForecastYear = Is set to the Current Forecast year value.
ForecastVersion = Is set to the appropiate archive Forecast version.
All input accounts have a UDA of "INPUT_ACCS" and not the UDA "SUMMED_ACCS"
A parent has only one account with the "INPUT_ACCS" UDA amoung its children
All siblings of the "INPUT_ACCS" member that are to be summed into the input account have a UDA of "SUMMED_ACCS"
FIX("LC")
FIX(&ActMonthEnd,&ForecastYear,"Basic",@IDESCENDANTS ("TOT_USG"),
@REMOVE (@IDESCENDANTS("Accounts"),
@LIST(
"30000000",@SHARE("30000000"),
"30003300",@SHARE("30003300"),
"30020400",@SHARE("30020400"),
"30020500",@SHARE("30020500"),
"30010200",@SHARE("30010200"),
"30010400",@SHARE("30010400"),
"41002200",@SHARE("41002200"),
"41002300",@SHARE("41002300"),
"74001000",@SHARE("74001000"),
"41000100",@SHARE("41000100"),
"41001400",@SHARE("41001400"),
"53000000",@SHARE("53000000"),
"59000000",@SHARE("59000000"),
"IP_Ship",@SHARE("IP_Ship"),
"IP Tolling Ship",@SHARE("IP Tolling Ship"),
"IP_NonAlum_Ship",@SHARE("IP_NonAlum_Ship"),
"3rd_Party_Ship",@SHARE("3rd_Party_Ship"),
"3rd party Tolling Ship",@SHARE("3rd party Tolling Ship"),
"Margin - Full",@SHARE("Margin - Full"),
"Margin - Tolling",@SHARE("Margin - Tolling"),
"Discounts - Full - Value",@SHARE("Discounts - Full - Value"),
"Discounts - Tolling - Value",@SHARE("Discounts - Tolling - Value"),
"Base Metal Freight / Logistics - USD",@SHARE("Base Metal Freight / Logistics - USD"),
"Flash Operating EBITDA",@SHARE("Flash Operating EBITDA"),
"Flash Total Book Inventory",@SHARE("Flash Total Book Inventory"),
"BMC / Tonne",@SHARE("BMC / Tonne"),
"IP BMC / Tonne",@SHARE("IP BMC / Tonne"),
"BMC_CPL",@SHARE("BMC_CPL"),
"BMC_Cur",@SHARE("BMC_Cur"),
"BMC_M0",@SHARE("BMC_M0"),
"BMC_M1",@SHARE("BMC_M1"),
"BMC_M2",@SHARE("BMC_M2"),
"BMC_M3",@SHARE("BMC_M3"),
"BMC_PQ",@SHARE("BMC_PQ"),
"CPL Adjustment",@SHARE("CPL Adjustment")
     CLEARDATA "Forecast";
ENDFIX
/* copy in Actual Currency Rates for proper monthly converison
FIX(&ActMonthEnd,&ForecastYear,"EOMRATE","Product_None","Dept_None","ICP_None",
"Entity_None","Rate_EUR_USD","Rate_INR_USD","Rate_GBP_USD","Rate_KRW_USD","Rate_BRL_USD",
"Rate_CHF_USD","Rate_CAD_USD","Rate_MYR_USD","Rate_SEK_USD")
DATACOPY "Actual"->"Final" TO "Forecast"->"Basic";
ENDFIX
/*Fix on members to copy Actual data to Forecast - */
FIX(&ActMonthEnd,&ForecastYear,"Final",@RELATIVE("Product Groups",0),@RELATIVE("Departments",0),
@RELATIVE("ICP",0),@RELATIVE("TOT_USG",0),@RELATIVE("Accounts",0))
"Actual"(
@CALCMODE(bottomup);
IF(@ISUDA("Accounts","INPUT_ACCS"))
"Basic"->"Forecast"->&ForecastYear=@SUM(@REMOVE(@RELATIVE(@PARENT(@CURRMBR("Accounts")),0),
@REMOVE(@RELATIVE(@PARENT(@CURRMBR("Accounts")),0),
@UDA("Accounts","SUMMED_ACCS"))))-@CURRMBR("Accounts");
     IF(@ISMBR("Tot_I/P_Mat_Costs_Roll Prod_INP"))
          "Basic"->"Forecast"->&ForecastYear->"Tot_I/P_Mat_Costs_Roll Prod_INP"=#Missing;
     ENDIF
     IF(@ISMBR("Metal_Costs_3rd_Party_INP"))
          "Basic"->"Forecast"->&ForecastYear->"Metal_Costs_3rd_Party_INP"=#Missing;
     ENDIF
     ELSEIF(@ISMBR("Oth_Exp_Misc_Inp"))
          "Basic"->"Forecast"->&ForecastYear->"Oth_Exp_Misc_Inp"="40110100"+"40079000"-"30100200";
     ELSEIF(@ISMBR("TOT_ALLOW_INP"))
          "Basic"->"Forecast"->&ForecastYear->"TOT_ALLOW_INP"="12005000"+"12005100";
     ELSEIF(@ISMBR("Int_Exp_Third_Oth_INP"))
          "Basic"->"Forecast"->&ForecastYear->"Int_Exp_Third_Oth_INP"="40071200"+"40071300"+"40075530"+"40075540"+"40075550"+"40075570"+"40075580"+"40075590"+"40075610"-"30063200";
     ELSEIF(@ISMBR("Realized_Der_Metal_Inp"))
          "Basic"->"Forecast"->&ForecastYear=@sum(@RELATIVE(@PARENT(@CURRMBR("Accounts")),0))-@CURRMBR("Accounts")-
          (2*("30121240"));
     ELSEIF(@ISMBR("Unrealized_Der_Metal_Inp"))
          "Basic"->"Forecast"->&ForecastYear=@sum(@RELATIVE(@PARENT(@CURRMBR("Accounts")),0))-@CURRMBR("Accounts")-
          (2*("30131240"));
     ELSEIF(@ISMBR("TOT_EMP_INP"))
"Basic"->"Forecast"->&ForecastYear=@SUM(@UDA("Accounts","EMP_ACCS"));

Milestones

My Client Requires the follwoing:
- Requires to plan Milestones on WBS elements. These Milestones are going to contain dates. Actuals must have already start being captured on this WBS, if not a message must notify the user that no actuals have been captured on this date as of yet.
How do I go about setting this up?

Johnny123 wrote:
As I understand, my client wants to put in a Forecast/Basic date in the milestone, if this date is reached without any actuals being captured on this WBS he should be notified. Also These are Capital Projects without Network and activities. Only WBS's.
>
> How would you go about setting this up? regarding the Milestone, actuals and notifications
>
> Thanks
Create Z program which should check the basic dates and also the actual dates, and also send a mail to the applicant in the WBSE as you required.. Use applicant filed to maintain the person to whom the mail to be send.
also schedule this Z program in the back ground to run every day.

Copying basic dates to forecast dates

Hi Experts,
I am using WBSE and activities in my project. I want to copy basic dates to forecast dates. But, when i am doing this in Edit>Reconcile date->Transfer basic dates to forecast dates. Then my Planning type in network header also gets change from Basic date to forecast date. which i don't want. I just want that my basic dates get copied to forecast dates , so that i can use forecast dates as my planed dates through the project and never change it. So, that i can always compare , basic dates, forecast dates and actual dates.
Thanks.

May be you can try the following....
1) Edit>Reconcile date->Transfer basic dates to forecast dates.
2) manually change Planning type in network header from forecast date to Basic date.

Planning method/Basic and Planning method/forecast field values are grey

Hi Experts
The Planning method/Basic and Planning method/forecast field values are grey in my project profile.
What customization would influence for this setting. I wish to change from 2 to 4. Please advise the solution/
warm regards
ramSiva

You can change the above field values only from WBS scheduling profile. If you want to change them, choose 'free scheduling' method.
Regards,
Mahendra

Forecast dates instead for Basic dates in ECP

Hello all,
We want to use the forecast dates in the project instead for basic dates in easy cost planning, is that possible to do?
In standard, ECP take the basic dates but it will be very usefull to use forecast dates in different CO-version as a forcast planning.
Do not hesitate to contact me,
Best regards
Jose Marin

Hi Abhra,
You can check both basic and forcast dates WBS Elements in project planning Board at a time.
as you said, you have to select both Basic and Forecast dates options in Set of Dates Icon. Before that while scheduling the entire project system will consider either Basic or Forecast dates at WBS Level and Carried out scheduling.
If you did Scheduling with Basic Dates then you have to transfer Basic dates to Forecast dates in Planning Board through Edit --> Reconsile dates --> copy basic dates to forecast dates.
if both Basic and Forecast dates are planning at WBS level, system shows you the Time Bars in different colour which you can check the corresponding colour matches with the specific dates through Legend.
Hope you can understand the above solution..
Regards,
Hari krishna.k

Authorization for Basic dates and Forecast dates

Hello colleagues,
My customer requires is to have separate authorizations for using Basic dates and Forecast dates within WBS Element, Network and Milestone.
Iv'e noticed that the rellevant autorization object to have this separation is C_PROJ_TCD ; field: PSARG ; activity: 111 & 112. However I wonder if this is relevant to all related objects in the project or only to the Project definition object.
If the answer is only to PD I will be glad to have an idea how to controll it within the other objects .
Thanks in advance
Best Regards,
Nir
Edited by: Nir Horvitz on Nov 23, 2010 10:32 AM
Edited by: Nir Horvitz on Nov 23, 2010 10:41 AM

It is for all the objects... but you can not control it on basis of only that auth object.
For network,
use object :
C_AFKO_ACT
and activity 22 Display dates
for Project def and WBS, use
C_PROJ_KOK, C_PROJ_PRC, C_PROJ_VNR
C_PRPS_KOK, C_PRPR_PRC, C_PRPS_VNR
Regards,
Amol Sarode

Difference between actual ,basic and forecast dates

hi,
wat is the difference between actual start date,basic start date and forecasted start date

Ady,
Can you give a little more info than this?
Regards
Gill

Basic Settings for Stastical Forecasting

Hi Guys,
Could you please provide the basic settings for Statistical forecasting.....
Regards,
Pullaiah.

Hi Pullaiah,
If you are doing stastical forecasting you have to do following setting,
1. if you are running forecast engine at aggregated level then while creating planning area, you should define calculation type "p" for forecast key figure (For disaggregating forecast key figure at detail level)
2.Check the forecastong box while design the planning book in initial tab page.
3.Create forecast profile under the resopective planning area(/SAPAPO/MC96B).
This is the basic setting you have to do before running forecast engine..
Hope this will help you
Regards
Sujay

Automate 'transfer of basic dates to forecast dates'

Hi Experts
I wish to have automatic transfer of Basic dates to FRC at the time of changing the status of Project definition to REL.
So that, after release i will prohibit the transfer of basic to FRC. This is required to retain original scheduled dates in FRC.
So, is there any userexit to build code for trigger transaction 'transfer basic to FRC' at the time of status change of PD?
Or you may suggest any new idea in this regards
Thanks and warm regards
ramSiva

Hi,
I am not sure if there is a standard way to do this, if anyone knows it please share your knowledge,
There are several ways to obtain this , but all of them envolve development :
- You can use this BADI ( if you are at least in 4.6 C) --> WORKBREAKDOWN_UPDATE ( method AT_SAVE)
- You can create an event for object BUS2001 when it is released and the you have to program to copy from one date to another date
- If possible you can use standard substitution (OPSN transaction) but you have to develop your requirement.
I am not sure it is very clear...
sara

APO basic ATP & Forecast

Hi All,
Kindly help,
I config Basic ATP agaisnt ATP check.
Now Issue is my newly created sales order is not getting confirmed in APO.Although it shows stock & recipts.
Regards
V4B

V4B,
You say that the ATP screen shows 'nothing'. That means that none of the items that you see in RRP3 (or in MD04 on the R/3 side) are being considered for ATP check, and therefore you will get no confirmation. On the ATP screen, the column entitled ATP quantity should show a quantity, and the quantity should be equal to or greater than the Simulated requirements quantity, on the date of the Simulated requirement. On this screen, you should have at least one row for 'stock' and at least one row which contains valid supply elements. Since you have 'nothing', your stock & supply elements are not being considered.
You also mention that you have stocks and receipts, and they show as onhand in //RRP3. According to your ATP check, the only items that will be relevant for ATP are 'Valuated, Unrestricted Use stock' and 'advanced shipping notification'. You have further stated that these are the items that exist in //RRP3. Please confirm. On //RRP3, the stock should display the 'CC', which is the only type of stock mentioned in your 'Scope of check'. You should also have one or more 'PO Memos'.
On the scope of check screen, you should at least have BM Sales orders selected as a requirements element. Please confirm.
I will assume that you are not using sublocations (storage locations in R/3) in your ATP check (scope of check screen). Please confirm. If you are using sublocations, all supply elements must be relevant for the same sublocation as the simulated requirement.
Finally, double check to make sure that the info you are viewing in /RRP3 is for the same product/location that you are using in your R/3 ATP check.
Best Regards,
DB49

Basics about the forecast key figure

Hello
There are lot of Key figures in use -
Statistical Forecast
Ex-Post forecast
Corrected forecast
Adjusted Sales history
Any idea what each stand for ?
Thank you in advance
KK

Hi
Statistical Forecast : This is system generated FCST based on FCST Technique used
Ex-Post forecast: Ex-Post Forecast is just calculating the forecast in the history horizon .This is calculated through the forecasting technique adopted by you .
Corrected forecast : After system has created Stat FCST, we can manipulate as per our requirement and this is called as correct FCST.
Adjusted Sales history :- It regarding the clearing the sales history, In case of some business extreme condition we have some peaks and down in sales history. We require to correct them , to get appropriate Statistical Forecast. This corrected sales history which is also called as adjusted sales history get used for Forecasting.
Thanks
Amol

Forecast - basics

Similar Messages

Maybe you are looking for