Do you have any question about this error?
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)
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.
The check and possible update of business volume data cannot be carried
out.
As a result, the data created may be incomplete.
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 archivedError message extract from SAP system. Copyright SAP SE.
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:
- Incorrect Document Number: The settlement document number provided may be incorrect or mistyped.
- 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.
- Document Deleted: The settlement document may have been deleted or archived, making it unavailable for retrieval.
- Authorization Issues: The user may not have the necessary authorizations to view or access the settlement document.
- Configuration Issues: There may be configuration issues in the settlement settings that prevent the document from being created or recognized.
Solutions:
- Verify Document Number: Check the settlement document number for accuracy. Ensure that it is the correct number and format.
- 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).
- Review Document Status: Use transaction codes like KOB1 or KOB2 to check if the settlement document exists or if it has been deleted.
- Authorization Check: Ensure that the user has the necessary authorizations to access the settlement document. This may involve checking user roles and permissions.
- Consult Configuration: Review the configuration settings related to settlements in the SAP system. Ensure that all necessary settings are correctly configured.
- 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:
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.
Get instant SAP help. Start your 7-day free trial now.
NAA069
Supplier billing document &1 does not exist in the system
What causes this issue? Supplier billing document &V1& no longer exists in the system, but is relevant for business volume updating for a con...
NAA068
Settlement document &1 does not exist in the system
What causes this issue? Settlement document &V1& no longer exists in the system, but is relevant for business volume updating for a condition...
NAA071
Supplier billing document &1 does not exist in the system (no check)
What causes this issue? For supplier billing document &V1&, the update of subsequent business volume data is to be checked for a condition re...
NAA072
Settlement document &1 is not a settlement document (internal error)
What causes this issue? Settlement document &V1& is a settlement document for arrangement &V2&. This is not allowed.System Response ...
Click on this link to search all SAP messages.