|
We modified the suspend release program so that upon a release it will check all other conditions lower in the suspend hierarchy & re-suspend if necessary with the new suspend code. Depending on how the suspend codes are setup, stock may or may not be allocated. If stock was allocated and the new suspend condition calls for no allocation, is there an easy way to call an existing JBA program to handle the de-allocation (including reservations) or should we code this logic directly into the suspend release program (OE165)? The batch allocation program OE320 can handle new allocations, but not de-allocations. Any suggestions?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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
