Skip to content

BDA Logo

BDA Compensation And Travel Planning Release Notes 2024.11.15.01

NOTICE

If you are on version 24.08.08 or later, please upgrade to 2024.10.03.01 or later to ensure all Comp functionalities are working properly

NOTICE

If your implementation of Compensation makes extensive use of Custom Fields 1/2 and Reporting overrides and you are running into issues with your environment--please contact the BDA Product Team for guidance on optimization and resolution.

BDA Core Technology Compatibility

This version needs at-least Core Technology 2024 11 15 01

OneStream Version Compatibility

This version is confirmed to work with OneStream version 6.3.x to 8.4.x

BDA Compensation and Travel Planning and Extensible dimensions (1)

If you are installing BDA Compensation and Travel Planning on a fresh application, Comp dimensions will get attached to the RootDim and using extensibility in these dimensions will be difficult. Keep in mind that on an existing application if you have a Top member in (UD1-UD8), Comp dimensions will use the dimension that has the "Top" member as the inherited dimension.

  1. Perform this check before installing the product.

Notes

  • If you are coming from a previous version that does not have "BDA Compensation and Travel Planning Client Content" Maintenance Unit.

    • Please download and upload Create CTP_CPX Client Content.xml to the target.

    client content xml location

    • Go to Business Rules and execute the rule to create the client content.

    Create Client Content

  • If you are coming from a version that still uses "BDA_SolutionEngineKey" to add Admin users to Compensation model.

    • Please download and upload SolutionKey MigrationRule.xml to the target.

    solution key xml location

    • Go to Business Rules and execute the rule to migrate old solution engine key users to new relational model.

    Migrate Solution key

Reserved Keywords

The following keywords cannot be used in BDA solutions (Columns aliases, member names)

  • ID
  • CalcUnit
  • Calc Unit
  • UnitName
  • Unit Name

Cube View updates needed coming to this release

If you are coming from a version prior to 2023.08.31.01, please go through the corresponding release note for the updates.

Download

New Features

Improved Functionality

Issues

Resolved
Known

Detailed New Features

Upcoming Features

Rollback upto last 5 data load

An option to roll back the loaded data to last 5 data loads

Load comparision report

A report that will show the differences between current load and last 5 data loads

Enable notifications

An option to enable notifications for Administrators for the following.

  • Calculation unit addition
  • User Management changes
  • Data Load

Solution Management

  • An option to uninstall Compensation and Travel planning.
  • An option to update/revert client configuration parameters.

Installation and Configuration Instructions

Installation

Info

The below steps must be performed for both a fresh install or an upgrade from a previous version.

  • Make sure that at least one valid workflow profile is setup and selected ahead of installing the BDA Compensation and Travel Planning.
  • If you are coming from a previous version that does not have "BDA Compensation and Travel Planning Client Content" Maintenance Unit, please talk to Product team about migrating the Config parameters to the "BDA Compensation and Travel Planning Client Content" Maintenance Unit.
  • If you are coming from a version that still uses "BDA_SolutionEngineKey" to add Admin users to Compensation model, please talk to Product team about migrating the admin users to the latest relational model.
  • Upload Zip File into Application -> Load/Extract -> Load
  • Once completed, navigate to OnePlace -> Dashboards -> BDA Compensation and Travel Planning Setup
  • Click on dashboard BDA CTP Install

    OnePlace dashboard

  • Click the button "Click to Install/Update BDA Comp and Travel Planning".

    Install screen

  • Once successful, you should see the following screen.

    Install success screen

Info

If you are using scenario type other than "Forecast", please make sure to keep text4 value in "Forecast" scenario type, removing the text will cause future installations reload everything and lead to rework.