Tracking "Discrepant" Parts

Jennifer - Thanks for the reply, I really appreciate the insight. We
have the QC module but so far have only used it for vendor returns, so I
probably need to investigate it more on how we can use it internally.
Also, the was you label your parts sounds really good for us too.
Thanks for helping to point me in a direction.
-Sarah

-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Jennifer
Sent: Thursday, April 12, 2007 2:33 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Tracking "Discrepant" Parts


Sarah,

We track 'discrepant' parts in a few ways. First, we flow the parts
through the QC module (NC, DMR). Then we segregate the parts and
accept them on a new job number that begins with the letter 'R'. We
usually take the original job number (example: 01234), add an 'R' to
the front of it ('R01234'). This signifies a rework job or a job
that's been passed through MRB with an internal deviation. We use
the comment fields (NC, DMR, new job) to identify exactly what is
wrong with the parts and any other pertinent information. This stands
out clearly on the new job traveler. We have a separate Zebra
printer that contains yellow tags as opposed to plain white. The new
basket tickets are printed on the yellow stock making it obvious to
anyone that there is or was a problem with that particular grouping
of parts.

If you don't want to go through the hassle of creating a new job for
1 or 2 pcs., maybe all you need to do is print out the identification
label/tag on different colored sticker/card stock and have a blank
line added so that the problem can be handwritten on the tag.

We are on v6.1 and are using the Vantage QC Module (Not AQM).

Jennifer Mesiano
DuPAGE Machine

--- In vantage@yahoogroups.com, <sarah.vareschi@...> wrote:
>
> I'm wondering what procedures other companies have in place for
tracking
> 'discrepant' or 'bad' parts? For example, we might be running 20
> components + 2 overruns. At one of our operations, one of those
pieces
> has a problem and is still carried through to be used 'for set-up
only'
> but is not a valid production piece. Or it might be 'discrepant'
> meaning it might be able to be saved. We are trying to determine
the
> best way to (1) identify these pieces and (2) document the history
of
> the piece so the next person picking up the job in the next
workcenter
> can clearly identify a potential problem piece and what and where
the
> problem occurred.
>
> We have issues using vantage electronically for this basically
because
> not sure of the best way to clearly flag the next guy that there is
an
> issue and what the issue is and where it occurred.
>
> Does anyone else have situations like this and if so, would you
share
> your procedures?
>
> Thanks!
> Sarah
>




Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must
have already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder
and Crystal Reports and other 'goodies', please goto:
http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto:
http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto:
http://groups.yahoo.com/group/vantage/links
Yahoo! Groups Links



<DIV><font size="1.5" face="Bookman Old Style">__________________________________________________________________________________________________________________

This email may contain material that is confidential, privileged and/or attorney work product for the sole use of the intended recipient. Any review, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
__________________________________________________________________________________________________________________<DIV><FONT>
Hello,



After Bernie helped confirm my suspicion that there is no adapter that
provides direct access to the PartOpr table I started to wonder if it is
possible to create a Foreign Key View that links to the PartOpr table.



Is it possible to create a Foreign Key View on the Part Maintenance Form
that links to PartOpr?



Thanks,

Joe Rojas

IT Manager

TNCO, Inc.

781-447-6661 x7506

jrojas@...



[Non-text portions of this message have been removed]
Kind of almost need an adapter to get a FKV...

Out of curiosity, what are you trying to achieve?

Bernie.


--- In vantage@yahoogroups.com, "Joe Rojas" <jrojas@...> wrote:
>
> Hello,
>
>
>
> After Bernie helped confirm my suspicion that there is no adapter
that
> provides direct access to the PartOpr table I started to wonder if
it is
> possible to create a Foreign Key View that links to the PartOpr
table.
>
>
>
> Is it possible to create a Foreign Key View on the Part Maintenance
Form
> that links to PartOpr?
>
>
>
> Thanks,
>
> Joe Rojas
>
> IT Manager
>
> TNCO, Inc.
>
> 781-447-6661 x7506
>
> jrojas@...
>
>
>
> [Non-text portions of this message have been removed]
>
We want purchasing to be able to update subcontract operations fields
like Days Out, Unit Cost, and Vendor.

I am trying to bypass having to do this via the Engineering WorkBench.



I want to add like a subcontract tab under revisions that would allow
buyers to make these changes directly to PartOpr.



Thanks,

Joe Rojas

IT Manager

TNCO, Inc.

781-447-6661 x7506

jrojas@...



________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of bw2868bond
Sent: Wednesday, March 07, 2007 12:14 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: V8 - Creating a Foreign Key View to access
PartOpr



Kind of almost need an adapter to get a FKV...

Out of curiosity, what are you trying to achieve?

Bernie.

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> , "Joe
Rojas" <jrojas@...> wrote:
>
> Hello,
>
>
>
> After Bernie helped confirm my suspicion that there is no adapter
that
> provides direct access to the PartOpr table I started to wonder if
it is
> possible to create a Foreign Key View that links to the PartOpr
table.
>
>
>
> Is it possible to create a Foreign Key View on the Part Maintenance
Form
> that links to PartOpr?
>
>
>
> Thanks,
>
> Joe Rojas
>
> IT Manager
>
> TNCO, Inc.
>
> 781-447-6661 x7506
>
> jrojas@...
>
>
>
> [Non-text portions of this message have been removed]
>





[Non-text portions of this message have been removed]
Well, If you just wanted to display data, the BomSearch would do the
trick. Updating it is a entirely different story. I'm thinking the
SDK would be needed to build yourself a PartOper adapter.

Maybe with some tinkering you could use some of the user defined
fields in the part table to 'store' the data you want written to
PartOper and then have a BAM run a .p 'super procedure' to actually
update the table - just a thought...

Bernie.

--- In vantage@yahoogroups.com, "Joe Rojas" <jrojas@...> wrote:
>
> We want purchasing to be able to update subcontract operations
fields
> like Days Out, Unit Cost, and Vendor.
>
> I am trying to bypass having to do this via the Engineering
WorkBench.
>
>
>
> I want to add like a subcontract tab under revisions that would
allow
> buyers to make these changes directly to PartOpr.
>
>
>
> Thanks,
>
> Joe Rojas
>
> IT Manager
>
> TNCO, Inc.
>
> 781-447-6661 x7506
>
> jrojas@...
>
>
>
> ________________________________
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On
Behalf
> Of bw2868bond
> Sent: Wednesday, March 07, 2007 12:14 PM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: V8 - Creating a Foreign Key View to access
> PartOpr
>
>
>
> Kind of almost need an adapter to get a FKV...
>
> Out of curiosity, what are you trying to achieve?
>
> Bernie.
>
> --- In vantage@yahoogroups.com <mailto:vantage%
40yahoogroups.com> , "Joe
> Rojas" <jrojas@> wrote:
> >
> > Hello,
> >
> >
> >
> > After Bernie helped confirm my suspicion that there is no adapter
> that
> > provides direct access to the PartOpr table I started to wonder
if
> it is
> > possible to create a Foreign Key View that links to the PartOpr
> table.
> >
> >
> >
> > Is it possible to create a Foreign Key View on the Part
Maintenance
> Form
> > that links to PartOpr?
> >
> >
> >
> > Thanks,
> >
> > Joe Rojas
> >
> > IT Manager
> >
> > TNCO, Inc.
> >
> > 781-447-6661 x7506
> >
> > jrojas@
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
Hmm, insteresting.

Only problem is that I don't know how to create .p files :-)



Thanks,

Joe Rojas

IT Manager

TNCO, Inc.

781-447-6661 x7506

jrojas@...



________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of bw2868bond
Sent: Wednesday, March 07, 2007 2:50 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: V8 - Creating a Foreign Key View to access
PartOpr



Well, If you just wanted to display data, the BomSearch would do the
trick. Updating it is a entirely different story. I'm thinking the
SDK would be needed to build yourself a PartOper adapter.

Maybe with some tinkering you could use some of the user defined
fields in the part table to 'store' the data you want written to
PartOper and then have a BAM run a .p 'super procedure' to actually
update the table - just a thought...

Bernie.

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> , "Joe
Rojas" <jrojas@...> wrote:
>
> We want purchasing to be able to update subcontract operations
fields
> like Days Out, Unit Cost, and Vendor.
>
> I am trying to bypass having to do this via the Engineering
WorkBench.
>
>
>
> I want to add like a subcontract tab under revisions that would
allow
> buyers to make these changes directly to PartOpr.
>
>
>
> Thanks,
>
> Joe Rojas
>
> IT Manager
>
> TNCO, Inc.
>
> 781-447-6661 x7506
>
> jrojas@...
>
>
>
> ________________________________
>
> From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf
> Of bw2868bond
> Sent: Wednesday, March 07, 2007 12:14 PM
> To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> Subject: [Vantage] Re: V8 - Creating a Foreign Key View to access
> PartOpr
>
>
>
> Kind of almost need an adapter to get a FKV...
>
> Out of curiosity, what are you trying to achieve?
>
> Bernie.
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%
40yahoogroups.com> , "Joe
> Rojas" <jrojas@> wrote:
> >
> > Hello,
> >
> >
> >
> > After Bernie helped confirm my suspicion that there is no adapter
> that
> > provides direct access to the PartOpr table I started to wonder
if
> it is
> > possible to create a Foreign Key View that links to the PartOpr
> table.
> >
> >
> >
> > Is it possible to create a Foreign Key View on the Part
Maintenance
> Form
> > that links to PartOpr?
> >
> >
> >
> > Thanks,
> >
> > Joe Rojas
> >
> > IT Manager
> >
> > TNCO, Inc.
> >
> > 781-447-6661 x7506
> >
> > jrojas@
> >
> >
> >
> > [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]
Sorry, can't help you out much there :-{
I have only made a couple 'simple' .p files to do 'simple' tasks.

I would start however, by turning on tracing and generate a log of
what gets changed when those fields are updated in the Eng Workbench.
Perhaps you may find that you can duplicate the fuctionality in
customization and calling the eng workbench functions although I have
the feeling an awful lot of stuff goes on there....

Sample .p below:

{ud/GlbAlert.i &TableName = "OrderRel"}

DEFINE VARIABLE promDate LIKE MfgSys.OrderDtl.Date02 NO-UNDO.
ASSIGN SendEmail = FALSE.
IF (MfgSys.OrderRel.OrderRelNum = 1)
THEN DO ON ERROR UNDO, LEAVE:
FIND MfgSys.OrderDtl WHERE MfgSys.OrderDtl.Company =
MfgSys.OrderRel.Company
AND MfgSys.OrderDtl.OrderNum = MfgSys.OrderRel.OrderNum
AND MfgSys.OrderDtl.OrderLine = MfgSys.OrderRel.OrderLine NO-LOCK
NO-ERROR.

ASSIGN MfgSys.OrderRel.Date02 = MfgSys.OrderDtl.Date02.

END.

--- In vantage@yahoogroups.com, "Joe Rojas" <jrojas@...> wrote:
>
> Hmm, insteresting.
>
> Only problem is that I don't know how to create .p files :-)
>
>
>
> Thanks,
>
> Joe Rojas
>
> IT Manager
>
> TNCO, Inc.
>
> 781-447-6661 x7506
>
> jrojas@...
>
>
>
> ________________________________
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On
Behalf
> Of bw2868bond
> Sent: Wednesday, March 07, 2007 2:50 PM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: V8 - Creating a Foreign Key View to access
> PartOpr
>
>
>
> Well, If you just wanted to display data, the BomSearch would do
the
> trick. Updating it is a entirely different story. I'm thinking the
> SDK would be needed to build yourself a PartOper adapter.
>
> Maybe with some tinkering you could use some of the user defined
> fields in the part table to 'store' the data you want written to
> PartOper and then have a BAM run a .p 'super procedure' to actually
> update the table - just a thought...
>
> Bernie.
>
> --- In vantage@yahoogroups.com <mailto:vantage%
40yahoogroups.com> , "Joe
> Rojas" <jrojas@> wrote:
> >
> > We want purchasing to be able to update subcontract operations
> fields
> > like Days Out, Unit Cost, and Vendor.
> >
> > I am trying to bypass having to do this via the Engineering
> WorkBench.
> >
> >
> >
> > I want to add like a subcontract tab under revisions that would
> allow
> > buyers to make these changes directly to PartOpr.
> >
> >
> >
> > Thanks,
> >
> > Joe Rojas
> >
> > IT Manager
> >
> > TNCO, Inc.
> >
> > 781-447-6661 x7506
> >
> > jrojas@
> >
> >
> >
> > ________________________________
> >
> > From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> [mailto:vantage@yahoogroups.com <mailto:vantage%
40yahoogroups.com> ] On
> Behalf
> > Of bw2868bond
> > Sent: Wednesday, March 07, 2007 12:14 PM
> > To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> > Subject: [Vantage] Re: V8 - Creating a Foreign Key View to access
> > PartOpr
> >
> >
> >
> > Kind of almost need an adapter to get a FKV...
> >
> > Out of curiosity, what are you trying to achieve?
> >
> > Bernie.
> >
> > --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> <mailto:vantage%
> 40yahoogroups.com> , "Joe
> > Rojas" <jrojas@> wrote:
> > >
> > > Hello,
> > >
> > >
> > >
> > > After Bernie helped confirm my suspicion that there is no
adapter
> > that
> > > provides direct access to the PartOpr table I started to wonder
> if
> > it is
> > > possible to create a Foreign Key View that links to the PartOpr
> > table.
> > >
> > >
> > >
> > > Is it possible to create a Foreign Key View on the Part
> Maintenance
> > Form
> > > that links to PartOpr?
> > >
> > >
> > >
> > > Thanks,
> > >
> > > Joe Rojas
> > >
> > > IT Manager
> > >
> > > TNCO, Inc.
> > >
> > > 781-447-6661 x7506
> > >
> > > jrojas@
> > >
> > >
> > >
> > > [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]
>
Found this in 8.00.811 help :-)

Advanced Customization
The Advanced Customization module will let you create Business
Objects and Adapters against any table. This functionality gives you
even more customization options.

As of this writing, the module is not released yet. To find out if it
is available, contact your account manager.


--- In vantage@yahoogroups.com, "bw2868bond" <bwalker@...> wrote:
>
> Sorry, can't help you out much there :-{
> I have only made a couple 'simple' .p files to do 'simple' tasks.
>
> I would start however, by turning on tracing and generate a log of
> what gets changed when those fields are updated in the Eng
Workbench.
> Perhaps you may find that you can duplicate the fuctionality in
> customization and calling the eng workbench functions although I
have
> the feeling an awful lot of stuff goes on there....
>
> Sample .p below:
>
> {ud/GlbAlert.i &TableName = "OrderRel"}
>
> DEFINE VARIABLE promDate LIKE MfgSys.OrderDtl.Date02 NO-UNDO.
> ASSIGN SendEmail = FALSE.
> IF (MfgSys.OrderRel.OrderRelNum = 1)
> THEN DO ON ERROR UNDO, LEAVE:
> FIND MfgSys.OrderDtl WHERE MfgSys.OrderDtl.Company =
> MfgSys.OrderRel.Company
> AND MfgSys.OrderDtl.OrderNum = MfgSys.OrderRel.OrderNum
> AND MfgSys.OrderDtl.OrderLine = MfgSys.OrderRel.OrderLine NO-
LOCK
> NO-ERROR.
>
> ASSIGN MfgSys.OrderRel.Date02 = MfgSys.OrderDtl.Date02.
>
> END.
>
> --- In vantage@yahoogroups.com, "Joe Rojas" <jrojas@> wrote:
> >
> > Hmm, insteresting.
> >
> > Only problem is that I don't know how to create .p files :-)
> >
> >
> >
> > Thanks,
> >
> > Joe Rojas
> >
> > IT Manager
> >
> > TNCO, Inc.
> >
> > 781-447-6661 x7506
> >
> > jrojas@
> >
> >
> >
> > ________________________________
> >
> > From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On
> Behalf
> > Of bw2868bond
> > Sent: Wednesday, March 07, 2007 2:50 PM
> > To: vantage@yahoogroups.com
> > Subject: [Vantage] Re: V8 - Creating a Foreign Key View to access
> > PartOpr
> >
> >
> >
> > Well, If you just wanted to display data, the BomSearch would do
> the
> > trick. Updating it is a entirely different story. I'm thinking
the
> > SDK would be needed to build yourself a PartOper adapter.
> >
> > Maybe with some tinkering you could use some of the user defined
> > fields in the part table to 'store' the data you want written to
> > PartOper and then have a BAM run a .p 'super procedure' to
actually
> > update the table - just a thought...
> >
> > Bernie.
> >
> > --- In vantage@yahoogroups.com <mailto:vantage%
> 40yahoogroups.com> , "Joe
> > Rojas" <jrojas@> wrote:
> > >
> > > We want purchasing to be able to update subcontract operations
> > fields
> > > like Days Out, Unit Cost, and Vendor.
> > >
> > > I am trying to bypass having to do this via the Engineering
> > WorkBench.
> > >
> > >
> > >
> > > I want to add like a subcontract tab under revisions that would
> > allow
> > > buyers to make these changes directly to PartOpr.
> > >
> > >
> > >
> > > Thanks,
> > >
> > > Joe Rojas
> > >
> > > IT Manager
> > >
> > > TNCO, Inc.
> > >
> > > 781-447-6661 x7506
> > >
> > > jrojas@
> > >
> > >
> > >
> > > ________________________________
> > >
> > > From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> > [mailto:vantage@yahoogroups.com <mailto:vantage%
> 40yahoogroups.com> ] On
> > Behalf
> > > Of bw2868bond
> > > Sent: Wednesday, March 07, 2007 12:14 PM
> > > To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> > > Subject: [Vantage] Re: V8 - Creating a Foreign Key View to
access
> > > PartOpr
> > >
> > >
> > >
> > > Kind of almost need an adapter to get a FKV...
> > >
> > > Out of curiosity, what are you trying to achieve?
> > >
> > > Bernie.
> > >
> > > --- In vantage@yahoogroups.com <mailto:vantage%
40yahoogroups.com>
> > <mailto:vantage%
> > 40yahoogroups.com> , "Joe
> > > Rojas" <jrojas@> wrote:
> > > >
> > > > Hello,
> > > >
> > > >
> > > >
> > > > After Bernie helped confirm my suspicion that there is no
> adapter
> > > that
> > > > provides direct access to the PartOpr table I started to
wonder
> > if
> > > it is
> > > > possible to create a Foreign Key View that links to the
PartOpr
> > > table.
> > > >
> > > >
> > > >
> > > > Is it possible to create a Foreign Key View on the Part
> > Maintenance
> > > Form
> > > > that links to PartOpr?
> > > >
> > > >
> > > >
> > > > Thanks,
> > > >
> > > > Joe Rojas
> > > >
> > > > IT Manager
> > > >
> > > > TNCO, Inc.
> > > >
> > > > 781-447-6661 x7506
> > > >
> > > > jrojas@
> > > >
> > > >
> > > >
> > > > [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]
> >
>
I'm wondering what procedures other companies have in place for tracking
'discrepant' or 'bad' parts? For example, we might be running 20
components + 2 overruns. At one of our operations, one of those pieces
has a problem and is still carried through to be used 'for set-up only'
but is not a valid production piece. Or it might be 'discrepant'
meaning it might be able to be saved. We are trying to determine the
best way to (1) identify these pieces and (2) document the history of
the piece so the next person picking up the job in the next workcenter
can clearly identify a potential problem piece and what and where the
problem occurred.

We have issues using vantage electronically for this basically because
not sure of the best way to clearly flag the next guy that there is an
issue and what the issue is and where it occurred.

Does anyone else have situations like this and if so, would you share
your procedures?

Thanks!
Sarah
Sarah,

We track 'discrepant' parts in a few ways. First, we flow the parts
through the QC module (NC, DMR). Then we segregate the parts and
accept them on a new job number that begins with the letter 'R'. We
usually take the original job number (example: 01234), add an 'R' to
the front of it ('R01234'). This signifies a rework job or a job
that's been passed through MRB with an internal deviation. We use
the comment fields (NC, DMR, new job) to identify exactly what is
wrong with the parts and any other pertinent information. This stands
out clearly on the new job traveler. We have a separate Zebra
printer that contains yellow tags as opposed to plain white. The new
basket tickets are printed on the yellow stock making it obvious to
anyone that there is or was a problem with that particular grouping
of parts.

If you don't want to go through the hassle of creating a new job for
1 or 2 pcs., maybe all you need to do is print out the identification
label/tag on different colored sticker/card stock and have a blank
line added so that the problem can be handwritten on the tag.

We are on v6.1 and are using the Vantage QC Module (Not AQM).

Jennifer Mesiano
DuPAGE Machine

--- In vantage@yahoogroups.com, <sarah.vareschi@...> wrote:
>
> I'm wondering what procedures other companies have in place for
tracking
> 'discrepant' or 'bad' parts? For example, we might be running 20
> components + 2 overruns. At one of our operations, one of those
pieces
> has a problem and is still carried through to be used 'for set-up
only'
> but is not a valid production piece. Or it might be 'discrepant'
> meaning it might be able to be saved. We are trying to determine
the
> best way to (1) identify these pieces and (2) document the history
of
> the piece so the next person picking up the job in the next
workcenter
> can clearly identify a potential problem piece and what and where
the
> problem occurred.
>
> We have issues using vantage electronically for this basically
because
> not sure of the best way to clearly flag the next guy that there is
an
> issue and what the issue is and where it occurred.
>
> Does anyone else have situations like this and if so, would you
share
> your procedures?
>
> Thanks!
> Sarah
>