Back to Subscription Main Page

Table of Contents

Navigating to Subscription Definitions

CONFIGURATION > BILLING APPLICATION > SUBSCRIPTIONS > SET UP BUSINESS DEFINITIONS

What are Subscription Definitions?

A Subscription Definition is a set of business rules and conditions which are used to create and maintain Subscriptions throughout their Life Cycle. For example, through the Subscription Definitions, you can define the maximum number of Subscriptions you can have per account or the maximum number of Main Services and Physical products that can be added to a Subscription.
Subscription Definitions provide a number of restrictions and controls and can be used to define product dependencies. For example, a rule can be set where additional channels cannot be added unless one of the Main channels is added first.

Subscription Definitions can be edited, deleted and have their Life Cycle State changed.

Navigate to Subscription Definitions and explore existing entries via the Summary page.
Click on the link (Name or Number) of the entry of your interest to access the Data Entry page and see more detail.
Use the Actions Menu to create a NEW Definition, modify (EDIT), or DELETE an existing one.
Use BACK to return to the Summary page and CANCEL to revert any unwanted changes made to the Definition.
Click on the Audit Log button to view a log of changes performed on the displayed Subscription Definition.

Check the Validations & Restrictions Table below for a list of available Actions when working with Subscriptions, including each Action's related validations and restrictions.View the Attributes Table for a comprehensive description of the Subscription Definition fields.

Validations & Restrictions

Action	Validations	Restrictions
Create	Mandatory Fields must be defined Name and Alternative Code must beunique	Not Applicable
Edit	Mandatory Fields must be defined Name and Alternative Code must beunique	Not Applicable
Delete	Not Applicable	Cannot be deleted if its the 'Active' Definition

Attributes

An * indicates a field is mandatory

Name

Description

Main Information

Name*

The name of the Definition.

Description

A description of the Definition.

Alternative Code*

The alternative code of the Definition. Unless otherwise specified, the Alternative Codes for new entries default to the Name initials in capital letters.

State

The state of the Definition which can be 'Active' or 'Inactive'. Only one Definition can be 'Active' at any given time.

Subscription Rules

Restrictions

Subscription Restrictions control the number of Subscriptions that can be owned by the same Accounts Receivable, based on a set of rules. The criteria that can be used to build each rule include the following:

Subscription Criteria
- Subscription Type
- Subscription Life Cycle State
Criteria for each Accounts Receivable
- The Accounts Receivable Classification
- The Accounts Receivable Credit rating
Maximum Number of Subscriptions: The maximum number of Subscriptions meeting the Subscription Criteria, allowed to be created per Accounts Receivable meeting the Accounts Receivable Criteria

In the following example the System is set to allow:

1 Subscription per Accounts Receivable with Employee Classification
3 Subscriptions per Accounts Receivable with Residential Classification
5 Subscriptions per Accounts Receivable regardless of the account's Classification

Service Rules

Restrictions

Service Restrictions

Service Restrictions control the number of Services that can be added either to one or all Subscriptions owned by the same Accounts Receivable.

Scope: The scope by which the conditions will be set.
- "Subscription": The rule will apply to the Services of a single Subscription.
  or
- "Accounts Receivable": The rule will apply to the sum of the Services of all the Subscriptions owned by the Accounts Receivable.
Restrictions:
- Minimum number of mandatory Services that should exist
- Maximum number of mandatory Services that should exist.
- Minimum number of optional Services that should exist.
- Maximum number of optional Services that should exist.

Dependencies

Service Dependencies

Service Dependencies control the Type of Services that can co-exist either on a Subscription or Subscriptions owned by the same Accounts Receivable.

Product or Product Type: Must be either Termed Services or Expenses.
Scope: The scope by which the conditions will be set.
- "Subscription": The rule will apply to Services of a single Subscription.
  or
- "Accounts Receivable": The rule will apply to the Services of all the Subscriptions owned by the Accounts Receivable.
Type of Prerequisites, can be one of the following:
- Services (Only Termed Services and Expense are allowed to be added to the list).
- Service Types (Only Termed Services and Expense are allowed to be added to the list).
- Traceable Physical Goods.
- Traceable Physical Good Types.
Prerequisites: Up to 10 Prerequisites can be added from the same Type. There is also the option to define whether all the specified values or if at least one of the values should be present.

Restrictions Per Distributor

Service Restrictions Per Distributor

Service Restrictions per Distributor control the number of Services that can be distributed by each Provisioning Distributor.

Provisioning Distributor: The Provisioning Distributor on which the restrictions should be applied.
Restrictions:
- Minimum number of mandatory Services that should exist.
- Maximum number of mandatory Services that should exist.
- Minimum number of optional Services that should exist.
- Maximum number of optional Services that should exist.

Dependencies Per Distributor

Service Dependencies Per Distributor

Service Dependencies Per Distributor control the Services that can be distributed on the same Provisioning Distributor.

Provisioning Distributor: The Distributor on which the dependency rules should be applied.
Type of Prerequisites, can be one of the following:
- Services (Only Termed Services and Expense are allowed to be added to the list).
- Service Types (Only Termed Services and Expense are allowed to be added to the list).
Prerequisites: Up to 10 Prerequisites can be added from the same Type. There is also the option to define whether all the specified values or if at least one of the values should be present.

Tiers

Tiers

Tiers are directly related to the Subscription Action 'Swap Services' and determine the swaps that can take place between Subscription Services and provides information on the Type of modification (i.e. if it constitutes an upgrade or downgrade).
Subscription Service Tiers aretwo dimensional; the first dimension is the Tier Level and the second dimension is the Tier Path.

The Path defines a set of Subscription Services, which can replace each other. Subscription Services can be replaced only by other Services under the same Path.
The Level characterises the replacement (i.e. if it constitutes an upgrade or downgrade) and is defined within each Tier Path.

Tier Paths can be related to a single root Path, in which case, the System will suggest replacements of Subscription Services belonging to a child Path, whenever a Subscription Service of the same Level is replaced.

Example

Level	Path 1 Not following any Path Root Path of Path 2	Path 2 Following: Path 1 Child Path of Path1	Path 3 Not following any Path
10	A1	B1	C1
20	A2	B2	C2
30	A3	B3
40		B4
40		B5

Based on the Subscription Service Tiers specified above the following events can take place:

A1, A2, A3 can replace each other.
B1, B2, B3, B4 can replace each other.
C1, C2 can replace each other.
Going from A1 to A2 or A3 is considered as a downgrade.
Going from A3 to A2 or A1 is considered as an upgrade.
Going from B4 to B5 and vice versa is considered a swap.
If a Subscription has A1, B1 and C1 then a change from A1 to A2 will suggest a change from B1 to B2, but it will not suggest a change from C1 to C2.

Based on the Subscription Service Tiers specified above the following events cannot take place:

Subscription Services belonging to Path 1 cannot replace or be replaced by a Subscription Service belonging to Path 2 or Path 3
Subscription Services belonging to Path 2 cannot replace or be replaced by a Subscription Service belonging to Path 1 or Path 3
Subscription Services belonging to Path 3 cannot replace or be replaced by a Subscription Service belonging to Path 1 or Path 2

Installed Item Rules

Restrictions

Installed Item Restrictions

Installed Item Restrictions control the number of Installed Items that can be added either to one or all Subscriptions owned by the same Accounts Receivable.

Scope: The scope by which the conditions will be set.
- "Subscription": The rule will apply to Installed Items of a single Subscription.
  or
- "Accounts Receivable": The rule will apply to the sum of the Installed Items of all the Subscriptions owned by the Accounts Receivable.
Physical Good Type: The Traceable Physical Good Type on which the restrictions for the number of the Installed Items will be applied.
Restrictions:
- Minimum number of Installed Items that should exist per traceable Physical Good Type.
- Maximum number of Installed Items that should exist per traceable Physical Good Type.

Dependencies

Installed Item Dependencies

Installed Item Dependencies control the Type of Installed Item that can co-exist either on a Subscription or Subscriptions owned by the same Accounts Receivable.

Product or Product Type: can only be Traceable Physical Goods.
Scope: The scope by which the conditions for the selected Product or Product Type will be set.
- "Subscription": The rule will apply to Physical Goods of a single Subscription.
  or
- "Accounts Receivable": The rule will apply to the Physical Goods of all the Subscriptions owned by the Accounts Receivable
Type of Prerequisites, can be one of the following:
- Traceable Physical Goods
- Traceable Physical Good Types
Prerequisites: Up to 10 Prerequisites can be added from the same Type. There is also the option to define whether all the specified values or if at least one of the values should be present.

Restrictions Per Distributor

Installed Item Restrictions Per Distributor

Installed Item Restrictions per Distributor control the number of Installed Items that can be distributed by each Provisioning Distributor.

Provisioning Distributor: The Provisioning Distributor on which the restrictions should be applied.
Physical Good Type: The Traceable Physical Good Type on which the restrictions for the number of the Installed Items will be applied.
Restrictions:
- - Minimum number of Installed Items that should exist per traceable Physical Good Type
  - Maximum number of Installed Items that should exist per traceable Physical Good Type

Dependencies Per Distributor

Installed Item Dependencies Per Distributor

Installed Item dependencies per Distributor control the type of Installed Items that can be distributed on the same Provisioning Distributor.

Provisioning Distributor: The Distributor on which dependency rules should be applied.
Type of Prerequisites can be one of the following
- Traceable Physical Goods
- Traceable Physical Good Types
Prerequisites: Up to 10 Prerequisites can be added from the same Type. There is also the option to define whether all the specified values or if at least one of the values should be present.

Log Information

Log Details

The standard set of Log Details information available in all entities.

Related Areas

Page:

Managing Subscriptions
Page:

Using Deactivate Normal Subscriptions Run Definitions
Page:

Scheduling Subscription Actions
Page:

Extending Binding End and Allowed Cancel Dates
Page:

Configuring Subscription Action and Sub Action Types
Page:

Using Execute Scheduled Subscription Actions Run Definitions
Page:

Using Take Subscriptions out of Short Term Deactivation Run Definitions
Page:

Using Deactivate Unsettled Subscriptions Run Definitions
Page:

Using Deactivate Subscriptions in Grace Run Definitions
Page:

Using Take Subscriptions out of Resting Run Definitions
Page:

Using Activate Settled Subscriptions Run Definitions
Page:

Become Subscriber
Page:

Cancel Expense
Page:

Configuring Subscription Definitions
Page:

Configuring Subscription Types

Helpful Links

Page:

CRM.COM Quickstart Manual
Page:

Working with Summary Pages - R18
Page:

Working with Summary Pages
Page:

Working with Summary Pages - R15
Page:

Extracting a Printout from a Data Entry page

Browser not supported