× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Dear Bonnie:

As providers of MAPICS Manufacturing Execution Systems (Hardware, 
Software, Services), we have been asked this same question many times.  In 
the past it was handled with a special retro reflective label stock that 
can be read at distances of say 35 feet or more.  This is depends on the 
"x" dimension of the bar code itself and the laser scanners depth of 
field. 

I would suggest you contact Klaus Frost of our hardware solutions group @ 
262-567-9240 x 157.  Klaus has a wealth of knowledge in this area.  You 
might also want to contact your hardware manufacturer for more 
information. 

Best Regards,

Rick Schweitzer
Information Systems Engineering
Paper-Less, LLC
mailto:rick.schweitzer@xxxxxxxxxxx
www.gopaper-less.com
Business: 207-676-2118
Cell: 207-423-4860





mapics-l-request@xxxxxxxxxxxx
Sent by: mapics-l-bounces@xxxxxxxxxxxx
11/17/2003 10:38 PM
Please respond to mapics-l

 
        To:     mapics-l@xxxxxxxxxxxx
        cc: 
        Subject:        MAPICS-L Digest, Vol 1, Issue 822


Send MAPICS-L mailing list submissions to
                 mapics-l@xxxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
                 http://lists.midrange.com/mailman/listinfo/mapics-l
or, via email, send a message with subject or body 'help' to
                 mapics-l-request@xxxxxxxxxxxx

You can reach the person managing the list at
                 mapics-l-owner@xxxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of MAPICS-L digest..."


Today's Topics:

   1. RE: Shortage / Due Reporting (Greg Novak, Momentum)
   2. Re: Shortage / Due Reporting (Mike Crawford)
   3. RE: Shortage / Due Reporting (David Kemp)
   4. Barcoding Warehouse Racks (Bonnie_Lokenvitz@xxxxxxxxxxxxxx)
   5. RE: Barcoding Warehouse Racks (Konrad Underkofler)
   6. Re: Barcoding Warehouse Racks (Michael.Huber@xxxxxxxxxxxxxxxxx)
   7. Re: Barcoding Warehouse Racks (DaleGindlesperger@xxxxxxxxxxx)
   8. Prox Terms (Marc.Rohde@xxxxxxxxxxxxxxxxx)
   9. RE: Prox Terms (Michael Franchino)


----------------------------------------------------------------------

message: 1
date: Mon, 17 Nov 2003 12:39:26 -0600
from: "Greg Novak, Momentum" <gnovak@xxxxxxxxxx>
subject: RE: Shortage / Due Reporting

Chuck,

Using Jacana/Valet for reporting permits connecting/accessing any data on
your AS/400.  You will probably need to create a subset that links from 
your
manufacturing order components to the purchase orders for the items.  This
is usually a simple procedure where you define the how the files are 
linked
to provide the information you want.

If you are interested, please contact me off list with the details of your
existing shortage reports and how you want the purchase orders included.
>From there we should be able to define your requirements and produce the
report you need.

Regards,
-Greg

Momentum is the developer of Info/WorkPlace (IWP), Jacana and Valet.

Gregory Novak
Manager North American Technical Services
Momentum Utilities Pty Ltd
(630) 985-1736
gnovak@xxxxxxxxxx
www.jacana.com
 
Making Information Work for your Business
www.intuator.com


-----Original Message-----
From: Chuck Kearney [mailto:ckearney@xxxxxxxxxxxxxxxxxx] 
Sent: Monday, November 17, 2003 7:57 AM
To: mapics-l@xxxxxxxxxxxx
Subject: Shortage / Due Reporting


To all, 

I'm looking to create a single report that will combine manufacturing 
order
shortage information with purchasing information.

We currently accomplish this manually using Microsoft Word. It's a good
report but with many issues such as time, accuracy, and timeliness.

All information used to create this report comes from Mapics. So why not 
let
the system do all of the work, right?

The "Manufacture Order Shortage Report --- Follow-Up Analysis ---" is used
to show what each manufacturing order is short. We use the purchase orders
to know when items are due.

Any ideas on how to accomplish this? We use Jacana/Valet for report 
writing.


Thank you, 

Chuck Kearney
Production Planner
Hydro Systems Company
Phone (513) 271-8800
Direct line (513) 842-2511






------------------------------

message: 2
date: Mon, 17 Nov 2003 14:17:04 -0500
from: Mike Crawford <mikec@xxxxxxxxxxxxxxxxxx>
subject: Re: Shortage / Due Reporting

Chuck,

I have a couple of questions:

1. what version of mapics are you on?
2. are you running the browser and integrator?
3. do you have operations navigator installed on one of your PCs?
4. how are you matching your MO records to you PO information?

My solution to you would involve creating an SQL view through Ops 
Navigator,
then add that view to the browser (through the integrator) and make it 
available
to your users.  I've used IWP for report generation, but once we moved to 
V5R1,
I switched almost all reporting to browser views.  Nice thing is, the data 
is
always live and it reduces a lot of paper pushing around the office.

Mike


Michael Crawford <mikec@xxxxxxxxxxxxxxxxxx>
Director of Information Systems
United Titanium, Inc.   330-264-2111




At 11/17/2003  08:57 AM, you wrote:
>To all,
>
>I'm looking to create a single report that will combine manufacturing 
order
>shortage information with purchasing information.
>
>We currently accomplish this manually using Microsoft Word. It's a good
>report but with many issues such as time, accuracy, and timeliness.
>
>All information used to create this report comes from Mapics. So why not 
let
>the system do all of the work, right?
>
>The "Manufacture Order Shortage Report --- Follow-Up Analysis ---" is 
used
>to show what each manufacturing order is short. We use the purchase 
orders
>to know when items are due.
>
>Any ideas on how to accomplish this? We use Jacana/Valet for report 
writing.
>
>
>Thank you,
>
>Chuck Kearney
>Production Planner
>Hydro Systems Company
>Phone (513) 271-8800
>Direct line (513) 842-2511
>
>_______________________________________________
>This is the MAPICS ERP System Discussion (MAPICS-L) mailing list
>To post a message email: MAPICS-L@xxxxxxxxxxxx
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/mailman/listinfo/mapics-l
>or email: MAPICS-L-request@xxxxxxxxxxxx
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/mapics-l.




------------------------------

message: 3
date: Mon, 17 Nov 2003 14:09:39 -0600
from: "David Kemp" <dkemp@xxxxxxxxxx>
subject: RE: Shortage / Due Reporting

Chuck,

We have done exactly what you are looking for with Jacana.  We took the
approach of creating some database files of our own and then building a
customized subset.  The database files can be built using Jacana and the
subset can be created using IWP.  The reason we built our own database
files and subset was to make the linking in the subset much less
complicated.  We linked a CL to a task that runs all of the reports to
build the database files and then runs the report to produce the printed
output.  This makes running the report very easy for the user.  We also
use Jacana to download this same information to Excel.

The report gives all the items that are short with all manufacturing
orders that require the item, all purchase orders for the item with
appropriate due dates, and all inventory currently on hand.  This is all
pulled live from the MAPICS files so the report is literally up to the
minute.

David Kemp 


-----Original Message-----
From: Chuck Kearney [mailto:ckearney@xxxxxxxxxxxxxxxxxx] 
Sent: Monday, November 17, 2003 7:57 AM
To: mapics-l@xxxxxxxxxxxx
Subject: Shortage / Due Reporting

To all, 

I'm looking to create a single report that will combine manufacturing
order
shortage information with purchasing information.

We currently accomplish this manually using Microsoft Word. It's a good
report but with many issues such as time, accuracy, and timeliness.

All information used to create this report comes from Mapics. So why not
let
the system do all of the work, right?

The "Manufacture Order Shortage Report --- Follow-Up Analysis ---" is
used
to show what each manufacturing order is short. We use the purchase
orders
to know when items are due.

Any ideas on how to accomplish this? We use Jacana/Valet for report
writing.


Thank you, 

Chuck Kearney
Production Planner
Hydro Systems Company
Phone (513) 271-8800
Direct line (513) 842-2511

_______________________________________________
This is the MAPICS ERP System Discussion (MAPICS-L) mailing list
To post a message email: MAPICS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/mapics-l
or email: MAPICS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/mapics-l.




------------------------------

message: 4
date: Mon, 17 Nov 2003 14:59:54 -0600
from: Bonnie_Lokenvitz@xxxxxxxxxxxxxx
subject: Barcoding Warehouse Racks



In anticipation of our new bar coding applications, we need to re-barcode
our racks.
Our current applications are used by warehouse handlers who use highlifts
and they
are at rack level when they scan.

In the future some of the users will be on traditional forklifts at floor
level.
Our problem are the racks at the 15 foot+ level.

How do others handle the physical labeling of racks?  Do your scanners
reach that distance?

Thanks,
Bonnie Lokenvitz
Engineered Polymers




------------------------------

message: 5
date: Mon, 17 Nov 2003 16:34:09 -0500
from: "Konrad Underkofler" <kdunderk@xxxxxxxxxxxxx>
subject: RE: Barcoding Warehouse Racks

Bonnie,

You need special long range scanners and the labels have to be special
reflective ones to get it to work correctly. A cheaper solution is to
also use a smaller barcode down on the lower racks to mimic what is
stored above so you can do a local short range scan. 

Regards

Konrad

-----Original Message-----
From: Bonnie_Lokenvitz@xxxxxxxxxxxxxx
[mailto:Bonnie_Lokenvitz@xxxxxxxxxxxxxx] 
Sent: Monday, November 17, 2003 4:00 PM
To: MAPICS ERP System Discussion
Subject: Barcoding Warehouse Racks




In anticipation of our new bar coding applications, we need to
re-barcode our racks. Our current applications are used by warehouse
handlers who use highlifts and they are at rack level when they scan.

In the future some of the users will be on traditional forklifts at
floor level. Our problem are the racks at the 15 foot+ level.

How do others handle the physical labeling of racks?  Do your scanners
reach that distance?

Thanks,
Bonnie Lokenvitz
Engineered Polymers


_______________________________________________
This is the MAPICS ERP System Discussion (MAPICS-L) mailing list To post
a message email: MAPICS-L@xxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit: http://lists.midrange.com/mailman/listinfo/mapics-l
or email: MAPICS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/mapics-l.




------------------------------

message: 6
date: Mon, 17 Nov 2003 16:13:32 -0600
from: Michael.Huber@xxxxxxxxxxxxxxxxx
subject: Re: Barcoding Warehouse Racks

We use legend labels on the rack uprights


----- AA3 ----| | ---- BB3 -----
----- AA2 ----| | ---- BB2 -----
----- AA1 ----| | ---- BB1 -----
                                       ^
                                        |_  A label is placed on the rack 
upright place around 5ft of the ground contains all the "level" barcodes 
and an arrow to specify which side it is on. Also the cross beams are 
barcoded.

This allows for scanning at walking height, or also at hi-lift height.

If you want a gun that can do long distances, check out the Symbol 
Powerscan XLR, but be aware they can be a bit funky.


Hope that helps.

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Michael K. Huber
Applications Development & AS/400 Operations
Pentair/Plymouth Products, Inc
502 Indiana Ave - Sheboygan, WI 53081
Phone: (920) 451-9417      FAX: (920) 803-3541     Cellular: (920) 
698-0013 Mobile Messaging: 9206980013@xxxxxxxxxxxxxx
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Confidentiality Note:   This e-mail message and any attachments to it are 
intended only for the named recipients and may contain confidential 
information.  If you are not one of the intended recipients, please do not 

duplicate or forward this e-mail message and immediately delete it from 
your computer.



Bonnie_Lokenvitz@xxxxxxxxxxxxxx 
Sent by: mapics-l-bounces@xxxxxxxxxxxx
11/17/2003 02:59 PM
Please respond to
MAPICS ERP System Discussion <mapics-l@xxxxxxxxxxxx>


To
MAPICS ERP System Discussion <mapics-l@xxxxxxxxxxxx>
cc

Subject
Barcoding Warehouse Racks








In anticipation of our new bar coding applications, we need to re-barcode
our racks.
Our current applications are used by warehouse handlers who use highlifts
and they
are at rack level when they scan.

In the future some of the users will be on traditional forklifts at floor
level.
Our problem are the racks at the 15 foot+ level.

How do others handle the physical labeling of racks?  Do your scanners
reach that distance?

Thanks,
Bonnie Lokenvitz
Engineered Polymers


_______________________________________________
This is the MAPICS ERP System Discussion (MAPICS-L) mailing list
To post a message email: MAPICS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/mapics-l
or email: MAPICS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/mapics-l.




------------------------------

message: 7
date: Mon, 17 Nov 2003 18:37:39 -0500
from: DaleGindlesperger@xxxxxxxxxxx
subject: Re: Barcoding Warehouse Racks


Bonnie,

We found the longer range scanners to be too picky.  What we did was
implement a process of item consolidation (try and locate items in a 
single
location as much as possible), and enhanced the data collection program to
preload the location where the item was found.  In the event where it was
being picked from an alternate location, they hit a function key, and all
the locations where the item is located is shown, then the user just
selects the correct item.

FYI, for RM transactions, we preload the location that was last used for a
pick or shipment, on the assumption that we are restocking.  It's correct
the majority of the time.  If not, the user marks where they put it and
keys it in the location field.

Small program, minor change.  Since the data writes to TRDATA (which 
hasn't
changed since we've been using it), it's been no problem for us.

Dale Gindlesperger
IT Manager/Special Projects Leader
Fleetwood Folding Trailers, Inc.
Somerset, PA



  
                      Bonnie_Lokenvitz@epc   
                      molding.com                 To:       MAPICS ERP 
System Discussion <mapics-l@xxxxxxxxxxxx> 
                      Sent by:                    cc:     
                      mapics-l-bounces@mid        Subject:  Barcoding 
Warehouse Racks 
                      range.com   
  
  
                      11/17/2003 03:59 PM   
                      Please respond to   
                      MAPICS ERP System   
                      Discussion   
  
  






In anticipation of our new bar coding applications, we need to re-barcode
our racks.
Our current applications are used by warehouse handlers who use highlifts
and they
are at rack level when they scan.

In the future some of the users will be on traditional forklifts at floor
level.
Our problem are the racks at the 15 foot+ level.

How do others handle the physical labeling of racks?  Do your scanners
reach that distance?

Thanks,
Bonnie Lokenvitz
Engineered Polymers


_______________________________________________
This is the MAPICS ERP System Discussion (MAPICS-L) mailing list
To post a message email: MAPICS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/mapics-l
or email: MAPICS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/mapics-l.








------------------------------

message: 8
date: Mon, 17 Nov 2003 16:01:16 -0600
from: Marc.Rohde@xxxxxxxxxxxxxxxxx
subject: Prox Terms

I am having problems getting Prox terms entered into Mapics to provide 
accurate due dates.  I am trying to enter "2% 10th Prox" which means that 
the invoice will be due on the 10th of the next month until the cut off of 

the month, which is the 25th.

This means if I invoice on 11/11/2003 the payment is due 12/10/2003.
If I invoice 11/26/2003 (after the 25th cut-off) the payment would be due 
1/10/2004
and invoices up to 12/25/2003 should be due 1/10/2004

I have spoken with Mapics and went round-and-round on this so I am 
throwing this issue out to the list for help.

At this point I have the terms set to:

Day Due:  10
Month End Cutoff: 25
Net Due: 25

I have "messed with" the net due to make the calculation work but cannot 
get this thing to calculate properly.

Your help is appreciated,
Marc Rohde
IT Manager
Pentair Water Treatment\Plymouth Products, Inc.
Work: 920-451-9421
Cell: 920-698-2008
Fax: 920-803-3540

------------------------------

message: 9
date: Mon, 17 Nov 2003 22:46:17 -0500
from: "Michael Franchino" <Michael.Franchino@xxxxxxxxxx>
subject: RE: Prox Terms

Marc,
 
What results are you getting.. The documentation states that what you did 
should provide the results that you are looking for.. What exactly is 
MAPICS returning as a date?
 
 

                 -----Original Message----- 
                 From: mapics-l-bounces@xxxxxxxxxxxx on behalf of 
Marc.Rohde@xxxxxxxxxxxxxxxxx 
                 Sent: Mon 11/17/2003 5:01 PM 
                 To: mapics-l@xxxxxxxxxxxx 
                 Cc: 
                 Subject: Prox Terms
 
 

                 I am having problems getting Prox terms entered into 
Mapics to provide 
                 accurate due dates.  I am trying to enter "2% 10th Prox" 
which means that 
                 the invoice will be due on the 10th of the next month 
until the cut off of 
                 the month, which is the 25th. 

                 This means if I invoice on 11/11/2003 the payment is due 
12/10/2003. 
                 If I invoice 11/26/2003 (after the 25th cut-off) the 
payment would be due 
                 1/10/2004 
                 and invoices up to 12/25/2003 should be due 1/10/2004 

                 I have spoken with Mapics and went round-and-round on 
this so I am 
                 throwing this issue out to the list for help. 

                 At this point I have the terms set to: 

                 Day Due:  10 
                 Month End Cutoff: 25 
                 Net Due: 25 

                 I have "messed with" the net due to make the calculation 
work but cannot 
                 get this thing to calculate properly. 

                 Your help is appreciated, 
                 Marc Rohde 
                 IT Manager 
                 Pentair Water Treatment\Plymouth Products, Inc. 
                 Work: 920-451-9421 
                 Cell: 920-698-2008 
                 Fax: 920-803-3540 
                 _______________________________________________ 
                 This is the MAPICS ERP System Discussion (MAPICS-L) 
mailing list 
                 To post a message email: MAPICS-L@xxxxxxxxxxxx 
                 To subscribe, unsubscribe, or change list options, 
                 visit: http://lists.midrange.com/mailman/listinfo/mapics-l 
                 or email: MAPICS-L-request@xxxxxxxxxxxx 
                 Before posting, please take a moment to review the 
archives 
                 at http://archive.midrange.com/mapics-l. 


------------------------------

_______________________________________________
This is the MAPICS ERP System Discussion (MAPICS-L) digest list
To post a message email: MAPICS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/mapics-l
or email: MAPICS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/mapics-l.



End of MAPICS-L Digest, Vol 1, Issue 822
****************************************





As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.