Configuring Accounts
In this topic you can find information on Account components as well as all of the configuration steps you need to use Accounts out of the box.
Accounts Objects
The Accounts module incorporates objects covering account creation, modification, and tracking.
Account Details
- account__v – The initial object for creating and working with an account
- address__v – This object stores all addresses for account profiles. It also stores physicians’ DEA and state license information.
- affiliation__v – This object stores affiliations between person accounts and business accounts visualized in the Sphere of Influence module
- child_account__v - This object stores the hierarchy relations between person accounts and business accounts in a Parent-Child, HCO-HCO, or HCO-HCP manner. These relationships are displayed in the Account Hierarchy.
Account Territory Management
- tsf__v – This object stores territory-specific fields for an account
Account Change Management
- data_change_request__v – This object stores information for the data change request header
- data_change_request_line__v – This object stores information for data change request lines
- dcr_field_type__v – This object indicates DCR-controlled fields and which changes need to be sent to Veeva Network
My Accounts
- account_list__v – This object stores a list of accounts
- account_list_item__v – This object’s records represent individual accounts in lists on the account_list__v object
- view__v - This object stores information about Account Views
Accounts Object Types
Object types are used on the Accounts object.
There are nineteen related object types on the account__v object:
- board__v – board membership account
- distributor_branch__v – distributor branch account
- distributor__v – distributor account
- employer__v – employer account
- government_agency__v – government agency account
- hospital_department__v – hospital department account
- hospital__v – hospital account
- institution__v – institution account
- kol__v – key opinion leader
- laboratory__v – laboratory account
- mco_plan__v – managed care plan account
- mco__v – managed care organization account
- organization__v – non-MCO organization
- personaccount__v – person account
- pharmacy__v – pharmacy account
- practice__v – medical practice account
- professional__v – medical professional account
- publication__v – publication account
- wholesaler__v – wholesaler account
Configuring Accounts for
To get started with Accounts, complete the configuration steps below.
- Verify established territories exist. Displaying My Accounts requires an established Territory Hierarchy with users and accounts assigned to territories.
- Grant the following permissions for all users:
Object Object Permission Object Types Fields Field Permission account__v
CRED
all
beds__c
departments__c
account_class__v
account_group__v
account_identifier__v
account_search_business__v
account_search_firstlast__v
account_search_lastfirst__v
account_type__v
aha__v
alternate_name__v
approved_email_opt_type__v
atl_last_update_date_time__v
business_description__v
business_professional_person__v
call_reminder__v
career_status__v
clm_opt_type__v
color__v
commercial_patient_days_1000__v
commercial_premiums_pmpm__v
contracts_process__v
country__v
country_code__v
credentials__v
customer_master_status__v
default_inventory_monitoring_type__v
default_order_type__v
do_not_call__v
do_not_create_child_account__v
do_not_sync_sales_data__v
enable_restricted_products__v
exclude_from_zip_to_terr_processing__v
external_id__v
formatted_name__v
furigana__v
gender__v
hmo__v
hmo_pos__v
hmo_market_shr__v
hospital_type__v
id__v
id2__v
inventory_monitoring_type__v
investigator__v
kol__v
language__v
master_align_id__v
me__v
medicaid__v
medical_expenses_pmpm
medical_loss_ratio__v
medicare__v
middle__v
mobile_id__v
model__v
national_company_id__v
national_healthcare_id__v
net_income_loss_000__v
no_orders__v
npi__v
offerings__v
order_type__v
- ownerid__V
payer_id__v
pdrp_opt_out__v
pdrp_opt_out_date__v
photo__v
pmpm_income_loss_000__v
ppo__v
ppo_pos__v
practice_at_hospital__v
practice_near_hospital__v
preferred_name__v
regional_strategy
restricted_products__v
sample_default__v
segmentations__v
speaker__v
specialty_1__v
group_specialty_1__v
group_specialty_2__v
specialty_2__v
spend_amount__v
spend_status__v
spend_status_value__v
suffix__v
target__v
tax_status__v
total_lives__v
total_mds_dos__v
total_pharmacists__v
total_physicians_enrolled__v
total_revenue_000__v
total_sent_message__v
union_id__v
country_user__v
veevaid__v
vl_link__v
vl_url__v
Read
territory_test__v
primary_parent__v
Edit
account_list__v CRED n/a n/a n/a account_list_item__v
CRED
n/a
n/a
n/a
account_overview_layout__v
R
n/a
timeline_engage__v (Field App Control)
Read
address__v
CRE
all
- account__v
- address_line_2__v
- appt_required__v
- billing__v
- brick__v
- business__v
- city__v
- comment__v
- controlled_address__v
- controlling_address__v
- country__v
- customer_master_status__v
- entity_reference_id__v
- external_id__v
- fax__v
- fax_2__v
- home__v
- inactive__v
- include_in_territory_assignment__v
- latitude__v
- license__v
- license_expiration_date__v
- license_status__v
- license_valid_to_sample__v
- lock__v
- longitude__v
- mailing__v
- map__v
- master_align_id__v
- mobile_id__v
- network_cds_entity_id__v
- network_dea_entity_id__v
- network_distributor_entity_id__v
- network_license_entity_id__v
- network_rxa_eligible__v
- no_address_copy__v
- office_notes__v
- phone__v
- phone_2__v
- network_sample_eligibility__v
- sample_send_status__v
- sample_status__v
- shipping__v
- source__v
- staff_notes__v
- state__v
- zip__v
- zip_4__v
Read
- best_times__v
- primary__v
Edit
address_coordinates__v
CRED
ios__v
- address__v
- geocode_fail__v
- last_geocode_date__v
- latitude__v
- longitude__v
- user_detail__v
Edit
affiliation__v
CRE
n/a
- role__v
- to_account_name__v
- to_account_record_type__v
Read
call__v
C
callreport__v
n/a
n/a
child_account__v
CRED
n/a
- alternate_name__v
- best_times__v
- child_account__v
- child_account_identifier__v
- child_account_search_lastfirst__v
- child_affiliation_count__v
- child_furigana__v
- child_name__v
- child_record_type__v
- copy_address__v
- customer_master_status__v
- external_id__v
- external_key__v
- formatted_name_furigana__v
- hierarchy_type__v
- location_identifier__v
- master_align_id__v
- mobile_id__v
- network_primary__v
- parent_child_furigana__v
- parent_account__v
- parent_account_identifier__v
- parent_affiliation_count__v
- parent_child_formatted_name__v
- parent_child_name__v
- parent_furigana__v
- parent_name__v
- parent_record_type__v
- primary__v
Read
childaccount_tsf__v
RE
n/a
- child_account__v
- external_id__v
- my_target__v
- territory__v
Edit
multichannel_activity__v
RE
n/a
- icon__v
- color__v
Read
record_type_name__v
Edit
multichannel_activity_line__v
R
n/a
n/a
n/a
record_type_name__v
Edit
order__v
R
n/a n/a n/a order_line__v R n/a n/a n/a preferences__v
RED
n/a
- last_account_view_used__v
- last_view_used__v
Read
product_metrics__v
at least R
n/a
n/a
n/a
territory__v R n/a n/a n/a tsf__v
at least CRE
n/a
territory__v
Read
user__v
R
n/a
security_profile__v
Read
user_teritorry__v
R
n/a
- territory__v
- user__v
Read
view__v
CRED
n/a
n/a
n/a
vmobile_home_page_layout__v
n/a
n/a
mc_activity__v (Field App Control)
Read
vmobile_object_configuration__v
R
n/a
security_profile__v
Read
- Enable the View App Page.
- Populate the Person Account Object Types Veeva Setting by selecting the account__v object types corresponding to person accounts. For example, Person Account, Professional, KOL.
Page Layout
For users managing the account hierarchy, add the Members or Member Of related list to the corresponding Account or PersonAccount page layouts.
Child Accounts
Add the desired child_account__v fields to the appropriate account__v object page layouts. For example, on the Professional page layout, you may want to add the Primary Parent field to the Account Information section.
Veeva Messages
Enter a comma-delimited list of column names in the ACCOUNT_LIST_COLS Veeva Message to display different account, address, or TSF-related information for each account in an account list. Use the following format: Object_API_Name.Field_API_Name.
For example, account__v.name__v,address__v.name__v,address__v.city__v
To add a column to the account list, include the column name in the ACCOUNT_LIST_COLS Veeva Message. Verify users have at least read field permission to all of the fields defined in the ACCOUNT_LIST_COLS Veeva Message.