A client with a 5-5 G/L Account Structure (2 segments with 5 digits each) recently upgraded to 2015 SQL from 4.30 Advanced. They have tons of VI import job that were converted. Among these are A/P Manual Check Entry and A/R Cash Receipts jobs both of which have G/L Distributions. They tested the imports in 2015 and it fails only on some G/L dist records and specifically with ""The G/L Account is required"". Upon closer look at source file, only the lines with a full 10-digit account number are failing. However these are all valid as seen in GL_Account table. Now where it passes, the Account Number happens to be same as the Account Key. So it appears the import is expecting the Account Key not the Account Number but they tell me it worked just fine in 4.30.
So is it supposed to work this way in 2015 where it's expecting the Account Key not the Account Number? I can write Perform Logic to lookup the Account Key from the Number but I'd rather approach this procedurally if there is a way.