RFE

INF-12298 Recalculate On Hand at Apply Count.docx

Request From CFA

This request is related to apply times entered for counts not impacting perpetual on hand values in InFORM. We'd like to test 2 potential solutions that I'll outline below.

1) Implement Correct On Hand functionality for all count types (preferred for perpetual inventory accuracy). If all count types had functionality where the user would enter a qty in each location and then save the count with InFORM applying the count to the time the count was saved, perpetual on hands would be as accurate as possible. This option would not allow for the month-end count to be reviewed and changed by the Operator/member of their leadership team before submitting. We'll need feedback from Financial Return Consultants and Supply Chain Consultants on this option.

2) Apply counts to apply date/time entered by user to each item's perpetual on hand value in InFORM. This option would entail all transactions impacting perpetual on hands that occurred after the count's apply date/time to be re-processed after the count was submitted to ensure perpetual on hand values accurately reflected the time the count was performed.

Additional Information Needed

We know that the network and system experiences heavy traffic and usage at the end of every month as CFA locations perform and submit end of month inventory counts. Because of this, before InFORM can commit to any work on this feature, we have to determine if the system can successfully handle the volume of on hand updates that we expect to receive during these times.

Question Around Suggestion 1:

1. What are the performance costs of allowing users to collectively update the system on hand in real time?
2. Will the system be frustrating or unusable?
3. Is there a risk of losing user entered data due to performance issues?

Questions Around Suggestion 2:

1. What are the performance costs to recalculating the on hand inventory of multiple locations at the same time?
2. How much additional work is required to use the user back-dated count time and any depletion from that time to now and recalculate system on hand inventory?
3. Will the system be frustrating or unusable?
4. Is there a risk of losing user entered data due to performance issues?

Additional Questions:

1. If the performance costs are too high, is there a 3rd option that satisfies the requirement and maintains site useability?
2. If so, what is this option?

InFORM will take on this initial request and complete this research. Once the performance issues, if any, are identified, that data will be shared with CFA as will our internal suggestions as to how to solve this problem.