SKU Detail Movement History

Current Status

This is shown on the Movement History tab on the SKU detail layout

On the tab is a single button marked movement which when clicked invokes a portal for the SKU with

Header

Field	Type	Definition	Comments	Retain on Stroke 2 Equivalent layout
SKU	Numeric	The SKU in question		There needs to be a SKU movement history - this is not really the ideal format
Expected	Numeric	'@sum of the Expected Balance for the SKU		It would be far better to have a transaction listing. To be defined, but would include Date Movement Type Qty User Balance after movement This is complicated by having differing balance types:- Expected Available Allocated Picked Warehouse Balance
Allocated	Numeric	as above but for Allocated Balance
Available	Numeric	as above but for Available Balance

Purchase Order Portal

This portal lists all PO's that contain the SKU. Typically Purchase Orders will increment a SKU available and warehouse balance when booked in

Field	Type	Definition	Comments	Retain on Stroke 2 Equivalent layout
Creation Date	date	PO Creation Date		Comments per Header
SKU	Numeric	Identifier for he SKU	This is redundant as SKU listed in header	Remove
Description	Text	SKU Description	would be better to list once in header section as repeated continually here	Remove
Quantity Received	Numeric	Qty of the SKU received on the PO
Total	Numeric	'@sum of QTY received

Fulfilment Portal

This portal lists all Fulfilments that contain the SKU. Typically fulfilments will decrement a SKU available and warehouse balance when picked

Field	Type	Definition	Comments	Retain on Stroke 2 Equivalent layout
Despatch Date	date	PO Creation Date		Comments per Header
Fulfilment No	Numeric	Identifier for the Fulfilment
SKU		Identifier for the SKU	This is redundant as SKU listed in header	Remove
Description	Text		would be better to list once in header section as repeated continually here	Remove
Qty	Numeric	'@sum of sent
Total	Numeric	'@sum of QTY sent

Date Entry Portal

This portal lists all data entry records for the SKU in question. Data entry is conceptually very similar to booking in. It is the actualisation of the SKU / location balance that comes around from the conclusion of the creating production processes. As such typically Data entry debits the expected balance by the qty due to be produced and credits the SKU available and location balance for the qty successfully produced.

Field	Type	Definition	Comments	Retain on Stroke 2 Equivalent layout
SKU	Numeric	Identifier for the SKU	This is redundant as SKU listed in header	Remove
Description	Text		would be better to list once in header section as repeated continually here	Remove
Job Number	Text	Identifier for the Job that resulted in data entreis
Department	Text	The department that owns the process line on the job
Position	Text	The position that was decorated
Qty to be Given	Text	The Qty given (debited from blank) for the process line
Production	Icon	Denotes the production Line status
Data Entry	Icon	Denotes the data entry status for the process line