Do you have any question about this error?
Message type: E = Error
Message class: F0 - FI batch program messages
Message number: 170
Message text: Payee company code not in table T001
Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.
To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.
Unfortunately, there isn't any extra information in this error notice.
First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).
Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.
You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.
The SAP error message F0170, which states "Payee company code not in table T001," typically occurs when a transaction involves a company code that is not recognized in the system. The T001 table in SAP contains the list of all company codes defined in the system, and if the company code for the payee is not present in this table, the error will be triggered.
Cause:
- Missing Company Code: The payee's company code has not been created or is not active in the T001 table.
- Incorrect Configuration: The company code may have been incorrectly entered in the transaction or configuration settings.
- Data Migration Issues: If data was migrated from another system, the company code may not have been included or properly configured.
- Inactive Company Code: The company code exists but is marked as inactive.
Solution:
Check Company Code in T001:
- Go to transaction code SE16 or SE16N.
- Enter the table name T001 and execute.
- Check if the payee's company code is listed. If it is not, you will need to create it.
Create or Activate Company Code:
- If the company code is missing, you can create it using transaction code OX15 (or SPRO -> Enterprise Structure -> Definition -> Financial Accounting -> Define Company Code).
- If the company code exists but is inactive, you may need to activate it.
Verify Transaction Data:
- Ensure that the transaction you are processing has the correct payee company code entered. Double-check for any typos or incorrect entries.
Consult with SAP Basis or Functional Team:
- If you are unsure about creating or modifying company codes, consult with your SAP Basis or functional team to ensure compliance with your organization’s policies.
Check Authorization:
- Ensure that you have the necessary authorizations to view or modify company codes in the system.
Related Information:
By following these steps, you should be able to resolve the F0170 error and ensure that the payee company code is correctly configured in your SAP system.
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 | ![]() |
![]() |
F0169 Run date may not be in the past
Self-Explanatory Message Since SAP believes that this specific error message is ...
F0168 System date is new run date
Self-Explanatory Message Since SAP believes that this specific error message is ...
F0171 Error when reading the company code address & (table SADR)
Self-Explanatory Message Since SAP believes that this specific error message is ...
F0172 Only values TLX, CDC, CDD, CHC, CHD, CHC, MAN, EUR or Z* are permitted
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.