x Want to participate? Join the group to interact
Options
  • State Verified Answer
  • Replies 3 replies
  • Subscribers 107 subscribers
  • Views 741 views
  • Users 0 members are here
Browse Forums
Announcements
293
topics
370
replies
Business Object Interface
1k
topics
7k
replies
Core Financial Modules
2k
topics
8k
replies
Customization and Productivity
3k
topics
12k
replies
Distribution, Manufacturing, and Applications
2k
topics
7k
replies
General Discussion
1k
topics
3k
replies
Partner Cloud
45
topics
91
replies
Payroll, Time Tracking, and Job Cost
777
topics
1k
replies
Reporting and Analytics
962
topics
3k
replies
Sage CRM for Sage 100
164
topics
357
replies
Technical and Installation
2k
topics
9k
replies
Year-end Forum
89
topics
237
replies
Jimmy Vi

Location of UserUpdatedKey/UserCreatedKey and How SequenceNo is picked?

SOLVED
Posted By

Hi,

I am looking at our backend tables and I am trying to determine what user did what.

In our worktickets I see UserCreatedKey and UserUpdatedKey but I cannot find a table that links those to the employees table.

I read that they might be stored in CI_Item because that links to SY_User.M4T but in our case they aren't. Any ideas on where I should look?

I am also trying to determine how Sage chooses the SequenceNo so that I can understand what is going on better so any information on that would be great too!

Thanks in advance!

  • +1
    verified answer

    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.

  • 0

    The SY_User table will have the UserKey field that will help you match up the UserCreatedKey and UserUpdatedKey.

  • 0 in reply to StefanouM

    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?

*Community Hub is the new name for Sage City