Thank you, I suspect this is what is going on, so I will pass this informatin along to my purchasing person. I'll verify this next time we have multiple subcontract PO's.
Â
Thanks again.
Â
Barbara
Â
Thanks again.
Â
Barbara
--- On Fri, 6/27/08, jplehr <jlehr@...> wrote:
From: jplehr <jlehr@...>
Subject: [Vantage] Re:Subcontract PO's
To: vantage@yahoogroups.com
Date: Friday, June 27, 2008, 2:48 PM
Vantage V. 8.03.305L
This may sound strange, but with what you said in your last couple
sentences I thought it is worth mentioning. This is what I have
experienced, on rare occassions.. .<I am not saying I have seen this
in P.O. Entry but will use it as an example>...
I create my first P.O.; I then move on to create my second P.O.
simply by selecting "File>New>New PO". This is where I have seen the
new P.O. retain information from the previous P.O. To resolve this I
started "Clearing" my form and the select "File>New>New PO". I
haven't seen or heard of any further issues.
Again, you may think I am crazy, but that is all I could see in my
research. May be worth looking at as you watch the process at hand.
--- In vantage@yahoogroups .com, Barbara Kite <barken2008@ ...> wrote:
>
> Rob
> Â
> No we do not have MRP as part of our package. I've asked my
purchasing person that the next time she is ready to prepare another
subcontract PO to call me and I want to watch what she is doing.Â
Today I looked at a couple that she did last week and I asked her
what part number was coming up on the PO instead of the part from
the job.  I then did a transaction history on the part number and
discovered that the part was from an earlier subcontract PO she did
that same day...mmmm, makes me wonder if the reason why we were not
having problems before is because she was only doing one subcontract
PO on a single day and when she runs multiple subcontract PO's on the
same day, if the system isn't pulling a part number from an earlier
PO created that day. This is what I want to verify the next time she
needs to issue them.Â
> Â
> Barbara
>
> --- On Thu, 6/26/08, Robert Brown <robertb_versa@ ...> wrote:
>
> From: Robert Brown <robertb_versa@ ...>
> Subject: Re: [Vantage] Re:Subcontract PO's
> To: vantage@yahoogroups .com
> Date: Thursday, June 26, 2008, 8:47 PM
>
>
>
>
>
>
> Barbara,
>
> You are not running MRP or the Global with any future date fence
are you?
>
> If so, your 'fence' may be the cause behind some jobs not properly
subcontract processing versus others that do (that are within your
fence).
>
> I'd verify that simple thing before going into the Vendor/Part/
PriceList and MoM research I recommended below.
>
> Rob Brown
>
> --- On Thu, 6/26/08, Robert Brown <robertb_versa@ yahoo.com> wrote:
> From: Robert Brown <robertb_versa@ yahoo.com>
> Subject: Re: [Vantage] Re:Subcontract PO's
> To: vantage@yahoogroups .com
> Date: Thursday, June 26, 2008, 4:32 PM
>
> Make sure you have an approved vendor set up with a price list for
your subcontract part (or subcontract Std Op if you aren't carrying a
redunent "service" part number in your MoMs).
>
> Then look at your methods. Compare all of the ones that you know
have generated jobs with details containing subcontract Ops
that 'work' versus those you know that resulted in Jobs that
misbehave re subcontract processing.
>
> I'd bet money that there is at least one clear difference between
the two groups of MoMs when you compare them.
>
> Make them (and all your MoMs containing subcontract Ops) conform to
the ones that have 'worked' in the past.
>
> Rob Brown
>
> --- On Thu, 6/26/08, barken2008 <barken2008@ yahoo. com> wrote:
>
> From: barken2008 <barken2008@ yahoo. com>
>
> Subject: [Vantage] Re:Subcontract PO's
>
> To: vantage@yahoogroups .com
>
> Date: Thursday, June 26, 2008, 2:28 PM
>
> In the job we have the operation as a subcontract operation . This
is
>
> a new issue with us as we've been doing subcontract operations for
>
> quite some time and then creating the subcontract PO. When we open
up
>
> a new PO and label it a subcontract PO, we put in the job number
and
>
> then go to the Mtl button to pull in the material from the job.
This
>
> is supposed to bring in the correct part number from the job, but
for
>
> some reason, it is not doing it. I've also found that it works
>
> correctly on some PO's but not on all P.O's, so it's a hit and miss
on
>
> whether or not it's going to pull the correct part number. I just
am
>
> at a loss on what to look for.
>
> Barbara
>
> --- In vantage@yahoogroups .com, RSN <rsnsfi@> wrote:
>
> >
>
> > Ms. Kite,
>
> > Which operation are you writing the PO to. Is there a part#
defined
>
> at the operation. then this part# supercedes the Job production
part#.
>
> > Thx
>
> > RSN
>
> >
>
> >
>
> >
>
> > [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]