Message type: E = Error
Message class: FB - Batch Programs
Message number: 737
Message text: No G/L account entered for & & & in bank account management
You must maintain a G/L account in company code &v1& for
house bank &v2& account ID &v3& to run this program.
The system terminates processing.
In bank account management, maintain the missing G/L account.
Run the program again.
Error message extract from SAP system. Copyright SAP SE.
FB737
- No G/L account entered for & & & in bank account management ?The SAP error message FB737 "No G/L account entered for & & & in bank account management" typically occurs when there is a missing configuration for a General Ledger (G/L) account in the bank account management settings. This error can arise during various processes, such as posting transactions or managing bank accounts.
Cause: Missing G/L Account Configuration: The most common cause is that the G/L account associated with the bank account has not been defined in the system. Incorrect Bank Account Settings: The bank account may not be properly configured in the system, leading to the absence of a linked G/L account. Data Entry Errors: There may be typographical errors or incorrect entries in the bank account management settings.
Solution: To resolve the FB737 error, follow these steps: Check Bank Account Configuration: Go to the transaction code FI12 (or use the menu path: Accounting > Financial Accounting > Bank Accounting > Master Data > Bank Accounts > Change). Locate
Get instant SAP help. Sign up for our Free Essentials Plan.
FB736
Bank account management has no entry with bank key & and account &
What causes this issue? Bank account management has no entry with bank key &V1& and account number &V2&.System Response The system i...
FB735
Account number & does not match bank key &
What causes this issue? House bank account table T012K contains aan entry with account number &V2&. There is no entry in the house bank tabl...
FB738
Program termination: DTAUS file already imported; see long text
What causes this issue? This DTAUS file was already imported at an earlier stage. Since only data for a single account statement can be contained in ...
FB739
Table T049E: & &: Specify offset and length of document number
What causes this issue? Length or offset of the document number are not maintained in the ISR table (T049E).System Response The system issues an err...
Click on this link to search all SAP messages.