Do you have any question about this error?
Message type: E = Error
Message class: F0 - FI batch program messages
Message number: 248
Message text: Cross-comp.code/acct accumulation: Paying/sending co.code must be unique
The extended withholding tax function is active for the company code
specified, and there are withholding tax types for which cross-company
code or cross-account accumulation is active.
In this case, paying and sending company codes must correspond for all
company codes linked by cross company code/account accumulation (i.e.
belonging to the same tax on sales/purchase group). This restriction is
necessary in order to ensure that withholding tax is processed
consistently in this special case.
Check your Customizing settings for the automatic payment program
(table T042).
Error message extract from SAP system. Copyright SAP SE.
The SAP error message F0248, which states "Cross-comp.code/acct accumulation: Paying/sending co.code must be unique," typically occurs in the context of financial transactions, particularly when dealing with cross-company code transactions in SAP. This error indicates that there is a conflict in the configuration of company codes and accounts that are being used in a transaction.
Cause:
- Duplicate Entries: The error often arises when there are duplicate entries for the combination of paying company code and sending company code in the configuration settings.
- Incorrect Configuration: The configuration for cross-company code transactions may not be set up correctly, leading to ambiguity in how transactions should be processed.
- Missing or Incorrect Master Data: The master data for the company codes or accounts involved may be incomplete or incorrectly set up.
Solution:
Check Configuration:
- Go to the configuration settings for cross-company code transactions in SAP (Transaction code: SPRO).
- Navigate to Financial Accounting (FI) > Accounts Receivable and Accounts Payable > Business Transactions > Cross-Company Code Transactions.
- Ensure that the combinations of company codes and accounts are unique and correctly configured.
Review Master Data:
- Check the master data for the company codes involved in the transaction. Ensure that they are correctly defined and that there are no duplicates.
- Verify that the accounts being used in the transaction are correctly assigned to the respective company codes.
Transaction Review:
- Review the specific transaction that triggered the error. Ensure that the paying and sending company codes are correctly specified and that they do not conflict with existing configurations.
Consult Documentation:
- Refer to SAP documentation or help resources for additional guidance on configuring cross-company code transactions.
Testing:
- After making changes, perform a test transaction to ensure that the error no longer occurs.
Related Information:
If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or a functional consultant who specializes in financial accounting within SAP.
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 | ![]() |
![]() |
F0247 No payment methods involving bank collection are defined for format &
What causes this issue? The MT100 Customer Transfer is a payment statement made...
F0246 Different settings for withholding tax are not permitted
What causes this issue? You want to process company codes which have different ...
F0249 Check run date
Self-Explanatory Message Since SAP believes that this specific error message is ...
F0250 Job scheduling terminated; read SYSLOG for details
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.