Message type: E = Error
Message class: MN - Message class for subsequent settlement (Purchasing)
Message number: 659
Message text: Document &1 is not a supplier billing document
An internal error occurred. Document &V1& for arrangement &V2& is not a
document for supplier billing.
This document is not processed. The system starts processing the next
document.
Contact your system administration.
This is probably due to a system error or a problem on the database.
Therefore, contact SAP.
Error message extract from SAP system. Copyright SAP SE.
MN659
- Document &1 is not a supplier billing document ?The SAP error message MN659, which states "Document &1 is not a supplier billing document," typically occurs when you are trying to process a document that the system does not recognize as a valid supplier billing document. This can happen in various scenarios, such as during invoice verification, payment processing, or when attempting to display or change a document. Causes: Incorrect Document Type: The document you are trying to process may not be classified as a supplier billing document in the system. Document Status: The document may be in a status that does not allow it to be processed as a supplier billing document (e.g., it may be a credit memo or a different type of document). Data Entry Error: There may have been a mistake in entering the document number or other relevant details. Document Not Created: The document may not have been created or posted correctly in the system. Authorization Issues: The user may
Get instant SAP help. Sign up for our Free Essentials Plan.
MN658
Billing document &1 relating to rebate arrangement &2 does not exist
What causes this issue? The data for billing document &V1&, which belongs to arrangement &V2&, could not be found in the system.Syste...
MN657
Accounting document &1 could not be found
What causes this issue? The data for accounting document &V1&, that belongs to arrangement &V4&, for company code &V2& in fis...
MN660
Document index contains invalid data records (internal error)
What causes this issue? largely identical to MN328!!! When settlement documents were imported to determine business volume data for arrangement &...
MN661
Settlement document missing
What causes this issue? The data for arrangement &V1& for settlement document &V2& (company code &V3&, fiscal year &V4&am...
Click on this link to search all SAP messages.