Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/BusinessEvents/BusinessEventsConfig.htm

## Configuring Business Event Tracking

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

Business Event Tracking relies on the following components:

#### Business Event Schedule (business\_event\_schedule\_\_v)

This object serves as the blueprint for the tracking process. It defines the rules and cadence for how tasks are generated, including the timing between visits, how long a task window remains open, and whether certain preliminary visits are required before ongoing monitoring begins.

#### Business Event (business\_event\_\_v)

This object is used for the high-level record that defines a specific monitoring initiative, for example, an EPPV or PI event. It acts as the parent record for the entire process, holding the general details, the associated product, and the overall start and end dates for the monitoring effort.

#### Business Event Target (business\_event\_target\_\_v)

This object is used for records identifying the specific accounts—for example, healthcare professionals or organizations—that are included in a Business Event. It tracks the status for that specific account (in progress, completed, or canceled) and helps business admins manage who is assigned to cover that target.

#### Business Event Task (business\_event\_task\_\_v)

This object contains records for the individual, actionable items that end users complete to fulfill regulatory requirements. Each task represents a specific visit type—for example, Pre-Explanation or Ongoing Monitoring visit—and includes specific deadlines to ensure the user stays compliant with the tracking schedule.

### Configuring Business Event Tracking for

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

To configure this module:

1. Ensure the following configuration is complete:
   * [Configuring Accounts](../Accounts/AcctConfig.htm)
   * [Configuring the Product Catalog](../Products/ConfigProduct.htm)
   * [Configuring Call Planning](../CallPlanning/CPConfig.htm) (to view Business Events in My Schedule)
2. Navigate to **Admin > Users & Groups > Permission Sets**.
3. Select the appropriate permission set.
4. Select the **Objects** tab.
5. Grant the following permissions:

   | Object | Object Permission | Object Types | Fields | Field Permission |
   | --- | --- | --- | --- | --- |
   | business\_event\_\_v | CRED | * eppv\_\_v * pi\_\_v | All editable fields | Edit |
   | business\_event\_schedule\_\_v | CRED | * eppv\_\_v * pi\_\_v | All editable fields | Edit |
   | business\_event\_target\_\_v | CRED | * eppv\_\_v * pi\_\_v | All editable fields | Edit |
   | business\_event\_task\_\_v | CRED | * eppv\_\_v * pi\_\_v | All editable fields | Edit |
6. Navigate to **Admin > Configuration > Objects > business\_event\_\_v > Object Types**.
7. Enable the **reassign\_owners\_\_v** action for all appropriate object types.
8. Navigate to **Admin > Configuration > Objects > business\_event\_target\_\_v > Object Types**.
9. Enable the **reopen\_target\_\_v** action for all appropriate object types.
10. Navigate to **Admin > Configuration > Objects > business\_event\_\_v > Layouts**.
11. Place the **allow\_cancellation\_\_v** and **business\_event\_schedule\_\_v** fields on the business\_event\_\_v layout.
12. Navigate to **Admin > Configuration > Objects > business\_event\_target\_\_v > Layouts**.
13. Place the following fields on the business\_event\_target\_\_v layout (optional):
14. assignee\_\_v
15. child\_account\_\_v
16. pharmacy\_\_v

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

To configure this module:

1. Ensure the following configuration is complete:
   * [Configuring Accounts](../Accounts/AcctConfig.htm)
   * [Configuring the Product Catalog](../Products/ConfigProduct.htm)
   * [Configuring Call Planning](../CallPlanning/CPConfig.htm) (to view Business Events in My Schedule)
2. Navigate to **Admin > Users & Groups > Permission Sets**.
3. Select the appropriate permission set.
4. Select the **Objects** tab.
5. Grant the following permissions:

   | Object | Object Permission | Object Types | Fields | Field Permission |
   | --- | --- | --- | --- | --- |
   | business\_event\_\_v | RE | * eppv\_\_v * pi\_\_v | * active\_\_v * allow\_cancellation\_\_v * business\_event\_status\_\_v * created\_by\_\_v * created\_date\_\_v * description\_\_v * end\_date\_\_v * modified\_by\_\_v * modified\_date\_\_v * name\_\_v * product\_\_v * start\_date\_\_v | Read |
   | business\_event\_target\_\_v | RE | * eppv\_\_v * pi\_\_v | * account\_\_v * assignee\_\_v * business\_event\_\_v * child\_account\_\_v (optional) * created\_by\_\_v * created\_date\_\_v * modified\_by\_\_v * modified\_date\_\_v * name\_\_v | Read |
   | * canceled\_date\_\_v * cancellation\_reason\_\_v * target\_status\_\_v | Edit |
   | business\_event\_task\_\_v | RE | * eppv\_\_v * pi\_\_v | * account\_\_v * business\_event\_\_v * business\_event\_target\_\_v * child\_account\_\_v (optional) * created\_by\_\_v * created\_date\_\_v * end\_date\_\_v * modified\_by\_\_v * modified\_date\_\_v * name\_\_v * ownerid\_\_v * start\_date\_\_v * task\_type\_\_v | Read |
   | * call2\_\_v * channel\_\_v * completed\_by\_\_v * completed\_date\_\_v * task\_status\_\_v | Edit |
6. Grant end users Execute permission to the **complete\_task\_\_v** and **cancel\_task\_\_v** actions on the business\_event\_task\_\_v object.
7. Grant end users Execute permission to the **business\_event\_tasks\_section\_\_v** object control on the call2\_\_v object.
8. Navigate to **Admin > Configuration > Objects > business\_event\_task\_\_v > Object Types**.
9. Enable the **complete\_task\_\_v** and **cancel\_task\_\_v** actions for all appropriate object types.
10. Navigate to **Admin > Configuration > Objects > call2\_\_v > Layouts**.
11. Place the **business\_event\_tasks\_section\_\_v** object control on the call2\_\_v layout.
12. Navigate to **Admin > Operations > business\_events\_job\_\_v**.
13. Set the Business Events Job status to **Active** and specify the job’s daily run schedule. The job creates Business Event Tasks for end users, based on admin-defined Business Event Schedules.

    The job runs on a daily schedule and cannot be configured to run hourly.
14. Navigate to **Business Admin > Objects > VMobile Object Configurations**.
15. Ensure the following VMOCs are active for the appropriate platforms:

    * business\_event\_\_v
    * business\_event\_target\_\_v
    * business\_event\_task\_\_v
16. Create [Business Event Records](#Creating) for the applicable EPPV or PI business events.

#### Displaying Business Events Records on Accounts

Optionally, users can be configured to access Business Event Target or Business Event Task records from Account layouts:

1. Navigate to **Admin > Configuration > Objects > account\_\_v > Layouts**.
2. Place either or both of the following Related Object sections on the layout:

* business\_event\_target\_\_v
* business\_event\_tasks\_\_v

#### Customizing Cancellation Reasons

Users must select a cancellation reason when canceling Business Event Tasks for a target. The following cancellation reasons are provided by default:

* Wrong Affiliation (wrong\_affiliation\_\_v)
* Patient Stopped Treatment (patient\_stopped\_treatment\_\_v)
* No Purchase (no\_purchase\_\_v)

To modify the list of cancellation reasons, edit the picklist field options available for the cancellation\_reason\_\_v field on the business\_event\_target\_\_v object. For more on editing picklist field options, see [Managing Picklists](https://platform.veevavault.help/en/lr/1269/) on the Vault platform help.

### Creating Business Event Records as

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

Business admin users create records for:

* Business Event Schedule - Define the frequency and characteristics of monitoring visits
* Business Events - Define the events requiring monitoring visits
* Business Event Targets - Define the accounts or child account requiring monitoring visits as part of the event

With the next run of the Business Events job, these records are used to generate Business Event Tasks for users to complete.

#### Business Event Schedule Records

To create a Business Event Schedule:

1. Navigate **Business Admin > Objects > Business Event Schedule**.
2. Select **Create**.
3. Select the **Business Event Schedule Type** (EPPV or PI).

   To match PI monitoring requirements, only a single task is created in PI schedules.
4. Select **Continue**.
5. Complete the following fields:

   * Pre-Explanation Required - Select this checkbox if a pre-explanation visit is required before ongoing monitoring tasks are created for EPPV events
   * Task Duration - Define the minimum number of days a task needs to be open. This is used when a task start date is approaching a task end date.
   * Phase 1 Task Interval - Define the number of days between Phase 1 ongoing monitoring tasks (typically 14 days)
   * Phase 2 Task Interval - Define the number of days between Phase 2 ongoing monitoring tasks (typically 28–30 days)
6. Select **Save**.

#### Business Event Records

To create a Business Event record:

1. Navigate **Business Admin > Objects > Business Events**.
2. Select **Create**.
3. Select the **Business Event Type** (EPPV or PI).
4. Select **Continue**.
5. Complete the following fields:

   * Business Event Name - Enter a descriptive name
   * Start Date - Monitoring period start date
   * End Date - Monitoring period end date
   * Product - Applicable product
   * Business Event Schedule - Applicable schedule
   * Product Launch Date - For EPPV Business Events; date the product was launched
   * Issue Date - For PI Business Events; date the new PI information was issued
   * Allow Cancellation (optional) - Select the Yes radio button to enable users to cancel tasks for targets in this event
6. Select the **Active** checkbox.
7. Select **Save**.

#### Business Event Target Records

To create a Business Event Target record:

1. Navigate **Business Admin > Objects > Business Event Targets**.
2. Select **Create**.
3. Select the **Business Event Target Type** (EPPV or PI).

   The Business Event Target Type must match the Business Event Type for the associated Business Event.
4. Select **Continue**.
5. Enter at least the following information:

   * Business Event - Select the appropriate event
   * Account - Select the appropriate account
   * Child Account (optional) - Select the appropriate child account, if [Child Accounts](../Call_Reporting_2/Executing/Activities/ChildAccounts.htm) are enabled

   Ensure the child account’s parent is selected in the Account field on the Business Event Target record.

   * Pre Explain Date (optional) - Define a specific date when the target’s Pre-Explanation task is due, if applicable

   If Pre-Explanation Required is selected on a future Business Event and the Pre Explain date is left blank, the system automatically sets the Pre Explain date to the start date of the task generated by the Business Events job. If the Business Event Task start date is in the past and the Pre Explain date is left blank for an EPPV event, the Pre Explain date is set to the Purchase Date.

   * Assignee (optional) - If there is a specific user that is responsible for the target, select that user as the assignee. If an assignee is not selected, it is automatically assigned according to the following criteria:
   * Active users who have territory alignment to the account and access to the product via My Setup Products are considered as potential assignees
   * If more than one user meets this criteria, the user highest in the territory hierarchy is selected as the assignee
   * If no user meets these criteria, the account owner is selected as the assignee
   * Purchase Date (optional) - If the account has made a purchase, select the appropriate purchase date. This field can be populated at any time and drives creation of Ongoing Monitoring tasks for EPPV targets.
   * Pharmacy (optional) - If the applicable product order was placed through a pharmacy, select a value to associate the Pharmacy account for record keeping
6. Select **Save**.

#### Task Creation Logic

The following task creation logic applies when Business Event Tasks are created for Business Event Targets:

* Phase 2 is capped at a maximum of four tasks
* Phase 1 and Phase 2 Task Intervals determine how many days a task stays open, replacing the previous Task Duration logic
* When a pre-explanation is required for a Business Event Target, timing depends on whether the Purchase Date field is populated:
* If the Purchase Date is not populated, the pre-explanation task spans the entire lifecycle (start date to end date) of the Business Event
* If the Purchase Date is populated, the pre-explanation task uses the same start and end dates as the first Phase 1 task
* When a task starts near a Business Event End Date, the Task Duration is used to determine whether the task extends beyond the event’s end date:
* If the final task’s duration causes it to exceed the Business Event End Date, the task automatically extends beyond the event's end date rather than ending prior to the specified Task Duration.

### Related Topics

[Business Events Overview](BusinessEventsOverview.htm)

[EPPV and PI Business Event Tracking](BusinessEventTracking.htm)