Account-Stamped Data

• key_stakeholder__v – Object that stores key stakeholders on an account plan
• key_stakeholder_name__v – Text value of the key stakeholder's name. Used for stakeholders not in the CRM system. Stamped when the Key Stakeholder is populated.

User-Stamped Data

• account_team_member__v – Stores team members on an account plan
• team_member_name__v – Text value of the team member on an account plan. For users who are not in the CRM system. Stamped when the Team Member is populated.

Account-Stamped Data

• call2__v – Stores the main call header information
• disbursed_to__v – Used to record sample disbursement information (if any). This contains all PDMA required fields (name, address, etc.) in text format. This value is copied in to the sample transaction object.
• supervising_physician_name__v – The name of the Supervising Physician at the time of the Call. The Supervising Physician of the Call is for a mid-level practitioner in a state where the collaborative relationship with the supervising physician is required to be captured on the call record. Stamped value.

Account-Stamped Data

• em_attendee__v – Object that stores attendees at events for Events Management
• furigana__v – Furigana for Japanese name. If the attendee is an Account, this data is copied from the Furigana field on the account.
• attendee_name__v – Text field to store the name of an attendee. Used for entering non-system attendees. If an account or user is listed as an attendee, this field populates automatically.
• first_name__v – Stores the attendee's first name
• last_name__v – Stores the attendee's last name
• em_speaker__v – Stores a list of people to be used as event speakers for Veeva Event Management
• first_name__v – Used to store the speaker’s first name. This is a stamped field.
• last_name__v – Used to store the speaker’s last name. This is a stamped field.
• middle_name__v – Used to store the speaker’s middle name. This is a stamped field.
• furigana__v – Used to store the speaker’s furigana representation. This is a stamped field.
• expense_header__v – Aggregates details of an expense line, such as the payee, the person who incurred the expense, and the payment status. Represents an invoice.
• payee__v – The entity that was paid. Stamped field storing the account name or surname.
• incurred_expense__v – The entity who incurred the expense. Stamped field.
• event_attendee__v

• attendee_name__v – Text field to store the name of an attendee. Used for entering non-system attendees. If an account or user is listed as an attendee, this field populates automatically.
• first_name__v – Stores the attendee's first name
• last_name__v – Stores the attendee's last name

Custom fields with the same API name are automatically stamped from em_attendee__v to event_attendee__v.

User-Stamped Data

• em_event_team_member__v – Team members for events in Veeva Event Management. Team members are automatically granted edit permission to an event.
• first_name__v – Stores the team member's first name
• last_name__v – Stores the team member's last name

Account-Stamped Data

• inventory_monitoring__v – The Inventory Monitoring object holds general information about the inventory monitoring activities that took place
• account_name__v – Stores the Account Name

Account-Stamped Data

• medical_inquiry_fulfillment__v – Captures the information from the initiating Medical Inquiry request, the current Assignee, and the Fulfillment Status
• account_display_name – Veeva internal field that ensures proper display of Account Name after account merges or territory realignments

User-Stamped Data

• stakeholder_clinical_trial__v – Object containing Clinical Trial participant information
• participant__v – personal data stamped about the user associated with the Clinical Trial
• stakeholder_publication__v – Object that stores publication participation information
• participant__v – Stamped data about the user associated with the publication

• event_attendee__v – This is a child object of medical_event__v. One row represents an entity (Account or User) who has been invited to attend to the Medical Event
• attendee__v – The text of the person selected in either the Account or User Lookup. This is populated by a Trigger on Save
• first_name__v – Stores the attendee's first name
• last_name__v – Stores the attendee's last name

Account-Stamped Data

• sent_email__v – Contains information about the Approved Emails sent to the accounts
• account__v – Lookup to the Account object
• bcc__v – Email address of an account (optional)
• email_content__v – The HTML of the email that was sent to the Account, may contain Account related information
• email_config_values__v – Token values for the Account related tokens are stamped in this field
• account_email__v – The email address of the Account to which email was sent
• email_activity__v contains information about the activities that occur on an Approved Email sent to the Account
• event_msg__v – The email address of the account to which email was sent
• multichannel_consent__v – Contains the information about consent captured for the Account
• account__v – The account whose consent information is stored
• channel_value__v – The channel value based on what channel the consent is for
• signature__v – The signature of the account stored in base64 format

Account-Stamped Data

• order__v – The Order object holds information on order quantities of selected product(s) for a selected account or account group. Price, applicable discounts and relevant shipping information are also available.
• account_name__v – Store the Account's name, stamped from Account lookup at the time of Order creation

Account-Stamped Data

• account_authorization__v – Contains account-related attributes related to licensing sampling controls
• supervising_account_name__v – The Account Name of the Supervising Account. Used to display the Supervising Account on Call if outside of a User's territory.
• sample_limit_transaction__v – Audit object, records all the sample limit records (even if the sample limit records are deleted).
• account_name__v – Account for which the Sample Limit was applied. Text value of Account Name.
• sample_order_transaction__v – Sample Order Transaction maintains and controls all transactional data related to Sample Orders, BRCs, and Sample Requests for PDMA and FDA compliance.
• account_name__v – The Account Name field stores the textual name of the Account that ordered the Sample. This includes a concatenation of the Account's Salutation, First Name, Last Name, and Credentials.
• sample_order_transaction_audit__v – Sample Order Transaction Audit is a read-only object that stores audit history of updates and deletions of Sample Order Transaction records. A row is created here only if a sample order transaction has been updated or deleted.
• account_name__v – Account Name is the audit representation of the Account Name field on the Sample Order Transaction object.
• Sample transaction – Sample Transaction maintains and controls all transactional data related to Samples for PDMA and FDA compliance.
• disbursed_to__v – Disbursed To represents the concatenated fields of Account Name, Account Title, Account License, Call Address and Call Date for a Disbursement Sample Transaction.
• sample_transaction_audit__v – Sample Transaction Audit is a read-only object that stores audit history of updates and deletions of Sample Transaction records. A row is created here only if a sample transaction has been updated or deleted.
• account__v – Account is the audit representation of the Account field on the Sample Transaction object
• content_acknowledgement__v – maintains fulfillment of Content receipt signatures. The following fields: Title, First, Middle, and Last Name fields on the Acknowledgment of Content screen default to the Person Account associated with the shipment. Users can overwrite these values with information pertaining to the person who signs for the receipt of the samples. A concatenated string of the name fields is captured in the received_by__v field.
• received_by__v – The textual name of the person signing for the receipt of the product shipment as indicated on the AOC Signature page.
• received_by_firstname__v – Stores the first name of the Receiver in the Content Acknowledgment form.
• received_by_lastname__v – Stores the last name of the Receiver in the Content Acknowledgment form.
• received_by_middle__v – Stores the Middle name of the Receiver in the Content Acknowledgment form.

Account-Stamped Data

• mc_cycle_plan_target__v – Defines a Cycle Plan Target and the overall interaction values assigned to the Target
• Custom pull-in fields – Customers may define additional MCCP Target fields to be pulled into the mc_cycle_plan_target__v page to aid in identifying the Target. Pull-in fields can be created to retrieve information from the following source objects: account__v, address__v and tsf__v. Source values are stamped into the pull-through field to preserve the historical value at the time of stamping.
• cycle_plan_target__v – This object stores the Cycle Plan Target is an Account that is included in a Cycle Plan
• Custom pull-in fields – Customers may display additional information per Cycle Plan Target. Pull-in fields can be created to retrieve information from the following source objects: account__v, address__v and tsf__v, allowing for ease of identification of each target account. Source values are stamped into the pull-through field to preserve the historical value at the time of stamping.
• cycle_plan_detail__v – This object holds the number of planned and actual calls, per product, for each Cycle Plan Target
• Custom pull-in fields – Customers may display additional information via pull-in fields created to retrieve information from the Product Metrics object. Source values are stamped into the pull-through field to preserve the historical value at the time of stamping.

Account-Stamped Data

• survey_target__v – A survey record that combines header information, questions, an account, and an assigned user
• account_display_name__v – Account Name stamped at the time of Survey Target creation