Inventory Cycle Count feature gap

[Yashwant Dhakad-2]

Hello All,
Currently, we don't have any user interface to do cycle count for the
warehouse, Where user can create or manage cycle count for different
locations within any facility. Authorized users to approve or reject the
count and record variance. Also, the recorded variance against
counted/scanned locations can be made available in the form of the report
on a daily basis. Based on this I am proposing this feature where we can
record and manage the cycle count through different sessions in following
steps:

   1. Create Cycle Count session: User can create a new cycle count session
   by scanning any location from the facility and system would list all the
   inventory items or product ids. The user can physically count or scan the
   inventory/product and update the physical count. Apart from this, user can
   also be allowed to manually add any not listed inventory item or product in
   the same session. Once record count is completed user can submit the
   cycle count session for review. As soon as the session is created the added
   locations can be locked from honoring any inward or outward inventory
   movement or transactions through them.
   2. Find Counting session: On this screen, User can view all the existing
   sessions and further filter by session id, facility, location and status.
   3. Review Cycle Count session:  On this screen, any authorized user can
   review the cycle count for open sessions and accept or reject the recorded
   count, once done system would create the
   necessary variance to corresponding inventory item or product and update
   the ATP/QOH accordingly.
   4. Variance Report screen: On this screen, the user can view the actual
   variance based on facility, location, product/inventory and date.
   5. Later on if required we can also schedule the submitted location for
   next cycle count by setting next counting date. This would allow to user
   see all the pending location on any given date where cycle count is due.
   And can start new sessions for the same.

Please share your thoughts and we make the necessary changes in the
workflow based on that feedback.

Thanks & Regards
--
Yashwant Dhakad

[Shi Jinghai-3]

Hi Yashwant,

Besides the scenario you described, I'm working on a retail scenario, selling goods in refrigerators/containers, when a door open/close, a count action is triggered and fulfilled by RFID, the variance will be generated to an auto payed order if the door is opened/closed by a customer.

Regards,

Shi Jinghai


-----邮件原件-----
发件人: Yashwant Dhakad [mailto:[hidden email]]
发送时间: 2018年7月28日 19:37
收件人: [hidden email]
抄送: Yashwant Dhakad
主题: Inventory Cycle Count feature gap

Hello All,
Currently, we don't have any user interface to do cycle count for the
warehouse, Where user can create or manage cycle count for different
locations within any facility. Authorized users to approve or reject the
count and record variance. Also, the recorded variance against
counted/scanned locations can be made available in the form of the report
on a daily basis. Based on this I am proposing this feature where we can
record and manage the cycle count through different sessions in following
steps:

   1. Create Cycle Count session: User can create a new cycle count session
   by scanning any location from the facility and system would list all the
   inventory items or product ids. The user can physically count or scan the
   inventory/product and update the physical count. Apart from this, user can
   also be allowed to manually add any not listed inventory item or product in
   the same session. Once record count is completed user can submit the
   cycle count session for review. As soon as the session is created the added
   locations can be locked from honoring any inward or outward inventory
   movement or transactions through them.
   2. Find Counting session: On this screen, User can view all the existing
   sessions and further filter by session id, facility, location and status.
   3. Review Cycle Count session:  On this screen, any authorized user can
   review the cycle count for open sessions and accept or reject the recorded
   count, once done system would create the
   necessary variance to corresponding inventory item or product and update
   the ATP/QOH accordingly.
   4. Variance Report screen: On this screen, the user can view the actual
   variance based on facility, location, product/inventory and date.
   5. Later on if required we can also schedule the submitted location for
   next cycle count by setting next counting date. This would allow to user
   see all the pending location on any given date where cycle count is due.
   And can start new sessions for the same.

Please share your thoughts and we make the necessary changes in the
workflow based on that feedback.

Thanks & Regards
--
Yashwant Dhakad

[swapnil]

One more scenario to consider while weighing in the design is that all the
categories' items are not necessarily required to be counted in the
facility. And at times these categories have dedicated locations for
stocking. For example, supply items or consumables.

It would be nice to make it configurable such that only eligible categories'
locations/items are listed for counting by default.

Thanks & Regards,
Swapnil

-----Original Message-----
From: Yashwant Dhakad <[hidden email]>
Sent: Saturday, July 28, 2018 5:07 PM
To: [hidden email]
Cc: Yashwant Dhakad <[hidden email]>
Subject: Inventory Cycle Count feature gap

Hello All,
Currently, we don't have any user interface to do cycle count for the
warehouse, Where user can create or manage cycle count for different
locations within any facility. Authorized users to approve or reject the
count and record variance. Also, the recorded variance against
counted/scanned locations can be made available in the form of the report on
a daily basis. Based on this I am proposing this feature where we can record
and manage the cycle count through different sessions in following
steps:

   1. Create Cycle Count session: User can create a new cycle count session
   by scanning any location from the facility and system would list all the
   inventory items or product ids. The user can physically count or scan the
   inventory/product and update the physical count. Apart from this, user
can
   also be allowed to manually add any not listed inventory item or product
in
   the same session. Once record count is completed user can submit the
   cycle count session for review. As soon as the session is created the
added
   locations can be locked from honoring any inward or outward inventory
   movement or transactions through them.
   2. Find Counting session: On this screen, User can view all the existing
   sessions and further filter by session id, facility, location and status.
   3. Review Cycle Count session:  On this screen, any authorized user can
   review the cycle count for open sessions and accept or reject the
recorded
   count, once done system would create the
   necessary variance to corresponding inventory item or product and update
   the ATP/QOH accordingly.
   4. Variance Report screen: On this screen, the user can view the actual
   variance based on facility, location, product/inventory and date.
   5. Later on if required we can also schedule the submitted location for
   next cycle count by setting next counting date. This would allow to user
   see all the pending location on any given date where cycle count is due.
   And can start new sessions for the same.

Please share your thoughts and we make the necessary changes in the workflow
based on that feedback.

Thanks & Regards
--
Yashwant Dhakad

[Yashwant Dhakad-2]

Hello All,
I have created a ticket <https://issues.apache.org/jira/browse/OFBIZ-10577>
for this and provided all the design notes.

Thanks & Regards
--
Yashwant Dhakad


On Mon, Jul 30, 2018 at 5:03 PM Swapnil Shah <[hidden email]>
wrote:

> One more scenario to consider while weighing in the design is that all the
> categories' items are not necessarily required to be counted in the
> facility. And at times these categories have dedicated locations for
> stocking. For example, supply items or consumables.
>
> It would be nice to make it configurable such that only eligible
> categories'
> locations/items are listed for counting by default.
>
> Thanks & Regards,
> Swapnil
>
> -----Original Message-----
> From: Yashwant Dhakad <[hidden email]>
> Sent: Saturday, July 28, 2018 5:07 PM
> To: [hidden email]
> Cc: Yashwant Dhakad <[hidden email]>
> Subject: Inventory Cycle Count feature gap
>
> Hello All,
> Currently, we don't have any user interface to do cycle count for the
> warehouse, Where user can create or manage cycle count for different
> locations within any facility. Authorized users to approve or reject the
> count and record variance. Also, the recorded variance against
> counted/scanned locations can be made available in the form of the report
> on
> a daily basis. Based on this I am proposing this feature where we can
> record
> and manage the cycle count through different sessions in following
> steps:
>
>    1. Create Cycle Count session: User can create a new cycle count session
>    by scanning any location from the facility and system would list all the
>    inventory items or product ids. The user can physically count or scan
> the
>    inventory/product and update the physical count. Apart from this, user
> can
>    also be allowed to manually add any not listed inventory item or product
> in
>    the same session. Once record count is completed user can submit the
>    cycle count session for review. As soon as the session is created the
> added
>    locations can be locked from honoring any inward or outward inventory
>    movement or transactions through them.
>    2. Find Counting session: On this screen, User can view all the existing
>    sessions and further filter by session id, facility, location and
> status.
>    3. Review Cycle Count session:  On this screen, any authorized user can
>    review the cycle count for open sessions and accept or reject the
> recorded
>    count, once done system would create the
>    necessary variance to corresponding inventory item or product and update
>    the ATP/QOH accordingly.
>    4. Variance Report screen: On this screen, the user can view the actual
>    variance based on facility, location, product/inventory and date.
>    5. Later on if required we can also schedule the submitted location for
>    next cycle count by setting next counting date. This would allow to user
>    see all the pending location on any given date where cycle count is due.
>    And can start new sessions for the same.
>
> Please share your thoughts and we make the necessary changes in the
> workflow
> based on that feedback.
>
> Thanks & Regards
> --
> Yashwant Dhakad
>