- Free Trial
Bug Tracker Incident #7317
Closing because this is really old and the reporter is no longer a partner.
cannot reproduce in 3.7.0RC. setup environment with lot controlled components, received same lot number multiple times, issued to W/O. forward and backward traces in Detailed Inventory History by Lot/Serial work correctly
Key tables involved appear to be ls and ls_detail. The double-receipt-same-lot causes multiple ls_detail records each refering to a single ls record. Also, the failure appears to involve the function, lshist.
Detailed Inventory History by Lot/Serial # report fails in Multi-Level Trace "forward" mode. Database Log displays error shown in attached text file.
Steps to Reproduce:
Failure problem appears to be isolated to circumstances where the report's forward "trace" encounters a Lot Controlled component where multiple receipts of the component were assigned to the same Lot Number. A simple BOM was created where all items were lot controlled. All components were received, however, one of the components was received twice using the same Lot Number. A work order was created and completed for the parent item, components issued, etc. Forward tracing from any component causes the report to fail.
A complete "backward" trace from the parent of the above example showed repeated detail of "sub-components" when the double-receipt-same-lot was tested on a sub-assembly component.
Mike, did you mean to confirm this? It looks like that''s what your note implies.
In the demo DB on 3.1beta2 received YPAINT1 in twice with the same lot number against the same PO.
Then completed an STRUCK1 against a work order.
Ran Detail Inventory History by Lot/Serial# for YPAINT1 on the lot that was received twice and selected Forward (and Backward) tracing.
Data displayed with a DB log error.
|lot trace report error log.txt|
|Incident||3720||error posting misc po voucher||Related to||x|
|Project||XTUPLEAPPS||Ported From Mantis||x|
SubscribersYou do not have permission to view subscribers.
No history available