Cleaning Data Tables of old data
I recently discovered that data from deleted Scenarios is not removed from many of the application data tables (XFW_PLP_Plan, XFW_PLP_Register, ...) Does anyone know why it remains and is it safe to remove as the scenario no longer exists. I would think removing the old data would improve performance and reduce db size. Or am I unaware of the tools to perform such maintenance?
Member Dimension correction
I created a detail account dimension without creating a summary account dimension first. When I attempt to create a summary account dimension now, I get an error message indicating the member already exists. I tried to delete the detailed dimension and start over but there is already data saved. How can I correct this?
Validation Errors mapping to placeholder
Hey Folks, I am looking to map all validation errors that might occur during an automated load to a placeholder member in the UD1 dimension, but i am running into issues as the mask rule approach is not working. Does anyone else have any other way to make this work? Below is what i have tried but i still get kickouts in the validation step of the load process.
Cannot access the file because it is being used by another process
I'm trying to export data via a Data Management step. I am running into frequent errors stating: Error processing Data Management Step '[DM STEP NAME]'. Unable to create or open file '[FILE PATH]'. The process cannot access the file '[FILE PATH]' because it is being used by another process. My servers were unoccupied as no tasks were running in the background in the task activity log. I've also tried via DM sequence and selecting my own server which did not help.
Scenario security to prevent data load for Actuals via XFSet
Is it possible to place a restriction on a scenario member to prevent data write via XFSet? This would prevent data load via XFSet for Actuals (so the workflow can't be bypassed), however would allow data send via XFSet for budget / forecast scenarios. Would appreciate any input if other users have dealt with this issue in the past.
