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

Close

How To Fix VG120 - Intermediate document does not exist.


SAP Error Message - Details

  • Message type: E = Error

  • Message class: VG - EDI Messages in SD

  • Message number: 120

  • Message text: Intermediate document does not exist.

  • Show details Hide details
  • What causes this issue?

    Internal error during processing of
    <GL:EDI>EDI</>-intermediate document
    <GL:Intermediate_Document>(intermediate document)</>.

    How to fix this error?

    INCLUDE 'NA_SYSAD1' OBJECT DOKU ID TX LANGUAGE E

    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message VG120 - Intermediate document does not exist. ?

    SAP Error Message:
    VG120 - Intermediate document does not exist


    Cause:

    The error message VG120 typically occurs in the context of IDoc (Intermediate Document) processing in SAP. It indicates that the system is trying to process or reference an IDoc that does not exist in the database. This can happen due to several reasons:

    • The IDoc number specified does not exist or was deleted.
    • The IDoc was never created or was not successfully generated.
    • There is a mismatch or incorrect IDoc number being passed to a function or program.
    • The IDoc has been archived or is not available in the current system.
    • The IDoc status is not appropriate for the operation being performed (e.g., trying to reprocess an IDoc that is not in a releasable status).

    When does this error occur?

    • During IDoc inbound or outbound processing.
    • When trying to display or reprocess an IDoc.
    • When a program or function module tries to fetch an IDoc by number but it is not found.
    • During ALE (Application Link Enabling) or EDI (Electronic Data Interchange) processing.

    Solution:

    1. Verify the IDoc Number:

      • Check if the IDoc number you are referencing is correct.
      • Use transaction WE02 or WE05 to search for the IDoc number.
      • If the IDoc does not exist, confirm the source system or process that should have created it.
    2. Check IDoc Status:

      • If the IDoc exists, verify its status.
      • Some operations require the IDoc to be in a specific status (e.g., status 30 - ready for dispatch).
      • Use transaction WE02 or WE05 to check the status.
    3. Recreate or Reprocess the IDoc:

      • If the IDoc was deleted or never created, regenerate the IDoc from the source application.
      • If the IDoc is in error status, try reprocessing it using transaction BD87.
    4. Check ALE/EDI Configuration:

      • Ensure that the partner profiles and message types are correctly configured.
      • Verify that the IDoc generation and processing settings are correct.
    5. Check for Archiving:

      • If the IDoc was archived, it will not be available in the active database.
      • Use transaction SARA to check archiving objects related to IDocs (e.g., IDOCS).
      • Retrieve the IDoc from archive if necessary.
    6. Debugging:

      • If the error occurs during a custom program or function module, debug to check why the IDoc number is not found.
      • Check the logic that fetches or references the IDoc.

    Related Information:

    • Transactions:
      • WE02 / WE05 - Display IDocs
      • BD87 - Reprocess IDocs
      • WE19 - Test tool for IDocs
      • SARA - Archive Administration
    • Tables:
      • EDIDC - Control record of IDoc
      • EDID4 - Data records of IDoc
    • Notes and Documentation:
      • SAP OSS Notes related to IDoc processing errors.
      • ALE and EDI configuration guides.
    • Common IDoc Status Codes:
      • 01 - IDoc created
      • 30 - IDoc ready for dispatch
      • 03 - Data passed to port OK
      • 51 - Error during processing

    Summary:

    The VG120 - Intermediate document does not exist error means the system cannot find the IDoc it is supposed to process. The main steps to resolve this are to verify the IDoc number, check its existence and status, ensure proper configuration, and reprocess or regenerate the IDoc if necessary. Use standard SAP transactions like WE02, WE05, and BD87 to manage and troubleshoot IDocs.


    If you provide more context (e.g., transaction, program, or scenario where the error occurs), I can give more specific guidance.

    • 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's SAP support assistant is amazing. Saves me countless hours trying to solve complex SAP issues myself. It's a real game changer!
Rate 1
Thomas Michael
SAP Consultant, Author & Speaker