Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/AccountPlanning/Config/ConfiguringAccountPlans.htm

## Configuring Account Plans

### Components

The account plans module is a structured framework for managing long-term projects related to key accounts. It consists of a hierarchical structure of objects that outline strategies, tactics, and actions necessary to achieve specific account goals. The main objects that comprise the account plans module are:

#### Account Plan (account\_plan\_\_v)

The Account Plan object is the top-level of the account plan hierarchy that defines the overall plan for an account.

#### Strategy (plan\_tactic\_\_v)

Strategies are general activities to be implemented as part of an account plan. They are typically configured as the second level of an account plan hierarchy.

#### Objective (account\_tactic\_\_v)

Objectives are specific activities to be completed for an account plan. They can be used to assign accounts to strategies or break down strategies into smaller, actionable steps. They are typically configured as the third level of an account plan hierarchy.

#### Action Item (action\_item\_\_v)

Action items are the specific tasks in the plan that team members execute to move the plan toward completion. Action Items can be executed from the plan or the Call Report. They are typically configured as the fourth and last layer of the account plan hierarchy in replacement of call objectives.

#### Call Objective (call\_objective\_\_v)

Call objectives are the specific tasks in the plan that team members execute to move the plan toward completion. Call objectives must be executed from the Call Report. They are typically configured as the fourth and last layer of the account plan hierarchy in replacement of action items.

#### Account Team Member (account\_team\_member\_\_v)

Account plan team members are colleagues who are responsible for collaborating on the account plan.

#### Key Stakeholders (key\_stakeholder\_\_v)

Key stakeholders are the people or accounts that are important to drive the plan forward.

#### SWOT (swot\_\_v)

The SWOT object is a SWOT (Strengths, Weaknesses, Opportunities, and Threats) analysis for an account plan. This allows multiple teams to easily contribute to a single account plan for an account and also provides flexibility for each team to have their own SWOT analysis and goals records. These records can also be used to differentiate SWOTs and goals by product, compound, or therapeutic area, based on the products associated with the account. KAMs can create and view SWOT records on the Account Plan page.

#### Related Modules

In addition to the account plan data model, account plans relate to other modules within CRM including:

* Product Plans (product\_plan\_\_v)
* Call (call2\_\_v)
* Opportunities (opportunity\_\_v)
* Patient Journeys (patient\_journey\_\_v)

### Guidance for Configuring the Account Plan Hierarchy

The Account Plan hierarchy is defined as a comma-separated list in the Account Plan Object Hierarchy Veeva Setting. For example: plan\_tactic\_\_v.account\_plan\_\_vr,account\_tactic\_\_v.plan\_tactic\_\_vr,action\_item\_\_v.account\_tactic\_\_vr

The following restrictions apply when creating an account plan:

* Either action item or call objective can be included at the lowest level of the hierarchy, not both
* Account plan is always the top level
* Custom objects can be configured as part of the hierarchy, with limitations

  While custom objects are supported in the hierarchy, it is not recommended to use them when using [Account Plan Sharing](../ManageAcctPlans/Account_Plan_Sharing.htm).
* The hierarchy should only have up to four levels including custom objects
* The hierarchy is defined on the Vault level in the account\_plan\_object\_hierarchy\_\_v Veeva Setting. Profile-specific settings are not supported for the account plan object hierarchy.

### Configuring Account Plans for

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

To configure this feature:

1. Grant the following permissions depending on the objects in the account plan hierarchy:

   | Object | Object Permission | Object Types | Fields | Field Permission |
   | --- | --- | --- | --- | --- |
   | account\_plan\_\_v | CRED | account\_plan\_\_v | * account\_\_v * name\_\_v * Account\_plan\_status\_\_v (optional) * active\_\_v * description\_\_v (optional) * start\_date\_\_v (optional) * end\_date\_\_v (optional) * health\_\_v (optional) | Edit |
   | plan\_tactic\_\_v | CRED | n/a | * account\_plan\_\_v * name\_\_v * plan\_tactic\_status\_\_v * product\_\_v (optional) | Edit |
   | account\_tactic\_\_v | CRED | account\_tactic\_\_v | * account\_\_v * account\_plan\_\_v * account\_tactic\_status\_\_v * description\_\_v (optional) * name\_\_v * plan\_tactic\_\_v | Edit |
   | action\_item\_\_v | CRED | kam\_\_v | * account\_\_v * account\_plan\_\_v * account\_tactic\_\_v * name\_\_v * action\_item\_status\_\_v * assignee\_\_v * completed\_by\_\_v * completed\_date\_\_v * description\_\_v * due\_date\_\_v * plan\_tactic\_\_v * start\_date\_\_v | Edit |
   | call\_objective\_\_v | CRED | action\_plan\_\_c  Custom object types must be created by an admin. | * account\_\_v * account\_plan\_\_v * account\_tactic\_\_v * plan\_tactic\_\_v | Edit |
   | Swot\_\_v (optional) | CRED | n/a | All fields (optional) | Edit |
2. Ensure the following VMOCs are active for the appropriate platforms:

   | Object | Sync Type | WHERE Clause |
   | --- | --- | --- |
   | account\_plan\_\_v | Top Level | WHERE account\_\_v IN (SELECT id FROM account\_\_vr) |
   | plan\_tactic\_\_v | Top Level | n/a |
   | account\_tactic\_\_v | Top Level | n/a |
   | action\_item\_\_v | Top Level | WHERE ownerid\_\_v = @@USER\_ID@@ OR assignee\_\_v = @@USER\_ID@@ |
   | action\_item\_\_v | Top Level | WHERE account\_\_v IN (SELECT id FROM account\_\_vr) |
   | action\_item\_\_v | Top Level | WHERE account\_plan\_\_v IN (SELECT id FROM account\_plan\_\_vr) |
   | call\_objective\_\_v | Top Level | WHERE account\_\_v IN (SELECT id FROM account\_\_vr) |
   | key\_stakeholder\_\_v | Full Sync | WHERE account\_plan\_\_v IN (SELECT id FROM account\_plan\_\_vr) |
   | account\_team\_member\_\_v | Top Level | WHERE account\_plan\_\_v IN (SELECT id FROM account\_plan\_\_vr) |
3. Expose the **swot\_\_v** related lists on the account\_plan\_\_v layouts. (Optional.) This allows end users to view and access the records on the Account Plan page.

#### Optional Configuration

* Configure [Stakeholder Navigator](../ManageAcctPlans/StakeholderNavAccountPlan.htm) to allow users to view a visual representation of relationships for accounts in a plan
* Configure the following sections to display on the Account Plan Layout:
* Account Plan Hierarchy
* Key Stakeholders

Configuring the Account Plan Hierarchy Section

To configure the Account Plan Hierarchy section:

1. Navigate to **Business Admin > Objects > Veeva Settings > Global Settings**.
2. Make note of the objects listed in the **account\_plan\_object\_hierarchy\_\_v** Veeva Setting so you can enable permissions for those objects in the steps below.
3. Navigate to **Admin > Users & Groups > Permission Sets**.
4. Select the appropriate permission set.
5. Select the **Objects** tab.
6. Grant at least Read access to all objects defined in the **account\_plan\_object\_hierarchy\_\_v** Veeva Setting.
7. Grant View access to the **hierarchy\_section\_\_v** section control.
8. Navigate to **Admin > Configuration > Objects > account\_plan\_\_v**.
9. Add the **hierarchy\_section\_\_v** section control to the appropriate account\_plan\_\_v layouts. This can be re-labeled to align with your company’s terminology (for example, Strategies Overview). The section name and tab name will display in the account plan UI based on the section name defined in the layout.

![](../../../Resources/Images/AccountPlans/BrowserRedesign/HierarchyTab.png)

Configuring Columns for the Hierarchy Section

Admins can configure up to 10 columns to display in the Hierarchy section of an account plan.

To configure the columns:

1. Navigate to **Business Admin > Objects > Veeva Settings > Global Settings**.
2. Update the following Veeva Settings to specify the columns that should display for that level of the hierarchy. The number of settings you update depends on the number of levels defined in the account\_plan\_object\_hierarchy\_\_v Veeva Setting.
   * account\_plan\_hierarchy\_lvl\_1\_cols\_\_v
   * account\_plan\_hierarchy\_lvl\_2\_cols\_\_v
   * account\_plan\_hierarchy\_lvl\_3\_cols\_\_v

   This functionality does not support profile-specific settings. Controlling and Dependent fields, and object reference fields with defined Criteria VQL, are not supported.

   Enter columns as a comma-delimited list of fields using the following format:

   object\_api\_name.field\_api\_name\_\_v

   For example, if the first level of the hierarchy is account\_tactic\_\_v, the Product, Type, and Description could be configured to display as columns by entering the following in the account\_plan\_hierarchy\_lvl\_1\_cols\_\_v setting:

   account\_tactic\_\_v.product\_\_v,account\_tactic\_\_v.type\_\_v,account\_tactic\_\_v.description\_\_v

   Attachment, long text, and rich text field types are not supported.
3. Navigate to **Admin > Users & Groups > Permission Sets**.
4. Select the appropriate permission set.
5. Select the **Objects** tab.
6. Grant users at least Read permission to all fields defined in the hierarchy column Veeva Settings above.
7. Grant users at least Read permission to the **Object Status** field on each of the objects included in the hierarchy column Veeva Settings above.

**Configuring Section Display Order**

To configure the section display order:

1. Navigate to **Admin > Users & Groups > Permission Sets**.
2. Select the appropriate permission set.
3. Select the **Objects** tab.
4. Grant users one of the following permissions for the **section\_display\_order\_\_v** field on the account\_plan\_\_v object:
   * Read - allows users to view the custom display order
   * Edit - allows users to edit the custom display order

   If the field is not populated, the display order is based on the configuration of the layout.

### Related Topics

[Account Plans Overview](../ManageAcctPlans/Account_Plans.htm)

[Account Plan Progress](../ManageAcctPlans/AcctPlanProgress.htm)