Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Unknown macro: {noprint}
Unknown macro: {float}

Contents

Change log:

Date:

Author:

Version:

Changes:

Completed

Ext.

Int.

Is in Core

Jira Ref.

Unknown macro: {page-info}
Unknown macro: {page-info}

0.1

Doc. created

No


x

Not yet

CDRP-5829 and CDRP-6067

Page under construction!!!

Purpose of This Document

To give an overview of subscription campaign sharing.

What is Subscription Campaign Sharing?

A subscription campaign (SC) is a relation, which tells you that a specific instance of a subscription is associated with a specific instance of a campaign.

In the CDRator system it is possible to share SCs. This means that after a SC has been created, the instance of the campaign can be set up to be usable by other entities than the subscription itself.

Sharing Methods

We have currently two methods for sharing a SCs

  • Shared Service sharing
  • Subscription Campaign Member sharing.

For more detailed information about each method, see [Billing:Shared Campaigns].

Sharing Groups Types

A SC can be shared with a Sharing Group Type. Currently we have defined that the following can be a Sharing Group Type:

  • Subscription
  • Billing Group
  • Account

A SC can be shared as many times as you like, and with as many different Sharing Groups Type as you like.

A SC is always used by a subscription in the rating process. This means that if you specify a SC to be shared with either a billing group or an account, then you actually mean that the SC is shared with all subscriptions under that billing group/account.

A subscription can only ever use the same instance of a campaign once for each time you rate a billing record or a fee. This means that even though a SC has been shared with both the billing group and the account that a specific subscription belongs to, then the subscription only get to use the campaign instance once for each object that is rated (and belongs to the subscription).

Each of the two Sharing Methods we have in our system supports all three Sharing Groups Types.

  • No labels