Quarantine/Non Existent Service - Revision history

Dcowan: added common non existent service fault reasons. See https://resources.emersion.com/display/OPS/Reasons+for+Non+Existent+Service+Fault

2017-02-06T01:49:56Z

added common non existent service fault reasons. See https://resources.emersion.com/display/OPS/Reasons+for+Non+Existent+Service+Fault

Scarpenter at 23:07, 29 November 2016

2016-11-29T23:07:28Z

Scarpenter: Created page with "{{DISPLAYTITLE:Quarantine: Non Existent Service}} = Overview = This page displays quarantined usage records grouped by service. The view aims to assist users quickly identify..."

2016-11-29T22:56:32Z

Created page with "{{DISPLAYTITLE:Quarantine: Non Existent Service}} = Overview = This page displays quarantined usage records grouped by service. The view aims to assist users quickly identify..."

New page

{{DISPLAYTITLE:Quarantine: Non Existent Service}}
= Overview =
This page displays quarantined usage records grouped by service. The view aims to assist users quickly identify which services and service identifiers need to be entered into the system in order for the usage to be processed.
The system will attempt to find a matching service from the usage record. Where a potential match is found, the potential service ID will be displayed. Users will still need to act upon any changes necessary to services before cleansing the quarantine in order for the usage to be processed.

'''!Important:Cleansing a collection of usage records for a given service will cleanse any other collection of usage records listed for the same service identifier.'''

Emersion can and does sometimes receive usage for the same identifier from two different carriers. For example when the service is shifted from one carrier or supplier to another. In these cases, the system will attempt to retrieve carrier based on the service type, then carrier. Should this fail, the system will attempt to retrieve it from the tariff and lastly based on the connector used when parsing the batch.

To access this screen:

Nav: '''Billing > Non Existent Service'''

There are 3 sub tabs for users to review quarantined usage by service

* Telephony BMS
* Data BMS
* Misc BMS

=See Also=
* [[Account_Management/Customer_Screen/Service_Subscriptions|The Service Subscription tab]]

@@ Line 24: / Line 24: @@
 == Cleansing Multiple Records ==
 If multiple usage records are quarantined for the same service, an easy way to cleanse all the usage pertaining to that specific service is to search on the service identifier to return all usage records with that service identifier. Tick the box at the top of the far-right column to choose all records in the list. ''Update To'' '''Cleanse''', and press '''Submit'''.
 =See Also=
 * [[Account_Management/Customer_Screen/Service_Subscriptions|The Service Subscription tab]]

@@ Line 4: / Line 4: @@
 The system will attempt to find a matching service from the usage record. Where a potential match is found, the potential service ID will be displayed. Users will still need to act upon any changes necessary to services before cleansing the quarantine in order for the usage to be processed.
-'''!Important:Cleansing a collection of usage records for a given service will cleanse any other collection of usage records listed for the same service identifier.'''
+'''!Important: Cleansing a collection of usage records for a given service will cleanse any other collection of usage records listed for the same service identifier.'''
 Emersion can and does sometimes receive usage for the same identifier from two different carriers. For example when the service is shifted from one carrier or supplier to another. In these cases, the system will attempt to retrieve carrier based on the service type, then carrier. Should this fail, the system will attempt to retrieve it from the tariff and lastly based on the connector used when parsing the batch.
@@ Line 17: / Line 17: @@
 * Data BMS
 * Misc BMS
 =See Also=
 * [[Account_Management/Customer_Screen/Service_Subscriptions|The Service Subscription tab]]