cancel
Showing results for 
Search instead for 
Did you mean: 

Deletion of Planning file entries in MRP

Former Member
0 Kudos

Hello,

Could any body suggest how to delete the planning file entries. I have tryed through MDRE transaction but its not getting delete

please advise

thanks

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi

MDRE transaction is check only. Please try MDAB transaction .

Regards,

Gaito

Former Member
0 Kudos

As you said I have tried even though its not getting delete

please advise

Former Member
0 Kudos

Please clarify one more thing ie when MRP run duplicate purchase requisitions are getting generated what are the consiquencies to heppen like this

Former Member
0 Kudos

Hi

 

  If you change 'ND' of MRP type in MRP view of Material master, the system delete planning file entrry.

You do not need to delete planning file entrry. MRP use flag of planning file.

Regards,

Gaito

Former Member
0 Kudos

When MRP run duplicate PR's getting generated for same material and before material reach to reorder point this is happining

we are using MRP type:VB manual reorderpoint

lotsize:HB

could you give anay advise why this is happining

is there any relation between planning file entries and duplicate PR's

in what kind of situvation this duplicate pr's get generate

Former Member
0 Kudos

99,

You should never have to delete planning file entries. SAP does not supply a standard program whose sole purpose is deleting these entries. Deleting an entry improperly using non-standard methods, will stop MRP from running against that material.

A common reason for duplicated procurement proposals in setting the rescheduling horizon improperly. You can verify this by looking at the MRP list of one of the Purchase reqs. Does it have any "20 Cancel process" exceptions? Reading the exception messages should always be your first troubleshooting step.

If this is the case, you should avoid firming any purchase reqs. You can also consider running MRP with Planning mode parameter set to "3 delete and recreate". This will delete any old unfirmed Purchase reqs before running MRP. If nothing else, it can make it a bit clearer exactly what is happening.

If you are getting Cancel Process exceptions, you can sometimes help yourself by changing the rescheduling horizon in OPPQ or OPPR. Try making it larger.

http://help.sap.com/erp2005_ehp_04/helpdata/EN/f4/7d2c9744af11d182b40000e829fbfe/frameset.htm

Another factor that could have an impact on the number of PrReqs is the Maximum lot size in the Material Master. If this field has an entry, try making it bigger.

Rgds,

DB49

Former Member
0 Kudos

Hi DB49

Thanks for your supporting

Actually we are running MRP at plant level, though MRP area is deactivated for two material when check in MD21 planning files are getting generated one is at plant level another one is at MRP area level

is there any specific reason for this to happen like this

as you said exception message 20 ie cancel process this is coming for existing PO

as i know exception message system will calculate based on planned delivery time and po delivery schedule

could you please explain on what calculation this will happen

system to give message 20 how much should be the gap between planned delivery time and po delivery schedule

Edited by: sapmm99 on Jun 2, 2010 12:25 PM

Edited by: sapmm99 on Jun 2, 2010 12:49 PM

Former Member
0 Kudos

99,

I though you said you were getting duplicate PRs? Now, you say you have a PO, and a PR?

Did you look at the rescheduling horizon? Did you read the SAP help I posted?

as i know exception message system will calculate based on planned delivery time and po delivery schedule

could you please explain on what calculation this will happen

I have no idea what your question means.

Exception message 20 means that the document is unnecessary, and should be canceled. There is no calculation, other than total receipts for the part exceed the reorder point quantity (the goal), and the entire receipt document (PR or PO) is no longer necessary to meet the requirements.

In manual reorder point, when today's stock falls below reorder point, the system will recognize a shortage. It will consider all existing firmed receipts. If it finds inadequate firmed receipts between 'today' and "today plus planned delivery time", it will create a proposal (purchase requisition).

If you want the system to also consider any firmed elements that currently exist outside of planned delivery time, then you need to make MRP propose rescheduling of the existing firmed element (firmed PR; or any PO). It will do this, according to the settings in your rescheduling check mentioned earlier. When this happens, MRP, instead of creating a new PR, will then suggest that you pull in (reschedule) the existing firmed element.

Rgds,

DB49

Former Member
0 Kudos

what I am asking is based on planed delivery time and PO delivery schedule system will give the exception message 20

I have tested the one scenario in that planed delivery time i have given 60 days once PR got generated then converted PR in to PO during converting changed the PO delivry schedule to november 2010

again changed data in material master like reorder point and maximum stocklevel then execute the MD03 then systen has generated the PR and for that existing PO system is showing exception message 20

then I have changed the existing PO delivery schedule to september 2010 then exception message 20 gone

so inorder to generate the exception message 20 how much gap should be there

and how this system will calculate

please advise

Former Member
0 Kudos

99,

Well, the details of how you constructed your test scenario are not entirely clear, but I believe the answer is in the link I posted earlier. Which by now, you surely will have read, yes?

If you wish to ask about scenarios concerning the rescheduling horizon, please raise a new message.

Rgds,

DB49

Former Member
0 Kudos

Hi DB,

As you said system does not give the exception message 20 cancel proceee for PR, only it will give for PO. Because lets say for example while creating the material master will give the planed delivery time 60 days when execute the MD03 based on planed delivery time system will generate either PR or planed order based on procurement type.

While converting the PR in to PO system automatically consider planed delivery time which has been given in to material master or other wise we can change the PO delivery schedule as per the need.

as per material master planed delivery time po delivery schedule should be 60 days from current date it means roughly first week of august

As per my investigation when change the po delivery schedule from august to november 2010

again when execute the MRP system is creating new PR at the same time for existing PO system is giving message 20

for example instead of novemebr if i enter the delivery schedule september in this case again when MRP run system does not showing exception message 20 as well system not creating the PR also ( if material not at reach to below reorder point)

always system based on planed delivry time system has to generate the exception message 20

but exactly on what base this message is happing i am unable to understand

if i am wrong please correct me

One more thing when system give exception message 20 but same PO when look at in to me22n for that there is no any deletion flag

so business users what they are telling how we can come to whether this PO needs to be processed or to be deleted

so simplay what they are doing just taking the PO print and sending to the resceptive vendors.

so due to this unnecessary inventory will increasing

Edited by: sapmm99 on Jun 3, 2010 11:44 AM

in spro where we can configure the exception messages could you please tell me

Edited by: sapmm99 on Jun 3, 2010 12:01 PM

Former Member
0 Kudos

99,

The reason that POs are generating the 20 message, and PRs are not, is entirely because of the date disparity, not because of "PO vs PR".

One thing that seems to be affecting this scenario is your expectations from the scheduling of the PRs and POs, and MRP's treatment of these two objects. You seem to want MRP to assume that the PO will be treated in the same way as it would a PR. This does not happen. POs are firm, most PRs are not. Because of this, scheduling disparities can result in the 20 message you are receiving against the POs.

When you convert the PR to a PO, look at the planned delivery time and GR processing time in the PO. ME23N Open the Detail section (bottom) > Select item > select Delivery Tab. Review these two times. Do they match the data found in your Material Master? I believe they may not.

Purchase orders are all 'sourced'. Purchase Requisitions usually are not. PRs and POs are often scheduled in different ways. The scheduling of the PO is typically dependent on the Vendor. Usually, this info is held in the Purchase Info Record, but there are other options. There are a number of ways your system can be configured in the area of scheduling POs, but I am guessing this is what is causing the differences in scheduling.

If you find that the GRPT and PDT are not identical to your material master settings, and this is unsatisfactory for you, then you need to determine the source of these two fields in the PO.

Now, if your only goal is to eliminate the 20 message, and you are currently happy with the scheduling of the two documents (PO & PR), then increase the rescheduling horizon, as I mentioned earlier. In this way, MRP will propose rescheduling this PO, rather than creating a new PR and proposing cancellation of the PO.

Rgds,

DB49

Former Member
0 Kudos

Hi DB,

As you said I have changed the rescheduling horizon from 100 to 360 then executed the MD03 and MD04 so PR got generated for two months time ( in material master given the planed delivery time 60 days ) while converting the pr in to po changed the po delivery schedule for ex august 2011as soon as save the po and come back to MD04 when execute system along with po again system is generating the pr also this time for existing po exception message is 10.

As per our requirement when execute the MD04 system generate the PR while converting the PR in to PO even if I give PO delivery schedule one year or more than one year time from current date system should not create any PR as well system should not give any exception message for that PO.

so please advise exactly what the configuration settings to be done inorder to fullfill my requirement.

one more thing if increase the rescheduling horizon what will happen, if decrease what will happen

Edited by: sapmm99 on Jun 8, 2010 6:50 AM

Former Member
0 Kudos

99,

I will assume that under these extremely unusual business requirements, you are happy to have a planned delivery time for 60 days, but during conversion of a pr to a PO, to instead get a planned delivery time of, say 1 year or more. You will forever be faced with shortages if you allow this to continue, since you will never order materials early enough to prevent stockouts.

Anyhow, I think you are also missing the entire point of reorder point planning. The concept is that when stock falls below a certain point, you get a PR at planned delivery time. Now, when you enter a PO at 1 year, you still want MRP to consider it. This is illogical, considering that your planned delivery time is 60 days.

Regardless, I will assume that you know what you are doing. The rescheduling horizon can help you here. It is designed, among other things, for the situation when a vendor's confirmations come back, and the confirmation exceeds the planned delivery time used in planning. In this case, MRP can be made to consider a fixed supply element even when it is outside planned delivery time. You generally set the rescheduling horizon for the greatest amount of time variance you expect to get from a vendor. Increasing the horizon will mean that fixed receipts farther out into the future will be considered in the net requirements calculation. Typical values of a rescheduling horizon would be, say, as much as 50% of your planned delivery time (this is totally a judgement call, but I can't think of any situation when I would have my RH be 6X of PDT).

The down side of making this quantity too high is that you will get stockouts. I guess this must be acceptable in your business.

Your requirements cannot be met with standard MRP (reorder point planning, no messages, PDT 60 days, Fixed receipt a year into the future). You will have to have a developer create custom code to achieve these requirements.

Sorry I couldn't be of more assistance. Please do not ask me about how the custom programming should be built, I do not make such recommendations in these forums.

Rgds,

DB49

Former Member
0 Kudos

Dear DB,

To provide solution for MRP issues you have taken more risk for me.

I have kept you in more trouble for that I am extremely sorry

Thank you very much for your continuous support and effective guidenence

From past couple of years I have been using this forum but I never see any other persions like you, Your only the THE BEST PERSON who has responded immediately and provide effective solution.

So many pople has to learn from you, how to give effective solution for the issue who ever using this forum.

Anyhow once again thank you very much for your effective guidence

Former Member
0 Kudos

Dear DB,

Now I have changed the rescheduling horizon from 100 to 50 then execute the MD03 and MD04 then PR got generated, while converting the PR in to PO changed the delivery schedule from august 2010 to august 2011so at that time no exception message and no duplicate PR create.

Again with out doing any changes in minum reorderpoint and maximum stock level just I have executed the MD03 then immediately system has given exception message 20 for that PO at the same time new PR got generate.

So my requirement is with out doing any changes in minium and maximum stock level even if i execute the MD03 system should not generate the exception message as well should not generate the PR also.

Even if execute MD03 with out doing any changes in minium and maximum stock level till august 2011 only that PO should appear

So please advise how this has to be protect and required settings to control the process.

Former Member
0 Kudos

99,

SAP software considers this condition to be an exception ('need' date is August 2010 via PDT, actual supply date is August 2011 via PO) . Every planner I ever worked with considers this condition to be an exception. SAP provides an exception message. You do not want the exception message. I don't really have anything further to say on this matter, other than to suggest you change your PDT so as to place the 'need' date to Aug 2011. Perhaps one of the other experts can offer better advice.

Rgds,

DB49

Former Member
0 Kudos

when create PO for non stock material it will pick price from PR to PO once it pick the value again it should not allow to change.

so what ever value is there in PR same should be in PO also even if we try to change PO value system should not allow

so please advise me much for your suggestion

Edited by: sapmm99 on Jun 12, 2010 10:20 AM

Answers (0)