Message type: E = Error
Message class: ME - Purchasing: General Messages
Message number: 520
Message text: No comparison possible
Either no releases of the relevant type have yet been generated against
this scheduling agreement, or releases have been generated but not yet
transmitted to the component supplier.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Check the delivery schedule release documentation to see whether
releases have been generated and transmitted:
<DS:TRAN.ME39>Display scheduling agreement delivery schedule</>
Error message extract from SAP system. Copyright SAP SE.
ME520
- No comparison possible ?The SAP error message ME520 "No comparison possible" typically occurs in the context of purchasing documents, particularly when trying to compare purchase orders with other documents like contracts or scheduling agreements. This error can arise due to various reasons, and understanding the cause is essential for finding a solution. Causes: Missing or Inconsistent Data: The purchasing documents may not have the necessary data for comparison, such as missing conditions, pricing, or item details. Document Type Issues: The document types involved in the comparison may not be compatible or may not allow for comparison. Status of Documents: One or more of the documents may be in a status that does not allow for comparison (e.g., a document is not yet released). Different Item Categories: The items being compared may belong to different categories that do not allow for comparison.
Configuration Issues: There may be configuration settings in the SAP system that prevent the comparison from being made. Solutions: Check
Get instant SAP help. Sign up for our Free Essentials Plan.
ME519
Requisition not subject any release strategy following changes
What causes this issue? The purchase requisition was subject to a <DS:GLOS.release_strategy>release strategy</>. The requisition was chan...
ME518
In the case of items with account assignment, please enter a plant
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
ME521
Session &: 1st transaction does not begin with a header record (type 1)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
ME522
Transaction & record &: data record not marked with record type 2
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.