Outgoing Payment Error (No matching records found 'G/L Accounts' (OACT) (ODBC -2028) [Message 131-183])

[former_member629222]

Hello,

Were encountering "No matching records found  'G/L Accounts' (OACT) (ODBC -2028)  [Message 131-183]" on Outgoing Payment, what seems to be the cause of this error, because the all the GL Accounts involves is all active, and when I change the posting date to Feb 1, 2012 the transaction is added, but when I used the actual date which is Jan 31, 2012, I encountered that error.

I do appreciate your help.

Regards,

Ellie

[former_member186095 · Accepted solution]

Hi,

Checked if you have defined exchange rate gain or loss account in G/L account determination --> tab  general.

if not, the error message will appear. So, to solve this problem is just set the exchange rate gain or loss account in G/L account determination --> tab  general.

Rgds,

[former_member629222 · Accepted solution]

Sir Jimmy,

We have defined the GL Determination on Exchange Rate Gain And Loss, this there any other setup need to check beside it.

Regards,

Ellie

[former_member186095 · Accepted solution]

Miss Ellie,

What about rounding account, have you set it in the G/L acct determination. Please set it too.

Check SAP note 874131 - "No matching record found 'G/L Accounts' (OACT) [ODBC 2028]".

The solution said that there must be rounding account defined in G/L acct determination before add the document.

Rgds,

[former_member629222 · Accepted solution]

Sir Jimmy,

The problem is already solve thank you for your help.

Very much appreciate,

Ellie

[former_member186095 · Accepted solution]

Miss Ellie,

You are welcome. Nice to hear the problem has solved.

Rgds,

JimM

[former_member186095]

Hi,

You must also check if the account code is inactive in the january 2012 period. If it is inactive, you must untict the inactive field.

Rgds,

[former_member629222]

Sir,

I already check all the GL account involves and the posting period, we have 2 databases, test and live, the prob is, in test db the scenario is working fine, but in live db that error arise, i check all the setup and find to discrepancies.

Regards,

Ellie