Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Align/Targeting/CloneMCCycle.htm

## Cloning an MC Cycle

Align operational users can clone an MC Cycle from Align, enabling the creation of new MC Cycles while avoiding inputting all MC Cycle information manually.

For example, the Align operational user is planning for the upcoming cycle period. Since very little has changed from the last cycle period to the next one, they clone the MC Cycle from the previous cycle period to use as a starting point when planning the next cycle.

The clone replicates the mc\_cycle\_\_v record as well as all associated records from the following objects:

* mc\_cycle\_channel\_\_v
* mc\_cycle\_product\_\_v
* aln\_account\_rule\_\_v
* aln\_targeting\_rule\_channel\_\_v
* aln\_targeting\_rule\_product\_\_v
* aln\_account\_rule\_criteria\_\_v

Targets are not cloned.

**Who can use this feature?**

* Align Operational Users - Browser
* [Cloning MC Cycles](#Cloning2)
* [Cloning MC Cycle Feedback](#Clone)
* Users require an Align License

### Configuring Cloning MC Cycles for

[![Closed](../../../../Skins/Default/Stylesheets/Images/transparent.gif)Align Operational Users](#)

To configure this feature, ensure the following features are configured:

* [Configuring Align](../Configuration/ConfiguringAlign.htm)
* [Modeling in Align](../TerrModeling.htm)
* [Configuring Multichannel Cycle Plans](../../CyclePlans/MCCP/ConfigMCCP.htm)

### Cloning MC Cycles as

[![Closed](../../../../Skins/Default/Stylesheets/Images/transparent.gif)Align Operational Users](#)

Align operational users can clone any production MC Cycle associated with an aln\_field\_force\_\_v record. MC Cycles associated with aln\_field\_force\_model\_\_v records cannot be cloned.

There are two types of MC Cycle clones:

* Production clones – The cloned MC Cycle associates with the same aln\_field\_force\_\_v record as the source MC Cycle
* Modeling clones – The cloned MC Cycle associates with the aln\_field\_force\_model\_\_v record corresponding to the aln\_field\_force\_\_v field of the source MC Cycle

#### Creating a Production Clone

To clone an MC Cycle:

1. Select the **Gear** button from one of the following pages:

   * The Cycles list view from the Targeting tab
   * The detail page of an mc\_cycle\_\_v record
   * The MC Cycles related list on the detail page of an aln\_field\_force\_\_v record
2. Select **Clone an Existing MC Cycle**.

   This option displays as **Clone Cycle** when selected from an MC Cycle detail page.
3. Populate the following fields with the appropriate information:

   * MC Cycle – The existing cycle to clone. When cloning from an MC Cycle detail page, this field is automatically populated. When cloning from the detail page of an aln\_field\_force\_\_v or aln\_field\_force\_model\_\_v record, only MC Cycles from the production Field Force may be selected.
   * Name – The name of the new cycle
   * Start Date – The start date of the new cycle
   * End Date – The end date of the new cycle
4. Select **Continue**.
5. Verify the information is correct before selecting **Confirm**.

A process task displays after selecting Confirm indicating the progress of the clone. An error displays if the Start and End Dates of the newly created MC Cycle overlap with an existing MC Cycle.

#### Creating a Modeling Clone

To create a modeling clone of an MC Cycle:

1. Navigate to the **MC Cycles** section of the appropriate aln\_field\_force\_model\_\_v record.
2. Select the **Gear** button.
3. Select **Clone an Existing MC Cycle**.
4. Populate the following fields with the appropriate information:

   * MC Cycle – The existing cycle to clone. When cloning from an MC Cycle detail page, this field is automatically populated. When cloning from the detail page of an aln\_field\_force\_\_v or aln\_field\_force\_model\_\_v record, only MC Cycles from the production Field Force may be selected.
   * Name – The name of the new cycle
   * Start Date – The start date of the new cycle
   * End Date – The end date of the new cycle
5. Select **Continue**.
6. Verify the information is correct before selecting **Confirm**.

A process task displays after selecting Confirm indicating the progress of the clone. An error displays if the Start and End Dates of the newly created MC Cycle overlap with an existing MC Cycle.

### Cloning MC Cycle Feedback as

[![Closed](../../../../Skins/Default/Stylesheets/Images/transparent.gif)Align Operational Users](#)

Align operational users can clone an MC Cycle’s [feedback](../TerrFeedback/Overview.htm) when running an Assignment Preview on a cloned MC Cycle. This enables end users to avoid providing the same feedback on the same accounts cycle to cycle, while still enabling modifying a cloned Cycle’s Targeting Rule, Channels, and Products.

Do not run an Assignment Preview during an MC Cycle's feedback period.

Cloning feedback includes the following information:

* Approved challenges of the following types that have been incorporated into the source MCCPs
* Add Target
* Edit Goal
* Remove Target
* Manual edits to the cycle, for example, adjusting a target’s goals or adding a target
* Data loads creating new targets

To clone an MC Cycle’s Targeting Feedback:

1. Clone the source MC Cycle.
2. Apply any refinements to the newly cloned MC Cycle, including its Channels, Products and Targeting Rule. This step is optional.
3. Initiate an **Assignment Preview**.
4. Select **Yes** in the Target Feedback Cloning section of the Preview Account Assignment Rules modal.

This section only displays if the Preview includes territories associated with a cloned MC Cycle.

#### Cloning Remove Target Feedback

Remove Target challenges made by users during Targeting Feedback can now be cloned from one MC Cycle to another. Remove Target challenges made in one MC Cycle are retained in the resulting cloned MC Cycle and can be revised via Targeting Feedback.

When an MC Cycle with Targeting Feedback is cloned, aln\_account\_exclusion\_\_v records generate for each account and automatically associate with the cloned MC Cycle. These clone aln\_account\_exclusion\_\_v records contain the following information:

* account\_\_v – References the same account as the source aln\_account\_exclusion\_\_v record
* assignment\_type\_\_v – target\_\_v
* end\_date\_\_v – The end date of the cloned MC Cycle
* exclusion\_reason\_\_v – feedback\_\_v
* exclusion\_type\_\_v – aln\_territory\_\_v
* mc\_cycle\_\_v – The cloned MC Cycle
* aln\_project\_\_v
* segments\_\_v – The list of segment IDs present when the target was initially removed
* send\_to\_crm\_\_v – Yes
* source\_\_v – cycle\_clone\_\_v
* start\_date\_\_v – The start date of the cloned MC Cycle
* aln\_territory\_model\_\_v – References the aln\_territory\_model\_\_v record corresponding aln\_account\_exclusion\_\_v record

#### Segment Changes

A target's segment refers to the channel and product groups in the targeting rule the account matched the criteria for, causing it to be designated a target.

If a target’s segment differs between the source cycle and the new cycle, feedback on the associated Channel and Product goals is not cloned. This is because changing the segment changes the target’s worth, and so the end user should review the new goals when providing feedback.

If a target removed using a Remove Target challenge changes segments in the cloned MC Cycle and still matches a targeting rule, the associated aln\_account\_exclusion\_\_v record is deleted and the account displays as a target when the MC Cycle is submitted for feedback.

#### Unlinking Targeting Channel and Product Groups

Channel groups and product groups in a targeting rule can be unlinked to prevent feedback on the targets in those groups from being cloned. This enables Align operational users to control if there is a certain channel or product group whose targets should have goals set strictly by the targeting rule.

Unlinking a targeting channel or product group cannot be undone.

To unlink a Targeting Channel or Product:

1. Navigate to the appropriate **Targeting Rule**.
2. Navigate to the appropriate **Channel Group or Product Group Label**.
3. Select **Feedback Cloning**.
4. Select **Unlink**.

### Related Topics

[Modeling in Align](../TerrModeling.htm)

[Territory Feedback Overview](../TerrFeedback/Overview.htm)