How To Fix VG870 - DB error saving intermediate document

SAP Error Message - Details

• Message type: E = Error

• Message class: VG - EDI Messages in SD

• Message number: 870

• Message text: DB error saving intermediate document

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 VG870 - DB error saving intermediate document ?

  The SAP error message VG870: DB error saving intermediate document typically occurs during the processing of goods movements or inventory management transactions, especially when handling intermediate documents in the system.
  
  Cause
  
  
  Database issues: The error usually indicates a problem when SAP tries to save an intermediate document to the database. This can be due to:
  
  Database locks or deadlocks on the relevant tables.
  Database inconsistencies or corruption.
  Insufficient database space or resource constraints.
  Network or communication issues between the application server and the database.
  
  
  
  Authorization or configuration problems: Sometimes, missing authorizations or incorrect configuration in the movement types or document types can cause the system to fail when saving intermediate documents.
  
  
  Custom enhancements or user exits: If there are custom developments (user exits, BADIs, or enhancements) triggered during the document save process, errors in the custom code can cause the save operation to fail.
  
  
  Data inconsistencies: Invalid or inconsistent data in the document being saved (e.g., missing mandatory fields, incorrect material master data) can also cause this error.
  
  
  
  Solution
  
  
  Check system logs and dumps:
  
  Use transaction ST22 to check for any short dumps related to this error.
  Use SM21 to review system logs for database or application errors.
  
  
  
  Analyze database locks:
  
  Use transaction SM12 to check for locked entries on tables related to intermediate documents (e.g., tables like MKPF, MSEG, or custom tables if applicable).
  If locks exist, investigate and release them if safe.
  
  
  
  Check database health:
  
  Coordinate with your database administrator to check for database errors, space issues, or performance problems.
  Run database consistency checks if needed.
  
  
  
  Review authorizations:
  
  Verify that the user has the necessary authorizations to create and save intermediate documents.
  
  
  
  Check configuration:
  
  Review the movement type and document type configuration in OMJJ and related IMG nodes.
  Ensure that the intermediate document settings are correct.
  
  
  
  Debug or review custom code:
  
  If custom enhancements are involved, debug the code to identify any exceptions or errors during the save process.
  
  
  
  Retry the transaction:
  
  Sometimes, transient issues cause the error. Retrying the transaction after resolving locks or system issues may succeed.
  
  
  
  SAP Notes and Support:
  
  Search for relevant SAP Notes using the message number VG870 or keywords like "DB error saving intermediate document".
  If the problem persists, consider raising a support ticket with SAP, providing detailed logs and dumps.
  
  
  
  
  Related Information
  
  
  Message Class: VG (Inventory Management)
  
  
  Common tables involved: MKPF (Material Document Header), MSEG (Material Document Segment)
  
  
  Transactions to check:
  
  MB1A, MB1B, MB1C (Goods movements)
  MIGO (Goods movement processing)
  ST22 (Dump analysis)
  SM12 (Lock entries)
  SM21 (System log)
  
  
  
  SAP Notes: Check SAP Service Marketplace or SAP ONE Support Launchpad for notes related to VG870.
  
  
  
  If you provide more context (e.g., transaction used, exact scenario, dump details), I can help with a more targeted analysis.