RE: PM-Non-inventory items

["Kevin Fox" <kdfox@xxxxxxxxxxxxxx>]

Hi Mary,

This depends on the level of "control" and "ease of use" that your company
desires.

I prefer to setup an item called "supplies" or "office supplies" for each
dept (so the GL interface can departmentalized the expenses). Then, during
requisition creation the use enters in the description field exactly what
they want ordered.  In this way, the buyer has control and the database does
not need to be so explicite.

Again, depends upon the subjective requires above.

Kevin Fox
kdfox@xxxxxxxxxxxxx

-----Original Message-----
From: Kennedy, Mary (ALIE) [mailto:Mary.Kennedy@xxxxxxxxxxxxxxxxxxxx] 
Sent: Wednesday, June 16, 2004 6:38 AM
To: MAPICS-L@xxxxxxxxxxxx
Subject: PM-Non-inventory items 


We are in the process of implementing Procurement Management. How do
those of you who are using PM handle non-inventory items such as
paper,pens,chemicals and other supplies.
Do you have an Item master record for each of these items? If so, who
enters the item master record -the requisitioners,buyers?
We are concerned about loading the Item Master with garbage  and
duplications. For example-if we have requisitioner  in Eng ordering blue
pens- would she enter the item master record for pens-blue so she can
create a requisition? Then the next person comes along and doesn't check
if there are blue pens already in the Item master so they enter another
record such as Pen-BL . I can see this becoming a mess.

Thanks for any advise,
Mary Kennedy
Smiths ESLI



******************************************
The information contained in, or attached to, this e-mail, may contain
confidential information and is intended solely for the use of the
individual or entity to whom they are addressed and may be subject to legal
privilege.  If you have received this e-mail in error you should notify the
sender immediately by reply e-mail, delete the message from your system and
notify your system manager.  Please do not copy it for any purpose, or
disclose its contents to any other person.  The views or opinions presented
in this e-mail are solely those of the author and do not necessarily
represent those of the company.  The recipient should check this e-mail and
any attachments for the presence of viruses.  The company accepts no
liability for any damage caused, directly or indirectly, by any virus
transmitted in this email.
******************************************