ofbiz-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre Smits (Jira)" <j...@apache.org>
Subject [jira] [Commented] (OFBIZ-10577) New Feature: Inventory Cycle Count
Date Fri, 07 Feb 2020 12:04:00 GMT

    [ https://issues.apache.org/jira/browse/OFBIZ-10577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17032326#comment-17032326

Pierre Smits commented on OFBIZ-10577:

Hi [~yashwant.dhakad],

Is this patch also somewhere implemented in a development/feature branch in a publicly available
git repo (e.g. on Github)?

If so, it may be beneficial to fellow community members to use that for review (and other
collaboration) purposes. And if everything checks out, the project can/may decide to use a
pull request to establish an officially endorsed 'OFBiz feature branch' to make it available
to the entire community, or directly merge it into another branch (trunk and or release branch).

IMO, providing enhancement contributions (bug fixes, improvements and new features) through
development branches in public git repos is more favourable as it leverages the key feature(s)
of git.

It avoids you to upload additional enhancements to the solution to this tickets, but also
to have reviewing community members to download these enhancements  and apply them to their
review branch.

> 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,
> *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.

This message was sent by Atlassian Jira

View raw message