---
schema_version: "1"
id: aa204ed65a38d60ba7f39c8ffd83a279400bb6ac7530118dd8d96bf62d025731
title: The Intelligent Sales Data Model
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/admin_intelligent_sales_data_model.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.admin_intelligent_sales_data_model.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: c9b3a8ba7591cf84649194669a37262fe21d1c471ab1ef44896e2742ba2d58f3
description: Intelligent Sales uses many objects to work its magic for your sales teams. But not all user roles interact directly with these objects. Admins interact with them more than sales reps or other field-oriented roles.
products:
  - Life Sciences
release: "264"
---
# The Intelligent Sales Data Model

Intelligent Sales uses many objects to work its magic for your sales teams. But not all user roles interact directly with these objects. Admins interact with them more than sales reps or other field-oriented roles.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition">
      <colgroup>
        <col>
      </colgroup>
      <tbody>
        <tr class="">
          <td class="slds-cell-wrap" style="vertical-align:top;">
            <p>Available in: Lightning Experience</p>
            <p style="margin-bottom:0;">Available in: <strong>Enterprise</strong> and <strong>Unlimited</strong> Editions with Health Cloud
              or Life Sciences Cloud</p>
          </td>

        </tr>
      </tbody>
    </table>

The Intelligent Sales data model includes these objects.

Account

Hospitals and providers that your organization deals with.

Patients that your devices are registered for in a surgical visit. If you use the Patient Registration flow in your action plan template, it automatically creates these records for you when the visit is completed. If Person Accounts are enabled for your Salesforce org and the sales rep has access to person accounts, the record created is always a person account record. And if not, it’s a business account record.

Action Plan Template

Reusable templates that add assessment tasks to visits.

Address

The address details for your locations.

Assessment Indicator Definition

The data type for the quantities recorded in generic visit key performance indicator records. For cycle counts, the data type must always be Number.

Assessment Task

Tasks sales reps complete during a surgical visit. The visit creation flow creates these records for you.

Contact

The point of contact for your sales reps at a given account location.

Generic Visit Key Performance Indicator

The expected quantities and the counted quantities of a product at an inventory location. As an admin, you create only a template record in this object, leaving all the value-related fields blank. Instance records are created when a cycle count is initiated, and the value-related fields are filled during the cycle count. At the time of execution, instance records for key performance indicators are created for a visit based on the Generic Visit Key Performance Indicator definition record. Actual and expected product values are populated during a visit based on your inventory records in Salesforce.

Generic Visit Task

The cycle count task for a specific product. Generic visit task records act as definition records that the system uses to create instance records for specific visits. At the time of execution, instance records for visit tasks are automatically created for a visit based on the Generic Visit Task definition record.

Generic Visit Task Context

The product item context for a generic visit task. Because these records must be associated with product item records, you need to create separate generic visit task context records for every product at every inventory location. Generic visit task context records act as definition records that the system uses to create instance records for specific visits. At the time of execution, instance records for visit task context are automatically created for a visit based on the Generic Visit Task Context definition record.

Generic Visit Task Context Relation

The junction object that connects generic visit task records with generic visit task context records. These records act as definition records that the system uses to create instance records for specific visits. At the time of execution, instance records for visit task context relation are automatically created for a visit based on the Generic Visit Task Context Relation definition record.

Location

The locations of different hospitals and your sales reps' inventories.

Order

This object isn’t a required part of the Intelligent Sales data model and is only used with the Order Authorization flow. When you use the order authorization flow in your action plan template, an order record is automatically created with billing details, including the product, quantity, and amount.

Product

The products your organization provides.

Product Availability Projection

The information about the projected availability of products related to visits and transfer requests. Don’t create or edit any records in this object; its data is managed automatically. Give your users read access to this object so that they can see their inventory projections in the Intelligent Sales app.

Product Fulfillment Location

A combination of records that ties a sales rep to an inventory, an account, and an account location.

A product fulfillment location consists of these references:

- A product
- An account that orders the product
- The location of the account
- The location of the product inventory fulfilling the order
- The sales rep responsible for the inventory and the location

Product Item

A combination of a product, the location of its inventory, and the quantity available at that location. If your product is serialized, the initial quantity for the Product Item record must be zero. Any change to the quantity is automatically handled based on changes in Serialized Product.

Product Request

The date by which a sales rep needs a transfer to happen. The request transfer flow creates these records for you.

Product Request Line Item

The junction object that connects a product request record and the corresponding product transfer record. The request transfer flow creates these records for you.

Product Required

The products that are added as required for different visits. The visit creation flow creates these records for you.

Product Transfer

Product transfers requested by sales reps when they have shortfalls. The request transfer flow creates these records for you.

Serialized Product

The serial numbers of individual products and the product item records that they’re associated with. Each new serialized product that’s associated with a product item record automatically increases the Product Item record quantity by one.

Visit

Visits created by sales teams to fulfill product orders from accounts or perform cycle counts for their inventories. The visit creation flow creates these records for you. This data model is centered around the Visits object.

Visited Party

The contacts sales reps visit at accounts. The visit creation flow creates these records for you.

Visitor

The sales reps assigned to different visits. The visit creation flow creates these records for you.

Work Type

The duration-related properties of a visit. For surgical visits, select the Is Used For Inventory Projection checkbox. For cycle count visits, select the Cycle Counting checkbox, and when applicable, the Blind Cycle Counting checkbox.