[jira] [Commented] (OFBIZ-10577) New Feature: Inventory Cycle Count
[ https://issues.apache.org/jira/browse/OFBIZ-10577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609879#comment-17609879 ] Yashwant Dhakad commented on OFBIZ-10577: - Hi [~jleroux] I have updated this [Pull Request|https://github.com/apache/ofbiz-framework/pull/322] with the latest trunk and it is ready for merge. Please review and let me know if you found any improvements. > 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, product >Affects Versions: Trunk, Upcoming Branch >Reporter: Yashwant Dhakad >Assignee: Yashwant Dhakad >Priority: Major > Labels: audit, inventory > Attachments: Checkbox Issue.png, FindSessionIssue.png, > InventoryItemLookup.png, ItemSubSeqId.png, Menu Error.png, Menu Error.png, > OFBIZ-10577-Database-Changes.patch, OFBIZ-10577.patch, Ui Issue.png, Ui > Issue.png, screenshot-1-find-session.png, screenshot-2-pending-locations.png, > screenshot-3-add-location-to-session.png, > screenshot-4-list-of-review-session.png, > screenshot-5-review-session-detail.png, screenshot-6-accept-session.png, > screenshot-7-complete-review.png, screenshot-8-report-screen.png > > > *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
[jira] [Commented] (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:comment-tabpanel=17432580#comment-17432580 ] Yashwant Dhakad commented on OFBIZ-9475: Do we need any other changes in this patch or we can push these changes? I think we can create sub tickets for duplicate code cleanup for serialize and non-serialize inventory. > 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: product >Affects Versions: Trunk >Reporter: Deepak Dixit >Assignee: Yashwant Dhakad >Priority: Major > Attachments: OFBIZ-9475.patch, 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
[jira] [Commented] (OFBIZ-10577) New Feature: Inventory Cycle Count
[ https://issues.apache.org/jira/browse/OFBIZ-10577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17432553#comment-17432553 ] Yashwant Dhakad commented on OFBIZ-10577: - Hi [~pawan] I have added support to create status history for InventoryCount and also removed my old PR and created new PR because some merge commits exist in my previous PR, can you please close the old Pull Request and use this new Pull Request? > 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, product >Affects Versions: Trunk >Reporter: Yashwant Dhakad >Assignee: Yashwant Dhakad >Priority: Major > Labels: audit, inventory > Attachments: Checkbox Issue.png, FindSessionIssue.png, > InventoryItemLookup.png, ItemSubSeqId.png, Menu Error.png, Menu Error.png, > OFBIZ-10577-Database-Changes.patch, OFBIZ-10577.patch, Ui Issue.png, Ui > Issue.png, screenshot-1-find-session.png, screenshot-2-pending-locations.png, > screenshot-3-add-location-to-session.png, > screenshot-4-list-of-review-session.png, > screenshot-5-review-session-detail.png, screenshot-6-accept-session.png, > screenshot-7-complete-review.png, screenshot-8-report-screen.png > > > *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 >
[jira] [Commented] (OFBIZ-12282) Create return is not working on demo trunk
[ https://issues.apache.org/jira/browse/OFBIZ-12282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17422747#comment-17422747 ] Yashwant Dhakad commented on OFBIZ-12282: - Thank you [~jleroux] > Create return is not working on demo trunk > -- > > Key: OFBIZ-12282 > URL: https://issues.apache.org/jira/browse/OFBIZ-12282 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Trunk >Reporter: Yashwant Dhakad >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Upcoming Branch > > Attachments: errorinreturn.png, returnscreen.png > > > For purchase order when we create a return then getting the Following Errors: > Error:Service invocation error on row (0): > org.codehaus.groovy.runtime.InvokerInvocationException: > org.apache.ofbiz.service.GenericServiceException: Error running Groovy method > [createReturnHeader] in Groovy file > [component://order/groovyScripts/order/OrderReturnServices.groovy]: (Cannot > get property 'useInvoiceIdForReturns' on null object)Service invocation > error on row (1): org.codehaus.groovy.runtime.InvokerInvocationException: > org.apache.ofbiz.service.GenericServiceException: Error running Groovy method > [createReturnHeader] in Groovy file > [component://order/groovyScripts/order/OrderReturnServices.groovy]: > (org.apache.ofbiz.service.GenericServiceException: Service > [getPartyAccountingPreferences] Failed (null))Service invocation error > on row (2): org.codehaus.groovy.runtime.InvokerInvocationException: > org.apache.ofbiz.service.GenericServiceException: Error running Groovy method > [createReturnHeader] in Groovy file > [component://order/groovyScripts/order/OrderReturnServices.groovy]: > (org.apache.ofbiz.service.GenericServiceException: Service > [getPartyAccountingPreferences] Failed (null))Service invocation error > on row (3): org.codehaus.groovy.runtime.InvokerInvocationException: > org.apache.ofbiz.service.GenericServiceException: Error running Groovy method > [createReturnHeader] in Groovy file > [component://order/groovyScripts/order/OrderReturnServices.groovy]: > (org.apache.ofbiz.service.GenericServiceException: Service > [getPartyAccountingPreferences] Failed (null)) > Steps to reproduce: > 1. Create PO and receive it and PO is automatically completed. > 2. Click on Create Return button in the order actions section. > 3. Navigated to create return screen. > 4. Select the items and click on Return Selected Item(s) button. > 5. Getting the above error. > Expected: The return should be created. > Actual: Getting error message. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-12282) Create return is not working on demo trunk
[ https://issues.apache.org/jira/browse/OFBIZ-12282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad updated OFBIZ-12282: Attachment: returnscreen.png errorinreturn.png > Create return is not working on demo trunk > -- > > Key: OFBIZ-12282 > URL: https://issues.apache.org/jira/browse/OFBIZ-12282 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Trunk >Reporter: Yashwant Dhakad >Priority: Minor > Attachments: errorinreturn.png, returnscreen.png > > > For purchase order when we create a return then getting the Following Errors: > Error:Service invocation error on row (0): > org.codehaus.groovy.runtime.InvokerInvocationException: > org.apache.ofbiz.service.GenericServiceException: Error running Groovy method > [createReturnHeader] in Groovy file > [component://order/groovyScripts/order/OrderReturnServices.groovy]: (Cannot > get property 'useInvoiceIdForReturns' on null object)Service invocation > error on row (1): org.codehaus.groovy.runtime.InvokerInvocationException: > org.apache.ofbiz.service.GenericServiceException: Error running Groovy method > [createReturnHeader] in Groovy file > [component://order/groovyScripts/order/OrderReturnServices.groovy]: > (org.apache.ofbiz.service.GenericServiceException: Service > [getPartyAccountingPreferences] Failed (null))Service invocation error > on row (2): org.codehaus.groovy.runtime.InvokerInvocationException: > org.apache.ofbiz.service.GenericServiceException: Error running Groovy method > [createReturnHeader] in Groovy file > [component://order/groovyScripts/order/OrderReturnServices.groovy]: > (org.apache.ofbiz.service.GenericServiceException: Service > [getPartyAccountingPreferences] Failed (null))Service invocation error > on row (3): org.codehaus.groovy.runtime.InvokerInvocationException: > org.apache.ofbiz.service.GenericServiceException: Error running Groovy method > [createReturnHeader] in Groovy file > [component://order/groovyScripts/order/OrderReturnServices.groovy]: > (org.apache.ofbiz.service.GenericServiceException: Service > [getPartyAccountingPreferences] Failed (null)) > Steps to reproduce: > 1. Create PO and receive it and PO is automatically completed. > 2. Click on Create Return button in the order actions section. > 3. Navigated to create return screen. > 4. Select the items and click on Return Selected Item(s) button. > 5. Getting the above error. > Expected: The return should be created. > Actual: Getting error message. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OFBIZ-12282) Create return is not working on demo trunk
Yashwant Dhakad created OFBIZ-12282: --- Summary: Create return is not working on demo trunk Key: OFBIZ-12282 URL: https://issues.apache.org/jira/browse/OFBIZ-12282 Project: OFBiz Issue Type: Bug Components: order Affects Versions: Trunk Reporter: Yashwant Dhakad For purchase order when we create a return then getting the Following Errors: Error:Service invocation error on row (0): org.codehaus.groovy.runtime.InvokerInvocationException: org.apache.ofbiz.service.GenericServiceException: Error running Groovy method [createReturnHeader] in Groovy file [component://order/groovyScripts/order/OrderReturnServices.groovy]: (Cannot get property 'useInvoiceIdForReturns' on null object)Service invocation error on row (1): org.codehaus.groovy.runtime.InvokerInvocationException: org.apache.ofbiz.service.GenericServiceException: Error running Groovy method [createReturnHeader] in Groovy file [component://order/groovyScripts/order/OrderReturnServices.groovy]: (org.apache.ofbiz.service.GenericServiceException: Service [getPartyAccountingPreferences] Failed (null))Service invocation error on row (2): org.codehaus.groovy.runtime.InvokerInvocationException: org.apache.ofbiz.service.GenericServiceException: Error running Groovy method [createReturnHeader] in Groovy file [component://order/groovyScripts/order/OrderReturnServices.groovy]: (org.apache.ofbiz.service.GenericServiceException: Service [getPartyAccountingPreferences] Failed (null))Service invocation error on row (3): org.codehaus.groovy.runtime.InvokerInvocationException: org.apache.ofbiz.service.GenericServiceException: Error running Groovy method [createReturnHeader] in Groovy file [component://order/groovyScripts/order/OrderReturnServices.groovy]: (org.apache.ofbiz.service.GenericServiceException: Service [getPartyAccountingPreferences] Failed (null)) Steps to reproduce: 1. Create PO and receive it and PO is automatically completed. 2. Click on Create Return button in the order actions section. 3. Navigated to create return screen. 4. Select the items and click on Return Selected Item(s) button. 5. Getting the above error. Expected: The return should be created. Actual: Getting error message. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11855) Convert RoutingServices.xml mini-lang to groovy
[ https://issues.apache.org/jira/browse/OFBIZ-11855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17318844#comment-17318844 ] Yashwant Dhakad commented on OFBIZ-11855: - Yes, I have removed the link for the PR. > Convert RoutingServices.xml mini-lang to groovy > --- > > Key: OFBIZ-11855 > URL: https://issues.apache.org/jira/browse/OFBIZ-11855 > Project: OFBiz > Issue Type: Sub-task >Reporter: Wiebke Pätzold >Assignee: Yashwant Dhakad >Priority: Minor > Attachments: OFBIZ-11855.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11855) Convert RoutingServices.xml mini-lang to groovy
[ https://issues.apache.org/jira/browse/OFBIZ-11855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17318440#comment-17318440 ] Yashwant Dhakad commented on OFBIZ-11855: - I have attached the patch because I am having some issues with my fork repositoy. > Convert RoutingServices.xml mini-lang to groovy > --- > > Key: OFBIZ-11855 > URL: https://issues.apache.org/jira/browse/OFBIZ-11855 > Project: OFBiz > Issue Type: Sub-task >Reporter: Wiebke Pätzold >Assignee: Yashwant Dhakad >Priority: Minor > Attachments: OFBIZ-11855.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11855) Convert RoutingServices.xml mini-lang to groovy
[ https://issues.apache.org/jira/browse/OFBIZ-11855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad updated OFBIZ-11855: Attachment: OFBIZ-11855.patch > Convert RoutingServices.xml mini-lang to groovy > --- > > Key: OFBIZ-11855 > URL: https://issues.apache.org/jira/browse/OFBIZ-11855 > Project: OFBiz > Issue Type: Sub-task >Reporter: Wiebke Pätzold >Assignee: Yashwant Dhakad >Priority: Minor > Attachments: OFBIZ-11855.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11855) Convert RoutingServices.xml mini-lang to groovy
[ https://issues.apache.org/jira/browse/OFBIZ-11855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17268371#comment-17268371 ] Yashwant Dhakad commented on OFBIZ-11855: - Yes, it is still open we can merge them. > Convert RoutingServices.xml mini-lang to groovy > --- > > Key: OFBIZ-11855 > URL: https://issues.apache.org/jira/browse/OFBIZ-11855 > Project: OFBiz > Issue Type: Sub-task >Reporter: Wiebke Pätzold >Assignee: Yashwant Dhakad >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-10577) New Feature: Inventory Cycle Count
[ https://issues.apache.org/jira/browse/OFBIZ-10577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17255059#comment-17255059 ] Yashwant Dhakad commented on OFBIZ-10577: - I have updated my PR with the latest codebase and resolved all the conflicts. > 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, product >Affects Versions: Trunk >Reporter: Yashwant Dhakad >Assignee: Yashwant Dhakad >Priority: Major > Labels: audit, inventory > Attachments: Checkbox Issue.png, FindSessionIssue.png, > InventoryItemLookup.png, ItemSubSeqId.png, Menu Error.png, Menu Error.png, > OFBIZ-10577-Database-Changes.patch, OFBIZ-10577.patch, Ui Issue.png, Ui > Issue.png, screenshot-1-find-session.png, screenshot-2-pending-locations.png, > screenshot-3-add-location-to-session.png, > screenshot-4-list-of-review-session.png, > screenshot-5-review-session-detail.png, screenshot-6-accept-session.png, > screenshot-7-complete-review.png, screenshot-8-report-screen.png > > > *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 > ***Extended entity:* > *FacilityLocation* > locked >
[jira] [Assigned] (OFBIZ-12054) Solution Design - OFBIZ-12053: Promising against Future Supply
[ https://issues.apache.org/jira/browse/OFBIZ-12054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad reassigned OFBIZ-12054: --- Assignee: Yashwant Dhakad > Solution Design - OFBIZ-12053: Promising against Future Supply > -- > > Key: OFBIZ-12054 > URL: https://issues.apache.org/jira/browse/OFBIZ-12054 > Project: OFBiz > Issue Type: Task > Components: order >Reporter: Swapnil Shah >Assignee: Yashwant Dhakad >Priority: Major > Fix For: Upcoming Branch > > > *Solution Design* > In search of answers for few basic questions around promising, here is the > list of few possible design options to explore and build on further: > * *How much to Promise* > Before making any systemic or manual promise its important to know how much > is remaining to be promised for any given order(item). It could be determined > as follows: > ** Let system first promise out of on hand inventory using its current > reservation mechanism. > ** Post inventory reservation, if Order item is still found backordered (BO) > i.e. couldn't get any promise from Inventory then it could easily be adjudged > how much more need to be promised yet based on summing up > ORDER_ITEM_SHIP_GRP_INV_RES(OISGIR).QUANTIT_NOT_AVAILABLE for given order item > * *How much is 'Promisable' or 'Available to Promise' (ATP) against supply:* > Before systemic or manual promises against new demand/orders, It must be > known how much is left or available to be promised. To begin with, all the > future supply scheduled to come into the system from vendors or suppliers are > usually gauged through Advance Shipment Notifications (ASNs) which can be > expressed via SHIPMENT model in OFBiz. Assuming this to be true, here are few > possible options: > ** SHIPMENT with dedicated SHIPMENT_TYPE either as 'INCOMING_SHIPMENT' or > 'PURCHASE_SHIPMENT' can be recognized as scheduled inbound supply on a > certain ESTIMATED_ARRIVAL_DATE (EAD) > ** SHIPMENT_ITEM can express the Product/SKU wise details of supply in terms > of QUANTITY > ** *_Extend SHIPMENT_ITEM (SI)_* _with new field_ *_'AVAILABLE_TO_PROMISE' > (ATP)_* _to now maintain the remaining qty left to be promised at product > level within a given shipment_ > ** All the promises to be made for any open demand/order can be based off > SI.ATP. At the same time, all the promises made based on it needs to keep on > reducing it so as to reflect correct supply snapshot (very much in line with > ATP on Inventory Item in OFBiz) > * *How to Promise* > There can be many ways to promise the demand against supply. Few of the > automated or manual ways that can be honored (in line with how on hand > Inventory is promised in OFBiz) could be based on following criteria: > ** *_FIFO_*: Order with earlier Estimated Ship Date (ESD) could get higher > precedence in getting supply promised than that of later ESDs. In case of > missing ESD, Order Date can be referred as fall back option > ** _*Order Priority*_: Order with higher priority takes precedence in > getting supply promised than that of lower priority order. > ** _*Order Priority + FIFO*_ : Order with higher priority gets precedence > but within same priority orders, FIFO based rules can be applied > ** _*Fair Share*_: In this manual approach control could be more in hand of > users to determine and set how much can be promised. It could come handy when > sales reps or merchandisers have their own set of custom rules to be applied > rather than having system making promises in automated fashion. > Depending upon the any of the preferred technique, system needs to keep > pegging the 'Promisable Supply' against 'Yet to be promised demand'. One of > the possible ways to maintain and capture this pegging could be: > * Add new table _*ORDER_ITEM_SHIP_GRP_SHIPMENT_RES (OISGSR)*_ with > ** ORDER_ID (PK) > ** SHIP_GROUP_SEQ_ID (PK) > ** ORDER_ITEM_SEQ_ID (PK) > ** SHIPMENT_ID (PK) > ** SHIPMENT_ITEM_SEQ_ID (PK) > ** RESERVE_ORDER_ENUM_ID (to capture the basis for promising i.e. FIFO, > PRIORITY, FAIR_SHARE etc.) > ** QUANTITY (Ordered Qty) > ** QUANTITY_NOT_AVAILABLE (Un-promised Qty left if any) > ** PROMISED_DATETIME (promised date based on S.EAD) > ** PRIORITY (optional - to adjudge the shipment to be used first if same > order item gets promised from multiple shipments. Lower the number, higher > the priority) > ** Standard 4 timestamps > * All the promises for an ordered item against future supply in (the form of > inbound shipment) could be made based off SI.ATP > * Any promise made from Inbound shipments could keep getting captured > through above table and get reflected on SI.ATP unless it gets completely > exhausted i.e. goes down to ZERO. > * *Where to
[jira] [Assigned] (OFBIZ-12053) Promising against Future Supply of Inventory
[ https://issues.apache.org/jira/browse/OFBIZ-12053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad reassigned OFBIZ-12053: --- Assignee: Yashwant Dhakad > Promising against Future Supply of Inventory > > > Key: OFBIZ-12053 > URL: https://issues.apache.org/jira/browse/OFBIZ-12053 > Project: OFBiz > Issue Type: New Feature > Components: order >Reporter: Swapnil Shah >Assignee: Yashwant Dhakad >Priority: Major > Fix For: Upcoming Branch > > > *Requirement Elicitation:* > Promising delivery of any product or SKU to a customer out of On Hand > inventory against any firm or forecasted demand arising in the form of Sales > Order in the system has been now been a established practice and well > supported to a great extent within Ofbiz. > However, there is a strong need felt to have a solution that can address the > problem in making promises to customer for any product or SKU out of any > future or expected supply of inventory through inbound shipments from vendors > or suppliers. There may be different natures of demand for which such kind of > solution capability can serve well like: > * Demand from orders which couldn't get any commitment out of on hand > inventory and thus are often termed as Backordered (BO) > * Demand from Advanced or Pre-booked orders while launching new product line > as inventory is yet to arrive at fulfilment locations > * Demand from booked orders against limited edition version of existing > product line as inventory is yet to arrive at fulfilment locations > * Demand from sample lines booked during pre-launch event > * and so on... > While attempting to promise customer from future supply for a product/SKU > then from solutioning stand point, anything that can try to address the > following questions should be a good start to begin with: > * How to promise (i.e., what should be the rules or constraints or basis for > promising order) > * How much to promise (i.e. how many units out of ordered units need to be > promised for any given order) > * How much is Available to Promise (i.e. how many promisable units available > from different sources or inbound shipments for a given product/SKU) > * Where to Promise from (i.e. from which source or inbound shipment the > order can be promised) > * When to promise (i.e. on what date a given order can be promised) > Let's use this space to add on to it with more such real time use scenarios > or questions that needs the right answer. > We could try writing the design to solve for it in a separate linked ticket > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11855) Convert RoutingServices.xml mini-lang to groovy
[ https://issues.apache.org/jira/browse/OFBIZ-11855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17202580#comment-17202580 ] Yashwant Dhakad commented on OFBIZ-11855: - I have completed the migration from mini lang to groovy for both (getProductRouting, getRoutingTaskAssocs) services. > Convert RoutingServices.xml mini-lang to groovy > --- > > Key: OFBIZ-11855 > URL: https://issues.apache.org/jira/browse/OFBIZ-11855 > Project: OFBiz > Issue Type: Sub-task >Reporter: Wiebke Pätzold >Assignee: Yashwant Dhakad >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (OFBIZ-11855) Convert RoutingServices.xml mini-lang to groovy
[ https://issues.apache.org/jira/browse/OFBIZ-11855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad reassigned OFBIZ-11855: --- Assignee: Yashwant Dhakad (was: Wiebke Pätzold) > Convert RoutingServices.xml mini-lang to groovy > --- > > Key: OFBIZ-11855 > URL: https://issues.apache.org/jira/browse/OFBIZ-11855 > Project: OFBiz > Issue Type: Sub-task >Reporter: Wiebke Pätzold >Assignee: Yashwant Dhakad >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (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:comment-tabpanel=17164789#comment-17164789 ] Yashwant Dhakad commented on OFBIZ-9475: Hi Deepak, Any update on this? If we commit this then I will start on duplicate code cleanup work. > 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: product >Affects Versions: Trunk >Reporter: Deepak Dixit >Assignee: Yashwant Dhakad >Priority: Major > Attachments: OFBIZ-9475.patch, 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
[jira] [Closed] (OFBIZ-11914) Getting Error in receiving PO
[ https://issues.apache.org/jira/browse/OFBIZ-11914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad closed OFBIZ-11914. --- Resolution: Fixed > Getting Error in receiving PO > - > > Key: OFBIZ-11914 > URL: https://issues.apache.org/jira/browse/OFBIZ-11914 > Project: OFBiz > Issue Type: Bug > Components: hhfacility >Affects Versions: Trunk >Reporter: Yashwant Dhakad >Assignee: Yashwant Dhakad >Priority: Major > Attachments: ReceivingError.png > > > During receiving when we add quantity accepted and click on Receive selected > product and it shows error. > Steps to reproduce: > # Create PO and approve. > # Click on the receive button in the action section on the view order screen. > # User navigated to receive screen select the shipment and click on Receive > selected shipment. > # The user navigated to the receiving screen. > # Enter the quantity accepted and click on receive selected products. > # Error page render. > Expected: The product should be received and user should be navigated to the > shipment receipt screen. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11914) Getting Error in receiving PO
[ https://issues.apache.org/jira/browse/OFBIZ-11914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17164787#comment-17164787 ] Yashwant Dhakad commented on OFBIZ-11914: - This ticket is duplicate of [OFBIZ-11909|https://issues.apache.org/jira/browse/OFBIZ-11909] ticket, so closing this ticket. > Getting Error in receiving PO > - > > Key: OFBIZ-11914 > URL: https://issues.apache.org/jira/browse/OFBIZ-11914 > Project: OFBiz > Issue Type: Bug > Components: hhfacility >Affects Versions: Trunk >Reporter: Yashwant Dhakad >Assignee: Yashwant Dhakad >Priority: Major > Attachments: ReceivingError.png > > > During receiving when we add quantity accepted and click on Receive selected > product and it shows error. > Steps to reproduce: > # Create PO and approve. > # Click on the receive button in the action section on the view order screen. > # User navigated to receive screen select the shipment and click on Receive > selected shipment. > # The user navigated to the receiving screen. > # Enter the quantity accepted and click on receive selected products. > # Error page render. > Expected: The product should be received and user should be navigated to the > shipment receipt screen. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (OFBIZ-11912) Shipment is not created during receiving
[ https://issues.apache.org/jira/browse/OFBIZ-11912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad updated OFBIZ-11912: Comment: was deleted (was: Closing this ticket as we have found duplicate tickets.) > Shipment is not created during receiving > > > Key: OFBIZ-11912 > URL: https://issues.apache.org/jira/browse/OFBIZ-11912 > Project: OFBiz > Issue Type: Bug > Components: hhfacility >Affects Versions: Trunk >Reporter: Yashwant Dhakad >Assignee: Pawan Verma >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-11912.patch, POShipmentError.png > > > Purchase shipment is not created during receiving. In demo-stable it is > working fine so it breaks in the trunk. > Here are the steps to regenerate: > # Create the Purchase Order. > # Approve the Purchase Order. > # Click on the Receive button in Action section on the order view screen. > # The user navigated to receive screen and getting error. > Expected result: User navigated to receive screen and Purchase shipment > should be visible on the Receive screen. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11912) Shipment is not created during receiving
[ https://issues.apache.org/jira/browse/OFBIZ-11912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17164783#comment-17164783 ] Yashwant Dhakad commented on OFBIZ-11912: - Closing this ticket as we have found duplicate tickets. > Shipment is not created during receiving > > > Key: OFBIZ-11912 > URL: https://issues.apache.org/jira/browse/OFBIZ-11912 > Project: OFBiz > Issue Type: Bug > Components: hhfacility >Affects Versions: Trunk >Reporter: Yashwant Dhakad >Assignee: Pawan Verma >Priority: Minor > Attachments: OFBIZ-11912.patch, POShipmentError.png > > > Purchase shipment is not created during receiving. In demo-stable it is > working fine so it breaks in the trunk. > Here are the steps to regenerate: > # Create the Purchase Order. > # Approve the Purchase Order. > # Click on the Receive button in Action section on the order view screen. > # The user navigated to receive screen and getting error. > Expected result: User navigated to receive screen and Purchase shipment > should be visible on the Receive screen. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11912) Shipment is not created during receiving
[ https://issues.apache.org/jira/browse/OFBIZ-11912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17164775#comment-17164775 ] Yashwant Dhakad commented on OFBIZ-11912: - I dig into this issue and found some typo when it was converted from XML to groovy. I have uploaded the patch for this issue. > Shipment is not created during receiving > > > Key: OFBIZ-11912 > URL: https://issues.apache.org/jira/browse/OFBIZ-11912 > Project: OFBiz > Issue Type: Bug > Components: hhfacility >Affects Versions: Trunk >Reporter: Yashwant Dhakad >Assignee: Yashwant Dhakad >Priority: Minor > Attachments: OFBIZ-11912.patch, POShipmentError.png > > > Purchase shipment is not created during receiving. In demo-stable it is > working fine so it breaks in the trunk. > Here are the steps to regenerate: > # Create the Purchase Order. > # Approve the Purchase Order. > # Click on the Receive button in Action section on the order view screen. > # The user navigated to receive screen and getting error. > Expected result: User navigated to receive screen and Purchase shipment > should be visible on the Receive screen. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11912) Shipment is not created during receiving
[ https://issues.apache.org/jira/browse/OFBIZ-11912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad updated OFBIZ-11912: Attachment: OFBIZ-11912.patch > Shipment is not created during receiving > > > Key: OFBIZ-11912 > URL: https://issues.apache.org/jira/browse/OFBIZ-11912 > Project: OFBiz > Issue Type: Bug > Components: hhfacility >Affects Versions: Trunk >Reporter: Yashwant Dhakad >Assignee: Yashwant Dhakad >Priority: Minor > Attachments: OFBIZ-11912.patch, POShipmentError.png > > > Purchase shipment is not created during receiving. In demo-stable it is > working fine so it breaks in the trunk. > Here are the steps to regenerate: > # Create the Purchase Order. > # Approve the Purchase Order. > # Click on the Receive button in Action section on the order view screen. > # The user navigated to receive screen and getting error. > Expected result: User navigated to receive screen and Purchase shipment > should be visible on the Receive screen. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OFBIZ-11914) Getting Error in receiving PO
Yashwant Dhakad created OFBIZ-11914: --- Summary: Getting Error in receiving PO Key: OFBIZ-11914 URL: https://issues.apache.org/jira/browse/OFBIZ-11914 Project: OFBiz Issue Type: Bug Components: hhfacility Affects Versions: Trunk Reporter: Yashwant Dhakad Attachments: ReceivingError.png During receiving when we add quantity accepted and click on Receive selected product and it shows error. Steps to reproduce: # Create PO and approve. # Click on the receive button in the action section on the view order screen. # User navigated to receive screen select the shipment and click on Receive selected shipment. # The user navigated to the receiving screen. # Enter the quantity accepted and click on receive selected products. # Error page render. Expected: The product should be received and user should be navigated to the shipment receipt screen. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (OFBIZ-11914) Getting Error in receiving PO
[ https://issues.apache.org/jira/browse/OFBIZ-11914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad reassigned OFBIZ-11914: --- Assignee: Yashwant Dhakad > Getting Error in receiving PO > - > > Key: OFBIZ-11914 > URL: https://issues.apache.org/jira/browse/OFBIZ-11914 > Project: OFBiz > Issue Type: Bug > Components: hhfacility >Affects Versions: Trunk >Reporter: Yashwant Dhakad >Assignee: Yashwant Dhakad >Priority: Major > Attachments: ReceivingError.png > > > During receiving when we add quantity accepted and click on Receive selected > product and it shows error. > Steps to reproduce: > # Create PO and approve. > # Click on the receive button in the action section on the view order screen. > # User navigated to receive screen select the shipment and click on Receive > selected shipment. > # The user navigated to the receiving screen. > # Enter the quantity accepted and click on receive selected products. > # Error page render. > Expected: The product should be received and user should be navigated to the > shipment receipt screen. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11912) Shipment is not created during receiving
[ https://issues.apache.org/jira/browse/OFBIZ-11912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad updated OFBIZ-11912: Attachment: POShipmentError.png > Shipment is not created during receiving > > > Key: OFBIZ-11912 > URL: https://issues.apache.org/jira/browse/OFBIZ-11912 > Project: OFBiz > Issue Type: Bug > Components: hhfacility >Affects Versions: Trunk >Reporter: Yashwant Dhakad >Assignee: Yashwant Dhakad >Priority: Minor > Attachments: POShipmentError.png > > > Purchase shipment is not created during receiving. In demo-stable it is > working fine so it breaks in the trunk. > Here are the steps to regenerate: > # Create the Purchase Order. > # Approve the Purchase Order. > # Click on the Receive button in Action section on the order view screen. > # The user navigated to receive screen and getting error. > Expected result: User navigated to receive screen and Purchase shipment > should be visible on the Receive screen. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OFBIZ-11912) Shipment is not created during receiving
Yashwant Dhakad created OFBIZ-11912: --- Summary: Shipment is not created during receiving Key: OFBIZ-11912 URL: https://issues.apache.org/jira/browse/OFBIZ-11912 Project: OFBiz Issue Type: Bug Components: hhfacility Affects Versions: Trunk Reporter: Yashwant Dhakad Purchase shipment is not created during receiving. In demo-stable it is working fine so it breaks in the trunk. Here are the steps to regenerate: # Create the Purchase Order. # Approve the Purchase Order. # Click on the Receive button in Action section on the order view screen. # The user navigated to receive screen and getting error. Expected result: User navigated to receive screen and Purchase shipment should be visible on the Receive screen. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (OFBIZ-11912) Shipment is not created during receiving
[ https://issues.apache.org/jira/browse/OFBIZ-11912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad reassigned OFBIZ-11912: --- Assignee: Yashwant Dhakad > Shipment is not created during receiving > > > Key: OFBIZ-11912 > URL: https://issues.apache.org/jira/browse/OFBIZ-11912 > Project: OFBiz > Issue Type: Bug > Components: hhfacility >Affects Versions: Trunk >Reporter: Yashwant Dhakad >Assignee: Yashwant Dhakad >Priority: Minor > > Purchase shipment is not created during receiving. In demo-stable it is > working fine so it breaks in the trunk. > Here are the steps to regenerate: > # Create the Purchase Order. > # Approve the Purchase Order. > # Click on the Receive button in Action section on the order view screen. > # The user navigated to receive screen and getting error. > Expected result: User navigated to receive screen and Purchase shipment > should be visible on the Receive screen. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-10577) New Feature: Inventory Cycle Count
[ https://issues.apache.org/jira/browse/OFBIZ-10577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17146954#comment-17146954 ] Yashwant Dhakad commented on OFBIZ-10577: - Hi [~pawan], I have done all the suggested changes. I see that the checkbox issue is at the framework level It also broken on other screens as well so you can create a new ticket for that. Apart from I agree with you for the status history improvement and we need to add one more entity for status history so can you create a new ticket for this as well? And I will take care of them in a new ticket. > 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, product >Affects Versions: Trunk >Reporter: Yashwant Dhakad >Assignee: Yashwant Dhakad >Priority: Major > Labels: audit, inventory > Attachments: Checkbox Issue.png, FindSessionIssue.png, > InventoryItemLookup.png, ItemSubSeqId.png, Menu Error.png, Menu Error.png, > OFBIZ-10577-Database-Changes.patch, OFBIZ-10577.patch, Ui Issue.png, Ui > Issue.png, screenshot-1-find-session.png, screenshot-2-pending-locations.png, > screenshot-3-add-location-to-session.png, > screenshot-4-list-of-review-session.png, > screenshot-5-review-session-detail.png, screenshot-6-accept-session.png, > screenshot-7-complete-review.png, screenshot-8-report-screen.png > > > *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 >
[jira] [Commented] (OFBIZ-10577) New Feature: Inventory Cycle Count
[ https://issues.apache.org/jira/browse/OFBIZ-10577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17146799#comment-17146799 ] Yashwant Dhakad commented on OFBIZ-10577: - Thank you Pawan for the feedback, I will change these and provide you the updated PR. > 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, product >Affects Versions: Trunk >Reporter: Yashwant Dhakad >Assignee: Yashwant Dhakad >Priority: Major > Labels: audit, inventory > Attachments: Checkbox Issue.png, FindSessionIssue.png, > InventoryItemLookup.png, ItemSubSeqId.png, Menu Error.png, Menu Error.png, > OFBIZ-10577-Database-Changes.patch, OFBIZ-10577.patch, Ui Issue.png, Ui > Issue.png, screenshot-1-find-session.png, screenshot-2-pending-locations.png, > screenshot-3-add-location-to-session.png, > screenshot-4-list-of-review-session.png, > screenshot-5-review-session-detail.png, screenshot-6-accept-session.png, > screenshot-7-complete-review.png, screenshot-8-report-screen.png > > > *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 > ***Extended entity:* > *FacilityLocation* > locked
[jira] [Commented] (OFBIZ-11395) Convert ProductionRunServices.xml file from mini-lang to groovy DSL
[ https://issues.apache.org/jira/browse/OFBIZ-11395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17069425#comment-17069425 ] Yashwant Dhakad commented on OFBIZ-11395: - I verified and fixed all the issues identified during the verification and all the inventory issuances for production run are working fine. Please have a look and let me know if you still found any issue. > Convert ProductionRunServices.xml file from mini-lang to groovy DSL > --- > > Key: OFBIZ-11395 > URL: https://issues.apache.org/jira/browse/OFBIZ-11395 > Project: OFBiz > Issue Type: Sub-task > Components: manufacturing >Affects Versions: Trunk >Reporter: Yashwant Dhakad >Assignee: Yashwant Dhakad >Priority: Minor > Labels: groovy, mini-lang > Attachments: OFBIZ-11395.patch > > > In this ticket, I have converted createProductionRunPartyAssign, > createProductionRunAssoc, issueProductionRunTask, > issueProductionRunTaskComponent, issueProductionRunTaskComponentInline and > issueInventoryItemToWorkEffort services into groovy DSL. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11395) Convert ProductionRunServices.xml file from mini-lang to groovy DSL
[ https://issues.apache.org/jira/browse/OFBIZ-11395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad updated OFBIZ-11395: Attachment: OFBIZ-11395.patch > Convert ProductionRunServices.xml file from mini-lang to groovy DSL > --- > > Key: OFBIZ-11395 > URL: https://issues.apache.org/jira/browse/OFBIZ-11395 > Project: OFBiz > Issue Type: Sub-task > Components: manufacturing >Affects Versions: Trunk >Reporter: Yashwant Dhakad >Assignee: Yashwant Dhakad >Priority: Minor > Labels: groovy, mini-lang > Attachments: OFBIZ-11395.patch > > > In this ticket, I have converted createProductionRunPartyAssign, > createProductionRunAssoc, issueProductionRunTask, > issueProductionRunTaskComponent, issueProductionRunTaskComponentInline and > issueInventoryItemToWorkEffort services into groovy DSL. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11395) Convert ProductionRunServices.xml file from mini-lang to groovy DSL
[ https://issues.apache.org/jira/browse/OFBIZ-11395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad updated OFBIZ-11395: Attachment: (was: OFBIZ-11395.patch) > Convert ProductionRunServices.xml file from mini-lang to groovy DSL > --- > > Key: OFBIZ-11395 > URL: https://issues.apache.org/jira/browse/OFBIZ-11395 > Project: OFBiz > Issue Type: Sub-task > Components: manufacturing >Affects Versions: Trunk >Reporter: Yashwant Dhakad >Assignee: Yashwant Dhakad >Priority: Minor > Labels: groovy, mini-lang > Attachments: OFBIZ-11395.patch > > > In this ticket, I have converted createProductionRunPartyAssign, > createProductionRunAssoc, issueProductionRunTask, > issueProductionRunTaskComponent, issueProductionRunTaskComponentInline and > issueInventoryItemToWorkEffort services into groovy DSL. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11395) Convert ProductionRunServices.xml file from mini-lang to groovy DSL
[ https://issues.apache.org/jira/browse/OFBIZ-11395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17042573#comment-17042573 ] Yashwant Dhakad commented on OFBIZ-11395: - I have converted all the services from ProductionRunServices.xml file into groovy and I am still verifying these services but you can start to verify and provide your feedback. For now, I have not removed the XML code and once I will thoroughly verify then I will remove these XML services. > Convert ProductionRunServices.xml file from mini-lang to groovy DSL > --- > > Key: OFBIZ-11395 > URL: https://issues.apache.org/jira/browse/OFBIZ-11395 > Project: OFBiz > Issue Type: Sub-task > Components: manufacturing >Affects Versions: Trunk >Reporter: Yashwant Dhakad >Assignee: Yashwant Dhakad >Priority: Minor > Labels: groovy, mini-lang > Attachments: OFBIZ-11395.patch > > > In this ticket, I have converted createProductionRunPartyAssign, > createProductionRunAssoc, issueProductionRunTask, > issueProductionRunTaskComponent, issueProductionRunTaskComponentInline and > issueInventoryItemToWorkEffort services into groovy DSL. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11395) Convert ProductionRunServices.xml file from mini-lang to groovy DSL
[ https://issues.apache.org/jira/browse/OFBIZ-11395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad updated OFBIZ-11395: Description: In this ticket, I have converted createProductionRunPartyAssign, createProductionRunAssoc, issueProductionRunTask, issueProductionRunTaskComponent, issueProductionRunTaskComponentInline and issueInventoryItemToWorkEffort services into groovy DSL. > Convert ProductionRunServices.xml file from mini-lang to groovy DSL > --- > > Key: OFBIZ-11395 > URL: https://issues.apache.org/jira/browse/OFBIZ-11395 > Project: OFBiz > Issue Type: Sub-task > Components: manufacturing >Affects Versions: Trunk >Reporter: Yashwant Dhakad >Assignee: Yashwant Dhakad >Priority: Minor > Labels: groovy, mini-lang > Attachments: OFBIZ-11395.patch > > > In this ticket, I have converted createProductionRunPartyAssign, > createProductionRunAssoc, issueProductionRunTask, > issueProductionRunTaskComponent, issueProductionRunTaskComponentInline and > issueInventoryItemToWorkEffort services into groovy DSL. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11395) Convert ProductionRunServices.xml file from mini-lang to groovy DSL
[ https://issues.apache.org/jira/browse/OFBIZ-11395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad updated OFBIZ-11395: Attachment: OFBIZ-11395.patch > Convert ProductionRunServices.xml file from mini-lang to groovy DSL > --- > > Key: OFBIZ-11395 > URL: https://issues.apache.org/jira/browse/OFBIZ-11395 > Project: OFBiz > Issue Type: Sub-task > Components: manufacturing >Affects Versions: Trunk >Reporter: Yashwant Dhakad >Assignee: Yashwant Dhakad >Priority: Minor > Labels: groovy, mini-lang > Attachments: OFBIZ-11395.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OFBIZ-11395) Convert ProductionRunServices.xml file from mini-lang to groovy DSL
Yashwant Dhakad created OFBIZ-11395: --- Summary: Convert ProductionRunServices.xml file from mini-lang to groovy DSL Key: OFBIZ-11395 URL: https://issues.apache.org/jira/browse/OFBIZ-11395 Project: OFBiz Issue Type: Sub-task Components: manufacturing Affects Versions: Trunk Reporter: Yashwant Dhakad Assignee: Yashwant Dhakad -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (OFBIZ-10577) New Feature: Inventory Cycle Count
[ https://issues.apache.org/jira/browse/OFBIZ-10577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034401#comment-17034401 ] Yashwant Dhakad edited comment on OFBIZ-10577 at 2/11/20 12:24 PM: --- Hi Pierre, Thank you for your suggestion. I have created a new branch on my fork repository and created [pull request|[https://github.com/yashwantdhakad/ofbiz-framework/pull/1]|https://github.com/yashwantdhakad/ofbiz-framework/pull/1] in that and if all the changes look good then I will create a pull request for Apache OFBiz repository. was (Author: yashwant.dhakad): Hi Pierre, Thank you for your suggestion. I have created a new branch on my fork repository and created [pull request|[https://github.com/yashwantdhakad/ofbiz-framework/pull/1] in that and if all the changes look good then I will create a pull request for Apache OFBiz repository. > 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 > Attachments: OFBIZ-10577-Database-Changes.patch, OFBIZ-10577.patch, > screenshot-1-find-session.png, screenshot-2-pending-locations.png, > screenshot-3-add-location-to-session.png, > screenshot-4-list-of-review-session.png, > screenshot-5-review-session-detail.png, screenshot-6-accept-session.png, > screenshot-7-complete-review.png, screenshot-8-report-screen.png > > > *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 >
[jira] [Comment Edited] (OFBIZ-10577) New Feature: Inventory Cycle Count
[ https://issues.apache.org/jira/browse/OFBIZ-10577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034401#comment-17034401 ] Yashwant Dhakad edited comment on OFBIZ-10577 at 2/11/20 12:24 PM: --- Hi Pierre, Thank you for your suggestion. I have created a new branch on my fork repository and created [pull request|[https://github.com/yashwantdhakad/ofbiz-framework/pull/1]] in that and if all the changes look good then I will create a pull request for Apache OFBiz repository. was (Author: yashwant.dhakad): Hi Pierre, Thank you for your suggestion. I have created a new branch on my fork repository and created [pull request|[https://github.com/yashwantdhakad/ofbiz-framework/pull/1]|https://github.com/yashwantdhakad/ofbiz-framework/pull/1] in that and if all the changes look good then I will create a pull request for Apache OFBiz repository. > 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 > Attachments: OFBIZ-10577-Database-Changes.patch, OFBIZ-10577.patch, > screenshot-1-find-session.png, screenshot-2-pending-locations.png, > screenshot-3-add-location-to-session.png, > screenshot-4-list-of-review-session.png, > screenshot-5-review-session-detail.png, screenshot-6-accept-session.png, > screenshot-7-complete-review.png, screenshot-8-report-screen.png > > > *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 >
[jira] [Commented] (OFBIZ-10577) New Feature: Inventory Cycle Count
[ https://issues.apache.org/jira/browse/OFBIZ-10577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034401#comment-17034401 ] Yashwant Dhakad commented on OFBIZ-10577: - Hi Pierre, Thank you for your suggestion. I have created a new branch on my fork repository and created [pull request|[https://github.com/yashwantdhakad/ofbiz-framework/pull/1] in that and if all the changes look good then I will create a pull request for Apache OFBiz repository. > 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 > Attachments: OFBIZ-10577-Database-Changes.patch, OFBIZ-10577.patch, > screenshot-1-find-session.png, screenshot-2-pending-locations.png, > screenshot-3-add-location-to-session.png, > screenshot-4-list-of-review-session.png, > screenshot-5-review-session-detail.png, screenshot-6-accept-session.png, > screenshot-7-complete-review.png, screenshot-8-report-screen.png > > > *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 > ***Extended entity:* > *FacilityLocation* > locked >
[jira] [Comment Edited] (OFBIZ-10577) New Feature: Inventory Cycle Count
[ https://issues.apache.org/jira/browse/OFBIZ-10577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17033461#comment-17033461 ] Yashwant Dhakad edited comment on OFBIZ-10577 at 2/11/20 12:21 PM: --- Thanks [~pierresmits] for your response. I agree with your above feedback on using github (or any other git repo tool). I've created a pull request for all the code changes of this feature. Please refer: [https://github.com/yashwantdhakad/ofbiz-framework/pull/1] Please review the changes and provide your valuable feedback. Thanks! was (Author: yashwant.dhakad): Thanks [~pierresmits] for your response. I agree with your above feedback on using github (or any other git repo tool). I've created a pull request for all the code changes of this feature. Please refer: [|https://github.com/apache/ofbiz-framework/pull/11] [https://github.com/yashwantdhakad/ofbiz-framework/pull/1] Please review the changes and provide your valuable feedback. Thanks! > 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 > Attachments: OFBIZ-10577-Database-Changes.patch, OFBIZ-10577.patch, > screenshot-1-find-session.png, screenshot-2-pending-locations.png, > screenshot-3-add-location-to-session.png, > screenshot-4-list-of-review-session.png, > screenshot-5-review-session-detail.png, screenshot-6-accept-session.png, > screenshot-7-complete-review.png, screenshot-8-report-screen.png > > > *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 >
[jira] [Comment Edited] (OFBIZ-10577) New Feature: Inventory Cycle Count
[ https://issues.apache.org/jira/browse/OFBIZ-10577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17033461#comment-17033461 ] Yashwant Dhakad edited comment on OFBIZ-10577 at 2/11/20 12:19 PM: --- Thanks [~pierresmits] for your response. I agree with your above feedback on using github (or any other git repo tool). I've created a pull request for all the code changes of this feature. Please refer: [https://github.com/yashwantdhakad/ofbiz-framework/pull/1] [|https://github.com/apache/ofbiz-framework/pull/11] Please review the changes and provide your valuable feedback. Thanks! was (Author: yashwant.dhakad): Thanks [~pierresmits] for your response. I agree with your above feedback on using github (or any other git repo tool). I've created a pull request for all the code changes of this feature. Please refer: [https://github.com/apache/ofbiz-framework/pull/11] Please review the changes and provide your valuable feedback. Thanks! > 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 > Attachments: OFBIZ-10577-Database-Changes.patch, OFBIZ-10577.patch, > screenshot-1-find-session.png, screenshot-2-pending-locations.png, > screenshot-3-add-location-to-session.png, > screenshot-4-list-of-review-session.png, > screenshot-5-review-session-detail.png, screenshot-6-accept-session.png, > screenshot-7-complete-review.png, screenshot-8-report-screen.png > > > *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
[jira] [Comment Edited] (OFBIZ-10577) New Feature: Inventory Cycle Count
[ https://issues.apache.org/jira/browse/OFBIZ-10577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17033461#comment-17033461 ] Yashwant Dhakad edited comment on OFBIZ-10577 at 2/11/20 12:19 PM: --- Thanks [~pierresmits] for your response. I agree with your above feedback on using github (or any other git repo tool). I've created a pull request for all the code changes of this feature. Please refer: [|https://github.com/apache/ofbiz-framework/pull/11] [https://github.com/yashwantdhakad/ofbiz-framework/pull/1] Please review the changes and provide your valuable feedback. Thanks! was (Author: yashwant.dhakad): Thanks [~pierresmits] for your response. I agree with your above feedback on using github (or any other git repo tool). I've created a pull request for all the code changes of this feature. Please refer: [https://github.com/yashwantdhakad/ofbiz-framework/pull/1] [|https://github.com/apache/ofbiz-framework/pull/11] Please review the changes and provide your valuable feedback. Thanks! > 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 > Attachments: OFBIZ-10577-Database-Changes.patch, OFBIZ-10577.patch, > screenshot-1-find-session.png, screenshot-2-pending-locations.png, > screenshot-3-add-location-to-session.png, > screenshot-4-list-of-review-session.png, > screenshot-5-review-session-detail.png, screenshot-6-accept-session.png, > screenshot-7-complete-review.png, screenshot-8-report-screen.png > > > *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 >
[jira] [Commented] (OFBIZ-10577) New Feature: Inventory Cycle Count
[ https://issues.apache.org/jira/browse/OFBIZ-10577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17033461#comment-17033461 ] Yashwant Dhakad commented on OFBIZ-10577: - Thanks [~pierresmits] for your response. I agree with your above feedback on using github (or any other git repo tool). I've created a pull request for all the code changes of this feature. Please refer: [https://github.com/apache/ofbiz-framework/pull/11] Please review the changes and provide your valuable feedback. Thanks! > 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 > Attachments: OFBIZ-10577-Database-Changes.patch, OFBIZ-10577.patch, > screenshot-1-find-session.png, screenshot-2-pending-locations.png, > screenshot-3-add-location-to-session.png, > screenshot-4-list-of-review-session.png, > screenshot-5-review-session-detail.png, screenshot-6-accept-session.png, > screenshot-7-complete-review.png, screenshot-8-report-screen.png > > > *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 >
[jira] [Commented] (OFBIZ-10577) New Feature: Inventory Cycle Count
[ https://issues.apache.org/jira/browse/OFBIZ-10577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17032318#comment-17032318 ] Yashwant Dhakad commented on OFBIZ-10577: - I have attached some screenshots for reference. Please have a look and provide your feedback. > 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 > Attachments: OFBIZ-10577-Database-Changes.patch, OFBIZ-10577.patch, > screenshot-1-find-session.png, screenshot-2-pending-locations.png, > screenshot-3-add-location-to-session.png, > screenshot-4-list-of-review-session.png, > screenshot-5-review-session-detail.png, screenshot-6-accept-session.png, > screenshot-7-complete-review.png, screenshot-8-report-screen.png > > > *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 > ***Extended entity:* > *FacilityLocation* > locked > lastCountDate > nextCountDate > **We will prevent the following inbound and outbound transactions within the > application if the location is locked for counting: > Inventory
[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: Attachment: screenshot-1-find-session.png screenshot-8-report-screen.png screenshot-7-complete-review.png screenshot-6-accept-session.png screenshot-5-review-session-detail.png screenshot-4-list-of-review-session.png screenshot-3-add-location-to-session.png screenshot-2-pending-locations.png > 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 > Attachments: OFBIZ-10577-Database-Changes.patch, OFBIZ-10577.patch, > screenshot-1-find-session.png, screenshot-2-pending-locations.png, > screenshot-3-add-location-to-session.png, > screenshot-4-list-of-review-session.png, > screenshot-5-review-session-detail.png, screenshot-6-accept-session.png, > screenshot-7-complete-review.png, screenshot-8-report-screen.png > > > *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 >
[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: Attachment: (was: OFBIZ-10577.patch) > 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 > Attachments: OFBIZ-10577-Database-Changes.patch, OFBIZ-10577.patch > > > *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 > ***Extended entity:* > *FacilityLocation* > locked > lastCountDate > nextCountDate > **We will prevent the 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
[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: Attachment: OFBIZ-10577.patch > 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 > Attachments: OFBIZ-10577-Database-Changes.patch, OFBIZ-10577.patch > > > *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 > ***Extended entity:* > *FacilityLocation* > locked > lastCountDate > nextCountDate > **We will prevent the 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 way.
[jira] [Commented] (OFBIZ-11339) Getting error on allocation plan approval
[ https://issues.apache.org/jira/browse/OFBIZ-11339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17030456#comment-17030456 ] Yashwant Dhakad commented on OFBIZ-11339: - Hi Pierre, This feature recently added so it is available in the trunk only. > Getting error on allocation plan approval > - > > Key: OFBIZ-11339 > URL: https://issues.apache.org/jira/browse/OFBIZ-11339 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Trunk >Reporter: Yashwant Dhakad >Assignee: Yashwant Dhakad >Priority: Minor > Attachments: > screenshot-demo-trunk.ofbiz.apache.org-2020.02.04-15_39_48.png > > > When we approve the allocation plan then it is showing error like facility id > is missing. I have attached the screenshot for reference. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (OFBIZ-11338) Error showing on Allocation Plan screen
[ https://issues.apache.org/jira/browse/OFBIZ-11338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad updated OFBIZ-11338: Comment: was deleted (was: Hi Pierre, This feature recently added so it is available in the trunk only.) > Error showing on Allocation Plan screen > --- > > Key: OFBIZ-11338 > URL: https://issues.apache.org/jira/browse/OFBIZ-11338 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Trunk >Reporter: Yashwant Dhakad >Assignee: Aman Mishra >Priority: Minor > Attachments: > screenshot-demo-trunk.ofbiz.apache.org-2020.02.04-15_30_53.png > > > On the Allocation plan screen an error occurs on the summary section. I have > attached the screen for reference. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11338) Error showing on Allocation Plan screen
[ https://issues.apache.org/jira/browse/OFBIZ-11338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17030453#comment-17030453 ] Yashwant Dhakad commented on OFBIZ-11338: - Hi Pierre, This feature recently added so it is available in the trunk only. > Error showing on Allocation Plan screen > --- > > Key: OFBIZ-11338 > URL: https://issues.apache.org/jira/browse/OFBIZ-11338 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Trunk >Reporter: Yashwant Dhakad >Assignee: Aman Mishra >Priority: Minor > Attachments: > screenshot-demo-trunk.ofbiz.apache.org-2020.02.04-15_30_53.png > > > On the Allocation plan screen an error occurs on the summary section. I have > attached the screen for reference. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11338) Error showing on Allocation Plan screen
[ https://issues.apache.org/jira/browse/OFBIZ-11338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17030454#comment-17030454 ] Yashwant Dhakad commented on OFBIZ-11338: - Hi Pierre, This feature recently added so it is available in the trunk only. > Error showing on Allocation Plan screen > --- > > Key: OFBIZ-11338 > URL: https://issues.apache.org/jira/browse/OFBIZ-11338 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Trunk >Reporter: Yashwant Dhakad >Assignee: Aman Mishra >Priority: Minor > Attachments: > screenshot-demo-trunk.ofbiz.apache.org-2020.02.04-15_30_53.png > > > On the Allocation plan screen an error occurs on the summary section. I have > attached the screen for reference. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11339) Getting error on allocation plan approval
[ https://issues.apache.org/jira/browse/OFBIZ-11339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad updated OFBIZ-11339: Affects Version/s: Trunk > Getting error on allocation plan approval > - > > Key: OFBIZ-11339 > URL: https://issues.apache.org/jira/browse/OFBIZ-11339 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Trunk >Reporter: Yashwant Dhakad >Assignee: Yashwant Dhakad >Priority: Minor > Attachments: > screenshot-demo-trunk.ofbiz.apache.org-2020.02.04-15_39_48.png > > > When we approve the allocation plan then it is showing error like facility id > is missing. I have attached the screenshot for reference. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11338) Error showing on Allocation Plan screen
[ https://issues.apache.org/jira/browse/OFBIZ-11338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad updated OFBIZ-11338: Affects Version/s: Trunk > Error showing on Allocation Plan screen > --- > > Key: OFBIZ-11338 > URL: https://issues.apache.org/jira/browse/OFBIZ-11338 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Trunk >Reporter: Yashwant Dhakad >Assignee: Yashwant Dhakad >Priority: Minor > Attachments: > screenshot-demo-trunk.ofbiz.apache.org-2020.02.04-15_30_53.png > > > On the Allocation plan screen an error occurs on the summary section. I have > attached the screen for reference. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (OFBIZ-11339) Getting error on allocation plan approval
[ https://issues.apache.org/jira/browse/OFBIZ-11339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad reassigned OFBIZ-11339: --- Assignee: Yashwant Dhakad > Getting error on allocation plan approval > - > > Key: OFBIZ-11339 > URL: https://issues.apache.org/jira/browse/OFBIZ-11339 > Project: OFBiz > Issue Type: Bug > Components: order >Reporter: Yashwant Dhakad >Assignee: Yashwant Dhakad >Priority: Minor > Attachments: > screenshot-demo-trunk.ofbiz.apache.org-2020.02.04-15_39_48.png > > > When we approve the allocation plan then it is showing error like facility id > is missing. I have attached the screenshot for reference. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OFBIZ-11339) Getting error on allocation plan approval
Yashwant Dhakad created OFBIZ-11339: --- Summary: Getting error on allocation plan approval Key: OFBIZ-11339 URL: https://issues.apache.org/jira/browse/OFBIZ-11339 Project: OFBiz Issue Type: Bug Components: order Reporter: Yashwant Dhakad Attachments: screenshot-demo-trunk.ofbiz.apache.org-2020.02.04-15_39_48.png When we approve the allocation plan then it is showing error like facility id is missing. I have attached the screenshot for reference. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (OFBIZ-11338) Error showing on Allocation Plan screen
[ https://issues.apache.org/jira/browse/OFBIZ-11338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad reassigned OFBIZ-11338: --- Assignee: Yashwant Dhakad > Error showing on Allocation Plan screen > --- > > Key: OFBIZ-11338 > URL: https://issues.apache.org/jira/browse/OFBIZ-11338 > Project: OFBiz > Issue Type: Bug > Components: order >Reporter: Yashwant Dhakad >Assignee: Yashwant Dhakad >Priority: Minor > Attachments: > screenshot-demo-trunk.ofbiz.apache.org-2020.02.04-15_30_53.png > > > On the Allocation plan screen an error occurs on the summary section. I have > attached the screen for reference. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OFBIZ-11338) Error showing on Allocation Plan screen
Yashwant Dhakad created OFBIZ-11338: --- Summary: Error showing on Allocation Plan screen Key: OFBIZ-11338 URL: https://issues.apache.org/jira/browse/OFBIZ-11338 Project: OFBiz Issue Type: Bug Components: order Reporter: Yashwant Dhakad Attachments: screenshot-demo-trunk.ofbiz.apache.org-2020.02.04-15_30_53.png On the Allocation plan screen an error occurs on the summary section. I have attached the screen for reference. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-10577) New Feature: Inventory Cycle Count
[ https://issues.apache.org/jira/browse/OFBIZ-10577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023550#comment-17023550 ] Yashwant Dhakad commented on OFBIZ-10577: - I have prevented the inbound and outbound transactions and uploaded the latest patch for these changes. I have added database changes form earlier patch as well so all the changes of this feature available in OFBIZ-10577.patch. Please have a look and let me know if you found any issues or improvements. > 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 > Attachments: OFBIZ-10577-Database-Changes.patch, OFBIZ-10577.patch > > > *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 > ***Extended entity:* > *FacilityLocation* > locked > lastCountDate > nextCountDate > **We will prevent the 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 >
[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: Attachment: (was: OFBIZ-10577.patch) > 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 > Attachments: OFBIZ-10577-Database-Changes.patch, OFBIZ-10577.patch > > > *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 > ***Extended entity:* > *FacilityLocation* > locked > lastCountDate > nextCountDate > **We will prevent the 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
[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: Attachment: (was: OFBIZ-10577.patch) > 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 > Attachments: OFBIZ-10577-Database-Changes.patch, OFBIZ-10577.patch, > OFBIZ-10577.patch > > > *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 > ***Extended entity:* > *FacilityLocation* > locked > lastCountDate > nextCountDate > **We will prevent the 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
[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: Attachment: OFBIZ-10577.patch > 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 > Attachments: OFBIZ-10577-Database-Changes.patch, OFBIZ-10577.patch, > OFBIZ-10577.patch > > > *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 > ***Extended entity:* > *FacilityLocation* > locked > lastCountDate > nextCountDate > **We will prevent the 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
[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: Attachment: OFBIZ-10577.patch > 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 > Attachments: OFBIZ-10577-Database-Changes.patch, OFBIZ-10577.patch, > OFBIZ-10577.patch > > > *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 > ***Extended entity:* > *FacilityLocation* > locked > lastCountDate > nextCountDate > **We will prevent the 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
[jira] [Commented] (OFBIZ-5027) Product Facility record should be created in case of its no record when calling setLastInventoryCount service as EECA.
[ https://issues.apache.org/jira/browse/OFBIZ-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023415#comment-17023415 ] Yashwant Dhakad commented on OFBIZ-5027: Hi Amardeep any update on this ticket? > Product Facility record should be created in case of its no record when > calling setLastInventoryCount service as EECA. > -- > > Key: OFBIZ-5027 > URL: https://issues.apache.org/jira/browse/OFBIZ-5027 > Project: OFBiz > Issue Type: Improvement > Components: product >Reporter: Amardeep Singh Jhajj >Assignee: Amardeep Singh Jhajj >Priority: Minor > Attachments: OFBIZ-5027-Release-10.04.patch, > OFBIZ-5027-Release-11.04.patch, OFBIZ-5027-trunk.patch > > > Currently, ProductFacility record is updated by setLastInventoryCount service > when create-store-remove operation performed on InventoryItemDetail entity > (by EECA). > This service is called to update lastInventoryCount field in ProductFacility > and this field helps us for checking product in-stock/out-of-stock. > This service helps only when ProductFacility will already present. Suppose, > if catalog manager forgot to setup facility or deleted it at > https://demo-trunk.ofbiz.apache.org:8443/catalog/control/EditProductFacilities?productId=WG-9943-B3 > and just setup Inventory during product setup then setLastInventoryCount > service would not be helpful. > So in my opinion, here ProductFacility should be first created in case of its > no record when updating lastInventoryCount in ProductFacility. > I am attaching patch for the same here. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (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:comment-tabpanel=17023413#comment-17023413 ] Yashwant Dhakad commented on OFBIZ-9475: Hi Deepak/Jacques, Any update on this? Can we commit these changes and create a sub ticket for the new improvements or code refactor. > 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: product >Affects Versions: Trunk >Reporter: Deepak Dixit >Assignee: Yashwant Dhakad >Priority: Major > Attachments: OFBIZ-9475.patch, 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
[jira] [Commented] (OFBIZ-10577) New Feature: Inventory Cycle Count
[ https://issues.apache.org/jira/browse/OFBIZ-10577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17012882#comment-17012882 ] Yashwant Dhakad commented on OFBIZ-10577: - Hello Guys, I have uploaded the patch for this new feature. Please have a look and provide your valuable feedback or suggestions. I am working on its inbound and outbound transactions and will provide a new patch for these transactions. > 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 > Attachments: OFBIZ-10577-Database-Changes.patch, OFBIZ-10577.patch > > > *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 > ***Extended entity:* > *FacilityLocation* > locked > lastCountDate > nextCountDate > **We will prevent the 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 >
[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: Attachment: OFBIZ-10577.patch > 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 > Attachments: OFBIZ-10577-Database-Changes.patch, OFBIZ-10577.patch > > > *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 > ***Extended entity:* > *FacilityLocation* > locked > lastCountDate > nextCountDate > **We will prevent the 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 way.
[jira] [Commented] (OFBIZ-10577) New Feature: Inventory Cycle Count
[ https://issues.apache.org/jira/browse/OFBIZ-10577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17010797#comment-17010797 ] Yashwant Dhakad commented on OFBIZ-10577: - Sure, Pierre, I will update this field and end of this week I will add a patch for this new feature. > 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 > Attachments: OFBIZ-10577-Database-Changes.patch > > > *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 > ***Extended entity:* > *FacilityLocation* > locked > lastCountDate > nextCountDate > **We will prevent the 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
[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: Description: *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 ***Extended entity:* *FacilityLocation* locked lastCountDate nextCountDate **We will prevent the 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 way. was: *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
[jira] [Commented] (OFBIZ-10577) New Feature: Inventory Cycle Count
[ https://issues.apache.org/jira/browse/OFBIZ-10577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17008781#comment-17008781 ] Yashwant Dhakad commented on OFBIZ-10577: - Hi Mathieu, Cycle count is an inventory auditing procedure of physical inventory whereby inventory is counted at regular intervals within a fiscal year. > 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 > Attachments: OFBIZ-10577-Database-Changes.patch > > > *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
[jira] [Assigned] (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 reassigned OFBIZ-10577: --- Assignee: Yashwant Dhakad (was: Ankit Joshi) > 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 > Attachments: OFBIZ-10577-Database-Changes.patch > > > *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
[jira] [Commented] (OFBIZ-7595) Replace references of Entity Engine methods with EntityQUery methods in various Groovy and Java Files
[ https://issues.apache.org/jira/browse/OFBIZ-7595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16848177#comment-16848177 ] Yashwant Dhakad commented on OFBIZ-7595: Hi [~sanjay.ya...@hotwaxsystems.com], I looked into code base and not found any reference for Entity Engine method and I thik all the methods replaced with Entity Query method. So we can can safely close this ticket. > Replace references of Entity Engine methods with EntityQUery methods in > various Groovy and Java Files > - > > Key: OFBIZ-7595 > URL: https://issues.apache.org/jira/browse/OFBIZ-7595 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk >Reporter: Sanjay Yadav >Assignee: Yashwant Dhakad >Priority: Minor > > Replace references of Entity Engine methods with EntityQUery methods in > various Groovy and Java Files. > This is a parent task to remove references of Entity Engine methods. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-7595) Replace references of Entity Engine methods with EntityQUery methods in various Groovy and Java Files
[ https://issues.apache.org/jira/browse/OFBIZ-7595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad reassigned OFBIZ-7595: -- Assignee: Yashwant Dhakad (was: Sanjay Yadav) > Replace references of Entity Engine methods with EntityQUery methods in > various Groovy and Java Files > - > > Key: OFBIZ-7595 > URL: https://issues.apache.org/jira/browse/OFBIZ-7595 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk >Reporter: Sanjay Yadav >Assignee: Yashwant Dhakad >Priority: Minor > > Replace references of Entity Engine methods with EntityQUery methods in > various Groovy and Java Files. > This is a parent task to remove references of Entity Engine methods. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-9506) OFBIZ-6964: Implementation to support replenishment planning through any inter-company facility
[ https://issues.apache.org/jira/browse/OFBIZ-9506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad updated OFBIZ-9506: --- Attachment: OFBIZ-9506.patch > OFBIZ-6964: Implementation to support replenishment planning through any > inter-company facility > --- > > Key: OFBIZ-9506 > URL: https://issues.apache.org/jira/browse/OFBIZ-9506 > Project: OFBiz > Issue Type: Sub-task > Components: manufacturing, order, product >Reporter: Swapnil M Mane >Assignee: Yashwant Dhakad >Priority: Major > Attachments: OFBIZ-9506.patch, OFBIZ-9506.patch, OFBIZ-9506.patch, > OFBIZ-9506.patch > > > For support of replenishment planning through any inter-company facility, > This task is for the code implementation on the basis of design/information > shared in the ticket https://issues.apache.org/jira/browse/OFBIZ-7356. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-9506) OFBIZ-6964: Implementation to support replenishment planning through any inter-company facility
[ https://issues.apache.org/jira/browse/OFBIZ-9506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16727430#comment-16727430 ] Yashwant Dhakad commented on OFBIZ-9506: I have updated the patch because the old patch is broken on the trunk. Will provide testing steps ASAP. > OFBIZ-6964: Implementation to support replenishment planning through any > inter-company facility > --- > > Key: OFBIZ-9506 > URL: https://issues.apache.org/jira/browse/OFBIZ-9506 > Project: OFBiz > Issue Type: Sub-task > Components: manufacturing, order, product >Reporter: Swapnil M Mane >Assignee: Yashwant Dhakad >Priority: Major > Attachments: OFBIZ-9506.patch, OFBIZ-9506.patch, OFBIZ-9506.patch, > OFBIZ-9506.patch > > > For support of replenishment planning through any inter-company facility, > This task is for the code implementation on the basis of design/information > shared in the ticket https://issues.apache.org/jira/browse/OFBIZ-7356. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-9506) OFBIZ-6964: Implementation to support replenishment planning through any inter-company facility
[ https://issues.apache.org/jira/browse/OFBIZ-9506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad reassigned OFBIZ-9506: -- Assignee: Yashwant Dhakad (was: Arun Patidar) > OFBIZ-6964: Implementation to support replenishment planning through any > inter-company facility > --- > > Key: OFBIZ-9506 > URL: https://issues.apache.org/jira/browse/OFBIZ-9506 > Project: OFBiz > Issue Type: Sub-task > Components: manufacturing, order, product >Reporter: Swapnil M Mane >Assignee: Yashwant Dhakad >Priority: Major > Attachments: OFBIZ-9506.patch, OFBIZ-9506.patch, OFBIZ-9506.patch > > > For support of replenishment planning through any inter-company facility, > This task is for the code implementation on the basis of design/information > shared in the ticket https://issues.apache.org/jira/browse/OFBIZ-7356. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-7357) OFBIZ-6964: Prepare Demo Data based on the propsed design to support replenishment planning through any inter-company facility
[ https://issues.apache.org/jira/browse/OFBIZ-7357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16727309#comment-16727309 ] Yashwant Dhakad commented on OFBIZ-7357: The demo data looks good to me. I am verifying the workflow in OFBIZ-9506 ticket and will provide testing steps ASAP. > OFBIZ-6964: Prepare Demo Data based on the propsed design to support > replenishment planning through any inter-company facility > -- > > Key: OFBIZ-7357 > URL: https://issues.apache.org/jira/browse/OFBIZ-7357 > Project: OFBiz > Issue Type: Sub-task > Components: manufacturing, order, product >Affects Versions: 15.12.01 >Reporter: Swapnil Shah >Assignee: Arun Patidar >Priority: Major > Attachments: OFBIZ-7357.patch, OFBIZ-7357.patch, OFBIZ-7357.patch > > > We can start preparing demo data for implementation and testing purpose based > on requirement and design details shared over OFBIZ-7355 & OFBIZ-7356 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (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:comment-tabpanel=1079#comment-1079 ] Yashwant Dhakad commented on OFBIZ-9475: I have uploaded the new patch for serializing inventory and following changes did in this patch: * Removed the service which updated the serialize inventory ATP/QOH based on status. * Added support in the workflow where inventory item transactions happen and created the IID record. * InventoryItem ATP/QOH automatically updated by IID record. * I have tested the following scenarios: ** Receive inventory. ** Reserve, issue and return inventory from the sales order. ** Produce, Issue and return from the production run. ** Inventory transfer. Please have a look and provide your valuable feedback. > 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, 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", >
[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: --- Attachment: OFBIZ-9475.patch > 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, 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 >
[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: --- Attachment: (was: OFBIZ-9475.patch) > 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, 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
[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: --- Attachment: OFBIZ-9475.patch > 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, 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 >
[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] [Created] (OFBIZ-10585) Production run not created for marketing package auto type product if component inventory is not available
Yashwant Dhakad created OFBIZ-10585: --- Summary: 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 Reporter: Yashwant Dhakad 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] [Assigned] (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 reassigned OFBIZ-9475: -- Assignee: Yashwant Dhakad (was: Vaibhav Jain) > 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 >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 for
[jira] [Assigned] (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 reassigned OFBIZ-10577: --- Assignee: Yashwant Dhakad > New Feature: Inventory Cycle Count > -- > > Key: OFBIZ-10577 > URL: https://issues.apache.org/jira/browse/OFBIZ-10577 > Project: OFBiz > Issue Type: New Feature >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 way. -- This
[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: Description: *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 way. was: *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
[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: Description: *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'. *4. 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 way. was: *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
[jira] [Created] (OFBIZ-10577) New Feature: Inventory Cycle Count
Yashwant Dhakad created OFBIZ-10577: --- Summary: New Feature: Inventory Cycle Count Key: OFBIZ-10577 URL: https://issues.apache.org/jira/browse/OFBIZ-10577 Project: OFBiz Issue Type: New Feature Reporter: Yashwant Dhakad *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'. *4. 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@Mention someone by typing their name... 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 way. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-9506) OFBIZ-6964: Implementation to support replenishment planning through any inter-company facility
[ https://issues.apache.org/jira/browse/OFBIZ-9506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad updated OFBIZ-9506: --- Attachment: (was: OFBIZ-9506.patch) > OFBIZ-6964: Implementation to support replenishment planning through any > inter-company facility > --- > > Key: OFBIZ-9506 > URL: https://issues.apache.org/jira/browse/OFBIZ-9506 > Project: OFBiz > Issue Type: Sub-task > Components: manufacturing, order, product >Reporter: Swapnil M Mane >Assignee: Yashwant Dhakad > Attachments: OFBIZ-9506.patch > > > For support of replenishment planning through any inter-company facility, > This task is for the code implementation on the basis of design/information > shared in the ticket https://issues.apache.org/jira/browse/OFBIZ-7356. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9506) OFBIZ-6964: Implementation to support replenishment planning through any inter-company facility
[ https://issues.apache.org/jira/browse/OFBIZ-9506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad updated OFBIZ-9506: --- Attachment: OFBIZ-9506.patch > OFBIZ-6964: Implementation to support replenishment planning through any > inter-company facility > --- > > Key: OFBIZ-9506 > URL: https://issues.apache.org/jira/browse/OFBIZ-9506 > Project: OFBiz > Issue Type: Sub-task > Components: manufacturing, order, product >Reporter: Swapnil M Mane >Assignee: Yashwant Dhakad > Attachments: OFBIZ-9506.patch > > > For support of replenishment planning through any inter-company facility, > This task is for the code implementation on the basis of design/information > shared in the ticket https://issues.apache.org/jira/browse/OFBIZ-7356. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9506) OFBIZ-6964: Implementation to support replenishment planning through any inter-company facility
[ https://issues.apache.org/jira/browse/OFBIZ-9506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad updated OFBIZ-9506: --- Attachment: OFBIZ-9506.patch > OFBIZ-6964: Implementation to support replenishment planning through any > inter-company facility > --- > > Key: OFBIZ-9506 > URL: https://issues.apache.org/jira/browse/OFBIZ-9506 > Project: OFBiz > Issue Type: Sub-task > Components: manufacturing, order, product >Reporter: Swapnil M Mane >Assignee: Yashwant Dhakad > Attachments: OFBIZ-9506.patch > > > For support of replenishment planning through any inter-company facility, > This task is for the code implementation on the basis of design/information > shared in the ticket https://issues.apache.org/jira/browse/OFBIZ-7356. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9506) OFBIZ-6964: Implementation to support replenishment planning through any inter-company facility
[ https://issues.apache.org/jira/browse/OFBIZ-9506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad updated OFBIZ-9506: --- Attachment: (was: OFBIZ-9506.patch) > OFBIZ-6964: Implementation to support replenishment planning through any > inter-company facility > --- > > Key: OFBIZ-9506 > URL: https://issues.apache.org/jira/browse/OFBIZ-9506 > Project: OFBiz > Issue Type: Sub-task > Components: manufacturing, order, product >Reporter: Swapnil M Mane >Assignee: Yashwant Dhakad > Attachments: OFBIZ-9506.patch > > > For support of replenishment planning through any inter-company facility, > This task is for the code implementation on the basis of design/information > shared in the ticket https://issues.apache.org/jira/browse/OFBIZ-7356. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9506) OFBIZ-6964: Implementation to support replenishment planning through any inter-company facility
[ https://issues.apache.org/jira/browse/OFBIZ-9506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad updated OFBIZ-9506: --- Attachment: OFBIZ-9506.patch > OFBIZ-6964: Implementation to support replenishment planning through any > inter-company facility > --- > > Key: OFBIZ-9506 > URL: https://issues.apache.org/jira/browse/OFBIZ-9506 > Project: OFBiz > Issue Type: Sub-task > Components: manufacturing, order, product >Reporter: Swapnil M Mane >Assignee: Yashwant Dhakad > Attachments: OFBIZ-9506.patch > > > For support of replenishment planning through any inter-company facility, > This task is for the code implementation on the basis of design/information > shared in the ticket https://issues.apache.org/jira/browse/OFBIZ-7356. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9506) OFBIZ-6964: Implementation to support replenishment planning through any inter-company facility
[ https://issues.apache.org/jira/browse/OFBIZ-9506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad updated OFBIZ-9506: --- Attachment: (was: OFBIZ-9506.patch) > OFBIZ-6964: Implementation to support replenishment planning through any > inter-company facility > --- > > Key: OFBIZ-9506 > URL: https://issues.apache.org/jira/browse/OFBIZ-9506 > Project: OFBiz > Issue Type: Sub-task > Components: manufacturing, order, product >Reporter: Swapnil M Mane >Assignee: Yashwant Dhakad > Attachments: OFBIZ-9506.patch > > > For support of replenishment planning through any inter-company facility, > This task is for the code implementation on the basis of design/information > shared in the ticket https://issues.apache.org/jira/browse/OFBIZ-7356. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9506) OFBIZ-6964: Implementation to support replenishment planning through any inter-company facility
[ https://issues.apache.org/jira/browse/OFBIZ-9506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad updated OFBIZ-9506: --- Attachment: (was: OFBIZ-9506.patch) > OFBIZ-6964: Implementation to support replenishment planning through any > inter-company facility > --- > > Key: OFBIZ-9506 > URL: https://issues.apache.org/jira/browse/OFBIZ-9506 > Project: OFBiz > Issue Type: Sub-task > Components: manufacturing, order, product >Reporter: Swapnil M Mane >Assignee: Yashwant Dhakad > Attachments: OFBIZ-9506.patch > > > For support of replenishment planning through any inter-company facility, > This task is for the code implementation on the basis of design/information > shared in the ticket https://issues.apache.org/jira/browse/OFBIZ-7356. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9506) OFBIZ-6964: Implementation to support replenishment planning through any inter-company facility
[ https://issues.apache.org/jira/browse/OFBIZ-9506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad updated OFBIZ-9506: --- Attachment: OFBIZ-9506.patch > OFBIZ-6964: Implementation to support replenishment planning through any > inter-company facility > --- > > Key: OFBIZ-9506 > URL: https://issues.apache.org/jira/browse/OFBIZ-9506 > Project: OFBiz > Issue Type: Sub-task > Components: manufacturing, order, product >Reporter: Swapnil M Mane >Assignee: Yashwant Dhakad > Attachments: OFBIZ-9506.patch > > > For support of replenishment planning through any inter-company facility, > This task is for the code implementation on the basis of design/information > shared in the ticket https://issues.apache.org/jira/browse/OFBIZ-7356. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9506) OFBIZ-6964: Implementation to support replenishment planning through any inter-company facility
[ https://issues.apache.org/jira/browse/OFBIZ-9506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad updated OFBIZ-9506: --- Attachment: OFBIZ-9506.patch Here is the patch to create MRP Events from the backup warehouse. > OFBIZ-6964: Implementation to support replenishment planning through any > inter-company facility > --- > > Key: OFBIZ-9506 > URL: https://issues.apache.org/jira/browse/OFBIZ-9506 > Project: OFBiz > Issue Type: Sub-task > Components: manufacturing, order, product >Reporter: Swapnil M Mane >Assignee: Yashwant Dhakad > Attachments: OFBIZ-9506.patch > > > For support of replenishment planning through any inter-company facility, > This task is for the code implementation on the basis of design/information > shared in the ticket https://issues.apache.org/jira/browse/OFBIZ-7356. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
