|
Invoice Voiding Action on-hold until "so & so" (some other employee name or job title) approves this action ... please wait ... phone extension # for that person might be wise to include at this point, since they might have to wait a long time. You may need to have some mechanism for safely bringing that program to a conclusion without bombing it if that person is currently on a business trip, on vacation, off sicek etc.
There may be a need to have a banner warning at beginning of doing any software that can void invoices ... WHO has to approve this, and if they are not currently around, so any voiding needs to be postponed until their return.
Consider a modification.The people who today have BPCS security access into the BPCS software that can void invoices ... when they take the voiding action, what would really happen, in the modification is that the invoice would become "coded for" void requested. Then a DIFFERENT person would have security access to the void approval program. They would see a list of invoices waiting for approval to void & they could take one of 3 actions.
YES ... the voiding is approved NO ... reverse the invoice to the old status WAIT ... no action yet, while we look into thisneed to add fields ... WHO requested the VOID status & space for some comment or reason field.
You may not have this in your environment, but in ours, we also go outside of BPCS to actually delete or change invoices. There is a process that is followed involving manual controls. I am not happy with that system, because if a question comes up later, we don't know WHEN the deletion occurred. The documentation, on why the deletion was done, is filed with the paperwork on the fiscal month in which it happened.
I suggest you check your BPCS security on WHO has access to the software that can do the voiding. That should be a tiny fraction of your total staff.
I suggest you check the BPCS software that does the voiding to see what kind of audit trail occurs, and who has ownership of that ... you might modify that so that the person who does the voiding does not have deletion access to the audit trail, rather the person who approves the voiding would control that.
I suggest you check your AS/400 security on WHO has access to delete or change stuff outside of BPCS, like going into an invoice and upping or downing the total $ amount, and if there is any audit trail whatsoever when that happens.
I suggest you check your OTHER security systems to see WHO has access to the data flow, sufficient to change #s ... for example, we use Ops Naf to put copies of BPCS reports into Excel ... that process is vulnerable to someone changing the #s before they get deliverd.
Hi, There is the feeling that someone may void invoices without approval. Though we have manual controls for voiding invoices on the system, the business thinks it will be well controlled if it is approved electronically or someone is prompted anytime something like that is happening. Regards, Isaac A. Antwi -----Original Message----- From: bpcs-l-bounces+iantwi=anglogoldashanti.com.gh@xxxxxxxxxxxx [mailto:bpcs-l-bounces+iantwi=anglogoldashanti.com.gh@xxxxxxxxxxxx] On Behalf Of Sajben@xxxxxxxxxxx Sent: Friday, January 12, 2007 17:15 To: SSA's BPCS ERP System Subject: Re: [BPCS-L] ACP invoice voiding Hi, There is no such standard BPCS feature in 6.1.01. What is the business need behind of this request? Regards Klara |---------+----------------------------------------------> | | "antwi, isaac a." | | | <iantwi@xxxxxxxxxxxxxxxxxxxxxxx> | | | Sent by: | | | bpcs-l-bounces+sajben=proffice.hu@m| | | idrange.com | | | | | | | | | 01/12/2007 05:21 PM | | | Please respond to SSA's BPCS ERP | | | System | | | | |---------+----------------------------------------------> >----------------------------------------------------------------------- ----------------------------------------------------------------------| | | | To: "SSA's BPCS ERP System" <bpcs-l@xxxxxxxxxxxx> | | cc: | | Subject: [BPCS-L] ACP invoice voiding | >----------------------------------------------------------------------- ----------------------------------------------------------------------| Hi All, Can we configure BPCS in such a way that a security officer will be prompted when someone tries to void and invoice or someone have to approve before an invoice is voided? We are on BPCS 6.1.01. Regards, Isaac A. Antwi Applications Manager AngloGold Ashanti Limited (Formerly Ashanti Goldfields Co. Ltd) Information Systems Department Obuasi Mine Tel: +233 (0)582 40494 Ext. 1591 Fax: +233 (0)582 40268 Mobile: +233 (0)24 4672164 E-mail: iantwi@xxxxxxxxxxxxxxxxxxxxxxx <mailto:iantwi@xxxxxxxxxxxxxxxxxxxxxxx> Confidentiality Warning This e-mail message contains confidential information which is intended for the use of the person to whom it is addressed. If you received it in error, please notify the sender and delete the material from any computer. Any disclosure, re-transmission, dissemination or any other use of this information is strictly prohibited -- This is the SSA's BPCS ERP System (BPCS-L) mailing list To post a message email: BPCS-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/bpcs-l or email: BPCS-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/bpcs-l. Delivered-To: sajben@xxxxxxxxxxx -- This is the SSA's BPCS ERP System (BPCS-L) mailing list To post a message email: BPCS-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/bpcs-l or email: BPCS-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/bpcs-l. Delivered-To: iantwi@xxxxxxxxxxxxxxxxxxxxxxx -- This is the SSA's BPCS ERP System (BPCS-L) mailing list To post a message email: BPCS-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/bpcs-l or email: BPCS-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/bpcs-l. Delivered-To: macwheel99@xxxxxxxxxxx
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.
midrange.com
