There are some user fields in the item master (like ITEMASA)... how
about using those?
-Jimmy
-----Original Message-----
From: Peter Vidal [mailto:Peter_Vidal@xxxxxxxx]
Sent: Tuesday, July 31, 2007 7:19 AM
To: mapics-l@xxxxxxxxxxxx
Subject: [MAPICS-L] Kanban
Hi list,
I had brief discussion yesterday with a client regarding entering the
word "Kanban" in the "Vendor" field in some files so anyone looking up
the p/n can identify it as a kanban item. I helped them to understand
that this might not be the best place to identify this.
As they agreed with my detailed explanations about this, they pointed
out the need to determine which field(s) can be used to identify the
Kanban items while reviewing the p/n in the Item Requirements Inquiry
and other screens of this nature. There will not be room in the
description field for Kanban in all part numbers. They need some means
to do this. It would also be nice to have it print on requisitions.
This new Kanban procedure is being implemented now and being pushed by
upper management so this is a rush request. I know that this is an old
issue so I am sure you have an easy answer for this. We do not want to
buy new stuff (at least for the moment) so whatever recommendations
comes, have to be based on our current MAPICS setup.
In terms of planning, inv control modules and other related tools, we
currently have (R6):
a) Browser
b) MRP
c) IM
d) PCCC
e) PMC
f) PUR
g) CRP
h) COM
Your advices and comments on this matter are really appreciated.
Thanks in advance!
Peter Vidal
MAPICS IT Technical Support Team / SR System Analyst 10540 Ridge Rd.,
Ste 203, New Port Richey, FL 34654-5111
http://www.pall.com
"A good player makes himself look good; a great player makes the team
look
good."- Anonymous
------------------------------------------------------------------------
--------
Attention:
This communication may contain information that is confidential,
privileged and/or exempt from disclosure under applicable law.
If you are not the intended recipient, please notify the sender
immediately and delete the original, all attachments, and all copies of
this communication.
------------------------------------------------------------------------
--------
midrange.com
