...
Column Name | Data type | Mandatory? (Create) | Mandatory? (Update) | Description | Permissible Values | Validations |
|---|---|---|---|---|---|---|
Supply ID | Number | No | No | System generated unique number for every supply | ||
Name | String | YesNo | Yes | A unique name If not specified system generates a unique number for the supply | ||
Procurement Date | Date | Yes | No | The date when the supplies are brought or the supply is set | ||
Expiry Date | Date | Yes | No | The date when supply will expire | ||
Procured Quantity | Number | No | No | The used number of items in supply. This applies to non-barcoded supply items. | ||
Available Quantity | Number | No | No | The available number of items in supply. This applies to non-barcoded supply items. | ||
Description | String | No | No | Comments or details related to supply | ||
Type#Supply Type ID | Number | Yes | No | System auto-generated unique number for every type under which the supply is created | ||
Type#Name | String | No | No | Name of type under which the supply is created | ||
Vendor#Name | String | Yes | No | This should be valid vendor name from the Vendors. Refer to Vendors and Locations | ||
Site#Name | String | No | No | The site where the supplies are stored. Ensure that supply site is included in the collection protocol site, or else the system will not allow to consume the item. | ||
Location#Name | String | No | No | Location within the site where the supplies are kept. E.g. cupboard, drawer. | Refer to Vendors and Locations | |
Allowed CP#1#Short Title | String | No | No | One ore more collection protocols for which this supply is procured for. You can consume the items only from allowed collection protocol. |
...