The Business Travel is used to add business travel/trip records to the Equus Platform in bulk. We added a new import to support adding business trip moves, destination records, and activities.
Overview
This is only available at the company level. To use the import, make sure the import should be active. Standard conventions for this sort of import apply, including (but not limited to):
This supports recordIdentifier=True. This will be used to match the Employee record. We do not want to create duplicate Employees
When lookupValue=True, this will look for CLASSIFICATION!DISPLAY_VALUE and will match on display value
When lookupValue=False, this will look for CLASSIFICATION!CODE
The import will INSERT for each row, group by Assignment Identifier if that exists
Everything is case Insensitive.
A blank column means “do not touch”. It does NOT mean “blank out”
The magic value <BLANK> means “save NULL to this column.”
Blank lines above the header row are skipped without error.
Each row of data is processed in a separate transaction.
If one row errors, execution proceeds to the next row.
Specific Field Requirements/Sample File
User should not have to include MOVE_TYPE as a column in the import. Import should always use Move Type = Business Trip
The import supports fields from the following tables. Note, specific supported fields are documented here:
Employee (Supports UPSERT only)
Assignment (Supports INSERT only)
Assignment Destination (Supports INSERT only)
Assignment Destination Activity (Supports INSERT only)
These fields are built out to support 5 activities
Data will be added to the import horizontal so we will have 5 columns for activity code and 5 columns for number of days. We will store the activity data vertically so if you have data for 3 columns of activities we would expect 3 rows of data get created on the activity table (ASSIGNMENT_DESTINATION_ACTIVITY)
The import does not support fields related to Assignment Destination Assessment
This also supports the Assignment Identifier field. Pick any value you like (alphanumeric), but make sure that every row of data that should serve as an update to this newly-created mobility record has the same value in this column, and that no row of data that should update a different assignment has this same value. This will allow you to link multiple destination records to one business trip move type record. You should fill this in for all lines of the import or leave this blank for all line of this import. You can refer to the Employee Assignment Flexible Header import on how this works.
We allow importing a new assignment and multiple new assignment destination records for that assignment within one single import file. The assignment destination record could have up to 5 activities that will be supported in the import
Every row in import will support a new assignment and assignment destination record unless you have Assignment Identifier
Activity will need to support columns with numbers for record count in horizontal column
Support up to 5 activities
Activities will be stored vertical in the database
Although Activity is not needed for PWN filing, this is a field that is needed for the Assessment