Do you have any question about this error?
Message type: E = Error
Message class: FR - Messages for FI Reporting
Message number: 159
Message text: Account & is not defined for bill liability in comp.code &
In the payment program configuration, account &V1& has not been entered
as the bank sub-account for a payment by bill of exchange.
The account number is rejected.
Enter the correct account number.
Error message extract from SAP system. Copyright SAP SE.
The SAP error message FR159 indicates that a specific account is not defined for bill liability in the specified company code. This error typically arises in the context of financial transactions, particularly when dealing with billing or invoicing processes in SAP.
Cause:
- Missing Configuration: The account specified in the error message has not been set up in the system for the relevant company code.
- Incorrect Account Assignment: The account may be incorrectly assigned or not assigned at all in the configuration settings for billing.
- Company Code Issues: The company code specified may not have the necessary settings or configurations for the account in question.
- Master Data Issues: The master data for the customer or vendor may not be correctly configured, leading to this error.
Solution:
Check Account Configuration:
- Go to the configuration settings in SAP (Transaction Code: SPRO).
- Navigate to Financial Accounting (FI) > Accounts Receivable and Accounts Payable > Business Transactions > Incoming Invoices > Define Account for Bill Liability.
- Ensure that the account in question is defined for the relevant company code.
Define the Account:
- If the account is not defined, you will need to create it. Make sure to specify the correct account type and ensure it is linked to the appropriate company code.
Review Master Data:
- Check the master data for the customer or vendor involved in the transaction. Ensure that the account assignments are correct and that the necessary accounts are linked.
Test the Configuration:
- After making changes, perform a test transaction to ensure that the error no longer occurs.
Consult Documentation:
- Refer to SAP documentation or help resources for additional guidance on configuring accounts for bill liability.
Related Information:
Transaction Codes: Familiarize yourself with relevant transaction codes such as:
SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
User Roles and Authorizations: Ensure that the user has the necessary authorizations to make changes to account configurations.
Testing Environment: If possible, make changes in a testing environment before applying them to the production system to avoid disruptions.
By following these steps, you should be able to resolve the FR159 error and ensure that the account is properly defined for bill liability in the specified company code.
Get instant SAP help. Start your 7-day free trial now.
Feature | Free Access | Free Trial |
---|---|---|
Basic SAP error explanation | ![]() |
![]() |
Step-by-Step Usage Guide | ![]() |
![]() |
Interactive SAP Coach Assistance | ![]() |
![]() |
AI Troubleshooting for T-Code Errors | ![]() |
![]() |
FR158 0 is an invalid entry
What causes this issue? The calculation of the dunning level can only be carrie...
FR157 Last dunning date is later than the current dunning date
What causes this issue? Last dunning date lies after the current dunning date. ...
FR160 Select documents
Self-Explanatory Message Since SAP believes that this specific error message is ...
FR161 No clearing account has been created for account &
Self-Explanatory Message Since SAP believes that this specific error message is ...
SAP messages fall into 3 different categories: Error messages
(message type = E), Warnings (W) or Informational (I) messages.
An error message will prevent you from continuing your work - it is a hard stop and you need to fix the error before you can proceed. A warning message will stop your work, however, you can then bypass the warning by pressing the Enter key on your keyboard. That said, it is still good practice to investigate the cause of the warning message and address it. An information message will not stop your work and is truly just for informational purposes.
Click on this link to search all SAP messages.