The call reporting module consists of a parent call object, child call objects, and associated objects that the call functionality depends on, for example attendees, account, or call. The main objects that comprise the call reporting module are:

Call (call2__v)

The call object stores all of the information for planned, saved, and submitted calls, including the account, address, territory, and date and time for each call. There is one call row for each account on a call. For group calls, attendee details are captured as child call2__v records. For unique activity group calls, the attendee details are captured as additional related records.

The Copy Record action is not supported for call2__v records.

Call Detail (call2_detail__v)

The Call Detail object stores all of the information for any product details recorded on a call. The product detailing section on the call report enables users to identify which products or topics were discussed from a predefined list, based on products assigned to the user in My Setup Products.

Call Discussion (call2_discussion__v)

The Call Discussion object stores all of the information for product discussions captured on a call. The Call Discussion object also enables creation of different product discussion layouts, which can be applied based on call object type.

Call Sample (call2_sample__v)

The Call Sample object stores all of the information for samples or promotional items recorded on a call.

Call Key Message (call2_key_message__v)

The Call Key Message object stores all of the Key Messages recorded on a call.

Call Follow-Up Template (call_followup_template__v)

The Call Follow-Up Template object stores all of the information for any follow-up activities recorded on a call. There is one follow-up template record for each follow-up activity type recorded on a call.

Expense (expense__v)

The Expense object stores all of the expense data recorded on a call.

My Setup Product (my_setup__v)

Each user’s product assignments are stored in My Setup Products. See Using the My Setup Tab for details on the object.

Sample Lot (sample_lot__v)

The Sample Lot object holds all lot numbers for products available to users. The Sample Lot object is a private object, meaning that users only have access to the Sample Lot record they own. See Creating Records for Sample Management for more information.

Call Type

Depending on the primary account on a call report, the platform, and the types of activities captured, the value of the call_type__v field on the call2__v object is set as follows:

Call Type	Criteria
Call Only	The call is against a person OR a business account. No details or samples are recorded.
Detail Only	The call is against a person account. There is at least one detail product selected. No samples are recorded.
Group Detail	The call is against a person account on a group call, a person account with call location, or a business account. There is at least one detail product selected. No samples are recorded.
Sample Only	The call is against a person OR a business account. There is at least one sample, BRC, or alternative sample product selected. No details are recorded.
Detail with Sample	The call is against a person account. There is at least one detail product selected AND at least one sample, BRC, or alternative sample product selected.
Group Detail with Sample	The call is against a person account on a group call, a person account with call location, or a business account. There is at least one detail product selected AND at least one sample, BRC, or alternative sample product selected.
Event Only	The call is against a medical event. No details are recorded.
Event Detail	The call is against a medical event. There is at least one detail product selected.

To configure this module:

1. Ensure Configuring Accounts and Configuring the Product Catalog are complete.
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
account__v	at least R	All applicable object types	n/a	n/a
call2__v	CRED	callreport__v event__v meetingbrief__v mslmeetingbrief__v	account__v add_key_message__v attendees__v attendee_type__v call_channel__v call_type__v child_account__v child_account_id__v controlling_parent_account__v detail_section_attribute__v detailed_products__v expense_amount__v expense_post_status__v last_device__v location_id__v location_name__v object_type__v submitted_by_mobile__v trigger_timestamp__v unlock__v	Edit
			entity_display_name__v is_parent_call__v parent_call__v	Read
call2_detail__v	CRED	n/a	call2__v detail_group__v detail_priority__v product__v type__v	Edit
			is_parent_call__v	Read
call2_discussion__v	CRED	callreport__v event__v meetingbrief__v mslmeetingbrief__v	account__v attendee_type__v call2__v call_date__v detail_group__v (optional; if using detail groups) mobile_id__v object_type__v product__v user__v	Edit
			is_parent_call__v	Read
call2_key_message__v	CRED	n/a	account__v call2__v call_date__v detail_group__v key_message__v key_message_name__v product__v reaction__v	Edit
			is_parent_call__v	Read
expense__v	CRED	call__v	amount__v call2__v description__v expense_type__v transaction_date__v	Edit
			local_currency__sys	Read
expense_type__v	R	expense_type__v	active__v exclude_from__v	Read
key_message__v	CRED	n/a	active__v language__v product__v	Edit
			description__v detail_group__v display_order__v media_file_name__v	Read
user__sys	n/a	n/a	first_name_sys last_name_sys system_owned_user__sys user_identifier__v	Read

6. Select the Pages tab in the appropriate permission set.
7. Grant View permission for the Call Reporting page.

To configure this module:

1. Ensure Configuring Accounts and Configuring the Product Catalog are complete.
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
   account__v	R	All applicable object types	account_identifier__v credentials__v (optional) do_not_call__v middle_name_cda__v (optional) preferred_name__v (optional) suffix_cda__v (optional)	Read
   address__v	CRE	repmaintained__v	name__v street_address_2_cda__v city_cda__v postal_code_cda__v primary_cda__v state__v	Read
   call_cycle_entry__v	CRED	n/a	name__v duration__v	Read
   call2__v	CRED	callreport__v event__v	account__v add_key_message__v address__v attendees__v attendee_type__v call_channel__v call_date__v call_datetime__v call_type__v call2_status__v child_account__v child_account_id__v controlling_parent_account__v detail_section_attribute__v detailed_products__v expense_amount__v expense_post_status__v last_device__v location_id__v location_name__v location_text__v mobile_last_modified_date_v object_type__v submitted_by_mobile__v territory__v trigger_timestamp__v user__v	Edit
   			entity_display_name__v is_parent_call__v parent_call__v	Read
   call2_detail__v	CRED	n/a	call2__v detail_group__v detail_priority__v product__v type__v	Edit
   			is_parent_call__v	Read
   call2_discussion__v	CRED	callreport__v event__v	account__v attendee_type__v call2__v call_date__v detail_group__v (optional; if using detail groups) mobile_id__v object_type__v product__v user__v	Edit
   			is_parent_call__v	Read
   call2_key_message__v	CRED	n/a	account__v call2__v call_date__v detail_group__v key_message__v key_message_name__v product__v reaction__v	Edit
   			is_parent_call__v	Read
   expense__v	CRED	call__v	amount__v call2__v description__v expense_type__v transaction_date__v	Edit
   			local_currency__sys	Read
   expense_type__v	R	expense_type__v	active__v exclude_from__v	Read
   key_message__v	R	n/a	active__v description__v detail_group__v display_order__v language__v media_file_name__v product__v	Read
   my_setup_products__v	CRED	n/a	favorite__v	Read
   tsf__v	R	All applicable object types	address__v	Read
   user__sys	n/a	n/a	first_name_sys last_name_sys system_owned_user__sys user_identifier__v	Read

6. Grant users View permission for the following controls on the call2__v object:
   • call_attendees_section__v
   • call_details_section__v
   • delete__v - Optional; enables the Delete button
   • key_messages_section__v
   • expenses_section__v
   • more_actions__v - Optional; enables the All Actions button
   • product_discussion_section__v
   • save__v
   • submit__v
7. Select the Pages tab in the appropriate permission set.
8. Grant View permission for the Call Reporting page.
9. Navigate to Admin > Configuration > Objects > call2__v.
10. Select the Object Types tab.
11. Ensure the following values are available under Picklist Values for the call_channel__v field on each call2__v object type:
    • face_to_face__v
    • video__v
    • phone__v
    • message__v
    • email__v
    • other__v
12. Select the Layouts tab.
13. Add the following section controls to the appropriate call2__v layouts:
    • call_attendees_section__v - Enables Adding Call Attendees
    • call_details_section__v - Enables Detailing Products on the Call Report
    • key_messages_section__v - Enables Using Key Messages on the Call Report
    • expenses_section__v - Enables Capturing Expenses on the Call Report
    • product_discussion_section__v - Enables Capturing Product Discussions on the Call Report

    Adding standard or custom fields to the Fields section on section controls (for example, call_attendees_section__v) is not supported, unless specified in feature configuration.

14. Ensure the buttons__c detail form section is added to all call2__v layouts, and add the following controls to the section: 

    • save__v - Every layout on the call2__v object must include the Save control in the buttons__c detail form section
    • submit__v
    • delete__v - Optional; enables the Delete button
    • more_actions__v - Optional; enables the All Actions button

    Fields are not supported in the buttons__c detail form section, unless specified in feature configuration.

15. Place the following fields on call2__v layouts:

    • call_channel__v

    Ensure the call_channel__v field is not set as read-only on call2__v layouts. If the call_channel__v field is read-only, sync errors may occur when users save calls.

    • call_datetime__v
    • call_type__v
    • territory__v
16. Navigate to Admin > Configuration > Objects > tsf__v.
17. Select the Layouts tab.
18. Place the preferred_account__v field on the appropriate tsf__v layouts.
19. Configure additional fields for product discussions, besides the product__v field (optional):
    
    • Navigate to Admin > Configuration > Objects > call2_discussion__v
    • Select the Layouts tab
    • Place the appropriate fields in the information_vod__c section on call2_discussion__v layouts to enable users to capture additional information about product discussions. By default, the section only includes the product__v field.
20. Ensure VMOCs are enabled for call reporting:
    • Navigate to Business Admin > Objects > vmobile_object_configuration__v
    • Ensure VMOCs are active for the following objects, on the appropriate platforms:
    • account__v
    • address__v
    • call2__v
    • call2_detail__v
    • call2_discussion__v
    • call2_key_message__v
    • expense__v
    • expense_type__v
    • key_message__v
    • my_setup_products__v
    • tsf__v
    • user__sys

Configuring the Record a Call Action

Users can create a call using the Record a Call action throughout Vault CRM. These buttons are available on the account__v and medical_event__v objects, and can be added to additional object types to provide specific functionality to users as needed.

Selecting the Record a Call action creates a call for the currently active account or medical event. The default object type of the call depends on the user’s profile, object type settings, and the default_call_record_type__v Veeva Setting, if configured. On mobile device platforms, the Record a Call action displays based on object permissions and any object type restrictions set by Restricting Calls by Account Object Type.

Configuring Layout Profiles for Call Reporting

To enable differing call report layouts based on the user's profile, configure layout profiles for the call report. Layout profiles are used to control the object layouts users see when viewing an object record detail page. This enables users to view different layouts depending on their assigned profile. For more on configuring layout profiles, see Configuring Layout Profiles.

This functionality is only available on the Browser platform.

Supporting Custom Fields

Custom fields can be added to the call2__v object to better support specific business processes. However, not all field types are supported on the call report. The following field types are available for all Vault CRM platforms:

• Yes/No
• Currency
• Date
• DateTime
• Number
• Picklist
• Picklist (Multi-select)
• Long Text
• Reference (Object Reference, Lookup)
• Text

Using Criteria VQL to Filter Records is not supported on the call report.

User Object References

For data capture and reporting needs in Vault CRM implementations where user attendees cannot be added to calls through the attendee search, create a generic object reference field from the call2__v object to the user__sys object. This enables users to indicate other Vault CRM users attended a call. When adding another Vault CRM user to a call via reference fields, a child call is created for the other user, but the other user is not treated as an actual attendee.

User object reference fields are not the equivalent of the Search User section attribute. Object reference fields are for data capture and reporting purposes only.