The SY_User Table contains the User Created Key that is the Unique Identifier for Sage 100 Users; this has nothing to do with a "Employee Maintenance" data table, but with the Sage 100 Logon.  

Sequence Keys are part of the Primary Key, and when all other elements are the same, the Sequence Number gives the record the added element to be different.  As an example, in JT_Transaction, the primary key is SO Number: WTNumber: WTStep: RecordType: TransactionDate: SequenceNo.  If you make two status changes on the same step on the same date, they would be Sequence 000000 and Sequence 000001.

The SY_User Table contains the User Created Key that is the Unique Identifier for Sage 100 Users; this has nothing to do with a "Employee Maintenance" data table, but with the Sage 100 Logon.  

Sequence Keys are part of the Primary Key, and when all other elements are the same, the Sequence Number gives the record the added element to be different.  As an example, in JT_Transaction, the primary key is SO Number: WTNumber: WTStep: RecordType: TransactionDate: SequenceNo.  If you make two status changes on the same step on the same date, they would be Sequence 000000 and Sequence 000001.

So just to confirm, the sequence number will only go up if all the fields including the userkey are the same?

So the same person/login would have to edit the same SO, WT, and Step on the same day and that would cause the sequence number to go up?