Sage 100

Unofficially and from testing only here is what I have found:

Sage assigns a new work ticket key by looking at the PM_WorkTicketHistoryHeader and finds the Highest key value in that table and does some sort of increment to get the next key.

The problem I have seen is if a work ticket converted where the work order number in legacy version has an alpha character, then the key assigned during data conversion is also alfa. So the highest key value in work ticket history table is Alpha and then Sage gets really crazy key values going forward.

For one client we found this out during testing so prior to go live, after converting data they had about 30 work orders that converted to alpha keys and they were all "test" work orders. So I used data file display and maintenance to delete those before they created any new work tickets. And then Sage used all numeric keys going forward.

For the record I HATE that the WorkTickeKey field even exists and wish that had never been added. Ther may be a valid reason for that field, but I have not found a reason

Unofficially and from testing only here is what I have found:

Sage assigns a new work ticket key by looking at the PM_WorkTicketHistoryHeader and finds the Highest key value in that table and does some sort of increment to get the next key.

The problem I have seen is if a work ticket converted where the work order number in legacy version has an alpha character, then the key assigned during data conversion is also alfa. So the highest key value in work ticket history table is Alpha and then Sage gets really crazy key values going forward.

For one client we found this out during testing so prior to go live, after converting data they had about 30 work orders that converted to alpha keys and they were all "test" work orders. So I used data file display and maintenance to delete those before they created any new work tickets. And then Sage used all numeric keys going forward.

For the record I HATE that the WorkTickeKey field even exists and wish that had never been added. Ther may be a valid reason for that field, but I have not found a reason

Unofficially and from testing only here is what I have found:

Sage assigns a new work ticket key by looking at the PM_WorkTicketHistoryHeader and finds the Highest key value in that table and does some sort of increment to get the next key.

The problem I have seen is if a work ticket converted where the work order number in legacy version has an alpha character, then the key assigned during data conversion is also alfa. So the highest key value in work ticket history table is Alpha and then Sage gets really crazy key values going forward.

For one client we found this out during testing so prior to go live, after converting data they had about 30 work orders that converted to alpha keys and they were all "test" work orders. So I used data file display and maintenance to delete those before they created any new work tickets. And then Sage used all numeric keys going forward.

For the record I HATE that the WorkTickeKey field even exists and wish that had never been added. Ther may be a valid reason for that field, but I have not found a reason

Unofficially and from testing only here is what I have found:

Sage assigns a new work ticket key by looking at the PM_WorkTicketHistoryHeader and finds the Highest key value in that table and does some sort of increment to get the next key.

The problem I have seen is if a work ticket converted where the work order number in legacy version has an alpha character, then the key assigned during data conversion is also alfa. So the highest key value in work ticket history table is Alpha and then Sage gets really crazy key values going forward.

For one client we found this out during testing so prior to go live, after converting data they had about 30 work orders that converted to alpha keys and they were all "test" work orders. So I used data file display and maintenance to delete those before they created any new work tickets. And then Sage used all numeric keys going forward.

For the record I HATE that the WorkTickeKey field even exists and wish that had never been added. Ther may be a valid reason for that field, but I have not found a reason

Unofficially and from testing only here is what I have found:

Sage assigns a new work ticket key by looking at the PM_WorkTicketHistoryHeader and finds the Highest key value in that table and does some sort of increment to get the next key.

The problem I have seen is if a work ticket converted where the work order number in legacy version has an alpha character, then the key assigned during data conversion is also alfa. So the highest key value in work ticket history table is Alpha and then Sage gets really crazy key values going forward.

For one client we found this out during testing so prior to go live, after converting data they had about 30 work orders that converted to alpha keys and they were all "test" work orders. So I used data file display and maintenance to delete those before they created any new work tickets. And then Sage used all numeric keys going forward.

For the record I HATE that the WorkTickeKey field even exists and wish that had never been added. Ther may be a valid reason for that field, but I have not found a reason

I agree Kevin, the problem is that instead of just starting the work ticket key at 000000000001 and incrementing during the conversion of work order to Production Management, they used the work ticket number as the key and then going forward after the conversion Sage is using the highest key in history and incrementing that to the next key.  I had one client that had created some test work orders using ZZZ0001 and that created keys that start with ZZZ and then some strange set of spaces and numbers behind it so new work tickets created after the upgrade stare with ZZZ and more cryptic values. 

You're correct that at this point it is what it is. But what it is, is not ideal to say the least.

Unofficially and from testing only here is what I have found:

Sage assigns a new work ticket key by looking at the PM_WorkTicketHistoryHeader and finds the Highest key value in that table and does some sort of increment to get the next key.

The problem I have seen is if a work ticket converted where the work order number in legacy version has an alpha character, then the key assigned during data conversion is also alfa. So the highest key value in work ticket history table is Alpha and then Sage gets really crazy key values going forward.

For one client we found this out during testing so prior to go live, after converting data they had about 30 work orders that converted to alpha keys and they were all "test" work orders. So I used data file display and maintenance to delete those before they created any new work tickets. And then Sage used all numeric keys going forward.

For the record I HATE that the WorkTickeKey field even exists and wish that had never been added. Ther may be a valid reason for that field, but I have not found a reason

I agree Kevin, the problem is that instead of just starting the work ticket key at 000000000001 and incrementing during the conversion of work order to Production Management, they used the work ticket number as the key and then going forward after the conversion Sage is using the highest key in history and incrementing that to the next key.  I had one client that had created some test work orders using ZZZ0001 and that created keys that start with ZZZ and then some strange set of spaces and numbers behind it so new work tickets created after the upgrade stare with ZZZ and more cryptic values. 

You're correct that at this point it is what it is. But what it is, is not ideal to say the least.

Unofficially and from testing only here is what I have found:

Sage assigns a new work ticket key by looking at the PM_WorkTicketHistoryHeader and finds the Highest key value in that table and does some sort of increment to get the next key.

The problem I have seen is if a work ticket converted where the work order number in legacy version has an alpha character, then the key assigned during data conversion is also alfa. So the highest key value in work ticket history table is Alpha and then Sage gets really crazy key values going forward.

For one client we found this out during testing so prior to go live, after converting data they had about 30 work orders that converted to alpha keys and they were all "test" work orders. So I used data file display and maintenance to delete those before they created any new work tickets. And then Sage used all numeric keys going forward.

For the record I HATE that the WorkTickeKey field even exists and wish that had never been added. Ther may be a valid reason for that field, but I have not found a reason

I agree Kevin, the problem is that instead of just starting the work ticket key at 000000000001 and incrementing during the conversion of work order to Production Management, they used the work ticket number as the key and then going forward after the conversion Sage is using the highest key in history and incrementing that to the next key.  I had one client that had created some test work orders using ZZZ0001 and that created keys that start with ZZZ and then some strange set of spaces and numbers behind it so new work tickets created after the upgrade stare with ZZZ and more cryptic values. 

You're correct that at this point it is what it is. But what it is, is not ideal to say the least.

Unofficially and from testing only here is what I have found:

Sage assigns a new work ticket key by looking at the PM_WorkTicketHistoryHeader and finds the Highest key value in that table and does some sort of increment to get the next key.

The problem I have seen is if a work ticket converted where the work order number in legacy version has an alpha character, then the key assigned during data conversion is also alfa. So the highest key value in work ticket history table is Alpha and then Sage gets really crazy key values going forward.

For one client we found this out during testing so prior to go live, after converting data they had about 30 work orders that converted to alpha keys and they were all "test" work orders. So I used data file display and maintenance to delete those before they created any new work tickets. And then Sage used all numeric keys going forward.

For the record I HATE that the WorkTickeKey field even exists and wish that had never been added. Ther may be a valid reason for that field, but I have not found a reason

I agree Kevin, the problem is that instead of just starting the work ticket key at 000000000001 and incrementing during the conversion of work order to Production Management, they used the work ticket number as the key and then going forward after the conversion Sage is using the highest key in history and incrementing that to the next key.  I had one client that had created some test work orders using ZZZ0001 and that created keys that start with ZZZ and then some strange set of spaces and numbers behind it so new work tickets created after the upgrade stare with ZZZ and more cryptic values. 

You're correct that at this point it is what it is. But what it is, is not ideal to say the least.

I agree Kevin, the problem is that instead of just starting the work ticket key at 000000000001 and incrementing during the conversion of work order to Production Management, they used the work ticket number as the key and then going forward after the conversion Sage is using the highest key in history and incrementing that to the next key.  I had one client that had created some test work orders using ZZZ0001 and that created keys that start with ZZZ and then some strange set of spaces and numbers behind it so new work tickets created after the upgrade stare with ZZZ and more cryptic values. 

You're correct that at this point it is what it is. But what it is, is not ideal to say the least.

Unofficially and from testing only here is what I have found:

Sage assigns a new work ticket key by looking at the PM_WorkTicketHistoryHeader and finds the Highest key value in that table and does some sort of increment to get the next key.

The problem I have seen is if a work ticket converted where the work order number in legacy version has an alpha character, then the key assigned during data conversion is also alfa. So the highest key value in work ticket history table is Alpha and then Sage gets really crazy key values going forward.

For one client we found this out during testing so prior to go live, after converting data they had about 30 work orders that converted to alpha keys and they were all "test" work orders. So I used data file display and maintenance to delete those before they created any new work tickets. And then Sage used all numeric keys going forward.

For the record I HATE that the WorkTickeKey field even exists and wish that had never been added. Ther may be a valid reason for that field, but I have not found a reason

I agree Kevin, the problem is that instead of just starting the work ticket key at 000000000001 and incrementing during the conversion of work order to Production Management, they used the work ticket number as the key and then going forward after the conversion Sage is using the highest key in history and incrementing that to the next key.  I had one client that had created some test work orders using ZZZ0001 and that created keys that start with ZZZ and then some strange set of spaces and numbers behind it so new work tickets created after the upgrade stare with ZZZ and more cryptic values. 

You're correct that at this point it is what it is. But what it is, is not ideal to say the least.

Unofficially and from testing only here is what I have found:

Sage assigns a new work ticket key by looking at the PM_WorkTicketHistoryHeader and finds the Highest key value in that table and does some sort of increment to get the next key.

The problem I have seen is if a work ticket converted where the work order number in legacy version has an alpha character, then the key assigned during data conversion is also alfa. So the highest key value in work ticket history table is Alpha and then Sage gets really crazy key values going forward.

For one client we found this out during testing so prior to go live, after converting data they had about 30 work orders that converted to alpha keys and they were all "test" work orders. So I used data file display and maintenance to delete those before they created any new work tickets. And then Sage used all numeric keys going forward.

For the record I HATE that the WorkTickeKey field even exists and wish that had never been added. Ther may be a valid reason for that field, but I have not found a reason