Without purchasing new software products that will only add more overhead and more "things to check" by IT. Every customer should be aware of ALL of the accesses to your database. Some customers will have built in interfaces that will add records to any files in the BPCS/LX environment and those interfaces should always be checked FIRST - In all of the versions/releases of BPCS/LX the file maintenance programs have never allowed duplicate records in the master files.
If duplicate records are found it is almost impossible to blame it on your data entry personnel or the base BPCS/LX file maintenance programs.
Somehow the records got added by an outside source.
Thanks,
Dan Sweeney
Senior ICS Project Lead |Bridgelogix | |simplify your supply chain | 918-280-4205 phone | 918-280-5550 fax |dan.sweeney@xxxxxxxxx
REGISTER NOW | System i User Conference 2011 | Gaylord Opryland | Nashville, TN | October 2 - 5 |
http://go.infor.com/systemiuserconference/
. Please don't print this e-mail unless you really need to.
-----Original Message-----
From: bpcs-l-bounces@xxxxxxxxxxxx [mailto:bpcs-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, September 29, 2011 8:38 AM
To: BPCS ERP System
Subject: Re: [BPCS-L] Duplicate Items in Item Master (and other data accidents)
<snip>
but finding the "guilty" party after
the fact doesn't erase the accident cost, it doesn't permanently slam the
back doors, and it doesn't train employees to keypunch flawlessly. There
will
always be the next data accident.
</snip>
After is after is after. Your product still alerts the farmer after the
horses escaped the barn. It doesn't lock the door. To do that you would
have to add constraints to the database. And triggers for more involved
situations. The problem with that is, if you throw a write error out
because of a violation would Infor's code be able to handle that? For
example would this code:
C WRITE(E) IPI100IM
C*
C IF NOT %ERROR AND OPERRFLAG=*BLANKS
C Z-ADD 1 S_IIML02
C EXSR SMVTOW
C ELSE
C END
C ENDSR
say "dude, there's a constraint violation"?
Let's use another example. The OP asked about duplicate records. Would
your solution catch that? For example I add a duplicate key outside of
infor. Would the DBA then get notified? Or is the product more focused
on individual field errors, like ranges and what not?
Rob Berendt
midrange.com
