Skip to main content
Documentation
Documentation
Administrator Guide
Last Updated: 2024-09-20
Troubleshooting: Financial Plan Can't Publish

Troubleshooting: Financial Plan Can't Publish

This topic provides strategies for diagnosing and resolving problems when publishing Financial plans from Workday Adaptive Planning into Workday Financials.

Errors Prevent Publishing

Publishing configuration issues can generate error messages when publishing Financial Plans. You can use the information here to help resolve publishing issues.
Cause
Solution
There were no Planning accounts found to export.
Security:
Set Up: Plan Publishing
 in the Adaptive Planning for Financial Plans functional area.
  1. Access the
    Edit Plan Structure
     task.
  2. Select
    Structured Dimension
    .
  3. Include at least 1 Account type in the
    Account Type
     field.
  4. Verify that the Workday External System in Adaptive Planning maps the correct Planning Account Types to the Workday Account Types configured in the plan structure.
The format of exported data read from Planning causes an error because incorrect formulas in the data export from Adaptive Planning.
In Adaptive Planning, run formula validation on the version you need to publish and correct any formula errors.
An HTTP request exception occurs.
Verify the User Sync configuration and the tenant setup.
  1. Complete User Sync.
  2. Configure the Tenant Setup.
  3. Add the publishing user to your Adaptive Plan Publisher security group and enable permissions for:
    • Business Process:
      Plan Event
       on
      Import Budget
       (WS Background Process).
    • Securable Integrations Get and Put access.
  4. Verify the Publishing feature flags enabled in Adaptive Planning.
  5. Clear additional spaces or invalid characters from the UI URL and the REST URL for the tenant set up in Adaptive Planning.
There are missing worktag values for required worktag types.
Security:
Set Up: Plan Publishing
 in the Adaptive Planning for Financial Plans functional area.
  1. Access the
    Edit Plan Structure
     task
  2. Configure dimensions as optional except for Company, Ledger Account, or any other dimensions in the Level.
An Invalid Cast Exception occurs preparing the account mapping values.
Verify metadata and data mapping profiles correctly map in Adaptive Planning integration loaders. Remove any invalid or unused profiles.
Duplicate mapping profiles exist.
Security:
Integration Designer
 permission in Adaptive Planning.
  1. Remove test or unused Planning Dimension Loaders in Adaptive Planning.
  2. Review metadata and data mapping profiles in Adaptive Planning. Account and Dimension type mapping both require configuration.
No Planning accounts found in the export.
Security:
  • Set Up: Plan Publishing
     in the Adaptive Planning for Financial Plans functional area.
  • Integration Designer
     permission in Adaptive Planning.
  1. Access the
    Edit Plan Structure
     task.
  2. Examine the account set to verify the accounts that you need.
  3. In Adaptive Planning integration, verify the account mappings in the Workday External System.
A Workday Client Exception occurs.
Security:
  • Set Up Tenant Setup - Security
     domain in the System functional area.
  • Security Administration
     domain in the System functional area.
  • Data Designer
     and
    Integration Operator
     permissions in Adaptive Planning.
  1. Access the
    Edit API Clients
     task.
  2. Ensure that
    Scope (Functional Areas)
     includes System.
  3. In Adaptive Planning, ensure that the UI and Rest URL are accurate for the Workday Credential.
  4. In Adaptive Planning, select
    Test Connection
     for the Workday Credential.
A processing error occurs because the submitted task didn't authorize.
Security:
  • Set Up Tenant Setup - Security
     domain in the System functional area.
  • Security Administration
     domain in the System functional area.
  • Data Designer
     and
    Integration Operator
     permissions in Adaptive Planning.
  1. Access the
    Maintain API Client
     task.
  2. Locate the API client in the list.
  3. Verify that
    Client Grant Type
     uses
    JWT Bearer Grant
     . Some older integrations use
    Authorization Code Grant
     which dictate access based on the user who authorized the grant.
Verify the publishing user:
  • Can create Plan structures and templates.
  • Has security group access to Business Process:
    Plan Event
     on
    Import Budget
     (WS Background Process).
Invalid IDs exist for a dimension.
Security:
Data Designer
 and
Integration Operator
 permissions in Adaptive Planning.
  1. In Adaptive Planning, verify that the data loaders connected to the Workday External System.
  2. Verify that mapped dimensions don't exist in concatenated mapping.
  3. Run metadata sync manually to synchronize Workday WIDs for new dimensions, if possible.
A key not found exception occurs.
Security:
Data Designer
 and
Integration Operator
 permissions in Adaptive Planning.
Verify the mappings in the Workday External System. A dimension on the Workday Plan doesn't map to a Planning dimension in the Adaptive Planning Workday External System.
An error occurs in date ranges between the Plan and the Adaptive Planning version.
Configure the date ranges for the Adaptive Planning version to match or contain the Plan data range. The Adaptive Planning version can use dates that come before the Plan start date. The Adaptive Planning version can't use dates that come after the Plan ends.
When publishing as a proxied user, non-proxied users encounter a temporarily stalled error.
Security:
Set Up: Plan Publishing
 in the Adaptive Planning for Financial Plans functional area.
Verify that non-proxied users viewing the publish plans page have Get permissions.
An error occurs indicating a ledger account is mapped to an invalid value and that I need to map the account to a different value.
Security:
Data Designer
 and
Integration Operator
 permissions in Adaptive Planning.
  1. Within Adaptive Planning Design Integrations, try running the account loader again.
  2. If the error continues, download member mappings from the account loader to verify the account exists in the mappings.
  3. If the account isn't in the downloaded member mappings file, manually add it to the file and upload the mappings back into the account loader.
  4. If the Workday report filters out this account, remove the filter in the Workday report.
  5. If the Workday data source in Adaptive Planning Design Integrations filters out this account, remove the filter.