Dgarratt at 17:09, 21 December 2023

2023-12-21T17:09:17Z

← Older revision		Revision as of 19:09, 21 December 2023
Line 14:		Line 14:
	* Data is written but not verified against the Material Batches Table<br><br>		* Data is written but not verified against the Material Batches Table<br><br>

	[[File:~~material_batches~~.~~jpg~~]]		[[File:Material batches.png\|600px\|thumb\|left\|Material Batches]]<br>

Dgarratt: Created page with "You should not normally need to add data to this screen as the system will automatically populate the data for you. However there maybe times when you need to some of the info..."

2012-09-16T09:31:58Z

Created page with "You should not normally need to add data to this screen as the system will automatically populate the data for you. However there maybe times when you need to some of the info..."

New page

You should not normally need to add data to this screen as the system will automatically populate the data for you. However there maybe times when you need to some of the information. You should note that the way Commander4j works with Expiry Dates is determined by a [[System Keys|System Key]] called '''EXPIRY DATE MODE'''. If EXPIRY DATE MODE is configured with the value BATCH then this table will be populated when you create a new pallet using the [[Production Declaration]] screen. 

The logic used by the system when System Key '''EXPIRY DATE MODE''' is ''BATCH'' 

* User attempts to create a new pallet (SSCC) using the Production Declaration screen. 
* As part of the validation the Material and Batch Number combination are looked up in the Material Batches database. 
* If the Material Batches does not exist in the system a new record is created and the Expiry Date as calculated/entered by the user is stored against it. 
* If the Material Batch already exists in the database then the Expiry date which has been provided by the user is compared with that held in the database. 
* If they are the same then the pallet is created, if they are different then an error message is reported back to the user. 

The logic used by the system when System Key '''EXPIRY DATE MODE''' is ''SSCC'' 

* Each SSCC created holds it's own Expiry Record as part of the Pallet Record. 
* Data is written but not verified against the Material Batches Table 

[[File:material_batches.jpg]]

Material Batches - Revision history

Dgarratt at 17:09, 21 December 2023

Dgarratt: Created page with "You should not normally need to add data to this screen as the system will automatically populate the data for you. However there maybe times when you need to some of the info..."