Workday Adaptive Planning Implementation & Integration

My Adaptive integrations can include:

• Import balances
• Import transactions
• Export plan data (budget / forecast)
• Update metadata

One trick that I've developed is to load data without using Adaptive's mapping tables. Mapping can be useful but in most cases it's redundant. Normally, when you create a new level, you also need to add a mapping for it. This is a waste of effort and a possible source of error. If your cost centres include the level code as part of the name (which is good practice), I can pull the hierarchy from Adaptive and build the mapping table in code. For example, if the raw data has a cost centre codes like "4321" and the levels have names like "4321 - Facilities Management" there is no need to use mappings.

Some features and options include:

• Request parameters from the user through Adaptive's integration front end
• Pull data from source with ODBC / JDBC
• Transform the data, eg reverse credits
• Clean special characters
• Load data without using mapping
• Load unmapped elements to a default place to ensure that the accounts balance or
• Create new accounts, levels or dimensions automatically
• Move the actuals pointer to allow the loaded period to appear in forecasts
• Catch errors and messages and email the status to finance admins
• Transform extracted data and load to your database

Adaptive's API can also be used for bulk updates, like creating a large set of users or other ad hoc projects such as moving data between plan versions.

A new feature of the API allows extracting security events, which you may want for an audit or ISO 27001 compliance.