Part.Plant Blank Title 71554

Yahoo Archive
1
I realize now what's happening....and someone mentioned it somewhere but
I skipped past it. A transfer entry is automatically created for these
parts. We don't do transfer orders currently, so no one was checking
there.



Ken





From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Ken Williams
Sent: Wednesday, December 03, 2008 9:18 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Part.Plant



We've been an Epicor customer for over two years now. The first 18
months was on Vista, but then we opened up another plant and needed to
upgrade to Vantage.

The upgrade for the most part has been pretty smooth. Lots of little
issues, but we've worked past them all.

Except one....

We have a parts database that is thousands large. All of these are
currently for one plant only. A large portion of these will need to be
setup in Ashland. As time goes on and new parts are entered, they
potentially need to be in both. This build up leads to two issues:

1. How do we update such a large percentage of parts to the new
plant without going through one at a time?

2. More importantly, if we have demand in plant B but the part is
only setup in plant A, there is no suggestion to purchase it, anywhere.
The part just gets lost in the system, no notification to anyone to do
anything with it (pull it, buy it, make it, etc...).

Any suggestions to tackle these 2 issues would be great,

Ken

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





[Non-text portions of this message have been removed]
2
We've been an Epicor customer for over two years now. The first 18
months was on Vista, but then we opened up another plant and needed to
upgrade to Vantage.



The upgrade for the most part has been pretty smooth. Lots of little
issues, but we've worked past them all.



Except one....



We have a parts database that is thousands large. All of these are
currently for one plant only. A large portion of these will need to be
setup in Ashland. As time goes on and new parts are entered, they
potentially need to be in both. This build up leads to two issues:



1. How do we update such a large percentage of parts to the new
plant without going through one at a time?

2. More importantly, if we have demand in plant B but the part is
only setup in plant A, there is no suggestion to purchase it, anywhere.
The part just gets lost in the system, no notification to anyone to do
anything with it (pull it, buy it, make it, etc...).



Any suggestions to tackle these 2 issues would be great,

Ken



[Non-text portions of this message have been removed]
3
regarding question 2,

Let's say part ABC123 is only made in PlantA

Open ABC123 in part master and on Plant tab, you add in PlantA as New Plant and set its type to "Manufacture".
Next, add in PlantB and specify it as type "Transfer" and pick PlantA as the Plant.
If you have minimums set for PlantB and the Process MRP check for PlantB, MRP will generate transfer suggestions for you.






________________________________
From: Ken Williams <ken@...>
To: vantage@yahoogroups.com
Sent: Wednesday, December 3, 2008 10:17:30 AM
Subject: [Vantage] Part.Plant


We've been an Epicor customer for over two years now. The first 18
months was on Vista, but then we opened up another plant and needed to
upgrade to Vantage.

The upgrade for the most part has been pretty smooth. Lots of little
issues, but we've worked past them all.

Except one....

We have a parts database that is thousands large. All of these are
currently for one plant only. A large portion of these will need to be
setup in Ashland. As time goes on and new parts are entered, they
potentially need to be in both. This build up leads to two issues:

1. How do we update such a large percentage of parts to the new
plant without going through one at a time?

2. More importantly, if we have demand in plant B but the part is
only setup in plant A, there is no suggestion to purchase it, anywhere.
The part just gets lost in the system, no notification to anyone to do
anything with it (pull it, buy it, make it, etc...).

Any suggestions to tackle these 2 issues would be great,

Ken

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






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

The first one is classic ServiceConnect territory. It would be easy
to run through all your parts and add in additional plant data. We
use this for making mass changes to data when our needs change. I
dont know how you would do this otherwise in any kind of safe manner.

As for the 2nd question, we do not run multi-plant so its difficult
to answer it. I assume that once you have set you parts up to exist
in both plants, Vantage will generate some kind of move suggestions.
Then again if I had a dollar for every time I had assumed Vantage
would do the obvious, I would indeed be rich...! ;o)

Sorry I can't be more help...

Nick


--- In vantage@yahoogroups.com, "Ken Williams" <ken@...> wrote:
>
> We've been an Epicor customer for over two years now. The first 18
> months was on Vista, but then we opened up another plant and needed
to
> upgrade to Vantage.
>
>
>
> The upgrade for the most part has been pretty smooth. Lots of
little
> issues, but we've worked past them all.
>
>
>
> Except one....
>
>
>
> We have a parts database that is thousands large. All of these are
> currently for one plant only. A large portion of these will need
to be
> setup in Ashland. As time goes on and new parts are entered, they
> potentially need to be in both. This build up leads to two issues:
>
>
>
> 1. How do we update such a large percentage of parts to the
new
> plant without going through one at a time?
>
> 2. More importantly, if we have demand in plant B but the
part is
> only setup in plant A, there is no suggestion to purchase it,
anywhere.
> The part just gets lost in the system, no notification to anyone to
do
> anything with it (pull it, buy it, make it, etc...).
>
>
>
> Any suggestions to tackle these 2 issues would be great,
>
> Ken
>
>
>
> [Non-text portions of this message have been removed]
>
5
I'm going to guess that the easiest thing to do would be to use
ServiceConnect to call Part.Update() for each part with a new PartPlant
record.



We own SC so this wouldn't be a big deal for us (and something we're
going to need to address ourselves). If you don't own SC then (I think)
you can still load existing workflows into the SC runtime and you'd be
able to populate the new plant with all of the parts you want to use
there. The easiest way to get the list of parts would be via a BAQ and
a dashboard, and pasting them into Excel and working with them there.



You could buy the Part import workflow from Epicor for not a lot of
money and I think you'd have all of the pieces you needed to do this.



-bws



--

Brian W. Spolarich ~ Manager, Information Services ~ Advanced Photonix /
Picometrix

bspolarich@... ~ 734-864-5618 ~
www.advancedphotonix.com



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Ken Williams
Sent: Wednesday, December 03, 2008 11:18 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Part.Plant



We've been an Epicor customer for over two years now. The first 18
months was on Vista, but then we opened up another plant and needed to
upgrade to Vantage.

The upgrade for the most part has been pretty smooth. Lots of little
issues, but we've worked past them all.

Except one....

We have a parts database that is thousands large. All of these are
currently for one plant only. A large portion of these will need to be
setup in Ashland. As time goes on and new parts are entered, they
potentially need to be in both. This build up leads to two issues:

1. How do we update such a large percentage of parts to the new
plant without going through one at a time?

2. More importantly, if we have demand in plant B but the part is
only setup in plant A, there is no suggestion to purchase it, anywhere.
The part just gets lost in the system, no notification to anyone to do
anything with it (pull it, buy it, make it, etc...).

Any suggestions to tackle these 2 issues would be great,

Ken



.


<http://geo.yahoo.com/serv?s=97359714/grpId=20369/grpspId=1705007181/msg
Id=71554/stime=1228320981/nc1=3848580/nc2=3848643/nc3=5191952>




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