Error messages for usage import failures

This topic provides a complete list of the error messages you might encounter while importing the usage data. For more information about handling import failures, see the Handling Failures section in Import Usage Data and How to handle usage import failure.

The following lists all the error messages for import failures:

• The ACCOUNT_ID is missing

• The ACCOUNT_ID does not match

• The UOM is missing

• The Account status is not active

• The UOM does not match

• File Import Failed: The UOM {} does not match any existing charge

• This usage record has been billed and cannt be updated

• The QTY is missing

• The QTY cannot be less than 0

• The Usage STARTDATE cannot be after the ENDDATE

• The Subscription is not ACTIVE

• Invalid Subscription ID

• Invalid Charge ID

• The Charge is not ACTIVE

• The Charge Type is not Usage

• The Subscription ID and Charge ID do not match

• The Charge and Billing Account do not match

• Failed to import usage: An invalid character (emoticon) was identified

• DESCRIPTION length is longer than the 200 character maximum

• The Usage Quantity exceeds 13 digits before the decimal place, the maximum digits supported by the system

• The Subscription and Billing Account do not match

• The STARTDATE is missing

• The STARTDATE format is invalid

• The CustomFiled {} date format is invalid

• The ENDDATE format is invalid

• The required custom field:{} is missing

• Invalid value for custom field: {}

• The length of the following custom field is longer than its field length: {}

• This row record has been omitted because all values are missing

• Usage cannot be imported into a closed accounting period

• File Import Failed: The unique-keys are the same at rows: {} {}

• The Usage Upload Process was rejected. {} at row: {}

Note: {} indicates the relevant values that will be retrieved and displayed for the specific error.