Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/CyclePlans/MCCP/Creating/PullIn.htm ## Supporting Pull-In Fields for MCCP To aid end users in identifying MCCP targets, making informed decisions about their outreach to accounts, and increasing efficiency when planning activities, target-related pull-in fields can be configured for the Targets and Edit Goals tabs in My Plan. Pull-in fields display as an additional column for each target. For example, Account Specialty, Address Zip (Postal) Code, or TSF Route. Source values are stamped to the MCCP pull-in field to preserve the historical value at the time of stamping. Pull-in fields can be created to retrieve information from the following source objects: * account\_\_v * address\_\_v * product\_metrics\_\_v * tsf\_\_v **Who can use this feature?** * End Users — iPad, Windows * [Using Pull-In Fields for MCCP](#Using) * Users do not require an additional license ### Configuring Pull-In Fields for MCCP for [![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)End Users](#) To configure this feature: 1. Ensure [Configuring Multichannel Cycle Plans](../ConfigMCCP.htm) is complete. 2. Navigate to **Admin > Configuration > Objects > mc\_cycle\_plan\_target\_\_v > Fields > Create**. 3. Create a field on the **mc\_cycle\_plan\_target\_\_v** object with the following parameters: * Label - Any value * API name - Use the format zvod\_\_. For example, zvod\_acc\_account\_group\_\_c Because fields must have unique field names, target pull-in fields cannot be created with the same field name and suffix as an existing standard Vault field. To create a pull-in field for a standard Vault field, the \_\_c suffix must be used. The MCCP process matches the source field and the pull-in field by disregarding the \_\_c suffix on the pull-in field and searching for a matching field with the \_\_v suffix. The must be one of the following values: + acc - For pull-in fields from the account\_\_v object + add - For pull-in fields from the address\_\_v object + tsf - For pull-in fields from the tsf\_\_v object * Data type - Use the same data type as the source field. The following data types are supported: + Date + DateTime + Formula - Must match the return type for the source formula field + Number + Picklist + Picklist (multi-select) + Text + Text Area + Yes/No 4. Navigate to **Admin > Users & Groups > Permission Sets**. 5. Select the appropriate permission set. 6. Select the **Objects** tab. 7. Grant end users at least Read permission to the new pull-in field on the **mc\_cycle\_plan\_target\_\_v** object. 8. Navigate to **Admin > Configuration > Objects > mc\_cycle\_plan\_target\_\_v > Object Types**. 9. Select the checkbox for the pull-in field to activate it for the appropriate object types. 10. Navigate to **Admin > Configuration > Objects > mc\_cycle\_plan\_\_v > Layouts**. 11. Add the pull-in field to the **mc\_cycle\_plan\_target\_\_v** related list on mc\_cycle\_plan\_\_v layouts: * Select the appropriate layout * Navigate to the **mc\_cycle\_plan\_target\_\_v** related list * Select **Edit Default Columns** * Add the new field to **Selected Columns** 12. Navigate to **Business Admin > Objects > mc\_cycle\_\_v**. 13. Select the **calculate\_pull\_through\_\_v** checkbox on the appropriate mc\_cycle\_\_v records to enable pull-in field processing when the MCCP process runs (optional). When this checkbox is selected, calculations are also run when the MC Cycle is in Planned status. The calculate\_pull\_through\_\_v field is cleared after the MCCP process runs. Only enable the calculate\_pull\_through\_\_v field on the mc\_cycle\_\_v object when pull-in fields need to be populated or repopulated, for example, when a cycle is first set to the in\_progress\_\_v status. Do not create workflows or triggers to reset the calculate\_pull\_through\_\_v field after the MCCP process runs as this could increase the overall MCCP calculation and processing duration. #### Configuring Product Metrics Pull-in Fields To configure product metrics pull-in fields: 1. Ensure [Configuring Multichannel Cycle Plans](../ConfigMCCP.htm) and [Creating Product-Specific Metric Configurations](../../../Products/ProdMetrics/ProductSpecificMetrics.htm) are complete. 2. Ensure the **applicable\_product\_metrics\_\_v** field is populated on the mc\_cycle\_plan\_product\_\_v record for the product goal. This field is automatically populated during MCCP processing. To display in My Plan, the product metrics pull-in field must be listed in this field. 3. Create a field on the **mc\_cycle\_plan\_product\_\_v** object with the following parameters: * Label - Any value * API name - Use the format zvod\_pm\_[sourcefieldname], for example, zvod\_pm\_segmentation\_\_c * Data type - Use the same data type as the source field Pull-in fields sourced from the product\_metrics\_\_v object must be created on the mc\_cycle\_plan\_product\_\_v object. 4. Grant end users Read permission to the new pull-in field on the **mc\_cycle\_plan\_product\_\_v** object. 5. Place the new pull-in field on the end user’s default **mc\_cycle\_plan\_product\_\_v** layout. [![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)Integration Users](#) To configure this feature: 1. Ensure [Configuring Multichannel Cycle Plans](../ConfigMCCP.htm) is complete. 2. Grant at least Read permission to the pull-in’s **source field** on the account\_\_v, address\_\_v, or tsf\_\_v objects. 3. Grant Read permission to the pull-in field on the **mc\_cycle\_plan\_target\_\_v** object. #### Configuring Product Metrics Pull-in Fields To configure product metrics pull-in fields: 1. Ensure [Configuring Multichannel Cycle Plans](../ConfigMCCP.htm) and [Creating Product-Specific Metric Configurations](../../../Products/ProdMetrics/ProductSpecificMetrics.htm) are complete. Ensure integration users have access to all records on the metric\_configuration\_\_v and product\_metrics\_\_v objects. 2. Grant Read permission to the **child\_account\_\_v** object. 3. Grant Edit permission to the new pull-in field on the **mc\_cycle\_plan\_product\_\_v** object. 4. Grant Read permission to the source field on the **product\_metrics\_\_v** object. 5. Grant at least Read permission to the following fields on the **product\_metrics\_\_v** object: * account\_\_v * detail\_group\_\_v * location\_\_v * product\_\_v 6. Grant at least Read permission to the following fields on the **metric\_configuration\_\_v** object: * active\_\_v * detail\_group\_\_v * detail\_topic\_\_v * name\_\_v * product\_\_v ### Using Pull-In Fields for MCCP as [![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)End Users](#) Each pull-in field displays as a column on the Targets and Edit Goals tabs in My Plan. For example, Account Specialty. Users can view and filter on pull-in field values. ![](../../../../Resources/Images/MCCP/Create/PullIns/Pullin1.PNG) Criteria for matching pull-in field values to targets varies depending on the source: * Account - Field values sourced from the account\_\_v object are matched to targets based on the account selected in the target\_\_v field on the mc\_cycle\_plan\_\_v record * Address - Field values source from the address\_\_v object are matched to targets based on first match: * Values from the TSF Address are used, if available. The territory\_\_v field on the mc\_cycle\_plan\_\_v record and the target\_\_v field on the mc\_cycle\_plan\_target\_\_v are matched to the territory\_\_v and account\_\_v fields on tsf\_\_v records. * If a TSF address is not available, the primary address for the account is used, based on the account in the target\_\_v field on the mc\_cycle\_plan\_target\_\_v record * If neither a TSF address nor a primary address are available, the target account’s address\_\_v record with the oldest Created Date is used, based on the account in the target\_\_v field on the mc\_cycle\_plan\_target\_\_v record * Product Metrics - Field values sourced from the product\_metrics\_\_v object are matched to targets based on the following criteria: * Account - The account\_\_v field on the mc\_cycle\_plan\_target\_\_v record is matched to the account\_\_v field on the product\_metrics\_\_v record * Detail Group - The detail\_group\_\_v field on the mc\_cycle\_plan\_product\_\_v record is matched to the detail\_group\_\_v field on the product\_metrics\_\_v object * Product - The product\_\_v field on the mc\_cycle\_plan\_product\_\_v record is matched to the products\_\_v field on the product\_metrics\_\_v object If [Supporting Child Accounts for Multichannel Cycle Plans](ChildAcct.htm) is enabled, targets which are child accounts are matched based on the location\_\_v field on the product\_metrics\_\_v object. * TSF - Field values sourced from the tsf\_\_v object are matched based on the territory\_\_v field on the mc\_cycle\_plan\_\_v record and the target\_\_v field on the mc\_cycle\_plan\_target\_\_v record. These fields are matched to the territory\_\_v and account\_\_v fields on the tsf\_\_v record, respectively. #### Filtering MCCP Targets by Pull-in Field Users can filter based on pull-in fields, either in combination with channel and product or separately. To filter targets based on pull-in fields: 1. Select the **filter** icon from the Targets tab or the Edit Goals tab. ![](../../../../Resources/Images/MCCP/Create/PullIns/Filter1.PNG) 2. Select a **channel** and **product** (optional). ![](../../../../Resources/Images/MCCP/Create/PullIns/Filter2.5.PNG) 3. Select **Add Filter**. ![](../../../../Resources/Images/MCCP/Create/PullIns/Filter2.PNG) 4. Select the appropriate filter criteria, then select **Done**. ![](../../../../Resources/Images/MCCP/Create/PullIns/Filter3.PNG) 5. Select **Apply**. Target accounts are filtered based on the selected criteria. ![](../../../../Resources/Images/MCCP/Create/PullIns/Filter4.5.PNG) ##### Filtering with Product Metrics Pull-In Fields Product Metrics Pull-In Fields are only available as filter criteria if the pull-in is also included in the available\_values\_\_v field on the product’s metric\_configuration\_\_v record. Filter criteria are further limited to values which are active for both the source field and the pull-in field on the mc\_cycle\_plan\_target\_\_v object. For example, a source field has values A, B, C, D, and E. Value D is inactive and value E is not included in the pull-in field values on the mc\_cycle\_plan\_target\_\_v object. Only values A, B, and C are available as filter criteria. ### Related Topics [Using the MCCP Interface](../Executing/MCCPInterface.htm) [Scheduling Calls for MCCP Targets](../Executing/ScheduleCalls.htm)