Difference between revisions of "Quarantine/Non Existent Service"
(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...") |
(added common non existent service fault reasons. See https://resources.emersion.com/display/OPS/Reasons+for+Non+Existent+Service+Fault) |
||
| (One intermediate revision by one other user not shown) | |||
| 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. | 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. | 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 | * Data BMS | ||
* Misc BMS | * Misc BMS | ||
| + | |||
| + | == Cleansing a Single Record == | ||
| + | |||
| + | Use the search criteria to search for usage records that have been quarantined. Once the service has been entered into the system, you can attempt to process the usage by ticking the box on the far-right of the usage record, selecting ''Update To'' to '''Cleanse''' and pressing '''Submit'''. | ||
| + | |||
| + | == 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'''. | ||
| + | |||
| + | == Possible Non Existent Service Reasons == | ||
| + | Note: Some of these reasons will not be able to be checked by you, but will give you some guidance as to what to check and would could prevent a usage record from matching a service correctly. If further assistance is required, please [[Support and help from Emersion|submit a support request]]. | ||
| + | |||
| + | * A Package Subscription at one or more tiers is not active. (''Can partially be checked via the UI'') | ||
| + | * A Service Subscription at one or more tiers is not active. (''Can partially be checked via the UI'') | ||
| + | * A Service at one more tiers is not active. (''Can partially be checked via the UI'') | ||
| + | * The Service is end dated. (''Can be checked via the UI'') | ||
| + | * The Start Date on the Package Subscription, the Service Subscription, the Service, or the service identifier does not cover the date of the usage. (''Can be checked via the UI'') | ||
| + | * The Service Identifier does not match that of the service identifier which the carrier has sent through. (''Can be checked via the UI'') | ||
| + | * The Service Identifier is end dated. (''Can be checked via the UI'') | ||
| + | * The Service Type Category of the service does not match that service type category on the mediated tariff. | ||
| + | * The Service Identifier record has a realm attached, however the usage record does not contain the realm in question. (''Can be partially checked via the UI'') | ||
=See Also= | =See Also= | ||
* [[Account_Management/Customer_Screen/Service_Subscriptions|The Service Subscription tab]] | * [[Account_Management/Customer_Screen/Service_Subscriptions|The Service Subscription tab]] | ||
Latest revision as of 11:49, 6 February 2017
Contents
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
Cleansing a Single Record
Use the search criteria to search for usage records that have been quarantined. Once the service has been entered into the system, you can attempt to process the usage by ticking the box on the far-right of the usage record, selecting Update To to Cleanse and pressing Submit.
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.
Possible Non Existent Service Reasons
Note: Some of these reasons will not be able to be checked by you, but will give you some guidance as to what to check and would could prevent a usage record from matching a service correctly. If further assistance is required, please submit a support request.
- A Package Subscription at one or more tiers is not active. (Can partially be checked via the UI)
- A Service Subscription at one or more tiers is not active. (Can partially be checked via the UI)
- A Service at one more tiers is not active. (Can partially be checked via the UI)
- The Service is end dated. (Can be checked via the UI)
- The Start Date on the Package Subscription, the Service Subscription, the Service, or the service identifier does not cover the date of the usage. (Can be checked via the UI)
- The Service Identifier does not match that of the service identifier which the carrier has sent through. (Can be checked via the UI)
- The Service Identifier is end dated. (Can be checked via the UI)
- The Service Type Category of the service does not match that service type category on the mediated tariff.
- The Service Identifier record has a realm attached, however the usage record does not contain the realm in question. (Can be partially checked via the UI)
