Issue Material Tags

Thanks for the info but I see this as a pretty extreme workaround
and I don't always want to print the tag. If others out there have
similar issues, I have created an enhancement request 12566MPS for a
method to print issued material tags from the Issue Material
interface. It seems to me that this should be a standard function??

Rich J @ ERMC
--- In vantage@yahoogroups.com, "Aaron Hoyt" <aaron.hoyt@...> wrote:
>
> For speed, I can't tell you, only because I have not tried to
compile a
> crystal report and distribute it for this purpose. We are
printing this
> using Data collection licenses and use as a trigger the
JobMtl.IssuedQty
> field. I first verify it's more than 0 (eliminate record
creations) and
> then compare it to the old issued quantity. If it's greater, it's
an issued
> quantity label and I process the logic for having issued material
to the
> job, if it's less I process the logic for return quantity and
print labels
> for return to stock. We do barcode the return labels (only the
part number
> and quantity for ease of inventory at month end), but most the
labels we
> print do not include barcodes at this time. Most of the labels
are to
> comply with our ISO system and it's identification requirements.
> The whole process of reporting an issue of material and waiting
for the
> label to print take about 15 to 20 seconds by estimation. Of
that, maybe 5
> to 7 seconds is waiting for the Wasp software to load and start
printing the
> label. This is just estimation, but it's been a long time since
we have had
> any credible complaints about the speed of the labels.
> Aaron Hoyt
> Vantage Plastics
> -----Original Message-----
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]On
Behalf Of
> ermc_v
> Sent: Monday, October 09, 2006 10:28 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: Issue Material Tags
>
>
> Thanks for the response. I would like to understand how your BAM
is
> set up, or what you are using as a trigger to generate the report
> info. I see Wasp is primarily a barcode software. We are
currently
> not applying bar codes to our inventory. Do you find this to
print
> faster than generating a Crystal report?
>
> Rich J
>
> --- In vantage@yahoogroups.com, "Aaron Hoyt" <aaron.hoyt@> wrote:
> >
> > Rich,
> > We do it via a BAM using Wasp Labeler. I can share the details
if
> you wish.
> > We print issued labels, return labels, report quantity labels,
end
> activity
> > labels, end setup labels, receive from Mfg labels, receive to
> inventory from
> > Purchase labels...All based on BAMs using Wasp Labeler
(because it
> was cheap
> > and command line accessible).
> > Aaron Hoyt
> > Vantage Plastics
> > -----Original Message-----
> > From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
On
> Behalf Of
> > ermc_v
> > Sent: Monday, October 09, 2006 9:51 AM
> > To: vantage@yahoogroups.com
> > Subject: [Vantage] Issue Material Tags
> >
> >
> > Has anyone found a way to print material tags when issuing
> material
> > from inventory? The Issue Material screen data is a temp table
> that
> > can't be accessed via Crystal.
> >
> > Rich J
> > ERMC
> >
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
Has anyone found a way to print material tags when issuing material
from inventory? The Issue Material screen data is a temp table that
can't be accessed via Crystal.

Rich J
ERMC
Rich,
We do it via a BAM using Wasp Labeler. I can share the details if you wish.
We print issued labels, return labels, report quantity labels, end activity
labels, end setup labels, receive from Mfg labels, receive to inventory from
Purchase labels...All based on BAMs using Wasp Labeler (because it was cheap
and command line accessible).
Aaron Hoyt
Vantage Plastics
-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]On Behalf Of
ermc_v
Sent: Monday, October 09, 2006 9:51 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Issue Material Tags


Has anyone found a way to print material tags when issuing material
from inventory? The Issue Material screen data is a temp table that
can't be accessed via Crystal.

Rich J
ERMC






[Non-text portions of this message have been removed]
Thanks for the response. I would like to understand how your BAM is
set up, or what you are using as a trigger to generate the report
info. I see Wasp is primarily a barcode software. We are currently
not applying bar codes to our inventory. Do you find this to print
faster than generating a Crystal report?

Rich J

--- In vantage@yahoogroups.com, "Aaron Hoyt" <aaron.hoyt@...> wrote:
>
> Rich,
> We do it via a BAM using Wasp Labeler. I can share the details if
you wish.
> We print issued labels, return labels, report quantity labels, end
activity
> labels, end setup labels, receive from Mfg labels, receive to
inventory from
> Purchase labels...All based on BAMs using Wasp Labeler (because it
was cheap
> and command line accessible).
> Aaron Hoyt
> Vantage Plastics
> -----Original Message-----
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]On
Behalf Of
> ermc_v
> Sent: Monday, October 09, 2006 9:51 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Issue Material Tags
>
>
> Has anyone found a way to print material tags when issuing
material
> from inventory? The Issue Material screen data is a temp table
that
> can't be accessed via Crystal.
>
> Rich J
> ERMC
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
For speed, I can't tell you, only because I have not tried to compile a
crystal report and distribute it for this purpose. We are printing this
using Data collection licenses and use as a trigger the JobMtl.IssuedQty
field. I first verify it's more than 0 (eliminate record creations) and
then compare it to the old issued quantity. If it's greater, it's an issued
quantity label and I process the logic for having issued material to the
job, if it's less I process the logic for return quantity and print labels
for return to stock. We do barcode the return labels (only the part number
and quantity for ease of inventory at month end), but most the labels we
print do not include barcodes at this time. Most of the labels are to
comply with our ISO system and it's identification requirements.
The whole process of reporting an issue of material and waiting for the
label to print take about 15 to 20 seconds by estimation. Of that, maybe 5
to 7 seconds is waiting for the Wasp software to load and start printing the
label. This is just estimation, but it's been a long time since we have had
any credible complaints about the speed of the labels.
Aaron Hoyt
Vantage Plastics
-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]On Behalf Of
ermc_v
Sent: Monday, October 09, 2006 10:28 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Issue Material Tags


Thanks for the response. I would like to understand how your BAM is
set up, or what you are using as a trigger to generate the report
info. I see Wasp is primarily a barcode software. We are currently
not applying bar codes to our inventory. Do you find this to print
faster than generating a Crystal report?

Rich J

--- In vantage@yahoogroups.com, "Aaron Hoyt" <aaron.hoyt@...> wrote:
>
> Rich,
> We do it via a BAM using Wasp Labeler. I can share the details if
you wish.
> We print issued labels, return labels, report quantity labels, end
activity
> labels, end setup labels, receive from Mfg labels, receive to
inventory from
> Purchase labels...All based on BAMs using Wasp Labeler (because it
was cheap
> and command line accessible).
> Aaron Hoyt
> Vantage Plastics
> -----Original Message-----
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]On
Behalf Of
> ermc_v
> Sent: Monday, October 09, 2006 9:51 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Issue Material Tags
>
>
> Has anyone found a way to print material tags when issuing
material
> from inventory? The Issue Material screen data is a temp table
that
> can't be accessed via Crystal.
>
> Rich J
> ERMC
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>






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