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

Similar Messages

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

Planning horizon and scheduling horizon

hi gurus
what is the difference beween planning horizon and scheduling horizon
and how it will effect on production planning/MRP
pls give me a detailed answer
Faisal

hi,
planning horizon
planning horizon specifies the period for the "Net change planning in the planning horizon".
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.
The length of the planning horizon should include at least the following:
the period in which sales orders are received
the delivery periods
the total lead times of the materials
re-schedule horizon
Define Rescheduling Horizon
The rescheduling horizon is the period in which System checks whether the existing dates still suit the requirements situation for receipt elements that can no longer be automatically changed in the planning run. If the dates of a particular element are no longer suitable
effect:
If no rescheduling horizon has been maintained, the system will not carry out a rescheduling check.
The system calculates the rescheduling horizon from the end of the replenishment lead time in reorder point planning.

SNP and PPDS planning horizons

Hai,
        I am reading through SNP and PP/DS planning horizons. I understand that SNP doesnot plan anything within SNP production horizon whereas PP/DS plans only within the PP/DS horizon.
Now, I get confused when trying to understand the following sentences:
1. If production horizon of SNP is smaller than the PP/DS horizon, the planning horizons of SNP and PP/DS overlap with each other. In this horizon, SNP determines the receipts with most cost-effective sources of supply and lot sizes and PP/DS plans the receipts in more detail.
2. If requirements within the SNP production horizon cannot be covered by PP/DS, then SNP plans the receipt outside the SNP production horizon(this corresponds to the logic in the PP/DS planning time fence in short term planning).
3. If the PP/DS horizon in the product master is set to be greater than SNP production horizon, this gives rise to an overlapping area in both SNP and PP/DS receipts are created.
Can anyone please help me undestand the above? An example or somedocumentation reference is appreciated.
Thank you.

Hi Visu,
Good question. You missed Planning Time Fence in the equation.
|--||--
>
1.       PTF             SNP            PPDS
You execute PPDS Heuristic (Product Heuristic) then requirements upto PPDS horizon will be covered by receipt elements (beyond Planning Time Fence). If you run SNP Heuristic then receipt elements will be created from SNP Horizon out in future deleting the receipt elements created by the previous PPDS run. But note that while PPDS planning is down to the second level SNP planning is minimum at a day level. If you have weekly buckets then all requirements for one week will be clubbed and single receipt element will get created. However you can consider SNP orders as fixed during PPDS Net Requirement Calculation through appropriate development.
|--||--
>
       PTF              PPDS           SNP
2. This is also not clear to me as I cannot build the scenario as described. The above diagram is the closest I could come up with. But in this case if you run SNP Heuristic and there are unmet requirements (sitting between PPDS and SNP horizon) then the receipt for that will be created only at the start of the SNP Horizon.
3. This is correct but already explained in 1.
Hope this clarifies or at least does not add to the confusion. BTW if you are interested then please read OSS Note 481906 - SNP - PP/DS integration (documentation).
Thanks,
Somnath

How to setup a query plan in effective at any time for SP or SQL query?

I have a SP which include a group by SQL statement. It retrieve data from a couple of tables which are over 1G size,
When I run this SP at first time, it take more than 5 minutes to get the result. then I run it again and again, Finally, it become very quick, I can get the result within second.
Not sure why. I guess it is because of query plan.
How to make it running at first time to get result within second? How to force a better best query plan in effective at first time to run the query?
If the engine has better plan in memory, could it be lost at some point? because I have the complain from end user said some times it is fast, sometime it is very slow.
How to resolve this problem?

thanks, kevin. Here is the pesudo query( I modify table name as business rule from my company). you are right, mytab3 is a lookup table.
Select d.stock,i.description,c.categoryname,
Round(IsNull(Sum(d.qty),0),2) AS qty,
From mytab1 d,mytab2 s,invent i,mytab3 c
Where
d.stock != 'param1'
And d.id1 = s.id1    --id1: univarchar(11)
And i.code = c.code   --code:univarchar(2)
And d.stock = i.stock --stock: univarchar(12)
And i.code2 = d.code2 --code2: univarchar(2)
And d.code2 = 'param2'
And s.id2 = 'param3'   --id2: univarchar(6)
Group By c.categoryname,d.stock,i.description
Order By d.stock
here is the query plan when run this query:
The command completed with no results returned
QUERY PLAN FOR STATEMENT 1 (at line 1).
Executed in parallel by coordinating process and 4 worker processes.
    STEP 1
        The type of query is SELECT (into Worktable1).
        GROUP BY
        Evaluate Grouped SUM OR AVERAGE AGGREGATE.
        Evaluate Grouped SUM OR AVERAGE AGGREGATE.
        Evaluate Grouped SUM OR AVERAGE AGGREGATE.
        Executed in parallel by coordinating process and 4 worker processes.
        FROM TABLE
            mytab2
            s
        Nested iteration.
        Index : ind_mytab2 _id2
        Forward scan.
        Positioning by key.
        Keys are:
            id2 ASC
        Executed in parallel with a 4-way hash scan.
        Using I/O Size 16 Kbytes for index leaf pages.
        With LRU Buffer Replacement Strategy for index leaf pages.
        Using I/O Size 16 Kbytes for data pages.
        With LRU Buffer Replacement Strategy for data pages.
        FROM TABLE
            mytab1
            d
        Nested iteration.
        Index : ind_det_inv
        Forward scan.
        Positioning by key.
        Keys are:
            id1 ASC
        Using I/O Size 16 Kbytes for index leaf pages.
        With LRU Buffer Replacement Strategy for index leaf pages.
        Using I/O Size 16 Kbytes for data pages.
        With LRU Buffer Replacement Strategy for data pages.
        FROM TABLE
            invent
            i
        Nested iteration.
        Using Clustered Index.
        Index : invent_pk
        Forward scan.
        Positioning by key.
        Keys are:
            stock ASC
            code2 ASC
        Using I/O Size 2 Kbytes for data pages.
        With LRU Buffer Replacement Strategy for data pages.
        FROM TABLE
            mytab3
            c
        Nested iteration.
        Table Scan.
        Forward scan.
        Positioning at start of table.
        Using I/O Size 2 Kbytes for data pages.
        With LRU Buffer Replacement Strategy for data pages.
        TO TABLE
            Worktable1.
        Parallel work table merge.
    STEP 2
        The type of query is INSERT.
        The update mode is direct.
        Executed by coordinating process.
        Worktable2 created, in allpages locking mode, for ORDER BY.
        FROM TABLE
            Worktable1.
        Nested iteration.
        Table Scan.
        Forward scan.
        Positioning at start of table.
        Using I/O Size 8 Kbytes for data pages.
        With MRU Buffer Replacement Strategy for data pages.
        TO TABLE
            Worktable2.
    STEP 3
        The type of query is SELECT.
        Executed by coordinating process.
        This step involves sorting.
        FROM TABLE
            Worktable2.
        Using GETSORTED
        Table Scan.
        Forward scan.
        Positioning at start of table.
        Using I/O Size 8 Kbytes for data pages.
        With MRU Buffer Replacement Strategy for data pages.
Total estimated I/O cost for statement 1 (at line 1): 1409882.
The sort for Worktable2 is done in Serial

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

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

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 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

Planning Horizon Effectiveness

Similar Messages

Maybe you are looking for