[jira] [Commented] (OFBIZ-10316) Fields going outside
[ https://issues.apache.org/jira/browse/OFBIZ-10316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16447070#comment-16447070 ] James Yong commented on OFBIZ-10316: Hi Padmavati, My desktop browser is showing okay. What is your browser size? > Fields going outside > > > Key: OFBIZ-10316 > URL: https://issues.apache.org/jira/browse/OFBIZ-10316 > Project: OFBiz > Issue Type: Improvement > Components: webpos > Environment: > [https://demo-trunk.ofbiz.apache.org/webpos/control/Login] >Reporter: Padmavati Rawat >Priority: Major > Attachments: FieldsUI.png > > > *Steps to regenerate: * > Open [https://demo-trunk.ofbiz.apache.org/webpos/control/Login] > Search customer through search by. > Select a customer from the list through a checkbox. > Check the First name and Address line 2 fields in the update modal. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10351) Tree View of Call Graph for Services and Simple Methods
[ https://issues.apache.org/jira/browse/OFBIZ-10351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Yong updated OFBIZ-10351: --- Attachment: OFBIZ-10351.patch > Tree View of Call Graph for Services and Simple Methods > --- > > Key: OFBIZ-10351 > URL: https://issues.apache.org/jira/browse/OFBIZ-10351 > Project: OFBiz > Issue Type: Improvement > Components: base >Affects Versions: Trunk >Reporter: James Yong >Assignee: James Yong >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-10351.patch, OFBIZ-10351.patch > > > Option to log a tree view of services and simple methods, and events that are > called in a request. > Some discussion at > https://lists.apache.org/thread.html/079455a596056334265ecbd410b4de13b6e61e1449ac258af5e9679b@%3Cdev.ofbiz.apache.org%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10221) Improve layout and structure of forms
[ https://issues.apache.org/jira/browse/OFBIZ-10221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16446723#comment-16446723 ] Deepak Dixit commented on OFBIZ-10221: -- >>I thought it would be easier to review if the different applications were >>separated. I agree, instead of attaching patch on this ticket, we can crate ticket by component > Improve layout and structure of forms > - > > Key: OFBIZ-10221 > URL: https://issues.apache.org/jira/browse/OFBIZ-10221 > Project: OFBiz > Issue Type: Improvement >Reporter: Julian Leichert >Assignee: Michael Brohl >Priority: Minor > Labels: backport-needed > Fix For: 17.12.01 > > Attachments: OFBIZ-10221-product.template.Main.patch, > OFBIZ-10221_content.content.ContentSearchOptions.patch, > OFBIZ-10221_content.template.cms.AddSubSite.patch, > OFBIZ-10221_content.template.contentsetup.UserPermissions.patch, > OFBIZ-10221_party.template.party.AddressMatchMap.patch, > OFBIZ-10221_product.template.AddMultipleImages.patch, > OFBIZ-10221_product.template.Main.patch, > OFBIZ-10221_webtools.entity.ArtifactInfo.patch, > OFBIZ-10221_webtools.entity.CheckDb.patch, > OFBIZ-10221_webtools.entity.EntityExportAll.patch, > OFBIZ-10221_webtools.entity.EntityImport.patch, > OFBIZ-10221_webtools.entity.EntityImportDir.patch, > OFBIZ-10221_webtools.entity.EntityImportReaders.patch, > OFBIZ-10221_webtools.entity.FetchLogs.patch, > OFBIZ-10221_webtools.entity.ViewDataFile.patch, > OFBIZ-10221_webtools.entity.XmlDsDump.patch > > > While working at a Theme, i discovered that the forms differ in their style > and structure. > I propose a standard form-structure, so that further styling and look is > coherent. > I.e. class definitions ( class="basic-form") are often missing, input-fields > vary in size and the layout does not follow a standard structure. > As mentioned in > [https://lists.apache.org/thread.html/3654e2f8ee3a7f8d6dd6e9dfe8b4184d11d4609a811daa03f6ab2805@%3Cdev.ofbiz.apache.org%3E] > I have attached an example patch, which modifies a form defined in FreeMarker > to conform it to the forms defined in any *Forms.xml. > Often those forms within FreeMarker templates differ from most other forms in > Ofbiz, > I propose a refactoring of these FreeMarker forms, to equalize all forms. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10221) Improve layout and structure of forms
[ https://issues.apache.org/jira/browse/OFBIZ-10221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16446722#comment-16446722 ] Deepak Dixit commented on OFBIZ-10221: -- Thanks [~Dennis Balkir], product.template.Main has been committed at ofbiz framework trunk at r#1829700 > Improve layout and structure of forms > - > > Key: OFBIZ-10221 > URL: https://issues.apache.org/jira/browse/OFBIZ-10221 > Project: OFBiz > Issue Type: Improvement >Reporter: Julian Leichert >Assignee: Michael Brohl >Priority: Minor > Labels: backport-needed > Fix For: 17.12.01 > > Attachments: OFBIZ-10221-product.template.Main.patch, > OFBIZ-10221_content.content.ContentSearchOptions.patch, > OFBIZ-10221_content.template.cms.AddSubSite.patch, > OFBIZ-10221_content.template.contentsetup.UserPermissions.patch, > OFBIZ-10221_party.template.party.AddressMatchMap.patch, > OFBIZ-10221_product.template.AddMultipleImages.patch, > OFBIZ-10221_product.template.Main.patch, > OFBIZ-10221_webtools.entity.ArtifactInfo.patch, > OFBIZ-10221_webtools.entity.CheckDb.patch, > OFBIZ-10221_webtools.entity.EntityExportAll.patch, > OFBIZ-10221_webtools.entity.EntityImport.patch, > OFBIZ-10221_webtools.entity.EntityImportDir.patch, > OFBIZ-10221_webtools.entity.EntityImportReaders.patch, > OFBIZ-10221_webtools.entity.FetchLogs.patch, > OFBIZ-10221_webtools.entity.ViewDataFile.patch, > OFBIZ-10221_webtools.entity.XmlDsDump.patch > > > While working at a Theme, i discovered that the forms differ in their style > and structure. > I propose a standard form-structure, so that further styling and look is > coherent. > I.e. class definitions ( class="basic-form") are often missing, input-fields > vary in size and the layout does not follow a standard structure. > As mentioned in > [https://lists.apache.org/thread.html/3654e2f8ee3a7f8d6dd6e9dfe8b4184d11d4609a811daa03f6ab2805@%3Cdev.ofbiz.apache.org%3E] > I have attached an example patch, which modifies a form defined in FreeMarker > to conform it to the forms defined in any *Forms.xml. > Often those forms within FreeMarker templates differ from most other forms in > Ofbiz, > I propose a refactoring of these FreeMarker forms, to equalize all forms. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OFBIZ-6264) Allow production run tasks to be performed at multiple facilities
[ https://issues.apache.org/jira/browse/OFBIZ-6264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits closed OFBIZ-6264. --- Resolution: Incomplete Unfortunately the description of this ticket does not detail the issue. Therefore it is difficult, for any contributor, to work on this. Given that the ticket did not attract any attention of other contributors, I am closing this ticket. > Allow production run tasks to be performed at multiple facilities > - > > Key: OFBIZ-6264 > URL: https://issues.apache.org/jira/browse/OFBIZ-6264 > Project: OFBiz > Issue Type: Improvement > Components: manufacturing >Affects Versions: Trunk >Reporter: Christian Carlow >Assignee: Pierre Smits >Priority: Major > > This issue was created as suggested by Pierre from OFBIZ-6085 which depends > on this functionality. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OFBIZ-6097) Add lifecycle maintenance capabilities for Schema Parties
[ https://issues.apache.org/jira/browse/OFBIZ-6097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits closed OFBIZ-6097. --- Resolution: Duplicate Closing as it seems a duplicate of OFBIZ-6072 > Add lifecycle maintenance capabilities for Schema Parties > - > > Key: OFBIZ-6097 > URL: https://issues.apache.org/jira/browse/OFBIZ-6097 > Project: OFBiz > Issue Type: Improvement > Components: manufacturing >Affects Versions: Trunk >Reporter: Pierre Smits >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OFBIZ-6085) Add support for production run inventory tracking
[ https://issues.apache.org/jira/browse/OFBIZ-6085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits closed OFBIZ-6085. --- > Add support for production run inventory tracking > - > > Key: OFBIZ-6085 > URL: https://issues.apache.org/jira/browse/OFBIZ-6085 > Project: OFBiz > Issue Type: Improvement > Components: manufacturing >Affects Versions: Trunk >Reporter: Christian Carlow >Assignee: Pierre Smits >Priority: Major > Attachments: OFBIZ-6085.patch > > > Production run inventory tracking seems worthy of support so that production > managers can get an idea of the department work load. InventoryItemDetails > should be created during production run declarations so that the material > that was stocked out for the production run can be tracked while it is being > manufacturing into the good. Essentially is would be like stock moves or > inventory xfers occuring within the production runs for the task fixed asset > facilities/locations. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OFBIZ-6085) Add support for production run inventory tracking
[ https://issues.apache.org/jira/browse/OFBIZ-6085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits resolved OFBIZ-6085. - Resolution: Not A Problem Setting resolution to 'Not a Problem' based on information provided in the comments. > Add support for production run inventory tracking > - > > Key: OFBIZ-6085 > URL: https://issues.apache.org/jira/browse/OFBIZ-6085 > Project: OFBiz > Issue Type: Improvement > Components: manufacturing >Affects Versions: Trunk >Reporter: Christian Carlow >Assignee: Pierre Smits >Priority: Major > Attachments: OFBIZ-6085.patch > > > Production run inventory tracking seems worthy of support so that production > managers can get an idea of the department work load. InventoryItemDetails > should be created during production run declarations so that the material > that was stocked out for the production run can be tracked while it is being > manufacturing into the good. Essentially is would be like stock moves or > inventory xfers occuring within the production runs for the task fixed asset > facilities/locations. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OFBIZ-5560) Production Run Task Issue Components does not take into account manual issuances created on the Materials tab
[ https://issues.apache.org/jira/browse/OFBIZ-5560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits resolved OFBIZ-5560. - Resolution: Not A Problem Setting resolution to 'Not a Problem' based on information provided in comment. > Production Run Task Issue Components does not take into account manual > issuances created on the Materials tab > - > > Key: OFBIZ-5560 > URL: https://issues.apache.org/jira/browse/OFBIZ-5560 > Project: OFBiz > Issue Type: Bug > Components: manufacturing >Affects Versions: Trunk >Reporter: Christian Carlow >Assignee: Pierre Smits >Priority: Major > > Production Run Task Issue Components functionality does not take into account > manual issuances created on the Materials tab. > To reproduce: > 1. Create a production run for 2 of product PIZZA > 2. Issue 1 of product PEPPERS to a task on the Materials tab > 3. Return to the "Edit Production Run" tab and click confirm > 4. Click "Quick Start All Tasks" > 5. Click the "Issue Components" button for the task > 6. Notice the functionality tries to issue 2 even though 1 has already been > manually issued -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OFBIZ-5560) Production Run Task Issue Components does not take into account manual issuances created on the Materials tab
[ https://issues.apache.org/jira/browse/OFBIZ-5560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits closed OFBIZ-5560. --- > Production Run Task Issue Components does not take into account manual > issuances created on the Materials tab > - > > Key: OFBIZ-5560 > URL: https://issues.apache.org/jira/browse/OFBIZ-5560 > Project: OFBiz > Issue Type: Bug > Components: manufacturing >Affects Versions: Trunk >Reporter: Christian Carlow >Assignee: Pierre Smits >Priority: Major > > Production Run Task Issue Components functionality does not take into account > manual issuances created on the Materials tab. > To reproduce: > 1. Create a production run for 2 of product PIZZA > 2. Issue 1 of product PEPPERS to a task on the Materials tab > 3. Return to the "Edit Production Run" tab and click confirm > 4. Click "Quick Start All Tasks" > 5. Click the "Issue Components" button for the task > 6. Notice the functionality tries to issue 2 even though 1 has already been > manually issued -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OFBIZ-5218) MRF Landing Page as Portal Page with some Portlet proposals
[ https://issues.apache.org/jira/browse/OFBIZ-5218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits closed OFBIZ-5218. --- > MRF Landing Page as Portal Page with some Portlet proposals > --- > > Key: OFBIZ-5218 > URL: https://issues.apache.org/jira/browse/OFBIZ-5218 > Project: OFBiz > Issue Type: Improvement > Components: manufacturing >Affects Versions: Trunk > Environment: any >Reporter: Carsten Schinzer >Assignee: Pierre Smits >Priority: Minor > Original Estimate: 120h > Remaining Estimate: 120h > > I would like to introduce a portal page when landing into the manufacturing > component after login. Just as we have already on e.g. ordermgr. > Ideas for portlets to be displayed are currently: > - stats on configuration data (how many routings/routing tasks/boms/... are > configured) > - stats on runtime data (how many production runs by status ...) > - top ten list of runs by status or duration > More ideas are welcome, of course ! > My plan is to collect the requirements into a design document/sheet per > portlet that I would attach here before moving on to implementation. For > personal reasons I will not be able to start with the implementation design > before ca. end July 2013. > Any other portlet ideas for MRP/MRF are appreciated until that deadline. Then > I would like to close the scoping and start writing designs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OFBIZ-5218) MRF Landing Page as Portal Page with some Portlet proposals
[ https://issues.apache.org/jira/browse/OFBIZ-5218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits resolved OFBIZ-5218. - Resolution: Not A Problem Setting resolution as not a problem, due to information provided in comments. > MRF Landing Page as Portal Page with some Portlet proposals > --- > > Key: OFBIZ-5218 > URL: https://issues.apache.org/jira/browse/OFBIZ-5218 > Project: OFBiz > Issue Type: Improvement > Components: manufacturing >Affects Versions: Trunk > Environment: any >Reporter: Carsten Schinzer >Assignee: Pierre Smits >Priority: Minor > Original Estimate: 120h > Remaining Estimate: 120h > > I would like to introduce a portal page when landing into the manufacturing > component after login. Just as we have already on e.g. ordermgr. > Ideas for portlets to be displayed are currently: > - stats on configuration data (how many routings/routing tasks/boms/... are > configured) > - stats on runtime data (how many production runs by status ...) > - top ten list of runs by status or duration > More ideas are welcome, of course ! > My plan is to collect the requirements into a design document/sheet per > portlet that I would attach here before moving on to implementation. For > personal reasons I will not be able to start with the implementation design > before ca. end July 2013. > Any other portlet ideas for MRP/MRF are appreciated until that deadline. Then > I would like to close the scoping and start writing designs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-5218) MRF Landing Page as Portal Page with some Portlet proposals
[ https://issues.apache.org/jira/browse/OFBIZ-5218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-5218: --- Assignee: Pierre Smits > MRF Landing Page as Portal Page with some Portlet proposals > --- > > Key: OFBIZ-5218 > URL: https://issues.apache.org/jira/browse/OFBIZ-5218 > Project: OFBiz > Issue Type: Improvement > Components: manufacturing >Affects Versions: Trunk > Environment: any >Reporter: Carsten Schinzer >Assignee: Pierre Smits >Priority: Minor > Original Estimate: 120h > Remaining Estimate: 120h > > I would like to introduce a portal page when landing into the manufacturing > component after login. Just as we have already on e.g. ordermgr. > Ideas for portlets to be displayed are currently: > - stats on configuration data (how many routings/routing tasks/boms/... are > configured) > - stats on runtime data (how many production runs by status ...) > - top ten list of runs by status or duration > More ideas are welcome, of course ! > My plan is to collect the requirements into a design document/sheet per > portlet that I would attach here before moving on to implementation. For > personal reasons I will not be able to start with the implementation design > before ca. end July 2013. > Any other portlet ideas for MRP/MRF are appreciated until that deadline. Then > I would like to close the scoping and start writing designs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10321) Multi-level BOM (same raw MM in different level) MRP not supportive
[
https://issues.apache.org/jira/browse/OFBIZ-10321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacopo Cappellato updated OFBIZ-10321:
--
Attachment: OFBIZ-10321.patch
> Multi-level BOM (same raw MM in different level) MRP not supportive
> ---
>
> Key: OFBIZ-10321
> URL: https://issues.apache.org/jira/browse/OFBIZ-10321
> Project: OFBiz
> Issue Type: Bug
> Components: manufacturing
>Affects Versions: Release Branch 16.11, 16.11.04
> Environment: OS: Windows Server 2008 R2
> Database: MySQL 5.7
> JDK: 1.8.0_131
>Reporter: Schumann Ye
>Assignee: Jacopo Cappellato
>Priority: Major
> Labels: usability
> Attachments: OFBIZ-10321.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> For MRP funciton in Manufacturing Manager, I intentionally created a BOM as
> follows:
> Level 0: Table (Qty 1, finished goods)
> Level 1: Wood (Qty 5, raw material)
> Level 1: Nails (Qty 20, raw material)
> Level 1: Varnish (Qty 1, raw material)
> Level 1: TableBoardCover (Qty 1, finished goods)
> Level 2: Wood (Qty 1, raw material)
> I've done all routing tasks associated with routings and linked with products.
> Everything is ok but when I run MRP, I get the following error messages:
>
> Code below:
> {code}
> Caused by: org.apache.ofbiz.entity.GenericDataSourceException: SQL Exception
> while executing the following:INSERT INTO MRP_EVENT (MRP_ID, PRODUCT_ID,
> EVENT_DATE, MRP_EVENT_TYPE_ID, FACILITY_ID, QUANTI
> TY, EVENT_NAME, IS_LATE, LAST_UPDATED_STAMP, LAST_UPDATED_TX_STAMP,
> CREATED_STAMP, CREATED_TX_STAMP) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
> (Duplicate entry '10008-{color:#f79232}10010{color}-2018-03-29 16:03:39-MRP_R
> EQUIREMENT' for key 'PRIMARY')
> at
> org.apache.ofbiz.entity.jdbc.SQLProcessor.executeUpdate(SQLProcessor.java:434)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.entity.datasource.GenericDAO.singleInsert(GenericDAO.java:173)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.entity.datasource.GenericDAO.insert(GenericDAO.java:115)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.entity.datasource.GenericHelperDAO.create(GenericHelperDAO.java:65)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.entity.GenericDelegator.create(GenericDelegator.java:883)
> ~[ofbiz.jar:?]
> at org.apache.ofbiz.entity.GenericValue.create(GenericValue.java:73)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.manufacturing.mrp.InventoryEventPlannedServices.createOrUpdateMrpEvent(InventoryEventPlannedServices.java:77)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.manufacturing.mrp.MrpServices.processBomComponent(MrpServices.java:568)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.manufacturing.mrp.MrpServices.executeMrp(MrpServices.java:799)
> ~[ofbiz.jar:?]
> ... 14 more
> Caused by:
> com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException:
> Duplicate entry '10008-{color:#f79232}10010{color}-2018-03-29
> 16:03:39-MRP_REQUIREMENT' for key 'PRIMARY'
> at sun.reflect.GeneratedConstructorAccessor179.newInstance(Unknown
> Source) ~[?:?]
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> ~[?:1.8.0_131]
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> ~[?:1.8.0_131]
> at com.mysql.jdbc.Util.handleNewInstance(Util.java:425)
> ~[mysql-connector-java-5.1.44-bin.jar:5.1.44]
> at com.mysql.jdbc.Util.getInstance(Util.java:408)
> ~[mysql-connector-java-5.1.44-bin.jar:5.1.44]
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:935)
> ~[mysql-connector-java-5.1.44-bin.jar:5.1.44]
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3973)
> ~[mysql-connector-java-5.1.44-bin.jar:5.1.44]
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3909)
> ~[mysql-connector-java-5.1.44-bin.jar:5.1.44]
> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2527)
> ~[mysql-connector-java-5.1.44-bin.jar:5.1.44]
> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2680)
> ~[mysql-connector-java-5.1.44-bin.jar:5.1.44]
> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2487)
> ~[mysql-connector-java-5.1.44-bin.jar:5.1.44]
> at
> com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1858)
> ~[mysql-connector-java-5.1.44-bin.jar:5.1.44]
> at
> com.mysql.jdbc.PreparedStatement.executeUpdateInternal(PreparedStatement.java:2079)
> ~[mysql-connector-java-5.1.44-bin.jar:5.1.44]
> at
> com.mysql.jdbc.PreparedStatement.executeUpdateInternal(PreparedStatement.java:2013)
> ~[mysql-connector-java-5.1.44-bin.jar:5.1.44]
> at
>
[jira] [Commented] (OFBIZ-10321) Multi-level BOM (same raw MM in different level) MRP not supportive
[
https://issues.apache.org/jira/browse/OFBIZ-10321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16446665#comment-16446665
]
Jacopo Cappellato commented on OFBIZ-10321:
---
As discussed in the user list (*), the issue is not in the logic in the MRP but
instead it is caused by the type of the EVENT_DATE field that, in the 16.11.*
releases, for MySQL, is still set to DATETIME instead of DATETIME(3) as in the
newer branches.
I suggest to apply the attached patch to the 16.11 branch.
(*) [https://s.apache.org/gzxV]
> Multi-level BOM (same raw MM in different level) MRP not supportive
> ---
>
> Key: OFBIZ-10321
> URL: https://issues.apache.org/jira/browse/OFBIZ-10321
> Project: OFBiz
> Issue Type: Bug
> Components: manufacturing
>Affects Versions: Release Branch 16.11, 16.11.04
> Environment: OS: Windows Server 2008 R2
> Database: MySQL 5.7
> JDK: 1.8.0_131
>Reporter: Schumann Ye
>Assignee: Jacopo Cappellato
>Priority: Major
> Labels: usability
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> For MRP funciton in Manufacturing Manager, I intentionally created a BOM as
> follows:
> Level 0: Table (Qty 1, finished goods)
> Level 1: Wood (Qty 5, raw material)
> Level 1: Nails (Qty 20, raw material)
> Level 1: Varnish (Qty 1, raw material)
> Level 1: TableBoardCover (Qty 1, finished goods)
> Level 2: Wood (Qty 1, raw material)
> I've done all routing tasks associated with routings and linked with products.
> Everything is ok but when I run MRP, I get the following error messages:
>
> Code below:
> {code}
> Caused by: org.apache.ofbiz.entity.GenericDataSourceException: SQL Exception
> while executing the following:INSERT INTO MRP_EVENT (MRP_ID, PRODUCT_ID,
> EVENT_DATE, MRP_EVENT_TYPE_ID, FACILITY_ID, QUANTI
> TY, EVENT_NAME, IS_LATE, LAST_UPDATED_STAMP, LAST_UPDATED_TX_STAMP,
> CREATED_STAMP, CREATED_TX_STAMP) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
> (Duplicate entry '10008-{color:#f79232}10010{color}-2018-03-29 16:03:39-MRP_R
> EQUIREMENT' for key 'PRIMARY')
> at
> org.apache.ofbiz.entity.jdbc.SQLProcessor.executeUpdate(SQLProcessor.java:434)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.entity.datasource.GenericDAO.singleInsert(GenericDAO.java:173)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.entity.datasource.GenericDAO.insert(GenericDAO.java:115)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.entity.datasource.GenericHelperDAO.create(GenericHelperDAO.java:65)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.entity.GenericDelegator.create(GenericDelegator.java:883)
> ~[ofbiz.jar:?]
> at org.apache.ofbiz.entity.GenericValue.create(GenericValue.java:73)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.manufacturing.mrp.InventoryEventPlannedServices.createOrUpdateMrpEvent(InventoryEventPlannedServices.java:77)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.manufacturing.mrp.MrpServices.processBomComponent(MrpServices.java:568)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.manufacturing.mrp.MrpServices.executeMrp(MrpServices.java:799)
> ~[ofbiz.jar:?]
> ... 14 more
> Caused by:
> com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException:
> Duplicate entry '10008-{color:#f79232}10010{color}-2018-03-29
> 16:03:39-MRP_REQUIREMENT' for key 'PRIMARY'
> at sun.reflect.GeneratedConstructorAccessor179.newInstance(Unknown
> Source) ~[?:?]
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> ~[?:1.8.0_131]
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> ~[?:1.8.0_131]
> at com.mysql.jdbc.Util.handleNewInstance(Util.java:425)
> ~[mysql-connector-java-5.1.44-bin.jar:5.1.44]
> at com.mysql.jdbc.Util.getInstance(Util.java:408)
> ~[mysql-connector-java-5.1.44-bin.jar:5.1.44]
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:935)
> ~[mysql-connector-java-5.1.44-bin.jar:5.1.44]
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3973)
> ~[mysql-connector-java-5.1.44-bin.jar:5.1.44]
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3909)
> ~[mysql-connector-java-5.1.44-bin.jar:5.1.44]
> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2527)
> ~[mysql-connector-java-5.1.44-bin.jar:5.1.44]
> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2680)
> ~[mysql-connector-java-5.1.44-bin.jar:5.1.44]
> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2487)
> ~[mysql-connector-java-5.1.44-bin.jar:5.1.44]
> at
> com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1858)
> ~[mysql-connector-java-5.1.44-bin.jar:5.1.44]
>
