I was giving one of our guys a hand last week with a client that kept getting an error message when trying to create a GL code.
The error the user was getting was as follows:
This record has been created since your attempt to create it.
I checked GL00100 and GL00105 by running the following script
SELECT ACTINDX FROM GL00105
SELECT ACTINDX FROM GL00100
This returned one value, I ran a select for the ACTINDX that showed and this was indeed for the code that the user was trying to create. Removing the information from this table should have resolved the problem. We did this and tried to then create the GL code again – but again, we got the error message.
Sure enough, the GL code was in GL00105 and not GL00100.
I decided that I would run Check Links on Account Master. During this process we got two errors:
It seemed to me that Check Links had found an issue and that the GL code did not exist in the table frl_acct_code and while trying to add the information back in using the ‘glCLAccountMSTR’ stored procedure, it encountered a primary key violation error which means that the information it was trying to insert was already there.
I had a look at the table frl_acct_code in the GP company database and sure enough the information was there. I removed it and removed the line from GL00105 again and attempted to create the GL code again.
Following up with some research on frl_acct_code, it looks like this table is from when the client used to run FRx – it’s added as a part of running FRx’s ‘Server Based Index’ script which is on the FRx 6.7 media.
The client is now on 2015 R2 with Management Reporter so I don’t believe this table should be in use anymore. They’re shortly moving to 2016 so this is maybe something we need to look into at the point of doing an upgrade in their staging environment.
Let me know if you’ve had any similar experiences!