The most probable scenario is that an account or GL parent member that was mapped to the Row Set being used for the financial statement you are viewing was removed from the GL hierarchy. The Row Set is now trying to refer to a GL item that no longer exists as it did when the Row Set was created.
Example:
A Row Set was created with the GL parent item “Employee Benefits”, which housed the 401k GL account. Assume the user wants to move the 401k account to be housed directly under “Personnel Expenses” and no longer wants to roll that GL into “Employee Benefits”. So, the user moves the account to “Personnel Expenses” and proceeds to delete the “Employee Benefits” item. Once Anterra updates the hierarchy, should the user return to a financial statement or Row Set that still references the “Employee Benefits” item, they will receive the missing entities message, as that item no longer exists in the GL hierarchy, but the Row Set was not updated.
In the Edit Row Set screen, the impacted rows
should highlight red. This where the user would remove the rows from the Row
Set. In the event that the GL item was referenced in a calculation, the user
would need delete the existing impacted calculation(s), and create a new
version of the calculation(s), if applicable. This can be performed in the Calculation
Manager screen.
Once the new calculation has been created, the user would need to return the ASB Builder > Edit Row Set screen to remove the incorrect calculation from the impacted Row Set(s). The user would then add the newly created calculation, if applicable.
Upon resolving all places the GL item was being referenced, the message should be resolved and the user should no longer see any red highlighted rows in the Edit Row Set screen. Should you still have issues after attempting the above steps, please feel free to reach out to support at support@anterratech.com for assistance.