Message type: E = Error
Message class: MN - Message class for subsequent settlement (Purchasing)
Message number: 666
Message text: Status &2 of settlement document &1 does not allow updating
Business volume data in
<DS:GLOS.3526C095AFAB52B9E10000009B38F974>subsequent settlement</> is
only updated from a settlement document when this document is released
to Accounting.
An update can also be triggered by the release of a supplier settlement
list containing the individual document.
The accounting status &V2& (&V3&) of document &V1& indicates that the
document update is not yet due.
Subsequent updating cannot be performed in this program run.
Please look into this matter.
Release document &V1& or the supplier settlement list to Accounting, if
necessary, or correct any errors that are preventing the document from
being released. The business volumes are then updated in the next
program run.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
MN666
- Status &2 of settlement document &1 does not allow updating ?The SAP error message MN666 indicates that there is an issue with the status of a settlement document in the SAP system. Specifically, the message states that the status of the settlement document does not allow for updates. This can occur in various scenarios, particularly in the context of project systems, internal orders, or other financial documents that have specific statuses that restrict changes.
Cause: The error can be caused by several factors, including: Document Status: The settlement document may be in a status that prohibits updates. For example, if the document is already settled or has been marked as complete, it may not allow further changes. Authorization Issues: The user may not have the necessary authorizations to make changes to the settlement document. System Configuration: Certain configurations in the SAP system may restrict updates based on business rules or settings. Document Locking: The document may be locked by another process or user, preventing updates.
Solution: To resolve
Get instant SAP help. Sign up for our Free Essentials Plan.
MN665
Reversal document for document &V1& could not be determined
What causes this issue? The system could not determine which of the two documents &V1& and &V2& (company code &V3& in fiscal ...
MN664
Arrangement or condition record number is missing in LIS structure &1
What causes this issue? You tried to delete statistical data for an arrangement from LIS structure &V1&, even though neither key figure "...
MN667
Status &2 of document &1 is not permitted (no updating)
What causes this issue? Business volume data in <DS:GLOS.3526C095AFAB52B9E10000009B38F974>subsequent settlement</> from Settlement Manage...
MN668
Supplier billing document type &1 is not relevant for subsequent settl.
What causes this issue? Business volume data in <DS:GLOS.3526C095AFAB52B9E10000009B38F974>subsequent settlement</> from Settlement Manage...
Click on this link to search all SAP messages.