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

Similar Messages

  • Forecast of SOP at background

    Hi,
    I am working with forecast of SOP at background, for that activity I have created variant.
    Here we are getting an error
    Product group/material is not allowed as an aggregation level
    For a Product group, if I have used other product group then its work. I have need requirement for that product group.
    Pl helps me for finding the solution.

    Hi,
    In your case you must be having as below:
    First level: Product group -- A
    Second level: Production group -- B
    Third level: Material
    You must be trying directly for PG A, which is first level PG>
    But, SAP does not allow the top level PG to be disaggregated. Disaggregation is only allowed if the members of a PG are materials, and not some other product group.
    In such a case, you first need to disaggregate from first level PG to second level PG -- from A to B and then carry out further activities for PG b, which is the lowest level PG.
    I hope this is helpful.
    Revert in case of problem.
    Shrenik

  • Forecast without SOP

    Dear Expert,
    Our requirement is that we have no SOP function, but we need the forecast for running MRP generate purchase proposal. how to do?
    regards
    Nathan

    Hi ,
    Maintain the forecast view of the materials & the relevent settings... Then execute material forecast from transaction MP38. Take a MRP run..the forecast requirement will be reflected as unplanned requirement & planned orders will be created accordingly.
    Thanks
    Mahesh

  • Material Forecast VS SOP Forecast

    Hi,
    Could anyone please explan to me what is the difference between the mtl forecast and the SOP forecast ? I have read the documentation a few times and still have not bee able to figure out what the difference is. Do we need to use both at the same time ? Do the forecasted values in the material master equate to the forecasted values you see in the SOP planning table ? Are these two interchangable ? I would really appreciate it if someone could explain this to me.
    Thanks

    Dear,
    It depends on the parameters used. First let you be clear that do you want to do it through SOP or Matrial master, then go ahead with that. It may be same or diffeent depends on the parameters used.
    If you do it in forecast in material master usually we use it for ra material where we use consumption based planning with VV.
    If you do sales forecast it is used for product and we are doing with a planning stg where we control the consumption.
    In SOP, we can control what to consider as consumotion or whether to take last year slaes...
    In material master it is just a consumption.
    Hence be  clear what is required for you and proceed

  • In SOP- transfer forecasted values from material master to info structure?

    Hi All,
    I wanted to test out a few scenarios. Do you know the answers  / can you help simulate and check the below?
    1.     If I run the forecast using different models for different materials using the total forecast run (MP38), the forecast values will get updated in the material master. Can I get these values transferred directly into the SOP (standard or flexible), without re-running the forecast in SOP? What I am looking at is a possible scenario where individual materials have different forecast model, so do not want to run forecast from SOP using one model for all.
    2.       Can you have the capability of selecting diff model (say based on material master data) in SOP for diff materials? When I ran SOP, the model I specify there for forecasting is applied for all materials
    3.       If I upload historical values/forecasted values in the material master, can I directly transfer them to SOP without any change to the value?
    Appreaciate your inputs.

    Hi All,
    I wanted to test out a few scenarios. Do you know the answers  / can you help simulate and check the below?
    1.     If I run the forecast using different models for different materials using the total forecast run (MP38), the forecast values will get updated in the material master. Can I get these values transferred directly into the SOP (standard or flexible), without re-running the forecast in SOP? What I am looking at is a possible scenario where individual materials have different forecast model, so do not want to run forecast from SOP using one model for all.
    2.       Can you have the capability of selecting diff model (say based on material master data) in SOP for diff materials? When I ran SOP, the model I specify there for forecasting is applied for all materials
    3.       If I upload historical values/forecasted values in the material master, can I directly transfer them to SOP without any change to the value?
    Appreciate your inputs.

  • SOP- Sales forecast in $ value

    Hello,
    Is it possible to enter a sale forecast is SOP or Flexible SOP in $ value of forecast sales, instead of at Quantity in "PCS". For example, we want to forecast for 6 months the sales of a product family. Is it possible in SOP or it must be done with CO/PA?
    Regards,
    Edited by: Boaz Weinstock on Jun 30, 2008 4:37 PM

    In the flexible planning, you should choose right planning type which has layout of sales value instead quantity.
    Planning type is linked to a planning table.
    Forecast comesup from history, CO/PA is used only for the cost benefit analysis.
    Thanks,
    Srinivas Karri

  • Preparing Forecast in SAP R/3

    Hi Gurus,
    Good Morning.
    I am trying to prepare a Forecast Plan for next 6 months based on the Sales History for Past 13 weeks.  The solution which i was thinking of is to prepare a Custom Sales Forecast report in SAP with the Sales History over the 13 weeks as the basis for the calculation , spread it out in monthly buckets and then upload it to the Planned Independent requirement table (MD61)
    If at all if i dont use the above option , In the system if i extend the forecast view then we can  plan the Total Consumption over there , ther total Consumption does looks for all the Sales Order over that particular period? and also how can i get the data in the the forecasting to be transferred to the Planned Independent requirement table ? It would be great if you are able to provide some Configuration/Setup details.
    Thanks in Advance..
    Thanks
    Balaji

    Balaji,
    It appears you are asking about R/3 forecasting, and not APO.  You don't have to write a custom report, SAP standard functionality provides your requirement.
    Standard methods in R/3 to arrive at Planned independent Requirements through a forecast are Material Forecasting (which creates forecasts based on historical consumption) and Sales and Operations Planning (which can forecast based on anything you design).
    Simplest to implement is material forecasting.  For most companies, FGs consumption data is more than adequate to provide realistic forecasts.
    Once your forecast is done, using either Material forecasting or SOP, it can automatically be converted to Planned Independent requirements.
    Material forecasting
    http://help.sap.com/erp2005_ehp_04/helpdata/EN/7d/c27278454011d182b40000e829fbfe/frameset.htm
    SOP
    http://help.sap.com/erp2005_ehp_04/helpdata/EN/a5/63201843a211d189410000e829fbbd/frameset.htm
    Creating PIRs
    http://help.sap.com/erp2005_ehp_04/helpdata/EN/cb/7f949443b711d189410000e829fbbd/frameset.htm
    Rgds,
    DB49

  • Sales Planning & Forecasting

    Dear Friends,
         We have negative stocks allowed for the materials.
         Pl tell me, whether we can configure Sales Planning & Forecasting and SOP.
    Thanks,
    Sreehari.
    Edited by: Sreehari Kondapalli on Jun 15, 2009 3:40 PM
    Edited by: Sreehari Kondapalli on Jun 16, 2009 10:57 AM

    Hi,
    You can get all the best practice documents over here.
    http://help.sap.com/bp_crmv250/CRM_DE/index.htm
    Click on Technical Information -> Building Block Library.
    Regards,
    Deepak
    Edited by: Deepak Ahuja on Jun 9, 2008 5:11 PM

  • SOP for Material and Customer

    Hi Gurus,
    is it possible to have a Forecast in SOP in which I have different customer using the same part number? Scenario is this customer gives separate forecast for this material. I need to consolidate this forecast and load to Demand Management.
    For example below:
    Customer       Forecast     Material
    Customer 1       200          Mat1
    Customer 2       300          Mat1
    Customer 3       250          Mat1
    I want to load the forecast by customer and transfer it in Demand management as a whole or separately will do. Is it possible to manipulate this data using SOP? may i know how?
    I only know the per material loading of forecast.
    Thanks,
    Raymond

    Hi,
    Your scnario can be achievd by Flexible Planning.
    You have to create InfoStructure where the Customers is a Characteristic Value.
    Please find the TCode to configure Flexible Planning as Follows:
    1. MC21: Create Info Structure
    2. MC7F: Planning Parameter
    3. MC61: Create Planning Hierrachy
    4. MC9B: Calculate Proportion
    5. MC8A: Create Planning Type
    6: MC93: Create Plan in Flexible Planning
    7. MC90: Transfer to Demand Management
    8. MD02: MRP Run.
    Regards
    Vinod

  • SOP-Change base unit to value???

    Hello,
    Is it possible to enter a sale forecast is SOP or Flexible SOP in $ value of forecast sales, instead of at Quantity in "PCS". For example, we want to forecast for 6 months the sales of a product family. Is it possible in SOP or it must be done with CO/PA?
    Regards,
    Dwi

    In the flexible planning, you should choose right planning type which has layout of sales value instead quantity.
    Planning type is linked to a planning table.
    Forecast comesup from history, CO/PA is used only for the cost benefit analysis.
    Thanks,
    Srinivas Karri

  • Characteristic Based Planning in SOP - R/3

    Hi Experts,
    I would like to plan my material variants (stockable items of my configurable products) using Sales & Operations Planning. To that end, I wanted to know, if there is a functionality available in the R/3 SOP system, with which I

    Hello
    If you don't want to use forecast based planning, the only alternative is to make the forecast in SOP.
    After making the forcast on SOP, the values are transfered to demand management and then MRP is used to generate planned orders.
    Take a look on the following link for more details:
    Planning Table: the Forecast - Sales & Operations Planning (LO-LIS-PLN) - SAP Library
    How to Run the Forecast with Mass Processing - Sales & Operations Planning (LO-LIS-PLN) - SAP Library
    How to Transfer Data to Demand Management with Mas - Sales & Operations Planning (LO-LIS-PLN) - SAP Library
    BR
    CAetano

  • Spec for this report not able to get values in the output

    okSection 1: Document information
    Title     PP – Total Component Requirement by Sales Forecast Report     Create Date     5/2/2006
    Author     Ivie Ng     Revision     1.0     Last changed on     
    Program type     ( X ) Report    (   ) Form        (   ) Batch input    (   ) Dialog program
    Priority     (   ) High       ( X ) Medium    (   ) Low
    Frequency      (   ) As require     (X ) Daily     (  ) Weekly       (  ) Monthly         (  ) Yearly
    (   ) Conversion
    Doc-Ref.     
    Section 2: Contact Person
    Task/Responsibility     Name     Signature     Date
    JM Project Manager     Sean Gilgunn          
    ISS Project Manager     YB Cisse          
    JM-Business Team Lead     Sathe          
    Functional Consultant      Ivie          
    ABAP Consultant     Soh          
    User Acceptance Test / Approved by                
    Transport               
    Section 3: Functional Description
    Background (whatever; Ex.Why does this program have to develop?)
    This is to allow materials dept to view and analyze total component requirement base on sales forecast ie. budget forecast, inactive version within specific planning horizon.
    Requirements
    In SOP, material dept will maintain planning data (sales & production plan) in various version.
    1. Active version: A00
    This version is transferred to demand mgmt as active version. MRP will use this planning data to create order proposals (planned orders, purchase requisitions).
    2. Inactive version: 001 – 999
    There are 3 types of inactive version in SOP:
    a) Sales forecast – 000 – 799
    b) Budge forecast – 800 – 820
    c) Forecast report – 821 – 999
    This report should allow to read any version of the sales forecast and return the total component requirements in the planning horizon that specify.
    Section 3.1: Selection screen
    Field name     Technical name     Type of selection field
         (*Please specify Transparent Table and field name)     (X) Single value             (  ) Range             ( ) Required field
              (  ) Single value             (X) Range             (  ) Required field
              (X) Single value             (  ) Range             (  ) Required field
    Section 3.2: Program Logic
    Business Requirement
    This report will allow option to choose to read the source from SOP or COPA.
    Input Selection
    Main Menu:
    o     Total Component Requirement from SOP forecast
    o     Total Component Requirement from COPA forecast
    If SOP is selected, Source = SOP
    If COPA is selected, Source = COPA
    Option 1: SOP
    1.     Input Layout
    Material: _____________    (note: allow multiple materials entry, no entry indicate all materials)
    RM Material Group: __________     (note: allow multiple entry, no entry indicate all Mat Grp)
    Plant:  MY11  (note: default value)
    Standard Price as of : _____________  (YYYYMM)
    Version: ________    (note: allow F4 option with Version and Description)
    Output Type: ____  (Month/Year)
    (If the output type chosen is Month, the below is display)
    Period From:  _________  (YYYYMM)
    Period To:      _________  (YYYYMM)
    (If the output type chosen is Year, the below is display)
    Period From:  __________ (YYYY)
    Period To:      __________ (YYYY)
    2.     Output Layout
    Plant: MY11
    Source:
    Version:
    System Date/Time:
    Output Layout in Month:
    Material     Desc     Component     Desc     UOM     M04.2006     M05.2006     M06.2006     M07.2006     M08.2006     M09.2006     BOM
    TO2368          NGK0003          PC                                   TO2368
              SIN96-015          MG                                   TO2368
              SIN96-066F          MG                                   TO2368
              SIN96-066N          MG                                   TO2368
              SIN96-127          GCL                                   WCS2004
              SIN96-055          G                                   WCS2004
              SIN96-110          G                                   WCS2004
              SIN96-007          G                                   WCS2004
              SIN96-002          GCL                                   WCS1003
              SIN96-001          GCL                                   WCS1003
              SIN96-006          GCL                                   WCS1003
              TO2358/511          PC                                   TO2368
              TO2358/512          PC                                   TO2368
              WCS2004          GCL                                   TO2368
              WCS1003          GCL                                   WCS2004
    Output Layout in Year:
    Material     Desc     Component     Desc     UOM     2006     2007     2008     BOM
    TO2368          NGK0003          PC                    TO2368
              SIN96-015          MG                    TO2368
              SIN96-066F          MG                    TO2368
              SIN96-066N          MG                    TO2368
              SIN96-127          GCL                    WCS2004
              SIN96-055          G                    WCS2004
              SIN96-110          G                    WCS2004
              SIN96-007          G                    WCS2004
              SIN96-002          GCL                    WCS1003
              SIN96-001          GCL                    WCS1003
              SIN96-006          GCL                    WCS1003
              TO2358/511          PC                    TO2368
              TO2358/512          PC                    TO2368
              WCS2004          GCL                    TO2368
              WCS1003          GCL                    WCS2004
    3.     Header Section:
    Header Field: Plant
    Print input field Plant.
    Header Field: Source
    If SOP is selected, Source = SOP
    If COPA is selected, Source = COPA
    Print Source.
    Header Field: Version
    Print input field Version, Print RMCP2-VETXT (version description).
    Header Field: System Date/Time
    Print current system date and time.
    4.     Table: S076 (SOP - Sales & Operations Planning)
    Read S076 rows with input selection of Material, Plant, Year, Month, Version sorted by Material.
          This table provides sales forecast figure.
    Table: MAKT – Material Decription
    Table: MARA - General Material Data
    Table: CDHDR - Change document header
    Table: CDPOS - Change document items
    5.     Details Section: -
    Read S076.PMNUX(Material).                    Note: There will be multiple rows in S076.PMNUX (Material)
    Field: Material
    Print S076.PMNUX(Material).
    Field: Description
    Read MAKT.MATNR(Material), Print MAKT.MAKTX.
    6.     Read L1 (Level 1) BOM Transaction: CS03
                   Where Material = S076.PMNUX (Material), Plant = MY11 (input field), BOM Usage = ’1’, Status = ‘01’
    7.     This is to print BOM component.
    If Input Material Group = ‘ ’
    Read Component (Material), Component Qty from BOM sorted by MARA.MTART (material type) = ‘ZROH’, ‘ZHLB’ , ‘ZRUH’
    If Input Material Group <> ‘ ’
    Read Component (Material), Component Qty from BOM sorted by MARA.MTART (material type) = ‘ZROH’, ‘ZHLB’ , ‘ZRUH’
          Where MARA-MATKL (Material Group) = Input Material Group.
    If MARA.MTART (material type) = ‘ZRUH’,
          Read L1 (Level 1) BOM Transaction: CS03
                  Where Material = S076.PMNUX, Plant = MY11 (input field), BOM Usage = ’1’, Status = ‘02’.
    GET RC29K-BMENG (Base Qty)  ***
    Field: Material Group
    Print MARA-MATKL
    Field: Component
    Print BOM Component.
    Field: Description
    Print MAKT.MAKTX.
    Field: UOM
    Print MARA.MEINS.
    Field: Currency
    Field: Standard Price
    If Input Standard Price Date = ‘’
       Print Currency = ‘ ‘
       Print Standard Price = 0
    Else
    Read CDHDR-OBJECTID (Material), CDHDR-CHANGENR (ChgNo)
    Where CDHDR-OBJECTID (Material) = BOM Component
    And CDHDR-TCODE (Transaction) = ‘MR21’
    And YYYYMM[CDHDR-UDATE (Date)] = Input Standard Price Date
    If NOT Found, look up YYYYMM[CDHDR-UDATE (Date)] – 1  
    I.e.    Input Standard Price Date is 200702, If CDHDR-UDATE (Date) Not Found, look up 200701.
    If Not Found, look up 200612 until the record is found    **
    If row return > 1, select the latest CDHDR-UDATE (Date)
    i.e. If rows return 20070201 and 20070215, Select 20070215    **
    Read CDPOS-CUKY_NEW (Currency), CDPOS-VALUE_NEW (New Value)
    Where CDPOS-OBJECTID (Material) = CDHDR-OBJECTID (Material)
    And CDPOS-CHANGENR (ChgNo) = CDHDR-CHANGENR (ChgNo)
    Print CDPOS-CUKY_NEW (Currency)
    Print CDPOS-VALUE_NEW (New Value)
    8.     If the output type is Year, print Requirement Qty in Yearly bucket.
    Requirement Qty = sum[S076-ABSAT (Sales) for current Year] ie 2006
    Requirement Qty = sum[S076-ABSAT (Sales) for current Year + 1] ie 2007
    Requirement Qty = sum[S076-ABSAT (Sales) for current Year + 2] ie 2008
         If the output type is Month, print Requirement Qty in Monthly bucket.
    Field: Month (ie. M04.2006)
    Requirement Qty = S076-ABSAT (Sales) * Component Qty / RC29K-BMENG (Base Q)
    Print Requirement Qty.
    Field: Total Price (ie. M04.2006)
    Total Price = Requirement Qty * Standard Price
    Print Total Price
    Field: Month (ie. M05.2006)
    Requirement Qty = S076-ABSAT (Sales) * Component Qty / RC29K-BMENG (Base Q)
    Print Requirement Qty.
    Field: Total Price (ie. M05.2006)
    Total Price = Requirement Qty * Standard Price
    Print Total Price
    Field: Month (ie. M06.2006)
    Requirement Qty = S076-ABSAT (Sales) * Component Qty / RC29K-BMENG (Base Q)
    Print Requirement Qty.
    Field: Total Price (ie. M06.2006)
    Total Price = Requirement Qty * Standard Price
    Print Total Price
    Field: Month (ie. M07.2006)
    Requirement Qty = S076-ABSAT (Sales) * Component Qty / RC29K-BMENG (Base Q)
    Print Requirement Qty.
    Field: Total Price (ie. M07.2006)
    Total Price = Requirement Qty * Standard Price
    Print Total Price
    Field: Month (ie. M08.2006)
    Requirement Qty = S076-ABSAT (Sales) * Component Qty / RC29K-BMENG (Base Q)
    Print Requirement Qty.
    Field: Total Price (ie. M08.2006)
    Total Price = Requirement Qty * Standard Price
    Print Total Price
    Note: Repeat the requirement qty display in Monthly bucket base on period specified.
    Field: BOM
    Print L1 BOM which is S076.PMNUX (Material)  from Step 6.
    If Is end of component,
          Repeat Step 5 for next Material in SOP (S076.PMNUX).
    If MARA.MTART (material type) = ‘ZROH’,
    Perform Step 7 to read next L1 BOM Component.
    Perform Step 8 to print Requirement Qty.
    If [MARA.MTART (material type) = ‘ZHLB’] and [MARA.MATKL(material group) = ‘WP0100’, ‘WP0110’, or ‘WP0120’],
          Go Step 9 to read L2 BOM.
    If [MARA.MTART (material type) = ‘ZHLB’] and [MARA.MATKL (material group) <> ‘WP0100’, ‘WP0110’, ‘WP0120’],
          Perform Step 7 to read next BOM Component.
          Perform Step 8 to print Requirement Qty.
    9.     Read L2 (level 2) BOM for the ZHLB at Transaction: CS03
                Where Plant = MY11(input field), BOM Usage= ’1’, Status = ‘01’.
    GET RC29K-BMENG (Base Qty)  ***
    10.     Read Component (Material), Component Qty from BOM sorted by MARA.MTART (material type) = ‘ZROH’, ‘ZHLB’.
    Field: Material Group
    Print MARA-MATKL
    Field: Component
    Print BOM Component.
    Field: Description
    Print MAKT.MAKTX.
    Field: UOM
    Print MARA.MEINS.
    Field: Month (ie. M04.2006)
    Requirement Qty = Requirement Qty from L1 BOM  * Component Qty / RC29K-BMENG (Base Q)
    Print Requirement Qty.
    Field: Total Price (ie. M04.2006)
    Total Price = Requirement Qty * Standard Price
    Print Total Price
    Field: Month (ie. M05.2006)
    Requirement Qty = Requirement Qty from L1 BOM * Component Qty / / RC29K-BMENG (Base Q)
          Print Requirement Qty.
    Field: Total Price (ie. M05.2006)
    Total Price = Requirement Qty * Standard Price
    Print Total Price
          Note: Repeat until end of Period.
    Field: BOM
    Print L2 BOM from Step 9.
    If is end of component, perform Step 7 to read next L1 BOM component, and Step 8 to print Requirement Qty.
    If MARA.MTART (material type) = ‘ZROH’,
    Perform Step 10 to read next L2 BOM Component.
    If MARA.MTART (material type) = ‘ZHLB’ and MARA.MATKL(material group) = ‘WP0100’, ‘WP0110’, or ‘WP0120’,
          Go Step 11 to read L3 BOM.
    If [MARA.MTART (material type) = ‘ZHLB’] and [MARA.MATKL (material group) <> ‘WP0100’, ‘WP0110’, ‘WP0120’],
          Perform Step 10 to read next L2 BOM Component.
    11.     Read L3 (level 3) BOM for the ZHLB at Transaction: CS03 where Plant=MY11(input field), BOM Usage=’1’, Status =‘01’.
    12.     Read Component (Material), Component Qty from BOM sorted by MARA.MTART (material type) = ‘ZROH’, ‘ZHLB’.
    Field: Material Group
    Print MARA-MATKL
    Field: Component
    Print BOM Component.
    Field: Description
    Print MAKT.MAKTX.
    Field: UOM
    Print MARA.MEINS.
    Field: Currency
    Field: Standard Price
    Read CDHDR-OBJECTID (Material), CDHDR-CHANGENR (ChgNo)
    Where CDHDR-OBJECTID (Material) = BOM Component
    And CDHDR-TCODE (Transaction) = ‘MR21’
    And YYYYMM[CDHDR-UDATE (Date)] = Input Standard Price Date
    If NOT Found, look up YYYYMM[CDHDR-UDATE (Date)] – 1  
    I.e.    Input Standard Price Date is 200702, If CDHDR-UDATE (Date) Not Found, look up 200701.
    If Not Found, look up 200612 until the record is found    **
    If row return > 1, select the latest CDHDR-UDATE (Date)
    i.e. If rows return 20070201 and 20070215, Select 20070215    **
    Read CDPOS-CUKY_NEW (Currency), CDPOS-VALUE_NEW (New Value)
    Where CDPOS-OBJECTID (Material) = CDHDR-OBJECTID (Material)
    And CDPOS-CHANGENR (ChgNo) = CDHDR-CHANGENR (ChgNo)
    Print CDPOS-CUKY_NEW (Currency)
    Print CDPOS-VALUE_NEW (New Value)
    Field: Month (ie. M04.2006)
    Requirement Qty = Requirement Qty from L2 BOM  * Component Qty / RC29K-BMENG (Base Q)
    Print Requirement Qty.
    Field: Total Price (ie. M04.2006)
    Total Price = Requirement Qty * Standard Price
    Print Total Price
    Field: Month (ie. M05.2006)
    Requirement Qty = Requirement Qty from L2 BOM * Component Qty / RC29K-BMENG (Base Q)
          Print Requirement Qty.
    Field: Total Price (ie. M05.2006)
    Total Price = Requirement Qty * Standard Price
    Print Total Price
          Note: Repeat until end of Period.
    Field: BOM
    Print L3 BOM from Step 11.
    If is end of component,
          Perform Step 10 to read next L2 BOM Component.
    If MARA.MTART (material type) = ‘ZROH’,
    Perform Step 12 to read next L3 BOM Component.
    If MARA.MTART (material type) = ‘ZHLB’ and MARA.MATKL(material group) = ‘WP0100’, ‘WP0110’, or ‘WP0120’,
          Repeat for next level of BOM reading.      ** for future BOM expansion **
    If [MARA.MTART (material type) = ‘ZHLB’] and [MARA.MATKL (material group) <> ‘WP0100’, ‘WP0110’, ‘WP0120’],
          Perform Step 12 to read next L3 BOM Component.
    13.     The report is ALV format and should allow to export to Excel. See example below:
    Option 2: COPA
    1.     Input Layout
    Company Code:  ________ 
    Plant:  MY11   
    Material: _____________    (note: allow multiple materials entry, no entry indicate all materials)
    Material Group: __________     (note: allow multiple materials entry, no entry indicate all materials)
    Standard Price as of : _____________  (YYYYMM)
    Version: ________    (note: allow F4 option with Version and Description)
    Read  V_TKEVS_CL-VERSI (Version),  V_TKEVS_CL-VTEXT (Version Description)
    Output Type: ____  (Month/Year)
    (If the output type chosen is Month, the below is display)
    Period From:  _________  (YYYYMM)
    Period To:      _________  (YYYYMM)
    (If the output type chosen is Year, the below is display)
    Period From:  __________ (YYYY)
    Period To:      __________ (YYYY)
    2.     Header Section:
    Header Field: Plant
    Print input field Plant.
    Header Field: Source
    If SOP is selected, Source = SOP
    If COPA is selected, Source = COPA
    Print Source.
    Header Field: Version
    Print V_TKEVS_CL-VERSI (Version),  V_TKEVS_CL-VTEXT (Version Description)
    Header Field: System Date/Time
    Print current system date and time.
    3.     Report details: -
    Table: CE2ASIA - JM Operating Concern
    If input selection is Monthly Report:-
    Read CE2ASIA-ARTNR (Product No), Sum[CE2ASIA-ABSMG001 (Sales Qty)]
    Where CE2ASIA-BUKRS (Company Code) = Input Company Code
    And CE2ASIA-WERKS (Plant) = Input Plant
    And CE2ASIA-PALEDGER (Currency Type) = ‘10’
    And [CE2ASIA-PERBL (FI Period) > = Input Period From And CE2ASIA-PERBL (FI Period) < = Input Period To]
    Group by CE2ASIA-ARTNR (Product No)
    If input selection is Yearly Report:-
    Read CE2ASIA-ARTNR (Product No), CE2ASIA-ABSMG001 (Sales Qty)
    Where CE2ASIA-BUKRS (Company Code) = Input Company Code
    And CE2ASIA-WERKS (Plant) = Input Plant
    And CE2ASIA-PALEDGER (Currency Type) = ‘10’
    And [YYYY[CE2ASIA-PERBL (FI Period)] > = Input Period From And CE2ASIA-PERBL (FI Period) < = Input Period To]
    Note: The details similar to Option 1: SOP, refer section (5)  to (13)
    Section 3.3: Report Layout
    Field name     Technical name     Comment
         (Please specify Transparent Table and field name)     (Ex. In case field does not read directly from transparent table but derive from formular or sum or else. Please show the detail how to do that.)
    Section 3.3: Unit Test Criteria
    Section 4: Technical Description
    Section 4.1: Object information
    Development class     
    Transport number     
    Section 4.2: Input/output file layout (In case upload/download file)
    *Please determine structure of  file like as below:
    No.     Field description     Type (Char,Numeric,…)     Length     Note
    Section 4.3: Report/Form information
    Paper size     Inch 11 8” X 11”     Type of printer     ( ) Laser printer     (X) Dot matrix
    Output report / Pre-printed Attach
    Technical Issue

    Hi gurus,actually this program selecion screen is linked to ..as
    First screen is .Sop
                          .copa
    Again for sop is having a selection screen and in this it is divide based on month and year seperately in two more screens.
    same for copa also....
    so pls tell me a correct solution where to correct and get values.
    Priority is very highhhhhhhhhhhhhh,so pls help me in sorting out this.

  • Planning in SAP R/3

    Hi,
    I have a requirement like this....
    For a product they want to take previous months sales data say for last 12 months... when we put this data upon execution system needs to propose the next future forecast data say for next 24 months after making some calculations ( ex. making average ) .... I know this can be done in APO... but client do not want to use APO and want this in ECC R/3
    Is this can be achieved in ECC R/3 ?. Problem here is they do not want to use forecast based planning also......is there any way this can be done in SOP
    Thanks
    Vinamrath

    Hello
    If you don't want to use forecast based planning, the only alternative is to make the forecast in SOP.
    After making the forcast on SOP, the values are transfered to demand management and then MRP is used to generate planned orders.
    Take a look on the following link for more details:
    Planning Table: the Forecast - Sales &amp;amp; Operations Planning (LO-LIS-PLN) - SAP Library
    How to Run the Forecast with Mass Processing - Sales &amp;amp; Operations Planning (LO-LIS-PLN) - SAP Library
    How to Transfer Data to Demand Management with Mas - Sales &amp;amp; Operations Planning (LO-LIS-PLN) - SAP Library
    BR
    CAetano

  • Help scope out MRP process

    We are kicking off an MRP project in a couple months and I need some help filling in a few gaps in my knowledge. I am fairly familiar with MM but hardly at all with PP. We are on ECC 6.0. Not running SRM/APO.
    Some background: My company wishes to do forecast based MRP. We have about 2 years of MM transactional history and inventory of data. We have not implemented any PP but are prepared to put in whichever components are required in support of the MRP process. However, a non-SAP system will remain our production order system. We use SAP MM/WM for procure to pay and IM of raw materials. The desire is to marry SAP's generated forecast based on historical data with a future sales/demand forecast created in Excel. This sales forecast lists out the finished good. The forecast gets generated quarterly for the next 3 months.
    A few questions I had:
    1) Since we do not care to valuate or inventory the finished good, I assume that we need to represent the finished good as a phantom material with the BOM components being the raw materials?
    2) What is the BADI that is used to import the Excel sales forecast? What transaction calls the BADI?
    3) I assume that after SAP marries the historical and future forecast data, there is the ability to view the consolidated forecast and make adjustments...what transaction is used for this?
    4) We have three plants and so far each plant has been carrying out its MRP planning (outside of SAP) on its own. However, there are many raw materials and finished goods that are common to the plants (ie same SAP material numbers) and, if not already, could be sourced from the same vendor for better pricing. On occasion, when there is a shortage in one plant we do a plant-to-plant transfer.
    a) I assume there is the capability to run MRP using the summarized forecast of all three plants? I'd group the plants under an MRP area, correct?
    b) Can some raw materials be planned at the plant level while other materials at the global level?
    c) Or if MRP takes place at the plant level, is there any functionality for our global procurement team to see a more summarized global view of the material requirements? He'd need this, for example, to negotiate better pricing on centrally agreed contracts with the vendor. 
    Thanks!
    Vlad

    Vlad,
    1) Since we do not care to valuate or inventory the finished good, I assume that we need to represent the finished good as a phantom material with the BOM components being the raw materials?
    Don't know where you got that idea.  I wouldn't do that, but I don't know all the particulars.  If you intend to sell finished goods, you probably will want to put them in a plant as stock.  If you intend to build finished goods, you probably shouldn't use a phantom.
    3) I assume that after SAP marries the historical and future forecast data, there is the ability to view the consolidated forecast and make adjustments...what transaction is used for this?
    Big assumption.  There are several ways to approach forecasting within SAP ECC.  These functionalities are not a 'transaction'.  I suggest you look at standard online help to get a feel of what is and is not possible.  Below is a bit of info about forecasting within SOP.  SOP is one of the planning methods with the greatest feature sets.  If SOP doesn't have enough functionality for you, then you probably need APO.  There are also simpler methods of forecasting in SAP.
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/a5/63201843a211d189410000e829fbbd/frameset.htm
    4) We have three plants and so far each plant has been carrying out its MRP planning (outside of SAP) on its own. However, there are many raw materials and finished goods that are common to the plants (i.e. same SAP material numbers) and, if not already, could be sourced from the same vendor for better pricing. On occasion, when there is a shortage in one plant we do a plant-to-plant transfer.
    a) I assume there is the capability to run MRP using the summarized forecast of all three plants? I'd group the plants under an MRP area, correct?
    another big assumption.  MRP, unlike forecasting, is generally done at the plant level.  There are ways to manage MRP so as to consolidate your demand into a single plant, but ultimately the purchased materials will have to be sent to the place where they are needed.  If you have 5 places where your RM is needed, you will either cut 5 POs, or one PO and then ship the parts internally to the point of use.
    b) Can some raw materials be planned at the plant level while other materials at the global level?
    Generally MRP planning parameters are set at the plant level.  There are, however, ways to manage your requirement.
    c) Or if MRP takes place at the plant level, is there any functionality for our global procurement team to see a more summarized global view of the material requirements?
    Yes
    In closing, expert Mario Adler has given you some sound advice.  What you are describing is a project.  Some companies take months or years to implement a solution similar to the one you are describing.  If you want to get the best bang for your buck, engage a consulting company who has done this before.  You will end up richer in the end.
    Best Regards,
    DB49

  • S076 SOP table for SD report (Sales Forecast Report ).

    Hi
    We are using S076 SOP table for SD report (Sales Forecast Report ).  This has only material number as key at present , where as we want to know if flexible planning will give material/shipto as key for forecast.
    Thanks In advance .

    Hi
       These are the key figures I am seeing in OMOJ , As I am new to this functionality                                  I am not able to add new key figures , can I request you to explain it to me ......
    Key figure                     F D 
    Sales     
    Production                         
    Stock level                        
    Target stock level                 
    Days' supply                       
    Target days' supply                
        Thanks

Maybe you are looking for