Forum Discussion
Think the first question is, is your process running any SQL queries?
It is a bit hard to diagnose something like this without more information. If it isn't your SQL then it sounds like its gonna be tricky. If if you are running SQL queries then narrow it down and feel free to share the SQL.
When you define a column numeric or decimal in an SQL Server database you specify the scale and precision (doc). If you try to store a number that doesn't fit in these bounds then it generates this error, e.g. decimal(8,2) has a max value of 999999.99
Thanks Daniel, my sequence isn't running any SQL. Its just the error number that gives a message hinting it maybe an issue with SQL in backend tables. I'm simply using the standard "Copy Data" functionality in OS Data Management using member filters below. It seems to be working for periods prior to M7 as well...
Related Content
- 12 months ago