Home > System Admin Role > Links & Integrations > xSage > xSage HRMS
xSage HRMS
Cyber Train and Sage HRMS can be connected so that when employees who are hired, terminated or have a job change Cyber Train will be updated with the information and the training profile can be adjusted. There two utilities (Direct or Web API) for both SQL and FoxPro.
Check the Sage Release Notes to see what changes have been made in Cyber Train or executables that work with Cyber Train.
If one would like additional resources to help with Sage integrations, check out the Sage Abra SQL HRMS Guides and/or Sage Knowledgebase.
What fields are transferred/updated
What is the difference between new employees and employee updates
Frequently Asked Questions
Back to the Top
In order for the two systems talk with each other, certain fields/codes need to match. When the below information matches, as employees are added or updated in the Sage HRMS, the information is added or updated in Cyber Train.
| Cyber Train Field |
Sage HRMS Field |
| Job Codes |
Job Title / Job Code |
| Employee Type |
Employment Type |
| Organization 1 |
Organizational Level 1 |
| Organization 2 |
Organizational Level 2 |
| Organization 3 |
Organizational Level 3 |
| Organization 4 |
Organizational Level 4 |
| Organization 5 |
Organizational Level 5 |
Direct Connection (SQL/FoxPro)
DOB, FirstName, MiddleName, LastName, StudentType, HomeStreet1, HomeStreet2, City, State, Zip, HomePhone, WorkPhone, WorkExt, CellPhone, WorkEmail, Empno, SSN, HireDate, EmployeeType, Company, IsEmployee (always defaults to Y), IsSupervisor, Supervisor, Supervisor2, NickName, ActiveStatus, JobCode, JobStartDate, Org1, Org2, Org3, Org4, Org5, OrgStartDate (same as HireDate)
Web Services (SQL/FoxPro)
DOB, FirstName, MiddleName, LastName, StudentType, HomeStreet1, HomeStreet2, City, State, Zip, HomePhone, WorkPhone, WorkExt, CellPhone, WorkEmail, Empno, SSN, HireDate, EmployeeType, Company, IsEmployee (always defaults to Y), IsSupervisor, Supervisor, Supervisor2, NickName, ActiveStatus, JobCode, JobStartDate, Org1, Org2, Org3, Org4, Org5, OrgStartDate (same as JobStartDate), CTLoginField (according to what you chose in the Link setup utility)
Back to the Top
The program scrolls through each employee found in Sage HRMS and it checks Cyber Train to see if the person already exists by comparing 'P_EMPNO' and 'P_COMPANY' in Sage HRMS to the 'EMPNO' field and 'Company Code' fields in Cyber Train. Additionally, everything is driven by the P_ACTIVE field in Sage HRMS. Thus, if an employee's P_ACTIVE field equals 'T', then the Employee is added as 'I' for 'Inactive' into Cyber Train. If the employee is anything other than a 'T,' the employee is added as 'A' for 'Active' into Cyber Train.
If the employee DOES NOT exist in Cyber Train, the employee is considered new and is added. A new employee (new student) added to the system creates a historical record in Cyber Train – Student File > History Page to read ‘Employee Imported from Abra Suite'. It adds the student with the job title, organization codes, supervisor information as it is listed in Sage HRMS. Additionally, if the job and organization codes have requirements attached them in Cyber Train, the outstanding requirements are added too.
If the employee DOES exist in Cyber Train, the employee is updated in Cyber Train where the fields are different between the two systems. This applies to all fields that can be transferred as employees change jobs, organization levels, employee type, etc... within a company. The exception to this are employees who have 'Termed' status in SageHRMS for more than 30 days. They will not be considered.
Back to the Top
When to use the Direct connection versus the Web API connection?
The Direct connection is used when the Sage HRMS and Cyber Train are on the same server. This allows one to enter the FoxPro or SQL information to connect the two databases together. However, should the systems be in different location such that one has his/her Cyber Train system hosted with Visibility Software and has the Sage HRMS system on site, the Web API connection is the route to go so that the two systems can talk to each other.
Can the utility filter information out?
The system does not filter anything out by default. There is a place for custom advanced criteria on the utility setup page. To enter custom advanced criteria contact Visibility Software Support to see if what is needed is possible.
Can organization codes be added to Cyber Train when the utility runs?
This is possible with the Web API connection only and when the codes in SageHRMS are located at the Company/Employer level (not the Enterprise level). If the organization codes are set to sync, the organization codes in Sage HRMS are created in Cyber Train > Codes > Organization to keep everything the same and then is added to the employee's record in Cyber Train – Student File > Contact Info Page > Job Detail Tab. Additionally, the ‘Original Hire Date’ field in Sage HRMS is added as the ‘Organization Start Date’ in Cyber Train.
Can job codes be added to Cyber Train when the utility runs?
This is possible with both the Direct and Web API connections and when the codes in SageHRMS are located at the Company/Employer level (not the Enterprise level). If the job codes are set to sync, the job codes in Sage HRMS are created in Cyber Train > Codes > Job Titles to keep everything the same and then is added to the employee's record in Cyber Train – Student File > Contact Info Page > Job Detail Tab. Additionally, the P_JOBDATE field in Sage HRMS is added as the ‘Job Start Date’ in Cyber Train.
How is the supervisor information transferred?
The utility looks to see who the employee's supervisor and secondary supervisor are in Sage HRMS and updates the 'Supervisor' and 'Secondary Approver' fields respectively in Cyber Train as long as everyone is in the same company code.
See also
|