FAQ: Load Plan and Actuals Data into Adaptive Planning

How can I make it easier to find parent values for a WID in a loader?: Create a
Parent Name
column that matches any SQL logic so you can see the parent values instead of having to look up a WID.

How can I import Adaptive Planning attribute values?: Adaptive Planning attributes store as hierarchies on the back end. Specify a parent column with a null value if you import attribute values.

How do I import aggregated journal lines?: Use one of these two methods:
Select
Manage Journal Line Summaries
within the Workday data source in Adaptive Planning to create an integration system. Imports from integration systems in managed journal line summaries support up to 5 million journal line row summaries per period.
Create reports in Workday and
Select Manage Reports
within the Workday data source in Adaptive Planning.

Why don't I see the objects that I just loaded?: Objects don't instantly synchronize into Adaptive Planning. You'll notice a delay. You can trigger a synchronization by updating a user profile in the
Users
section of
Administration
page. Change the display name in your own profile by 1 character and save it to trigger a synchronization.

How long should I wait between loading metadata and loading data with the Planning Data Loader?: Wait 15 to 30 minutes between loading metadata and loading data to ensure that a full synchronization completes.

How can I check for errors before I run a loader?: Select
Preview Loader Output
in the
Actions
pane for a loader and download the XML it generates. Examine the XML for errors.

How can I examine the content of the Preview Loader Output XML?: Open the XML file in an advanced text editor like Notepad++ or using a web browser.
XML tags indicate the hierarchy. The end of a tag gets marked by a closing
/>
.
A leaf account that has no children looks like
<account code="10000" name="Cash" />
, where 1 string of data gets wrapped by the
<
and
>
.
Hierarchical structures that contain multiple elements get terminated with a tag. Example:
</account>
.

How can I test my SQL filters before I load metadata?: Look at the results of your filters under
Tables to Import
(the Staging Area) of your data source before you run your loader.

What should I do if I know the metadata changed since the last time I loaded it?: Always use the Data Import
option when you run the loader. Errors can occur if metadata changed and a new import hasn't been run in a while. If you need to override what's in the staging area because of errors, reimport in the data source just before running the loader.

How can I filter out duplicates in a data source?: Remove duplicates on extraction from the source system. Set up the report from Workday or other source system to consolidate and aggregate within the report so that only unique rows exist in Design Integrations.

You can identify, flag, and filter duplicates to remove them for a successful load.

Create an identical data source and create a
Subquery
column with a
Does Not Equal
type and this statement:

(P.DistinctCol(ID) = R.DistinctCol(ID) AND P.DistinctCol(Label) = R.DistinctCol(Label) AND P.UniqueCol(ID) < R.UniqueCol(ID))

The
P
represents your source table and
R
represents the identical copy.
The
DistinctCol
represents the columns that you want a distinct value of.
The
UniqueCol
must be a unique record throughout the entire data set, like
Employee ID
.
The result of the subquery will be True/False. Any duplicate sets should have 1 True result and the rest False. There isn’t much control as to which record gets the True, so verify that you don't need other columns with varying values.
You can use the
Subquery
column as a filter.

How can I prevent duplicate Position rows from the PLN ALL Positions report as part of publishing a workforce plan?: The
Plan Version ID
wasn't included as a required prompt every runtime within the Workday Data Source. Add
Plan Version ID
so that it always prompts as a version parameter.

What does an error like Period (with stratum id=0) at 12/1/2019 12:00:00 AM not found mean?: This error indicates the need for a metadata sync. To resolve it, contact Adaptive Planning Support. Resolving this error won't cause an impact or outage.

What does an error like Following subtree root nodes cannot be recognized in Planning mean?: A parent node listed for a member doesn't exist within the data source. The parent-child hierarchy must exist for all of the rows of the data source, from the bottom of the hierarchy to the top. The full hierarchy must load within the same loader.

What does an error like Unable to re-parent account underneath a Leaf account mean?: An existing member without children always identifies as a leaf member. The loader might not be able to add children to existing leaf members. Fix this by:
Manually creating a place holder member in Adaptive Planning.
Running the loader again.
Deleting the place holder member.

What does an error like The following Source Accounts result in the same account in Planning mean?: This error can occur if the loader tries to change a name to an existing value or values in the loader. It can also occur with multiple changes to the metadata mappings, SQL columns, and SQL filters. The most effective way to clear out the metadata mappings is to delete and recreate the metadata loader.

What does an error like One or more locked versions use this account. Changing how it rolls up may change values in these locked versions mean?: This error occurs when adding or moving members that affect rollup members. Select
Proceed with Warnings
in the loader to continue.

What does an error like The account __________ already exists within the system mean?: An account code in the loader uses the same name as an existing account.; If you find no duplicates in your structure you're trying to load, sometimes this is a false error message, and can be resolved by deleted the Loader and creating a new one.

What does an error like The Workday report defines more than one column which resolves after cononicalization to the same label 'dimension_id'. Change the XML Alias of these report columns to uniquely identify them without relying on periods, underscores, or other special characters mean?: This error occurs when two Workday Data Source columns use the same XML alias in a Workday report, or when the XML alias contains special characters that generate a duplicate alias. Duplicate XML aliases cause duplicate staging columns to silently populate with values from only one of the two columns.; This error can occur when a Workday report includes an object with XML Alias MyObject
. When imported, Adaptive Planning integration automatically creates two columns with column names based on the underlying alias MyObject_Label
and MyObject_Id
. If you already have another column in the report with alias MyObject_Id
or MyObject.Id
then the automatically created column name may conflict with your column.; Change the newest column that was added. A change to an existing column that has downstream SQL formulas will break the connection, and require you to re-link.; Remove any special characters in your XML aliases from the Workday Report and use unique labels for each one.; An update to XML Aliases requires the
Import Structure
step prior to
Import Data
.