Western Digital Archibus Synchronizations
The RSC SQL Automation Engine runs your employee sync to update ARCHIBUS from source data. This document is a summary of your employee sync and related automations.
Data Imports
Data Source
Source Type:
Location: \\RSC-FILE\FILEMANAGER\WDC\SFTP\client_fm_target\ILMFeedForArchibus.txt
Details: Daily file drop off via SFTP
Notes: Created by ILM – After processing file renamed and left in folder
Scheduled: Daily (7 days) 5:40pm PST
Log emailed to: notify@rsc2lc.com
Employee Sync
Master Function: EMSYNC
Data Path: ILM -> rsc_emsource table -> rsc_emdown table -> em table
Note: data follows this path as it is formatted for the appropriate field. Before running the emsource and emdown tables are cleared of all previous data. All data from the source is first pulled into the emsource table.
Scheduled: Daily (7 days) 2:00am PST
Sync Log emailed to: notify@rsc2lc.com, cafmappsupport@wdc.com
ILM |
EMSOURCE |
EMDOWN |
EM |
Updated if changed in source? |
employeeID |
Field1 |
Emnumber |
Em_number |
yes |
FirstName |
Field2 |
Firstname prefname |
Name_first name_pref |
Yes no |
LastName |
Field3 |
Lastname |
Name_last |
yes |
Field 2 + Field 3 + Field 1 |
Combinedname |
Em_id |
no |
|
Title |
Field4 |
Jobtitledown |
Job_title |
yes |
DepartCode |
Field5 |
Team |
Rsc_team_id |
yes |
DepartmentName |
Field6 |
Team_name |
(populates team table) |
yes |
IsManager |
Field7 |
Option2 |
Is_manager |
yes |
WorkPhone |
Field8 |
Phonedown |
phone |
yes |
IPPhone |
Field9 |
Extensiondown |
extension |
yes |
|
Field10 |
Emaildown |
|
yes |
EmployeeType |
Field11 |
Emstddown |
Em_std |
yes |
Grade |
Field12 |
(not used) |
yes |
|
HireDate |
Field13 |
Date_hire |
Date_hired |
yes |
EndDate |
Field14 |
(not used) |
yes |
|
EmployeeStatus |
Field15 |
Statusdown |
status |
yes |
ManagerEmployeeID |
Field16 |
Manageriddown |
Mgr_number |
yes |
ManagerName |
Field17 |
Managerdown |
Mgr_name |
yes |
Country |
Field18 |
Pers_area |
Pers_area |
yes |
LocationName |
Field19 |
Pers_area_sub |
Pers_area_sub |
yes |
CostCenter |
Field20 |
(not used) |
yes |
|
CostCenterName |
Field21 |
(not used) |
yes |
|
CloudDeptId |
Field22 |
Department |
Dp_id |
yes |
CloudDeptIdDescr |
Field23 |
depname |
(populates department table) |
yes |
Employee Seating Automation
Automatically assigns employees to buildings based on the mapping from their pers_area_sub (LocationName) to the building code in the rsc_translation table. Also populates floor if building only has one floor.
Note: This mapping is not complete, so not all employees can be seated automatically. The main goal is to seat direct labor this way, which is why direct/indirect labor information has been requested in employee source.
Scheduled: Daily (7 days) 4:00am PST
Function: EMSEAT
New Hire Moves Created
When a new employee is added to the database (update_type = new) a new hire move is created for them.
Scheduled: part of the employee sync
Function: EM_TO_MO_NEW
Em |
Mo |
Em_id |
Em_id |
Date_hired |
Date_to_perform |
Pers_area_sub |
To_location |
Dv_id |
To_dv_id |
Dp_id |
To_dp_id |
Move_type = New Hire |
Note on “Insert Only” – these fields are populated when the record is created. If they are changed the automation does not update them back.
User Records Created
When a new employee is added to the database (update_type = new) a user record is created for them.
Master Function: WC_USERS_SYNC
Scheduled: Daily (7 Days) 3:00am PST
Log emailed to: notify@rsc2lc.com
Em |
Afm_users |
Updated if changed in source? |
Net_user_name |
User_name |
Yes |
|
|
Yes |
User_level set to 0 |
Insert only |
|
User_pwd set to NO_PASSWORD |
Insert only |
|
Role_name set to WDC GENERIC USER |
Insert only |
|
Sync_status set to 1 (update) |
Insert only |
Note on “Insert Only” – these fields are populated when the record is created. If they are changed the automation does not update them back.
Employee Deletion
Deletion criteria: employee is no longer in sync file for 3 sync cycles – this is referred to as “not found in source file”.
Manual Employees: Sync ignores all employees who have a sync mode of “no update”.
Deletion action:
- Not in source first time sync runs: update type set to “delete”
- Not in source second time sync runs: update type set to “deleted”
- Not in source third time sync runs: employee is archived to the hem (historical employee) table and removed from the employee table.
Notification or approval for deletion: None
Leaving Moves Created
When a new employee is removed from the database a leaving move is created for them.
Scheduled: part of the employee sync
Function: EM_TO_MO_LEAVE
Em |
Mo |
Em_id |
Em_id |
Bl_id |
From_bl_id |
Fl_id |
From_fl_id |
Rm_id |
From_rm_id |
manager |
Mo_coord |
Move_type = Leaving |
Cloud Department Updates
Note: We are not currently receiving division information
New Department: If a department in the employee source is new it will be inserted into the dp table.
- Approval required for insertion: no
Updated Department Name: If the name of a department changes it will be updated in the dp tables.
- Approval required for update: no
Employee Standard Updates
New Employee Standard: If an employee standard the employee source is new it will be inserted into the emstd table.
- Approval required for insertion: no
Data Exports
Employee Data Export
Source Type:
Location: \\RSC-FILE\FILEMANAGER\WDC\SFTP\client_source\em_export.csv
Details: Daily file drop off to SFTP, to be picked up by WD
Notes: Archived to “old” folder each day
Scheduled: Daily (7 days) 3:30am PST
Log emailed to: notify@rsc2lc.com, cafmappsupport@wdc.com
Em table |
Export Field Order |
em_number |
field1 |
name_first |
field2 |
name_last |
field3 |
job_title |
field4 |
rsc_team_id |
field5 |
is_manager |
field6 |
phone |
field7 |
extension |
field8 |
|
field9 |
em_std |
field10 |
date_hired |
field12 |
mgr_number |
field15 |
bl_id |
field17 |
fl_id |
field18 |
rm_id |
field19 |
pers_area_sub |
field21 |
em_id |
field22 |
Data Warehouse Integration
All Archibus data is available to the data warehouse team through a direct read-only database connection.
More information: https://knowledgebase.rsc2lc.com/wd-direct-database-read-only-access-for-reporting/
Was this helpful?
0 / 0