Information Systems:ASW Invoice Number Series - Revision history

Norwinu at 17:35, 27 May 2021

2021-05-27T17:35:27Z

Norwinu at 19:59, 20 May 2021

2021-05-20T19:59:02Z

Norwinu at 19:05, 20 May 2021

2021-05-20T19:05:42Z

Norwinu: Norwinu moved page Information Systems:Monitor Invoice Numbers to Information Systems:ASW Invoice Number Series

2021-05-20T18:18:39Z

Norwinu moved page Information Systems:Monitor Invoice Numbers to Information Systems:ASW Invoice Number Series

New page

==Invoice Numbers - Estimated to Wrap in 2018==

We started in 2005 with an invoice number of 1000001, and credit note number of 3000001. On June 5, 2009 invoice numbers passed 3000000 and duplicated the credit note numbers. ASW was fine, as it accesses files by invoice number / type (1-invoice, 2-credit note) / year. The extensions were not. We quickly changed them to use the same key structure - after changing the next invoice number (in the number series table) to 5000001.

When the invoice number reaches 8999999 it will go back to 1000001. I don't think anything will happen - but keep an eye on it just in case.

In order to monitor the process, get the current invoice number (series 4) from the [[Table Maintenance Programs|Number Series Table]], and periodically add it to this document.

2015 Dec 16 8078278

Sheilav at 17:35, 16 December 2015

2015-12-16T17:35:58Z

Sheilav: /* Invoice Numbers - Estimated to Wrap in 2018 */

2015-12-16T17:31:02Z

Invoice Numbers - Estimated to Wrap in 2018

Sheilav at 17:29, 16 December 2015

2015-12-16T17:29:12Z

Sheilav: Created page with "==Invoice Numbers - Estimated to Wrap in 2018== We started in 2005 with an invoice number of 1000001, and credit note number of 3000001. On June 5, 2009 invoice numbers pass..."

2015-12-16T17:23:05Z

Created page with "==Invoice Numbers - Estimated to Wrap in 2018== We started in 2005 with an invoice number of 1000001, and credit note number of 3000001. On June 5, 2009 invoice numbers pass..."

New page

==Invoice Numbers - Estimated to Wrap in 2018==

We started in 2005 with an invoice number of 1000001, and credit note number of 3000001. On June 5, 2009 invoice numbers passed 3000000 and duplicated the credit note numbers. ASW was fine, as it accesses files by invoice number / type (1-invoice, 2-credit note) / year. The extensions were not. We quickly changed them to use the same key structure - after changing the next invoice number (in the number series table) to 5000001.

When the invoice number reaches 8999999 it will go back to 1000001. I don't think anything will happen - but keep an eye on it just in case.

In order to monitor the process, get the current invoice number (series INV) from the [[Document Number Series Table]], and add it to this document.

2015 Dec 16 8078278

@@ Line 10: / Line 10: @@
 ! Table name !! Field name (invoice number field) !! Notes !! Overlap prevention
 |-
 |-
 |}
-==Archive==
+==History==
 ===Invoice Numbers - Estimated to Wrap in 2018===

@@ Line 2: / Line 2: @@
 ==Number series wrap and overlap==
-In 2018, the last used number approached '''Last number''', or 8999999. Passing this would have caused a '''wrap''' of the number series back to the specified '''First number''': 1000001. uniPHARM started with 1000001 when we went live with ASW, so to avoid duplicates and "buy more time", '''First number''' was set to 100001, theoretically yielding 900,000 unused invoice numbers. This wrap was successful.
+In 2018, the number series approached '''Last number''', or 8999999. Passing this would have caused a '''wrap''' of the number series back to the specified '''First number''': 1000001. uniPHARM started with 1000001 when we went live with ASW, so to avoid duplicates and "buy more time", '''First number''' was set to 100001, theoretically yielding 900,000 unused invoice numbers. This wrap was successful.
 In 2021, the series approached '''First number''', which means there would officially be duplication in the system (documents with the same invoice number), or '''overlap'''. Protelo suggested that for ASW files/tables that have invoice number as a column, any keys using the invoice number would use the year as well, meaning the duplication shouldn't be a problem. UNITY tables however, should be checked, as there was likely no specific provision for this condition during database design. The following tables to monitor have been identified:
@@ Line 10: / Line 10: @@
 ! Table name !! Field name (invoice number field) !! Notes !! Overlap prevention
 |-
-| UZIVLIP || Example || Set invoice number to 0. ||
+| UZIVLIP || Example || - || -
 |-
-| NCHEADP || Example || Example ||
+| NCHEADP || NSINV# || - || -
 |}

← Older revision		Revision as of 19:05, 20 May 2021
Line 1:		Line 1:
		+	Invoice numbers are generated/maintained through ''ASW Number Series'' which keeps track of the last used invoice and auto-increments these numbers.
⚫	==Invoice Numbers - Estimated to Wrap in 2018==
		+
		+	==Number series wrap and overlap==
		+	In 2018, the last used number approached '''Last number''', or 8999999. Passing this would have caused a '''wrap''' of the number series back to the specified '''First number''': 1000001. uniPHARM started with 1000001 when we went live with ASW, so to avoid duplicates and "buy more time", '''First number''' was set to 100001, theoretically yielding 900,000 unused invoice numbers. This wrap was successful.
		+
		+	In 2021, the series approached '''First number''', which means there would officially be duplication in the system (documents with the same invoice number), or '''overlap'''. Protelo suggested that for ASW files/tables that have invoice number as a column, any keys using the invoice number would use the year as well, meaning the duplication shouldn't be a problem. UNITY tables however, should be checked, as there was likely no specific provision for this condition during database design. The following tables to monitor have been identified:
		+
		+	{\| class="wikitable"
		+	\|-
		+	! Table name !! Field name (invoice number field) !! Notes !! Overlap prevention
		+	\|-
		+	\| UZIVLIP \|\| Example \|\| Set invoice number to 0. \|\|
		+	\|-
		+	\| NCHEADP \|\| Example \|\| Example \|\|
		+	\|-
		+	\| NCDETP \|\| Example \|\| Example
		+
		+	\|}
		+
		+	==Archive==
		⚫	===Invoice Numbers - Estimated to Wrap in 2018===

	We started in 2005 with an invoice number of 1000001, and credit note number of 3000001. On June 5, 2009 invoice numbers passed 3000000 and duplicated the credit note numbers. ASW was fine, as it accesses files by invoice number / type (1-invoice, 2-credit note) / year. The extensions were not. We quickly changed them to use the same key structure - after changing the next invoice number (in the number series table) to 5000001.		We started in 2005 with an invoice number of 1000001, and credit note number of 3000001. On June 5, 2009 invoice numbers passed 3000000 and duplicated the credit note numbers. ASW was fine, as it accesses files by invoice number / type (1-invoice, 2-credit note) / year. The extensions were not. We quickly changed them to use the same key structure - after changing the next invoice number (in the number series table) to 5000001.

@@ Line 5: / Line 5: @@
 When the invoice number reaches 8999999 it will go back to 1000001.  I don't think anything will happen - but keep an eye on it just in case.
-In order to monitor the process, get the current invoice number (series INV) from the [[Table Maintenance Programs|Document Number Series Table]], and add it to this document.
+In order to monitor the process, get the current invoice number (series INV) from the [[Table Maintenance Programs|Document Number Series Table]], and periodically add it to this document.
 Dec 16     8078278