Unable to associate child obs department with a new Parent - Error: REVMGR-21102
book
Article ID: 188515
calendar_today
Updated On:
Products
Clarity PPM SaaSClarity PPM On Premise
Issue/Introduction
REVMGR-21102: Department child cannot be updated because association mode for one of the objects associated with its OBS is set to Lowest Unit. Steps to Reproduce:
Create New OBS department ID parent
Create New OBS Department ID child
When I try to make the parent OBS a parent to the child OBS, I get the above error
Note:
This issue may only be seen for new departments, where some existing parent OBSs are able to be mapped as parents to the new department OBS child if they already have children / sub departments assigned to them.
Environment
Release : All Supported Releases
Component : CA PPM SAAS STUDIO
Cause
This is due to one or more associated objects for the Department OBS being set to "Lowest Unit"
If the department you want to make a parent did not have any children prior to changing an associated object to “Lowest Unit”, it won’t allow you to make it a parent, because the department is considered the lowest level in the OBS.
If you created a department and added children to it prior to changing one of you associated objects to “Lowest Unit”, then change one associated object to “Lowest Unit”, you can assign new departments to this existing parent. This is because in this scenario, the parent is not considered the “Lowest Unit” because it already has children beneath it
If the default, override default, or both are set to any value other than the Lowest Unit, then the values for both these fields become blank when you change the
Association Mode from Any Unit to Lowest Unit If any instance of the associated object has a unit which is not set to Lowest Unit, an error message appears. When the read-only and mandatory fields are set and you change the Association Mode from Any Unit to Lowest Unit, an error message appears.