[jira] [Updated] (OFBIZ-10577) New Feature: Inventory Cycle Count
[ https://issues.apache.org/jira/browse/OFBIZ-10577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad updated OFBIZ-10577: Component/s: hhfacility > New Feature: Inventory Cycle Count > -- > > Key: OFBIZ-10577 > URL: https://issues.apache.org/jira/browse/OFBIZ-10577 > Project: OFBiz > Issue Type: New Feature > Components: hhfacility >Affects Versions: Trunk >Reporter: Yashwant Dhakad >Assignee: Yashwant Dhakad >Priority: Major > > *Here are the design notes for cycle count workflow:* > *Find Session Screen:* In this screen, we will show all the sessions created > in the system with respect to the facility, locations, inventory count item, > current status, and created date. We have a search field to filter the > records on the basis of the facility, status. > *Find Pending Locations:* In this screen, we have a table listing all the > pending locations whose countings are pending and we can create a session for > them. All details regarding the pending locations are listed here with the > location, next count date, last count date and days extended for the count, > total inventory item and product for this location. We have facets for > filtering the records on the basis of the facility, not scanned since and > scheduled for next scan. Also, we have a global search at the top of the > screen. In Pending Locations screen, we have a Create Session button. To > create a session we can either select one or more records from the below list > or create a new session by yourself. > In Create Session screen, the basic overview is shown in the "Overview" > section and the items are listed in the "Items" section. We can create a new > line item by clicking on the 'Add' button and we can also update the item > quantity. After completing this, we can proceed with this session and mark it > with 'Pending for Review' status from the 'Status' button at the top of the > screen or we can simply 'Reject'. 'Reject' status button is available at the > top of the screen. > *Find Review Screen:* In this screen, we have a table listing all the > locations pending for the review. All the details regarding the review > sessions are listed with the facility, locations and counted inventory item. > We have facets for filtering records on the basis of the facility. By > clicking any session we can go to its detail screen, where basic details > regarding this session are listed in the 'Overview' section and items are > listed in the 'Items' section. We can select any number of rows and mark them > as 'Accept' or 'Reject'. When these items are marked as 'Accepted' then the > variance is created and these are added in the Count Progress report. Only > authorized persons can accept or reject the sessions and once the session is > accepted it is marked as 'Completed'. > *Count Progress Report:* In this screen, User can view the advanced counting > related analytics with respect to all the 'Completed' status session from > Reports Screen. We can filter the records on the basis of the facility and > within the date range. We can also see the percentage of the total locations, > inventory items counted and errors occurred during the process. Item variance > details are listed in the below section in tabular form. > Following changes to the existing data model to support end to end counting > process flow: > *New entities:* > *InventoryCount* > inventoryCountId > uploadedByUserLogin > facilityId > statusId > createdDatetime > *InventoryCountItem* > inventoryCountId > inventoryCountItemSeqId > inventoryItemId > itemStatusId > locationSeqId > productId > productIdentifier > quantity > *InventoryCountVariance* > inventoryCountId > inventoryCountItemSeqId > inventoryItemId > productId > productIdentifier > locationSeqId > systemQuantityOnHand > actualQuantityOnHand > varianceQuantityOnHand > totalCost > actualCost > costVariance > actualValue > totalValue > valueVariance > unitCost > *ProductCategoryFacilityLocation* > facilityId > locationSeqId > productCategoryId > fromDate > thruDate > isCountable > *Extended entity:* > *FacilityLocation* > locked > lastCountDate > nextCountDate > *ProductCategory* > isCountable > We will prevent following inbound and outbound transactions within the > application if the location is locked for counting: > Inventory Transfer > Issuance against Sales Order > Sales Return receiving > Inventory receive > Issuance and return inventory in manufacturing Job > Kit breakup > Update Location > Physical Variance creation > The locked locations won’t have any bearing on the transactions that are > affecting the only ATP of parts i.e. Reserving component for Jobs/Sales > Orders etc.
[jira] [Updated] (OFBIZ-9475) Refactor serialize and non-serialize inventory item implementaion
[ https://issues.apache.org/jira/browse/OFBIZ-9475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad updated OFBIZ-9475: --- Component/s: hhfacility > Refactor serialize and non-serialize inventory item implementaion > - > > Key: OFBIZ-9475 > URL: https://issues.apache.org/jira/browse/OFBIZ-9475 > Project: OFBiz > Issue Type: Improvement > Components: hhfacility >Affects Versions: Trunk >Reporter: Deepak Dixit >Assignee: Yashwant Dhakad >Priority: Major > Attachments: OFBIZ-9475.patch, OFBIZ-9475.patch, OFBIZ-9475.patch, > OFBIZ-9475.patch > > > As discussed on dev mailing list [1][2] we need to refactor serialize and > non-serialize inventory item design. > As per current implementation serialize inventory item work on status and > non-serialized inventory item work on inventory item detail. > Proposed Design: > - Use inventory item detail for both serialise and non-serialize inventory > item. Only one additional condition for serialized inventory item that qoh > can't be greater then one. > - We can maintain inventory item status record for both type > [1] http://markmail.org/thread/bd2bpiv6c5wvl7km > [2] http://ofbiz.markmail.org/thread/kro5kcggp4fcose7 > As we do a lot of discussion in the respective mail threads. > [1] http://markmail.org/thread/bd2bpiv6c5wvl7km > [2] http://ofbiz.markmail.org/thread/kro5kcggp4fcose7 > According to this email threads, I conclude that:- > There are 2 types of the inventory item in OFBiz. > 1. *Serialized* > 2. *Non serialized* > Majorly there are 3 entities to manage the various transaction of serialised > and non-serialized inventory items. > 1. _InventoryItem_ > 2. _InventoryItemDetail_ > 3. _InventoryItemStatus_ > Following changes need to be done in the workflow of inventory item records:- > 1) There is no need to manage a different workflow for serialised and non- > serialised inventory items. > 2) Transaction of serialised and non-serialised inventory item should be > managed in both InventoryItemStatus and InventoryItemDetail entity. > a) Transaction of serialised inventory items is managed by > inventoryItemstatus entity not managed in inventoryItemDetail entity. While > inventoryItemDetail and inventoryItemStatus should be managed for both > serialised and non-serialised inventory items. > b) As ATP/QOH/AQT are updated on the basis of ATPDIFF/QOHDIFF/AQTDIFF in > non-serialised inventory item. We should follow the same pattern for > serialised inventory item. > c) Change in ATP/QOH/AQT is tracked by inventoryItemDetail entity. > d)Status transaction of an inventory item is tracked in > InventoryItemStatus entity. > 3) No need to manage separate status for serialised and non-serialised > inventory item. They are already distinguished on the basis of inventory item > type. > 1. *Serialised*:- > In a serialised inventory item as of now ATP/QOH/AQT are managed on the > basis of inventory item status.While ATP/QOH/AQT should be the sum of > ATPDIFF/QOHDIFF/AQTDIFF of inventory item detail. > Ex: > 1. If we receive 2 inventory of serialised inventory item then 2 separate > inventory item records are created > InventoryItem:- > inventoryItemId="10001",status="AVAILABLE", ATP="1", QOH="1",AQT="1" > inventoryItemId="10002",status="AVAILABLE", ATP="1", QOH="1",AQT="1" > InventoryItemDetail:- > inventoryItemId="10001", inventoryItemDetailSeqId="10001", ATPDIFF="1", > QOHDIFF="1", AQTDIFF="1" > inventoryItemId="10002", inventoryItemDetailSeqId="10002", ATPDIFF="1", > QOHDIFF="1", AQTDIFF="1" > InventoryItemStatus:- > inventoryItemId="10001" statusId="AVAILABLE" > inventoryItemId="10002" statusId="AVAILABLE" > 2. If status of inventory item is changed from AVAILABLE -> PROMISED then > InventoryItem:- > inventoryItemId="10001",status="PROMISED", ATP="1", QOH="1",AQT="1" > inventoryItemId="10002",status="AVAILABLE", ATP="1", QOH="1",AQT="1" > InventoryItemDetail:- > inventoryItemId="10001", inventoryItemDetailSeqId="10001", ATPDIFF="1", > QOHDIFF="1", AQTDIFF="1" > inventoryItemId="10001", inventoryItemDetailSeqId="10002", ATPDIFF="-1", > QOHDIFF="0", AQTDIFF="0" > inventoryItemId="10002", inventoryItemDetailSeqId="10002", ATPDIFF="1", > QOHDIFF="1", AQTDIFF="1" > InventoryItemStatus:- > inventoryItemId="10001" statusId="AVAILABLE" statusEndDateTime="" > inventoryItemId="10002" statusId="PROMISED" > 2. *Non-serialised*:- > At the time of receive non-serialised inventory, Item should be received > in Available status. So that status of non-serialised inventory item can be > managed further. > Status of non-serialised inventory item should be managed at inventory > item level not on inventory item detail level i.e. there are limited > inventory item status
[jira] [Updated] (OFBIZ-10577) New Feature: Inventory Cycle Count
[ https://issues.apache.org/jira/browse/OFBIZ-10577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad updated OFBIZ-10577: Affects Version/s: Trunk > New Feature: Inventory Cycle Count > -- > > Key: OFBIZ-10577 > URL: https://issues.apache.org/jira/browse/OFBIZ-10577 > Project: OFBiz > Issue Type: New Feature >Affects Versions: Trunk >Reporter: Yashwant Dhakad >Assignee: Yashwant Dhakad >Priority: Major > > *Here are the design notes for cycle count workflow:* > *Find Session Screen:* In this screen, we will show all the sessions created > in the system with respect to the facility, locations, inventory count item, > current status, and created date. We have a search field to filter the > records on the basis of the facility, status. > *Find Pending Locations:* In this screen, we have a table listing all the > pending locations whose countings are pending and we can create a session for > them. All details regarding the pending locations are listed here with the > location, next count date, last count date and days extended for the count, > total inventory item and product for this location. We have facets for > filtering the records on the basis of the facility, not scanned since and > scheduled for next scan. Also, we have a global search at the top of the > screen. In Pending Locations screen, we have a Create Session button. To > create a session we can either select one or more records from the below list > or create a new session by yourself. > In Create Session screen, the basic overview is shown in the "Overview" > section and the items are listed in the "Items" section. We can create a new > line item by clicking on the 'Add' button and we can also update the item > quantity. After completing this, we can proceed with this session and mark it > with 'Pending for Review' status from the 'Status' button at the top of the > screen or we can simply 'Reject'. 'Reject' status button is available at the > top of the screen. > *Find Review Screen:* In this screen, we have a table listing all the > locations pending for the review. All the details regarding the review > sessions are listed with the facility, locations and counted inventory item. > We have facets for filtering records on the basis of the facility. By > clicking any session we can go to its detail screen, where basic details > regarding this session are listed in the 'Overview' section and items are > listed in the 'Items' section. We can select any number of rows and mark them > as 'Accept' or 'Reject'. When these items are marked as 'Accepted' then the > variance is created and these are added in the Count Progress report. Only > authorized persons can accept or reject the sessions and once the session is > accepted it is marked as 'Completed'. > *Count Progress Report:* In this screen, User can view the advanced counting > related analytics with respect to all the 'Completed' status session from > Reports Screen. We can filter the records on the basis of the facility and > within the date range. We can also see the percentage of the total locations, > inventory items counted and errors occurred during the process. Item variance > details are listed in the below section in tabular form. > Following changes to the existing data model to support end to end counting > process flow: > *New entities:* > *InventoryCount* > inventoryCountId > uploadedByUserLogin > facilityId > statusId > createdDatetime > *InventoryCountItem* > inventoryCountId > inventoryCountItemSeqId > inventoryItemId > itemStatusId > locationSeqId > productId > productIdentifier > quantity > *InventoryCountVariance* > inventoryCountId > inventoryCountItemSeqId > inventoryItemId > productId > productIdentifier > locationSeqId > systemQuantityOnHand > actualQuantityOnHand > varianceQuantityOnHand > totalCost > actualCost > costVariance > actualValue > totalValue > valueVariance > unitCost > *ProductCategoryFacilityLocation* > facilityId > locationSeqId > productCategoryId > fromDate > thruDate > isCountable > *Extended entity:* > *FacilityLocation* > locked > lastCountDate > nextCountDate > *ProductCategory* > isCountable > We will prevent following inbound and outbound transactions within the > application if the location is locked for counting: > Inventory Transfer > Issuance against Sales Order > Sales Return receiving > Inventory receive > Issuance and return inventory in manufacturing Job > Kit breakup > Update Location > Physical Variance creation > The locked locations won’t have any bearing on the transactions that are > affecting the only ATP of parts i.e. Reserving component for Jobs/Sales > Orders etc. as they don’t affect QOH in any
[jira] [Updated] (OFBIZ-10585) Production run not created for marketing package auto type product if component inventory is not available
[ https://issues.apache.org/jira/browse/OFBIZ-10585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad updated OFBIZ-10585: Affects Version/s: Release Branch 17.12 Trunk Release Branch 16.11 > Production run not created for marketing package auto type product if > component inventory is not available > -- > > Key: OFBIZ-10585 > URL: https://issues.apache.org/jira/browse/OFBIZ-10585 > Project: OFBiz > Issue Type: Bug > Components: manufacturing >Affects Versions: Trunk, Release Branch 16.11, Release Branch 17.12 >Reporter: Yashwant Dhakad >Priority: Major > > When we create an order for marketing package auto, the system checks the > component inventory and if found then it creates the production run job and > produce marketing package inventory, but if component quantity not available > then it does not create the job. So if we don't have an inventory item of > component then production run should be created with created status. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10585) Production run not created for marketing package auto type product if component inventory is not available
[ https://issues.apache.org/jira/browse/OFBIZ-10585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad updated OFBIZ-10585: Component/s: manufacturing > Production run not created for marketing package auto type product if > component inventory is not available > -- > > Key: OFBIZ-10585 > URL: https://issues.apache.org/jira/browse/OFBIZ-10585 > Project: OFBiz > Issue Type: Bug > Components: manufacturing >Affects Versions: Trunk, Release Branch 16.11, Release Branch 17.12 >Reporter: Yashwant Dhakad >Priority: Major > > When we create an order for marketing package auto, the system checks the > component inventory and if found then it creates the production run job and > produce marketing package inventory, but if component quantity not available > then it does not create the job. So if we don't have an inventory item of > component then production run should be created with created status. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-9746) updateContentAssoc does not return success/error message to the UI.
[ https://issues.apache.org/jira/browse/OFBIZ-9746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16627413#comment-16627413 ] Jacques Le Roux commented on OFBIZ-9746: Seems appropriate indeed, the same should be done when creating a content association (only R16), thanks! BTW, removeContentAssoc (delete) is already entity-auto so works. > updateContentAssoc does not return success/error message to the UI. > --- > > Key: OFBIZ-9746 > URL: https://issues.apache.org/jira/browse/OFBIZ-9746 > Project: OFBiz > Issue Type: Bug > Components: content >Affects Versions: Release Branch 16.11 >Reporter: Rohit Rai >Assignee: Aditya Sharma >Priority: Major > > 1. Go to, Content. > 2. Find contents using the find form and select any content from the list./ > 3. Click on the submenu "Association" > 4. In the Edit content association section, select a through date and click > on update > The date gets updated but the user is not presented with the success message > on the UI. > Here is the link to the form, > [https://demo-stable.ofbiz.apache.org/content/control/EditContentAssoc?contentId=BLOGROOT] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-8842) Search operation on 'AssocRevisionItemView' entity causing exception.
[ https://issues.apache.org/jira/browse/OFBIZ-8842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suraj Khurana updated OFBIZ-8842: - Fix Version/s: (was: Release Branch 17.12) (was: Release Branch 16.11) 16.11.05 17.12.01 > Search operation on 'AssocRevisionItemView' entity causing exception. > - > > Key: OFBIZ-8842 > URL: https://issues.apache.org/jira/browse/OFBIZ-8842 > Project: OFBiz > Issue Type: Bug > Components: framework/webtools >Affects Versions: Trunk >Reporter: Humera Khan >Assignee: Suraj Khurana >Priority: Major > Fix For: 17.12.01, 16.11.05 > > Attachments: Assoc_Actual.png, Assoc_Expected.png, OFBIZ-8842.patch > > > Steps to regenerate : > 1. Go to Entity Data Maintenance in webtools. > 2. Search entity 'AssocRevisionItemView'. Click on it and go to the overview > page. > 3. Click on the Find button. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10342) Service Log screen is broken
[
https://issues.apache.org/jira/browse/OFBIZ-10342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16627146#comment-16627146
]
Jacques Le Roux commented on OFBIZ-10342:
-
Hi Rishi, All,
Right, actually {{rs.setEndStamp()}} is needed where an exception is thrown,
not only in in catch blocks. For all the rest, the last {{rs.setEndStamp()}} is
sufficient.
I wondered if we should also add these somehow related lines, which are just
after the last current {{rs.setEndStamp()}}, while adding {{rs.setEndStamp()}}
elsewhere
{code}
long timeToRun = System.currentTimeMillis() - serviceStartTime;
long showServiceDurationThreshold =
UtilProperties.getPropertyAsLong("service", "showServiceDurationThreshold", 0);
long showSlowServiceThreshold =
UtilProperties.getPropertyAsLong("service", "showSlowServiceThreshold", 1000);
{code}
But there is already another existing {{rs.setEndStamp()}} in this catch block
{code}
} catch (Throwable t) {
if (Debug.timingOn()) {
UtilTimer.closeTimer(localName + " / " + modelService.name,
"Sync service failed...", module);
}
String errMsg = "Service [" + modelService.name + "] threw an
unexpected exception/error";
engine.sendCallbacks(modelService, context, t,
GenericEngine.SYNC_MODE);
try {
TransactionUtil.rollback(beganTrans, errMsg, t);
} catch (GenericTransactionException te) {
Debug.logError(te, "Cannot rollback transaction", module);
}
rs.setEndStamp();
if (t instanceof ServiceAuthException) {
throw (ServiceAuthException) t;
} else if (t instanceof ServiceValidationException) {
throw (ServiceValidationException) t;
} else if (t instanceof GenericServiceException) {
throw (GenericServiceException) t;
} else {
throw new GenericServiceException("Service [" +
modelService.name + "] Failed" + modelService.debugInfo() , t);
}
} finally {
{code}
with no set for timeToRun, showServiceDurationThreshold and
showSlowServiceThreshold.
I did not digg further but I guess it's OK to do the same everywhere else it's
needed (ie neglecting timeToRun, showServiceDurationThreshold and
showSlowServiceThreshold).
Also I did not try to improve the code in this issue (could be done, 273
lines... but not easy...).
Please check the attached patch in case I missed something, thanks.
> Service Log screen is broken
>
>
> Key: OFBIZ-10342
> URL: https://issues.apache.org/jira/browse/OFBIZ-10342
> Project: OFBiz
> Issue Type: Bug
> Components: framework/webtools
>Reporter: Swapnil M Mane
>Assignee: Jacques Le Roux
>Priority: Major
> Attachments: OFBIZ-10342.patch, serviceLog.png
>
>
> Service Log screen is broken.
> Steps to regenerate
> # Navigate to Logging menu under webtools
> [https://demo-trunk.ofbiz.apache.org/webtools/control/LogView]
> # Select Service Log menu
> *Console Logs*
> {code:java}
> |T| [[[ServiceLog(Domain:https://localhost)] Request Begun,
> encoding=[UTF-8]- total:0.0,since last(Begin):0.0]]
> 2018-04-16 16:23:03,482 |jsse-nio-8443-exec-8 |RequestHandler
> |I| Rendering View [ServiceLog]. Hidden sessionId by default.
> 2018-04-16 16:23:03,483 |jsse-nio-8443-exec-8 |ServiceDispatcher
> |T| Sync service [webtools/getUserPreferenceGroup] finished in [1]
> milliseconds
> 2018-04-16 16:23:03,484 |jsse-nio-8443-exec-8 |ScriptUtil
> |W| Error running script at location
> [component://webtools/groovyScripts/service/Services.groovy]:
> java.lang.NullPointerException
> java.lang.NullPointerException: null
> at
> org.apache.ofbiz.service.RunningService.getEndStamp(RunningService.java:63)
> ~[ofbiz.jar:?]
> at org.apache.ofbiz.service.RunningService$getEndStamp$2.call(Unknown
> Source) ~[?:?]
> at Services$_run_closure1.doCall(Services.groovy:43) ~[?:?]
> at sun.reflect.GeneratedMethodAccessor98.invoke(Unknown Source) ~[?:?]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[?:1.8.0_66]
> at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_66]
> at
> org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93)
> ~[groovy-all-2.4.13.jar:2.4.13]
> at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
> ~[groovy-all-2.4.13.jar:2.4.13]
> at
> org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:294)
> ~[groovy-all-2.4.13.jar:2.4.13]
>
[jira] [Updated] (OFBIZ-10342) Service Log screen is broken
[
https://issues.apache.org/jira/browse/OFBIZ-10342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux updated OFBIZ-10342:
Attachment: OFBIZ-10342.patch
> Service Log screen is broken
>
>
> Key: OFBIZ-10342
> URL: https://issues.apache.org/jira/browse/OFBIZ-10342
> Project: OFBiz
> Issue Type: Bug
> Components: framework/webtools
>Reporter: Swapnil M Mane
>Assignee: Jacques Le Roux
>Priority: Major
> Attachments: OFBIZ-10342.patch, serviceLog.png
>
>
> Service Log screen is broken.
> Steps to regenerate
> # Navigate to Logging menu under webtools
> [https://demo-trunk.ofbiz.apache.org/webtools/control/LogView]
> # Select Service Log menu
> *Console Logs*
> {code:java}
> |T| [[[ServiceLog(Domain:https://localhost)] Request Begun,
> encoding=[UTF-8]- total:0.0,since last(Begin):0.0]]
> 2018-04-16 16:23:03,482 |jsse-nio-8443-exec-8 |RequestHandler
> |I| Rendering View [ServiceLog]. Hidden sessionId by default.
> 2018-04-16 16:23:03,483 |jsse-nio-8443-exec-8 |ServiceDispatcher
> |T| Sync service [webtools/getUserPreferenceGroup] finished in [1]
> milliseconds
> 2018-04-16 16:23:03,484 |jsse-nio-8443-exec-8 |ScriptUtil
> |W| Error running script at location
> [component://webtools/groovyScripts/service/Services.groovy]:
> java.lang.NullPointerException
> java.lang.NullPointerException: null
> at
> org.apache.ofbiz.service.RunningService.getEndStamp(RunningService.java:63)
> ~[ofbiz.jar:?]
> at org.apache.ofbiz.service.RunningService$getEndStamp$2.call(Unknown
> Source) ~[?:?]
> at Services$_run_closure1.doCall(Services.groovy:43) ~[?:?]
> at sun.reflect.GeneratedMethodAccessor98.invoke(Unknown Source) ~[?:?]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[?:1.8.0_66]
> at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_66]
> at
> org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93)
> ~[groovy-all-2.4.13.jar:2.4.13]
> at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
> ~[groovy-all-2.4.13.jar:2.4.13]
> at
> org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:294)
> ~[groovy-all-2.4.13.jar:2.4.13]
> at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022)
> ~[groovy-all-2.4.13.jar:2.4.13]
> at groovy.lang.Closure.call(Closure.java:414)
> ~[groovy-all-2.4.13.jar:2.4.13]
> at
> org.codehaus.groovy.runtime.DefaultGroovyMethods.callClosureForMapEntry(DefaultGroovyMethods.java:5276)
> ~[groovy-all-2.4.13.jar:2.4.13]
> at
> org.codehaus.groovy.runtime.DefaultGroovyMethods.each(DefaultGroovyMethods.java:2117)
> ~[groovy-all-2.4.13.jar:2.4.13]
> at org.codehaus.groovy.runtime.dgm$164.invoke(Unknown Source)
> ~[groovy-all-2.4.13.jar:2.4.13]
> at
> org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoMetaMethodSiteNoUnwrapNoCoerce.invoke(PojoMetaMethodSite.java:274)
> ~[groovy-all-2.4.13.jar:2.4.13]
> at
> org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite.call(PojoMetaMethodSite.java:56)
> ~[groovy-all-2.4.13.jar:2.4.13]
> at
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:125)
> ~[groovy-all-2.4.13.jar:2.4.13]
> at Services.run(Services.groovy:38) ~[?:?]
> at
> org.apache.ofbiz.base.util.GroovyUtil.runScriptAtLocation(GroovyUtil.java:209)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.base.util.ScriptUtil.executeScript(ScriptUtil.java:342)
> [ofbiz.jar:?]
> at
> org.apache.ofbiz.base.util.ScriptUtil.executeScript(ScriptUtil.java:324)
> [ofbiz.jar:?]
> at
> org.apache.ofbiz.widget.model.AbstractModelAction$Script.runAction(AbstractModelAction.java:634)
> [ofbiz.jar:?]
> at
> org.apache.ofbiz.widget.model.AbstractModelAction.runSubActions(AbstractModelAction.java:143)
> [ofbiz.jar:?]
> at
> org.apache.ofbiz.widget.model.ModelScreenWidget$Section.renderWidgetString(ModelScreenWidget.java:277)
> [ofbiz.jar:?]
> at
> org.apache.ofbiz.widget.model.ModelScreen.renderScreenString(ModelScreen.java:164)
> [ofbiz.jar:?]
> at
> org.apache.ofbiz.widget.renderer.ScreenRenderer.render(ScreenRenderer.java:140)
> [ofbiz.jar:?]
> at
> org.apache.ofbiz.widget.renderer.ScreenRenderer.render(ScreenRenderer.java:102)
> [ofbiz.jar:?]
> at
> org.apache.ofbiz.widget.renderer.macro.MacroScreenViewHandler.render(MacroScreenViewHandler.java:115)
> [ofbiz.jar:?]
> at
> org.apache.ofbiz.webapp.control.RequestHandler.renderView(RequestHandler.java:1014)
> [ofbiz.jar:?]
> at
>
[jira] [Commented] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16627142#comment-16627142 ] Deepak Nigam commented on OFBIZ-10518: -- Thanks for the inputs [~arunpati], [~suraj.khurana]. [~arunpati], It is not configurable as of now. We can make it configurable to use the allocation feature or not. Yes, for auto reserved, inventory will be allocated as same as item qty along with auto approve of Allocation Plan. [~suraj.khurana], The answer to all of your queries is no as of now. But yes, we can definitely include these in the design. > Inventory (Supply) Allocation Planning > -- > > Key: OFBIZ-10518 > URL: https://issues.apache.org/jira/browse/OFBIZ-10518 > Project: OFBiz > Issue Type: New Feature > Components: order, product >Reporter: Deepak Nigam >Assignee: Deepak Nigam >Priority: Major > Fix For: Trunk > > Attachments: CreateAllocationPlan-Step1.png, > CreateAllocationPlan-Step2.png, CreateAllocationPlanEditMode-Step2.png, > EditAllocationPlan.png, FindAllocationPlan.png, OFBiz-10518.patch, > ViewAllocationPlan.png > > > In the current implementation of inventory reservation flow, inventory gets > reserved for the order based on the reservation algorithm (FIFO, LIFO etc). > Many times, the fulfilment cycle of the order is too long or due to some > unexpected circumstances, the order holds the inventory for a long time. In > such scenarios, inventory availability becomes one of the major bottlenecks > in fulfilling the other sales order and businesses often remains short > supplied against the demand. > > We can provide a feature (Create, Find and Edit supply allocation screen) to > allocate the available and any future supply judiciously amongst existing > customers orders by considering different factors like estimated delivery > dates, order priority, customer preference etc. > > Following are the details design notes for the same: > > An order in the approved status will be considered as ‘Eligible for > Allocation’. The proposed supply allocation planning will have the following > set of features: > > *Create Allocation Plan:* > The authorized user will be able to initiate the process by setting the > desired product. > > *View/Edit Allocation Plan:* > 1) The system would search and list all the order lines which are eligible > for allocation for that particular product. > 2) The user can filter and sort the orders by various parameters like Sale > Channel, Customer, Order Id, Estimated Ship Date etc. > 3) The user can then prioritize the order by moving up or down the given > order in the priority ranking. Higher is the order in display result list, > higher will be the priority it would get during reservations. > 4) The user can set the ‘Allocated Quantity’ against ordered quantity at > order item line level. > 5) Once the Allocation Plan is submitted, the system would auto-assign the > priority and set the allocated quantity for each of the submitted orders to > be honoured during order reservations at any point in time. > 7) Incoming shipments would be reserved by honouring the same allocation plan > during order promising cycle. > 8) After allocating supply as per the allocation plan, any excess stock > should be reserved based on the standard FIFO method. > 9) If any of the items of an order is not planned via the Allocation Plan, > then also it should be reserved based on default FIFO criteria. > 10) The allocation for all the sales orders should be allowed for revision > unless the Shipment Plan is created against them. > > *Find Allocation Plan:* > The authorized user can search allocation plan(s) with filters like Plan Id, > Order Id, Product Id, Plan Method, Status etc. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-9746) updateContentAssoc does not return success/error message to the UI.
[ https://issues.apache.org/jira/browse/OFBIZ-9746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16627137#comment-16627137 ] Aditya Sharma commented on OFBIZ-9746: -- Sure Jacques. But as OFBIZ-9907 is an improvement, I was wondering rather than backporting we can return successMessage from the simple-method. WDYT? > updateContentAssoc does not return success/error message to the UI. > --- > > Key: OFBIZ-9746 > URL: https://issues.apache.org/jira/browse/OFBIZ-9746 > Project: OFBiz > Issue Type: Bug > Components: content >Affects Versions: Release Branch 16.11 >Reporter: Rohit Rai >Assignee: Aditya Sharma >Priority: Major > > 1. Go to, Content. > 2. Find contents using the find form and select any content from the list./ > 3. Click on the submenu "Association" > 4. In the Edit content association section, select a through date and click > on update > The date gets updated but the user is not presented with the success message > on the UI. > Here is the link to the form, > [https://demo-stable.ofbiz.apache.org/content/control/EditContentAssoc?contentId=BLOGROOT] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10342) Service Log screen is broken
[
https://issues.apache.org/jira/browse/OFBIZ-10342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux reassigned OFBIZ-10342:
---
Assignee: Jacques Le Roux
> Service Log screen is broken
>
>
> Key: OFBIZ-10342
> URL: https://issues.apache.org/jira/browse/OFBIZ-10342
> Project: OFBiz
> Issue Type: Bug
> Components: framework/webtools
>Reporter: Swapnil M Mane
>Assignee: Jacques Le Roux
>Priority: Major
> Attachments: serviceLog.png
>
>
> Service Log screen is broken.
> Steps to regenerate
> # Navigate to Logging menu under webtools
> [https://demo-trunk.ofbiz.apache.org/webtools/control/LogView]
> # Select Service Log menu
> *Console Logs*
> {code:java}
> |T| [[[ServiceLog(Domain:https://localhost)] Request Begun,
> encoding=[UTF-8]- total:0.0,since last(Begin):0.0]]
> 2018-04-16 16:23:03,482 |jsse-nio-8443-exec-8 |RequestHandler
> |I| Rendering View [ServiceLog]. Hidden sessionId by default.
> 2018-04-16 16:23:03,483 |jsse-nio-8443-exec-8 |ServiceDispatcher
> |T| Sync service [webtools/getUserPreferenceGroup] finished in [1]
> milliseconds
> 2018-04-16 16:23:03,484 |jsse-nio-8443-exec-8 |ScriptUtil
> |W| Error running script at location
> [component://webtools/groovyScripts/service/Services.groovy]:
> java.lang.NullPointerException
> java.lang.NullPointerException: null
> at
> org.apache.ofbiz.service.RunningService.getEndStamp(RunningService.java:63)
> ~[ofbiz.jar:?]
> at org.apache.ofbiz.service.RunningService$getEndStamp$2.call(Unknown
> Source) ~[?:?]
> at Services$_run_closure1.doCall(Services.groovy:43) ~[?:?]
> at sun.reflect.GeneratedMethodAccessor98.invoke(Unknown Source) ~[?:?]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[?:1.8.0_66]
> at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_66]
> at
> org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93)
> ~[groovy-all-2.4.13.jar:2.4.13]
> at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
> ~[groovy-all-2.4.13.jar:2.4.13]
> at
> org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:294)
> ~[groovy-all-2.4.13.jar:2.4.13]
> at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022)
> ~[groovy-all-2.4.13.jar:2.4.13]
> at groovy.lang.Closure.call(Closure.java:414)
> ~[groovy-all-2.4.13.jar:2.4.13]
> at
> org.codehaus.groovy.runtime.DefaultGroovyMethods.callClosureForMapEntry(DefaultGroovyMethods.java:5276)
> ~[groovy-all-2.4.13.jar:2.4.13]
> at
> org.codehaus.groovy.runtime.DefaultGroovyMethods.each(DefaultGroovyMethods.java:2117)
> ~[groovy-all-2.4.13.jar:2.4.13]
> at org.codehaus.groovy.runtime.dgm$164.invoke(Unknown Source)
> ~[groovy-all-2.4.13.jar:2.4.13]
> at
> org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoMetaMethodSiteNoUnwrapNoCoerce.invoke(PojoMetaMethodSite.java:274)
> ~[groovy-all-2.4.13.jar:2.4.13]
> at
> org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite.call(PojoMetaMethodSite.java:56)
> ~[groovy-all-2.4.13.jar:2.4.13]
> at
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:125)
> ~[groovy-all-2.4.13.jar:2.4.13]
> at Services.run(Services.groovy:38) ~[?:?]
> at
> org.apache.ofbiz.base.util.GroovyUtil.runScriptAtLocation(GroovyUtil.java:209)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.base.util.ScriptUtil.executeScript(ScriptUtil.java:342)
> [ofbiz.jar:?]
> at
> org.apache.ofbiz.base.util.ScriptUtil.executeScript(ScriptUtil.java:324)
> [ofbiz.jar:?]
> at
> org.apache.ofbiz.widget.model.AbstractModelAction$Script.runAction(AbstractModelAction.java:634)
> [ofbiz.jar:?]
> at
> org.apache.ofbiz.widget.model.AbstractModelAction.runSubActions(AbstractModelAction.java:143)
> [ofbiz.jar:?]
> at
> org.apache.ofbiz.widget.model.ModelScreenWidget$Section.renderWidgetString(ModelScreenWidget.java:277)
> [ofbiz.jar:?]
> at
> org.apache.ofbiz.widget.model.ModelScreen.renderScreenString(ModelScreen.java:164)
> [ofbiz.jar:?]
> at
> org.apache.ofbiz.widget.renderer.ScreenRenderer.render(ScreenRenderer.java:140)
> [ofbiz.jar:?]
> at
> org.apache.ofbiz.widget.renderer.ScreenRenderer.render(ScreenRenderer.java:102)
> [ofbiz.jar:?]
> at
> org.apache.ofbiz.widget.renderer.macro.MacroScreenViewHandler.render(MacroScreenViewHandler.java:115)
> [ofbiz.jar:?]
> at
> org.apache.ofbiz.webapp.control.RequestHandler.renderView(RequestHandler.java:1014)
> [ofbiz.jar:?]
> at
>
[jira] [Commented] (OFBIZ-9746) updateContentAssoc does not return success/error message to the UI.
[ https://issues.apache.org/jira/browse/OFBIZ-9746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16627069#comment-16627069 ] Jacques Le Roux commented on OFBIZ-9746: Hi Aditya Just tried to backport r1813623 in R16. I just got a small conflict in contentservices.xml, will you handle it? > updateContentAssoc does not return success/error message to the UI. > --- > > Key: OFBIZ-9746 > URL: https://issues.apache.org/jira/browse/OFBIZ-9746 > Project: OFBiz > Issue Type: Bug > Components: content >Affects Versions: Release Branch 16.11 >Reporter: Rohit Rai >Assignee: Aditya Sharma >Priority: Major > > 1. Go to, Content. > 2. Find contents using the find form and select any content from the list./ > 3. Click on the submenu "Association" > 4. In the Edit content association section, select a through date and click > on update > The date gets updated but the user is not presented with the success message > on the UI. > Here is the link to the form, > [https://demo-stable.ofbiz.apache.org/content/control/EditContentAssoc?contentId=BLOGROOT] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16627057#comment-16627057 ] Suraj Khurana commented on OFBIZ-10518: --- +1 [~arunpati]. We should make it configurable similarly as we recently did for accounting Please let me confirm if these cases are handled or not. I check and curious to know how this is handled. 1. How maySplit is handled in OrderItemShipGroup in case of manual allocation, I propose we should mark this indicator as true in case of manual allocation. 2. Suppose a case where out of 20 ordered quantity, 10 are approved for allocation, after reservation, can we again edit allocation qty to 5? Will it also re-reserve and change reservation as well to 5? If it is not working like this, IMO, we need to handle it. 3. Did we honour facility in this? I think it is not properly handle in current patch. Thanks [~deepak.nigam] for this work. > Inventory (Supply) Allocation Planning > -- > > Key: OFBIZ-10518 > URL: https://issues.apache.org/jira/browse/OFBIZ-10518 > Project: OFBiz > Issue Type: New Feature > Components: order, product >Reporter: Deepak Nigam >Assignee: Deepak Nigam >Priority: Major > Fix For: Trunk > > Attachments: CreateAllocationPlan-Step1.png, > CreateAllocationPlan-Step2.png, CreateAllocationPlanEditMode-Step2.png, > EditAllocationPlan.png, FindAllocationPlan.png, OFBiz-10518.patch, > ViewAllocationPlan.png > > > In the current implementation of inventory reservation flow, inventory gets > reserved for the order based on the reservation algorithm (FIFO, LIFO etc). > Many times, the fulfilment cycle of the order is too long or due to some > unexpected circumstances, the order holds the inventory for a long time. In > such scenarios, inventory availability becomes one of the major bottlenecks > in fulfilling the other sales order and businesses often remains short > supplied against the demand. > > We can provide a feature (Create, Find and Edit supply allocation screen) to > allocate the available and any future supply judiciously amongst existing > customers orders by considering different factors like estimated delivery > dates, order priority, customer preference etc. > > Following are the details design notes for the same: > > An order in the approved status will be considered as ‘Eligible for > Allocation’. The proposed supply allocation planning will have the following > set of features: > > *Create Allocation Plan:* > The authorized user will be able to initiate the process by setting the > desired product. > > *View/Edit Allocation Plan:* > 1) The system would search and list all the order lines which are eligible > for allocation for that particular product. > 2) The user can filter and sort the orders by various parameters like Sale > Channel, Customer, Order Id, Estimated Ship Date etc. > 3) The user can then prioritize the order by moving up or down the given > order in the priority ranking. Higher is the order in display result list, > higher will be the priority it would get during reservations. > 4) The user can set the ‘Allocated Quantity’ against ordered quantity at > order item line level. > 5) Once the Allocation Plan is submitted, the system would auto-assign the > priority and set the allocated quantity for each of the submitted orders to > be honoured during order reservations at any point in time. > 7) Incoming shipments would be reserved by honouring the same allocation plan > during order promising cycle. > 8) After allocating supply as per the allocation plan, any excess stock > should be reserved based on the standard FIFO method. > 9) If any of the items of an order is not planned via the Allocation Plan, > then also it should be reserved based on default FIFO criteria. > 10) The allocation for all the sales orders should be allowed for revision > unless the Shipment Plan is created against them. > > *Find Allocation Plan:* > The authorized user can search allocation plan(s) with filters like Plan Id, > Order Id, Product Id, Plan Method, Status etc. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16627036#comment-16627036 ] Arun Patidar commented on OFBIZ-10518: -- [~deepak.nigam] For auto reserved, inventory will be allocated as same as item qty along with auto approve of Allocation Plan, correct? > Inventory (Supply) Allocation Planning > -- > > Key: OFBIZ-10518 > URL: https://issues.apache.org/jira/browse/OFBIZ-10518 > Project: OFBiz > Issue Type: New Feature > Components: order, product >Reporter: Deepak Nigam >Assignee: Deepak Nigam >Priority: Major > Fix For: Trunk > > Attachments: CreateAllocationPlan-Step1.png, > CreateAllocationPlan-Step2.png, CreateAllocationPlanEditMode-Step2.png, > EditAllocationPlan.png, FindAllocationPlan.png, OFBiz-10518.patch, > ViewAllocationPlan.png > > > In the current implementation of inventory reservation flow, inventory gets > reserved for the order based on the reservation algorithm (FIFO, LIFO etc). > Many times, the fulfilment cycle of the order is too long or due to some > unexpected circumstances, the order holds the inventory for a long time. In > such scenarios, inventory availability becomes one of the major bottlenecks > in fulfilling the other sales order and businesses often remains short > supplied against the demand. > > We can provide a feature (Create, Find and Edit supply allocation screen) to > allocate the available and any future supply judiciously amongst existing > customers orders by considering different factors like estimated delivery > dates, order priority, customer preference etc. > > Following are the details design notes for the same: > > An order in the approved status will be considered as ‘Eligible for > Allocation’. The proposed supply allocation planning will have the following > set of features: > > *Create Allocation Plan:* > The authorized user will be able to initiate the process by setting the > desired product. > > *View/Edit Allocation Plan:* > 1) The system would search and list all the order lines which are eligible > for allocation for that particular product. > 2) The user can filter and sort the orders by various parameters like Sale > Channel, Customer, Order Id, Estimated Ship Date etc. > 3) The user can then prioritize the order by moving up or down the given > order in the priority ranking. Higher is the order in display result list, > higher will be the priority it would get during reservations. > 4) The user can set the ‘Allocated Quantity’ against ordered quantity at > order item line level. > 5) Once the Allocation Plan is submitted, the system would auto-assign the > priority and set the allocated quantity for each of the submitted orders to > be honoured during order reservations at any point in time. > 7) Incoming shipments would be reserved by honouring the same allocation plan > during order promising cycle. > 8) After allocating supply as per the allocation plan, any excess stock > should be reserved based on the standard FIFO method. > 9) If any of the items of an order is not planned via the Allocation Plan, > then also it should be reserved based on default FIFO criteria. > 10) The allocation for all the sales orders should be allowed for revision > unless the Shipment Plan is created against them. > > *Find Allocation Plan:* > The authorized user can search allocation plan(s) with filters like Plan Id, > Order Id, Product Id, Plan Method, Status etc. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16626996#comment-16626996 ] Arun Patidar commented on OFBIZ-10518: -- [~deepak.nigam] , is it configurable to use Allocation or not? This will help to control additional load on DB if we do not want to entertain Allocation plan. > Inventory (Supply) Allocation Planning > -- > > Key: OFBIZ-10518 > URL: https://issues.apache.org/jira/browse/OFBIZ-10518 > Project: OFBiz > Issue Type: New Feature > Components: order, product >Reporter: Deepak Nigam >Assignee: Deepak Nigam >Priority: Major > Fix For: Trunk > > Attachments: CreateAllocationPlan-Step1.png, > CreateAllocationPlan-Step2.png, CreateAllocationPlanEditMode-Step2.png, > EditAllocationPlan.png, FindAllocationPlan.png, OFBiz-10518.patch, > ViewAllocationPlan.png > > > In the current implementation of inventory reservation flow, inventory gets > reserved for the order based on the reservation algorithm (FIFO, LIFO etc). > Many times, the fulfilment cycle of the order is too long or due to some > unexpected circumstances, the order holds the inventory for a long time. In > such scenarios, inventory availability becomes one of the major bottlenecks > in fulfilling the other sales order and businesses often remains short > supplied against the demand. > > We can provide a feature (Create, Find and Edit supply allocation screen) to > allocate the available and any future supply judiciously amongst existing > customers orders by considering different factors like estimated delivery > dates, order priority, customer preference etc. > > Following are the details design notes for the same: > > An order in the approved status will be considered as ‘Eligible for > Allocation’. The proposed supply allocation planning will have the following > set of features: > > *Create Allocation Plan:* > The authorized user will be able to initiate the process by setting the > desired product. > > *View/Edit Allocation Plan:* > 1) The system would search and list all the order lines which are eligible > for allocation for that particular product. > 2) The user can filter and sort the orders by various parameters like Sale > Channel, Customer, Order Id, Estimated Ship Date etc. > 3) The user can then prioritize the order by moving up or down the given > order in the priority ranking. Higher is the order in display result list, > higher will be the priority it would get during reservations. > 4) The user can set the ‘Allocated Quantity’ against ordered quantity at > order item line level. > 5) Once the Allocation Plan is submitted, the system would auto-assign the > priority and set the allocated quantity for each of the submitted orders to > be honoured during order reservations at any point in time. > 7) Incoming shipments would be reserved by honouring the same allocation plan > during order promising cycle. > 8) After allocating supply as per the allocation plan, any excess stock > should be reserved based on the standard FIFO method. > 9) If any of the items of an order is not planned via the Allocation Plan, > then also it should be reserved based on default FIFO criteria. > 10) The allocation for all the sales orders should be allowed for revision > unless the Shipment Plan is created against them. > > *Find Allocation Plan:* > The authorized user can search allocation plan(s) with filters like Plan Id, > Order Id, Product Id, Plan Method, Status etc. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-9746) updateContentAssoc does not return success/error message to the UI.
[ https://issues.apache.org/jira/browse/OFBIZ-9746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma reassigned OFBIZ-9746: Assignee: Aditya Sharma > updateContentAssoc does not return success/error message to the UI. > --- > > Key: OFBIZ-9746 > URL: https://issues.apache.org/jira/browse/OFBIZ-9746 > Project: OFBiz > Issue Type: Bug > Components: content >Affects Versions: Release Branch 16.11 >Reporter: Rohit Rai >Assignee: Aditya Sharma >Priority: Major > > 1. Go to, Content. > 2. Find contents using the find form and select any content from the list./ > 3. Click on the submenu "Association" > 4. In the Edit content association section, select a through date and click > on update > The date gets updated but the user is not presented with the success message > on the UI. > Here is the link to the form, > [https://demo-stable.ofbiz.apache.org/content/control/EditContentAssoc?contentId=BLOGROOT] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-9746) updateContentAssoc does not return success/error message to the UI.
[ https://issues.apache.org/jira/browse/OFBIZ-9746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16626968#comment-16626968 ] Aditya Sharma commented on OFBIZ-9746: -- For trunk and 17.12, the issue is resolved as the service has been converted to entity-auto from minilang under OFBIZ-9907. > updateContentAssoc does not return success/error message to the UI. > --- > > Key: OFBIZ-9746 > URL: https://issues.apache.org/jira/browse/OFBIZ-9746 > Project: OFBiz > Issue Type: Bug > Components: content >Affects Versions: Release Branch 16.11 >Reporter: Rohit Rai >Priority: Major > > 1. Go to, Content. > 2. Find contents using the find form and select any content from the list./ > 3. Click on the submenu "Association" > 4. In the Edit content association section, select a through date and click > on update > The date gets updated but the user is not presented with the success message > on the UI. > Here is the link to the form, > [https://demo-stable.ofbiz.apache.org/content/control/EditContentAssoc?contentId=BLOGROOT] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10579) Date filtered queries with caching should be restricted to cache
[ https://issues.apache.org/jira/browse/OFBIZ-10579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16626963#comment-16626963 ] Deepak Nigam commented on OFBIZ-10579: -- +1. Patch looks good to me also. > Date filtered queries with caching should be restricted to cache > > > Key: OFBIZ-10579 > URL: https://issues.apache.org/jira/browse/OFBIZ-10579 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Affects Versions: Upcoming Branch >Reporter: Suraj Khurana >Assignee: Suraj Khurana >Priority: Major > Attachments: OFBIZ-10579.patch > > > As per discussion on Dev ML > https://markmail.org/thread/3qnkihmsyhly3lsg -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-9746) updateContentAssoc does not return success/error message to the UI.
[ https://issues.apache.org/jira/browse/OFBIZ-9746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16626925#comment-16626925 ] Jacques Le Roux commented on OFBIZ-9746: Thanks for the update Aditiya > updateContentAssoc does not return success/error message to the UI. > --- > > Key: OFBIZ-9746 > URL: https://issues.apache.org/jira/browse/OFBIZ-9746 > Project: OFBiz > Issue Type: Bug > Components: content >Affects Versions: Release Branch 16.11 >Reporter: Rohit Rai >Priority: Major > > 1. Go to, Content. > 2. Find contents using the find form and select any content from the list./ > 3. Click on the submenu "Association" > 4. In the Edit content association section, select a through date and click > on update > The date gets updated but the user is not presented with the success message > on the UI. > Here is the link to the form, > [https://demo-stable.ofbiz.apache.org/content/control/EditContentAssoc?contentId=BLOGROOT] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
