.Usage Imports v2019.7

Capability

This Import allows Users to Import Usage records and is functionally similar to the Calls Import .

Matches On

Usage matches on the Service ID field.

Fields

Service ID

Required

Datatype is String.

Default value is blank.

Bill Date

Datatype is String.

Default value is blank.

Cost

Datatype is String.

Default value is blank.

Description

Datatype is String.

Default value is blank.

Quantity

Datatype is String.

Default value is blank.

Service Type

Datatype is String.

Default value is blank.

A Service record must exist for each Usage record.

The Service can exist as any Service Type.

If the Import Format specifies a particular service type, only services from that type will be considered in the Service ID lookup.

Usage Time

Data type is String.

Default value is blank.

Usage Date

Data type is String.

Default value is blank.

Usage Date/Time

Data type is String.

Default value is blank.

Usage Type

Data type is String.

Default value is blank.

Permitted values are from the USAGE_TYPE List Values: Data Storage or Bandwidth

Child Records

There are no Child records on Usage records.

Flags / Conditional Logic

There are no current Conditional Logic flags for the Usage import.

Errors

Because of the very large volume of Imported data that can occur for Calls and Usage Imports, the Error reporting is done very differently. For other Imports, if an Error happens, the Error is reported in the Imported Records grid. For Calls and Usage, the Error is stored as a code in the Call or Usage record. The available codes are in this list. This list is shared for Calls and Usage. Some of these are specifically for Calls and never happens for Usage.

Errors

An error occurred during the Import File Processing. This re-tries each night.

Unrecoverable Errors

An error occurred that cannot be fixed. It does not try again each night.

Rating Errors

An error during the rating process. This re-tries each night.

Billing Errors

Indicates an error occurred during the billing process.

Notes

• A Service must exist for each Usage record.
• The Service can exist as any Service type.
• If the Import Format specifies a particular Service Type, only Services from that type is considered in the Service ID lookup.

UDF Associations

UDFs cannot be associated with Usage records.