It's built in to 702 and available upon request for 701 and I think 700 as well.
It does check to make sure there are no open transactions for the part in question before allowing the change to occur.
It does check to make sure there are no open transactions for the part in question before allowing the change to occur.
--- In vantage@yahoogroups.com, Joshua Giese <jgiese@...> wrote:
>
> Wait so in 702 they released a utility for changing the UOM of a part?!
>
>
>
> Joshua Giese
>
> CTO
>
> 920.437.6400 Ext. 337
>
> Site ID: 27450-E905700B2-SQL64
>
> ----- Original Message -----
>
> From: "Elizabeth" <gracefulthreads@...>
> To: vantage@yahoogroups.com
> Sent: Wednesday, May 29, 2013 8:40:35 AM
> Subject: [Vantage] Re: Is there a way to change UOM in Epicor 9?
>
>
>
> In 9.05.702, it's under System Management > Utilities > Part UOM Conversion.
>
> It's part of my testing methodology... my engineers are quite excited by it. Oh Joy.
>
> Ernie Lowell
> Diba Industries
>
> --- In vantage@yahoogroups.com , "Dan Sirow" <dansirow@> wrote:
> >
> >
> >
> >
> >
> >
> >
> > I was told at Insights there is a way with 9.05.702.
> >
> > From field help for Primary UOM on Part Screen:
> > Once a new part has been assigned a primary Inventory UOM code and is saved or used for any kind of transaction in the Epicor application, the Inventory UOM code can only be changed using the Part UOM Class Conversion Maintenance program.
> >
> > But I can't find that program - I would call support and ask. If you find out, let us know.
> >
> > --- In vantage@yahoogroups.com , "kayd.indaco" <kay.d@> wrote:
> > >
> > > We are loading our master files in Epicor 9.05.700C and realized we loaded some UOMs incorrectly. Now we can't make changes.
> > >
> > > I realize the wrong UOMs can be inactivated, but that makes it messy because there are several of them. Does anyone know of a way to fix this problem? Our planned go live date is in two weeks.
> > >
> > > Thanks in advance for any help,
> > > Kay Doolin
> > > Indaco Metals LLC
> > > 405.273.9200
> > >
> >
>
>
>
>
>
> [Non-text portions of this message have been removed]
>