Vic,
On our system, when you regenerate MRP, all mrp job suggestion IDS are wiped out and replaced with new ones (they do not repeat). Am I reading correctly from your post that if you regenerate suggestions that the same MRP numbers appear again?Quote: Worse, if MRP is run again, and the new MRP job HAPPENS to get the same number as the one.....
Carey
To: vantage@yahoogroups.comFrom: vic.drecchio@...: Mon, 8 Dec 2008 09:40:20 -0500Subject: RE: [Vantage] MRP Procedural Question
Robert,Basically, if a PO suggestion is accepted, it contains a pointer to theMRP job that spawned it. If the MRP job is then firmed before the PO iscut, then the PO can no longer be cut, as it errors that the job is nolonger valid. Worse, if MRP is run again, and a new MRP job happens toget the same number as the one that originally spawned the POsuggestion, the system incorrectly assumes the demand is already beingfilled by the PO (regardless of what is actually being purchased)because of that number, and no suggestions are generated. Our workaroundis to not firm jobs until after the POs have been cut, but this is goingto cause unnecessary delays and coordination. We're also likely to runinto circumstances where we simply cannot make things happen in thisorder.Is this normal?-----Original Message-----From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On BehalfOf Robert BrownSent: Saturday, December 06, 2008 12:15 AMTo: vantage@yahoogroups.comSubject: Re: [Vantage] MRP Procedural QuestionVic,Run Net change mrp (or simply Generate PO suggestions) before havingyour buyers dig in after your big, long duration mrp jobs are Firmed.The mrp suggestion aren't real time updated. They are batch process andact paradigm.Rob--- On Fri, 12/5/08, Vic Drecchio <vic.drecchio@...> wrote:From: Vic Drecchio <vic.drecchio@...>Subject: [Vantage] MRP Procedural QuestionTo: vantage@yahoogroups.comDate: Friday, December 5, 2008, 5:12 PMI'll do my best to explain this........We are having a challenge with MRP.We have very long jobs that may take up to 18 mos.We run MRP and MRP creates unfirm MRPxxxxxx jobs and PO Suggestionslinked to those unfirm MRPxxxxxxx jobs.In our business, we may immediately firm and release a job to the floorto get CAD going or whatever. When we firm a MRPxxxxx job, it changesthe Job number. (normal behavior) So our floor starts working on this newly firmed job.The next day (after the job is released) Purchasing goes in to act onthe PO Sug's.The PO Sug's are still looking at the MRPxxxxx job(s) and weren'tupdated when we firmed the job up.I think I got it all. We tried to act on the PO Sug's and Vantageburped at us because those MRPxxxxx jobs aren't valid any more.Is this a bug? Anyone seen this? Are we doing anything wrong? Anyinput or ideas?Thank you in advance!Vic DrecchioERP AdministratorTIMCO Aviation ServicesGreensboro, NCEmail: vic.drecchio@ timco.aeroOffice: x3091Mobile: [Non-text portions of this message have been removed]------------------------------------Useful links for the Yahoo!Groups Vantage Board are: ( Note: You musthave already linked your email address to a yahoo id to enable access. )(1) To access the Files Section of our Yahoo!Group for Report Builderand Crystal Reports and other 'goodies', please goto:http://groups.yahoo.com/group/vantage/files/. (2) To search through old msg's goto:http://groups.yahoo.com/group/vantage/messages(3) To view links to Vendors that provide Vantage services goto:http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links
_________________________________________________________________
Send e-mail faster without improving your typing skills.
http://windowslive.com/Explore/hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_speed_122008
[Non-text portions of this message have been removed]
On our system, when you regenerate MRP, all mrp job suggestion IDS are wiped out and replaced with new ones (they do not repeat). Am I reading correctly from your post that if you regenerate suggestions that the same MRP numbers appear again?Quote: Worse, if MRP is run again, and the new MRP job HAPPENS to get the same number as the one.....
Carey
To: vantage@yahoogroups.comFrom: vic.drecchio@...: Mon, 8 Dec 2008 09:40:20 -0500Subject: RE: [Vantage] MRP Procedural Question
Robert,Basically, if a PO suggestion is accepted, it contains a pointer to theMRP job that spawned it. If the MRP job is then firmed before the PO iscut, then the PO can no longer be cut, as it errors that the job is nolonger valid. Worse, if MRP is run again, and a new MRP job happens toget the same number as the one that originally spawned the POsuggestion, the system incorrectly assumes the demand is already beingfilled by the PO (regardless of what is actually being purchased)because of that number, and no suggestions are generated. Our workaroundis to not firm jobs until after the POs have been cut, but this is goingto cause unnecessary delays and coordination. We're also likely to runinto circumstances where we simply cannot make things happen in thisorder.Is this normal?-----Original Message-----From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On BehalfOf Robert BrownSent: Saturday, December 06, 2008 12:15 AMTo: vantage@yahoogroups.comSubject: Re: [Vantage] MRP Procedural QuestionVic,Run Net change mrp (or simply Generate PO suggestions) before havingyour buyers dig in after your big, long duration mrp jobs are Firmed.The mrp suggestion aren't real time updated. They are batch process andact paradigm.Rob--- On Fri, 12/5/08, Vic Drecchio <vic.drecchio@...> wrote:From: Vic Drecchio <vic.drecchio@...>Subject: [Vantage] MRP Procedural QuestionTo: vantage@yahoogroups.comDate: Friday, December 5, 2008, 5:12 PMI'll do my best to explain this........We are having a challenge with MRP.We have very long jobs that may take up to 18 mos.We run MRP and MRP creates unfirm MRPxxxxxx jobs and PO Suggestionslinked to those unfirm MRPxxxxxxx jobs.In our business, we may immediately firm and release a job to the floorto get CAD going or whatever. When we firm a MRPxxxxx job, it changesthe Job number. (normal behavior) So our floor starts working on this newly firmed job.The next day (after the job is released) Purchasing goes in to act onthe PO Sug's.The PO Sug's are still looking at the MRPxxxxx job(s) and weren'tupdated when we firmed the job up.I think I got it all. We tried to act on the PO Sug's and Vantageburped at us because those MRPxxxxx jobs aren't valid any more.Is this a bug? Anyone seen this? Are we doing anything wrong? Anyinput or ideas?Thank you in advance!Vic DrecchioERP AdministratorTIMCO Aviation ServicesGreensboro, NCEmail: vic.drecchio@ timco.aeroOffice: x3091Mobile: [Non-text portions of this message have been removed]------------------------------------Useful links for the Yahoo!Groups Vantage Board are: ( Note: You musthave already linked your email address to a yahoo id to enable access. )(1) To access the Files Section of our Yahoo!Group for Report Builderand Crystal Reports and other 'goodies', please goto:http://groups.yahoo.com/group/vantage/files/. (2) To search through old msg's goto:http://groups.yahoo.com/group/vantage/messages(3) To view links to Vendors that provide Vantage services goto:http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links
_________________________________________________________________
Send e-mail faster without improving your typing skills.
http://windowslive.com/Explore/hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_speed_122008
[Non-text portions of this message have been removed]