8.03 and an invisible Plant

Hello Dan, I have seen some similar events when copying information
across databases. I have a few questions, were the parts that are
causing the issue imported from another datasource? If so were they
copied from the training database? I suspect that the information was
imported with the incorrect company ID attached to the record, I my
case I was able to copy an entire database into a blank database.
When I tried to access any of the information via the application I
could not, but when searching the background I could see all of the
data. So I changed the company ID and was then able to see all of the
records, in my case the issue was across the board where as yours
seems to only be with some entries. You should be able to run some
sort of script updating any entries that are listed as 'Vantage'
to 'Mfgsys' and this should get everything back into the correct
plant.

Let me know if this helps,

Jared Hillis
Second Foundation Consulting.


--- In vantage@yahoogroups.com, "Dan Ernst" <dernst@...> wrote:
>
> I thought it was a workstation but now I have been able to
duplicate
> the same thing at my workstation. Epicor has a copy of my database
> and are going to see if they can duplicate it. So far only thing I
> have discovered is MRP did not create a job for these orders. But
> looking at the orders they all looked normal except one of them was
> missing a Marketing Campaign. We have 8 configured parts and this
has
> happened on 3 different parts. I don't have a problem fixing it via
> odbc into Access but would like to know what is going on. I have 2
> more orders that MRP did not create a job for and I'd bet they
would
> go to the wrong plant.
>
> Thanks Gerard
>
> Dan Ernst
> Correct Craft, Inc.
>
>
> --- In vantage@yahoogroups.com, "Gerard Wadman" <gwadman@> wrote:
> >
> > Dan,
> >
> > I would connect to the JobHead table via MS Access
via
> ODBC.
> >
> > Once connected, I would not delete the job, I would however
update
> the
> > plant field with the correct plant, assuming that the data in the
> field
> > is wrong.
> >
> > Once updated I would go back into the job using Vantage and then
> delete
> > the job from within the app.
> >
> >
> >
> > If you are uncomfortable doing this and you have a support
> contract, FTP
> > a copy of your current DB to Epicor, they should be able to
> identify the
> > problem and write a fix that you can execute from the admin tools.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Gerard M Wadman
> >
> > Sr. Network Systems Engineer
> >
> >
> >
> > Scandius BioMedical Inc.
> >
> > 11A Beaver Brook Road
> >
> > Littleton, MA 01460
> >
> >
> >
> > 978/486-4088 x 124
> >
> > 978/486-4108 (fax)
> >
> >
> >
> > http://www.scandius.com/
> >
> >
> >
> >
> >
> > This e-mail is for the use of the intended recipient(s) only. If
you
> > have received this e-mail in error, please notify the sender
> immediately
> > and then delete it. If you are not the intended recipient, you
must
> not
> > use, disclose or distribute this e-mail without the author's prior
> > permission. We have taken precautions to minimize the risk of
> > transmitting software viruses, but we advise you to carry out
your
> own
> > virus checks on any attachment to this message. We do not accept
> > liability for any loss or damage caused by software viruses
> >
> >
> >
> >
> >
> >
> >
> > ________________________________
> >
> > From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On
> Behalf
> > Of Dan Ernst
> > Sent: Monday, April 09, 2007 1:58 PM
> > To: vantage@yahoogroups.com
> > Subject: [Vantage] 8.03 and an invisible Plant
> >
> >
> >
> > Here is a bizzare one hopefully someone can help me. Support is
> > clueless on this one. We had one user manually created 2 jobs
> through
> > planning workbench and it created it but when we went to access
> these
> > jobs it gave the following error message Job: 499233 is located
in
> > plant: Vantage. Access not allowed.
> >
> > We only have 1 plant and it is called MfgSys. I have created a
BAQ
> > using JobHead table and it shows 2 jobs being in a plant named
> Vantage.
> >
> > I tried the same thing from my workstation and it created the job
> in
> > the correct plant. I have asked the user to reboot her computer
but
> am
> > afraid to ask her to create any more jobs until I can find out
how
> to
> > gain access and delete the ones in the invisible plant.
> >
> > Does anyone know how to unlink these jobs from the order when we
> have
> > no access to a plant that does not exist within our Vantage?
> > We are on 8.03.305E
> >
> > I know it sounds a little crazy.
> >
> > Thanks
> > Dan Ernst
> > Correct Craft, Inc.
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
Here is a bizzare one hopefully someone can help me. Support is
clueless on this one. We had one user manually created 2 jobs through
planning workbench and it created it but when we went to access these
jobs it gave the following error message Job: 499233 is located in
plant: Vantage. Access not allowed.

We only have 1 plant and it is called MfgSys. I have created a BAQ
using JobHead table and it shows 2 jobs being in a plant named Vantage.

I tried the same thing from my workstation and it created the job in
the correct plant. I have asked the user to reboot her computer but am
afraid to ask her to create any more jobs until I can find out how to
gain access and delete the ones in the invisible plant.

Does anyone know how to unlink these jobs from the order when we have
no access to a plant that does not exist within our Vantage?
We are on 8.03.305E

I know it sounds a little crazy.

Thanks
Dan Ernst
Correct Craft, Inc.
Dan,

I would connect to the JobHead table via MS Access via ODBC.

Once connected, I would not delete the job, I would however update the
plant field with the correct plant, assuming that the data in the field
is wrong.

Once updated I would go back into the job using Vantage and then delete
the job from within the app.



If you are uncomfortable doing this and you have a support contract, FTP
a copy of your current DB to Epicor, they should be able to identify the
problem and write a fix that you can execute from the admin tools.









Gerard M Wadman

Sr. Network Systems Engineer



Scandius BioMedical Inc.

11A Beaver Brook Road

Littleton, MA 01460



978/486-4088 x 124

978/486-4108 (fax)



http://www.scandius.com/





This e-mail is for the use of the intended recipient(s) only. If you
have received this e-mail in error, please notify the sender immediately
and then delete it. If you are not the intended recipient, you must not
use, disclose or distribute this e-mail without the author's prior
permission. We have taken precautions to minimize the risk of
transmitting software viruses, but we advise you to carry out your own
virus checks on any attachment to this message. We do not accept
liability for any loss or damage caused by software viruses







________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Dan Ernst
Sent: Monday, April 09, 2007 1:58 PM
To: vantage@yahoogroups.com
Subject: [Vantage] 8.03 and an invisible Plant



Here is a bizzare one hopefully someone can help me. Support is
clueless on this one. We had one user manually created 2 jobs through
planning workbench and it created it but when we went to access these
jobs it gave the following error message Job: 499233 is located in
plant: Vantage. Access not allowed.

We only have 1 plant and it is called MfgSys. I have created a BAQ
using JobHead table and it shows 2 jobs being in a plant named Vantage.

I tried the same thing from my workstation and it created the job in
the correct plant. I have asked the user to reboot her computer but am
afraid to ask her to create any more jobs until I can find out how to
gain access and delete the ones in the invisible plant.

Does anyone know how to unlink these jobs from the order when we have
no access to a plant that does not exist within our Vantage?
We are on 8.03.305E

I know it sounds a little crazy.

Thanks
Dan Ernst
Correct Craft, Inc.





[Non-text portions of this message have been removed]
I thought it was a workstation but now I have been able to duplicate
the same thing at my workstation. Epicor has a copy of my database
and are going to see if they can duplicate it. So far only thing I
have discovered is MRP did not create a job for these orders. But
looking at the orders they all looked normal except one of them was
missing a Marketing Campaign. We have 8 configured parts and this has
happened on 3 different parts. I don't have a problem fixing it via
odbc into Access but would like to know what is going on. I have 2
more orders that MRP did not create a job for and I'd bet they would
go to the wrong plant.

Thanks Gerard

Dan Ernst
Correct Craft, Inc.


--- In vantage@yahoogroups.com, "Gerard Wadman" <gwadman@...> wrote:
>
> Dan,
>
> I would connect to the JobHead table via MS Access via
ODBC.
>
> Once connected, I would not delete the job, I would however update
the
> plant field with the correct plant, assuming that the data in the
field
> is wrong.
>
> Once updated I would go back into the job using Vantage and then
delete
> the job from within the app.
>
>
>
> If you are uncomfortable doing this and you have a support
contract, FTP
> a copy of your current DB to Epicor, they should be able to
identify the
> problem and write a fix that you can execute from the admin tools.
>
>
>
>
>
>
>
>
>
> Gerard M Wadman
>
> Sr. Network Systems Engineer
>
>
>
> Scandius BioMedical Inc.
>
> 11A Beaver Brook Road
>
> Littleton, MA 01460
>
>
>
> 978/486-4088 x 124
>
> 978/486-4108 (fax)
>
>
>
> http://www.scandius.com/
>
>
>
>
>
> This e-mail is for the use of the intended recipient(s) only. If you
> have received this e-mail in error, please notify the sender
immediately
> and then delete it. If you are not the intended recipient, you must
not
> use, disclose or distribute this e-mail without the author's prior
> permission. We have taken precautions to minimize the risk of
> transmitting software viruses, but we advise you to carry out your
own
> virus checks on any attachment to this message. We do not accept
> liability for any loss or damage caused by software viruses
>
>
>
>
>
>
>
> ________________________________
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On
Behalf
> Of Dan Ernst
> Sent: Monday, April 09, 2007 1:58 PM
> To: vantage@yahoogroups.com
> Subject: [Vantage] 8.03 and an invisible Plant
>
>
>
> Here is a bizzare one hopefully someone can help me. Support is
> clueless on this one. We had one user manually created 2 jobs
through
> planning workbench and it created it but when we went to access
these
> jobs it gave the following error message Job: 499233 is located in
> plant: Vantage. Access not allowed.
>
> We only have 1 plant and it is called MfgSys. I have created a BAQ
> using JobHead table and it shows 2 jobs being in a plant named
Vantage.
>
> I tried the same thing from my workstation and it created the job
in
> the correct plant. I have asked the user to reboot her computer but
am
> afraid to ask her to create any more jobs until I can find out how
to
> gain access and delete the ones in the invisible plant.
>
> Does anyone know how to unlink these jobs from the order when we
have
> no access to a plant that does not exist within our Vantage?
> We are on 8.03.305E
>
> I know it sounds a little crazy.
>
> Thanks
> Dan Ernst
> Correct Craft, Inc.
>
>
>
>
>
> [Non-text portions of this message have been removed]
>