Spreadsheet Import

Prerequisites

Required permissions:
Import Capabilities and edit access to the specific intersections you want to import data to.
Or Import to All Locations, which enables import to all areas, regardless of location or level access.
To validate imports, the importing user should have at least Full View access to all intersections where data imports.
For transactions import, you must have the transactions module and Reference: Transactions.
Know the sheet name and Concept: Sheet Types the data will import to.
Have an export from your ERP or other source system in a CSV, XLSX, or other file you can copy data from.
To make the process efficient, verify that the accounts, levels, and dimensions your data values need to load to already exist in Adaptive Planning.

Navigation

Basic Steps

Select the import type and where you are importing from.
Select where to import to.
For spreadsheet imports, download and fill in a template for one of the following:
Modeled Data
Cube Data
Standard Data
Transactions Data
Import the template and select your account, level, and dimension value mappings if applicable.

Select the Import Type

Select Where to Import From

Select Where to Import To

Enter Template Columns and Date Formats for Spreadsheet Imports

Date Formats for Import

The following legacy formats for dates are accepted within time period columns:

Excel Date Format: Adaptive Planning will find the time period that contains this date at the appropriate time strata.
Text strings in the format MMM-YYYY (e.g. jun-2016): If your organization configured a custom calendar, this format will not be accepted.

The preferred method of entering dates within imported files is to use time period codes. See Steps: Change Calendars.

Fill in a Standard Data Template

Standard Sheet Data Import Columns

Account (Required): An account identifier from your external system such as an account name or account code. It cannot be empty. This column can also accept the header Account Code.
Level Code (Required): Organization level codes from your general ledger. It cannot be empty.
Split Label: Used to distinguish between two or more splits. It can be left blank if it isn't needed.
Region Code: This is an example of a custom dimension column and can be renamed to any dimension in Adaptive Planning, or it, along with its dimension name column can be deleted. Add dimension code columns to specify more dimensions. Every dimension value must have a unique dimension value code.
Region Name (Optional): This is an example of a custom dimension column and can be renamed to any dimension in Adaptive Planning, or it, along with its dimension code column, can be deleted. If the name column for a dimension doesn't exist, the dimension code is used for the dimension name. If the dimension name column exists, you must populate its cells. Duplicate dimension value names can exist only when their dimension value codes differ.
Time Period: Represented by codes of time periods at the import accounts' time strata, or any date within the target time periods. Requires at least one time period of data.

Standard data templates come with a sample row of data to help you understand how to fill the template.

Standard Data Example Import Template

The example below shows a standard data import template. Standard data templates come with a sample row of data to help you understand how to fill them out.

	A	B	C	D	E	F	G	H	I
1	Account	Level Code	Split Label	Region Code	Region Name	01/2018	02/2018
2	Accounts Receivable	West Coast	ABC	EUR	EUR	229806.30	227238.90
3

Single Column Standard Data Import Template Example

If you select

Import without Code and Name columns for display names

on the Import page or if you turn on

Enable Single Column Data Import/Export for Display Name

in

Administration > General Setup

, your import template will look like:

	A	B	C	D	E	F	G	H
1	Account	Level	Split Label	Region	01/2018	02/2018
2	Accounts Receivable	West Coast	ABC	EUR	229806.30	227238.90
3

Fill in a Modeled Sheet Data Template

Select a sheet. You will know the selected sheet is a modeled sheet if you see Import Mode options.
Select an import mode. If your instance uses access rules, some of the options are different. See Reference: Access Rules and Your Model.
Add the imported rows to the sheet.
Replace all data in the sheet, for all levels.
Replace all the data in the sheet, but only for imported levels.
Update existing rows. Only required column is Import Key. Sheets with
Allow splits
selected do not support updates. Values in the Import Key column of your imported file must be unique.
Update existing rows and add new rows. Only required columns are Import Key, Level, and any text selectors, even when not adding new rows. Sheets with
Allow splits
selected do not support updates. Values in the Import Key column of your imported file must be unique.
Click
Download template
and follow its instructions to create the columns and fill in the data you need to import.
Click
Choose File
and browse to the template you edited and click
Import
.
Select an
Import Key
for import modes that update rows. Choose a custom dimension or level to indicate the rows in the modeled sheet your import will update. Any rows that match the import key will update. Values in the Import Key column of your imported file must be unique.
Select how you want
Adaptive Planning
to map account identifiers, levels or dimension values from your file.

Modeled Sheet Import Columns

Required fields and columns for modeled sheets vary depending on the model sheet definition.

Fill in a Cube Sheet Data Template

Select a sheet. You will know if the selected sheet is a cube sheet if you do not see Import Mode options.
Click
Download template
and follow its instructions to create the columns and fill in the data you need to import.
Click
Choose File
and browse to the template you edited and click
Import
.
Select how you want
Adaptive Planning
to map account identifiers, levels or dimension values from your file.

Cube Sheet Import Columns

Level Code (required): Organization levels from your general ledger. It cannot be empty.
Account (required): An account identifier from your external system such as an account name or account code. It cannot be empty.
Custom Dimensions (required): All other labeled columns represent Custom Dimensions available on the cube. Each dimension requires a dimension code column. Enter codes of values in each dimension for each row.
If the name column for a dimension doesn't exist, the dimension code is used for the dimension name. If the dimension name column exists, you must populate its cells. Duplicate dimension value names can exist only when their dimension value codes differ.
The final columns represent time periods which contain the data. Values in these columns are the values which will import into the corresponding location in the cube. A value of 0 imports as a blank value to allow for erasing data in the cube. Titles of time period columns are codes of time periods at the import accounts' time strata, or any date within the target time periods.

Cube Sheet Example Import Template

A Product Revenue Cube Sheet may require columns for:

Level Code
Account
Customer Code
Customer Name
Product Code
Product Name
and at least one time period

	A	B	C	D	E	G	H
1	Level Code	Account Code	Customer Code	Customer Name	Product Code	Product Name	01/2015
2
3

Single Column Cube Sheet Example Import Template

If you select

Import without Code and Name columns for display names

on the Import page or if you turn on

Enable Single Column Data Import/Export for Display Name

in

Administration > General Setup

, your import template will look like:

	A	B	C	D	E
1	Level	Account	Customer	Product	01/2015
2
3

Select or Add Mappings

Data Import to Locked Levels in Sheets

Submitted for Review
Approved
Approved and Locked