Skip to main content
Adaptive Insights
Knowledge and Support - Adaptive Insights

Object Modeling

Only available with Adaptive Insights for Sales

The Object Modeling page lets you

  • Map columns from transaction tables or modeled sheets to the modeled sheet and cube sheets required for Territory Map Charts. The tables or sheets hold data from your imported sales transactions or customer relationship management system (CRM). From the cube sheet, you can drill into the transaction table or modeled sheet. 
  • Select the modeled sheets that contribute selections in their rows to named regions for sales region management.
  • Select the Total Addressable Market (TAM) modeled sheet used for sales region management.

Dimensions for sales representative, geography, and sales region need to exist before you begin mapping. For the geography dimension, the area codes, zip codes and states of sales territories must be dimension values. Dimension values can be imported with the Planning Dimension Loader that is available with Integration. Your sales representative's names become dimension values for the sales representative dimension. Your sales region names become dimension values for the sales region dimension.

Object Modeling

Before You Begin

  • To access Object Modeling you need the Transactions Access, Model Management Access, Model, and Transactions permissions.

How You Get There

To get to Object Modeling, click navicon.gif and Modeling. In the Sales Planning menu, choose Object Modeling.

Sales Rep Geographies

Assigning your sales representatives to their corresponding geographies requires a geographic code and a sales representative for that geographic code. The territory map chart in Discovery needs these territory assignments to be defined on a territory assignment modeled sheet.

Field Description
Geo Code The dimension used to define the geographies for territory planning. Geography dimension values can be area codes, zip codes, and states within the U.S. They are stored as dimension values so that they can be selected in modeled and cube sheets.
Sales Rep ID The dimension used to define your sales representatives. Sales representatives are stored as dimension values so that they can be selected in the territory assignment modeled sheet and in the cube sheet required for a territory map chart in Discovery.
Sales Region The dimension used to define your sales regions. Sales regions are stored as dimension values so that they can be selected in the sales region modeled sheet. Sales region dimension values also get assigned to the rows in the Total Addressable Market (TAM) modeled sheet.

Object Definition

Object definitions are collections of transaction tables or modeled sheets. You select the columns of the table or sheet to populate the cube and modeled accounts of the cube sheet needed for a territory map chart. Example definitions include sales opportunity data or customer annual recurring revenue data generated by your sales team.

When you select columns they get listed in table dot notation form like Transactiontype.Tablename.Columnname.

Up to five transactions tables can be created per Adaptive Insights for Sales instance.

Field Description
Transaction Type A transaction type is a sales team transaction table created in Modeling > Model Management > Transactions. Or, a modeled sheet created in Modeling > Model Management > Sheets. Examples include sales opportunities or customers.
ID Code The column from your transaction table to use as the ID for records in your transaction data. As an example, Salesforce uses a 15 or 18 character long unique identifier for transaction records.
Account name The cube or modeled sheet accounts to associate with the transaction table columns you need to load. The column names you select here must match the names of the modeled or cube accounts that load this data. For example, if you are loading from a OpportunityCount column in your Opportunities transactions type, your cube sheet must have a cube account Opportunities.OpportunityCount.
Start Date The column from your transaction table to use as the start date of the transactions, if needed. For example, if you select sales opportunities transactions, the created date of the opportunity in your CRM could be used for start date.
End Date The column from your transaction table to use as the end of the transactions, if needed. For example, if you select sales opportunities transactions, the date the sale closes could be used as end date.

Named Region Filter Criteria

The named region filter criteria are the modeled sheets that contribute their dimension value choices to create a sales region. Sales regions are a mix of geographic territories, market segments, named sales accounts, and/or industries that sales representatives sell to. A region can be assigned to an individual or a team. A sales region model sheet contains one row for each sales region. Each row in that sales regions sheet references a combination of the selections in other modeled sheets.

Field Description
Filter A filter is a modeled sheet that contributes dimension value selections to a named region. Multiple filters, i.e. sheets, can contribute to a named region.
Add Filter Adds a contributing modeled sheet to the named region. You can add as many contributing modeled sheets as you like. Usually, a sheet for geographies, segments, and industries contribute to a named region.

Sales Region Sheet

The sales region sheet, typically named Sales Regions, is required for creating and managing sales regions. This sheet lists sales regions as hierarchical dimensions. Each region is a dimension value within the Sales Region dimension. This sheet accepts dimension value selections from multiple sheets to compose a region.

Assignment Sheet

The assignment modeled sheet, typically named Territory Assignments, is required for creating a Territory Map Chart. This sheet matches sales representatives to the territories and market segments they are assigned to. It requires columns for the sales representative and geography dimensions.  Other columns for market segment, industry, and assignment dates are typically found on it, too.

Object Modeling - Assignment Sheet

Cube Sheet

The level from your organization structure and the cube sheet within that level that you are loading transaction data to. This is the cube sheet containing your sales representatives that you would select in a Territory Map Chart's data settings.

Object Modeling - Cube Sheet

This cube sheet must have cube accounts with account codes named after the transaction table columns that load into it.

As an example, if you are loading the OpportunityCount column from your Opportunities transactions to an Opportunities cube sheet, that cube sheet must have a cube account with the code OpportunityCount. Because cube accounts take their full account codes from the sheets they reside in, this account's code would be Opportunities.OpportunityCount and would match the transaction table column Opportunities.OpportunityCount.

Cube Account Codes

TAM Sheet

The Total Addressable Market (TAM) modeled sheet contains rows with sales information on companies, market segment, geographic location, count, and other market categories. Each row in this sheet gets assigned a sales region dimension value. The sales region dimension value then becomes a filter when used in other sheets. That dimension value will surface only the data for the selected region.

Object Modeling - TAM Sheet

Territory Service Statistics

The territory service tracks the combination of the dimensions, object definitions (transactions data), model sheets, and cube sheets required for territory map charts and sales region assignment.

You can view statistics for imports or loads to the territory service by navigating to Model > Model Management and clicking Territory Service.

Field Description
Label Attributes for the territory service. Indicates the name of the sheet loaded to, or if Cube Generation and Cube Load into Cache were triggered.
Number of records loaded The number of records loaded by the action.
Number of columns in a record The number of columns in a record loaded by the action.
Last loaded time The date and time of the last load to the label.
How long it took The duration of the last load in the format (HH:MM:SS:MS).

 

  • Was this article helpful?