Field | Type | Definition | Comments | Retain on Stroke 2 Equivalent layout |
> |
Navigation |
Open Detail form |
The detail dropdown |
TBC |
Warehouse Discrepancy |
Numeric |
=(@sum of SKU Available + @sum of SKU Allocated)-(@sum of SKU warehouse location balances) |
In simple terms the running balance of ins and outs compared to warehouse position |
Yes |
SKU |
Numeric |
Unique reference identifier for item |
|
Yes |
£ icon |
Navigation |
Opens pop up allowing a search for origin PO's for the Sku including purchase costs for specified a date range |
Original intention was for tracking ink costs |
TBC |
Description |
Text |
Concatenation of various attributes depending on Product type |
See Here for details - But query need for size and type as they are layout fields |
Yes |
Size |
Text |
Size field from sku detail |
If size is displayed here, it should be removed from description |
Yes |
EOTL |
Flag |
Currently not used |
|
No/TBC ? |
Shopify Set up Flag |
Flag |
Speaking to webstores these update to green when a SKU is set up & linked successfully to the shopify equivalent |
Looking at the code it is based on Design Group and Company API Integration fields <> Blank |
|
Shopify Flag |
Flag |
Note: the first of these is called Bool_Old; the second Bool - what is the use case ? |
Webstores say they need this |
Yes |
Type (note there is no label) |
Text |
Taken from item sub-Type, e.g. T-Shirt; Cap; Apron etc |
If type is contained in description it should be removed from the layout as it's a duplication |
No |
Favourite |
Boolean |
Unless this is user specifific iot it not much use - was designed so that pick lists could be filtered by user favourites |
Can it be user specific ? |
TBC |
Detail |
Navigation |
Invokes Drop down with subset of sku detail info - fields / tabs will need to be defined |
Needs contents to be defined |
Yes |
Product |
Text |
This is the highest level product type; e.g Blank Garment |
The applicable values for this field
should be rationalised For example, the below 4 values may conceivably cover the inventory
[This requires discussion to agree upon rationalised value list] |
Yes |
Suitability for Digital |
Flag |
Currently not used |
|
No/TBC ? |
Owner |
Text |
Is the Company Name from Company Table |
Note: clicking here invokes picker to allow company choice |
Yes |
Primary Supplier |
Text |
This is supplier name from SKU Detail > Product attributes table - Is it used ? |
How is this used |
TBC |
Price Group |
Text |
Mechanism to link TOT SKU to supplier Products for various reasons - import prices; price updates |
This is not great- what is really needed is configurable mapping between TOT Data object and an external source to allow the field mapping to occur. Note a really smart idea would be to allow different mappings definitions for the same TOT object to differing external sources |
Yes - Some form of configurable mapping. |
Colour Shade |
Text |
Another element of the price group |
|
|
VAT Type |
Look up[ |
Looks up value in the VAT table (adult; child) |
Does it belong in list layout ? |
TBC >? |
Allocated |
Numeric |
@sum of allocated qty for SKU |
|
Yes |
Min |
Numeric |
Defined QTY that represents the minimum stock balance that should be held |
|
Yes |
Available above Min |
Numeric |
Calculated as Available - Min |
Colour coding if breached ? |
Yes |
Available |
Numeric |
@sum of available qty for SKU |
Warehouse balance should equal Available + Allocated |
Yes |
Set |
Button |
Allows users to amend the current Available balance |
Query use of this - available balances should really be a result of a transaction. It would be better audit wise if adjustment transaction was used |
TBC ? |
Adjust |
Button |
Allows users to increment or decrement the available balance |
Makes sense to have this and embellish with adj reason field to aid auditing - and store as a movement transaction |
Yes |
Expected |
Numeric |
@sum of Expected qty for SKU |
|
Yes |
Lines |
Button |
Invokes Drop down with three portals to explain the expected balance [PO, Bucket. Job Lines] |
If Expected is Zero - should button be hidden ? |
Yes |
Image |
Button |
View [Insert , Deleted] the family image for the SKU. Colour coded to denote when image loaded |
|
Yes |
Select |
Button |
Allows for multiple records to be selected |
|
Yes |
Cost |
Numeric |
Displays (1st ??) Supplier cost for item - is it needed here ? |
How do you represents when > 1 cost |
TBC |
Weight |
Numeric |
Weight of item in KG - does it belong on a list layout ? |
|
TBC |
Printer SKU |
Button |
Prints [specify qty] of SKU barcode labels needed |
Who uses this here |
TBC |
In the SKU list layout, the description field is a concatenation of a series of attributes which differs according to Product Type
Product Type | Attribute 1 | Attribute 2 | Attribute 3 | Attribute 4 | Attribute 5 | Attribute 6 | Attribute 7 |
Blank Screen |
x_TEXT_d_Frame_Description_sort |
|
|
|
|
|
|
Consumable |
d_Brand |
d_Description |
d_PackageSize |
d_UnitOfMeasure) |
|
|
|
Digitisation/Subbed Art |
d_Description) |
|
|
|
|
|
|
Embroidery Thread |
x_TEXT_Ink_Colour_formatted |
d_Brand |
d_Description |
d_PackageSize |
d_UnitOfMeasure) |
|
|
Merchandise |
d_Category |
d_Description |
d_Colour |
d_Item_Type |
d_Size) |
|
|
Mixed Screen Ink |
x_TEXT_Ink_Colour_formatted |
d_Description |
d_ColourReference |
d_Item_Type ) |
|
|
|
Peripheral |
d_Category |
d_Description |
d_Item_Type |
d_Colour |
d_Size) |
|
|
Printed Garment |
d_Category |
d_Description |
d_ColourWay |
d_Item_Type |
d_Colour |
d_Size |
d_Trim) |
Purchased Screen Ink |
x_TEXT_Ink_Colour_formatted |
d_Description |
d_ColourReference |
d_Item_Type ) |
|
|
|
Service Item |
d_Description) |
|
|
|
|
|
|
Blank Garment |
d_Brand |
d_Item_Type |
d_Style |
d_Colour |
d_Trim |
d_Size) |
|
Cleaning Supplies |
d_Brand |
d_Description |
d_PackageSize |
d_UnitOfMeasure) |
|
|
|
General Item |
d_Description) |
|
|
|
|
|
|
Screen Frame |
d_Description) |
|
|
|
|
|
|
Support Item |
d_Item_Type |
d_Category |
d_Colour |
d_Description) |
|
|
|