Planning Horizon in Requiremets view

Hi,
Planning Horizon in Requirements view gives a warning if "From Date" is more than 1 month back.
Can someone point out which setting is effecting this.
Is there any way to increase this limit.
Thanks in advance.
Kumar

Hi Kumar - yes the only way to change that warning message to an error message is thru modification or copy of the program. One alternative is to create a transaction variant for the transaction /sapapo/rrp1 where you block that field from being changed. The field is defaulted to current date always so by preventing the user from changing that will always enforce the current date. I do not think that you can include logic such as today's date minus 30 in the transaction variant but that may be another option. Another option would be to create a new transaction pointing to the same program that /sapapo/rrp1 uses and create a variant assigned to the transaction. Then you could use TVARV or date manipulation in the variant, protect that field and assign the variant in the new transaction. Then you would need to reasign the transactions accordingly in user roles. Why do you need to restrict the requirements view to 30 days in the past?
Regards
Andy

Similar Messages

  • Planning Horizon

    Dear All,
    What is the MRP Planning Horizon,Please describe in simple

    Dear,
    You can define the Planning horizon in OPPQ under MRP group then we assign this MRP group to material master in MRP1 view.
    NETPL ( Net change planning in planning horizon)  you will get it in MD02, MD01: With this processing key only material where the indicator NETPL has been set in planning calendar are planned.For example if we set planning horizon as 30 days then in the material in which MRP relevant changes happened in last 30 days will only be planned. This planning restricts the scope of planning or number of material which reduces the runtime of planning run..
    Planning horizon is the period beyond it, requirements don't generate planned orders.
    Hope clear to you.
    Regards,
    R.Brahmankar

  • MRP: Planning horizon & opening period

    hi MM Experts,
    please, explain what is "MRP planning horizon" and what is the impact on MD03 ?
    please expalin elso "the MRP Opening  period" and what's his utility ?
    both of them are in the OMI8 tcode.
    thanx in advance.
    SDA

    Hi. Hope this helps.
    Planning horizon is the Time period in days, MRP will consider the requirements for Planning. We can define this in number of days in OPPQ and/or in OPPR.
    Simply it is = Cumulative lead time + Longest batching period.
    You can define the Planning horizon in OPPQ/OPPR as mentioned above
    & under MRP group then we assign this MRP group to material master in MRP1 view.
    NETPL ( Net change planning in planning horizon) you will get it in MD02, MD01: With this processing key only material where the indicator NETPL has been set in planning calendar are planned.For example if we set planning horizon as 30 days then in the material in which MRP relevant changes happened in last 30 days will only be planned. This planning restricts the scope of planning or number of material which reduces the runtime of planning run. Planning horizon is the period beyond it, requirements don't generate planned orders.
    Opening Period is...
    Opening period is like a "release window". The length of the opening period is the window of opportunity a planner has to convert the planned order to a purchase req.
    For example - Component A has a lead time of 14 days and opening period of 5 days. Requirement on 12-22-03
    Opening Date - 01/12/09
    Start Date - 08/12/09
    Finish Date - 22/12/09
    Now the planner can convert the order starting Dec. 1st, instead of Dec. 8. It basically is a buffer in the lead time to get things on order a little sooner than needed.
    Thanks.

  • Planning Horizon - Two T Codes

    Dear Experts,
    We have 2 T-Codes where we can maintain Planning Horizon.
    OPPQ - Maintanence of Plant Parameters.
    OMDX - Planning Horizon
    If I change the value (no. of days) of Planning Horizon in a T-Code, it gets automatically changed if I view it with another T-Code (OPPQ & OMDX).
    I want to know, why 2 T-Codes are provided to do the same thing?
    Is there any reason behind?
    Pls guide.
    Regards,
    Rohit.

    Dear,
    In OPPQ is for plant parameter so it is not only relevancy for Planning Horizon. You can change the rescheduling horizon, Coversion type. Same thing you will get in OPPR also.
    But OMDX  is only for  to maintain the Planning Horizon if you change her it will get copied to OPPQ and OPPR if in MRP group.
    So you can say it is short cut to define planning Horizon.
    Regards,
    R.Brhmankar

  • Std report to view planned price1, planned price date1 in view costing 2

    Hello Guru
    Is it possible to view planned price1, planned price date1 in view costing 2 in material master using standard SAP report when I select specific material and plant in selection screen ?
    I really want standard SAP report but don't want to create my own query specific for this case
    Any reply would be appreciated
    Thanks

    HI,
    In Table SE16N - MBEW you can get the planned price data.
    Regards,
    BK

  • Getting an error while activating a planning area "Enter values for planning horizon From and planning horizon To for the storage time profile level"

    Dear S&OP community,
    I am getting following error while creating a planning ares in a newly installed sandbox. "Enter values for planning horizon From and planning horizon To for the storage time profile level".
    This what I did...
    1) Created new attributes and master data objects and activated them successfully.
    2) Time profile created and activated successfully
    3) Trying to create planing area by assigning  time profile in step 2 and assigned master data from step1..Unable to save the data and system returns 
    this error - "Enter values for planning horizon From and planning horizon To for the storage time profile level"
    My understanding is time profile needs to be active  but doesn't have to have values...
    Any help is appreciated.
    Thanks,
    Krishna

    YS,
    Here are my time profile settings
    Level       Name          Display Horizon - Past  Display Horizon - Future
    1             Monthly     -6                                       11         
    2             Quarterly     -2                                       3
    3             Yearly        -1                                       2
    Time profile is active and but time profile data is not loaded
    Thanks,
    Krishna

  • MRP planning horizon

    Hello,
    One of our businesses has a requirement that planning horizon in MD64 / MD65 be defined once only for the first 3 planning periods. Planning period is in months. They enter forecasts for 12 months. They want that the first time they use MD64 they should be able to make entries for all 12 months. Subsequently, when they are entering forecasts for planning periods they want that entries for the first 3 months from the current date should be locked/ uneditable. For example, on 1 Jun 2008 they enter quantites for the first 3 months as 1000, 1200, 800. The next time independent reqs are defined the quantities 1000, 1200 and 800 should be uneditable. Is this possible? Or is there a way to accomplish this at the initial screen where the planning horizon is entered (by placing a check of some sort on the "from" date so that it must be 3 months forward from the current date). Perhaps some check at the basis level? Any suggestions would be greatly appreciated.
    Regards
    Edited by: Khan Awkhan on Jun 5, 2008 9:23 AM

    Hi,
    In Jan first you have created 12 months requirement & ran MRP. So planned order created for all 12 months.
    Now change in material master MRP type P1.
    Planning time fence - 3 months ie, 90 days.
    Again run MRP. System firm all the existing planned orders which are between these 90 days. No automatic changes will happen if you run MRP once again.
    If you create new proposal with in this 90 days, system will not change the existing planned orders and new planned order will create after the planning time fence.
    P1 function is, with in the planning horizon already existing planned order convert to firm planned order. If any new proposal comes within this period system creates planned order at the end of planning time fence.
    Suppose if you run MRP on Feb, system will consider 90 days from the current date. So Feb, Mar,Apr planned order get firm. No automatic changes will happen.
    Regards,
    Dharma

  • Planning Horizon Business Content

    Hi,
    Does anyone know if there is a business content for Planning Horizon for Stock - via transaction MD63/61 ?

    Dear Mohd,
    there is no standard extractor available for your data , You can use a Generic Extraction on tables PBIM and PBED to get your desired data .
    Hope it helps.
    Thanks,
    Krish

  • Planning Horizon Issue

    Hi All,
    We have maintained planning horizon of 40 days. Kindly suggest if procurement proposals can be created beyond 40 days of planning horizon.
    regards,
    Mohit

    Hi Mohit,
    We maintain the planning horizon to shorten the MRP planning run. The system then only plans materials that have undergone a change relevant to MRP within the planning horizon
    In your case an MRP run will not create the procurement proposals beyond 40 days. However, you can still create the procurement proposals manually.
    Regards,
    Pradeep.

  • TP/VS: Planning Horizon

    Dear all,
    I am facing a problem when I try to optimize a shipment.
    The follow message is displayed in the log:
    Vehicle CRTA BAU T 01 has unscheduled breaks. This can lead to inconsistencies.
    Orders cannot be scheduled in the planning horizon
    The best solution found is to not deliver any orders
    0 of 1 orders could be delivered
    What this message means?
    My Optimization Profile is set with a huge planning horizon date:
    Start Date:           26.11.2010
    End Date:            25.01.2011
    Duration (Days)  60
    In my delivery:
    Requested Delivery Time: From 30.11.2010 To 30.11.2010
    Today is 26.11.2010
    The duration of the transport:  54:44
    What procedures should I take to fix this message?
    Thanks a lot.
    Thiago

    Dear Thiago,
    if you check the optimizer message log, you can see the message /SAPAPO/VS367                                                         
    Diagnosis:                                                            
    You have maintained breaks without a fixed start time.                
    System Response:                                                      
    These breaks might not be supported by the optimizer and they are processed differently by liveCache and the optimizer. This can lead to problems when scheduling the associated shipments.         
    Please recheck how your Vehicle resource is maintained (from...to...) and also the Break duration. I assume this break was maintained without any fixed start time
    Hope this information helps you.                                       
    Regards,
    Tibor

  • Planning Horizon Effectiveness

    Dear Experts,
    Can some one explain me what does the planning horizon in MRP mean?
    In OPPQ,we have defined Planning Horizon as 180days.
    What I would like to know is that,How this 180days are considered?Whether the Factory calender is considered? whether it is 180 days from the MRP run date or how?
    I need to know this as my actual aim is to find out the reason behind the creation of system proposed Planned Orders. The system is considering the newly arriving Purchase orders only if it si scheduled before 10June09 and suppose if it is 11June09 the system proposes a Planned Order for the items.(But 11June is not 180days either from today's date or from the begining of 2009)
    Please reply...
    Points assured...
    Regards,
    Bhavin

    During MRP you might be using Create Purchase requisition indicator 2 - Purchase requisitions in opening period. if you have set indicator 2 (Purchase requisitions in opening period), the system only creates planned orders for procurement after the opening period. Within the opening period system creates purchase requisitions.
    When you select this indicator, the system creates purchase requisitions instead of planned orders when it determines an opening date that is before the date of the planning run

  • PR is generating beyond planning horizon

    Hi All,
    We have an issue with MRP.
    MRP type-VB / V1
    Lot size-HB
    Planning Horizon-90
    Rescheduling Horizon-100
    Recorder pt=100
    Max stock level=150
    Stock =1130
    Requirement= 1300 (Requirement date for 300 quantities is on 01.12.2011)
    As requirement is too far still it is creating PR after MRP run, Can you please check?
    Not sure whether Planning Horizon will consider for V1 and VB also?
    Thanks,
    Suhas

    I guess that it only creates a PR with V1, not VB, right?
    I think that even with V1 it will not if you run MRP in "net change in planning horizon" mode.

  • System considers dependant requirements lying outside planning horizon

    Hello Experts,
    Iam running the MRP for procurement. I have defined a planning horizon so that system will consider the requirements of that period. Iam using NETPL as my planning method in MRP. I wanted to create only purchase requisitions during this period so I selected 1 as my creation indicator as well.
    But the issue Iam facing is, system is not skipping the dependant requirements which is outside planning horizon. System skips only PIRs.
    For all the dependant requirements outside planning horizon, system creates planned orders and for those within plannning horizon system creates purchase requisition. Is there any settings to skip system considering dependant requirements outside planning horizon.??
    Thanks
    Prathib

    Hello
    I believe that there is a misunderstanding about what exactly is the planning horizon. Using a planning horizon does not means that the requirements outside the horizon will not be planned.
    The planning horizon represents a part of the planning area, where a planning file entry is made for the MRP processing key net change planning in the planning horizon (NETPL).
    In this kind of net change planning, only those materials that have undergone a change that is relevant to MRP within the planning horizon are included in the planning run. Such materials receive a net change planning indicator in the planning file.
    That means, if an MRP relevant change is made for a material within the planning horizon, the planning file entry NEPLT is set for this material.
    You can check in the SAP Help how the planning horizon works, see below:
    "You can also use a planning horizon to further limit the scope of the planning run. In "net change planning in the planning horizon", the system only plans materials that have undergone a change that is relevant to the planning run within the period which you defined as the planning horizon. The system sets the net change planning horizon indicator automatically for these materials."
    http://help.sap.com/erp2005_ehp_06/helpdata/EN/f4/7d274f44af11d182b40000
    e829fbfe/frameset.htm
    So, the planning horizon only define is the planning file will be marked as "net change planning".
    BR
    Caetano

  • MRP plans sales orders outside planning horizon

    MRP plans Sales order for Finished Goods Outside planning horizon even when using NETPL. Strategy 40 is in use with 3 level BOMs. Planning horizon - 200 day. How could it be prevented?

    Dear,
    Please check have you assigned any MRP group to your material masters in MRP1view? Then check the planning horizon maintain in MRP group in OPPR also check same for your plant in OPPQ.
    If you define it as 200 days then system will only plan the requirement which falls under 200 days with processing key as NETPL.
    If we set planning horizon as 200 days then in the material in which MRP relevant changes happened in last 200 days will only be planned. Planning horizon is the period beyond it, requirements don't generate planned orders
    Please check and revert back.
    Regards,
    R.Brahmankar

  • MRP looking past planning horizon?

    Dear Experts,
    We have a material that exists on a purchase order.  The material is a HALB, with MRP Type = PD and
    Procurement Type = F (purchased).  The Planning Horizon for the plant is 180 days and there is no planning horizon defined for MRP Group.  The Purchase Order has a  delivery date of 12/31/2009 (well past the horizon).   But, Purchase Requesitions are not being created during the MRP run.  The MRP settings we are using are NETPL, 1, 3, 1, 3, 1.
    It is acting like it is looking past the planning horizon and seeing the purchase order that is far out in the future.
    Does anyone have any ideas on what is happening?
    Thank you,
    Melissa

    Hi Melissa,
    The 250 days is workdays & not calendar days & hence it is beyond 31/12/2009. This is the reason why the system is considering the PO.
    If you're in test system, you can test by increasing the delivery date of the PO say to 31/12/2010 & run MRP, it would create a procurement proposal.
    Hope it answers your query.
    If helpful award points
    Regards,
    Vivek

Maybe you are looking for