|
I know that many BPCS programs process various inventory transactions according to logic in the program such that the transaction effect rules are a bit of a sham, while some transactions are processed according to some of the rules in the effects. I just do not have a clear mental picture of the differences. I found by accident that this effect does nothing to inventory ... no issues, no multiple issues, no adjustments, nothing. I had always thought that it consumed components corresponding to the item being reported in JIT600 as scrap, and if we had a data reporting / transcribing problem, we could back that out via negative RJ in INV500 for scrap & negative PR & multi-issue for quantity made, being sensitive to the operation actually consuming the material. I went to the BPCS documentation on 405 CD for inventory transactions & compared what it had for the default settings for every transaction effect we had, and our current settings, and every time I found a difference, I looked up the significance of that field. In general I was in total agreement with our changes. However, our RJ is identical to what 405 CD documentation says it is out of the box from SSA which I am thinking is a bug. I am hoping that JIT600 logic processes this correctly ... when the scrap is reported, if that is the operation that consumes the components, it does a multiple issue against all the components going into that operation. I have not traced the logic on this scenario but have looked at it in the past & what seemed to be happening, was correctly computing PR & issues math, then saying, oh this or that is PR CI RJ I suspect INV500 relies heavily on the rules in the transaction effects, so that where we would be at risk would be in corrections to labor transactions that involved scrap. Or am I totally off the wall here? Does JIT600 issue CI multiple issue for both PR and RJ reporting, in which RJ is merely a record that CI occurred, and is not supposed to be done on INV500 at all. MacWheel99@aol.com (Alister Wm Macintyre) (Al Mac)
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.