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

Close

How To Fix VG860 - Unknown error closing intermediate document


SAP Error Message - Details

  • Message type: E = Error

  • Message class: VG - EDI Messages in SD

  • Message number: 860

  • Message text: Unknown error closing intermediate 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 VG860 - Unknown error closing intermediate document ?

    SAP Error Message:
    VG860 - Unknown error closing intermediate document


    Cause:

    The error VG860 typically occurs during the closing of an intermediate document in SAP Logistics Invoice Verification (LIV) or during invoice processing in Materials Management (MM). The message indicates that SAP encountered an unexpected or unknown error when trying to close or finalize an intermediate document (such as an invoice document or a related accounting document).

    Common causes include:

    • Inconsistent or incomplete data in the intermediate document or related purchase order/invoice.
    • Database inconsistencies or missing entries related to the document.
    • Authorization issues preventing the system from updating or closing the document.
    • Custom enhancements or user exits causing unexpected behavior during document closing.
    • Locking or update conflicts in the database tables during the closing process.
    • Missing or incorrect configuration in the invoice verification or document management settings.
    • Technical issues such as short dumps or system errors during the process.

    Solution:

    1. Check the Application Log and Short Dumps:

      • Use transaction SLG1 to check application logs for detailed error messages related to the document.
      • Check for any short dumps in ST22 that occurred at the time of the error for more technical details.
    2. Verify Document Consistency:

      • Check the intermediate document and related purchase order/invoice for completeness and correctness.
      • Use transaction MRBR (Release Blocked Invoices) or MRRL to check for blocked or problematic invoices.
      • Use MB03 to display material documents and verify their status.
    3. Check Authorizations:

      • Ensure the user has the necessary authorizations to close or post the document.
      • Use transaction SU53 immediately after the error to check for missing authorizations.
    4. Review Custom Code:

      • If there are any user exits, BADIs, or enhancements related to invoice verification or document closing, review them for errors or unexpected behavior.
    5. Database and Lock Checks:

      • Check for database locks or update conflicts using transaction SM12.
      • If locks exist, investigate and release if appropriate.
    6. Reprocess or Reset the Document:

      • Sometimes, reprocessing the document or resetting its status can help.
      • Use transaction MR11 (Invoice Document Reversal) or MR8M (Cancel Invoice Document) if applicable, then repost.
    7. SAP Notes and Support:

      • Search for SAP Notes related to message VG860 for known bugs or patches.
      • Example SAP Note: Check SAP OSS Notes for VG860 or related invoice verification errors.

    Related Information:

    • Transaction Codes:

      • MIRO - Enter Incoming Invoice
      • MRBR - Release Blocked Invoices
      • MRRL - Evaluated Receipt Settlement
      • MB03 - Display Material Document
      • SLG1 - Application Log
      • ST22 - ABAP Runtime Errors
      • SM12 - Lock Entries
      • MR11 - Cancel Invoice Document
      • MR8M - Cancel Invoice Document
    • Tables to Check:

      • RBKP - Invoice Document Header
      • RSEG - Invoice Document Segment
      • BKPF - Accounting Document Header
      • BSEG - Accounting Document Segment
    • Common SAP Notes:

      • Search SAP Support Portal with keywords: "VG860 Unknown error closing intermediate document"
      • Check for notes related to invoice verification errors or document closing issues.

    Summary:

    The VG860 error is a generic message indicating an unknown problem during the closing of an intermediate document in invoice verification. The resolution involves checking logs, verifying data consistency, authorizations, custom code, and system locks. If the problem persists, consult SAP Notes or open a support ticket with SAP, providing detailed logs and dump analysis.


    If you provide more context (e.g., transaction used, document numbers, system version), I can help narrow down the cause further.

    • 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
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant