Data Integration
Effective planning and reporting — including annual budgeting, rolling forecasts, variance analysis, and what-if scenarios — requires tight integration with multiple systems. These systems typically include the General Ledger (GL), Customer Relationship Management system (CRM), Human Resource system (HR) and other elements of the Enterprise Resource Planning system or a centralized data warehouse.
Adaptive Planning has several options for integrating with other enterprise systems, located either on-premise or in the cloud.
- Standard Adaptive Planning functionality includes the ability to import data via Excel files, and export data to Excel or flat files.
- Adaptive Planning Connectors enable automated data import and export between Adaptive Planning and other enterprise systems. Connectors are available for the most common source systems and databases, and may be deployed at any time during or after implementation.
- Adaptive Planning’s Hosted Connector is a cloud-based integration platform that allows companies to quickly and easily integrate Adaptive Planning with other cloud-based systems, such as Salesforce.com, Intacct, FinancialForce.com, NetSuite OpenAir, Plex Systems, and others.
- Adaptive Planning and NetSuite have together developed custom, best-in-class data integration. The NetSuite Connector features a simple set-up that can be completed in minutes; supports bi-directional export and import between the applications; and allows users with the appropriate permission to drill down from Adaptive Planning into the underlying transactions within NetSuite.
- Adaptive Planning APIs (application program interfaces) can be used to develop custom integrations with on-premise and cloud-based applications.
How It Works
The process for importing data via Excel is a simple matter of extracting data from a back end system (GL, HR, CRM, etc.), formatting it to map data fields to corresponding data fields in Adaptive Planning, then using the standard import functionality. Data can also be exported to a flat file.
Data integration with these same systems can be automated via the Connectors described above. The process of automatic data integration falls into three main steps:
- Automated data integration begins with extraction of data from the source system. This step extracts raw data from GL or other database tables, and transforms it into the equivalent of a trial balance report, listing accounts and amounts for the specified time period.
- Once the trial balance report is obtained, the next step is to separate the account codes into the pieces used by Adaptive Planning. This step transforms this data into an XML file acceptable for uploading, using SFTP (Secure File Transfer Protocol.)
- This step loads the XML file created in the previous step into the Adaptive Planning server, using a data integration web service. In this process, the server logs such things as the credentials of the user doing the uploading, and the timestamp of the upload. The server then performs the final step — the natural account code, department, region, and all other non-numeric fields created in the Transform step above are mapped into the corresponding fields in Adaptive Planning. This tells the server which Adaptive Planning accounts, plans, and other dimensions should receive the uploaded data. The Load step is then executed by the Adaptive Planning server.
Key Features of Connectors
- Fully customizable
- Support all data sources
- Support simple to complex mapping requirements
- Extract, transform and load data automatically
- Support audit and exception reporting, including email alerts
- Can be scheduled to import hourly, daily, monthly, or on demand
- Enable automated export of Adaptive Planning data into target systems (e.g., GL or data warehouse)
Adaptive Planning has integrated with more than 75 GL and enterprise systems. Examples of source systems where the Adaptive Planning Connector has been implemented include:
- Great Plains 10.0
- Intacct
- Lawson 9.0.1
- MAS 90 4.3
- MAS 500
- Multiview
- NetSuite
- Oracle 11.5.10.2
- Oracle E-Business 11.5
- PeopleSoft 8
- Quickbooks 2004-2010
- Salesforce.com
- SAP R3 4.6c
- Solomon 6.5/7.0
- Native SQL Server 2005
- Generic ODBC 3.x databases