If you need to hang onto item #s, each with a different serial #, perhaps
give some thought to how to code those item #s, to minimize human effort to
maintain them, and lower risk of running out of item #s in some block of #s,
or colliding with another system of designating item #s, as has happened to
us several times.
Success has many fathers, while failure is an orphan.
From: bpcs-l-bounces@xxxxxxxxxxxx [mailto:bpcs-l-bounces@xxxxxxxxxxxx] On
Behalf Of Pete Helgren
Sent: Monday, February 07, 2011 4:56 PM
To: BPCS ERP System
Subject: [BPCS-L] Best practice on calling SFC500 from a custom program
This is a little involved so I'll try to keep it brief. I have recently
implemented an EDI 866 processing program which basically creates an
order for a one-off, unique item tied to a unique serial number. The
manual way that something like this is currently handled is that a query
is used to select inventory items that have a on hand quantity of zero
with an outstanding order for an item. Then the Shop Floor Order
program is called (SFC500) and the shop order entered.
With this 866 record, I need to link the unique serial number of the
ordered item to the shop order. The only way I can think to do this
would be to pass that serial number into the program, but I am not
familiar enough with SFC500 to know what the best approach would be.
The reason I need the shop floor order and the serial number linked is
that the traveler and the packing list need to carry the serial number
Currently I have written a program that will display the 866 orders that
have not yet been processed and do not have a current shop floor order
for the item. I'd like to call SFC500 from my program, passing the
serial number and maybe the order number to the SFC500 program. Or, be
able to retrieve the shop order number once the shop floor order program
For those of you who might have done something similar in version 405CD
of BPCS, any pointers or suggestions on how to accomplish this in the
most expedient fashion?
This mailing list archive is Copyright 1997-2020 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