Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/CyclePlans/MCCP/Creating/CreateMCCP.htm

## Creating Multichannel Cycle Plans

MCCP admin users create Multichannel Cycle Plans (MCCP) to provide a structured framework for planning and executing cross-channel campaigns. MCCP are created either through data loading or manual record creation.

Each MCCP consists of two primary components: a cycle and a cycle plan. The cycle defines the overall structure, including dates, channels, products, and weighting criteria. The cycle plan specifies territories and targets within the context of the cycle.

**Who can use this feature?**

* MCCP Admin Users — Browser
* [Understanding MCCP Status](#Understa)
* [Creating Multichannel Cycle Plans](#Creating8)
* Users do not require an additional license

### Configuring Creating Multichannel Cycle Plans for

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

To configure this feature, ensure [Configuring Multichannel Cycle Plans](../ConfigMCCP.htm) is complete.

### Understanding MCCP Status as

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

When creating a cycle, MCCP admin users set the status for the overall cycle to one of three values: planned, in progress, or completed. The Process Scheduler uses the cycle status and the start and end date on the cycle to calculate when plans are activated and displayed to users. The next time the Process Scheduler runs after a change in cycle status, status fields are updated accordingly.

Cycle plan status is determined by the mc\_cycle\_status\_\_v field on the mc\_cycle\_\_v object and the mc\_cycle\_plan\_status\_\_v field on the mc\_cycle\_plan\_\_v object. There are three possible values for these status fields:

* planned\_\_v - The cycle plan is not active yet. Channel and product calculations occur to enable end users to stay informed on future goals.
* in\_progress\_\_v - The cycle plan is active. To provide end users time to submit any remaining activities at the end of a cycle plan, plans remain in this status for up to 30 days after the cycle end date. The 30-day period is not configurable.
* completed\_\_v - The plan is no longer active. When the cycle status changes from in\_progress\_\_v to completed\_\_v, calculations occur one last time. Once the cycle status is completed\_\_v and the final calculation is completed, queries and calculations are no longer processed.
* If the cycle status is in\_progress\_\_v after 30 days past the cycle end date, the cycle and its plans are automatically set to completed\_\_v and final calculations are processed

### Creating Multichannel Cycle Plans as

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

To create Multichannel Cycle Plans in bulk, data load Multichannel Cycle Plan records into Vault CRM using the Vault Loader. For more information on data loading, see [About Vault Loader](https://platform.veevavault.help/en/gr/26597/).

To manually create Multichannel Cycle Plans, complete the following sections in this order:

* [Creating Cycles](#Creating)
* [Creating Cycle Channels](#Creating2)
* [Creating Cycle Products](#Creating3)
* [Creating Multichannel Cycle Plans](#Creating4)
* [Creating Multichannel Cycle Plan Targets](#Creating5)
* [Creating Multichannel Cycle Plan Channels](#Creating6)
* [Creating Multichannel Cycle Plan Products](#Creating7)

Although cycle plans are created on the Browser platform, users on mobile devices can view and use MCCP.

#### Creating Cycles

The Multichannel Cycle record serves as the foundation for generating channel and product records. This record contains essential details for the cycle, for example, cycle name and start and end dates Each cycle plan must be linked to a corresponding cycle.

To create a cycle:

1. Open the **MC Cycles** tab.
   ![](../../../../Resources/Images/MCCP/Create/CreatingMCCP/Create1.png)
2. Select the **Create** button.
3. Enter at least the following information:
   * name\_\_v - Cycle name
   * start\_date\_\_v - Cycle start date
   * end\_date\_\_v - Cycle end date
   * mc\_cycle\_status\_\_v - Initial cycle status
   * over\_reached\_threshold\_\_v - Number indicating a percent at which targets are considered over reached for the cycle, based on the cycle's elapsed time
   * under\_reached\_threshold\_\_v - Number indicating a percent at which targets are considered under reached for the cycle, based on the cycle's elapsed time

For more on threshold calculations, see [Defining Over Reached and Under Reached Thresholds](MCCPCalculations.htm).

![](../../../../Resources/Images/MCCP/Create/CreatingMCCP/Create2Cropped.png)4. Select **Save**.

#### Creating Cycle Channels

After creating a cycle, channels need to be added to the cycle. Channels are comprised of activities from one of the following supported objects:

* call2\_\_v - Call Reporting
* em\_attendee\_\_v - Events Management
* event\_attendee\_\_v - Medical Events
* sent\_email\_\_v - Approved Email
* multichannel\_activity\_\_v - CLM

To create cycle channels:

1. Open an **mc\_cycle\_\_v** record.
2. Select **Create** from the MC Cycle Channels section.
   ![](../../../../Resources/Images/MCCP/Create/CreatingMCCP/Copy of CycleChannel1.png)
3. Select an object type:
   * Channel with Product - Indicates the channel has products aligned to it, and the MC Cycle Products related list is on the respective mc\_cycle\_channel\_\_v layout
   * Channel Only - Indicates the channel does not have products aligned to it, and the MC Cycle Products related list is not on the mc\_cycle\_channel\_\_v layout
     ![](../../../../Resources/Images/MCCP/Create/CreatingMCCP/Copy of CycleChannel2.png)
4. Select **Continue**.
5. Enter the appropriate information:

* channel\_object\_\_v - One of the following objects:
* call2\_\_v - Product detailing activities are queried from the call2\_detail\_\_v object
* em\_attendee\_\_v - Activities are queried from Events Management attendee records
* event\_attendee\_\_v - Activities are queried from Medical Event attendee records
* multichannel\_activity\_\_v - CLM activities are queried from the multichannel\_activity\_line\_\_v object
* sent\_email\_\_v - Approved Email activities are queried from the sent\_email\_\_v object
* channel\_label\_\_v - The channel label end users see
* channel\_weight\_\_v - The channel activity’s level of importance, relative to other channel activities
* If only a single channel is added to the cycle, this field can be populated with the number 1. If multiple channels are used, place different weights on each channel activity. A higher weight number means higher importance.
  ![](../../../../Resources/Images/MCCP/Create/CreatingMCCP/Copy of CycleChannel3.png)

6. Select **Save**.
   ![](../../../../Resources/Images/MCCP/Create/CreatingMCCP/Copy of Cyclechannel5.png)
7. Select **Edit > Add Criteria** on the newly created mc\_cycle\_channel\_\_v record to add Channel Criteria. Channel Criteria define which records count towards cycle goals when MCCPs are processed.
8. Populate the Field, Operator, and Value fields in the Channel Criteria section.

* Certain special characters in VQL, for example the single-quote (') character, must be escaped with a backslash (\). See [Introduction to Vault Queries](https://developer.veevavault.com/vql/) for more information.
* The list of fields comes from the object listed in the channel\_object\_\_v field on the mc\_cycle\_channel\_\_v object
* Channel criteria for Events Management events can be based on fields from the em\_event\_\_v object in addition to em\_attendee\_\_v
* Channel criteria for Medical Events can be based on fields from the medical\_event\_\_v object in addition to event\_attendee\_\_v
* The Operator picklist values and the Value input field type are determined by the selected field’s data type. The Contains operator is not supported in Vault CRM.
* Null values are not supported for the following operators:
* <
* >
* <=
* >=

  An error displays when users attempt to save null values for these operators. Users must resolve the error before saving the record.
* The following types of fields are not available when creating channel criteria:
* Datetime fields
* Formula fields
* Long text, rich text, and text area fields greater than 255 characters
* Lookup fields
* Object reference fields

![](../../../../Resources/Images/MCCP/Create/CreatingMCCP/Copy of CycleChannel6.png)

9. Select **Save**.

#### Creating Cycle Products

When a Channel with Products cycle channel is created, products need to be associated with the cycle channel. MCCP admin users create cycle products to define which products are tracked for each channel, in a given cycle.

Cycle product records are not needed for Channel Only channels.

To create cycle products:

1. Open an **mc\_cycle\_channel\_\_v** record.
   ![](../../../../Resources/Images/MCCP/Create/CreatingMCCP/Copy of CycleChannel7.png)
2. Select **Create** from the MC Cycle Products section.
3. Complete at least the **product\_\_v** and **product\_weight\_\_v** fields. product\_weight\_\_v indicates how important the product is, relative to other products in the plan. A higher weight number means higher importance.
   ![](../../../../Resources/Images/MCCP/Create/CreatingMCCP/Copy of CycleProduct2.png)
4. Select **Save**.

Although cycle channels have channel criteria, cycle products do not have channel criteria. Products inherit the cycle channel criteria.

#### Creating Multichannel Cycle Plans

Multichannel Cycle Plan records serve as the header record for the territory. Each MCCP must reference an mc\_cycle\_\_v record.

To create a Multichannel Cycle Plan:

1. Open the **MC Cycle Plan** tab.
   ![](../../../../Resources/Images/MCCP/Create/CreatingMCCP/Copy of MCCP1.png)
2. Select **Create**.
3. Enter information in at least the following fields:
   * name\_\_v - Cycle plan name
   * territory\_\_v - Territory for the plan
   * ownerid\_\_v – The MCCP End User
   * mc\_cycle\_plan\_status\_\_v - Initial cycle plan status
   * cycle\_\_v - The cycle the plan is associated with

   Remaining fields are calculated by the MCCP process when the value of the mc\_cycle\_plan\_\_status\_\_v field on the mc\_cycle\_plan\_\_v record is in\_progress\_\_v.
   ![](../../../../Resources/Images/MCCP/Create/CreatingMCCP/CreateMCCP.png)
4. Select **Save**.

#### Creating Multichannel Cycle Plan Targets

Multichannel Cycle Plan Targets are child records of the Multichannel Cycle Plan record. They serve as the junction between a cycle plan and accounts targeted in the plan, identifying which accounts users in the territory should focus on in a given cycle.

To create MCCP targets:

1. Open an **mc\_cycle\_plan\_\_v** record.
   ![](../../../../Resources/Images/MCCP/Create/CreatingMCCP/CreateMCTarget1Cropped.png)
2. Select **Create** from the MC Cycle Plan Targets section.
3. Enter information in at least the following fields:
   * target\_\_v - The targeted account
   * cycle\_plan\_\_v - Automatically populated with the originating cycle plan
   * mc\_cycle\_plan\_target\_status\_\_v - Indicates the target’s status. Select Active to include the target in the cycle plan.

   Merged status is set by the system when a target is the losing account during an account merge where both the winning and losing accounts were on the same cycle plan. For more information on merging accounts, see [Merging Accounts with MCCP Records](../../../Accounts/ManagingAccountInfo/Account_Merge_Administration.htm#MCCP).

   * channel\_interactions\_goal\_\_v - The ideal number of interactions between the end user and the account within the dates specified on the mc\_cycle\_\_v record

     For events channels, populate the team\_channel\_interactions\_goal\_\_v field instead. Individual goals and product goals are not supported for events channels. For more on team-based goals, see [Adding Team-Based Goals](TeamGoals.htm).
   * product\_interactions\_goal\_\_v - The ideal number of product interactions between the end user and the account within the dates specified on the mc\_cycle\_\_v record. Required when MC Cycle Products are in use (channel\_product\_\_v object type is selected on the mc\_cycle\_channel\_\_v record).

   Remaining fields are calculated by the MCCP process when the value of the mc\_cycle\_plan\_\_status\_\_v field on the mc\_cycle\_plan\_\_v record is in\_progress\_\_v.

   ![](../../../../Resources/Images/MCCP/Create/CreatingMCCP/CreateMCTarget2.png)
4. Select **Save**.

#### Creating Multichannel Cycle Plan Channels

The Multichannel Cycle Plan Channel connects target accounts to the Multichannel Cycle Channel. Only align targets to channels which apply to the target account.

To create an MCCP channel:

1. Open an **mc\_cycle\_plan\_target\_\_v** record.
   ![](../../../../Resources/Images/MCCP/Create/CreatingMCCP/CreateMCChannel1.png)
2. Select **Create** from the MC Cycle Plan Channels section.
3. Select an object type:
   * Channel with Product - Indicates the channel has products aligned to it, and the MC Cycle Products related list is on the respective mc\_cycle\_channel\_\_v layout
   * Channel Only - Indicates the channel does not have products aligned to it, and the MC Cycle Products related list is not on the mc\_cycle\_channel\_\_v layout
     ![](../../../../Resources/Images/MCCP/Create/CreatingMCCP/CreateMCChannel2.png)
4. Select **Continue**.
5. Select a cycle channel from the **ctrl\_mc\_cycle\_\_v** field.
   ![](../../../../Resources/Images/MCCP/Create/CreatingMCCP/CreateMCChannel3.png)
6. Enter information in at least the following fields:
   * cycle\_plan\_target\_\_v - Automatically populated with the current target
   * cycle\_channel\_\_v - Select a cycle channel from the associated cycle
   * channel\_activity\_goal\_\_v - The ideal number of activities for this channel within the time frame specified on the mc\_cycle\_\_v record

   For events channels, populate the team\_channel\_activity\_goal\_\_v field instead. Individual goals are not supported for events channels. For more on team-based goals, see [Adding Team-Based Goals](TeamGoals.htm).

   The remaining fields are calculated by the MCCP process when the value of the mc\_cycle\_plan\_\_status\_\_v field on the mc\_cycle\_plan\_\_v record is in\_progress\_\_v.
   ![](../../../../Resources/Images/MCCP/Create/CreatingMCCP/CreateMcChannel4.png)
7. Select **Save**.

#### Creating Multichannel Cycle Plan Products

Multichannel Cycle Plan Product records are child records of the Cycle Plan Channel. These records serve as the connection between the targeted account and the products applicable for the channel. Not all products under the channel may be applicable to the target.

MC Cycle Products are not supported for events channels.

To create MCCP products:

1. Open an **mc\_cycle\_plan\_channel\_\_v** record.
   ![](../../../../Resources/Images/MCCP/Create/CreatingMCCP/CreateMCProduct1Cropped.png)
2. Select **Create** from the MC Cycle Products section.
3. Enter information into at least the following fields:
   * cycle\_plan\_channel\_\_v - The channel the product is associated with
   * cycle\_product\_\_v - The product; only cycle products from the respective Cycle Channel and Cycle can be added
   * product\_activity\_goal\_\_v - Goal for MCCP activity on this channel/product combination

   ![](../../../../Resources/Images/MCCP/Create/CreatingMCCP/CreateMCProduct2.png)
4. Select **Save**.

### Example: Creating a Multichannel Cycle Plan as

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

MCCP can be created through [data loading](#Create) or [manual record creation](#Creating). The following example shows how MCCP can be used to support business processes and provides high-level guidance on how an MCCP admin user sets up a cycle plan, regardless of whether the plan is data loaded or manually created.

For example, an MCCP admin user wants to create a cycle plan for the first quarter of 2024. The cycle plan must meet the following requirements:

* Track activity for two channels - Face-to-Face and Sent Email
* Track activity for two products in the Face-to-Face channel - Cholecap and Labrinone

To set up the MCCP, the MCCP admin user must create the following records at a minimum, in this order:

* mc\_cycle\_\_v
* mc\_cycle\_channel\_\_v
* mc\_cycle\_product\_\_v - Only required for channels with products
* mc\_cycle\_plan\_\_v
* mc\_cycle\_plan\_target\_\_v
* mc\_cycle\_plan\_channel\_\_v
* mc\_cycle\_plan\_product\_\_v - Only required for channels with products

#### Creating the Cycle

First, the MCCP admin user needs to create an overall cycle record to define the name, dates, and status for the cycle plan. To do so, they create an mc\_cycle\_\_v record with the following values:

| Field | Example Value |
| --- | --- |
| name\_\_v | Q1 2024 |
| start\_date\_\_v | 01/01/2024 |
| end \_date\_\_v | 03/31/2024 |
| mc\_cycle\_status\_\_v | planned\_\_v |
| under\_reached\_threshold\_\_v | 30 |
| over\_reached\_threshold\_\_v | 30 |

#### Creating Cycle Channels

After creating the cycle, the MCCP admin user creates mc\_cycle\_channel\_\_v records to define which channels are included in the cycle.

##### Channel with Products

Since products need to be tracked for the Face-to-Face channel in this example, the MCCP admin user uses the channel\_product\_\_v object type to create an mc\_cycle\_channel\_\_v record with the following values:

| Field | Example Value |
| --- | --- |
| object\_type\_\_v | channel\_product\_\_v |
| channel\_label\_\_v | Face-to-Face |
| cycle\_\_v | Reference to parent cycle - Q1 2024 |
| channel\_object\_\_v | call2\_\_v |
| channel\_weight\_\_v | 1 |

##### Channel Only

Since products do not need to be tracked for the Sent Email channel in this example, the MCCP admin user uses the channel\_\_v object type to create an mc\_cycle\_channel\_\_v record with the following values:

| Field | Example Value |
| --- | --- |
| object\_type\_\_v | channel \_\_v |
| channel\_label\_\_v | Sent Email |
| cycle\_\_v | Reference to parent cycle - Q1 2024 |
| channel\_object\_\_v | sent\_email\_\_v |
| channel\_weight\_\_v | 0.5 |

#### Creating Cycle Products

Because the Face-to-Face channel is a Channel with Product, the MCCP admin user next creates mc\_cycle\_product\_\_v records. These records define which product activity is tracked within a Channel with Product. The MCCP admin user creates an mc\_cycle\_product\_\_v record for each product which should be tracked:

##### Cholecap

| Field | Example Value |
| --- | --- |
| object\_type\_\_v | product\_\_v |
| channel\_\_v | Reference to the parent cycle channel - Face-to-Face |
| product\_\_v | Reference to the appropriate product\_\_v record - Cholecap |
| channel\_weight\_\_v | 1 |

##### Labrinone

| Field | Example Value |
| --- | --- |
| object\_type\_\_v | product\_\_v |
| channel\_\_v | Reference to the parent cycle channel - Face-to-Face |
| product\_\_v | Reference to the appropriate product\_\_v record - Labrinone |
| channel\_weight\_\_v | 0.8 |

#### Creating the Multichannel Cycle Plan

After setting up the overarching cycle, cycle channels, and cycle products, the MCCP admin user next creates the territory-specific multichannel cycle plan and associated channels, targets, and products. The mc\_cycle\_plan\_\_v record is the connection between the broader cycle and the territory-specific plan.

For this cycle, the MCCP admin user creates an mc\_cycle\_plan\_\_v record with the following values:

| Field | Value |
| --- | --- |
| name\_\_v | Q1 Plan |
| territory\_\_v | 101 |
| cycle\_\_v | Reference to Q1 2024 mc\_cycle\_\_v record |
| mc\_cycle\_plan\_status\_\_v | planned\_\_v |

#### Creating Multichannel Cycle Plan Targets

After creating the mc\_cycle\_plan\_\_v record, the MCCP admin user creates mc\_cycle\_plan\_target\_\_v records to identify which accounts are included as targets in the plan. The MCCP admin user needs to create an mc\_cycle\_plan\_target\_\_v record for each target account; only accounts with mc\_cycle\_plan\_target\_\_v records are tracked in the MCCP.

As an example for one target account, the MCCP admin user creates an mc\_cycle\_plan\_target\_\_v record with the following values:

| Field | Value |
| --- | --- |
| target\_\_v | Reference to an account\_\_v record. For example, Clinton Ackerman. |
| mc\_cycle\_plan\_target\_status\_\_v | active\_\_v |

#### Creating Multichannel Cycle Plan Channels

Next, the MCCP admin user creates mc\_cycle\_plan\_channel\_\_v records to define which channels are used to contact the target account. mc\_cycle\_plan\_channel\_\_v records are children of the MCCP target record; create channel records for each target in the plan.

In this example, each target needs a Channel with Product mc\_cycle\_plan\_channel\_\_v record for the Face-to-Face channel and a Channel Only mc\_cycle\_plan\_channel\_\_v record for the Sent Email channel.

##### Channel with Products

Since products need to be tracked for the Face-to-Face channel, the MCCP admin user uses the channel\_product\_\_v object type to create mc\_cycle\_\_plan\_channel\_\_v records with the following values:

| Field | Value |
| --- | --- |
| object\_type\_\_v | channel\_with\_product\_\_v |
| cycle\_plan\_target\_\_v | Reference to the parent MC Cycle Plan Target record. For example, Clinton Ackerman’s target record. |
| ctrl\_mc\_cycle\_\_v | Reference to the mc\_cycle\_\_v record - Q1 2024 |
| cycle\_channel\_\_v | Reference to the mc\_cycle\_channel\_\_v record - Face-to-Face |

##### Channel Only

Since products do not need to be tracked for the Sent Email channel, the MCCP admin user user the channel\_\_v object type to create mc\_cycle\_plan\_channel\_\_v records with the following values:

| Field | Value |
| --- | --- |
| object\_type\_\_v | channel\_\_\_v |
| cycle\_plan\_target\_\_v | Reference to the parent MC Cycle Plan Target record. For example, Clinton Ackerman’s target record. |
| ctrl\_mc\_cycle\_\_v | Reference to the mc\_cycle\_\_v record - Q1 2024 |
| cycle\_channel\_\_v | Reference to the mc\_cycle\_channel\_\_v record - Sent Email |

#### Creating Multichannel Cycle Plan Products

Finally, the MCCP admin user creates mc\_cycle\_plan\_product\_\_v records for the Face-to-Face channel since it is a Channel with Products. The MCCP admin user creates an mc\_cycle\_\_plan\_product\_\_v record for each product which should be tracked against the channel-target combination:

##### Cholecap

| Field | Value |
| --- | --- |
| ctrl\_mc\_cycle\_\_v | Reference to the mc\_cycle\_\_v record - Q1 2024 |
| ctrl\_mc\_cycle\_channel\_\_v | Reference to the mc\_cycle\_channel\_\_v record - Face-to-Face |
| cycle\_product\_\_v | Reference to the mc\_cycle\_product\_\_v record - Cholecap |

##### Labrinone

| Field | Value |
| --- | --- |
| ctrl\_mc\_cycle\_\_v | Reference to the mc\_cycle\_\_v record - Q1 2024 |
| ctrl\_mc\_cycle\_channel\_\_v | Reference to the mc\_cycle\_channel\_\_v record - Face-to-Face |
| cycle\_product\_\_v | Reference to the mc\_cycle\_product\_\_v record - Labrinone |

### Related Topics

[Configuring Multichannel Cycle Plans](../ConfigMCCP.htm)

[Defining Over Reached and Under Reached Thresholds](MCCPCalculations.htm)

[Using the MCCP Interface](../Executing/MCCPInterface.htm)