‘Parent Organization Code’ does not change, after moving the organization units between other organization units.
Steps:
Go to Graphical Organization Structure window.
Then you can move the organizational units between other organizational units (you can drag and drop the organizational units). Before doing it, please notice that ‘Parent Organization Code’ of ‘SUB LEVEL 02’ is ‘LEVEL 01’.
Then move (Drag and Drop) ‘SUB LEVEL 02’ organization unit to ‘LEVEL 02’. But ‘Parent Organization Code’ does not change to ‘LEVEL 02’.
Page 1 / 1
Hi Ishara,
This is a known issue, for which a case already exists. According to R&D, this behavior is caused by a framework issue. As soon as the framework allows it, it will be fixed. Since it's only a display issue (in the table itself and in the graphical structure all is fine), no real harm is done.
Best regards,
Martin
Hi there,
I’d like to offer our experience as users of this screen. We were observing errors in our org unit setup where a user was reaching an incorrect conclusion based on what that field was presenting. The user was working on this page changing the HR setup and concluded that the parent ID could not be changed.
Now we know about this issue we can train our users appropriately, however, I do not think a conclusion that no harm is caused with this issue as users of this page likely will not appreciate the database side. They are making decisions based on the information presented to them in this page, if that information is incorrect, their decisions will introduce errors.
I agree, this is very confusing. we just fond this issue in our environment and it took time for us to investigate and found the issue as known.
We follow IFS Ever green and now we have 24R2SU5 but still no fix for this issue. Hope it will come soon…
@Asadan @leadingzeros @Ishara This is going to fixed only in 25R2 and not before
@R Lum Wai - I tried moving organizations in the 25R1 enablement environment and the parent organization codes changed accordingly.
@Dharshankumaar Mahendran I can only go on what the support case advised when I raised this as an issue back in January 2025 - if it has been fixed in 25R1 then that is great news
Hi @R Lum Wai - thanks for the response, the response from the support case is confusing, happy its working as expected in 25r1, Have a good day.
Hi @R Lum Wai - thanks for the response, the response from the support case is confusing, happy its working as expected in 25r1, Have a good day.
