Create an instance of an electronic stock card during receiving process

@Shiyu Jin, our approach was to call out the receiving stories separately because it would be the receiving from a requisition. At this point, issues don't 'require' a requisition to be submitted. Does that make sense? How we should tackle these inter-dependencies should still be discussed. I'd like to hear from you about sequencing and how to tackle these processes from a development perspective.

@Mary Jo Kochendorfer@Lakshmi Balachandran
I assume the ticket https://openlmis.atlassian.net/browse/OLMIS-712#icft=OLMIS-712 is also related to this ticket?

Agree, we should reuse OLMIS-1632. And yes, https://openlmis.atlassian.net/browse/OLMIS-1632#icft=OLMIS-1632 should cover ad-hoc issue and receipt, this is for the normal/local receive process.

1. I've removed that line from AC1. The initial idea was to create stock cards as soon as the product list is created. Since we've changed that to creating stock cards when an initial stock movement happens, we don't need that line.

2. To be defined in the Receiving Epic, OLMIS-646. Also see this page which now has a first level of detail on how the Receiving Epic will work.

3. Yes. Also defined in https://openlmis.atlassian.net/browse/OLMIS-646#icft=OLMIS-646

@Mary Jo Kochendorfer@Lakshmi Balachandran
I assume this story is for the normal receive/issue process?
Since we have the story https://openlmis.atlassian.net/browse/OLMIS-1632#icft=OLMIS-1632 to handle all creation for stock card/line items, I believe we can reuse that function. However, there are few questions I want to ask:

• As for #1, you said 'this will only apply to those products not on the facility's product list'. Do you mean the system will create a stock card even if the product does not on the facility's approval list?

• How will the system know when the shipped products have arrived?

• Will the storeroom manager count/check how many products shipped in case the request amount on the requisition does not match the amount shipped

@Mary Jo Kochendorfer Discussion Point

Just a thought, should stock cards be program wise or product wise?

Stock will arrive in a facility as a result of an order line that is created through a requisition request. Requisitions are based on programs and not products.

I think ( we can discuss it ) it will be easy to manage stock cards wr.t. programs instead of products. Reconciliation will be easy while confirming Proof of Delivery

Physical Stock check can be challenging if stock cards are by programs because it will be difficult to get a cumulative picture. But that can be handled by giving user view w.r.t products count as mentioned in https://openlmis.atlassian.net/browse/OLMIS-18#icft=OLMIS-18