Lot Number Tracking - Revision history

Jgullickson: /* Rack Filling Tokens */

2022-12-22T19:48:43Z

Rack Filling Tokens

2022-12-22T19:47:36Z

Added Rack Filling Lot Number tokens

2022-12-22T19:45:52Z

Tokens

2021-11-24T16:07:40Z

Lot/Batch Number Generation

2021-11-24T16:06:33Z

Lot/Batch Traceability

2017-12-05T18:45:50Z

Tokens = UINM

2017-12-05T18:45:26Z

Tokens = UINAddLOC

2017-12-04T17:31:36Z

Examples

2017-12-04T17:21:34Z

Tokens

2017-12-04T17:19:52Z

Lot/Batch Number Generation

@@ Line 70: / Line 70: @@
 ** It is recommended that if the Location-specific Lot Number ID token is used for prepopulating the Lot #, then make make the Location ID consistent for all locations, such as, always use 4 letters in this field, in order to facilitate the use of a Lot # Validation Pattern.
-====Examples====
+=====Examples=====
 For both of these examples, assume that Courtney Smith is doing the fill on January 2, 2019, from your Pittsburgh Branch.
@@ Line 91: / Line 91: @@
 That would not be a great lot number because everything which is filled in January, no  matter what day, no matter what year, no matter what location, would all have the lot # CS1.
-==Rack Filling Tokens ==
+====Rack Filling Tokens ====
 When you utilize TrackAbout's Rack Filling feature you will have this additional set of token to select from:

@@ Line 69: / Line 69: @@
 ** For example, if a Branch named Pittsburgh has PITT as the Lot Number ID, then PITT can become part of all Lot Numbers when the Fill is done in Pittsburgh.
 ** It is recommended that if the Location-specific Lot Number ID token is used for prepopulating the Lot #, then make make the Location ID consistent for all locations, such as, always use 4 letters in this field, in order to facilitate the use of a Lot # Validation Pattern.
 ====Examples====
@@ Line 93: / Line 90: @@
 That would not be a great lot number because everything which is filled in January, no  matter what day, no matter what year, no matter what location, would all have the lot # CS1.
 ===Bulk Lot Tracking===

@@ Line 16: / Line 16: @@
 ===Lot / Batch Number Generation===
 TrackAbout provides the means to allow you to track your own Lot Numbers, or the system can be configured to auto-generate Lot Numbers based on a specified format as part of our the Filling functionality. When your TrackAbout representative sets this  up, they tell TrackAbout what it should put in the Lot # field to make the Lot # unique. There is a whole list of "tokens" which can be entered in. Here is the list of tokens, including explanations, followed by a couple of examples.
 ====Tokens====
@@ Line 67: / Line 69: @@
 ** For example, if a Branch named Pittsburgh has PITT as the Lot Number ID, then PITT can become part of all Lot Numbers when the Fill is done in Pittsburgh.
 ** It is recommended that if the Location-specific Lot Number ID token is used for prepopulating the Lot #, then make make the Location ID consistent for all locations, such as, always use 4 letters in this field, in order to facilitate the use of a Lot # Validation Pattern.
 ====Examples====

@@ Line 14: / Line 14: @@
 Many industries are now required by law to track the Lots or Batches associated with their products.
-===Lot/Batch Number Generation===
+===Lot / Batch Number Generation===
-TrackAbout provides the means to allow you to track your own Lot Numbers, or the system can be configured to auto-generate Lot Numbers based on a specified format as part of our the Filling functionality. When your TrackAbout representative sets this  up, s/he tells TrackAbout what it should put in the Lot # field to make the Lot # unique. There is a whole list of "tokens" which can be entered in. Here is the list of tokens, including explanations, followed by a couple of examples.
+TrackAbout provides the means to allow you to track your own Lot Numbers, or the system can be configured to auto-generate Lot Numbers based on a specified format as part of our the Filling functionality. When your TrackAbout representative sets this  up, they tell TrackAbout what it should put in the Lot # field to make the Lot # unique. There is a whole list of "tokens" which can be entered in. Here is the list of tokens, including explanations, followed by a couple of examples.
 ====Tokens====

@@ Line 8: / Line 8: @@
 ===Lot/Batch Traceability===
-These identifications numbers can be used for tracing and accountability of the product.
+These identifications numbers can be used for tracing and accountability of the product. Tracking Lot Numbers is particularly helpful in cases such as:
 * Product Recalls
 * Product Expiration tracking
 Many industries are now required by law to track the Lots or Batches associated with their products.
 ===Lot/Batch Number Generation===

@@ Line 83: / Line 83: @@
 Please note that for this example, the same Lot Number could be generated in Pittsburgh every year on January 2, so including the year could help with uniqueness of lot numbers.
-=====Tokens = UINM=====
+=====Tokens = [UIN][M]=====
 * UIN = User's initials, so this would be CS for Courtney Smith
 * M = Month 1-12, so in January, this would be 1.

@@ Line 73: / Line 73: @@
 For both of these examples, assume that Courtney Smith is doing the fill on January 2, 2019, from your Pittsburgh Branch.
-=====Tokens = UINAddLOC=====
+=====Tokens = [UIN][A][dd][LOC]=====
 * UIN = User's initials,  so this would be CS for Courtney Smith
 * A = Month as letter, so filling in January would make this be A