How To Fix RDSV_FI_XX017 - Document &1 &2 &3 exists and must not represent a gap; please check


SAP Error Message - Details

  • Message type: E = Error

  • Message class: RDSV_FI_XX - Regulatory Document and Signature Validation in FI

  • Message number: 017

  • Message text: Document &1 &2 &3 exists and must not represent a gap; please check

  • Show details Hide details
  • What causes this issue?

    You can only legally record a document number as a gap if this specific
    number is ?lost?.
    The Document exists or might exist in the near future and must not
    represent a gap in the relevant document number range.

    System Response

    The system prevents the recording when a document number exists in the
    relevant document database table and you try to enter it as ?lost?.

    How to fix this error?

    Check if the document number is really 'lost'. Check also if the
    document number is assigned to a document that has not yet been finally
    committed to the database.
    <ZU>Note</>
    The system can assign a document number to a posting but the update to
    the document database table BKPF is delayed for a longer time period
    because of technical settings; for example, during collective postings
    or immediate printing calls.

    The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

    Procedure for System Administrators


    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message RDSV_FI_XX017 - Document &1 &2 &3 exists and must not represent a gap; please check ?

    The SAP error message RDSV_FI_XX017 indicates that there is a gap in the document number range for financial documents. This typically occurs when a document number that is expected to be sequential is missing or has been skipped. The error message specifies that the document with the given identifiers (e.g., &1, &2, &3) exists, but there is a gap in the sequence that needs to be addressed.

    Cause:

    1. Missing Document Numbers: A document number that should exist in the sequence is missing. This can happen due to various reasons, such as manual deletions, errors during document posting, or issues with number range configuration.
    2. Incorrect Number Range Configuration: The number range settings for the document type may not be correctly configured, leading to gaps.
    3. Document Deletion: If documents were deleted or reversed improperly, it could create gaps in the sequence.
    4. Parallel Processing: If multiple users are posting documents simultaneously, it may lead to gaps if the system is not configured to handle concurrent postings correctly.

    Solution:

    1. Check Document Number Range:

      • Go to the transaction code SNRO (Number Range Objects) and check the number range object related to the document type in question.
      • Verify that the number range is correctly defined and that there are no gaps in the assigned range.
    2. Review Document Posting:

      • Use transaction codes like FB03 (Display Document) to check the specific documents mentioned in the error message.
      • Look for any missing documents in the sequence and investigate why they are missing.
    3. Adjust Number Range:

      • If you find that the number range is not configured correctly, you may need to adjust it. This can be done in the configuration settings for the specific document type.
      • Ensure that the number range is set to allow for the required sequence without gaps.
    4. Consult with Basis Team:

      • If the issue persists, consult with your SAP Basis team to check for any underlying system issues or inconsistencies that may be causing the problem.
    5. Repost Documents:

      • If documents were deleted or reversed, you may need to repost them to restore the sequence.
    6. Check for Custom Code:

      • If there are any custom developments or enhancements in your SAP system that handle document postings, review them to ensure they are not causing the issue.

    Related Information:

    • Transaction Codes:
      • SNRO: Number Range Objects
      • FB03: Display Document
      • OBD2: Maintain Number Ranges for Document Types
    • SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
    • Documentation: Review SAP documentation for number range management and financial document posting to ensure compliance with best practices.

    By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


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