2024 Financial Planning change log

This page displays the change log for all Financial Planning releases in the year 2024.

NOTE: For links to the change logs and release notes for all Financial Planning releases, see Change log library.

General Availability releases

GA 2024.4 (11/18/24)

This release includes the following enhancement and issue fixes.

Enhancements

This release includes the following enhancement to existing features:

Added ability to add custom columns

Users can add custom columns to the following tables:

NODE
MODEL

Improved the Transfer to FP utility

When selecting Job Code as the Management Reporting FTE Source and Reconcile Job Code to ACCT to No, the unreconciled Job Code data now appears in the Code Mapping & Validation section.

Issues fixed

This release resolved the following issues:

Issue	Description
Transfer to FP - Salaries data not reconciling when Jobcode is MR FTE Source and contract labor is present. [#101437]	Summary: When transferring data from the Management Reporting source using the Transfer to FP utility, salary data did not reconcile with the Contract Labor records. Resolution: Removed some filters to prevent duplicated and inaccurate Contract Labor amounts within the transferred data.
PFB-03786 - Operations and Expense nodes only print headers (and no details) - check all nodes. [#58124]	Summary: When printing individual Operations and Expense nodes, only headers printed (no details). Resolution: Adjusted the formatting for the templates to include details.
Transfer to FP - YR1 and YR2 JobCode data may be incorrect when Actuals/Budget is data source. [#103492]	Summary: When transferring data from the Management Reporting source with the Actuals/Budget as the data source for YR1 and YR2 using the Transfer to FP utility, the amounts were calculated inaccurately. Resolution: Corrected the formulas in the import to calculate YR1 and YR2 correctly.
Case Number 00560777 - Financial Planning code 625004. [#104791]	Summary: During the transfer to Financial Planning, records were changed from Payor 0 to Payor 1 for code 625004. Resolution: Corrected the source for the FSDetail column to ACCT_FPCode table for Payor Update.

GA 2024.3 (8/19/24)

This release includes the following enhancement and issue fixes.

Enhancements

This release includes the following enhancement to existing features:

Added benefits codes

Added all available benefits codes to the Data Collection template.

Added utility to save the annual rating agency median data

Created a utility to save the annual rating agency median data. Contact Support for assistance with loading the data.

Issues fixed

This release resolved the following issues:

Issue	Description
[Transfer to FP] Saved Period Ending values not pulling in for YR1 or YR2. [#62422]	Summary: When entering a selection for the Period Ending fields for year 1 or 2 of the Transfer to FP utility, those values were not saved. Resolution: Values selected are now saved in the Period Ending fields for year 1 or 2 of the Transfer to FP utility.
Transfer to FP - Error thrown when attempting to map JOBCODE.FPCategory (Step #7). [#91274]	Summary: An error appeared when attempting to map job codes in the Transfer to FP utility. Resolution: Users can successfully map job codes in the Transfer to FP utility.
Transfer to FP - Error thrown when Year 3 balance sheet settings updated (Step #3), then Year 3 product changed (Step #2). [#92492]	Summary: An error appeared when changing Step 2 after making a balance sheet configuration selection in Step 3 in the Transfer to FP utility. Resolution: Users can successfully make a balance sheet configuration selection in Step 3, and then change the selection of Step 2 in the Transfer to FP utility.

Issue

Description

[Transfer to FP] Saved Period Ending values not pulling in for YR1 or YR2. [#62422]

Summary: When entering a selection for the Period Ending fields for year 1 or 2 of the Transfer to FP utility, those values were not saved.

Resolution: Values selected are now saved in the Period Ending fields for year 1 or 2 of the Transfer to FP utility.

Transfer to FP - Error thrown when attempting to map JOBCODE.FPCategory (Step #7). [#91274]

Summary: An error appeared when attempting to map job codes in the Transfer to FP utility.

Resolution: Users can successfully map job codes in the Transfer to FP utility.

Transfer to FP - Error thrown when Year 3 balance sheet settings updated (Step #3), then Year 3 product changed (Step #2). [#92492]

Summary: An error appeared when changing Step 2 after making a balance sheet configuration selection in Step 3 in the Transfer to FP utility.

Resolution: Users can successfully make a balance sheet configuration selection in Step 3, and then change the selection of Step 2 in the Transfer to FP utility.

GA 2024.2 (5/20/24)

This release includes the following enhancements and issue fixes.

Enhancements

This release includes the following enhancement to existing features:

Disable year in data transfer

Users can now disable Year 3 in a data transfer.

Issues fixed

This release resolved the following issues:

Issue	Description
PFB-08669 - Transfer to Financial Planning errors on Net Assets. [#58122]	Summary: When selecting Year 3 in the Transfer to Financial Planning utility, duplicate codes were created related to Net Assets, preventing the import from saving. Resolution: Corrected the code to only create unique codes and save the import.
FP CP Consolidating Report Error Upon Scenario. [#92191]	Summary: The Scenario field displayed an error even though the report was working properly. Resolution: The Scenario field now displays the correct scenario name.

GA 2024.1 (2/19/24)

This release contains no new customer-facing features, enhancements, and issue fixes.

Patch releases

Patch 2024.4.1 (11/25/24)

This patch release includes the following issue fix.

Issues fixed

This release resolved the following issue:

Issue	Description
Some 2026+ FP file group tables created with 2025 data populated. [#112676]	Summary: Records for the year 2025 appeared in some tables that were created for 2026 and beyond. Resolution: Changed the year from the prototype file group from 2025 to 9999. This change determines that the File Group Year for the prototype file group cannot be a year for which a user would have a file group.

Issue

Description

Some 2026+ FP file group tables created with 2025 data populated. [#112676]

Summary: Records for the year 2025 appeared in some tables that were created for 2026 and beyond.

Resolution: Changed the year from the prototype file group from 2025 to 9999. This change determines that the File Group Year for the prototype file group cannot be a year for which a user would have a file group.