Do you have any question about this error?
Message type: E = Error
Message class: EK - IS-U Accounts Receivable and Payable
Message number: 310
Message text: Charges from category &, amount & & have been posted
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.
EK310
- Charges from category &, amount & & have been posted ?The SAP error message EK310 indicates that there are charges from a specific category and amount that have already been posted in the system. This error typically arises in the context of procurement and invoice verification processes, particularly when dealing with purchase orders, invoices, or goods receipts.
Cause:
- Duplicate Posting: The most common cause of this error is an attempt to post an invoice or a charge that has already been recorded in the system.
- Incorrect Invoice Verification: If the invoice verification process is not correctly aligned with the purchase order or if there are discrepancies in the amounts, this error can occur.
- Configuration Issues: There may be issues with the configuration of the account assignment or the charge categories in the system.
- Data Entry Errors: Manual entry errors can lead to attempts to post charges that have already been processed.
Solution:
- Check for Duplicate Entries: Review the relevant purchase orders and invoices to ensure that the charges have not already been posted. You can do this by checking the document flow in the purchase order or invoice.
- Correct Invoice Amounts: If there are discrepancies in the amounts, ensure that the invoice amounts match the purchase order amounts. Adjust the invoice if necessary.
- Review Configuration: If the issue persists, check the configuration settings related to account assignments and charge categories to ensure they are set up correctly.
- Consult with Finance/Accounting: If you are unsure about the postings, consult with your finance or accounting team to verify the correct amounts and postings.
- Use Transaction Codes: Utilize transaction codes like ME23N (Display Purchase Order) or MIRO (Invoice Verification) to investigate the details of the postings.
Related Information:
If the problem persists after following these steps, it may be necessary to escalate the issue to your SAP support team or consult with an SAP expert for further assistance.
Get instant SAP help. Start your 7-day free trial now.
EK309
Posting charges to business partner & is not possible
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
EK308
Workflow could not be generated for disconnection document &
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
EK311
No document type or main/subtransaction defined for charge category &
What causes this issue? The charges determined in the dunning run could not be posted automatically. Possibly, the The system issues an error message...
EK312
Disconnection document & for contract account & already exists
What causes this issue? During a dunning run, a dunning level was reached at which a disconnection document is created. The disconnection document &a...
Click on this link to search all SAP messages.