Shot in the dark (8.0 Wishfull thinking)

Yahoo Archive
1
Hmm.... Did they say why changing the prefix would make the database start
creating jobs again?


Dianna Musgrave
IS/ERP Manager
Stone County Ironworks
870-269-8108 ext. 2099
http://www.stoneiron.com <http://www.stoneiron.com/>



_____

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Lindquist, Pam
Sent: Thursday, June 08, 2006 1:04 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Shot in the dark (8.0 Wishfull thinking)



We had a similar problem in V8. All of a sudden MRP would not create any
jobs at all. Our consultant suggested we change the MRP prefix in
Company setup to something different. This worked. As far as I know the
original problem is still in development.

Pam Lindquist
Metro Machine & Engineering

________________________________

From: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
[mailto:vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com] On
Behalf
Of Dianna Musgrave
Sent: Thursday, June 08, 2006 12:07 PM
To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
Subject: RE: [Vantage] Shot in the dark (8.0 Wishfull thinking)

We ran into a situation where MRP stopped creating jobs in the middle of
an
order. We sent the database to Epicor several months ago, but there is
no
answer as to what the problem was.

So, we decided we must have a problem with our old data from several
companies that were created and are no longer used. We are entering our
data in Vantage 8 hoping that with a fresh database, it will solve the
issue.

We decided to set up workstations in each department and we will put the
Vantage 6 database on a backup server for access to history. It is not
ideal, but we do not feel comfortable keeping the obsolete data.

Dianna Musgrave
IS/ERP Manager
Stone County Ironworks
870-269-8108 ext. 2099
http://www.stoneiro <http://www.stoneiron.com> n.com <http://www.stoneiro
<http://www.stoneiron.com> n.com>
<http://www.stoneiro <http://www.stoneiron.com/> n.com/ <http://www.stoneiro
<http://www.stoneiron.com/> n.com/> >

_____

From: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
<mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
<mailto:vantage%40yahoogroups.com> ] On
Behalf Of
Bruce Butler
Sent: Wednesday, June 07, 2006 12:55 PM
To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
<mailto:vantage%40yahoogroups.com>
Subject: [Vantage] Shot in the dark (8.0 Wishfull thinking)

In our move towards 8.0 we are weighing the advantages of starting new
vs. maintaining our History. Ideally we would like to get rid of all
the old workcenters, old bins, unused vendors, old customers, old part
numbers, etc.., but still have easy access to our history.

The only way I have been able to come up with for doing this is to
create a second company which will be new data, and upgrade the 6.1 to
8.0 as a second company within the same app. This is ok, but not really
what we want.

How have others with the same desires balanced this?

Thanks,

Bruce Butler, IT Manager

Knappe & Koester <http://www.knappe- <http://www.knappe-
<http://www.knappe-koester.com/> koester.com/
<http://www.knappe- <http://www.knappe-koester.com/> koester.com/> >
koester.com/>

18 Bradco Street

Keene, NH

p. 603-355-1166

f. 603-355-2266

bbutler@knappe- <mailto:bbutler%40knappe-koester.com> koester.com

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

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

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






[Non-text portions of this message have been removed]
2
In our move towards 8.0 we are weighing the advantages of starting new
vs. maintaining our History. Ideally we would like to get rid of all
the old workcenters, old bins, unused vendors, old customers, old part
numbers, etc.., but still have easy access to our history.



The only way I have been able to come up with for doing this is to
create a second company which will be new data, and upgrade the 6.1 to
8.0 as a second company within the same app. This is ok, but not really
what we want.



How have others with the same desires balanced this?



Thanks,



Bruce Butler, IT Manager

Knappe & Koester <http://www.knappe-koester.com/>

18 Bradco Street

Keene, NH

p. 603-355-1166

f. 603-355-2266

bbutler@...





[Non-text portions of this message have been removed]
3
That is basically what we did. We converted 6.1 to 8.0 basically as is
about 15 months ago. After about 4 months, we needed to merge our company
with another just down the street. Most things between the companies were
incompatible so we took the opportunity to start a new company in Vantage
and start from scratch.

I know other areas did some clean up, but I can only speak from the
engineering/operations perspective:

It was a lot of work--we completely redid all of our operations and most
resource groups (work centers) so the engineering group had to manually
re-enter our MOM's for all the parts (we had to make engineering-type
decisions regarding the new options so we couldn't have temps or other
assistance).

But this also gave us the opportunity to leave a lot of parts behind (we
only brought over stuff that we had accessed in the last year or so). We
occasionally have to add in parts from the old database as we need them,
but it is nice to have everything pretty much clean.

To access the old companies, we just click over. Everything is disabled in
the old except for some trackers and a few reports, which is basically all
we need.

When we first converted over to the new database, we were in both
constantly, so IT enabled our engineering group to have multiple sessions
of Vantage open, so we could look at more than one database at the same
time. After a few months, we didn't need that any more so they switched us
back to one session. And 1 year later, we maybe access the old stuff once
every 2-3 weeks.

It was totally worth it for us (in my opinion). It's not something I'd want
to do again anytime soon, but 8.0 is so different it really seemed like the
perfect place to make a clean break.

Amy O'Malley
Synovis IS
Manufacturing Process Engineer
Minneapolis, Minnesota

On Jun 7 2006, Bruce Butler wrote:
>In our move towards 8.0 we are weighing the advantages of starting new
>vs. maintaining our History. Ideally we would like to get rid of all
>the old workcenters, old bins, unused vendors, old customers, old part
>numbers, etc.., but still have easy access to our history.
>The only way I have been able to come up with for doing this is to
>create a second company which will be new data, and upgrade the 6.1 to
>8.0 as a second company within the same app. This is ok, but not really
>what we want.
4
We ran into a situation where MRP stopped creating jobs in the middle of an
order. We sent the database to Epicor several months ago, but there is no
answer as to what the problem was.

So, we decided we must have a problem with our old data from several
companies that were created and are no longer used. We are entering our
data in Vantage 8 hoping that with a fresh database, it will solve the
issue.

We decided to set up workstations in each department and we will put the
Vantage 6 database on a backup server for access to history. It is not
ideal, but we do not feel comfortable keeping the obsolete data.


Dianna Musgrave
IS/ERP Manager
Stone County Ironworks
870-269-8108 ext. 2099
http://www.stoneiron.com <http://www.stoneiron.com/>



_____

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Bruce Butler
Sent: Wednesday, June 07, 2006 12:55 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Shot in the dark (8.0 Wishfull thinking)



In our move towards 8.0 we are weighing the advantages of starting new
vs. maintaining our History. Ideally we would like to get rid of all
the old workcenters, old bins, unused vendors, old customers, old part
numbers, etc.., but still have easy access to our history.

The only way I have been able to come up with for doing this is to
create a second company which will be new data, and upgrade the 6.1 to
8.0 as a second company within the same app. This is ok, but not really
what we want.

How have others with the same desires balanced this?

Thanks,

Bruce Butler, IT Manager

Knappe & Koester <http://www.knappe- <http://www.knappe-koester.com/>
koester.com/>

18 Bradco Street

Keene, NH

p. 603-355-1166

f. 603-355-2266

bbutler@knappe- <mailto:bbutler%40knappe-koester.com> koester.com

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






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

Just curious about your MRP runs dropping jobs, as we are currently
experiencing a problem like that too (Vantage 6.10.529)

In our case, we'll have a forecast for a part that has subassemblies
that are Make to Stock (which normally makes MRP spawn sub-jobs to build
one top-level assembly) but in our case, the problem is that MRP will
simply not create jobs for _some_ sub-assemblies (and once it stops,
demand for sub-assemblies further don the BOM don't get created either).


The sub-assemblies effected are not the same ones each time, or, should
I say, change over time.

We are running SQL Server as our DB, and have been back and forth with
Epicor Customer Support since April 2005.

Duane
Imago Scientific


________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
On Behalf Of Dianna Musgrave
Sent: Thursday, June 08, 2006 12:07 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Shot in the dark (8.0 Wishfull thinking)



We ran into a situation where MRP stopped creating jobs in the
middle of an
order. We sent the database to Epicor several months ago, but
there is no
answer as to what the problem was.

So, we decided we must have a problem with our old data from
several
companies that were created and are no longer used. We are
entering our
data in Vantage 8 hoping that with a fresh database, it will
solve the
issue.

We decided to set up workstations in each department and we will
put the
Vantage 6 database on a backup server for access to history. It
is not
ideal, but we do not feel comfortable keeping the obsolete data.


Dianna Musgrave
IS/ERP Manager
Stone County Ironworks
870-269-8108 ext. 2099
http://www.stoneiron.com <http://www.stoneiron.com>
<http://www.stoneiron.com/ <http://www.stoneiron.com/> >

_____

From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf Of
Bruce Butler
Sent: Wednesday, June 07, 2006 12:55 PM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: [Vantage] Shot in the dark (8.0 Wishfull thinking)

In our move towards 8.0 we are weighing the advantages of
starting new
vs. maintaining our History. Ideally we would like to get rid of
all
the old workcenters, old bins, unused vendors, old customers,
old part
numbers, etc.., but still have easy access to our history.

The only way I have been able to come up with for doing this is
to
create a second company which will be new data, and upgrade the
6.1 to
8.0 as a second company within the same app. This is ok, but not
really
what we want.

How have others with the same desires balanced this?

Thanks,

Bruce Butler, IT Manager

Knappe & Koester <http://www.knappe-
<http://www.knappe-koester.com/ <http://www.knappe-koester.com/> >
koester.com/>

18 Bradco Street

Keene, NH

p. 603-355-1166

f. 603-355-2266

bbutler@knappe- <mailto:bbutler%40knappe-koester.com>
koester.com

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

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






NOTICE: These communications may contain privileged or other confidential information for the sole use of the designated recipients. If you have received it in error, please advise the sender by reply email and immediately delete the message and any attachments without reviewing, copying or disclosing the contents.



[Non-text portions of this message have been removed]
6
We had a similar problem in V8. All of a sudden MRP would not create any
jobs at all. Our consultant suggested we change the MRP prefix in
Company setup to something different. This worked. As far as I know the
original problem is still in development.

Pam Lindquist
Metro Machine & Engineering

________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Dianna Musgrave
Sent: Thursday, June 08, 2006 12:07 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Shot in the dark (8.0 Wishfull thinking)



We ran into a situation where MRP stopped creating jobs in the middle of
an
order. We sent the database to Epicor several months ago, but there is
no
answer as to what the problem was.

So, we decided we must have a problem with our old data from several
companies that were created and are no longer used. We are entering our
data in Vantage 8 hoping that with a fresh database, it will solve the
issue.

We decided to set up workstations in each department and we will put the
Vantage 6 database on a backup server for access to history. It is not
ideal, but we do not feel comfortable keeping the obsolete data.


Dianna Musgrave
IS/ERP Manager
Stone County Ironworks
870-269-8108 ext. 2099
http://www.stoneiron.com <http://www.stoneiron.com>
<http://www.stoneiron.com/ <http://www.stoneiron.com/> >

_____

From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf Of
Bruce Butler
Sent: Wednesday, June 07, 2006 12:55 PM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: [Vantage] Shot in the dark (8.0 Wishfull thinking)

In our move towards 8.0 we are weighing the advantages of starting new
vs. maintaining our History. Ideally we would like to get rid of all
the old workcenters, old bins, unused vendors, old customers, old part
numbers, etc.., but still have easy access to our history.

The only way I have been able to come up with for doing this is to
create a second company which will be new data, and upgrade the 6.1 to
8.0 as a second company within the same app. This is ok, but not really
what we want.

How have others with the same desires balanced this?

Thanks,

Bruce Butler, IT Manager

Knappe & Koester <http://www.knappe- <http://www.knappe-koester.com/
<http://www.knappe-koester.com/> >
koester.com/>

18 Bradco Street

Keene, NH

p. 603-355-1166

f. 603-355-2266

bbutler@knappe- <mailto:bbutler%40knappe-koester.com> koester.com

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

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






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