Do you have any question about this error?
Message type: E = Error
Message class: MN - Message class for subsequent settlement (Purchasing)
Message number: 670
Message text: Document &1 is a settlement document (no business volume update)
Document &V1& (Settlement Management) is a settlement document in
<DS:GLOS.3526C095AFAB52B9E10000009B38F974>subsequent settlement</> for
arrangement &V2&.
It is not possible to update business volume data from settlement
documents.
Please look into this matter.
This situation is usually caused by a program error. Therefore, contact
your system administrator.
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.
MN670
- Document &1 is a settlement document (no business volume update) ?The SAP error message MN670 indicates that the document you are trying to process is a settlement document, which means it is not eligible for a business volume update. This typically occurs in the context of settlement processes in SAP, particularly in modules like SAP Controlling (CO) or Asset Accounting (FI-AA).
Cause:
- Settlement Document: The document in question is a settlement document, which is used to settle costs from one cost object to another. Settlement documents do not have a business volume associated with them, hence they cannot be updated in the same way as regular business transactions.
- Incorrect Transaction: You may be trying to perform a transaction that is not applicable to settlement documents, such as trying to post a business volume update or make changes that are not allowed for settled items.
- Configuration Issues: There may be configuration settings in your SAP system that are not aligned with the expected behavior for settlement documents.
Solution:
- Review the Document: Check the document number referenced in the error message to confirm that it is indeed a settlement document. You can do this by using transaction codes like KSB1 (for cost centers) or S_ALR_87013611 (for settlement documents).
- Use Appropriate Transactions: Ensure that you are using the correct transaction codes for the actions you want to perform. If you need to update or analyze business volumes, make sure you are working with the correct type of document.
- Consult Documentation: Refer to SAP documentation or help files for guidance on how to handle settlement documents and what actions are permissible.
- Configuration Check: If you suspect a configuration issue, consult with your SAP Basis or CO consultant to review the settings related to settlement documents and business volume updates.
Related Information:
If the issue persists after following these steps, it may be beneficial to reach out to your SAP support team for further assistance.
Get instant SAP help. Start your 7-day free trial now.
MN669
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...
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...
MN671
Cancel settlement document &2 (company code &3, fiscal year &4)
What causes this issue? In the same settlement run &V1&, at least one other settlement document for the arrangement was cancelled. However, i...
MN672
No document categories transferred (function module &1)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.