Quarantine/Service Feature Quarantine - Revision history

Scarpenter: /* Resolution: Unable to ascertain price */

2016-12-06T03:42:21Z

‎Resolution: Unable to ascertain price

Scarpenter at 06:20, 17 November 2016

2016-11-17T06:20:30Z

Scarpenter at 03:54, 17 November 2016

2016-11-17T03:54:35Z

Scarpenter: /* Resolution: Unable to ascertain price */

2016-11-17T03:53:53Z

‎Resolution: Unable to ascertain price

Scarpenter at 03:53, 17 November 2016

2016-11-17T03:53:09Z

Scarpenter: /* Overview */

2016-11-17T03:50:30Z

‎Overview

Scarpenter: Created page with "{{DISPLAYTITLE:Service Feature Quarantine}} = Overview = The Service feature Quarantine page will report on service feature subscriptions which are currently unable to be bill..."

2016-11-17T03:38:51Z

Created page with "{{DISPLAYTITLE:Service Feature Quarantine}} = Overview = The Service feature Quarantine page will report on service feature subscriptions which are currently unable to be bill..."

New page

{{DISPLAYTITLE:Service Feature Quarantine}}
= Overview =
The Service feature Quarantine page will report on service feature subscriptions which are currently unable to be billed because:

* a price cannot be found; or
* a product rate card is not assigned to the service plan related to the service feature or the service feature subscription period.

Unlike BMS and MISC usage where we are able to programmatically ascertain issues with records, service feature subscriptions are different in that they are recurring subscriptions versus an individual usage record. As such, they are handled slightly differently.

Thye system will automatically try to process these records every 3 days. The next scheduled retry is displayed in the '''Retry After''' column. Repair the underlying issue, and the system will retry in due course and process the usage without the user having to manually cleanse, as they do with telephony or other quarantine. If users want the system to re-try these record can be flagged and manually removed from quarantine. In this case, the system will retry immediately.

To access this screen:

Nav: '''Billing > Quarantine > Service Feature'''

[[File: Quarantine-service-feat-main.png|1200px|The Service Feature Quarantine page in Cumulus]]

==Reason: Unable to ascertain price==
Here is an example of how to investigate and resolve the issues where the reason is ''Unable to ascertain price''. In this example we will focus on this record from the screenshot above.

[[file: 01-record-for-cleanse.png|1200px|Record to be investigated and resolved]]

Since there is no ID for the product rate card, we will use the service plan ID to view the service plan. We also want to note the Product ID. This will be used to add a rate to the product in the product rate card.

Go to '''Packages and Plans > Management > Service Plans''' and find the service plan. Be sure to include both BUY and SELL plans in your search.

[[file: 02-find-service-plan.png|1200px|Search for the service plan]]

Click the ID of the service plan to open and inspect it. Being that service feature prices are stored within Product Rate Cards, you will also want to review the '''Associated Product Rate Cards''' tab.

[[file: 03-inspect-service-plan.png|1200px|Inspect the service plan]]

There are two issues immediately evident that shows this service plan is not configured correctly.
* There is no Associated Product Rate Card. It is mandatory for all service plans to have a product rate card.
* The status of the service plan is '''Draft''', despite having a '''saleable from''' date.

How this mis-configuration occured is out of scope of this article. This article will focus soley on resolving the problem so that the quarantined records can be processed.

As this is a BUY service plan for the ''AAPT IP-Line (Auth)'' service type, we will look for an appropriate BUY product rate card to link. In this scenario we will use the AAPT Broadband BUY product rate card pictured below.

[[file: 04-inspect-prc.png|1200px|Inspect the product rate card]]

Upon inspection, this product rate card:
* has no product rates in it. This is why the system could not find a price.
* is in a status of DRAFT.

In summary, to be able to remove from quarantine and retry pricing the service feature with success, the configuration must be corrected as follows;
# Ensuring that the product rate card has a price for the service feature.
# Setting the ''Date Effective'' date on the associated product rate card so that rating engine can process the usage. Usage received before the ''Date Effective'' date cannot be rated.
# Setting the product rate card is in a useable state.
# Associating the BUY product rate card to the service plan.
# Setting the service plan to saleable state.

When creating a new rate, use the Product ID from the Service Feature Quarantine page to easily search for the product that needs a price.

Here is the product rate card with updated configuration.

[[file: 05-adjusted-prc.png|1200px|Adjusted product rate card with the price for the service feature]]

Here is the service plan updated to have the product rate card associated and now in a usable status. Note that when associating the product rate card ensure the ''Date Effective'' date covers the date the usage was received. If the usage was received before this date, Emersion's rating system cannot process the usage and it will fall back into quarantine. Usage that cannot be rated at all must be written off.

[[file: 06-adjusted-service-plan.png|1200px|Adjusted service plan with product rate card]]

Once the adjustments have been made, users have one of two options:

# Wait for the system to automatically retry processing.
# Remove the record from quarantine which will push it back to Retry queue.

=See Also=
* [[Quarantine|Quarantine Main Page]]
* [[Account_Management/Customer_Screen/Service_Subscriptions/Feature_Management|Service Feature Management]]
* [[Account_Management/Customer_Screen/Service_Subscriptions/Service_Feature_History|Service Feature History]]

@@ Line 25: / Line 25: @@
 == Access Control ==
-Access to the Service Feature Quarantine page can be controlled via the '''Service Feature Quarantine'''. Enabling this power will grant users full access to the page.
+Access to the Service Feature Quarantine page can be controlled via the '''Service Feature Quarantine''' power. Enabling this power will grant users full access to the page.
 == Resolution: Unable to ascertain price ==

@@ Line 22: / Line 22: @@
 # Select ''Remove'' from the '''Update To''' field.
 # Press '''Submit'''.
 == Resolution: Unable to ascertain price ==

@@ Line 74: / Line 74: @@
 Here is the product rate card with updated configuration.
 [[file: 05-adjusted-prc.png|1200px|Adjusted product rate card with the price for the service feature]]
 Here is the service plan updated to have the product rate card associated and now in a usable status.  Note that when associating the product rate card ensure the ''Date Effective'' date covers the date the usage was received. If the usage was received before this date, Emersion's rating system cannot process the usage and it will fall back into quarantine. Usage that cannot be rated at all must be written off.
 [[file: 06-adjusted-service-plan.png|1200px|Adjusted service plan with product rate card]]
 Once the adjustments have been made, users have one of two options:
 # Remove the record from quarantine which will push it back to Retry queue.
 =See Also=

@@ Line 13: / Line 13: @@
 Nav: '''Billing > Quarantine > Service Feature'''
 [[File: Quarantine-service-feat-main.png|1200px|The Service Feature Quarantine page in Cumulus]]
@@ Line 28: / Line 29: @@
 == Resolution: Unable to ascertain price ==
 This section contains an example of how to investigate and resolve issues where the reason is ''Unable to ascertain price''. We will focus on this record from the screenshot above.
 [[file: 01-record-for-cleanse.png|1200px|Record to be investigated and resolved]]
@@ Line 35: / Line 37: @@
 Go to '''Packages and Plans > Management > Service Plans''' and find the service plan. Be sure to include both BUY and SELL plans in your search.
 [[file: 02-find-service-plan.png|1200px|Search for the service plan]]
@@ Line 40: / Line 43: @@
 Click the ID of the service plan to open and inspect it. Being that service feature prices are stored within Product Rate Cards, you will also want to review the '''Associated Product Rate Cards''' tab.
 [[file: 03-inspect-service-plan.png|1200px|Inspect the service plan]]
@@ Line 51: / Line 55: @@
 As this is a BUY service plan for the ''AAPT IP-Line (Auth)'' service type, we will look for an appropriate BUY product rate card to link. In this scenario we will use the AAPT Broadband BUY product rate card pictured below.
 [[file: 04-inspect-prc.png|1200px|Inspect the product rate card]]
@@ Line 69: / Line 74: @@
 Here is the product rate card with updated configuration.
 [[file: 05-adjusted-prc.png|1200px|Adjusted product rate card with the price for the service feature]]

@@ Line 1: / Line 1: @@
 {{DISPLAYTITLE:Service Feature Quarantine}}
 = Overview =
-The Service feature Quarantine page will report on service feature subscriptions which are currently unable to be billed because:
+The service feature quarantine page will report on service feature subscriptions which are currently unable to be billed because:
 * a price cannot be found; or
 * a product rate card is not assigned to the service plan related to the service feature or the service feature subscription period.
-Unlike BMS and MISC usage where we are able to programmatically ascertain issues with records, service feature subscriptions are different in that they are recurring subscriptions versus an individual usage record. As such, they are handled slightly differently.
+Unlike BMS and MISC usage where we are able to ascertain issues with records, service feature subscriptions are different in that they are recurring subscriptions versus an individual usage record. The differences mean that processing of the settings is different to that of usage.
-Thye system will automatically try to process these records every 3 days. The next scheduled retry is displayed in the '''Retry After''' column. Repair the underlying issue, and the system will retry in due course and process the usage without the user having to manually cleanse, as they do with telephony or other quarantine. If users want the system to re-try these record can be flagged and manually removed from quarantine. In this case, the system will retry immediately.
+The system will automatically try to process these records every 3 days. The next scheduled retry is displayed in the '''Retry After''' column. Repair the underlying issue, and the system will retry without the user having to manually 'cleanse' records from quarantine like with telephony or other usage. If users want the system to instigate a retry outside of the automatic schedule, the record can be flagged and removed from quarantine. In cases where manual removal occurs, the system will retry immediately.
 To access this screen:
@@ Line 16: / Line 16: @@
 [[File: Quarantine-service-feat-main.png|1200px|The Service Feature Quarantine page in Cumulus]]
-==Reason: Unable to ascertain price==
+== Manual Removing and Retrying ==
-Here is an example of how to investigate and resolve the issues where the reason is ''Unable to ascertain price''. In this example we will focus on this record from the screenshot above.
+To manually remove a record from service feature quarantine:
 [[file: 01-record-for-cleanse.png|1200px|Record to be investigated and resolved]]