Table of Contents | ||||
---|---|---|---|---|
|
Capability
This Import allows Users to Import Usage records and is functionally similar to the Calls Import.
The resulting usage will appear in the Usage Details and Usage Detail ErrorsĀ grids.
Matches On
Usage matches on the Service ID field.
...
You can also provide an Alias value of an existing Service. The provided Alias value must exactly match the format in the Alias record.
Service RECID
Datatype is Number.
Default is blank.
This is used to specify the Service Record for Services that have a blank Service ID.
If this is provided, the provided value must be a valid existing Service RECID.
If it is not, it will cause an error.
If a Service RECID value is provided, the Service ID field will be ignored.
Bill Date
Datatype is String.
...
Default value is blank.
Usage Date/Time
Requiredif Usage Date and Usage Time are not provided.
...
An error occurred during the Import File Processing. This re-tries each night.
Toggle cloak |
---|
Cloak |
---|
|
Unrecoverable Errors
An error occurred that cannot be fixed. It does not try again each night.
Toggle cloak |
---|
Cloak |
---|
|
Rating Errors
An error during the rating process. This re-tries each night.
Toggle cloak |
---|
Cloak |
---|
|
Billing Errors
Indicates an error occurred during the billing process.
Toggle cloak |
---|
Cloak |
---|
|
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.
...