Cost Estimate/Compensation Calculation Templates can be migrated from the system level or company level and created at the system level or company level.
Excluding Large Spreadsheets
When ‘Cost Estimate/Compensation Calculation Template’ is selected from the ‘Migration Package Type’ dropdown, a field for ‘Max Spreadsheet Size (MB)’ will appear. The purpose of this field is to provide the user with a method of preventing very large spreadsheet calculation files from being included in the Migration Package (often large spreadsheet files can cause the migration process to time out).
When this field is blank or is set to ‘0’, the migration package will attempt to migrate all spreadsheets in the template.
If during the migration the user encounters a timeout error, or if prior to a migration they believe the package is large enough that an error is likely, they may enter a number in this field. This will exclude any spreadsheets larger than the indicated max size from the migration package. This number can be a decimal value to exclude files smaller than 1MB. Upon import, users are notified when a spreadsheet is excluded so that it can be added manually.
Line Items Not Supported (the Line Item will be created and set but will need to be manually verified for correctness):
Comp Worksheet Line Item Type
Custom Calc (Old) Type
Additional Considerations:
System & Company Template
If Target Cost Estimate ID is not supplied and a template with the same name already exists, the package will fail.
If Target Cost Estimate ID is supplied but does not exist in the target system, the package will fail.
Always verify the target Template ID. If a target Cost Estimate Template ID is specified, the package will overwrite all information, even if you were to accidentally put the wrong the ID in and the templates are nothing alike.
Custom Calculations
If a company-level template that uses spreadsheet calculations is being migrated to the target system as a system-level template, the template will not be added if the spreadsheet does not exist and the user will get an error message. Spreadsheet Calculations are not supported at the system level.
The Migration Package will only try to add spreadsheet calculations that it identifies are not already in the system. Spreadsheet calculations will never be updated through a Migration Package Import; If a spreadsheet calculation import is attempted and on already exists in the system with the same name, the calculation will not be added.
Custom Field and Section
Custom fields at both the header and line item level are copied over. However, if the target system is not configured to show those fields, they will not be displayed.
Custom sections and sub sections will be looked up by name. If the section is not found, it will be defaulted to Base Compensation. If a subsection cannot be found, it will be defaulted to nothing.
If the Annual Increase Percentage Start Month is not one of the Equus provided codes, it will be defaulted to January.
Tax Position Set
If a Tax Position Set does not exist in the target system, a new Tax Position Set will be created.
If a Tax Position Set does exist in the target system, the migrated package will associate that set with the template. Changes made to an existing set will not be updated in the target system.
What-If Cost Estimate Template
Header fields (checkboxes and Alias) are copied over.
Associated Reports and Parameters for WICE templates are matched on report number and parameter ID in the target system. If they cannot be matched, then the parameter will not be migrated and an error message will appear.
When a parameter is assigned a custom code and custom group code, the migration package will match to classification description and display value. If more than one matching classification group is present in the target system, or if the classification group cannot be found then the parameter will not be migrated and the user will be messaged.
If the classification code for a parameter is inactive on the target system, then the parameter will not be migrated and the user will be messaged.
Text parameter values are copied over.
Cost Estimate Line Items for What-If Cost Estimate templates are matched on definition name.
Line-item defaults are mapped to the corresponding line items in the target system.
Updates are carried over to the target system.
If a line item is inactive in the target system then it will not be migrated and the user will be messaged.
If there are multiple default inputs within one line item calculation, only one default will migrate over and the user will be messaged.
Things to Note
The Migration Package attempted to match Calculations by the name as it is stored in the Compensation Calculation table. If it finds a match, it uses that in the target system and assumes that it's correct.
Expense Accounts are matched on Account number and Sub-Account number (if one is specified) in the target system. If it cannot be located then it will not be added and the user will be messaged.