Any changes to Project attributes in both Classic and Modern User Experience (MUX) are causing the Department OBS value to be reset to the default. If Financial plans are already created on the project, the following error is generated in Classic and Modern instead of the Department being changed: Error: The department cannot be changed to a different entity after financial plans have been created.
In Classic: If the field is not added to the Edit View in Classic, updating any Project attributes resets the Department OBS to the default whether there's already a value set or not. If the field is added to the Edit View in Classic, the issue does not happen.
In Modern UX: If the field is added to the Blueprint in MUX, updating any Project attributes on the Project resets the Department OBS to the default regardless of a value being set or not.
Note: This issue can also be observed after certain jobs such as Investment Allocation job are run.
STEPS TO REPRODUCE:
Expected Results: Department OBS remains as the value set for the project
Actual Results: Department OBS changes to the default value set on the project object
STEPS TO REPRODUCE:
Expected Results: Department OBS remains as the value set for the project
Actual Results: Department OBS changes to the default value set on the project object
Release : 15.9.1 patch 1, 15.9.2
Component : CA PPM SAAS FINANCIAL MANAGEMENT
This issue is caused by: DE60890.
DE60890 is fixed in 15.9.2 patch 1 and 15.9.3.
Important: If you run into an issue implementing the workaround above, implement the steps below as referenced in Department OBS Default value on project object cannot be changed
If the above workaround does not work, please reach out to Broadcom Support for assistance. See Contact Support for more details in how to contact support.
See also Default Department OBS not assigned if not displayed due to DE56545 fixed in 15.9.1 patch 1 and 15.9.2.
See Known Issues for the list of known defects in Clarity 15.9.2