Another BPCS feature is the need to do extensive testing with any
modification or upgrade, even upgrades from vendors, perhaps especially
with fixes from SSA. This is because BPCS is so versatile in its ability
to serve so many different industries situations, that it is impossible to
do proper testing before software delivered to clients.
Example ... we are at a particular version of BPCS. Mostly working Ok, but
there are some problems, to be fixed by installing some PTF BMR etc. which
does in fact fix a whole slew of things, but in the process, some stuff
that was working Ok is now broken.
You have to get a list of the software modules being replaced in the
package of fixes, then test 100% of those pieces of software, including all
programs that invoke them.
As you identify stuff that is now broke, that was working Ok before, copies
of what was earlier working goes into library list to fix the latest
collection of fixes.
Fortunately for us, everything that got broke at PTF-1 was fixed by later
collections of fixes, without introducing additional this scenario.
The problems of this nature (that we found) at PTF-1 were:
Billing; INV110; SYS800; various MRP
>Programmer/Analyst/Computer Janitor/BS artiste/etc.
As an Amazon Associate we earn from qualifying purchases.