Question:

What are the Common Causes of Data not Being Copied During the Feedback Cloning Process in Veeva Align? This involves the scenarios of MCCPs, MCCP Targets, MCCP Channels, MCCP Products not getting copied.

Answer:

When an MC Cycle gets copied using the Clone an Existing Cycle button, the following records get replicated:

• mc_cycle_channel__aln
• mc_cycle_product__aln
• account_rule__aln
• targeting_rule_channel__aln
• targeting_rule_product__aln
• account_rule_criteria__aln

The Assignment Preview and Assignment Commit processes are responsible for cloning MCCP Targets, MCCPs, MCCP Channels, MCCP Products. This also gets carried out in case there are no Targeting Rules.

As stated by Cloning an MC Cycle:

Cloning feedback includes the following information:

• Approved Add Target, Edit Goal, and Remove Target type Targeting Feedback challenges that have been incorporated into the source MCCPs
• Manual edits to the cycle by the administrator, for example, adjusting a target’s goals or adding a target
• Data loads made by the administrator to create new targets

I. In the case of MC Cycle Plan Channels and MC Cycle Plan Products, The functionality only clones them if they have valid, approved feedback, furthermore, the records and their source MCCP Target records meet the following criteria:

The source MCCP Target record has the source__aln of import__aln or cycle_clone__aln or the Activity Goal Edit field of the source MCCP Channel record/MCCP Product record is not null.

II. The functionality checks for date ranges as well, especially in Modeling Projects. The Planned Publish Date value of the Project has to be between the start date and end date of the target Model Account Territory, moreover, the start date and end date of the associated MCCP Target record has to be between the start date and end date of the target Model Account Territory. The Model Account Territory corresponding to the Territory Model (MC Cycle Plan) and Target Account must exist.
The Model Account Territory needs to be active during the whole MC Cycle start/end period.

III. There are segmentation differences between the source and target MC Cycles. This scenario is covered in the Align Help documentation: Cloning an MC Cycle

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 are 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 account_exclusion__aln record is deleted and the account displays as a target when the MC Cycle is submitted for feedback.

Related Documentation:

Align Help Documentation: 

• Cloning an MC Cycle