The Import screen on the Rates & Rules > Bulk Rate Update > Import screen features search options that allow you to search for a Bulk Rate Import batch that you have submitted so that you can check if the batch has completed processing. Using these search options, you can also list and see details about historic batches that have been processed in the past.
...
Status | Description |
In Progress | Indicates that the batch has been created and has began processing but is yet to be completed. |
Completed | Indicates that the batch has completed processing and all rates that were included in the imported file were updated successfully. |
Completed with Exceptions | Indicates that the batch has completed processing successfully but some rates in the import file could not be updated due to exceptions (for more information, see Validation Errors & Exceptions) |
Rates Import Failed Due to an Exception | Indicates that the batch completed processing but no rates could be updated due to exceptions (for more information, see Validation Errors & Exceptions) |
File Validation Failed | Indicates that the batch completed processing but no rates could be updated because one or more mandatory columns in the imported file was blank or contained data in an unexpected format (for more information, see Validation Errors & Exceptions) |
Failed | Indicates that the batch could not be processed due to a system error or network outage or similar. Note that if a batch fails, you can upload the same updated rates file to attempt the bulk rate update again. |
...
Exception Message
...
Actions
...
The ID provided in the PayBillRateRuleId column does not match an existing pay rate rule. The ID in the import file has been edited or the original pay rate rule no longer exists in the agreement.
...
Check that the rate rule has not been removed from the corresponding agreement. If not, export the agreement rates again to a new Bulk Rate Update file so that the correct ID is generated and import the new file.
...
The ID provided in the PayBillRateRuleId column does not match an existing pay rate sub-rule on the corresponding pay rate rule. The ID in the import file has been edited or the original pay rate sub rule no longer exists in the agreement.
...
Check that the sub-rule has not been removed from the pay rate rule. If not, export the agreement rates again to a new Bulk Rate Update file so that the correct ID is generated and import the new file.
...
A rate effective date must be provided in the NewValidityStartDate column.
...
In the exception file, key in the missing date in the NewValidityStartDate column, save the file and import the updated file.
...
The date in the NewValidityStartDate column cannot be the same or lower than the validity start date of the exported validity period.
...
Change the date in the NewValidityStartDate column to a date that is later than the date in the ValidityStartDate column, save the file and import the updated file.
...
The date in the NewValidityStartDate column cannot be after the agreement header validity end date.
...
Change the date in the NewValidityStartDate column to a date that falls within the validity period of the corresponding agreement.
...
A pay rate rule already exists on the corresponding pay agreement on the date specified in the NewValidityStartDate column for the same hierarchy level/hierarchy value/hierarchy group/pay code combination.
...
Check that the date provided in the NewValidityStartDate column is correct. If necessary, change the date, save the file and import the update file.
...
Rates linked to the same pay rate rule cannot have different dates specified in the NewValidityStartDate column.
...
Change the date in the NewValidityStartDate column for each row in the exception file that corresponds to the same rate rule to be the same date, save the file and import the updated file.
...
The date in the NewValidityStartDate column must be greater than the last timesheet end date of the pay agreement.
...
Change the date in the NewValidityStartDate column to a date that is later than the date in the LastTimesheetEndDate column, save the file and import the updated file.
...
The NewRate column cannot contain a value because the rate type is Direct Valuation or Payee Rate.
...
Delete the value in the NewRate column, save the file and import the updated file.
...
The NewRate column must contain a value.
...
Key in a pay rate or pay value in the NewRate column, save the file and import the updated file.
...
The NewRateDescription column cannot contain more than 60 characters.
...
Shorten the rate description that is keyed in the NewRateDescription column so that it is no more than 60 characters (including spaces), save the file and import the updated file.
...
The NewRateDescription column must be blank because the pay rate rule is flagged as Calculation Only.
...
Delete the text in the NewRateDescription column, save the file and import the updated file.
...
The corresponding pay agreement is currently included in an open Back Pay batch and could not be updated.
...
Close the relevant Back Pay batch in Rates and Rules before trying to import the exception file again.
...
The corresponding rate rule cannot be updated because there is already a later validity period for the rate rule.
To update the rate rule, export the latest validity period.
...
Check if the updated rate rule already exists on the corresponding agreement. If not, export the rates for that agreement to a new Bulk Rate Update file, making sure that the date you specify in the Rate Valid On or After Date field on the Export tab of the Bulk Rate Update screen is set to a date that is late enough to pick up the last, open-ended set of rates for the corresponding agreement.
...
The NewRateMinimum field cannot contain a value because the rate type is Direct Valuation.
...
Delete the value in the NewRateMinimum column, save the file and import the updated file.
...
The NewRateMinimum field cannot contain a value because the rate type is Payee.
...
Delete the value in the NewRateMinimum column, save the file and import the updated file.
...
The NewRateMinimum field cannot contain a value because the rate type is Calculation.
...
Delete the value in the NewRateMinimum column, save the file and import the updated file.
...
The NewRateMinimum field cannot contain a non-numeric value.
...
Change the value that has been keyed in the NewRateMinimum column so that it does not contain any alphabetical characters, save the file and import the update file.
...
The NewRateMinimum field cannot contain a value because the rate is a top up rate.
...
Delete the value in the NewRateMinimum column, save the file and import the updated file.
...
The NewRateDescription field cannot contain a value because the rate is a top up rate.
...
Delete the value in the NewRateDescription column, save the file and import the updated file.
...
Exception Message
...
Action
...
The ID provided in the BillRateRuleId column does not match an existing bill rate rule. The ID in import file has been edited or the original bill rate rule no longer exists on the bill agreement.
...
Check that the rate rule has not been removed from the corresponding agreement. If not, export the agreement rates again to a new Bulk Rate Update file so that the correct ID is generated and import the new file.
...
The ID provided in the BillRateSubRuleId column does not match an existing bill rate sub rule on the corresponding bill rate rule. The ID in the import file has been edited or the original bill rate sub rule no longer exists on the bill agreement.
...
Check that the sub-rule has not been removed from the bill rate rule. If not, export the agreement rates again to a new Bulk Rate Update file so that the correct ID is generated and import the new file.
...
A rate effective date must be provided in the NewValidityStartDate column.
...
In the exception file, key in the missing date in the NewValidityStartDate column, save the file and import the updated file.
...
The date in the NewValidityStartDate column cannot be the same or lower than the validity start date of the exported validity period.
...
Change the date in the NewValidityStartDate column to a date that is later than the date in the ValidityStartDate column, save the file and import the updated file.
...
The date in the NewValidityStartDate column cannot be after the agreement header validity end date.
...
Change the date in the NewValidityStartDate column to a date that falls within the validity period of the corresponding agreement.
...
A bill rate rule already exists on the corresponding bill agreement on the date specified in the NewValidityStartDate column for the same hierarchy level/hierarchy value/hierarchy group/bill code combination.
...
Check that the date provided in the NewValidityStartDate column is correct. If necessary, change the date, save the file and import the update file.
...
Rates linked to the same bill rate rule cannot have different dates specified in the NewValidityStartDate column.
...
Change the date in the NewValidityStartDate column for each row in the exception file that corresponds to the same rate rule to be the same date, save the file and import the updated file.
...
The date in the NewValidityStartDate column must be greater than the last timesheet end date of the bill agreement.
...
Change the date in the NewValidityStartDate column to a date that is later than the date in the LastTimesheetEndDate column, save the file and import the updated file.
...
The NewRate column cannot contain a value because the margin/markup type is Use Other Rate Dollar Margin.
...
Delete the value in the NewRate column, save the file and import the updated file.
...
The NewRate column must contain a value.
...
Key in a pay rate or pay value in the NewRate column, save the file and import the updated file.
...
The NewRate field cannot contain a value because the rate rule uses a Bill Rate Formula.
...
Delete the value in the NewRate column, save the file and import the updated file.
...
The corresponding rate rule cannot be updated because there is already a later validity period for the rate rule.
To update the rate rule, export the latest validity period.
...
Check if the updated rate rule already exists on the corresponding agreement. If not, export the rates for that agreement to a new Bulk Rate Update file, making sure that the date you specify in the Rate Valid On or After Date field on the Export tab of the Bulk Rate Update screen is set to a date that is late enough to pick up the last, open-ended set of rates for the corresponding agreement.
...
The BillRateFormulaID column must contain an integer.
...
Export the rates for the corresponding agreement again to a new Bulk Rate Update file, update the file as required and import the updated file.
...
The ID provided in the BillRateFormulaId field does not match an existing formula. The ID in the import file has been edited or the formula no longer exists.
...
Export the rates for the corresponding agreement again to a new Bulk Rate Update file, update the file as required and import the updated file.
...
The NewBillRateFormula field cannot be blank because the margin/markup type of the rate rule is BillRateFormula.
...
Key in a valid bill rate formula name in the NewBillRateFormula column, save the file and import the updated file.
...
The value specified in the NewBillRateFormula field does not match an existing bill rate formula name in Rates and Rules maintenance.
...
Check that the name of the bill rate formula in the NewBillRateFormula column matches the name of a bill rate formula that exists in Rates and Rules maintenance. If not, change the name in the NewBillRateFormula column to the name of a valid, existing bill rate formula, save the file and import the updated file.
...
The NewBillFormula field must be blank because the margin/markup type of the rate rule is not BillRateFormula.
...
Delete the value that has been keyed in the NewBillRateFormula column, save the file and import the updated file.
...
the |
...
bulk |
...
Exception Message
Action
The ID provided in the StandardRateHeaderId column does not match an existing standard rates header. The ID in the import file has been edited or the original standard rates header no longer exists.
Export the rates again to a new Bulk Rate Update file so that the correct ID is generated and import the new file. If the exception still occurs, the standard rates header no longer exists.
The ID provided in the StandardRateId column does not match the ID of any pay and bill rates for the standard rates header that is identified in the StandardRateHeaderId column. The ID in the import file has been edited or the original standard rates header no longer exists.
Export the rates again to a new Bulk Rate Update file so that the correct ID is generated and import the new file. If the exception still occurs, the pay/bill rate combination linked to the identified standard rates header may have been deleted since the rates were originally exported to the Bulk Rate Update file.
The ID provided in the PayBillRuleId column does not match the ID of the pay rate that is identified in the StandardRateId column. The ID in the import file has been edited or the pay rate no longer exists for the pay and bill rate combination identified in the StandardRateId column.
Export the rates again to a new Bulk Rate Update file so that the correct ID is generated and import the new file. If the exception still occurs, the pay/bill rate combination linked to the identified standard rates header may have been deleted since the rates were originally exported to the Bulk Rate Update file.
The ID provided in the BillRateRuleId column does not match the ID of the pay rate that is identified in the StandardRateId column. The ID in the import file has been edited or the bill rate no longer exists for the pay and bill rate combination identified in the StandardRateId column.
Export the rates again to a new Bulk Rate Update file so that the correct ID is generated and import the new file. If the exception still occurs, the pay/bill rate combination linked to the identified standard rates header may have been deleted since the rates were originally exported to the Bulk Rate Update file.
A rate effective date must be provided in the NewValidityStartDate column.
In the exception file, key in the missing date in the NewValidityStartDate c olumn, save the file and import the updated file.
The date in the NewValidityStartDate column cannot fall within the date range of an existing rate set validity period.
In the exception file, change the date in the NewValidityStartDate column to a date that is after the date in the ValdityStartDate field, save the file and import the updated file.
The date in the NewValidityStartDate column cannot fall outside the start and end dates of the job order.
In the exception file, change the date in the NewValidityStartDate column to a date that is no later than the end date of the corresponding job order, save the file and import the updated file.
The date in the NewValidityStartDate column cannot fall on or before the last timesheet end date for the job order.
In the exception file, change the date in the NewValidityStartDate column to a date after the date in the LastTimesheetEndDate column, save the file and import the updated file.
Rates linked to the rate set cannot have different dates specified in the NewValidityStartDate column.
In the exception file, change the date in the NewValidityStartDate column for each row that corresponds to the same rate set so that the date is the same in each of those respective rows, save the file and import the updated file.
The NewPayRate column cannot contain a value because the pay rate is flagged as Direct Valuation.
In the exception file, delete the value in the NewPayRate column, save the file and import the updated file.
The NewPayRate column cannot be blank.
In the exception file, key a value in the NewPayRate column, save the file and import the updated file.
The NewPayRate column cannot contain more than 60 characters.
In the exception file, edit the text in the NewPayRate column so that it is no longer than 60 characters in length.
The NewBillValue column cannot be blank.
In the exception file, key a value in the NewBillValue column, save the file and import the updated file.
The NewBillValue field cannot contain a value because the rate rule uses a Bill Rate Formula.
Delete the value in the NewBillValue column, save the file and import the updated file.
rate |
To
update |
again |
The BillRateFormulaID column must contain an integer.
Export the rates for the corresponding agreement again to a new Bulk Rate Update file, update the file as required and import the updated file.
The ID provided in the BillRateFormulaId field does not match an existing formula. The ID in the import file has been edited or the formula no longer exists.
Export the rates for the corresponding agreement again to a new Bulk Rate Update file, update the file as required and import the updated file.
The NewBillRateFormula field cannot be blank because the bill type of the rate rule is BillRateFormula.
Key in a valid bill rate formula name in the NewBillRateFormula column, save the file and import the updated file.
The value specified in the NewBillRateFormula field does not match an existing bill rate formula name in Rates and Rules maintenance.
Check that the name of the bill rate formula in the NewBillRateFormula co lumn matches the name of a bill rate formula that exists in Rates and Rules maintenance. If not, change the name in the NewBillRateFormula c olumn to the name of a valid, existing bill rate formula, save the file and import the updated file.
The NewBillFormula field must be blank because the bill type of the rate rule is not BillRateFormula.
. |