Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Mac Item Revision/ECN
- Thread starter jdblank
- Start date
Please define your needs.
Macola Progression or Macola ES?
Assumming you mean Progression, it allow you to create ECNs within macola for a change in the bill to be effective at some time in the future. Once that datehas come, post the ENC. This updates the product structure file.
What it does not do that people commonly want:
* Only 1 parent item per ECN
* No historical BOM kept on file, although the
captured BOMs are available as long as you do not
purge the associated POP andor SFC files.
So please define your needs. I know of no 3rd party enhancement that offers this, but who knows.
Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports
"A fine is a tax for doing wrong. A tax is a fine for doing well.
" - unknown
Macola Progression or Macola ES?
Assumming you mean Progression, it allow you to create ECNs within macola for a change in the bill to be effective at some time in the future. Once that datehas come, post the ENC. This updates the product structure file.
What it does not do that people commonly want:
* Only 1 parent item per ECN
* No historical BOM kept on file, although the
captured BOMs are available as long as you do not
purge the associated POP andor SFC files.
So please define your needs. I know of no 3rd party enhancement that offers this, but who knows.
Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports
"A fine is a tax for doing wrong. A tax is a fine for doing well.
" - unknown
- Thread starter
- #3
Standard Cost environment with Forecasts as demand driver.
1) Use Up/Replace scenario for ECN - Due to forecasting, the BOM Obsolete and Effective dates are “moving targets” when actual sold comes in, these dates are being managed manually and it is hurting.
2) I do in fact think I want to maintain 2 item numbers (as revisions), as 2 different revision part numbers will be on hand at the same time with different standard costs. My hopes is on the OE side, punch in main part number (as well as invoice and pack slip it) and revision actually picked hits cogs account. On the forecast side, forecast 1 part number.
3) In addition to #2, throw multiple routings for the same part - Primary Route is preferred, but the alternate route increases our capacity in times when needed and will also be used – each route is significantly different in costs. The other main catch here is - each machine on those routes requires different componentry, or BOM – so my material costs are different depending on which route I take as well. As you can see, I am in a myriad of GL variances on whatever route I take. I see this process being managed by an item revision rather nicely as well.
I know I can manipulate these using a different location to store standards – however, this creates problems with my WMS and then would need to modify that. I could also do the alternate part number manually, but his is a hack as well, especially trying to drive MRP requirements using multiple parts for one forecast part. Any route I take on the work around side, is either a hack, or would need modifications to other programs, so………………..I figured I’d check this place out and see if anyone knows someone with something already written to save some time.
Just checking, not much on the web search and this one is pretty complicated to solve in standard code, thanks for the response dgillz.
1) Use Up/Replace scenario for ECN - Due to forecasting, the BOM Obsolete and Effective dates are “moving targets” when actual sold comes in, these dates are being managed manually and it is hurting.
2) I do in fact think I want to maintain 2 item numbers (as revisions), as 2 different revision part numbers will be on hand at the same time with different standard costs. My hopes is on the OE side, punch in main part number (as well as invoice and pack slip it) and revision actually picked hits cogs account. On the forecast side, forecast 1 part number.
3) In addition to #2, throw multiple routings for the same part - Primary Route is preferred, but the alternate route increases our capacity in times when needed and will also be used – each route is significantly different in costs. The other main catch here is - each machine on those routes requires different componentry, or BOM – so my material costs are different depending on which route I take as well. As you can see, I am in a myriad of GL variances on whatever route I take. I see this process being managed by an item revision rather nicely as well.
I know I can manipulate these using a different location to store standards – however, this creates problems with my WMS and then would need to modify that. I could also do the alternate part number manually, but his is a hack as well, especially trying to drive MRP requirements using multiple parts for one forecast part. Any route I take on the work around side, is either a hack, or would need modifications to other programs, so………………..I figured I’d check this place out and see if anyone knows someone with something already written to save some time.
Just checking, not much on the web search and this one is pretty complicated to solve in standard code, thanks for the response dgillz.
- Status
Similar threads
- Locked
- Question