Skip to main content
hamburger menu Created with Sketch.
We are currently experiencing an issue with creating new support tickets from the Help Center portal. Some users are unable to select the appropriate form when submitting their tickets. We are working to resolve the issue.

Search the Knowledge Base

What is MCCP Mismatching in Veeva CRM and in Veeva Align?

  • Updated

Question:

What is Multichannel Cycle Plan (MCCP) mismatching in Veeva CRM and in Veeva Align?

Answer:

Suppose each letter refers to a record of the relevant object. MCCP mismatching in both systems refers to the following scenario at the MC Cycle Plan Channel level:

MC Cycle "A" -> MC Cycle Plan "B" -> MC Cycle Plan Target "C" -> MC Cycle Plan Channel "D" -> MC Cycle Channel "E" <- MC Cycle "F".

This means that the user and target account-related MCCP data do not match with the same MC Cycle that the MC Cycle Channel belongs to.

The same mismatching situation can also occur at the MC Cycle Plan Product, MC Cycle Product level.

These scenarios are regarded as a misconfiguration, a significant data issue, and must be fixed in both systems.

Clues that may indicate the mismatching issue are as follows:

  • In Veeva CRM, the following error message may appear in the View Results of specific Bulk Data Load Jobs and it may imply a mismatching scenario:

    "INVALID_FIELD:Number of fields in header is different from the row. header = x row = y:--"

  • In Veeva Align, the (Model) Assignment Commit process may terminate due to mismatching.
Note: These mismatching scenarios at both levels may exist at the same time. 

Related Documentation:

CRM Help Documentation:

Align Help Documentation: 

Knowledge Base:

 

 

Powered by Zendesk