Skip to main content
Documentation
Documentation
Adaptive Planning
Last Updated: 2023-06-23
Concept: Integration

Concept: Integration

The integration framework acts as a secure bridge for importing data and metadata from different data sources into
Adaptive Planning
. Data sources can include spreadsheets, databases, and cloud-based or on-premises systems. You can filter, clean, map, and merge the information coming from these sources to eliminate potential import errors. You can also schedule tasks and operations so that data automatically imports at specific times.
The architecture of the
Adaptive Planning
 Integration framework supports this flow:
  1. Connecting to sources, including
    Adaptive Planning
    , Workday, NetSuite, Salesforce, SAGE Intacct, MSDGP, and other cloud systems. Creating on-premise Agents to load data directly from Oracle or other on-site systems. Importing spreadsheets to load directly from uploaded .XLSX files.
  2. Adaptive Planning
     and Consolidation, or Dashboards taking the loaded data or metadata to update the model, accounts, sheets, transactions, or charts.
  3. Loaders mapping the data or metadata from the source system to the corresponding destination in
    Adaptive Planning
    , and loading it. The staging area for data preparation of extracts from source systems. Manual or scheduled tasks formatting and filtering the data from the staging area to hand it off to Loaders. Data Sources and Adapters extracting data from source systems.
For information on integrating Adaptive Planning with Workday HCM and Financials, see: Steps: Configure Adaptive Planning for HCM and Financials.

Business Users of Integration: Developers, Implementers, and Analysts

This architecture supports the workflows of these types of business users, with work shifting from one to the next in this order:
  1. Developers (only required for Custom Cloud Data Sources)
  2. Implementers
  3. Analysts
Each group gets a permission set with permissions in
Adaptive Planning
. Each type of business user contributes to the overall Integration workflow. Most business users function as Implementers and Analysts. Implementers configure data sources so that Analysts can run tasks. If you require a Custom Could Data Source (CCDS) to pull data from a web-accessible system, a Developer user begins the workflow by writing JavaScript to import data. The workflow then shifts to an Implementer, and finally an Analyst.

Developer Workflow

Integration Developer Permissions
The Developer user only becomes a requirement when you need a Custom Cloud Data Source (CCDS) to import data from a web-accessible system. Developers receive the permissions of Integration Developer. The developer users must be experienced javaScript programmers to make use of the APIs that pull data into
Adaptive Planning
.
  1. Define parameters.
  2. Create scripts and test them.
  3. Release the CCDS to a data designer.
Refer to the CCDS documentation to view the full CCDS workflow.

Implementer Workflow

Data Designer Permissions
The Implementer, with the Integration permissions of Data Designer, creates the data sources that Analysts use to run their tasks. Implementers:
  • Select data from columns in tables.
  • Filter that data.
  • Preview the data.
  • Merge that data with other data.
  • Prepare it for analyst users.
Analysts users can then run tasks on the data. Implementers can also grant permissions to users or groups to execute tasks. Granting permissions lets implementers restrict lower-level data entry staff to executing specific tasks without letting them access anything else.
If you require a CCDS, the Data Designer relies on the Integration Developer to first write and test JavaScript.
  1. Define data sources, including their transforms and mappings.
  2. Create loaders.
  3. Create tasks.

Analyst Workflow

Integration Operator Permissions
Analyst users (often FP&A staff), with the permissions of Integration Operator, run manual or scheduled tasks to get data into
Adaptive Planning
. Analysts can only see and execute tasks based on the launch permissions an Implementer user grants them.
  1. Run manual or scheduled tasks.
  2. Manage notifications.
  3. View the results in
    Adaptive Planning
     sheets.