We are 405 CD a bit beyond PTF-1
Rel-2 is like a rename for PTF-2 in that there was a huge volume of pieces of code replaced, including SFC620, but I ran PDM-54 on source code for the SFC620 inside REL-2 vs. that inside PTF-1 and they identical ... I think each REL or PTF or whatever coding reference they use, is an aggregation of all changes so far,that came out in individual BMRs between the mass releases.

After REL-02 there was what was called the Y2K bundle of final fixes, which had hundreds of programs, but SFC620 was not in there. There were also some random other BMRs, but SFC620 not in what we got, so your SFC620 is same as ours, vanilla wise. We modified our SFC620 because we believed there was a bug in the algorithm for closing shop orders.

In any definition of a shop order being completed, there is the consumption of the inventory to make the parts, and the labor reporting on the individual steps. We think BPCS was designed to place closure of individual operations and labor saying we done, at a higher priority than all the inventory transactions getting posted correctly, and that the math for scrap was incorrect. We made modificaitons based on this analysis to correct the algorithm.

Does your company use a programming standard that makes it possible to tell the difference between your company modifications and that which came from SSA?

I was not able to find the modification of which you speak, in the code we got from SSA. I only did a cursory check of the coding, since Monday was an extremely tiring day for me. I may look again later.

Wee too have found a great many bugs in BPCS, but not all of them came from SSA.

Al Mac
BPCS/405CD modifier

> We are using BPCS 4.05 CD PTF1. The last mod to program SFC620 was
> 24128 09Apr97. This program ran into an endless loop in our
> production environment.
>
> This endless loop seems to have been introduced on 07Aug96 (mod 26JL6)
> when two FLTK04 CHAIN IPF600LT commands were added at lines 1191 and
> 1194.
>
> Unfortunately, the key being used in these chain commands is not
> unique, which caused the endless loop.
>
> Commenting out the two chain commands seems to have rectified the
> problem.
>
> If you know of any similar bugs in BPCS 4.05 CD PTF1 please let me
> know.
>
> Thanks in advance.
>
> Peter Lunde
> Manager, IT
> WellSpring Pharmaceutical Canada Corp
> 400 Iroquois Shore Rd
> Oakville, ON, L6H 1M5
> Phone: 905-337-4505
> Cell: 416-948-5863
> Fax: 905-337-7239
--
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 thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 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.