We are having a problem with the PM creation of a purchase order.
Our company requires all requisitions which are being turned into a PO
MUST be a separate release. We use job numbers which are kept in a user
field within the item release record.

When 2 or more requisitions have the same Item number and Due to Stock
date and you create a blanket per requisitions, it combines the
quantities and makes it one release- we then lose the individuality of
the job numbers which can be different for each release due to stock on
the same day.

We would like to know if there is a way to change a program ,option or
client setting so that this doesn't happen. This is a really big problem
for us to go forward with our PM implementation so any help would really
be appreciated.

Thanks
Mary Kennedy
Wayne Baldwin





******************************************
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.
******************************************


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-2021 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.