Do you have any question about this error?
Message type: E = Error
Message class: FD - EDI Messages in FI
Message number: 136
Message text: Several postings created; tax may be incorrect; check session
The invoice is so large that several documents had to be created.
Since however the taxes are posted as a total, they could not be
divided up between the individual documents. This is only possible if
the amounts of the invoice line items are transferred including the
tax.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Please have a look at the last invoice in the BDC session. You can
find the tax posting here. Divide the tax amount up between the
individual partial invoices when posting the documents (the balance
of the partial invoices generally corresponds to the tax amount).
Error message extract from SAP system. Copyright SAP SE.
FD136
- Several postings created; tax may be incorrect; check session ?The SAP error message FD136 ("Several postings created; tax may be incorrect; check session") typically occurs during the processing of financial documents, particularly in the context of tax calculations and postings. This error indicates that multiple postings have been created in a session, and there is a potential issue with the tax calculations that need to be verified.
Cause:
- Multiple Postings: The error arises when the system detects that multiple postings have been created in a single session, which can lead to inconsistencies in tax calculations.
- Tax Configuration Issues: There may be issues with the tax configuration in the system, such as incorrect tax codes, rates, or settings that affect how tax is calculated.
- Document Splitting: If document splitting is enabled, it may lead to multiple line items being created, which can trigger this error if the tax amounts do not match.
- Data Entry Errors: Incorrect data entry during the posting process can also lead to discrepancies in tax calculations.
Solution:
- Check the Session: Review the session that generated the error. You can do this by going to transaction code FB03 (Display Document) or FBV3 (Display Parked Document) to check the details of the postings.
- Verify Tax Codes: Ensure that the tax codes used in the postings are correct and that the tax rates are up to date. You can check this in the transaction code OB40 (Define Tax Codes) or OBYZ (Maintain Tax Types).
- Review Configuration: Check the configuration settings for tax calculation in the system. This includes settings in SPRO (SAP Reference IMG) under Financial Accounting > Financial Accounting Global Settings > Tax on Sales/Purchases.
- Correct Data Entry: If the error is due to incorrect data entry, correct the entries and reprocess the documents.
- Consult with Tax Experts: If you are unsure about the tax implications, consult with your finance or tax department to ensure compliance with local tax regulations.
- Reprocess the Session: After making the necessary corrections, you may need to reprocess the session to ensure that the postings are correctly recorded.
Related Information:
By following these steps, you should be able to identify the cause of the FD136 error and implement the necessary solutions to resolve it.
Get instant SAP help. Start your 7-day free trial now.
FD135
Batch input session & was created
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FD134
Document & & & was posted
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FD137
Account statement created: ID: &
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FD138
Account statement posted
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.