Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now

Close

How To Fix WS062 - No journal entry created for document &


SAP Error Message - Details

  • Message type: E = Error

  • Message class: WS - Supplier Billing Document

  • Message number: 062

  • Message text: No journal entry created for document &

  • Show details Hide details


  • Self-Explanatory Message

    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.



    What else can you do?

    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.


Smart SAP Assistant

  • What is the cause and solution for SAP error message WS062 - No journal entry created for document & ?

    SAP Error Message:
    WS062 - No journal entry created for document &


    Cause:

    This error occurs when SAP attempts to post a document but fails to create the corresponding journal entry in the financial accounting (FI) module. The system processes the document but, due to certain conditions or configuration issues, the journal entry is not generated.

    Common causes include:

    • Missing or incorrect account assignment: The document line items may lack proper G/L account assignments or cost center assignments.
    • Posting period issues: The posting date might be in a closed or blocked posting period.
    • Document type or posting key configuration: The document type or posting key may not be configured to create FI documents.
    • Integration issues: Problems in the integration between the sub-ledger (e.g., MM, SD) and FI.
    • User exit or BAdI logic: Custom code might be preventing the creation of the journal entry.
    • Authorization issues: The user may lack authorization to post FI documents.
    • Technical errors: Database or system errors during posting.

    Solution:

    To resolve the WS062 error, follow these steps:

    1. Check Document Details:

      • Verify that all line items have valid and complete account assignments.
      • Ensure that the G/L accounts are open and valid for posting.
    2. Verify Posting Period:

      • Check if the posting date falls within an open posting period in transaction OB52.
      • If the period is closed, open it or change the posting date.
    3. Review Document Type and Posting Key Configuration:

      • Use transaction OBA7 to check document type settings.
      • Ensure the document type allows FI postings.
      • Check posting keys in OB41 for correct configuration.
    4. Check Integration Settings:

      • For MM or SD documents, verify the integration settings with FI.
      • Ensure that the relevant account determination is correctly maintained.
    5. Analyze Custom Code:

      • Review any user exits, BADIs, or enhancements that might affect posting.
      • Debug the posting process to identify if custom logic is causing the issue.
    6. Check Authorizations:

      • Verify that the user has the necessary authorizations to post FI documents.
    7. Review System Logs and Dumps:

      • Check transaction SM21 (system log) and ST22 (short dumps) for related errors.
      • Look for database or system errors during posting.
    8. Repost or Correct Document:

      • If possible, correct the document and repost.
      • Use transaction FBRA to reset the cleared status if relevant.

    Related Information:

    • Transaction Codes:

      • FB03 - Display Document
      • OB52 - Maintain Posting Periods
      • OBA7 - Document Types
      • OB41 - Posting Keys
      • SM21 - System Log
      • ST22 - Dump Analysis
    • Notes and SAP Help:

      • Check SAP Notes related to WS062 for specific patches or known issues.
      • SAP Help Portal for FI document posting and integration.
    • Common Scenarios:

      • Posting MM invoice without proper account assignment.
      • SD billing document not generating FI document due to missing configuration.
      • Custom enhancements blocking FI document creation.

    Summary:
    The WS062 error indicates that SAP did not create a journal entry for a document due to configuration, authorization, or integration issues. Careful review of account assignments, posting periods, document types, and custom code is necessary to identify and fix the root cause.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Sign up for our Free Essentials Plan.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
The AI Support Assistant is great. It provides comprehensive assistance even on the most difficult issues. I highly recommend this service.
Rate 1
John Jordan
SAP Consultant & Author