|
midrange.com
Hi:
We're on BPCS 6101 BB Dic 2000 C/S and we have just gone live with QMS (not
LMS).
QMS is very stable (we haven't had any errors until now). Prior to the
launch, we updated the available BMRS for a couple of issues. We're not
using BPCS result entry because it's too slow for us and we developed a
additional module to update
the information in qre. All the rest, is done using std QMS.
We have discovered a couple of issues that we didn't predict such as the
use of "U" & "R" transacciones with negative values. They change the lot
status to "Q" independent of the previous status (because in the effect
maintenance they have the trigger QA setting. We're analyzing whether to
create a Q'/R' without the trigger QA setting for negative or add the task
of changing
the lot status back to the original status (we have an update trigger on
iln inserting into a special audit table when
the lot, expiration and/or retest fields are changed).
Hope this helps.
Regards,
Pablo Lewin, CPIM
Project Manager
Gerencia de Proyectos y Sistemas
Laboratorio Chile S.A.
Avenida Maraton 1315, Santiago, Chile
Tel: (562) 3655240
Fax: (562) 3655052
email: pablo.lewin@labchile.cl
--------------------------------------------------------------------------------------------------------------------------------------------------------
CONFIDENTIALITY NOTE/NOTA DE CONFIDENCIALIDAD
This message and attachments may be confidential communication. It may also
contain information that is priviledge or otherwise legally exempt from
disclosure. If you have received it by mistake please let us know by e-mail
immediately and delete it from your system; you should also not copy the
message nor disclose its contents to anyone. Thank you.
Este mensaje y adjuntos pueden ser confidenciales. Tambien puede contener
informacion amparada por el secreto profesional. Si usted ha recibido este
e-mail por error, por favor comuniquelo inmediatamente via e-mail y tenga
la amabilidad de destruirlo; no debera copiar el mensaje ni divulgar su
contenido a ninguna persona. Muchas gracias.
--------------------------------------------------------------------------------------------------------------------------------------------------------
----- Remitido por pablo lewin/ICL/IVAX con fecha 06/01/2003 12:12 PM -----
Fran Clements
<ClementF@cbfleet Para: "'SSA's BPCS ERP
System'" <bpcs-l@midrange.com>
.com> cc:
Enviado por: Asunto: RE: BPCS-L digest, Vol
1 #501 - 5 msgs
bpcs-l-bounces@mi
drange.com
06/01/2003 10:30
AM
Por favor,
responda a "SSA's
BPCS ERP System"
RE MESSAGE 5, WE ARE ALSO ON 6.1.01 AND WE ALSO USE QMS TO RELEASE LOT
CONTROLLED ITEMS AND TO MANAGE EXPIRATION/RETEST DATING.
WE DO NOT PRESENTLY USE LMS. HAVE DISCUSSED FROM TIME TO TIME. WOULD ALSO
BE INTERESTED IN ADVICE/COMMENTS CONCERNING LMS.
-----Original Message-----
From: Mehmood Merchant (Merck) [mailto:mmerchant@merck.com.pk]
Sent: Sunday, January 05, 2003 3:30 PM
To: bpcs-l@midrange.com
Subject: Fw: BPCS-L digest, Vol 1 #501 - 5 msgs
> Anyone can provide details of BPCS QMS/LMS modules. Has anyone any
experience with
> these modules? Advice?
>
> Mehmood Merchant
>
> ----- Original Message -----
> From: <bpcs-l-request@midrange.com>
> To: <bpcs-l@midrange.com>
> Sent: Friday, January 03, 2003 11:00 PM
> Subject: BPCS-L digest, Vol 1 #501 - 5 msgs
>
>
> > Send BPCS-L mailing list submissions to
> > bpcs-l@midrange.com
> >
> > To subscribe or unsubscribe via the World Wide Web, visit
> > http://lists.midrange.com/cgi-bin/listinfo/bpcs-l
> > or, via email, send a message with subject or body 'help' to
> > bpcs-l-request@midrange.com
> >
> > You can reach the person managing the list at
> > bpcs-l-admin@midrange.com
> >
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of BPCS-L digest..."
> >
> >
> > Today's Topics:
> >
> > 1. Re: MRP Questions (Mhamilton8685@aol.com)
> > 2. AR Statement Issue (Tom Jedrzejewicz @ San Pedro)
> > 3. RE: AR Statement Issue (DeeDee Virgei)
> > 4. Re: AR Statement Issue (Bill)
> > 5. QMS/LMS (Vince Rowe)
> >
> > --__--__--
> >
> > Message: 1
> > From: Mhamilton8685@aol.com
> > Date: Thu, 2 Jan 2003 14:25:51 EST
> > Subject: Re: MRP Questions
> > To: bpcs-l@midrange.com
> > Reply-To: bpcs-l@midrange.com
> >
> > Paul,
> >
> > I don't disagree with your findings.
> >
> > Myron
> >
> > --__--__--
> >
> > Message: 2
> > Date: Thu, 02 Jan 2003 14:01:56 -0800
> > From: "Tom Jedrzejewicz @ San Pedro" <TJedrzejewicz@contessa.com>
> > To: <bpcs-l@midrange.com>
> > Subject: AR Statement Issue
> > Reply-To: bpcs-l@midrange.com
> >
> > Folks - got a strange issue here.
> >
> > A customer took a deduction on a payment on 2-Dec, and A/R entered a
> > Debit Memo to account for the difference. This is standard procedure.
> > After the deduction was checked to be correct, a Credit Memo was
entered
> > on 26-Dec and properly offset the Debit Memo.
> >
> > However, when the AR close was run, the original Debit was soft-deleted
> > (status to ZD), and the associated Credit was left active (status =3D
> > 'RC'). So now the credit shows on the statement, and the statement
> > (ACR410) doesn't balance to A/R.
> >
> > Any help would be appreciated . . . we are on v4.0.03.
> >
> > Thanks!
> > Tom Jedrzejewicz, Contessa Food Products
> > THIS MESSAGE IS INTENDED ONLY FOR THE USE OF THE INDIVIDUAL OR ENTITY
TO
> WH=
> > ICH IT IS ADDRESSED AND MAY CONTAIN INFORMATION THAT IS PRIVILEGED,
> CONFIDE=
> > NTIAL AND EXEMPT FROM DISCLOSURE UNDER APPLICABLE LAW. If the reader
of
> th=
> > is message is not the intended recipient, or the employee or agent
> responsi=
> > ble for delivering the message to the intended recipient, you are
hereby
> no=
> > tified that any dissemination, distribution, copying, downloading,
storing
> =
> > or forwarding of this communication is prohibited. If you have
received
> th=
> > is communication in error, please notify us immediately via email and
> delet=
> > e the message from your computer files and/or data base. Thank you.
> >
> > --__--__--
> >
> > Message: 3
> > From: DeeDee Virgei <DeeDee.Virgei@nelsonstud.com>
> > To: "'bpcs-l@midrange.com'" <bpcs-l@midrange.com>
> > Subject: RE: AR Statement Issue
> > Date: Thu, 2 Jan 2003 17:11:06 -0500
> > Reply-To: bpcs-l@midrange.com
> >
> > Hi Tom,
> >
> > We have something similar happen when we accidentally combine customers
w/
> > different currency codes in a billing batch... I'd check the RCURR
> > (Currency Code) and the RCOMP (Company Number) on the RAR file on both
> > records. Also, we've had similar problems w/ corporate accounts, where
we
> > debited the child account and credited the corporate account (or visa
> > versa). Hope this helps.
> >
> > DeeDee Virgei
> >
> > -----Original Message-----
> > From: Tom Jedrzejewicz @ San Pedro [mailto:TJedrzejewicz@contessa.com]
> > Sent: Thursday, January 02, 2003 5:02 PM
> > To: bpcs-l@midrange.com
> > Subject: AR Statement Issue
> >
> >
> > Folks - got a strange issue here.
> >
> > A customer took a deduction on a payment on 2-Dec, and A/R entered a
> > Debit Memo to account for the difference. This is standard procedure.
> > After the deduction was checked to be correct, a Credit Memo was
entered
> > on 26-Dec and properly offset the Debit Memo.
> >
> > However, when the AR close was run, the original Debit was soft-deleted
> > (status to ZD), and the associated Credit was left active (status =
> > 'RC'). So now the credit shows on the statement, and the statement
> > (ACR410) doesn't balance to A/R.
> >
> > Any help would be appreciated . . . we are on v4.0.03.
> >
> > Thanks!
> > Tom Jedrzejewicz, Contessa Food Products
> > THIS MESSAGE IS INTENDED ONLY FOR THE USE OF THE INDIVIDUAL OR ENTITY
TO
> > WHICH IT IS ADDRESSED AND MAY CONTAIN INFORMATION THAT IS PRIVILEGED,
> > CONFIDENTIAL AND EXEMPT FROM DISCLOSURE UNDER APPLICABLE LAW. If the
> reader
> > of this message is not the intended recipient, or the employee or agent
> > responsible for delivering the message to the intended recipient, you
are
> > hereby notified that any dissemination, distribution, copying,
> downloading,
> > storing or forwarding of this communication is prohibited. If you have
> > received this communication in error, please notify us immediately via
> email
> > and delete the message from your computer files and/or data base.
Thank
> > you.
> > _______________________________________________
> > This is the SSA's BPCS ERP System (BPCS-L) mailing list
> > To post a message email: BPCS-L@midrange.com
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/cgi-bin/listinfo/bpcs-l
> > or email: BPCS-L-request@midrange.com
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/bpcs-l.
> >
> > --__--__--
> >
> > Message: 4
> > From: "Bill" <billzbubb@subdimension.com>
> > To: <bpcs-l@midrange.com>
> > Subject: Re: AR Statement Issue
> > Date: Thu, 2 Jan 2003 14:21:28 -0800
> > Reply-To: bpcs-l@midrange.com
> >
> > Tom Jedrzejewicz @ San Pedro wrote:
> > > A customer took a deduction on a payment on 2-Dec, and A/R entered a
> > > Debit Memo to account for the difference. This is standard
procedure.
> > > After the deduction was checked to be correct, a Credit Memo was
> > > entered
> > > on 26-Dec and properly offset the Debit Memo.
> > >
> > > However, when the AR close was run, the original Debit was
> > > soft-deleted
> > > (status to ZD), and the associated Credit was left active (status =
> > > 'RC'). So now the credit shows on the statement, and the statement
> > > (ACR410) doesn't balance to A/R.
> >
> > Tom,
> >
> > In cases like this, I always want to look at the raw file data to see
if
> it
> > might shed light on what might be happening. Easiest way would be to
run
> > RunQry *None QryFile((RAR)) . What's the remaining due amount on the
zero
> > sequence records?
> >
> > Bill
> >
> >
> > --__--__--
> >
> > Message: 5
> > From: Vince Rowe <vrowe@mariettacorp.com>
> > To: bpcs-l@midrange.com
> > Subject: QMS/LMS
> > Date: Fri, 3 Jan 2003 09:24:35 -0500
> > Reply-To: bpcs-l@midrange.com
> >
> > We are currently using portions of QMS to manage release status of
Quality
> > Controlled items and want to implement LMS to track lab testing. We
are
> on
> > 6.1.01 MM . Has anyone any experience with this? Pitfalls? Advice?
> >
> > Thanks,
> >
> > Vince Rowe
> > MIS
> > Marietta Corp.
> > vrowe@mariettacorp.com
> >
> >
> > --__--__--
> >
> > _______________________________________________
> > This is the SSA's BPCS ERP System (BPCS-L) digest list
> > To post a message email: BPCS-L@midrange.com
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/cgi-bin/listinfo/bpcs-l
> > or email: BPCS-L-request@midrange.com
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/bpcs-l.
> >
> >
> >
> > End of BPCS-L Digest
> >
>
_______________________________________________
This is the SSA's BPCS ERP System (BPCS-L) mailing list
To post a message email: BPCS-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo.cgi/bpcs-l
or email: BPCS-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/bpcs-l.
_______________________________________________
This is the SSA's BPCS ERP System (BPCS-L) mailing list
To post a message email: BPCS-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo.cgi/bpcs-l
or email: BPCS-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/bpcs-l.
As an Amazon Associate we earn from qualifying purchases.
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.
