How To Fix NAA070 - Settlement document &1 does not exist in the system (no check)


SAP Error Message - Details

  • Message type: E = Error

  • Message class: NAA - Subsequent settlement (Purchasing)

  • Message number: 070

  • Message text: Settlement document &1 does not exist in the system (no check)

  • Show details Hide details
  • What causes this issue?

    The update of subsequent business volume data for a condition record of
    arrangement &V2& is to be checked for settlement document &V1&.
    The settlement document may be relevant here, but the document no longer
    exists in the system.

    System Response

    The check and possible update of business volume data cannot be carried
    out.
    As a result, the data created may be incomplete.

    How to fix this error?

    Check the business volume data for arrangement &V2&.
    If necessary, contact your system administrator.
    Possible causes:

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

    The document has already been archived
    Hardware or software error
    Internal program error (document not imported to internal buffer)
    The condition record concerned has (internal) number &V3&.

    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message NAA070 - Settlement document &1 does not exist in the system (no check) ?

    The SAP error message NAA070, which states "Settlement document &1 does not exist in the system (no check)," typically occurs in the context of settlement processing in SAP, particularly when dealing with internal orders, projects, or other cost objects. This error indicates that the system is unable to find the specified settlement document, which can be due to several reasons.

    Causes:

    1. Incorrect Document Number: The settlement document number provided may be incorrect or mistyped.
    2. Document Not Created: The settlement document may not have been created yet. This can happen if the settlement process has not been executed or if there were issues during the settlement run.
    3. Document Deleted: The settlement document may have been deleted or archived, making it unavailable for retrieval.
    4. Authorization Issues: The user may not have the necessary authorizations to view or access the settlement document.
    5. Configuration Issues: There may be configuration issues in the settlement settings that prevent the document from being created or recognized.

    Solutions:

    1. Verify Document Number: Check the settlement document number for accuracy. Ensure that it is the correct number and format.
    2. Check Settlement Process: Ensure that the settlement process has been executed for the relevant cost object. If not, run the settlement transaction (e.g., KO88 for internal orders).
    3. Review Document Status: Use transaction codes like KOB1 or KOB2 to check if the settlement document exists or if it has been deleted.
    4. Authorization Check: Ensure that the user has the necessary authorizations to access the settlement document. This may involve checking user roles and permissions.
    5. Consult Configuration: Review the configuration settings related to settlements in the SAP system. Ensure that all necessary settings are correctly configured.
    6. Check for Archiving: If the document has been archived, consult with your SAP Basis team to see if it can be retrieved or if the archiving settings need to be adjusted.

    Related Information:

    • Transaction Codes: Familiarize yourself with relevant transaction codes such as KO88 (Settlement of Internal Orders), KOB1 (Order Document Overview), and KOB2 (Order Document List).
    • SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions to common problems.
    • Documentation: Review SAP documentation related to settlement processes for internal orders or projects to ensure compliance with best practices.

    If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP support team or reach out to SAP support for further assistance.

    • 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 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