Lot Tracking

system · June 27, 2008, 4:18am

Note sure if this will help:-

We also use lot tracking for many of our parts. Vantage doesn't have
the capability to auto-generate a next lot number, and having a
number of goods receiving operators meant that it was difficult to
decide what the next lot number would be. We would have to record it
off-system somewhere, and this was going to be a pain to manage.

I therefore added a button to the receipt entry form which calculates
a lot number based on a date and time code. In fact I use the
following format: "080627/45567". The first 6-digits are the year,
the month and the day, and the last 5 digits are the number of
seconds which elapsed since midnight. Hence lot numbers are specific
to the date and time the part was entered ( at a resolution of 1-
second ). Ok, we will have a problem if two people enter parts at
exactly the same time, but that has never happened yet :o)

Therefore when the goods receiving operator enters the next part,
they click my "Get Lot Number" button, and the next lot number is
generated and stored in the field.

We find this works pretty well...

I hope this helps!

Nick Taylor

--- In vantage@yahoogroups.com, "eltaria.foong" <eltaria.foong@...>
wrote:

>
> Hi, I've been thinking about Lot Tracking in Vantage too.
>
> Someone mentioned they use Job Number as lot number, let's say i

have

> a Job 000090 which runs for a month, during the course of the
> production, I've received 2 different lot of the same materials,

lot A

> 56,000 and lot B 44,000.
>
> If I saved the finished good under Lot 000090, and 1 month down the
> road the supplier called and said Lot A is problematic, seems like
> I'll have to recall the entire batch of 000090?
>
> How would we be able to best handle this then?
> I was thinking of using 000090-1, 000090-2, 000090-3 and so on until
> the last run.
>
> Of course, there may be a possibility that a part of the job will be
> taking in 2 lots of materials, but at least we would've kept it down
> to a minimum, instead of recalling the entire batch of 100,000 in

job

> 000090?
>
>
> --- In vantage@yahoogroups.com, "Manasa Reddy" <manasa@> wrote:
> >
> > Each labor detail record has a unique number...maybe you can use

that

> > field on the shipment somehow as your traceability.
> >
> >
> >
> > Something to look at maybe....?????
> >
> >
> >
> >
> >
> >
> >
> > M. Manasa Reddy
> >
> > manasa@
> >
> > P: 630-806-2000
> >
> > F: 630-806-2001
> >
> > ________________________________
> >
> > From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On

Behalf

> > Of Arnulfo Mora
> > Sent: Tuesday, November 13, 2007 10:45 AM
> > To: vantage@yahoogroups.com
> > Subject: [Vantage] Re: Lot Tracking
> >
> >
> >
> > What we are currently planning is to use MES to report quantities

in

> > the basket. When the operator finish a basket they will hit report
> > quantity in MES, print tag, and send it on to the next operation

or to

> > shipping. For ASN's, we are required to have a unique number on

each

> > shipment. With what we can currently tell, we will not be able to

put

> > a unique number on the shipping tag for traceability. This is a
> > requirement for many automotive companies. This unique number is

used

> > to track back to the exact time, date, steel coil, operator, etc.

when

> > a customer calls in with a concern/rejection. We would use the

serial

> > number for containment of all baskets created under a certain

steel

> > tag number, after a certain number of hits, or any other items

that

> > may be suspect. The unique number is the trigger for all
> > correspondence with our customer. In essence, we need to serialize
> > every container (basket), but not every part. If you have any
> > additional questions, please let me know.
> >
> > Thanks in Advance,
> >
> > Eric
> >
> >
> > --- In vantage@yahoogroups.com <mailto:vantage%

40yahoogroups.com> ,

> > "Michael McWilliams"
> > <mmcwilliams22@> wrote:
> > >
> > > Right now they are in Numeric fields. Every receipt line is a
> > > new "Lot" basically serial but not exactly. That number is

generated

> > > by getting the next number from a UD table & creating a
> > > corresponding UD record. It then takes the numbers that you

entered

> > > and pushes them into the UD table. I am working on a

verification

> > > that will only allow you to enter if the properties are within
> > > acceptable values.
> > >
> > > We are required to have a "Bundle" number on our shipping tags.
> > > Every bundle gets a unique number. Since you are creating

baskets

> > > of parts I do not belive that the Vantage serialization will

work.

> > > It wants you to give a uniqe number to every unit that is

created.

> > > I have a question about your creation of baskets. Do you use

MES to

> > > do this or will it be done in the office?
> > > --- In vantage@yahoogroups.com <mailto:vantage%

40yahoogroups.com> ,

> > "Arnulfo Mora" <amora@> wrote:
> > > >
> > > > Mr. McWilliams,
> > > >
> > > > How are you entering all of the Physical and Chemical

properties

> > > into
> > > > Vantage? Are you just dumping the information into a text

field,

> > > or
> > > > are you taking that information and verifying it against a

material

> > > > specification? Also, are you required to have a serial number

on

> > > your
> > > > shipping tags? We are currently implementing Vantage and are
> > > looking
> > > > for a way to use a serial number to track individual baskets

of

> > > parts
> > > > shipped to our customer. The serial number would be a self
> > > > populating, unique, sequential number. Thanks for any

information

> > > in
> > > > advance.
> > > >
> > > > Eric
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>

system · June 27, 2008, 12:34pm

Lot Tracking is a very good tool for keeping a record of daily or "runs" of
production for Items or groups of items that need to be tracked for a
multiple of reasons. Lot Tracking is a manual tracking method and is not
designed for generating a unique number for each item. If you are in need
of uniquely identifying each item made take a look at serial numbers.
Serial numbers are a great way to guarantee that every item produced has its
own identification that you can access at any time now and in the future.
There IS more work involved by using them but in many cases well worth the
extra effort. Ask your CAM or call me for more information if you are
interested.

Thank you,

Kevin Kadamus

Senior Consultant

Epicor Authorized Partner

kkadamus@...

952-905-0387

CONFIDENTIALITY NOTICE: This electronic email transmission may contain
consultant/client privilege and confidential information intended only for
the individual or entity named above. Any dissemination, use, distribution,
copying or disclosure of this communication by any other person or entity is
strictly prohibited. Should you receive this transmission in error, please
notify the sender by telephone at 952-905-0387.

_____

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
nmtaylor1969
Sent: Friday, June 27, 2008 4:18 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Lot Tracking

Note sure if this will help:-

We also use lot tracking for many of our parts. Vantage doesn't have
the capability to auto-generate a next lot number, and having a
number of goods receiving operators meant that it was difficult to
decide what the next lot number would be. We would have to record it
off-system somewhere, and this was going to be a pain to manage.

I therefore added a button to the receipt entry form which calculates
a lot number based on a date and time code. In fact I use the
following format: "080627/45567". The first 6-digits are the year,
the month and the day, and the last 5 digits are the number of
seconds which elapsed since midnight. Hence lot numbers are specific
to the date and time the part was entered ( at a resolution of 1-
second ). Ok, we will have a problem if two people enter parts at
exactly the same time, but that has never happened yet :o)

Therefore when the goods receiving operator enters the next part,
they click my "Get Lot Number" button, and the next lot number is
generated and stored in the field.

We find this works pretty well...

I hope this helps!

Nick Taylor

--- In vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com,
"eltaria.foong" <eltaria.foong@...>
wrote:

>
> Hi, I've been thinking about Lot Tracking in Vantage too.
>
> Someone mentioned they use Job Number as lot number, let's say i

have

> a Job 000090 which runs for a month, during the course of the
> production, I've received 2 different lot of the same materials,

lot A

> 56,000 and lot B 44,000.
>
> If I saved the finished good under Lot 000090, and 1 month down the
> road the supplier called and said Lot A is problematic, seems like
> I'll have to recall the entire batch of 000090?
>
> How would we be able to best handle this then?
> I was thinking of using 000090-1, 000090-2, 000090-3 and so on until
> the last run.
>
> Of course, there may be a possibility that a part of the job will be
> taking in 2 lots of materials, but at least we would've kept it down
> to a minimum, instead of recalling the entire batch of 100,000 in

job

> 000090?
>
>
> --- In vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com,

"Manasa Reddy" <manasa@> wrote:

> >
> > Each labor detail record has a unique number...maybe you can use

that

> > field on the shipment somehow as your traceability.
> >
> >
> >
> > Something to look at maybe....?????
> >
> >
> >
> >
> >
> >
> >
> > M. Manasa Reddy
> >
> > manasa@
> >
> > P: 630-806-2000
> >
> > F: 630-806-2001
> >
> > ________________________________
> >
> > From: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com

[mailto:vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com] On
Behalf

> > Of Arnulfo Mora
> > Sent: Tuesday, November 13, 2007 10:45 AM
> > To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
> > Subject: [Vantage] Re: Lot Tracking
> >
> >
> >
> > What we are currently planning is to use MES to report quantities

in

> > the basket. When the operator finish a basket they will hit report
> > quantity in MES, print tag, and send it on to the next operation

or to

> > shipping. For ASN's, we are required to have a unique number on

each

> > shipment. With what we can currently tell, we will not be able to

put

> > a unique number on the shipping tag for traceability. This is a
> > requirement for many automotive companies. This unique number is

used

> > to track back to the exact time, date, steel coil, operator, etc.

when

> > a customer calls in with a concern/rejection. We would use the

serial

> > number for containment of all baskets created under a certain

steel

> > tag number, after a certain number of hits, or any other items

that

> > may be suspect. The unique number is the trigger for all
> > correspondence with our customer. In essence, we need to serialize
> > every container (basket), but not every part. If you have any
> > additional questions, please let me know.
> >
> > Thanks in Advance,
> >
> > Eric
> >
> >
> > --- In vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com

<mailto:vantage%
40yahoogroups.com> ,

> > "Michael McWilliams"
> > <mmcwilliams22@> wrote:
> > >
> > > Right now they are in Numeric fields. Every receipt line is a
> > > new "Lot" basically serial but not exactly. That number is

generated

> > > by getting the next number from a UD table & creating a
> > > corresponding UD record. It then takes the numbers that you

entered

> > > and pushes them into the UD table. I am working on a

verification

> > > that will only allow you to enter if the properties are within
> > > acceptable values.
> > >
> > > We are required to have a "Bundle" number on our shipping tags.
> > > Every bundle gets a unique number. Since you are creating

baskets

> > > of parts I do not belive that the Vantage serialization will

work.

> > > It wants you to give a uniqe number to every unit that is

created.

> > > I have a question about your creation of baskets. Do you use

MES to

> > > do this or will it be done in the office?
> > > --- In vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com

<mailto:vantage%
40yahoogroups.com> ,

> > "Arnulfo Mora" <amora@> wrote:
> > > >
> > > > Mr. McWilliams,
> > > >
> > > > How are you entering all of the Physical and Chemical

properties

> > > into
> > > > Vantage? Are you just dumping the information into a text

field,

> > > or
> > > > are you taking that information and verifying it against a

material

> > > > specification? Also, are you required to have a serial number

on

> > > your
> > > > shipping tags? We are currently implementing Vantage and are
> > > looking
> > > > for a way to use a serial number to track individual baskets

of

> > > parts
> > > > shipped to our customer. The serial number would be a self
> > > > populating, unique, sequential number. Thanks for any

information

> > > in
> > > > advance.
> > > >
> > > > Eric
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>

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

system · June 28, 2008, 2:37am

I agree with your comments. Just to remove any ambiguity, we use
serial number tracking for all appropriate manufactured parts that we
make in-house, and we use lot-tracking for material receipts coming
in from vendors. Currently every receipt line will get a different
lot number, but I guess in reality we could probably make a lot
number apply to all lines on a specific receipt. ( I haven't tried
this, so I dont know if Vahtage will allow different parts to exist
within one lot ). We merely wish to know where any given part came
from in the event we have a field failure etc. A lot number based on
a date and time code works well in our particular application.

--- In vantage@yahoogroups.com, "Kevin Kadamus" <kkadamus@...> wrote:
>
> Lot Tracking is a very good tool for keeping a record of daily
or "runs" of
> production for Items or groups of items that need to be tracked for
a
> multiple of reasons. Lot Tracking is a manual tracking method and
is not
> designed for generating a unique number for each item. If you are
in need
> of uniquely identifying each item made take a look at serial
numbers.
> Serial numbers are a great way to guarantee that every item
produced has its
> own identification that you can access at any time now and in the
future.
> There IS more work involved by using them but in many cases well
worth the
> extra effort. Ask your CAM or call me for more information if you
are
> interested.
>
>
>
>
>
> Thank you,
>
>
>
>
>
> Kevin Kadamus
>
> Senior Consultant
>
> Epicor Authorized Partner
>
>
>
> kkadamus@...
>
> 952-905-0387
>
>
>
> CONFIDENTIALITY NOTICE: This electronic email transmission may
contain
> consultant/client privilege and confidential information intended
only for
> the individual or entity named above. Any dissemination, use,
distribution,
> copying or disclosure of this communication by any other person or
entity is
> strictly prohibited. Should you receive this transmission in error,
please
> notify the sender by telephone at 952-905-0387.
>
> _____
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On
Behalf Of
> nmtaylor1969
> Sent: Friday, June 27, 2008 4:18 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: Lot Tracking
>
>
>
> Note sure if this will help:-
>
> We also use lot tracking for many of our parts. Vantage doesn't
have
> the capability to auto-generate a next lot number, and having a
> number of goods receiving operators meant that it was difficult to
> decide what the next lot number would be. We would have to record
it
> off-system somewhere, and this was going to be a pain to manage.
>
> I therefore added a button to the receipt entry form which
calculates
> a lot number based on a date and time code. In fact I use the
> following format: "080627/45567". The first 6-digits are the year,
> the month and the day, and the last 5 digits are the number of
> seconds which elapsed since midnight. Hence lot numbers are
specific
> to the date and time the part was entered ( at a resolution of 1-
> second ). Ok, we will have a problem if two people enter parts at
> exactly the same time, but that has never happened yet :o)
>
> Therefore when the goods receiving operator enters the next part,
> they click my "Get Lot Number" button, and the next lot number is
> generated and stored in the field.
>
> We find this works pretty well...
>
> I hope this helps!
>
> Nick Taylor
>
> --- In vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com,
> "eltaria.foong" <eltaria.foong@>
> wrote:
> >
> > Hi, I've been thinking about Lot Tracking in Vantage too.
> >
> > Someone mentioned they use Job Number as lot number, let's say i
> have
> > a Job 000090 which runs for a month, during the course of the
> > production, I've received 2 different lot of the same materials,
> lot A
> > 56,000 and lot B 44,000.
> >
> > If I saved the finished good under Lot 000090, and 1 month down
the
> > road the supplier called and said Lot A is problematic, seems like
> > I'll have to recall the entire batch of 000090?
> >
> > How would we be able to best handle this then?
> > I was thinking of using 000090-1, 000090-2, 000090-3 and so on
until
> > the last run.
> >
> > Of course, there may be a possibility that a part of the job will
be
> > taking in 2 lots of materials, but at least we would've kept it
down
> > to a minimum, instead of recalling the entire batch of 100,000 in
> job
> > 000090?
> >
> >
> > --- In vantage@yahoogroups <mailto:vantage%
40yahoogroups.com> .com,
> "Manasa Reddy" <manasa@> wrote:
> > >
> > > Each labor detail record has a unique number...maybe you can
use
> that
> > > field on the shipment somehow as your traceability.
> > >
> > >
> > >
> > > Something to look at maybe....?????
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > M. Manasa Reddy
> > >
> > > manasa@
> > >
> > > P: 630-806-2000
> > >
> > > F: 630-806-2001
> > >
> > > ________________________________
> > >
> > > From: vantage@yahoogroups <mailto:vantage%
40yahoogroups.com> .com
> [mailto:vantage@yahoogroups <mailto:vantage%
40yahoogroups.com> .com] On
> Behalf
> > > Of Arnulfo Mora
> > > Sent: Tuesday, November 13, 2007 10:45 AM
> > > To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
> > > Subject: [Vantage] Re: Lot Tracking
> > >
> > >
> > >
> > > What we are currently planning is to use MES to report
quantities
> in
> > > the basket. When the operator finish a basket they will hit
report
> > > quantity in MES, print tag, and send it on to the next
operation
> or to
> > > shipping. For ASN's, we are required to have a unique number on
> each
> > > shipment. With what we can currently tell, we will not be able
to
> put
> > > a unique number on the shipping tag for traceability. This is a
> > > requirement for many automotive companies. This unique number
is
> used
> > > to track back to the exact time, date, steel coil, operator,
etc.
> when
> > > a customer calls in with a concern/rejection. We would use the
> serial
> > > number for containment of all baskets created under a certain
> steel
> > > tag number, after a certain number of hits, or any other items
> that
> > > may be suspect. The unique number is the trigger for all
> > > correspondence with our customer. In essence, we need to
serialize
> > > every container (basket), but not every part. If you have any
> > > additional questions, please let me know.
> > >
> > > Thanks in Advance,
> > >
> > > Eric
> > >
> > >
> > > --- In vantage@yahoogroups <mailto:vantage%
40yahoogroups.com> .com
> <mailto:vantage%
> 40yahoogroups.com> ,
> > > "Michael McWilliams"
> > > <mmcwilliams22@> wrote:
> > > >
> > > > Right now they are in Numeric fields. Every receipt line is a
> > > > new "Lot" basically serial but not exactly. That number is
> generated
> > > > by getting the next number from a UD table & creating a
> > > > corresponding UD record. It then takes the numbers that you
> entered
> > > > and pushes them into the UD table. I am working on a
> verification
> > > > that will only allow you to enter if the properties are
within
> > > > acceptable values.
> > > >
> > > > We are required to have a "Bundle" number on our shipping
tags.
> > > > Every bundle gets a unique number. Since you are creating
> baskets
> > > > of parts I do not belive that the Vantage serialization will
> work.
> > > > It wants you to give a uniqe number to every unit that is
> created.
> > > > I have a question about your creation of baskets. Do you use
> MES to
> > > > do this or will it be done in the office?
> > > > --- In vantage@yahoogroups <mailto:vantage%
40yahoogroups.com> .com
> <mailto:vantage%
> 40yahoogroups.com> ,
> > > "Arnulfo Mora" <amora@> wrote:
> > > > >
> > > > > Mr. McWilliams,
> > > > >
> > > > > How are you entering all of the Physical and Chemical
> properties
> > > > into
> > > > > Vantage? Are you just dumping the information into a text
> field,
> > > > or
> > > > > are you taking that information and verifying it against a
> material
> > > > > specification? Also, are you required to have a serial
number
> on
> > > > your
> > > > > shipping tags? We are currently implementing Vantage and
are
> > > > looking
> > > > > for a way to use a serial number to track individual
baskets
> of
> > > > parts
> > > > > shipped to our customer. The serial number would be a self
> > > > > populating, unique, sequential number. Thanks for any
> information
> > > > in
> > > > > advance.
> > > > >
> > > > > Eric
> > >
> > >
> > >
> > >
> > >
> > > [Non-text portions of this message have been removed]
> > >
> >
>
>
>
>
>
> [Non-text portions of this message have been removed]
>

system · July 12, 2008, 10:10am

Nick,
Your Date/Timestamp lot numbering is an excellent idea that I would like to use as we implement Vantage here. Would you be willing to share your code for your Receipt Entry button to generate your Lot numbers?

Thanks,
Ed

________________________________
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of nmtaylor1969
Sent: Saturday, June 28, 2008 1:38 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Lot Tracking

I agree with your comments. Just to remove any ambiguity, we use
serial number tracking for all appropriate manufactured parts that we
make in-house, and we use lot-tracking for material receipts coming
in from vendors. Currently every receipt line will get a different
lot number, but I guess in reality we could probably make a lot
number apply to all lines on a specific receipt. ( I haven't tried
this, so I dont know if Vahtage will allow different parts to exist
within one lot ). We merely wish to know where any given part came
from in the event we have a field failure etc. A lot number based on
a date and time code works well in our particular application.

--- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>, "Kevin Kadamus" <kkadamus@...> wrote:
>
> Lot Tracking is a very good tool for keeping a record of daily
or "runs" of
> production for Items or groups of items that need to be tracked for
a
> multiple of reasons. Lot Tracking is a manual tracking method and
is not
> designed for generating a unique number for each item. If you are
in need
> of uniquely identifying each item made take a look at serial
numbers.
> Serial numbers are a great way to guarantee that every item
produced has its
> own identification that you can access at any time now and in the
future.
> There IS more work involved by using them but in many cases well
worth the
> extra effort. Ask your CAM or call me for more information if you
are
> interested.
>
>
>
>
>
> Thank you,
>
>
>
>
>
> Kevin Kadamus
>
> Senior Consultant
>
> Epicor Authorized Partner
>
>
>
> kkadamus@...
>
> 952-905-0387
>
>
>
> CONFIDENTIALITY NOTICE: This electronic email transmission may
contain
> consultant/client privilege and confidential information intended
only for
> the individual or entity named above. Any dissemination, use,
distribution,
> copying or disclosure of this communication by any other person or
entity is
> strictly prohibited. Should you receive this transmission in error,
please
> notify the sender by telephone at 952-905-0387.
>
> _____
>
> From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On
Behalf Of
> nmtaylor1969
> Sent: Friday, June 27, 2008 4:18 AM
> To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
> Subject: [Vantage] Re: Lot Tracking
>
>
>
> Note sure if this will help:-
>
> We also use lot tracking for many of our parts. Vantage doesn't
have
> the capability to auto-generate a next lot number, and having a
> number of goods receiving operators meant that it was difficult to
> decide what the next lot number would be. We would have to record
it
> off-system somewhere, and this was going to be a pain to manage.
>
> I therefore added a button to the receipt entry form which
calculates
> a lot number based on a date and time code. In fact I use the
> following format: "080627/45567". The first 6-digits are the year,
> the month and the day, and the last 5 digits are the number of
> seconds which elapsed since midnight. Hence lot numbers are
specific
> to the date and time the part was entered ( at a resolution of 1-
> second ). Ok, we will have a problem if two people enter parts at
> exactly the same time, but that has never happened yet :o)
>
> Therefore when the goods receiving operator enters the next part,
> they click my "Get Lot Number" button, and the next lot number is
> generated and stored in the field.
>
> We find this works pretty well...
>
> I hope this helps!
>
> Nick Taylor
>
> --- In vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com,
> "eltaria.foong" <eltaria.foong@>
> wrote:
> >
> > Hi, I've been thinking about Lot Tracking in Vantage too.
> >
> > Someone mentioned they use Job Number as lot number, let's say i
> have
> > a Job 000090 which runs for a month, during the course of the
> > production, I've received 2 different lot of the same materials,
> lot A
> > 56,000 and lot B 44,000.
> >
> > If I saved the finished good under Lot 000090, and 1 month down
the
> > road the supplier called and said Lot A is problematic, seems like
> > I'll have to recall the entire batch of 000090?
> >
> > How would we be able to best handle this then?
> > I was thinking of using 000090-1, 000090-2, 000090-3 and so on
until
> > the last run.
> >
> > Of course, there may be a possibility that a part of the job will
be
> > taking in 2 lots of materials, but at least we would've kept it
down
> > to a minimum, instead of recalling the entire batch of 100,000 in
> job
> > 000090?
> >
> >
> > --- In vantage@yahoogroups <mailto:vantage%
40yahoogroups.com> .com,
> "Manasa Reddy" <manasa@> wrote:
> > >
> > > Each labor detail record has a unique number...maybe you can
use
> that
> > > field on the shipment somehow as your traceability.
> > >
> > >
> > >
> > > Something to look at maybe....?????
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > M. Manasa Reddy
> > >
> > > manasa@
> > >
> > > P: 630-806-2000
> > >
> > > F: 630-806-2001
> > >
> > > ________________________________
> > >
> > > From: vantage@yahoogroups <mailto:vantage%
40yahoogroups.com> .com
> [mailto:vantage@yahoogroups <mailto:vantage%
40yahoogroups.com> .com] On
> Behalf
> > > Of Arnulfo Mora
> > > Sent: Tuesday, November 13, 2007 10:45 AM
> > > To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
> > > Subject: [Vantage] Re: Lot Tracking
> > >
> > >
> > >
> > > What we are currently planning is to use MES to report
quantities
> in
> > > the basket. When the operator finish a basket they will hit
report
> > > quantity in MES, print tag, and send it on to the next
operation
> or to
> > > shipping. For ASN's, we are required to have a unique number on
> each
> > > shipment. With what we can currently tell, we will not be able
to
> put
> > > a unique number on the shipping tag for traceability. This is a
> > > requirement for many automotive companies. This unique number
is
> used
> > > to track back to the exact time, date, steel coil, operator,
etc.
> when
> > > a customer calls in with a concern/rejection. We would use the
> serial
> > > number for containment of all baskets created under a certain
> steel
> > > tag number, after a certain number of hits, or any other items
> that
> > > may be suspect. The unique number is the trigger for all
> > > correspondence with our customer. In essence, we need to
serialize
> > > every container (basket), but not every part. If you have any
> > > additional questions, please let me know.
> > >
> > > Thanks in Advance,
> > >
> > > Eric
> > >
> > >
> > > --- In vantage@yahoogroups <mailto:vantage%
40yahoogroups.com> .com
> <mailto:vantage%
> 40yahoogroups.com> ,
> > > "Michael McWilliams"
> > > <mmcwilliams22@> wrote:
> > > >
> > > > Right now they are in Numeric fields. Every receipt line is a
> > > > new "Lot" basically serial but not exactly. That number is
> generated
> > > > by getting the next number from a UD table & creating a
> > > > corresponding UD record. It then takes the numbers that you
> entered
> > > > and pushes them into the UD table. I am working on a
> verification
> > > > that will only allow you to enter if the properties are
within
> > > > acceptable values.
> > > >
> > > > We are required to have a "Bundle" number on our shipping
tags.
> > > > Every bundle gets a unique number. Since you are creating
> baskets
> > > > of parts I do not belive that the Vantage serialization will
> work.
> > > > It wants you to give a uniqe number to every unit that is
> created.
> > > > I have a question about your creation of baskets. Do you use
> MES to
> > > > do this or will it be done in the office?
> > > > --- In vantage@yahoogroups <mailto:vantage%
40yahoogroups.com> .com
> <mailto:vantage%
> 40yahoogroups.com> ,
> > > "Arnulfo Mora" <amora@> wrote:
> > > > >
> > > > > Mr. McWilliams,
> > > > >
> > > > > How are you entering all of the Physical and Chemical
> properties
> > > > into
> > > > > Vantage? Are you just dumping the information into a text
> field,
> > > > or
> > > > > are you taking that information and verifying it against a
> material
> > > > > specification? Also, are you required to have a serial
number
> on
> > > > your
> > > > > shipping tags? We are currently implementing Vantage and
are
> > > > looking
> > > > > for a way to use a serial number to track individual
baskets
> of
> > > > parts
> > > > > shipped to our customer. The serial number would be a self
> > > > > populating, unique, sequential number. Thanks for any
> information
> > > > in
> > > > > advance.
> > > > >
> > > > > Eric
> > >
> > >
> > >
> > >
> > >
> > > [Non-text portions of this message have been removed]
> > >
> >
>
>
>
>
>
> [Non-text portions of this message have been removed]
>

________________________________
The information contained in this message is intended solely for the individual to whom it is specifically and originally addressed. This message and its contents may contain confidential or privileged information. If you are not the intended recipient, you are hereby notified that any disclosure or distribution, or taking any action in reliance on the contents of this information, is strictly prohibited.
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 cannot accept liability for any loss or damage caused by software viruses.

This message (including any attachments) is intended only for
the use of the individual or entity to which it is addressed and
may contain information that is non-public, proprietary,
privileged, confidential, and exempt from disclosure under
applicable law or may constitute as attorney work product.
If you are not the intended recipient, you are hereby notified
that any use, dissemination, distribution, or copying of this
communication is strictly prohibited. If you have received this
communication in error, notify us immediately by telephone and
(i) destroy this message if a facsimile or (ii) delete this message
immediately if this is an electronic communication.

Thank you.

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

system · July 12, 2008, 1:06pm

Ok Ed, here you go...

I am assuming you are ok with the basic customisation stuff. You will
need to add a new command button into the "Stock" tab which is going
to replace the existing "Get Lot Receipt" button. You will need to
move the x,y location of the old button off screen somewhere as
making it invisible doesn't work. It just comes back to haunt you
when you run the form for real :o(

Into the click() event code of your new button you will need the
following code:-

Dim edvStockDtl As EpiDataView = CType(oTrans.EpiDataViews
("StockDtl"), EpiDataView)
if not edvStockDtl.HasRow then exit sub
edvStockDtl.dataView(edvStockDtl.Row).BeginEdit()
edvStockDtl.dataView(edvStockDtl.Row)("LotNum") = format
(datetime.now,"yyMMdd") + "/" + format
(Date.Now.TimeOfDay.TotalSeconds,"00000" ).ToString()
edvStockDtl.dataView(edvStockDtl.Row).EndEdit()
oTrans.NotifyAll()

This will handle the receipt of inventory items. If you want to lot
trace your buy direct stuff you will need to add a similar button to
the "Job Material" tab. This time however you will need to reference
the JobMtlDtl data view and not the StockDtl data view.

I played around with having a single method to create the lot number
and just call this from each button ( for example you might need a
3rd button for sub-contract material ), but I hit problems. As I was
under pressure to get something working I left the code alone and
just had three buttons each generating the lot number string. This
works fine.

I used this methodology in a previous system which has run for the
last 20-years. Unless 2 or more operators hit the button at exactly
the same second in the same day you will get unique lot numbers. It
works well for us.

Have fun :o)

Nick

--- In vantage@yahoogroups.com, Ed Garbowski <egarbowski@...> wrote:
>
> Nick,
> Your Date/Timestamp lot numbering is an excellent idea that I
would like to use as we implement Vantage here. Would you be willing
to share your code for your Receipt Entry button to generate your Lot
numbers?
>
> Thanks,
> Ed
>
>
> ________________________________
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On
Behalf Of nmtaylor1969
> Sent: Saturday, June 28, 2008 1:38 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: Lot Tracking
>
>
> I agree with your comments. Just to remove any ambiguity, we use
> serial number tracking for all appropriate manufactured parts that
we
> make in-house, and we use lot-tracking for material receipts coming
> in from vendors. Currently every receipt line will get a different
> lot number, but I guess in reality we could probably make a lot
> number apply to all lines on a specific receipt. ( I haven't tried
> this, so I dont know if Vahtage will allow different parts to exist
> within one lot ). We merely wish to know where any given part came
> from in the event we have a field failure etc. A lot number based on
> a date and time code works well in our particular application.
>
> --- In vantage@yahoogroups.com<mailto:vantage%
40yahoogroups.com>, "Kevin Kadamus" <kkadamus@> wrote:
> >
> > Lot Tracking is a very good tool for keeping a record of daily
> or "runs" of
> > production for Items or groups of items that need to be tracked
for
> a
> > multiple of reasons. Lot Tracking is a manual tracking method and
> is not
> > designed for generating a unique number for each item. If you are
> in need
> > of uniquely identifying each item made take a look at serial
> numbers.
> > Serial numbers are a great way to guarantee that every item
> produced has its
> > own identification that you can access at any time now and in the
> future.
> > There IS more work involved by using them but in many cases well
> worth the
> > extra effort. Ask your CAM or call me for more information if you
> are
> > interested.
> >
> >
> >
> >
> >
> > Thank you,
> >
> >
> >
> >
> >
> > Kevin Kadamus
> >
> > Senior Consultant
> >
> > Epicor Authorized Partner
> >
> >
> >
> > kkadamus@
> >
> > 952-905-0387
> >
> >
> >
> > CONFIDENTIALITY NOTICE: This electronic email transmission may
> contain
> > consultant/client privilege and confidential information intended
> only for
> > the individual or entity named above. Any dissemination, use,
> distribution,
> > copying or disclosure of this communication by any other person or
> entity is
> > strictly prohibited. Should you receive this transmission in
error,
> please
> > notify the sender by telephone at 952-905-0387.
> >
> > _____
> >
> > From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On
> Behalf Of
> > nmtaylor1969
> > Sent: Friday, June 27, 2008 4:18 AM
> > To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
> > Subject: [Vantage] Re: Lot Tracking
> >
> >
> >
> > Note sure if this will help:-
> >
> > We also use lot tracking for many of our parts. Vantage doesn't
> have
> > the capability to auto-generate a next lot number, and having a
> > number of goods receiving operators meant that it was difficult to
> > decide what the next lot number would be. We would have to record
> it
> > off-system somewhere, and this was going to be a pain to manage.
> >
> > I therefore added a button to the receipt entry form which
> calculates
> > a lot number based on a date and time code. In fact I use the
> > following format: "080627/45567". The first 6-digits are the year,
> > the month and the day, and the last 5 digits are the number of
> > seconds which elapsed since midnight. Hence lot numbers are
> specific
> > to the date and time the part was entered ( at a resolution of 1-
> > second ). Ok, we will have a problem if two people enter parts at
> > exactly the same time, but that has never happened yet :o)
> >
> > Therefore when the goods receiving operator enters the next part,
> > they click my "Get Lot Number" button, and the next lot number is
> > generated and stored in the field.
> >
> > We find this works pretty well...
> >
> > I hope this helps!
> >
> > Nick Taylor
> >
> > --- In vantage@yahoogroups <mailto:vantage%
40yahoogroups.com> .com,
> > "eltaria.foong" <eltaria.foong@>
> > wrote:
> > >
> > > Hi, I've been thinking about Lot Tracking in Vantage too.
> > >
> > > Someone mentioned they use Job Number as lot number, let's say i
> > have
> > > a Job 000090 which runs for a month, during the course of the
> > > production, I've received 2 different lot of the same materials,
> > lot A
> > > 56,000 and lot B 44,000.
> > >
> > > If I saved the finished good under Lot 000090, and 1 month down
> the
> > > road the supplier called and said Lot A is problematic, seems
like
> > > I'll have to recall the entire batch of 000090?
> > >
> > > How would we be able to best handle this then?
> > > I was thinking of using 000090-1, 000090-2, 000090-3 and so on
> until
> > > the last run.
> > >
> > > Of course, there may be a possibility that a part of the job
will
> be
> > > taking in 2 lots of materials, but at least we would've kept it
> down
> > > to a minimum, instead of recalling the entire batch of 100,000
in
> > job
> > > 000090?
> > >
> > >
> > > --- In vantage@yahoogroups <mailto:vantage%
> 40yahoogroups.com> .com,
> > "Manasa Reddy" <manasa@> wrote:
> > > >
> > > > Each labor detail record has a unique number...maybe you can
> use
> > that
> > > > field on the shipment somehow as your traceability.
> > > >
> > > >
> > > >
> > > > Something to look at maybe....?????
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > M. Manasa Reddy
> > > >
> > > > manasa@
> > > >
> > > > P: 630-806-2000
> > > >
> > > > F: 630-806-2001
> > > >
> > > > ________________________________
> > > >
> > > > From: vantage@yahoogroups <mailto:vantage%
> 40yahoogroups.com> .com
> > [mailto:vantage@yahoogroups <mailto:vantage%
> 40yahoogroups.com> .com] On
> > Behalf
> > > > Of Arnulfo Mora
> > > > Sent: Tuesday, November 13, 2007 10:45 AM
> > > > To: vantage@yahoogroups <mailto:vantage%
40yahoogroups.com> .com
> > > > Subject: [Vantage] Re: Lot Tracking
> > > >
> > > >
> > > >
> > > > What we are currently planning is to use MES to report
> quantities
> > in
> > > > the basket. When the operator finish a basket they will hit
> report
> > > > quantity in MES, print tag, and send it on to the next
> operation
> > or to
> > > > shipping. For ASN's, we are required to have a unique number
on
> > each
> > > > shipment. With what we can currently tell, we will not be able
> to
> > put
> > > > a unique number on the shipping tag for traceability. This is
a
> > > > requirement for many automotive companies. This unique number
> is
> > used
> > > > to track back to the exact time, date, steel coil, operator,
> etc.
> > when
> > > > a customer calls in with a concern/rejection. We would use the
> > serial
> > > > number for containment of all baskets created under a certain
> > steel
> > > > tag number, after a certain number of hits, or any other items
> > that
> > > > may be suspect. The unique number is the trigger for all
> > > > correspondence with our customer. In essence, we need to
> serialize
> > > > every container (basket), but not every part. If you have any
> > > > additional questions, please let me know.
> > > >
> > > > Thanks in Advance,
> > > >
> > > > Eric
> > > >
> > > >
> > > > --- In vantage@yahoogroups <mailto:vantage%
> 40yahoogroups.com> .com
> > <mailto:vantage%
> > 40yahoogroups.com> ,
> > > > "Michael McWilliams"
> > > > <mmcwilliams22@> wrote:
> > > > >
> > > > > Right now they are in Numeric fields. Every receipt line is
a
> > > > > new "Lot" basically serial but not exactly. That number is
> > generated
> > > > > by getting the next number from a UD table & creating a
> > > > > corresponding UD record. It then takes the numbers that you
> > entered
> > > > > and pushes them into the UD table. I am working on a
> > verification
> > > > > that will only allow you to enter if the properties are
> within
> > > > > acceptable values.
> > > > >
> > > > > We are required to have a "Bundle" number on our shipping
> tags.
> > > > > Every bundle gets a unique number. Since you are creating
> > baskets
> > > > > of parts I do not belive that the Vantage serialization will
> > work.
> > > > > It wants you to give a uniqe number to every unit that is
> > created.
> > > > > I have a question about your creation of baskets. Do you use
> > MES to
> > > > > do this or will it be done in the office?
> > > > > --- In vantage@yahoogroups <mailto:vantage%
> 40yahoogroups.com> .com
> > <mailto:vantage%
> > 40yahoogroups.com> ,
> > > > "Arnulfo Mora" <amora@> wrote:
> > > > > >
> > > > > > Mr. McWilliams,
> > > > > >
> > > > > > How are you entering all of the Physical and Chemical
> > properties
> > > > > into
> > > > > > Vantage? Are you just dumping the information into a text
> > field,
> > > > > or
> > > > > > are you taking that information and verifying it against a
> > material
> > > > > > specification? Also, are you required to have a serial
> number
> > on
> > > > > your
> > > > > > shipping tags? We are currently implementing Vantage and
> are
> > > > > looking
> > > > > > for a way to use a serial number to track individual
> baskets
> > of
> > > > > parts
> > > > > > shipped to our customer. The serial number would be a self
> > > > > > populating, unique, sequential number. Thanks for any
> > information
> > > > > in
> > > > > > advance.
> > > > > >
> > > > > > Eric
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > [Non-text portions of this message have been removed]
> > > >
> > >
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
> ________________________________
> The information contained in this message is intended solely for
the individual to whom it is specifically and originally addressed.
This message and its contents may contain confidential or privileged
information. If you are not the intended recipient, you are hereby
notified that any disclosure or distribution, or taking any action in
reliance on the contents of this information, is strictly prohibited.
> 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 cannot accept liability
for any loss or damage caused by software viruses.
>
> This message (including any attachments) is intended only for
> the use of the individual or entity to which it is addressed and
> may contain information that is non-public, proprietary,
> privileged, confidential, and exempt from disclosure under
> applicable law or may constitute as attorney work product.
> If you are not the intended recipient, you are hereby notified
> that any use, dissemination, distribution, or copying of this
> communication is strictly prohibited. If you have received this
> communication in error, notify us immediately by telephone and
> (i) destroy this message if a facsimile or (ii) delete this message
> immediately if this is an electronic communication.
>
> Thank you.
>
>
> [Non-text portions of this message have been removed]
>

system · July 14, 2008, 8:06am

Ed,

We have discovered a bug in the code I sent you ( typical! ), and I
am currently investigating the problem.

I think the call to oTrans.NotifyAll() is causing the record pointer
to move by accident. I believe this is resulting in the wrong parts
being receipted on some occasions by our operators.

Rob, perhaps your knowledge may be able to assist ?

I notice from the object explorer that this method can be called in
two ways:-

oTrans.NotifyAll(BruteForce) Scary or what!?
oTrans.NotifyAll(type, view)

I am hoping that the latter restricts the refresh to the current
dataview and might stop the record pointer from moving. Its a stab in
the dark, but I might be right...

The "type" parameter is described as:
Epicor.Mfg.UI.FrameWork.EpiTransaction+NotifyType

My skills are not good enough for me to deduce what this parameter
is. Would you happen to know ?

I have sent an e-mail to Epicor support, but sometimes this can be a
much faster medium. Any help would be gratefully received.

Thanks,

Nick

--- In vantage@yahoogroups.com, Ed Garbowski <egarbowski@...> wrote:
>
> Nick,
> Your Date/Timestamp lot numbering is an excellent idea that I
would like to use as we implement Vantage here. Would you be willing
to share your code for your Receipt Entry button to generate your Lot
numbers?
>
> Thanks,
> Ed
>
>
> ________________________________
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On
Behalf Of nmtaylor1969
> Sent: Saturday, June 28, 2008 1:38 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: Lot Tracking
>
>
> I agree with your comments. Just to remove any ambiguity, we use
> serial number tracking for all appropriate manufactured parts that
we
> make in-house, and we use lot-tracking for material receipts coming
> in from vendors. Currently every receipt line will get a different
> lot number, but I guess in reality we could probably make a lot
> number apply to all lines on a specific receipt. ( I haven't tried
> this, so I dont know if Vahtage will allow different parts to exist
> within one lot ). We merely wish to know where any given part came
> from in the event we have a field failure etc. A lot number based on
> a date and time code works well in our particular application.
>
> --- In vantage@yahoogroups.com<mailto:vantage%
40yahoogroups.com>, "Kevin Kadamus" <kkadamus@> wrote:
> >
> > Lot Tracking is a very good tool for keeping a record of daily
> or "runs" of
> > production for Items or groups of items that need to be tracked
for
> a
> > multiple of reasons. Lot Tracking is a manual tracking method and
> is not
> > designed for generating a unique number for each item. If you are
> in need
> > of uniquely identifying each item made take a look at serial
> numbers.
> > Serial numbers are a great way to guarantee that every item
> produced has its
> > own identification that you can access at any time now and in the
> future.
> > There IS more work involved by using them but in many cases well
> worth the
> > extra effort. Ask your CAM or call me for more information if you
> are
> > interested.
> >
> >
> >
> >
> >
> > Thank you,
> >
> >
> >
> >
> >
> > Kevin Kadamus
> >
> > Senior Consultant
> >
> > Epicor Authorized Partner
> >
> >
> >
> > kkadamus@
> >
> > 952-905-0387
> >
> >
> >
> > CONFIDENTIALITY NOTICE: This electronic email transmission may
> contain
> > consultant/client privilege and confidential information intended
> only for
> > the individual or entity named above. Any dissemination, use,
> distribution,
> > copying or disclosure of this communication by any other person or
> entity is
> > strictly prohibited. Should you receive this transmission in
error,
> please
> > notify the sender by telephone at 952-905-0387.
> >
> > _____
> >
> > From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On
> Behalf Of
> > nmtaylor1969
> > Sent: Friday, June 27, 2008 4:18 AM
> > To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
> > Subject: [Vantage] Re: Lot Tracking
> >
> >
> >
> > Note sure if this will help:-
> >
> > We also use lot tracking for many of our parts. Vantage doesn't
> have
> > the capability to auto-generate a next lot number, and having a
> > number of goods receiving operators meant that it was difficult to
> > decide what the next lot number would be. We would have to record
> it
> > off-system somewhere, and this was going to be a pain to manage.
> >
> > I therefore added a button to the receipt entry form which
> calculates
> > a lot number based on a date and time code. In fact I use the
> > following format: "080627/45567". The first 6-digits are the year,
> > the month and the day, and the last 5 digits are the number of
> > seconds which elapsed since midnight. Hence lot numbers are
> specific
> > to the date and time the part was entered ( at a resolution of 1-
> > second ). Ok, we will have a problem if two people enter parts at
> > exactly the same time, but that has never happened yet :o)
> >
> > Therefore when the goods receiving operator enters the next part,
> > they click my "Get Lot Number" button, and the next lot number is
> > generated and stored in the field.
> >
> > We find this works pretty well...
> >
> > I hope this helps!
> >
> > Nick Taylor
> >
> > --- In vantage@yahoogroups <mailto:vantage%
40yahoogroups.com> .com,
> > "eltaria.foong" <eltaria.foong@>
> > wrote:
> > >
> > > Hi, I've been thinking about Lot Tracking in Vantage too.
> > >
> > > Someone mentioned they use Job Number as lot number, let's say i
> > have
> > > a Job 000090 which runs for a month, during the course of the
> > > production, I've received 2 different lot of the same materials,
> > lot A
> > > 56,000 and lot B 44,000.
> > >
> > > If I saved the finished good under Lot 000090, and 1 month down
> the
> > > road the supplier called and said Lot A is problematic, seems
like
> > > I'll have to recall the entire batch of 000090?
> > >
> > > How would we be able to best handle this then?
> > > I was thinking of using 000090-1, 000090-2, 000090-3 and so on
> until
> > > the last run.
> > >
> > > Of course, there may be a possibility that a part of the job
will
> be
> > > taking in 2 lots of materials, but at least we would've kept it
> down
> > > to a minimum, instead of recalling the entire batch of 100,000
in
> > job
> > > 000090?
> > >
> > >
> > > --- In vantage@yahoogroups <mailto:vantage%
> 40yahoogroups.com> .com,
> > "Manasa Reddy" <manasa@> wrote:
> > > >
> > > > Each labor detail record has a unique number...maybe you can
> use
> > that
> > > > field on the shipment somehow as your traceability.
> > > >
> > > >
> > > >
> > > > Something to look at maybe....?????
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > M. Manasa Reddy
> > > >
> > > > manasa@
> > > >
> > > > P: 630-806-2000
> > > >
> > > > F: 630-806-2001
> > > >
> > > > ________________________________
> > > >
> > > > From: vantage@yahoogroups <mailto:vantage%
> 40yahoogroups.com> .com
> > [mailto:vantage@yahoogroups <mailto:vantage%
> 40yahoogroups.com> .com] On
> > Behalf
> > > > Of Arnulfo Mora
> > > > Sent: Tuesday, November 13, 2007 10:45 AM
> > > > To: vantage@yahoogroups <mailto:vantage%
40yahoogroups.com> .com
> > > > Subject: [Vantage] Re: Lot Tracking
> > > >
> > > >
> > > >
> > > > What we are currently planning is to use MES to report
> quantities
> > in
> > > > the basket. When the operator finish a basket they will hit
> report
> > > > quantity in MES, print tag, and send it on to the next
> operation
> > or to
> > > > shipping. For ASN's, we are required to have a unique number
on
> > each
> > > > shipment. With what we can currently tell, we will not be able
> to
> > put
> > > > a unique number on the shipping tag for traceability. This is
a
> > > > requirement for many automotive companies. This unique number
> is
> > used
> > > > to track back to the exact time, date, steel coil, operator,
> etc.
> > when
> > > > a customer calls in with a concern/rejection. We would use the
> > serial
> > > > number for containment of all baskets created under a certain
> > steel
> > > > tag number, after a certain number of hits, or any other items
> > that
> > > > may be suspect. The unique number is the trigger for all
> > > > correspondence with our customer. In essence, we need to
> serialize
> > > > every container (basket), but not every part. If you have any
> > > > additional questions, please let me know.
> > > >
> > > > Thanks in Advance,
> > > >
> > > > Eric
> > > >
> > > >
> > > > --- In vantage@yahoogroups <mailto:vantage%
> 40yahoogroups.com> .com
> > <mailto:vantage%
> > 40yahoogroups.com> ,
> > > > "Michael McWilliams"
> > > > <mmcwilliams22@> wrote:
> > > > >
> > > > > Right now they are in Numeric fields. Every receipt line is
a
> > > > > new "Lot" basically serial but not exactly. That number is
> > generated
> > > > > by getting the next number from a UD table & creating a
> > > > > corresponding UD record. It then takes the numbers that you
> > entered
> > > > > and pushes them into the UD table. I am working on a
> > verification
> > > > > that will only allow you to enter if the properties are
> within
> > > > > acceptable values.
> > > > >
> > > > > We are required to have a "Bundle" number on our shipping
> tags.
> > > > > Every bundle gets a unique number. Since you are creating
> > baskets
> > > > > of parts I do not belive that the Vantage serialization will
> > work.
> > > > > It wants you to give a uniqe number to every unit that is
> > created.
> > > > > I have a question about your creation of baskets. Do you use
> > MES to
> > > > > do this or will it be done in the office?
> > > > > --- In vantage@yahoogroups <mailto:vantage%
> 40yahoogroups.com> .com
> > <mailto:vantage%
> > 40yahoogroups.com> ,
> > > > "Arnulfo Mora" <amora@> wrote:
> > > > > >
> > > > > > Mr. McWilliams,
> > > > > >
> > > > > > How are you entering all of the Physical and Chemical
> > properties
> > > > > into
> > > > > > Vantage? Are you just dumping the information into a text
> > field,
> > > > > or
> > > > > > are you taking that information and verifying it against a
> > material
> > > > > > specification? Also, are you required to have a serial
> number
> > on
> > > > > your
> > > > > > shipping tags? We are currently implementing Vantage and
> are
> > > > > looking
> > > > > > for a way to use a serial number to track individual
> baskets
> > of
> > > > > parts
> > > > > > shipped to our customer. The serial number would be a self
> > > > > > populating, unique, sequential number. Thanks for any
> > information
> > > > > in
> > > > > > advance.
> > > > > >
> > > > > > Eric
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > [Non-text portions of this message have been removed]
> > > >
> > >
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
> ________________________________
> The information contained in this message is intended solely for
the individual to whom it is specifically and originally addressed.
This message and its contents may contain confidential or privileged
information. If you are not the intended recipient, you are hereby
notified that any disclosure or distribution, or taking any action in
reliance on the contents of this information, is strictly prohibited.
> 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 cannot accept liability
for any loss or damage caused by software viruses.
>
> This message (including any attachments) is intended only for
> the use of the individual or entity to which it is addressed and
> may contain information that is non-public, proprietary,
> privileged, confidential, and exempt from disclosure under
> applicable law or may constitute as attorney work product.
> If you are not the intended recipient, you are hereby notified
> that any use, dissemination, distribution, or copying of this
> communication is strictly prohibited. If you have received this
> communication in error, notify us immediately by telephone and
> (i) destroy this message if a facsimile or (ii) delete this message
> immediately if this is an electronic communication.
>
> Thank you.
>
>
> [Non-text portions of this message have been removed]
>

system · July 14, 2008, 8:49am

Nick,

NotifyAll is excessive, use Notify instead try:

YourDataView.Notify(New EpiNotifyArgs(FormName,
yourDataView.Row, yourDataview.Column))

Regards,

Stephen

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of nmtaylor1969
Sent: 14 July 2008 13:06
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Lot Tracking / Rob Can You Help ?!

Ed,

We have discovered a bug in the code I sent you ( typical! ), and I
am currently investigating the problem.

I think the call to oTrans.NotifyAll() is causing the record pointer
to move by accident. I believe this is resulting in the wrong parts
being receipted on some occasions by our operators.

Rob, perhaps your knowledge may be able to assist ?

I notice from the object explorer that this method can be called in
two ways:-

oTrans.NotifyAll(BruteForce) Scary or what!?
oTrans.NotifyAll(type, view)

I am hoping that the latter restricts the refresh to the current
dataview and might stop the record pointer from moving. Its a stab in
the dark, but I might be right...

The "type" parameter is described as:
Epicor.Mfg.UI.FrameWork.EpiTransaction+NotifyType

My skills are not good enough for me to deduce what this parameter
is. Would you happen to know ?

I have sent an e-mail to Epicor support, but sometimes this can be a
much faster medium. Any help would be gratefully received.

Thanks,

Nick

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> , Ed
Garbowski <egarbowski@...> wrote:

>
> Nick,
> Your Date/Timestamp lot numbering is an excellent idea that I

would like to use as we implement Vantage here. Would you be willing
to share your code for your Receipt Entry button to generate your Lot
numbers?

>
> Thanks,
> Ed
>
>
> ________________________________
> From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>

[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf Of nmtaylor1969

> Sent: Saturday, June 28, 2008 1:38 AM
> To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> Subject: [Vantage] Re: Lot Tracking
>
>
> I agree with your comments. Just to remove any ambiguity, we use
> serial number tracking for all appropriate manufactured parts that

we

> make in-house, and we use lot-tracking for material receipts coming
> in from vendors. Currently every receipt line will get a different
> lot number, but I guess in reality we could probably make a lot
> number apply to all lines on a specific receipt. ( I haven't tried
> this, so I dont know if Vahtage will allow different parts to exist
> within one lot ). We merely wish to know where any given part came
> from in the event we have a field failure etc. A lot number based on
> a date and time code works well in our particular application.
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>

<mailto:vantage%
40yahoogroups.com>, "Kevin Kadamus" <kkadamus@> wrote:

> >
> > Lot Tracking is a very good tool for keeping a record of daily
> or "runs" of
> > production for Items or groups of items that need to be tracked

for

> a
> > multiple of reasons. Lot Tracking is a manual tracking method and
> is not
> > designed for generating a unique number for each item. If you are
> in need
> > of uniquely identifying each item made take a look at serial
> numbers.
> > Serial numbers are a great way to guarantee that every item
> produced has its
> > own identification that you can access at any time now and in the
> future.
> > There IS more work involved by using them but in many cases well
> worth the
> > extra effort. Ask your CAM or call me for more information if you
> are
> > interested.
> >
> >
> >
> >
> >
> > Thank you,
> >
> >
> >
> >
> >
> > Kevin Kadamus
> >
> > Senior Consultant
> >
> > Epicor Authorized Partner
> >
> >
> >
> > kkadamus@
> >
> > 952-905-0387
> >
> >
> >
> > CONFIDENTIALITY NOTICE: This electronic email transmission may
> contain
> > consultant/client privilege and confidential information intended
> only for
> > the individual or entity named above. Any dissemination, use,
> distribution,
> > copying or disclosure of this communication by any other person or
> entity is
> > strictly prohibited. Should you receive this transmission in

error,

> please
> > notify the sender by telephone at 952-905-0387.
> >
> > _____
> >
> > From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>

<mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>] On

> Behalf Of
> > nmtaylor1969
> > Sent: Friday, June 27, 2008 4:18 AM
> > To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>

<mailto:vantage%40yahoogroups.com>

> > Subject: [Vantage] Re: Lot Tracking
> >
> >
> >
> > Note sure if this will help:-
> >
> > We also use lot tracking for many of our parts. Vantage doesn't
> have
> > the capability to auto-generate a next lot number, and having a
> > number of goods receiving operators meant that it was difficult to
> > decide what the next lot number would be. We would have to record
> it
> > off-system somewhere, and this was going to be a pain to manage.
> >
> > I therefore added a button to the receipt entry form which
> calculates
> > a lot number based on a date and time code. In fact I use the
> > following format: "080627/45567". The first 6-digits are the year,
> > the month and the day, and the last 5 digits are the number of
> > seconds which elapsed since midnight. Hence lot numbers are
> specific
> > to the date and time the part was entered ( at a resolution of 1-
> > second ). Ok, we will have a problem if two people enter parts at
> > exactly the same time, but that has never happened yet :o)
> >
> > Therefore when the goods receiving operator enters the next part,
> > they click my "Get Lot Number" button, and the next lot number is
> > generated and stored in the field.
> >
> > We find this works pretty well...
> >
> > I hope this helps!
> >
> > Nick Taylor
> >
> > --- In vantage@yahoogroups <mailto:vantage%

40yahoogroups.com> .com,

> > "eltaria.foong" <eltaria.foong@>
> > wrote:
> > >
> > > Hi, I've been thinking about Lot Tracking in Vantage too.
> > >
> > > Someone mentioned they use Job Number as lot number, let's say i
> > have
> > > a Job 000090 which runs for a month, during the course of the
> > > production, I've received 2 different lot of the same materials,
> > lot A
> > > 56,000 and lot B 44,000.
> > >
> > > If I saved the finished good under Lot 000090, and 1 month down
> the
> > > road the supplier called and said Lot A is problematic, seems

like

> > > I'll have to recall the entire batch of 000090?
> > >
> > > How would we be able to best handle this then?
> > > I was thinking of using 000090-1, 000090-2, 000090-3 and so on
> until
> > > the last run.
> > >
> > > Of course, there may be a possibility that a part of the job

will

> be
> > > taking in 2 lots of materials, but at least we would've kept it
> down
> > > to a minimum, instead of recalling the entire batch of 100,000

in

> > job
> > > 000090?
> > >
> > >
> > > --- In vantage@yahoogroups <mailto:vantage%
> 40yahoogroups.com> .com,
> > "Manasa Reddy" <manasa@> wrote:
> > > >
> > > > Each labor detail record has a unique number...maybe you can
> use
> > that
> > > > field on the shipment somehow as your traceability.
> > > >
> > > >
> > > >
> > > > Something to look at maybe....?????
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > M. Manasa Reddy
> > > >
> > > > manasa@
> > > >
> > > > P: 630-806-2000
> > > >
> > > > F: 630-806-2001
> > > >
> > > > ________________________________
> > > >
> > > > From: vantage@yahoogroups <mailto:vantage%
> 40yahoogroups.com> .com
> > [mailto:vantage@yahoogroups <mailto:vantage%
> 40yahoogroups.com> .com] On
> > Behalf
> > > > Of Arnulfo Mora
> > > > Sent: Tuesday, November 13, 2007 10:45 AM
> > > > To: vantage@yahoogroups <mailto:vantage%

40yahoogroups.com> .com

> > > > Subject: [Vantage] Re: Lot Tracking
> > > >
> > > >
> > > >
> > > > What we are currently planning is to use MES to report
> quantities
> > in
> > > > the basket. When the operator finish a basket they will hit
> report
> > > > quantity in MES, print tag, and send it on to the next
> operation
> > or to
> > > > shipping. For ASN's, we are required to have a unique number

on

> > each
> > > > shipment. With what we can currently tell, we will not be able
> to
> > put
> > > > a unique number on the shipping tag for traceability. This is

a

> > > > requirement for many automotive companies. This unique number
> is
> > used
> > > > to track back to the exact time, date, steel coil, operator,
> etc.
> > when
> > > > a customer calls in with a concern/rejection. We would use the
> > serial
> > > > number for containment of all baskets created under a certain
> > steel
> > > > tag number, after a certain number of hits, or any other items
> > that
> > > > may be suspect. The unique number is the trigger for all
> > > > correspondence with our customer. In essence, we need to
> serialize
> > > > every container (basket), but not every part. If you have any
> > > > additional questions, please let me know.
> > > >
> > > > Thanks in Advance,
> > > >
> > > > Eric
> > > >
> > > >
> > > > --- In vantage@yahoogroups <mailto:vantage%
> 40yahoogroups.com> .com
> > <mailto:vantage%
> > 40yahoogroups.com> ,
> > > > "Michael McWilliams"
> > > > <mmcwilliams22@> wrote:
> > > > >
> > > > > Right now they are in Numeric fields. Every receipt line is

a

> > > > > new "Lot" basically serial but not exactly. That number is
> > generated
> > > > > by getting the next number from a UD table & creating a
> > > > > corresponding UD record. It then takes the numbers that you
> > entered
> > > > > and pushes them into the UD table. I am working on a
> > verification
> > > > > that will only allow you to enter if the properties are
> within
> > > > > acceptable values.
> > > > >
> > > > > We are required to have a "Bundle" number on our shipping
> tags.
> > > > > Every bundle gets a unique number. Since you are creating
> > baskets
> > > > > of parts I do not belive that the Vantage serialization will
> > work.
> > > > > It wants you to give a uniqe number to every unit that is
> > created.
> > > > > I have a question about your creation of baskets. Do you use
> > MES to
> > > > > do this or will it be done in the office?
> > > > > --- In vantage@yahoogroups <mailto:vantage%
> 40yahoogroups.com> .com
> > <mailto:vantage%
> > 40yahoogroups.com> ,
> > > > "Arnulfo Mora" <amora@> wrote:
> > > > > >
> > > > > > Mr. McWilliams,
> > > > > >
> > > > > > How are you entering all of the Physical and Chemical
> > properties
> > > > > into
> > > > > > Vantage? Are you just dumping the information into a text
> > field,
> > > > > or
> > > > > > are you taking that information and verifying it against a
> > material
> > > > > > specification? Also, are you required to have a serial
> number
> > on
> > > > > your
> > > > > > shipping tags? We are currently implementing Vantage and
> are
> > > > > looking
> > > > > > for a way to use a serial number to track individual
> baskets
> > of
> > > > > parts
> > > > > > shipped to our customer. The serial number would be a self
> > > > > > populating, unique, sequential number. Thanks for any
> > information
> > > > > in
> > > > > > advance.
> > > > > >
> > > > > > Eric
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > [Non-text portions of this message have been removed]
> > > >
> > >
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
> ________________________________
> The information contained in this message is intended solely for

the individual to whom it is specifically and originally addressed.
This message and its contents may contain confidential or privileged
information. If you are not the intended recipient, you are hereby
notified that any disclosure or distribution, or taking any action in
reliance on the contents of this information, is strictly prohibited.

> 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 cannot accept liability
for any loss or damage caused by software viruses.

>
> This message (including any attachments) is intended only for
> the use of the individual or entity to which it is addressed and
> may contain information that is non-public, proprietary,
> privileged, confidential, and exempt from disclosure under
> applicable law or may constitute as attorney work product.
> If you are not the intended recipient, you are hereby notified
> that any use, dissemination, distribution, or copying of this
> communication is strictly prohibited. If you have received this
> communication in error, notify us immediately by telephone and
> (i) destroy this message if a facsimile or (ii) delete this message
> immediately if this is an electronic communication.
>
> Thank you.
>
>
> [Non-text portions of this message have been removed]
>

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

system · July 14, 2008, 9:16am

Many thanks Stephen...

However I am not clear on the command syntax. Is there anywhere
within the object browser that I can find out what EpiNotifyArgs
should consist of ?

My dataview is called: edvStockDtl and the field in question is
LotNum.

Any help with the correct syntax would be greatly appreciated...

Best regards,

Nick

--- In vantage@yahoogroups.com, "Stephen Edginton" <stephene@...>
wrote:

>
> Nick,
>
> NotifyAll is excessive, use Notify instead try:
>
>
>
> YourDataView.Notify(New EpiNotifyArgs(FormName,
> yourDataView.Row, yourDataview.Column))
>
>
>
> Regards,
>
> Stephen
>
>
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On

Behalf

> Of nmtaylor1969
> Sent: 14 July 2008 13:06
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: Lot Tracking / Rob Can You Help ?!
>
>
>
> Ed,
>
> We have discovered a bug in the code I sent you ( typical! ), and I
> am currently investigating the problem.
>
> I think the call to oTrans.NotifyAll() is causing the record

pointer

> to move by accident. I believe this is resulting in the wrong parts
> being receipted on some occasions by our operators.
>
> Rob, perhaps your knowledge may be able to assist ?
>
> I notice from the object explorer that this method can be called in
> two ways:-
>
> oTrans.NotifyAll(BruteForce) Scary or what!?
> oTrans.NotifyAll(type, view)
>
> I am hoping that the latter restricts the refresh to the current
> dataview and might stop the record pointer from moving. Its a stab

in

> the dark, but I might be right...
>
> The "type" parameter is described as:
> Epicor.Mfg.UI.FrameWork.EpiTransaction+NotifyType
>
> My skills are not good enough for me to deduce what this parameter
> is. Would you happen to know ?
>
> I have sent an e-mail to Epicor support, but sometimes this can be

a

> much faster medium. Any help would be gratefully received.
>
> Thanks,
>
> Nick
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,

Ed

> Garbowski <egarbowski@> wrote:
> >
> > Nick,
> > Your Date/Timestamp lot numbering is an excellent idea that I
> would like to use as we implement Vantage here. Would you be

willing

> to share your code for your Receipt Entry button to generate your

Lot

> numbers?
> >
> > Thanks,
> > Ed
> >
> >
> > ________________________________
> > From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> [mailto:vantage@yahoogroups.com <mailto:vantage%

40yahoogroups.com> ] On

> Behalf Of nmtaylor1969
> > Sent: Saturday, June 28, 2008 1:38 AM
> > To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> > Subject: [Vantage] Re: Lot Tracking
> >
> >
> > I agree with your comments. Just to remove any ambiguity, we use
> > serial number tracking for all appropriate manufactured parts

that

> we
> > make in-house, and we use lot-tracking for material receipts

coming

> > in from vendors. Currently every receipt line will get a different
> > lot number, but I guess in reality we could probably make a lot
> > number apply to all lines on a specific receipt. ( I haven't tried
> > this, so I dont know if Vahtage will allow different parts to

exist

> > within one lot ). We merely wish to know where any given part came
> > from in the event we have a field failure etc. A lot number based

on

> > a date and time code works well in our particular application.
> >
> > --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> <mailto:vantage%
> 40yahoogroups.com>, "Kevin Kadamus" <kkadamus@> wrote:
> > >
> > > Lot Tracking is a very good tool for keeping a record of daily
> > or "runs" of
> > > production for Items or groups of items that need to be tracked
> for
> > a
> > > multiple of reasons. Lot Tracking is a manual tracking method

and

> > is not
> > > designed for generating a unique number for each item. If you

are

> > in need
> > > of uniquely identifying each item made take a look at serial
> > numbers.
> > > Serial numbers are a great way to guarantee that every item
> > produced has its
> > > own identification that you can access at any time now and in

the

> > future.
> > > There IS more work involved by using them but in many cases well
> > worth the
> > > extra effort. Ask your CAM or call me for more information if

you

> > are
> > > interested.
> > >
> > >
> > >
> > >
> > >
> > > Thank you,
> > >
> > >
> > >
> > >
> > >
> > > Kevin Kadamus
> > >
> > > Senior Consultant
> > >
> > > Epicor Authorized Partner
> > >
> > >
> > >
> > > kkadamus@
> > >
> > > 952-905-0387
> > >
> > >
> > >
> > > CONFIDENTIALITY NOTICE: This electronic email transmission may
> > contain
> > > consultant/client privilege and confidential information

intended

> > only for
> > > the individual or entity named above. Any dissemination, use,
> > distribution,
> > > copying or disclosure of this communication by any other person

or

> > entity is
> > > strictly prohibited. Should you receive this transmission in
> error,
> > please
> > > notify the sender by telephone at 952-905-0387.
> > >
> > > _____
> > >
> > > From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> <mailto:vantage%40yahoogroups.com>
> [mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> <mailto:vantage%40yahoogroups.com>] On
> > Behalf Of
> > > nmtaylor1969
> > > Sent: Friday, June 27, 2008 4:18 AM
> > > To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> <mailto:vantage%40yahoogroups.com>
> > > Subject: [Vantage] Re: Lot Tracking
> > >
> > >
> > >
> > > Note sure if this will help:-
> > >
> > > We also use lot tracking for many of our parts. Vantage doesn't
> > have
> > > the capability to auto-generate a next lot number, and having a
> > > number of goods receiving operators meant that it was difficult

to

> > > decide what the next lot number would be. We would have to

record

> > it
> > > off-system somewhere, and this was going to be a pain to manage.
> > >
> > > I therefore added a button to the receipt entry form which
> > calculates
> > > a lot number based on a date and time code. In fact I use the
> > > following format: "080627/45567". The first 6-digits are the

year,

> > > the month and the day, and the last 5 digits are the number of
> > > seconds which elapsed since midnight. Hence lot numbers are
> > specific
> > > to the date and time the part was entered ( at a resolution of

1-

> > > second ). Ok, we will have a problem if two people enter parts

at

> > > exactly the same time, but that has never happened yet :o)
> > >
> > > Therefore when the goods receiving operator enters the next

part,

> > > they click my "Get Lot Number" button, and the next lot number

is

> > > generated and stored in the field.
> > >
> > > We find this works pretty well...
> > >
> > > I hope this helps!
> > >
> > > Nick Taylor
> > >
> > > --- In vantage@yahoogroups <mailto:vantage%
> 40yahoogroups.com> .com,
> > > "eltaria.foong" <eltaria.foong@>
> > > wrote:
> > > >
> > > > Hi, I've been thinking about Lot Tracking in Vantage too.
> > > >
> > > > Someone mentioned they use Job Number as lot number, let's

say i

> > > have
> > > > a Job 000090 which runs for a month, during the course of the
> > > > production, I've received 2 different lot of the same

materials,

> > > lot A
> > > > 56,000 and lot B 44,000.
> > > >
> > > > If I saved the finished good under Lot 000090, and 1 month

down

> > the
> > > > road the supplier called and said Lot A is problematic, seems
> like
> > > > I'll have to recall the entire batch of 000090?
> > > >
> > > > How would we be able to best handle this then?
> > > > I was thinking of using 000090-1, 000090-2, 000090-3 and so on
> > until
> > > > the last run.
> > > >
> > > > Of course, there may be a possibility that a part of the job
> will
> > be
> > > > taking in 2 lots of materials, but at least we would've kept

it

> > down
> > > > to a minimum, instead of recalling the entire batch of

100,000

> in
> > > job
> > > > 000090?
> > > >
> > > >
> > > > --- In vantage@yahoogroups <mailto:vantage%
> > 40yahoogroups.com> .com,
> > > "Manasa Reddy" <manasa@> wrote:
> > > > >
> > > > > Each labor detail record has a unique number...maybe you can
> > use
> > > that
> > > > > field on the shipment somehow as your traceability.
> > > > >
> > > > >
> > > > >
> > > > > Something to look at maybe....?????
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > M. Manasa Reddy
> > > > >
> > > > > manasa@
> > > > >
> > > > > P: 630-806-2000
> > > > >
> > > > > F: 630-806-2001
> > > > >
> > > > > ________________________________
> > > > >
> > > > > From: vantage@yahoogroups <mailto:vantage%
> > 40yahoogroups.com> .com
> > > [mailto:vantage@yahoogroups <mailto:vantage%
> > 40yahoogroups.com> .com] On
> > > Behalf
> > > > > Of Arnulfo Mora
> > > > > Sent: Tuesday, November 13, 2007 10:45 AM
> > > > > To: vantage@yahoogroups <mailto:vantage%
> 40yahoogroups.com> .com
> > > > > Subject: [Vantage] Re: Lot Tracking
> > > > >
> > > > >
> > > > >
> > > > > What we are currently planning is to use MES to report
> > quantities
> > > in
> > > > > the basket. When the operator finish a basket they will hit
> > report
> > > > > quantity in MES, print tag, and send it on to the next
> > operation
> > > or to
> > > > > shipping. For ASN's, we are required to have a unique

number

> on
> > > each
> > > > > shipment. With what we can currently tell, we will not be

able

> > to
> > > put
> > > > > a unique number on the shipping tag for traceability. This

is

> a
> > > > > requirement for many automotive companies. This unique

number

> > is
> > > used
> > > > > to track back to the exact time, date, steel coil, operator,
> > etc.
> > > when
> > > > > a customer calls in with a concern/rejection. We would use

the

> > > serial
> > > > > number for containment of all baskets created under a

certain

> > > steel
> > > > > tag number, after a certain number of hits, or any other

items

> > > that
> > > > > may be suspect. The unique number is the trigger for all
> > > > > correspondence with our customer. In essence, we need to
> > serialize
> > > > > every container (basket), but not every part. If you have

any

> > > > > additional questions, please let me know.
> > > > >
> > > > > Thanks in Advance,
> > > > >
> > > > > Eric
> > > > >
> > > > >
> > > > > --- In vantage@yahoogroups <mailto:vantage%
> > 40yahoogroups.com> .com
> > > <mailto:vantage%
> > > 40yahoogroups.com> ,
> > > > > "Michael McWilliams"
> > > > > <mmcwilliams22@> wrote:
> > > > > >
> > > > > > Right now they are in Numeric fields. Every receipt line

is

> a
> > > > > > new "Lot" basically serial but not exactly. That number is
> > > generated
> > > > > > by getting the next number from a UD table & creating a
> > > > > > corresponding UD record. It then takes the numbers that

you

> > > entered
> > > > > > and pushes them into the UD table. I am working on a
> > > verification
> > > > > > that will only allow you to enter if the properties are
> > within
> > > > > > acceptable values.
> > > > > >
> > > > > > We are required to have a "Bundle" number on our shipping
> > tags.
> > > > > > Every bundle gets a unique number. Since you are creating
> > > baskets
> > > > > > of parts I do not belive that the Vantage serialization

will

> > > work.
> > > > > > It wants you to give a uniqe number to every unit that is
> > > created.
> > > > > > I have a question about your creation of baskets. Do you

use

> > > MES to
> > > > > > do this or will it be done in the office?
> > > > > > --- In vantage@yahoogroups <mailto:vantage%
> > 40yahoogroups.com> .com
> > > <mailto:vantage%
> > > 40yahoogroups.com> ,
> > > > > "Arnulfo Mora" <amora@> wrote:
> > > > > > >
> > > > > > > Mr. McWilliams,
> > > > > > >
> > > > > > > How are you entering all of the Physical and Chemical
> > > properties
> > > > > > into
> > > > > > > Vantage? Are you just dumping the information into a

text

> > > field,
> > > > > > or
> > > > > > > are you taking that information and verifying it

against a

> > > material
> > > > > > > specification? Also, are you required to have a serial
> > number
> > > on
> > > > > > your
> > > > > > > shipping tags? We are currently implementing Vantage and
> > are
> > > > > > looking
> > > > > > > for a way to use a serial number to track individual
> > baskets
> > > of
> > > > > > parts
> > > > > > > shipped to our customer. The serial number would be a

self

> > > > > > > populating, unique, sequential number. Thanks for any
> > > information
> > > > > > in
> > > > > > > advance.
> > > > > > >
> > > > > > > Eric
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > [Non-text portions of this message have been removed]
> > > > >
> > > >
> > >
> > >
> > >
> > >
> > >
> > > [Non-text portions of this message have been removed]
> > >
> >
> >
> >
> > ________________________________
> > The information contained in this message is intended solely for
> the individual to whom it is specifically and originally addressed.
> This message and its contents may contain confidential or

privileged

> information. If you are not the intended recipient, you are hereby
> notified that any disclosure or distribution, or taking any action

in

> reliance on the contents of this information, is strictly

prohibited.

> > 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 cannot accept

liability

> for any loss or damage caused by software viruses.
> >
> > This message (including any attachments) is intended only for
> > the use of the individual or entity to which it is addressed and
> > may contain information that is non-public, proprietary,
> > privileged, confidential, and exempt from disclosure under
> > applicable law or may constitute as attorney work product.
> > If you are not the intended recipient, you are hereby notified
> > that any use, dissemination, distribution, or copying of this
> > communication is strictly prohibited. If you have received this
> > communication in error, notify us immediately by telephone and
> > (i) destroy this message if a facsimile or (ii) delete this

message

> > immediately if this is an electronic communication.
> >
> > Thank you.
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
>
>
> [Non-text portions of this message have been removed]
>

system · July 14, 2008, 9:31am

Try a Application.DoEvents() before the notify. I have fixed (or found a workaround for) some NotifyAll() problems by using that before the call to NotifyAll().

Thanks,
Kunal

----- Original Message ----
From: nmtaylor1969 <n.taylor@...>
To: vantage@yahoogroups.com
Sent: Monday, July 14, 2008 7:06:01 AM
Subject: [Vantage] Re: Lot Tracking / Rob Can You Help ?!

Ed,

We have discovered a bug in the code I sent you ( typical! ), and I
am currently investigating the problem.

I think the call to oTrans.NotifyAll( ) is causing the record pointer
to move by accident. I believe this is resulting in the wrong parts
being receipted on some occasions by our operators.

Rob, perhaps your knowledge may be able to assist ?

I notice from the object explorer that this method can be called in
two ways:-

oTrans.NotifyAll( BruteForce) Scary or what!?
oTrans.NotifyAll( type, view)

I am hoping that the latter restricts the refresh to the current
dataview and might stop the record pointer from moving. Its a stab in
the dark, but I might be right...

The "type" parameter is described as:
Epicor.Mfg.UI. FrameWork. EpiTransaction+ NotifyType

My skills are not good enough for me to deduce what this parameter
is. Would you happen to know ?

I have sent an e-mail to Epicor support, but sometimes this can be a
much faster medium. Any help would be gratefully received.

Thanks,

Nick

--- In vantage@yahoogroups .com, Ed Garbowski <egarbowski@ ...> wrote:
>
> Nick,
> Your Date/Timestamp lot numbering is an excellent idea that I
would like to use as we implement Vantage here. Would you be willing
to share your code for your Receipt Entry button to generate your Lot
numbers?
>
> Thanks,
> Ed
>
>
> ____________ _________ _________ __
> From: vantage@yahoogroups .com [mailto:vantage@yahoogroups .com] On
Behalf Of nmtaylor1969
> Sent: Saturday, June 28, 2008 1:38 AM
> To: vantage@yahoogroups .com
> Subject: [Vantage] Re: Lot Tracking
>
>
> I agree with your comments. Just to remove any ambiguity, we use
> serial number tracking for all appropriate manufactured parts that
we
> make in-house, and we use lot-tracking for material receipts coming
> in from vendors. Currently every receipt line will get a different
> lot number, but I guess in reality we could probably make a lot
> number apply to all lines on a specific receipt. ( I haven't tried
> this, so I dont know if Vahtage will allow different parts to exist
> within one lot ). We merely wish to know where any given part came
> from in the event we have a field failure etc. A lot number based on
> a date and time code works well in our particular application.
>
> --- In vantage@yahoogroups .com<mailto:vantage%
40yahoogroups. com>, "Kevin Kadamus" <kkadamus@> wrote:
> >
> > Lot Tracking is a very good tool for keeping a record of daily
> or "runs" of
> > production for Items or groups of items that need to be tracked
for
> a
> > multiple of reasons. Lot Tracking is a manual tracking method and
> is not
> > designed for generating a unique number for each item. If you are
> in need
> > of uniquely identifying each item made take a look at serial
> numbers.
> > Serial numbers are a great way to guarantee that every item
> produced has its
> > own identification that you can access at any time now and in the
> future.
> > There IS more work involved by using them but in many cases well
> worth the
> > extra effort. Ask your CAM or call me for more information if you
> are
> > interested.
> >
> >
> >
> >
> >
> > Thank you,
> >
> >
> >
> >
> >
> > Kevin Kadamus
> >
> > Senior Consultant
> >
> > Epicor Authorized Partner
> >
> >
> >
> > kkadamus@
> >
> > 952-905-0387
> >
> >
> >
> > CONFIDENTIALITY NOTICE: This electronic email transmission may
> contain
> > consultant/client privilege and confidential information intended
> only for
> > the individual or entity named above. Any dissemination, use,
> distribution,
> > copying or disclosure of this communication by any other person or
> entity is
> > strictly prohibited. Should you receive this transmission in
error,
> please
> > notify the sender by telephone at 952-905-0387.
> >
> > _____
> >
> > From: vantage@yahoogroups .com<mailto:vantage% 40yahoogroups. com>
[mailto:vantage@yahoogroups .com<mailto:vantage% 40yahoogroups. com>] On
> Behalf Of
> > nmtaylor1969
> > Sent: Friday, June 27, 2008 4:18 AM
> > To: vantage@yahoogroups .com<mailto:vantage% 40yahoogroups. com>
> > Subject: [Vantage] Re: Lot Tracking
> >
> >
> >
> > Note sure if this will help:-
> >
> > We also use lot tracking for many of our parts. Vantage doesn't
> have
> > the capability to auto-generate a next lot number, and having a
> > number of goods receiving operators meant that it was difficult to
> > decide what the next lot number would be. We would have to record
> it
> > off-system somewhere, and this was going to be a pain to manage.
> >
> > I therefore added a button to the receipt entry form which
> calculates
> > a lot number based on a date and time code. In fact I use the
> > following format: "080627/45567" . The first 6-digits are the year,
> > the month and the day, and the last 5 digits are the number of
> > seconds which elapsed since midnight. Hence lot numbers are
> specific
> > to the date and time the part was entered ( at a resolution of 1-
> > second ). Ok, we will have a problem if two people enter parts at
> > exactly the same time, but that has never happened yet :o)
> >
> > Therefore when the goods receiving operator enters the next part,
> > they click my "Get Lot Number" button, and the next lot number is
> > generated and stored in the field.
> >
> > We find this works pretty well...
> >
> > I hope this helps!
> >
> > Nick Taylor
> >
> > --- In vantage@yahoogroups <mailto:vantage%
40yahoogroups. com> .com,
> > "eltaria.foong" <eltaria.foong@ >
> > wrote:
> > >
> > > Hi, I've been thinking about Lot Tracking in Vantage too.
> > >
> > > Someone mentioned they use Job Number as lot number, let's say i
> > have
> > > a Job 000090 which runs for a month, during the course of the
> > > production, I've received 2 different lot of the same materials,
> > lot A
> > > 56,000 and lot B 44,000.
> > >
> > > If I saved the finished good under Lot 000090, and 1 month down
> the
> > > road the supplier called and said Lot A is problematic, seems
like
> > > I'll have to recall the entire batch of 000090?
> > >
> > > How would we be able to best handle this then?
> > > I was thinking of using 000090-1, 000090-2, 000090-3 and so on
> until
> > > the last run.
> > >
> > > Of course, there may be a possibility that a part of the job
will
> be
> > > taking in 2 lots of materials, but at least we would've kept it
> down
> > > to a minimum, instead of recalling the entire batch of 100,000
in
> > job
> > > 000090?
> > >
> > >
> > > --- In vantage@yahoogroups <mailto:vantage%
> 40yahoogroups. com> .com,
> > "Manasa Reddy" <manasa@> wrote:
> > > >
> > > > Each labor detail record has a unique number...maybe you can
> use
> > that
> > > > field on the shipment somehow as your traceability.
> > > >
> > > >
> > > >
> > > > Something to look at maybe....??? ??
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > M. Manasa Reddy
> > > >
> > > > manasa@
> > > >
> > > > P: 630-806-2000
> > > >
> > > > F: 630-806-2001
> > > >
> > > > ____________ _________ _________ __
> > > >
> > > > From: vantage@yahoogroups <mailto:vantage%
> 40yahoogroups. com> .com
> > [mailto:vantage@ yahoogroups <mailto:vantage%
> 40yahoogroups. com> .com] On
> > Behalf
> > > > Of Arnulfo Mora
> > > > Sent: Tuesday, November 13, 2007 10:45 AM
> > > > To: vantage@yahoogroups <mailto:vantage%
40yahoogroups. com> .com
> > > > Subject: [Vantage] Re: Lot Tracking
> > > >
> > > >
> > > >
> > > > What we are currently planning is to use MES to report
> quantities
> > in
> > > > the basket. When the operator finish a basket they will hit
> report
> > > > quantity in MES, print tag, and send it on to the next
> operation
> > or to
> > > > shipping. For ASN's, we are required to have a unique number
on
> > each
> > > > shipment. With what we can currently tell, we will not be able
> to
> > put
> > > > a unique number on the shipping tag for traceability. This is
a
> > > > requirement for many automotive companies. This unique number
> is
> > used
> > > > to track back to the exact time, date, steel coil, operator,
> etc.
> > when
> > > > a customer calls in with a concern/rejection. We would use the
> > serial
> > > > number for containment of all baskets created under a certain
> > steel
> > > > tag number, after a certain number of hits, or any other items
> > that
> > > > may be suspect. The unique number is the trigger for all
> > > > correspondence with our customer. In essence, we need to
> serialize
> > > > every container (basket), but not every part. If you have any
> > > > additional questions, please let me know.
> > > >
> > > > Thanks in Advance,
> > > >
> > > > Eric
> > > >
> > > >
> > > > --- In vantage@yahoogroups <mailto:vantage%
> 40yahoogroups. com> .com
> > <mailto:vantage%
> > 40yahoogroups. com> ,
> > > > "Michael McWilliams"
> > > > <mmcwilliams22@ > wrote:
> > > > >
> > > > > Right now they are in Numeric fields. Every receipt line is
a
> > > > > new "Lot" basically serial but not exactly. That number is
> > generated
> > > > > by getting the next number from a UD table & creating a
> > > > > corresponding UD record. It then takes the numbers that you
> > entered
> > > > > and pushes them into the UD table. I am working on a
> > verification
> > > > > that will only allow you to enter if the properties are
> within
> > > > > acceptable values.
> > > > >
> > > > > We are required to have a "Bundle" number on our shipping
> tags.
> > > > > Every bundle gets a unique number. Since you are creating
> > baskets
> > > > > of parts I do not belive that the Vantage serialization will
> > work.
> > > > > It wants you to give a uniqe number to every unit that is
> > created.
> > > > > I have a question about your creation of baskets. Do you use
> > MES to
> > > > > do this or will it be done in the office?
> > > > > --- In vantage@yahoogroups <mailto:vantage%
> 40yahoogroups. com> .com
> > <mailto:vantage%
> > 40yahoogroups. com> ,
> > > > "Arnulfo Mora" <amora@> wrote:
> > > > > >
> > > > > > Mr. McWilliams,
> > > > > >
> > > > > > How are you entering all of the Physical and Chemical
> > properties
> > > > > into
> > > > > > Vantage? Are you just dumping the information into a text
> > field,
> > > > > or
> > > > > > are you taking that information and verifying it against a
> > material
> > > > > > specification? Also, are you required to have a serial
> number
> > on
> > > > > your
> > > > > > shipping tags? We are currently implementing Vantage and
> are
> > > > > looking
> > > > > > for a way to use a serial number to track individual
> baskets
> > of
> > > > > parts
> > > > > > shipped to our customer. The serial number would be a self
> > > > > > populating, unique, sequential number. Thanks for any
> > information
> > > > > in
> > > > > > advance.
> > > > > >
> > > > > > Eric
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > [Non-text portions of this message have been removed]
> > > >
> > >
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
> ____________ _________ _________ __
> The information contained in this message is intended solely for
the individual to whom it is specifically and originally addressed.
This message and its contents may contain confidential or privileged
information. If you are not the intended recipient, you are hereby
notified that any disclosure or distribution, or taking any action in
reliance on the contents of this information, is strictly prohibited.
> 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 cannot accept liability
for any loss or damage caused by software viruses.
>
> This message (including any attachments) is intended only for
> the use of the individual or entity to which it is addressed and
> may contain information that is non-public, proprietary,
> privileged, confidential, and exempt from disclosure under
> applicable law or may constitute as attorney work product.
> If you are not the intended recipient, you are hereby notified
> that any use, dissemination, distribution, or copying of this
> communication is strictly prohibited. If you have received this
> communication in error, notify us immediately by telephone and
> (i) destroy this message if a facsimile or (ii) delete this message
> immediately if this is an electronic communication.
>
> Thank you.
>
>
> [Non-text portions of this message have been removed]
>

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

system · July 14, 2008, 10:02am

You could try

edvStockDtl.Notify(new EpiNotifyArgs(formName,
edvStockDtl.Row,EpiTransaction.Initialize)

There are many constructors for the EpiNotifyArgs

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of nmtaylor1969
Sent: 14 July 2008 14:17
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Lot Tracking / Rob Can You Help ?!

Many thanks Stephen...

However I am not clear on the command syntax. Is there anywhere
within the object browser that I can find out what EpiNotifyArgs
should consist of ?

My dataview is called: edvStockDtl and the field in question is
LotNum.

Any help with the correct syntax would be greatly appreciated...

Best regards,

Nick

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
"Stephen Edginton" <stephene@...>
wrote:

>
> Nick,
>
> NotifyAll is excessive, use Notify instead try:
>
>
>
> YourDataView.Notify(New EpiNotifyArgs(FormName,
> yourDataView.Row, yourDataview.Column))
>
>
>
> Regards,
>
> Stephen
>
>
>
> From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>

[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf

> Of nmtaylor1969
> Sent: 14 July 2008 13:06
> To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> Subject: [Vantage] Re: Lot Tracking / Rob Can You Help ?!
>
>
>
> Ed,
>
> We have discovered a bug in the code I sent you ( typical! ), and I
> am currently investigating the problem.
>
> I think the call to oTrans.NotifyAll() is causing the record

pointer

> to move by accident. I believe this is resulting in the wrong parts
> being receipted on some occasions by our operators.
>
> Rob, perhaps your knowledge may be able to assist ?
>
> I notice from the object explorer that this method can be called in
> two ways:-
>
> oTrans.NotifyAll(BruteForce) Scary or what!?
> oTrans.NotifyAll(type, view)
>
> I am hoping that the latter restricts the refresh to the current
> dataview and might stop the record pointer from moving. Its a stab

in

> the dark, but I might be right...
>
> The "type" parameter is described as:
> Epicor.Mfg.UI.FrameWork.EpiTransaction+NotifyType
>
> My skills are not good enough for me to deduce what this parameter
> is. Would you happen to know ?
>
> I have sent an e-mail to Epicor support, but sometimes this can be

a

> much faster medium. Any help would be gratefully received.
>
> Thanks,
>
> Nick
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>

<mailto:vantage%40yahoogroups.com> ,
Ed

> Garbowski <egarbowski@> wrote:
> >
> > Nick,
> > Your Date/Timestamp lot numbering is an excellent idea that I
> would like to use as we implement Vantage here. Would you be

willing

> to share your code for your Receipt Entry button to generate your

Lot

> numbers?
> >
> > Thanks,
> > Ed
> >
> >
> > ________________________________
> > From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>

<mailto:vantage%40yahoogroups.com>

> [mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>

<mailto:vantage%
40yahoogroups.com> ] On

> Behalf Of nmtaylor1969
> > Sent: Saturday, June 28, 2008 1:38 AM
> > To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>

<mailto:vantage%40yahoogroups.com>

> > Subject: [Vantage] Re: Lot Tracking
> >
> >
> > I agree with your comments. Just to remove any ambiguity, we use
> > serial number tracking for all appropriate manufactured parts

that

> we
> > make in-house, and we use lot-tracking for material receipts

coming

> > in from vendors. Currently every receipt line will get a different
> > lot number, but I guess in reality we could probably make a lot
> > number apply to all lines on a specific receipt. ( I haven't tried
> > this, so I dont know if Vahtage will allow different parts to

exist

> > within one lot ). We merely wish to know where any given part came
> > from in the event we have a field failure etc. A lot number based

on

> > a date and time code works well in our particular application.
> >
> > --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>

<mailto:vantage%40yahoogroups.com>

> <mailto:vantage%
> 40yahoogroups.com>, "Kevin Kadamus" <kkadamus@> wrote:
> > >
> > > Lot Tracking is a very good tool for keeping a record of daily
> > or "runs" of
> > > production for Items or groups of items that need to be tracked
> for
> > a
> > > multiple of reasons. Lot Tracking is a manual tracking method

and

> > is not
> > > designed for generating a unique number for each item. If you

are

> > in need
> > > of uniquely identifying each item made take a look at serial
> > numbers.
> > > Serial numbers are a great way to guarantee that every item
> > produced has its
> > > own identification that you can access at any time now and in

the

> > future.
> > > There IS more work involved by using them but in many cases well
> > worth the
> > > extra effort. Ask your CAM or call me for more information if

you

> > are
> > > interested.
> > >
> > >
> > >
> > >
> > >
> > > Thank you,
> > >
> > >
> > >
> > >
> > >
> > > Kevin Kadamus
> > >
> > > Senior Consultant
> > >
> > > Epicor Authorized Partner
> > >
> > >
> > >
> > > kkadamus@
> > >
> > > 952-905-0387
> > >
> > >
> > >
> > > CONFIDENTIALITY NOTICE: This electronic email transmission may
> > contain
> > > consultant/client privilege and confidential information

intended

> > only for
> > > the individual or entity named above. Any dissemination, use,
> > distribution,
> > > copying or disclosure of this communication by any other person

or

> > entity is
> > > strictly prohibited. Should you receive this transmission in
> error,
> > please
> > > notify the sender by telephone at 952-905-0387.
> > >
> > > _____
> > >
> > > From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>

<mailto:vantage%40yahoogroups.com>

> <mailto:vantage%40yahoogroups.com>
> [mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>

<mailto:vantage%40yahoogroups.com>

> <mailto:vantage%40yahoogroups.com>] On
> > Behalf Of
> > > nmtaylor1969
> > > Sent: Friday, June 27, 2008 4:18 AM
> > > To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>

<mailto:vantage%40yahoogroups.com>

> <mailto:vantage%40yahoogroups.com>
> > > Subject: [Vantage] Re: Lot Tracking
> > >
> > >
> > >
> > > Note sure if this will help:-
> > >
> > > We also use lot tracking for many of our parts. Vantage doesn't
> > have
> > > the capability to auto-generate a next lot number, and having a
> > > number of goods receiving operators meant that it was difficult

to

> > > decide what the next lot number would be. We would have to

record

> > it
> > > off-system somewhere, and this was going to be a pain to manage.
> > >
> > > I therefore added a button to the receipt entry form which
> > calculates
> > > a lot number based on a date and time code. In fact I use the
> > > following format: "080627/45567". The first 6-digits are the

year,

> > > the month and the day, and the last 5 digits are the number of
> > > seconds which elapsed since midnight. Hence lot numbers are
> > specific
> > > to the date and time the part was entered ( at a resolution of

1-

> > > second ). Ok, we will have a problem if two people enter parts

at

> > > exactly the same time, but that has never happened yet :o)
> > >
> > > Therefore when the goods receiving operator enters the next

part,

> > > they click my "Get Lot Number" button, and the next lot number

is

> > > generated and stored in the field.
> > >
> > > We find this works pretty well...
> > >
> > > I hope this helps!
> > >
> > > Nick Taylor
> > >
> > > --- In vantage@yahoogroups <mailto:vantage%
> 40yahoogroups.com> .com,
> > > "eltaria.foong" <eltaria.foong@>
> > > wrote:
> > > >
> > > > Hi, I've been thinking about Lot Tracking in Vantage too.
> > > >
> > > > Someone mentioned they use Job Number as lot number, let's

say i

> > > have
> > > > a Job 000090 which runs for a month, during the course of the
> > > > production, I've received 2 different lot of the same

materials,

> > > lot A
> > > > 56,000 and lot B 44,000.
> > > >
> > > > If I saved the finished good under Lot 000090, and 1 month

down

> > the
> > > > road the supplier called and said Lot A is problematic, seems
> like
> > > > I'll have to recall the entire batch of 000090?
> > > >
> > > > How would we be able to best handle this then?
> > > > I was thinking of using 000090-1, 000090-2, 000090-3 and so on
> > until
> > > > the last run.
> > > >
> > > > Of course, there may be a possibility that a part of the job
> will
> > be
> > > > taking in 2 lots of materials, but at least we would've kept

it

> > down
> > > > to a minimum, instead of recalling the entire batch of

100,000

> in
> > > job
> > > > 000090?
> > > >
> > > >
> > > > --- In vantage@yahoogroups <mailto:vantage%
> > 40yahoogroups.com> .com,
> > > "Manasa Reddy" <manasa@> wrote:
> > > > >
> > > > > Each labor detail record has a unique number...maybe you can
> > use
> > > that
> > > > > field on the shipment somehow as your traceability.
> > > > >
> > > > >
> > > > >
> > > > > Something to look at maybe....?????
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > M. Manasa Reddy
> > > > >
> > > > > manasa@
> > > > >
> > > > > P: 630-806-2000
> > > > >
> > > > > F: 630-806-2001
> > > > >
> > > > > ________________________________
> > > > >
> > > > > From: vantage@yahoogroups <mailto:vantage%
> > 40yahoogroups.com> .com
> > > [mailto:vantage@yahoogroups <mailto:vantage%
> > 40yahoogroups.com> .com] On
> > > Behalf
> > > > > Of Arnulfo Mora
> > > > > Sent: Tuesday, November 13, 2007 10:45 AM
> > > > > To: vantage@yahoogroups <mailto:vantage%
> 40yahoogroups.com> .com
> > > > > Subject: [Vantage] Re: Lot Tracking
> > > > >
> > > > >
> > > > >
> > > > > What we are currently planning is to use MES to report
> > quantities
> > > in
> > > > > the basket. When the operator finish a basket they will hit
> > report
> > > > > quantity in MES, print tag, and send it on to the next
> > operation
> > > or to
> > > > > shipping. For ASN's, we are required to have a unique

number

> on
> > > each
> > > > > shipment. With what we can currently tell, we will not be

able

> > to
> > > put
> > > > > a unique number on the shipping tag for traceability. This

is

> a
> > > > > requirement for many automotive companies. This unique

number

> > is
> > > used
> > > > > to track back to the exact time, date, steel coil, operator,
> > etc.
> > > when
> > > > > a customer calls in with a concern/rejection. We would use

the

> > > serial
> > > > > number for containment of all baskets created under a

certain

> > > steel
> > > > > tag number, after a certain number of hits, or any other

items

> > > that
> > > > > may be suspect. The unique number is the trigger for all
> > > > > correspondence with our customer. In essence, we need to
> > serialize
> > > > > every container (basket), but not every part. If you have

any

> > > > > additional questions, please let me know.
> > > > >
> > > > > Thanks in Advance,
> > > > >
> > > > > Eric
> > > > >
> > > > >
> > > > > --- In vantage@yahoogroups <mailto:vantage%
> > 40yahoogroups.com> .com
> > > <mailto:vantage%
> > > 40yahoogroups.com> ,
> > > > > "Michael McWilliams"
> > > > > <mmcwilliams22@> wrote:
> > > > > >
> > > > > > Right now they are in Numeric fields. Every receipt line

is

> a
> > > > > > new "Lot" basically serial but not exactly. That number is
> > > generated
> > > > > > by getting the next number from a UD table & creating a
> > > > > > corresponding UD record. It then takes the numbers that

you

> > > entered
> > > > > > and pushes them into the UD table. I am working on a
> > > verification
> > > > > > that will only allow you to enter if the properties are
> > within
> > > > > > acceptable values.
> > > > > >
> > > > > > We are required to have a "Bundle" number on our shipping
> > tags.
> > > > > > Every bundle gets a unique number. Since you are creating
> > > baskets
> > > > > > of parts I do not belive that the Vantage serialization

will

> > > work.
> > > > > > It wants you to give a uniqe number to every unit that is
> > > created.
> > > > > > I have a question about your creation of baskets. Do you

use

> > > MES to
> > > > > > do this or will it be done in the office?
> > > > > > --- In vantage@yahoogroups <mailto:vantage%
> > 40yahoogroups.com> .com
> > > <mailto:vantage%
> > > 40yahoogroups.com> ,
> > > > > "Arnulfo Mora" <amora@> wrote:
> > > > > > >
> > > > > > > Mr. McWilliams,
> > > > > > >
> > > > > > > How are you entering all of the Physical and Chemical
> > > properties
> > > > > > into
> > > > > > > Vantage? Are you just dumping the information into a

text

> > > field,
> > > > > > or
> > > > > > > are you taking that information and verifying it

against a

> > > material
> > > > > > > specification? Also, are you required to have a serial
> > number
> > > on
> > > > > > your
> > > > > > > shipping tags? We are currently implementing Vantage and
> > are
> > > > > > looking
> > > > > > > for a way to use a serial number to track individual
> > baskets
> > > of
> > > > > > parts
> > > > > > > shipped to our customer. The serial number would be a

self

> > > > > > > populating, unique, sequential number. Thanks for any
> > > information
> > > > > > in
> > > > > > > advance.
> > > > > > >
> > > > > > > Eric
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > [Non-text portions of this message have been removed]
> > > > >
> > > >
> > >
> > >
> > >
> > >
> > >
> > > [Non-text portions of this message have been removed]
> > >
> >
> >
> >
> > ________________________________
> > The information contained in this message is intended solely for
> the individual to whom it is specifically and originally addressed.
> This message and its contents may contain confidential or

privileged

> information. If you are not the intended recipient, you are hereby
> notified that any disclosure or distribution, or taking any action

in

> reliance on the contents of this information, is strictly

prohibited.

> > 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 cannot accept

liability

> for any loss or damage caused by software viruses.
> >
> > This message (including any attachments) is intended only for
> > the use of the individual or entity to which it is addressed and
> > may contain information that is non-public, proprietary,
> > privileged, confidential, and exempt from disclosure under
> > applicable law or may constitute as attorney work product.
> > If you are not the intended recipient, you are hereby notified
> > that any use, dissemination, distribution, or copying of this
> > communication is strictly prohibited. If you have received this
> > communication in error, notify us immediately by telephone and
> > (i) destroy this message if a facsimile or (ii) delete this

message

> > immediately if this is an electronic communication.
> >
> > Thank you.
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
>
>

.

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

system · July 14, 2008, 1:14pm

Sorry - Never have tried use of it. (You put it well - too scary!)

Maybe Mark W?

Rob

--- On Mon, 7/14/08, nmtaylor1969 <n.taylor@...> wrote:

From: nmtaylor1969 <n.taylor@...>
Subject: [Vantage] Re: Lot Tracking / Rob Can You Help ?!
To: vantage@yahoogroups.com
Date: Monday, July 14, 2008, 8:06 AM

Ed,

We have discovered a bug in the code I sent you ( typical! ), and I
am currently investigating the problem.

I think the call to oTrans.NotifyAll( ) is causing the record pointer
to move by accident. I believe this is resulting in the wrong parts
being receipted on some occasions by our operators.

Rob, perhaps your knowledge may be able to assist ?

I notice from the object explorer that this method can be called in
two ways:-

oTrans.NotifyAll( BruteForce) Scary or what!?
oTrans.NotifyAll( type, view)

I am hoping that the latter restricts the refresh to the current
dataview and might stop the record pointer from moving. Its a stab in
the dark, but I might be right...

The "type" parameter is described as:
Epicor.Mfg.UI. FrameWork. EpiTransaction+ NotifyType

My skills are not good enough for me to deduce what this parameter
is. Would you happen to know ?

I have sent an e-mail to Epicor support, but sometimes this can be a
much faster medium. Any help would be gratefully received.

Thanks,

Nick

--- In vantage@yahoogroups .com, Ed Garbowski <egarbowski@ ...> wrote:
>
> Nick,
> Your Date/Timestamp lot numbering is an excellent idea that I
would like to use as we implement Vantage here. Would you be willing
to share your code for your Receipt Entry button to generate your Lot
numbers?
>
> Thanks,
> Ed
>
>
> ____________ _________ _________ __
> From: vantage@yahoogroups .com [mailto:vantage@yahoogroups .com] On
Behalf Of nmtaylor1969
> Sent: Saturday, June 28, 2008 1:38 AM
> To: vantage@yahoogroups .com
> Subject: [Vantage] Re: Lot Tracking
>
>
> I agree with your comments. Just to remove any ambiguity, we use
> serial number tracking for all appropriate manufactured parts that
we
> make in-house, and we use lot-tracking for material receipts coming
> in from vendors. Currently every receipt line will get a different
> lot number, but I guess in reality we could probably make a lot
> number apply to all lines on a specific receipt. ( I haven't tried
> this, so I dont know if Vahtage will allow different parts to exist
> within one lot ). We merely wish to know where any given part came
> from in the event we have a field failure etc. A lot number based on
> a date and time code works well in our particular application.
>
> --- In vantage@yahoogroups .com<mailto:vantage%
40yahoogroups. com>, "Kevin Kadamus" <kkadamus@> wrote:
> >
> > Lot Tracking is a very good tool for keeping a record of daily
> or "runs" of
> > production for Items or groups of items that need to be tracked
for
> a
> > multiple of reasons. Lot Tracking is a manual tracking method and
> is not
> > designed for generating a unique number for each item. If you are
> in need
> > of uniquely identifying each item made take a look at serial
> numbers.
> > Serial numbers are a great way to guarantee that every item
> produced has its
> > own identification that you can access at any time now and in the
> future.
> > There IS more work involved by using them but in many cases well
> worth the
> > extra effort. Ask your CAM or call me for more information if you
> are
> > interested.
> >
> >
> >
> >
> >
> > Thank you,
> >
> >
> >
> >
> >
> > Kevin Kadamus
> >
> > Senior Consultant
> >
> > Epicor Authorized Partner
> >
> >
> >
> > kkadamus@
> >
> > 952-905-0387
> >
> >
> >
> > CONFIDENTIALITY NOTICE: This electronic email transmission may
> contain
> > consultant/client privilege and confidential information intended
> only for
> > the individual or entity named above. Any dissemination, use,
> distribution,
> > copying or disclosure of this communication by any other person or
> entity is
> > strictly prohibited. Should you receive this transmission in
error,
> please
> > notify the sender by telephone at 952-905-0387.
> >
> > _____
> >
> > From: vantage@yahoogroups .com<mailto:vantage% 40yahoogroups. com>
[mailto:vantage@yahoogroups .com<mailto:vantage% 40yahoogroups. com>] On
> Behalf Of
> > nmtaylor1969
> > Sent: Friday, June 27, 2008 4:18 AM
> > To: vantage@yahoogroups .com<mailto:vantage% 40yahoogroups. com>
> > Subject: [Vantage] Re: Lot Tracking
> >
> >
> >
> > Note sure if this will help:-
> >
> > We also use lot tracking for many of our parts. Vantage doesn't
> have
> > the capability to auto-generate a next lot number, and having a
> > number of goods receiving operators meant that it was difficult to
> > decide what the next lot number would be. We would have to record
> it
> > off-system somewhere, and this was going to be a pain to manage.
> >
> > I therefore added a button to the receipt entry form which
> calculates
> > a lot number based on a date and time code. In fact I use the
> > following format: "080627/45567" . The first 6-digits are the year,
> > the month and the day, and the last 5 digits are the number of
> > seconds which elapsed since midnight. Hence lot numbers are
> specific
> > to the date and time the part was entered ( at a resolution of 1-
> > second ). Ok, we will have a problem if two people enter parts at
> > exactly the same time, but that has never happened yet :o)
> >
> > Therefore when the goods receiving operator enters the next part,
> > they click my "Get Lot Number" button, and the next lot number is
> > generated and stored in the field.
> >
> > We find this works pretty well...
> >
> > I hope this helps!
> >
> > Nick Taylor
> >
> > --- In vantage@yahoogroups <mailto:vantage%
40yahoogroups. com> .com,
> > "eltaria.foong" <eltaria.foong@ >
> > wrote:
> > >
> > > Hi, I've been thinking about Lot Tracking in Vantage too.
> > >
> > > Someone mentioned they use Job Number as lot number, let's say i
> > have
> > > a Job 000090 which runs for a month, during the course of the
> > > production, I've received 2 different lot of the same materials,
> > lot A
> > > 56,000 and lot B 44,000.
> > >
> > > If I saved the finished good under Lot 000090, and 1 month down
> the
> > > road the supplier called and said Lot A is problematic, seems
like
> > > I'll have to recall the entire batch of 000090?
> > >
> > > How would we be able to best handle this then?
> > > I was thinking of using 000090-1, 000090-2, 000090-3 and so on
> until
> > > the last run.
> > >
> > > Of course, there may be a possibility that a part of the job
will
> be
> > > taking in 2 lots of materials, but at least we would've kept it
> down
> > > to a minimum, instead of recalling the entire batch of 100,000
in
> > job
> > > 000090?
> > >
> > >
> > > --- In vantage@yahoogroups <mailto:vantage%
> 40yahoogroups. com> .com,
> > "Manasa Reddy" <manasa@> wrote:
> > > >
> > > > Each labor detail record has a unique number...maybe you can
> use
> > that
> > > > field on the shipment somehow as your traceability.
> > > >
> > > >
> > > >
> > > > Something to look at maybe....??? ??
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > M. Manasa Reddy
> > > >
> > > > manasa@
> > > >
> > > > P: 630-806-2000
> > > >
> > > > F: 630-806-2001
> > > >
> > > > ____________ _________ _________ __
> > > >
> > > > From: vantage@yahoogroups <mailto:vantage%
> 40yahoogroups. com> .com
> > [mailto:vantage@ yahoogroups <mailto:vantage%
> 40yahoogroups. com> .com] On
> > Behalf
> > > > Of Arnulfo Mora
> > > > Sent: Tuesday, November 13, 2007 10:45 AM
> > > > To: vantage@yahoogroups <mailto:vantage%
40yahoogroups. com> .com
> > > > Subject: [Vantage] Re: Lot Tracking
> > > >
> > > >
> > > >
> > > > What we are currently planning is to use MES to report
> quantities
> > in
> > > > the basket. When the operator finish a basket they will hit
> report
> > > > quantity in MES, print tag, and send it on to the next
> operation
> > or to
> > > > shipping. For ASN's, we are required to have a unique number
on
> > each
> > > > shipment. With what we can currently tell, we will not be able
> to
> > put
> > > > a unique number on the shipping tag for traceability. This is
a
> > > > requirement for many automotive companies. This unique number
> is
> > used
> > > > to track back to the exact time, date, steel coil, operator,
> etc.
> > when
> > > > a customer calls in with a concern/rejection. We would use the
> > serial
> > > > number for containment of all baskets created under a certain
> > steel
> > > > tag number, after a certain number of hits, or any other items
> > that
> > > > may be suspect. The unique number is the trigger for all
> > > > correspondence with our customer. In essence, we need to
> serialize
> > > > every container (basket), but not every part. If you have any
> > > > additional questions, please let me know.
> > > >
> > > > Thanks in Advance,
> > > >
> > > > Eric
> > > >
> > > >
> > > > --- In vantage@yahoogroups <mailto:vantage%
> 40yahoogroups. com> .com
> > <mailto:vantage%
> > 40yahoogroups. com> ,
> > > > "Michael McWilliams"
> > > > <mmcwilliams22@ > wrote:
> > > > >
> > > > > Right now they are in Numeric fields. Every receipt line is
a
> > > > > new "Lot" basically serial but not exactly. That number is
> > generated
> > > > > by getting the next number from a UD table & creating a
> > > > > corresponding UD record. It then takes the numbers that you
> > entered
> > > > > and pushes them into the UD table. I am working on a
> > verification
> > > > > that will only allow you to enter if the properties are
> within
> > > > > acceptable values.
> > > > >
> > > > > We are required to have a "Bundle" number on our shipping
> tags.
> > > > > Every bundle gets a unique number. Since you are creating
> > baskets
> > > > > of parts I do not belive that the Vantage serialization will
> > work.
> > > > > It wants you to give a uniqe number to every unit that is
> > created.
> > > > > I have a question about your creation of baskets. Do you use
> > MES to
> > > > > do this or will it be done in the office?
> > > > > --- In vantage@yahoogroups <mailto:vantage%
> 40yahoogroups. com> .com
> > <mailto:vantage%
> > 40yahoogroups. com> ,
> > > > "Arnulfo Mora" <amora@> wrote:
> > > > > >
> > > > > > Mr. McWilliams,
> > > > > >
> > > > > > How are you entering all of the Physical and Chemical
> > properties
> > > > > into
> > > > > > Vantage? Are you just dumping the information into a text
> > field,
> > > > > or
> > > > > > are you taking that information and verifying it against a
> > material
> > > > > > specification? Also, are you required to have a serial
> number
> > on
> > > > > your
> > > > > > shipping tags? We are currently implementing Vantage and
> are
> > > > > looking
> > > > > > for a way to use a serial number to track individual
> baskets
> > of
> > > > > parts
> > > > > > shipped to our customer. The serial number would be a self
> > > > > > populating, unique, sequential number. Thanks for any
> > information
> > > > > in
> > > > > > advance.
> > > > > >
> > > > > > Eric
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > [Non-text portions of this message have been removed]
> > > >
> > >
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
> ____________ _________ _________ __
> The information contained in this message is intended solely for
the individual to whom it is specifically and originally addressed.
This message and its contents may contain confidential or privileged
information. If you are not the intended recipient, you are hereby
notified that any disclosure or distribution, or taking any action in
reliance on the contents of this information, is strictly prohibited.
> 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 cannot accept liability
for any loss or damage caused by software viruses.
>
> This message (including any attachments) is intended only for
> the use of the individual or entity to which it is addressed and
> may contain information that is non-public, proprietary,
> privileged, confidential, and exempt from disclosure under
> applicable law or may constitute as attorney work product.
> If you are not the intended recipient, you are hereby notified
> that any use, dissemination, distribution, or copying of this
> communication is strictly prohibited. If you have received this
> communication in error, notify us immediately by telephone and
> (i) destroy this message if a facsimile or (ii) delete this message
> immediately if this is an electronic communication.
>
> Thank you.
>
>
> [Non-text portions of this message have been removed]
>

system · July 14, 2008, 5:17pm

>
> Sorry - Never have tried use of it. (You put it well - too scary!)
>
> Maybe Mark W?

When it comes to serious VB customization, I defer to Steve E. or Bernie W.

Separately, I figured that since Epicor took a lot of trouble to separate
the user interface from the business rules that I would try to put business
logic into BPMs instead of user interface.

But since you're asking for this on a click event, I wonder if it's possible
to fire a BPM event from a button and have that code update the lot field?

Mark W.

system · July 14, 2008, 7:45pm

Neat idea Mark... Trap the BO method called when the (presumably native)button is clicked?

Rob

--- On Mon, 7/14/08, Mark Wonsil <mark_wonsil@...> wrote:

From: Mark Wonsil <mark_wonsil@...>
Subject: RE: [Vantage] Re: Lot Tracking / Rob Can You Help ?!
To: vantage@yahoogroups.com
Date: Monday, July 14, 2008, 5:17 PM

>
> Sorry - Never have tried use of it. (You put it well - too scary!)
>
> Maybe Mark W?

When it comes to serious VB customization, I defer to Steve E. or Bernie W.

Separately, I figured that since Epicor took a lot of trouble to separate
the user interface from the business rules that I would try to put business
logic into BPMs instead of user interface.

But since you're asking for this on a click event, I wonder if it's possible
to fire a BPM event from a button and have that code update the lot field?

Mark W.

system · July 18, 2008, 8:23am

Ed,

The magic line of code in the lot tracking code snippet is:

edvStockDtl.Notify( New EpiNotifyArgs(oTrans.EpiBaseForm,
edvStockDtl.Row, EpiTransaction.NotifyType.Initialize ))

This should replace the oTrans.NotifyAll() method call. You will need
change the dataview name as required.

You should find the lot tracking code now works fine. ;o)

Thanks to Epicor for helping me out with this...

Nick

--- In vantage@yahoogroups.com, Ed Garbowski <egarbowski@...> wrote:
>
> Nick,
> Your Date/Timestamp lot numbering is an excellent idea that I
would like to use as we implement Vantage here. Would you be willing
to share your code for your Receipt Entry button to generate your Lot
numbers?
>
> Thanks,
> Ed
>
>
> ________________________________
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On
Behalf Of nmtaylor1969
> Sent: Saturday, June 28, 2008 1:38 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: Lot Tracking
>
>
> I agree with your comments. Just to remove any ambiguity, we use
> serial number tracking for all appropriate manufactured parts that
we
> make in-house, and we use lot-tracking for material receipts coming
> in from vendors. Currently every receipt line will get a different
> lot number, but I guess in reality we could probably make a lot
> number apply to all lines on a specific receipt. ( I haven't tried
> this, so I dont know if Vahtage will allow different parts to exist
> within one lot ). We merely wish to know where any given part came
> from in the event we have a field failure etc. A lot number based on
> a date and time code works well in our particular application.
>
> --- In vantage@yahoogroups.com<mailto:vantage%
40yahoogroups.com>, "Kevin Kadamus" <kkadamus@> wrote:
> >
> > Lot Tracking is a very good tool for keeping a record of daily
> or "runs" of
> > production for Items or groups of items that need to be tracked
for
> a
> > multiple of reasons. Lot Tracking is a manual tracking method and
> is not
> > designed for generating a unique number for each item. If you are
> in need
> > of uniquely identifying each item made take a look at serial
> numbers.
> > Serial numbers are a great way to guarantee that every item
> produced has its
> > own identification that you can access at any time now and in the
> future.
> > There IS more work involved by using them but in many cases well
> worth the
> > extra effort. Ask your CAM or call me for more information if you
> are
> > interested.
> >
> >
> >
> >
> >
> > Thank you,
> >
> >
> >
> >
> >
> > Kevin Kadamus
> >
> > Senior Consultant
> >
> > Epicor Authorized Partner
> >
> >
> >
> > kkadamus@
> >
> > 952-905-0387
> >
> >
> >
> > CONFIDENTIALITY NOTICE: This electronic email transmission may
> contain
> > consultant/client privilege and confidential information intended
> only for
> > the individual or entity named above. Any dissemination, use,
> distribution,
> > copying or disclosure of this communication by any other person or
> entity is
> > strictly prohibited. Should you receive this transmission in
error,
> please
> > notify the sender by telephone at 952-905-0387.
> >
> > _____
> >
> > From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On
> Behalf Of
> > nmtaylor1969
> > Sent: Friday, June 27, 2008 4:18 AM
> > To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
> > Subject: [Vantage] Re: Lot Tracking
> >
> >
> >
> > Note sure if this will help:-
> >
> > We also use lot tracking for many of our parts. Vantage doesn't
> have
> > the capability to auto-generate a next lot number, and having a
> > number of goods receiving operators meant that it was difficult to
> > decide what the next lot number would be. We would have to record
> it
> > off-system somewhere, and this was going to be a pain to manage.
> >
> > I therefore added a button to the receipt entry form which
> calculates
> > a lot number based on a date and time code. In fact I use the
> > following format: "080627/45567". The first 6-digits are the year,
> > the month and the day, and the last 5 digits are the number of
> > seconds which elapsed since midnight. Hence lot numbers are
> specific
> > to the date and time the part was entered ( at a resolution of 1-
> > second ). Ok, we will have a problem if two people enter parts at
> > exactly the same time, but that has never happened yet :o)
> >
> > Therefore when the goods receiving operator enters the next part,
> > they click my "Get Lot Number" button, and the next lot number is
> > generated and stored in the field.
> >
> > We find this works pretty well...
> >
> > I hope this helps!
> >
> > Nick Taylor
> >
> > --- In vantage@yahoogroups <mailto:vantage%
40yahoogroups.com> .com,
> > "eltaria.foong" <eltaria.foong@>
> > wrote:
> > >
> > > Hi, I've been thinking about Lot Tracking in Vantage too.
> > >
> > > Someone mentioned they use Job Number as lot number, let's say i
> > have
> > > a Job 000090 which runs for a month, during the course of the
> > > production, I've received 2 different lot of the same materials,
> > lot A
> > > 56,000 and lot B 44,000.
> > >
> > > If I saved the finished good under Lot 000090, and 1 month down
> the
> > > road the supplier called and said Lot A is problematic, seems
like
> > > I'll have to recall the entire batch of 000090?
> > >
> > > How would we be able to best handle this then?
> > > I was thinking of using 000090-1, 000090-2, 000090-3 and so on
> until
> > > the last run.
> > >
> > > Of course, there may be a possibility that a part of the job
will
> be
> > > taking in 2 lots of materials, but at least we would've kept it
> down
> > > to a minimum, instead of recalling the entire batch of 100,000
in
> > job
> > > 000090?
> > >
> > >
> > > --- In vantage@yahoogroups <mailto:vantage%
> 40yahoogroups.com> .com,
> > "Manasa Reddy" <manasa@> wrote:
> > > >
> > > > Each labor detail record has a unique number...maybe you can
> use
> > that
> > > > field on the shipment somehow as your traceability.
> > > >
> > > >
> > > >
> > > > Something to look at maybe....?????
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > M. Manasa Reddy
> > > >
> > > > manasa@
> > > >
> > > > P: 630-806-2000
> > > >
> > > > F: 630-806-2001
> > > >
> > > > ________________________________
> > > >
> > > > From: vantage@yahoogroups <mailto:vantage%
> 40yahoogroups.com> .com
> > [mailto:vantage@yahoogroups <mailto:vantage%
> 40yahoogroups.com> .com] On
> > Behalf
> > > > Of Arnulfo Mora
> > > > Sent: Tuesday, November 13, 2007 10:45 AM
> > > > To: vantage@yahoogroups <mailto:vantage%
40yahoogroups.com> .com
> > > > Subject: [Vantage] Re: Lot Tracking
> > > >
> > > >
> > > >
> > > > What we are currently planning is to use MES to report
> quantities
> > in
> > > > the basket. When the operator finish a basket they will hit
> report
> > > > quantity in MES, print tag, and send it on to the next
> operation
> > or to
> > > > shipping. For ASN's, we are required to have a unique number
on
> > each
> > > > shipment. With what we can currently tell, we will not be able
> to
> > put
> > > > a unique number on the shipping tag for traceability. This is
a
> > > > requirement for many automotive companies. This unique number
> is
> > used
> > > > to track back to the exact time, date, steel coil, operator,
> etc.
> > when
> > > > a customer calls in with a concern/rejection. We would use the
> > serial
> > > > number for containment of all baskets created under a certain
> > steel
> > > > tag number, after a certain number of hits, or any other items
> > that
> > > > may be suspect. The unique number is the trigger for all
> > > > correspondence with our customer. In essence, we need to
> serialize
> > > > every container (basket), but not every part. If you have any
> > > > additional questions, please let me know.
> > > >
> > > > Thanks in Advance,
> > > >
> > > > Eric
> > > >
> > > >
> > > > --- In vantage@yahoogroups <mailto:vantage%
> 40yahoogroups.com> .com
> > <mailto:vantage%
> > 40yahoogroups.com> ,
> > > > "Michael McWilliams"
> > > > <mmcwilliams22@> wrote:
> > > > >
> > > > > Right now they are in Numeric fields. Every receipt line is
a
> > > > > new "Lot" basically serial but not exactly. That number is
> > generated
> > > > > by getting the next number from a UD table & creating a
> > > > > corresponding UD record. It then takes the numbers that you
> > entered
> > > > > and pushes them into the UD table. I am working on a
> > verification
> > > > > that will only allow you to enter if the properties are
> within
> > > > > acceptable values.
> > > > >
> > > > > We are required to have a "Bundle" number on our shipping
> tags.
> > > > > Every bundle gets a unique number. Since you are creating
> > baskets
> > > > > of parts I do not belive that the Vantage serialization will
> > work.
> > > > > It wants you to give a uniqe number to every unit that is
> > created.
> > > > > I have a question about your creation of baskets. Do you use
> > MES to
> > > > > do this or will it be done in the office?
> > > > > --- In vantage@yahoogroups <mailto:vantage%
> 40yahoogroups.com> .com
> > <mailto:vantage%
> > 40yahoogroups.com> ,
> > > > "Arnulfo Mora" <amora@> wrote:
> > > > > >
> > > > > > Mr. McWilliams,
> > > > > >
> > > > > > How are you entering all of the Physical and Chemical
> > properties
> > > > > into
> > > > > > Vantage? Are you just dumping the information into a text
> > field,
> > > > > or
> > > > > > are you taking that information and verifying it against a
> > material
> > > > > > specification? Also, are you required to have a serial
> number
> > on
> > > > > your
> > > > > > shipping tags? We are currently implementing Vantage and
> are
> > > > > looking
> > > > > > for a way to use a serial number to track individual
> baskets
> > of
> > > > > parts
> > > > > > shipped to our customer. The serial number would be a self
> > > > > > populating, unique, sequential number. Thanks for any
> > information
> > > > > in
> > > > > > advance.
> > > > > >
> > > > > > Eric
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > [Non-text portions of this message have been removed]
> > > >
> > >
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
> ________________________________
> The information contained in this message is intended solely for
the individual to whom it is specifically and originally addressed.
This message and its contents may contain confidential or privileged
information. If you are not the intended recipient, you are hereby
notified that any disclosure or distribution, or taking any action in
reliance on the contents of this information, is strictly prohibited.
> 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 cannot accept liability
for any loss or damage caused by software viruses.
>
> This message (including any attachments) is intended only for
> the use of the individual or entity to which it is addressed and
> may contain information that is non-public, proprietary,
> privileged, confidential, and exempt from disclosure under
> applicable law or may constitute as attorney work product.
> If you are not the intended recipient, you are hereby notified
> that any use, dissemination, distribution, or copying of this
> communication is strictly prohibited. If you have received this
> communication in error, notify us immediately by telephone and
> (i) destroy this message if a facsimile or (ii) delete this message
> immediately if this is an electronic communication.
>
> Thank you.
>
>
> [Non-text portions of this message have been removed]
>

system · July 18, 2008, 8:52am

Thanks for the code and the 'beau cous' of time that you saved me in trying to make this work myself. Greatly appreciated!

Ed

________________________________
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of nmtaylor1969
Sent: Friday, July 18, 2008 7:23 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Lot Tracking

Ed,

The magic line of code in the lot tracking code snippet is:

edvStockDtl.Notify( New EpiNotifyArgs(oTrans.EpiBaseForm,
edvStockDtl.Row, EpiTransaction.NotifyType.Initialize ))

This should replace the oTrans.NotifyAll() method call. You will need
change the dataview name as required.

You should find the lot tracking code now works fine. ;o)

Thanks to Epicor for helping me out with this...

Nick

--- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>, Ed Garbowski <egarbowski@...> wrote:
>
> Nick,
> Your Date/Timestamp lot numbering is an excellent idea that I
would like to use as we implement Vantage here. Would you be willing
to share your code for your Receipt Entry button to generate your Lot
numbers?
>
> Thanks,
> Ed
>
>
> ________________________________
> From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On
Behalf Of nmtaylor1969
> Sent: Saturday, June 28, 2008 1:38 AM
> To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
> Subject: [Vantage] Re: Lot Tracking
>
>
> I agree with your comments. Just to remove any ambiguity, we use
> serial number tracking for all appropriate manufactured parts that
we
> make in-house, and we use lot-tracking for material receipts coming
> in from vendors. Currently every receipt line will get a different
> lot number, but I guess in reality we could probably make a lot
> number apply to all lines on a specific receipt. ( I haven't tried
> this, so I dont know if Vahtage will allow different parts to exist
> within one lot ). We merely wish to know where any given part came
> from in the event we have a field failure etc. A lot number based on
> a date and time code works well in our particular application.
>
> --- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com><mailto:vantage%
40yahoogroups.com>, "Kevin Kadamus" <kkadamus@> wrote:
> >
> > Lot Tracking is a very good tool for keeping a record of daily
> or "runs" of
> > production for Items or groups of items that need to be tracked
for
> a
> > multiple of reasons. Lot Tracking is a manual tracking method and
> is not
> > designed for generating a unique number for each item. If you are
> in need
> > of uniquely identifying each item made take a look at serial
> numbers.
> > Serial numbers are a great way to guarantee that every item
> produced has its
> > own identification that you can access at any time now and in the
> future.
> > There IS more work involved by using them but in many cases well
> worth the
> > extra effort. Ask your CAM or call me for more information if you
> are
> > interested.
> >
> >
> >
> >
> >
> > Thank you,
> >
> >
> >
> >
> >
> > Kevin Kadamus
> >
> > Senior Consultant
> >
> > Epicor Authorized Partner
> >
> >
> >
> > kkadamus@
> >
> > 952-905-0387
> >
> >
> >
> > CONFIDENTIALITY NOTICE: This electronic email transmission may
> contain
> > consultant/client privilege and confidential information intended
> only for
> > the individual or entity named above. Any dissemination, use,
> distribution,
> > copying or disclosure of this communication by any other person or
> entity is
> > strictly prohibited. Should you receive this transmission in
error,
> please
> > notify the sender by telephone at 952-905-0387.
> >
> > _____
> >
> > From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com>] On
> Behalf Of
> > nmtaylor1969
> > Sent: Friday, June 27, 2008 4:18 AM
> > To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com>
> > Subject: [Vantage] Re: Lot Tracking
> >
> >
> >
> > Note sure if this will help:-
> >
> > We also use lot tracking for many of our parts. Vantage doesn't
> have
> > the capability to auto-generate a next lot number, and having a
> > number of goods receiving operators meant that it was difficult to
> > decide what the next lot number would be. We would have to record
> it
> > off-system somewhere, and this was going to be a pain to manage.
> >
> > I therefore added a button to the receipt entry form which
> calculates
> > a lot number based on a date and time code. In fact I use the
> > following format: "080627/45567". The first 6-digits are the year,
> > the month and the day, and the last 5 digits are the number of
> > seconds which elapsed since midnight. Hence lot numbers are
> specific
> > to the date and time the part was entered ( at a resolution of 1-
> > second ). Ok, we will have a problem if two people enter parts at
> > exactly the same time, but that has never happened yet :o)
> >
> > Therefore when the goods receiving operator enters the next part,
> > they click my "Get Lot Number" button, and the next lot number is
> > generated and stored in the field.
> >
> > We find this works pretty well...
> >
> > I hope this helps!
> >
> > Nick Taylor
> >
> > --- In vantage@yahoogroups <mailto:vantage%
40yahoogroups.com> .com,
> > "eltaria.foong" <eltaria.foong@>
> > wrote:
> > >
> > > Hi, I've been thinking about Lot Tracking in Vantage too.
> > >
> > > Someone mentioned they use Job Number as lot number, let's say i
> > have
> > > a Job 000090 which runs for a month, during the course of the
> > > production, I've received 2 different lot of the same materials,
> > lot A
> > > 56,000 and lot B 44,000.
> > >
> > > If I saved the finished good under Lot 000090, and 1 month down
> the
> > > road the supplier called and said Lot A is problematic, seems
like
> > > I'll have to recall the entire batch of 000090?
> > >
> > > How would we be able to best handle this then?
> > > I was thinking of using 000090-1, 000090-2, 000090-3 and so on
> until
> > > the last run.
> > >
> > > Of course, there may be a possibility that a part of the job
will
> be
> > > taking in 2 lots of materials, but at least we would've kept it
> down
> > > to a minimum, instead of recalling the entire batch of 100,000
in
> > job
> > > 000090?
> > >
> > >
> > > --- In vantage@yahoogroups <mailto:vantage%
> 40yahoogroups.com> .com,
> > "Manasa Reddy" <manasa@> wrote:
> > > >
> > > > Each labor detail record has a unique number...maybe you can
> use
> > that
> > > > field on the shipment somehow as your traceability.
> > > >
> > > >
> > > >
> > > > Something to look at maybe....?????
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > M. Manasa Reddy
> > > >
> > > > manasa@
> > > >
> > > > P: 630-806-2000
> > > >
> > > > F: 630-806-2001
> > > >
> > > > ________________________________
> > > >
> > > > From: vantage@yahoogroups <mailto:vantage%
> 40yahoogroups.com> .com
> > [mailto:vantage@yahoogroups <mailto:vantage%
> 40yahoogroups.com> .com] On
> > Behalf
> > > > Of Arnulfo Mora
> > > > Sent: Tuesday, November 13, 2007 10:45 AM
> > > > To: vantage@yahoogroups <mailto:vantage%
40yahoogroups.com> .com
> > > > Subject: [Vantage] Re: Lot Tracking
> > > >
> > > >
> > > >
> > > > What we are currently planning is to use MES to report
> quantities
> > in
> > > > the basket. When the operator finish a basket they will hit
> report
> > > > quantity in MES, print tag, and send it on to the next
> operation
> > or to
> > > > shipping. For ASN's, we are required to have a unique number
on
> > each
> > > > shipment. With what we can currently tell, we will not be able
> to
> > put
> > > > a unique number on the shipping tag for traceability. This is
a
> > > > requirement for many automotive companies. This unique number
> is
> > used
> > > > to track back to the exact time, date, steel coil, operator,
> etc.
> > when
> > > > a customer calls in with a concern/rejection. We would use the
> > serial
> > > > number for containment of all baskets created under a certain
> > steel
> > > > tag number, after a certain number of hits, or any other items
> > that
> > > > may be suspect. The unique number is the trigger for all
> > > > correspondence with our customer. In essence, we need to
> serialize
> > > > every container (basket), but not every part. If you have any
> > > > additional questions, please let me know.
> > > >
> > > > Thanks in Advance,
> > > >
> > > > Eric
> > > >
> > > >
> > > > --- In vantage@yahoogroups <mailto:vantage%
> 40yahoogroups.com> .com
> > <mailto:vantage%
> > 40yahoogroups.com> ,
> > > > "Michael McWilliams"
> > > > <mmcwilliams22@> wrote:
> > > > >
> > > > > Right now they are in Numeric fields. Every receipt line is
a
> > > > > new "Lot" basically serial but not exactly. That number is
> > generated
> > > > > by getting the next number from a UD table & creating a
> > > > > corresponding UD record. It then takes the numbers that you
> > entered
> > > > > and pushes them into the UD table. I am working on a
> > verification
> > > > > that will only allow you to enter if the properties are
> within
> > > > > acceptable values.
> > > > >
> > > > > We are required to have a "Bundle" number on our shipping
> tags.
> > > > > Every bundle gets a unique number. Since you are creating
> > baskets
> > > > > of parts I do not belive that the Vantage serialization will
> > work.
> > > > > It wants you to give a uniqe number to every unit that is
> > created.
> > > > > I have a question about your creation of baskets. Do you use
> > MES to
> > > > > do this or will it be done in the office?
> > > > > --- In vantage@yahoogroups <mailto:vantage%
> 40yahoogroups.com> .com
> > <mailto:vantage%
> > 40yahoogroups.com> ,
> > > > "Arnulfo Mora" <amora@> wrote:
> > > > > >
> > > > > > Mr. McWilliams,
> > > > > >
> > > > > > How are you entering all of the Physical and Chemical
> > properties
> > > > > into
> > > > > > Vantage? Are you just dumping the information into a text
> > field,
> > > > > or
> > > > > > are you taking that information and verifying it against a
> > material
> > > > > > specification? Also, are you required to have a serial
> number
> > on
> > > > > your
> > > > > > shipping tags? We are currently implementing Vantage and
> are
> > > > > looking
> > > > > > for a way to use a serial number to track individual
> baskets
> > of
> > > > > parts
> > > > > > shipped to our customer. The serial number would be a self
> > > > > > populating, unique, sequential number. Thanks for any
> > information
> > > > > in
> > > > > > advance.
> > > > > >
> > > > > > Eric
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > [Non-text portions of this message have been removed]
> > > >
> > >
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
> ________________________________
> The information contained in this message is intended solely for
the individual to whom it is specifically and originally addressed.
This message and its contents may contain confidential or privileged
information. If you are not the intended recipient, you are hereby
notified that any disclosure or distribution, or taking any action in
reliance on the contents of this information, is strictly prohibited.
> 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 cannot accept liability
for any loss or damage caused by software viruses.
>
> This message (including any attachments) is intended only for
> the use of the individual or entity to which it is addressed and
> may contain information that is non-public, proprietary,
> privileged, confidential, and exempt from disclosure under
> applicable law or may constitute as attorney work product.
> If you are not the intended recipient, you are hereby notified
> that any use, dissemination, distribution, or copying of this
> communication is strictly prohibited. If you have received this
> communication in error, notify us immediately by telephone and
> (i) destroy this message if a facsimile or (ii) delete this message
> immediately if this is an electronic communication.
>
> Thank you.
>
>
> [Non-text portions of this message have been removed]
>

________________________________
The information contained in this message is intended solely for the individual to whom it is specifically and originally addressed. This message and its contents may contain confidential or privileged information. If you are not the intended recipient, you are hereby notified that any disclosure or distribution, or taking any action in reliance on the contents of this information, is strictly prohibited.
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 cannot accept liability for any loss or damage caused by software viruses.

This message (including any attachments) is intended only for
the use of the individual or entity to which it is addressed and
may contain information that is non-public, proprietary,
privileged, confidential, and exempt from disclosure under
applicable law or may constitute as attorney work product.
If you are not the intended recipient, you are hereby notified
that any use, dissemination, distribution, or copying of this
communication is strictly prohibited. If you have received this
communication in error, notify us immediately by telephone and
(i) destroy this message if a facsimile or (ii) delete this message
immediately if this is an electronic communication.

Thank you.

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

system · June 23, 2009, 8:41am

I am new to Vantage 8.03.407 and we have a similar situation where we create 'Printed Rolls' which are then converted into 'Cases' of 'Bags' and the 'Cases' are then created into a 'Pallet' and the PalletID is our unique container id that we need for shipping. I came across your message in this group and I wanted to reach out to see how did you eventually accomplish this. If you would be so kind as to possibly share your findings it would be greatly appreciated. Our PM for implementation has not been able to address this very important issues for us yet.

--- In vantage@yahoogroups.com, Ed Garbowski <egarbowski@...> wrote:
>
> Thanks for the code and the 'beau cous' of time that you saved me in trying to make this work myself. Greatly appreciated!
>
> Ed
>
>
> ________________________________
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of nmtaylor1969
> Sent: Friday, July 18, 2008 7:23 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: Lot Tracking
>
>
> Ed,
>
> The magic line of code in the lot tracking code snippet is:
>
> edvStockDtl.Notify( New EpiNotifyArgs(oTrans.EpiBaseForm,
> edvStockDtl.Row, EpiTransaction.NotifyType.Initialize ))
>
> This should replace the oTrans.NotifyAll() method call. You will need
> change the dataview name as required.
>
> You should find the lot tracking code now works fine. ;o)
>
> Thanks to Epicor for helping me out with this...
>
> Nick
>
> --- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>, Ed Garbowski <egarbowski@> wrote:
> >
> > Nick,
> > Your Date/Timestamp lot numbering is an excellent idea that I
> would like to use as we implement Vantage here. Would you be willing
> to share your code for your Receipt Entry button to generate your Lot
> numbers?
> >
> > Thanks,
> > Ed
> >
> >
> > ________________________________
> > From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On
> Behalf Of nmtaylor1969
> > Sent: Saturday, June 28, 2008 1:38 AM
> > To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
> > Subject: [Vantage] Re: Lot Tracking
> >
> >
> > I agree with your comments. Just to remove any ambiguity, we use
> > serial number tracking for all appropriate manufactured parts that
> we
> > make in-house, and we use lot-tracking for material receipts coming
> > in from vendors. Currently every receipt line will get a different
> > lot number, but I guess in reality we could probably make a lot
> > number apply to all lines on a specific receipt. ( I haven't tried
> > this, so I dont know if Vahtage will allow different parts to exist
> > within one lot ). We merely wish to know where any given part came
> > from in the event we have a field failure etc. A lot number based on
> > a date and time code works well in our particular application.
> >
> > --- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com><mailto:vantage%
> 40yahoogroups.com>, "Kevin Kadamus" <kkadamus@> wrote:
> > >
> > > Lot Tracking is a very good tool for keeping a record of daily
> > or "runs" of
> > > production for Items or groups of items that need to be tracked
> for
> > a
> > > multiple of reasons. Lot Tracking is a manual tracking method and
> > is not
> > > designed for generating a unique number for each item. If you are
> > in need
> > > of uniquely identifying each item made take a look at serial
> > numbers.
> > > Serial numbers are a great way to guarantee that every item
> > produced has its
> > > own identification that you can access at any time now and in the
> > future.
> > > There IS more work involved by using them but in many cases well
> > worth the
> > > extra effort. Ask your CAM or call me for more information if you
> > are
> > > interested.
> > >
> > >
> > >
> > >
> > >
> > > Thank you,
> > >
> > >
> > >
> > >
> > >
> > > Kevin Kadamus
> > >
> > > Senior Consultant
> > >
> > > Epicor Authorized Partner
> > >
> > >
> > >
> > > kkadamus@
> > >
> > > 952-905-0387
> > >
> > >
> > >
> > > CONFIDENTIALITY NOTICE: This electronic email transmission may
> > contain
> > > consultant/client privilege and confidential information intended
> > only for
> > > the individual or entity named above. Any dissemination, use,
> > distribution,
> > > copying or disclosure of this communication by any other person or
> > entity is
> > > strictly prohibited. Should you receive this transmission in
> error,
> > please
> > > notify the sender by telephone at 952-905-0387.
> > >
> > > _____
> > >
> > > From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com>
> [mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com>] On
> > Behalf Of
> > > nmtaylor1969
> > > Sent: Friday, June 27, 2008 4:18 AM
> > > To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com>
> > > Subject: [Vantage] Re: Lot Tracking
> > >
> > >
> > >
> > > Note sure if this will help:-
> > >
> > > We also use lot tracking for many of our parts. Vantage doesn't
> > have
> > > the capability to auto-generate a next lot number, and having a
> > > number of goods receiving operators meant that it was difficult to
> > > decide what the next lot number would be. We would have to record
> > it
> > > off-system somewhere, and this was going to be a pain to manage.
> > >
> > > I therefore added a button to the receipt entry form which
> > calculates
> > > a lot number based on a date and time code. In fact I use the
> > > following format: "080627/45567". The first 6-digits are the year,
> > > the month and the day, and the last 5 digits are the number of
> > > seconds which elapsed since midnight. Hence lot numbers are
> > specific
> > > to the date and time the part was entered ( at a resolution of 1-
> > > second ). Ok, we will have a problem if two people enter parts at
> > > exactly the same time, but that has never happened yet :o)
> > >
> > > Therefore when the goods receiving operator enters the next part,
> > > they click my "Get Lot Number" button, and the next lot number is
> > > generated and stored in the field.
> > >
> > > We find this works pretty well...
> > >
> > > I hope this helps!
> > >
> > > Nick Taylor
> > >
> > > --- In vantage@yahoogroups <mailto:vantage%
> 40yahoogroups.com> .com,
> > > "eltaria.foong" <eltaria.foong@>
> > > wrote:
> > > >
> > > > Hi, I've been thinking about Lot Tracking in Vantage too.
> > > >
> > > > Someone mentioned they use Job Number as lot number, let's say i
> > > have
> > > > a Job 000090 which runs for a month, during the course of the
> > > > production, I've received 2 different lot of the same materials,
> > > lot A
> > > > 56,000 and lot B 44,000.
> > > >
> > > > If I saved the finished good under Lot 000090, and 1 month down
> > the
> > > > road the supplier called and said Lot A is problematic, seems
> like
> > > > I'll have to recall the entire batch of 000090?
> > > >
> > > > How would we be able to best handle this then?
> > > > I was thinking of using 000090-1, 000090-2, 000090-3 and so on
> > until
> > > > the last run.
> > > >
> > > > Of course, there may be a possibility that a part of the job
> will
> > be
> > > > taking in 2 lots of materials, but at least we would've kept it
> > down
> > > > to a minimum, instead of recalling the entire batch of 100,000
> in
> > > job
> > > > 000090?
> > > >
> > > >
> > > > --- In vantage@yahoogroups <mailto:vantage%
> > 40yahoogroups.com> .com,
> > > "Manasa Reddy" <manasa@> wrote:
> > > > >
> > > > > Each labor detail record has a unique number...maybe you can
> > use
> > > that
> > > > > field on the shipment somehow as your traceability.
> > > > >
> > > > >
> > > > >
> > > > > Something to look at maybe....?????
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > M. Manasa Reddy
> > > > >
> > > > > manasa@
> > > > >
> > > > > P: 630-806-2000
> > > > >
> > > > > F: 630-806-2001
> > > > >
> > > > > ________________________________
> > > > >
> > > > > From: vantage@yahoogroups <mailto:vantage%
> > 40yahoogroups.com> .com
> > > [mailto:vantage@yahoogroups <mailto:vantage%
> > 40yahoogroups.com> .com] On
> > > Behalf
> > > > > Of Arnulfo Mora
> > > > > Sent: Tuesday, November 13, 2007 10:45 AM
> > > > > To: vantage@yahoogroups <mailto:vantage%
> 40yahoogroups.com> .com
> > > > > Subject: [Vantage] Re: Lot Tracking
> > > > >
> > > > >
> > > > >
> > > > > What we are currently planning is to use MES to report
> > quantities
> > > in
> > > > > the basket. When the operator finish a basket they will hit
> > report
> > > > > quantity in MES, print tag, and send it on to the next
> > operation
> > > or to
> > > > > shipping. For ASN's, we are required to have a unique number
> on
> > > each
> > > > > shipment. With what we can currently tell, we will not be able
> > to
> > > put
> > > > > a unique number on the shipping tag for traceability. This is
> a
> > > > > requirement for many automotive companies. This unique number
> > is
> > > used
> > > > > to track back to the exact time, date, steel coil, operator,
> > etc.
> > > when
> > > > > a customer calls in with a concern/rejection. We would use the
> > > serial
> > > > > number for containment of all baskets created under a certain
> > > steel
> > > > > tag number, after a certain number of hits, or any other items
> > > that
> > > > > may be suspect. The unique number is the trigger for all
> > > > > correspondence with our customer. In essence, we need to
> > serialize
> > > > > every container (basket), but not every part. If you have any
> > > > > additional questions, please let me know.
> > > > >
> > > > > Thanks in Advance,
> > > > >
> > > > > Eric
> > > > >
> > > > >
> > > > > --- In vantage@yahoogroups <mailto:vantage%
> > 40yahoogroups.com> .com
> > > <mailto:vantage%
> > > 40yahoogroups.com> ,
> > > > > "Michael McWilliams"
> > > > > <mmcwilliams22@> wrote:
> > > > > >
> > > > > > Right now they are in Numeric fields. Every receipt line is
> a
> > > > > > new "Lot" basically serial but not exactly. That number is
> > > generated
> > > > > > by getting the next number from a UD table & creating a
> > > > > > corresponding UD record. It then takes the numbers that you
> > > entered
> > > > > > and pushes them into the UD table. I am working on a
> > > verification
> > > > > > that will only allow you to enter if the properties are
> > within
> > > > > > acceptable values.
> > > > > >
> > > > > > We are required to have a "Bundle" number on our shipping
> > tags.
> > > > > > Every bundle gets a unique number. Since you are creating
> > > baskets
> > > > > > of parts I do not belive that the Vantage serialization will
> > > work.
> > > > > > It wants you to give a uniqe number to every unit that is
> > > created.
> > > > > > I have a question about your creation of baskets. Do you use
> > > MES to
> > > > > > do this or will it be done in the office?
> > > > > > --- In vantage@yahoogroups <mailto:vantage%
> > 40yahoogroups.com> .com
> > > <mailto:vantage%
> > > 40yahoogroups.com> ,
> > > > > "Arnulfo Mora" <amora@> wrote:
> > > > > > >
> > > > > > > Mr. McWilliams,
> > > > > > >
> > > > > > > How are you entering all of the Physical and Chemical
> > > properties
> > > > > > into
> > > > > > > Vantage? Are you just dumping the information into a text
> > > field,
> > > > > > or
> > > > > > > are you taking that information and verifying it against a
> > > material
> > > > > > > specification? Also, are you required to have a serial
> > number
> > > on
> > > > > > your
> > > > > > > shipping tags? We are currently implementing Vantage and
> > are
> > > > > > looking
> > > > > > > for a way to use a serial number to track individual
> > baskets
> > > of
> > > > > > parts
> > > > > > > shipped to our customer. The serial number would be a self
> > > > > > > populating, unique, sequential number. Thanks for any
> > > information
> > > > > > in
> > > > > > > advance.
> > > > > > >
> > > > > > > Eric
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > [Non-text portions of this message have been removed]
> > > > >
> > > >
> > >
> > >
> > >
> > >
> > >
> > > [Non-text portions of this message have been removed]
> > >
> >
> >
> >
> > ________________________________
> > The information contained in this message is intended solely for
> the individual to whom it is specifically and originally addressed.
> This message and its contents may contain confidential or privileged
> information. If you are not the intended recipient, you are hereby
> notified that any disclosure or distribution, or taking any action in
> reliance on the contents of this information, is strictly prohibited.
> > 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 cannot accept liability
> for any loss or damage caused by software viruses.
> >
> > This message (including any attachments) is intended only for
> > the use of the individual or entity to which it is addressed and
> > may contain information that is non-public, proprietary,
> > privileged, confidential, and exempt from disclosure under
> > applicable law or may constitute as attorney work product.
> > If you are not the intended recipient, you are hereby notified
> > that any use, dissemination, distribution, or copying of this
> > communication is strictly prohibited. If you have received this
> > communication in error, notify us immediately by telephone and
> > (i) destroy this message if a facsimile or (ii) delete this message
> > immediately if this is an electronic communication.
> >
> > Thank you.
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
> ________________________________
> The information contained in this message is intended solely for the individual to whom it is specifically and originally addressed. This message and its contents may contain confidential or privileged information. If you are not the intended recipient, you are hereby notified that any disclosure or distribution, or taking any action in reliance on the contents of this information, is strictly prohibited.
> 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 cannot accept liability for any loss or damage caused by software viruses.
>
> This message (including any attachments) is intended only for
> the use of the individual or entity to which it is addressed and
> may contain information that is non-public, proprietary,
> privileged, confidential, and exempt from disclosure under
> applicable law or may constitute as attorney work product.
> If you are not the intended recipient, you are hereby notified
> that any use, dissemination, distribution, or copying of this
> communication is strictly prohibited. If you have received this
> communication in error, notify us immediately by telephone and
> (i) destroy this message if a facsimile or (ii) delete this message
> immediately if this is an electronic communication.
>
> Thank you.
>
>
> [Non-text portions of this message have been removed]
>

Topic		Replies	Views
Lot Tracking Blank Title 57606 Yahoo Archive	9	522	June 26, 2007
Lot Tracking and Serial Number Tracking in Vantage 6.10 Yahoo Archive	6	1378	July 23, 2010
Lot Numbers in reported MES quantities for medical products Yahoo Archive	7	329	March 25, 2009
Part Tracking/Lot Tracking through Mfg Process in Vantage/Epicor 9.x Yahoo Archive	0	495	November 4, 2010
MES Lot # and SN reporting from MES v8.03.40x Yahoo Archive	4	524	March 31, 2009

Lot Tracking

Related Topics