FCCS Entity Hierarchy movement causing Data issue
In the month of May (P5) a Parent entity E_923 was created in FCCS entity hierarchy and an existing level 0 member E252 (which initially was under E_919) was moved to E_923. The method used for moving entity E252 was cut paste method. This method is causing the system to generate difference for Mvmts_FX_Opening. We have moved entity before using the same cut-paste method but haven't faced data issue then.
The data issue is now continuing for P6 and P7 as well, and is not consistent. The data mismatch varies over periods.
Tagged:
0