Stock Card: Use Cases
Legend
Red: user cannot input
Yellow (yellow): Mandatory field
Green: at least one field should not be null, also support all fields are not null. For example, the adjust reason can be null if the received from/issue to column has value.
| Date | Document number | Received quantity | Received from | Issue quantity | Issue to | Adjustment quantity | Adjustment reason | Stock on Hand | Signature |
|---|---|---|---|---|---|---|---|---|---|---|
Receive | User Input | User input, no format requirement, no validation | User input, postitive whole number | User choose from list or input for ad hoc | Can not fill in | Can not fill in | Can not fill in | User choose from list, must choose + reason, or input + | Auto pupolated | User input, no format requirement, no validation |
Issue | User Input | User input, no format requirement, no validation | Can not fill in | Can not fill in | User input, postitive whole number | User choose from list or input for ad hoc | Can not fill in | User choose from list, must choose from - reason, or input - | Auto pupolated | User input, no format requirement, no validation |
Positive Adjustment | User Input | User input, no format requirement, no validation | Can not fill in | Empty when it is internal adjustment e.g. products return. Otherwise it must be chosen by user | Can not fill in | Can not fill in | User input, postitive whole number | User choose from list, must choose positive adjustment reason, or free input | Auto pupolated | User input, no format requirement, no validation |
Negative Adjustment | User Input | User input, no format requirement, no validation | Can not fill in | Can not fill in | Can not fill in | Ok to be empty, if empty, then reason must exist | User input, postitive whole number | User choose from list, must choose negative reason, or freetext input | Auto pupolated | User input, no format requirement, no validation |
Phisical Stock Count | Auto populated by system | Does not apply | Can not fill in | Can not fill in | Can not fill in | Can not fill in | Auto populated | Auto populated | Auto pupolated | User input, no format requirement, no validation |
Comments
@Lakshmi Balachandran, the user cases would be very complex so I did not write them all here. I prefer talking to you guys first and then record our agreements here. However, I can explain the meaning of different colours here:
Red: user cannot input
Yellow: Mandatory field
Green: at least one field should not be null, also support all fields are not null. For example, the adjust reason can be null if the received from/issue to column has value.
White: optional field
@Shiyu JIN Largely agree and we can discuss more on the next call. Two points: (A) I understand what the red stands for, but what's the difference between yellow and green?, (B) For physical stock count, SOH is not autopopulated, but rather user input. Or rather, user should have the ability to input the phy stock count (that's not clear from this table), from which adjustment quantity is auto populated and SOH can be calculated from that (and will equal the phy stock count amount entered by user).