Account Plan Deep Cloning

• Browser

Account Plan Deep Cloning allows Key Account Managers (KAMs) to clone account plans for reuse. The team working on the account plan continually measures the success of the plan, and, based on success rates, can reuse account plans for other Key Accounts to achieve similar results.

Customers can also create account plans to act as templates they manage. KAMs can clone those templates to start a new account plan. Also, if customers create new account plans every year for their accounts, a KAM can clone a previous year’s account plan to use as the basis for the new plan.

For example, Sarah Jones, a KAM, wrote an account plan for Newton Memorial Hospital. The account plan goal is to convert Newton Memorial to Cholecap over other arthritis products. Because the account plan was successful, Sarah clones the account plan to use the same account plan for Chilton Memorial Hospital.

Considerations for Account Plan Deep Cloning

• The Medical_Insight_vod and Call2_vod objects are not available for cloning as part of an Account Plan Deep Clone and do not display on the Clone Account Plan screen
• If a user attempts to open an account plan without the appropriate permissions, an invalid permissions error message displays

• Records are cloned as is, with the following exceptions:

• If the out-of-the-box Account Plan hierarchy objects are in use, the Progress_vod field values are reset, and the Status is set to Pending_vod. Additionally, all fields on the hierarchy object representing counts of child objects, for example, Total_Account_Tactics_vod__c, are reset, and the Completed_Flag_vod check box on the Call_Objective_vod object are deselected.
• The Owner_vod field on all cloned records is set to the user who initiates the clone
• Any fields the user does not have FLS access to are not copied over in the clone
• Active_vod is set to false
• The values of the following fields are preset by the cloning process:

  Object	Field	New Value
  Plan_Tactic_vod	Progress_vod	0
  	Status_vod	Pending_vod
  	Account_Tactic_Progress_vod__c	(null) Recalculated based on triggers if account tactics are also copied
  	Completed_Account_Tactics_vod__c	(null) Recalculated based on triggers if account tactics are also copied
  	Total_Account_Tactics_vod__c	(null) Recalculated based on triggers if account tactics are also copied
  Account_Tactic_vod	Progress_vod	0
  	Status_vod	Pending_vod
  	Call_Objectives_Progress_vod__c	(null) Recalculated based on triggers if call objectives are also copied
  	Completed_Call_Objectives_vod__c	(null) Recalculated based on triggers if call objectives are also copied
  	Total_Call_Objectives_vod__c	(null) Recalculated based on triggers if call objectives are also copied
  Action_Item_vod	Status_vod	Pending_vod
  	Completed_By_vod__c	(null)
  	Completed_Date_vod__c	(null)
  	Assignee_vod__c	(null)
  Call_Objective_vod	Call2_vod	(null)
  	Completed_Flag_vod	FALSE
  	Date_vod	(null)
  	Suggestion_vod__c	(null)
  	Suggestion_Reason_vod__c	(null)
  	Prerequisite_vod__c	Updated to reflect the newly-created prerequisite Call Objective if it was copied as part of the clone process, otherwise (null)
  	Parent_Objective_vod__c	(null)
  	Non_Executable_vod__c	Set via trigger if the Call Objective has a prerequisite
  Custom objects	Progress_vod	0
  	Status_vod	Pending_vod

Configuring Account Plan Deep Cloning

To enable Account Plan Deep Cloning for end users:

1. Grant the following permissions:

   Object	OLS	Record Types	Fields	FLS
   Account_Plan_vod	CR	n/a	Clones_vod	edit

2. Grant the user Create and Read access to all objects used within the Account Plan Object Hierarchy. Ensure the user has Read and Edit access to all required fields for those objects, as well as any lookup fields on the object to its parent in the Account Plan Object Hierarchy.
3. Grant the user Create and Read access to all objects with a lookup field to the account plan. Ensure the user has Read and Edit access to all required fields for those objects, as well as the lookup field to the account plan.
4. Add the Account_Plan_Deep_Clone_vod action to relevant Account Plan page layouts.
5. Grant access to the VeevaAccountPlanController Apex class for end users.

The VeevaAccountPlanController Apex class is only available in Lightning-enabled orgs.

To enable custom objects to be part of an Account Plan Deep Clone, create a lookup relationship with the Account_Plan_vod object.

Using Account Plan Deep Cloning

The Clone Account Plan screen can be launched by selecting the Clone Account Plan button on any account plan.

The Account Plan Hierarchy and Other sections display objects that meet the following criteria:

• Account Plan Hierarchy - Includes objects that are a part of the Account Plan Hierarchy, defined via the Veeva setting
• Other - Includes objects that have a lookup to the Account Plan

For either section, objects only display in the Clone modal if the account plan has records for those objects that are part of the account plan. (For example, Action Items does not display if the account plan doesn't have Action Items, even if Action Items are configured to be a part of the Account Plan Hierarchy).

The items in the Account Plan Hierarchy section display based on what is configured. Account Plan Deep Cloning works with out-of-the-box and customized Account Plan Hierarchies, including customized Account Plan Hierarchies that include custom objects. Additionally, Account Plan Deep Cloning supports cloning records from related custom objects that have a lookup to the Account Plan object.

When an account plan is cloned, the account plan, records from the selected hierarchy, and records from related objects are cloned. The Clones_vod field on the Account_Plan_vod object is populated on the newly created account plan to reference the account plan that was cloned.