Reg:PIR /Deliver date of sales order

Question

Dear Friends,
i have an issuie ragardding PIR (MD61).
I have created a demand from N0vember to March
Weekly 20no.s  machines ,.
For Ex:
November :60. Decenber:80, Jan:100..like that way till Maurch.
in the month of march i have planned 100.(totalplanned quantity is 390)
And sales orders have consumed the PIR.. in the month of march i have palnned only for first 15 days 100no.snext 15 days are remaining. suppose if the sales people create the new sales order it should give the delivery time in the month of march.But here the delivery dates  is showing in month of Decmber only.
may i know whats the reason..i hane not ,maintained Consumption mode in MRP-3. please let me know the solution.
Thanks in advance..

Answer 1

Dayanan,
I must appologize for my earlier inaccurate answer.  I was unfortunately relying on SAP online help which implies that only Strategies 50, 60, 52, 63, 74 use availability check against planning (planned independent requirements). 
http://help.sap.com/saphelp_erp60_sp/helpdata/en/cf/70124adf2d11d1b55e0000e82de178/frameset.htm 
This help statement is misleading.  Upon further research into your problem, I have discovered that 56 also, by default, performs availablity check against planning. What you are describing is therefore standard behavior.
Availability check against planning ignores supply elements, including FGs stock or FGs production orders.  Configuration contained in OVZ9 that I mentioned in my earlier answer is mostly irrelevant.  The system instead performs Availability check against the un-consumed Planned independent requirements.  The assumption is that you faithfully build/procure the components of your forecast, and therefore you can confirm any new sales order, as long as unconsumed PIRs exist.  The final assembly process is implicitly assumed to have unlimited capacity to perform your FGs assembly, as long as unconsumed PIRs exist.
Calculation of un-consumed forecast (from which your SD confirmation dates will be derived) is affected in turn by the consumption mode in the Material Master, as you have noted in your research, and by the backward and forward consumption periods in your Material Master.
Now, your problem originally was that you were getting confirmations (delivery dates) in December, when in fact you wanted them to confirmed for your next 'open' forecasting period, which for this material is in March.
The unexpected confirmation in December means that the customer requested a December or earlier delivery date, and there are unconsumed PIRs still left in December (eg, not enough customers have already entered orders for December to have entirely consumed the existing December forecast).
I will assume by your distress that you are unable to produce FGs product in time to meet the December confirmation deadline.  The way most companies solve this issue is to periodically (weekly at a minimum, some do this daily) is to run a job that deletes all PIRs within a specific time frame (eg, any PIRs earlier than, say, '2 weeks from now').  The window within which these PIRs are deleted is typically related to FGs processing time and FGs capacity load.  You will have to decide what is the best window for you. 
You can Mass delete PIRs using MD75.  You can commit this to a job by creating a variant, and then using report RM60RR30 in batch.  If you are already executing this report regularly, you probably want to review the Key Date, and move it forward in time a bit.
Best Regards,
DB49
Edited by: Dogboy49 on Nov 25, 2010 5:15 AM