Multiple BOMs per revision?

Yahoo Archive
1
Alternate methods work as far as creating multiple BOMs under a single revision, but in the case of a "bad" BOM, I wouldn't think you'd want to keep it active anyway. Also, if you use standard costing, you'd have to remember to pull the alternate method every time you roll costs for the part.

IMO, if your company policy precludes you from fixing the existing rev with only the check in comments for documentation, this is what "minor" revs were made for.

--- In vantage@yahoogroups.com, Mark Wonsil <mark_wonsil@...> wrote:
>
> I third. You might be able to get creative with alternate methods. Remember
> that ECO* tables generally only persist while in the EWB - once checked-in,
> they delete many of the records. You'd want to look at PartMtl, PartOpr,
> etc.
>
> Mark W.
>
> On Tue, Oct 25, 2011 at 3:40 PM, Manasa Reddy <manasa@...> wrote:
>
> > **
> >
> >
> > I second Vic.
> >
> > But I have to ask why you would want this function to begin with?
> > Outside of it not making sense, there is obviously something that is
> > needed, but is not being communicated correctly to find the right answer
> > for you.
> >
> > I was just wondering if you can elaborate more?
> >
> > M. Manasa Reddy
> >
> > manasa@...
> >
> > 630.806.2000 x1515
> >
> > Ex scientia, vera
> >
> > ________________________________
> >
> > From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
> > Of Elizabeth
> > Sent: Tuesday, October 25, 2011 2:03 PM
> > To: vantage@yahoogroups.com
> > Subject: [Vantage] Multiple BOMs per revision?
> >
> > My quality manager asked me today if Epicor is able to uprev a BOM
> > without uprevving the part. I don't think it can, at least I can't find
> > a mechanism to support the function, but then in the System Data
> > Dictionary the ECOMtl Table is described as "Child of the ECORev table".
> > If that is indeed the case can the ECORev table have multiple child
> > tables, and how would they relate? So far I haven't found any way to do
> > so.
> >
> > Ernie Lowell
> > Diba Industries
> >
> > [Non-text portions of this message have been removed]
> >
> >
> >
>
>
> [Non-text portions of this message have been removed]
>
2
My quality manager asked me today if Epicor is able to uprev a BOM without uprevving the part. I don't think it can, at least I can't find a mechanism to support the function, but then in the System Data Dictionary the ECOMtl Table is described as "Child of the ECORev table". If that is indeed the case can the ECORev table have multiple child tables, and how would they relate? So far I haven't found any way to do so.

Ernie Lowell
Diba Industries
3
Nope.

From: Elizabeth
Sent: Tuesday, October 25, 2011 3:02 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Multiple BOMs per revision?


My quality manager asked me today if Epicor is able to uprev a BOM without uprevving the part. I don't think it can, at least I can't find a mechanism to support the function, but then in the System Data Dictionary the ECOMtl Table is described as "Child of the ECORev table". If that is indeed the case can the ECORev table have multiple child tables, and how would they relate? So far I haven't found any way to do so.

Ernie Lowell
Diba Industries




No virus found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.1834 / Virus Database: 2092/4573 - Release Date: 10/25/11


[Non-text portions of this message have been removed]
4
I second Vic.



But I have to ask why you would want this function to begin with?
Outside of it not making sense, there is obviously something that is
needed, but is not being communicated correctly to find the right answer
for you.



I was just wondering if you can elaborate more?







M. Manasa Reddy

manasa@...

630.806.2000 x1515



Ex scientia, vera

________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Elizabeth
Sent: Tuesday, October 25, 2011 2:03 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Multiple BOMs per revision?





My quality manager asked me today if Epicor is able to uprev a BOM
without uprevving the part. I don't think it can, at least I can't find
a mechanism to support the function, but then in the System Data
Dictionary the ECOMtl Table is described as "Child of the ECORev table".
If that is indeed the case can the ECORev table have multiple child
tables, and how would they relate? So far I haven't found any way to do
so.

Ernie Lowell
Diba Industries





[Non-text portions of this message have been removed]
5
The scenario she gave was if an engineer entered a typo on a quantity required on the BOM, say entered 2 instead of 20 for a particular material. On the floor they find this, then pass the information back up the chain of command. She wants to be able to retain document control on the BOM separate from the revision itself, and not have to up-rev the entire part to correct a typo.

I wondered why she just couldn't fix the typo, but she wanted me to ask.

Ernie Lowell
Diba Industries

--- In vantage@yahoogroups.com, "Manasa Reddy" <manasa@...> wrote:
>
> I second Vic.
>
>
>
> But I have to ask why you would want this function to begin with?
> Outside of it not making sense, there is obviously something that is
> needed, but is not being communicated correctly to find the right answer
> for you.
>
>
>
> I was just wondering if you can elaborate more?
>
>
>
>
>
>
>
> M. Manasa Reddy
>
> manasa@...
>
> 630.806.2000 x1515
>
>
>
> Ex scientia, vera
>
> ________________________________
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
> Of Elizabeth
> Sent: Tuesday, October 25, 2011 2:03 PM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Multiple BOMs per revision?
>
>
>
>
>
> My quality manager asked me today if Epicor is able to uprev a BOM
> without uprevving the part. I don't think it can, at least I can't find
> a mechanism to support the function, but then in the System Data
> Dictionary the ECOMtl Table is described as "Child of the ECORev table".
> If that is indeed the case can the ECORev table have multiple child
> tables, and how would they relate? So far I haven't found any way to do
> so.
>
> Ernie Lowell
> Diba Industries
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
6
I third. You might be able to get creative with alternate methods. Remember
that ECO* tables generally only persist while in the EWB - once checked-in,
they delete many of the records. You'd want to look at PartMtl, PartOpr,
etc.

Mark W.

On Tue, Oct 25, 2011 at 3:40 PM, Manasa Reddy <manasa@...> wrote:

> **
>
>
> I second Vic.
>
> But I have to ask why you would want this function to begin with?
> Outside of it not making sense, there is obviously something that is
> needed, but is not being communicated correctly to find the right answer
> for you.
>
> I was just wondering if you can elaborate more?
>
> M. Manasa Reddy
>
> manasa@...
>
> 630.806.2000 x1515
>
> Ex scientia, vera
>
> ________________________________
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
> Of Elizabeth
> Sent: Tuesday, October 25, 2011 2:03 PM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Multiple BOMs per revision?
>
> My quality manager asked me today if Epicor is able to uprev a BOM
> without uprevving the part. I don't think it can, at least I can't find
> a mechanism to support the function, but then in the System Data
> Dictionary the ECOMtl Table is described as "Child of the ECORev table".
> If that is indeed the case can the ECORev table have multiple child
> tables, and how would they relate? So far I haven't found any way to do
> so.
>
> Ernie Lowell
> Diba Industries
>
> [Non-text portions of this message have been removed]
>
>
>


[Non-text portions of this message have been removed]