[ https://issues.apache.org/jira/browse/OFBIZ-5054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jacques Le Roux resolved OFBIZ-5054. ------------------------------------ Resolution: Fixed Fix Version/s: Release Branch 12.04 SVN trunk Release Branch 11.04 Release Branch 10.04 Thanks Tom, your initiative helped much to quickly do the task (I directly tested on trunk demo) Your patch is in trunk r1399761 R12.04 r1399762 11 and 10 will come later (buildbot - for CI - port 1099 conflict not resolved yet) > Find Inventory Event Planned Displays Error Message > --------------------------------------------------- > > Key: OFBIZ-5054 > URL: https://issues.apache.org/jira/browse/OFBIZ-5054 > Project: OFBiz > Issue Type: Bug > Components: manufacturing > Affects Versions: SVN trunk > Environment: Trunk > Reporter: Tom Burns > Assignee: Jacques Le Roux > Priority: Minor > Fix For: Release Branch 10.04, Release Branch 11.04, SVN trunk, > Release Branch 12.04 > > Attachments: OFBIZ-5054MRPFindInventorError.patch > > > In the Manufacturing Manager MRP feature MRP Log displays an error when Find > is clicked in the Find Inventory Event Planned screenlet. > To reproduce: > 1. Create a Routing table (details beyond the scope of this note) > 2. Navigate to the Manufacturing MRP feature. > 3. Select Run MPR > 4. Enter an MRP Name and Facility > 5. Click Submit > 6. Select MRP Log Tab > 7. When Status is finished click Find in the Find Inventory Event Planned > screenlet. > Expected: > MRP Plan > Actual: > Error message before MRP Plan > Error on line 159, column 17 in > component://manufacturing/webapp/manufacturing/mrp/findInventoryEventPlan.ftl > null is undefined. It cannot be assigned to initialQohEvent The problematic > instruction: ---------- ==> assignment: initialQohEvent=null [on line 159, > column 17 in > component://manufacturing/webapp/manufacturing/mrp/findInventoryEventPlan.ftl] > ---------- Java backtrace for programmers: ---------- > ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira