Do you have any question about this error?
Message type: E = Error
Message class: MN - Message class for subsequent settlement (Purchasing)
Message number: 587
Message text: Bus. vol. update for purchasing document &, item & incomplete (dlv sched)
Translation: Largely identical to MN 380
The business volume data created for purchasing document &V1&, item
&V2& for arrangement &V3& was checked for completeness. The system
found that a dataset is missing.
Possible causes:
Internal error in function 'Recompilation of business volume data' Data
is not updated.
The schedule line is incomplete (dataset missing).
The function is performed, but the business volume data created is
probably incomplete.
Look into the matter. The analysis function (see pushbutton) may help
you here.
Determine the update transaction and read the messages.
If a schedule line exists, then there is an internal program error in
the function 'Recompilation of business volume data'.
If there is no schedule line, you must recreate the missing datasets,
i.e. the schedule line.
You may then have run the program again once you have corrected the
error.
If necessary, contact your system administrator.
The condition record for arrangement &V3& has (internal) number &V4&.
Error message extract from SAP system. Copyright SAP SE.
MN587
- Bus. vol. update for purchasing document &, item & incomplete (dlv sched) ?The SAP error message MN587 indicates that there is an issue with the business volume update for a purchasing document and item, specifically related to delivery schedules. This error typically arises when the system is unable to update the business volume due to incomplete or missing data.
Cause:
- Incomplete Delivery Schedule: The delivery schedule for the purchasing document may not be fully defined or may have missing entries.
- Missing Data: Required fields or data related to the purchasing document or item may be incomplete or incorrectly entered.
- Configuration Issues: There may be configuration issues in the system that prevent the update from being processed correctly.
- Document Status: The purchasing document may be in a status that does not allow for updates (e.g., blocked or not fully processed).
- Authorization Issues: The user may not have the necessary authorizations to perform the update.
Solution:
- Check Delivery Schedule: Review the delivery schedule for the purchasing document and ensure that all necessary entries are complete and correct.
- Verify Data Completeness: Ensure that all required fields in the purchasing document are filled out correctly. This includes checking for any missing information in the item details.
- Review Document Status: Check the status of the purchasing document to ensure it is not blocked or in a state that prevents updates.
- Configuration Review: If you suspect a configuration issue, consult with your SAP Basis or configuration team to ensure that the settings for business volume updates are correct.
- Authorization Check: Ensure that the user attempting to perform the update has the necessary authorizations to do so.
- Transaction Logs: Check transaction logs for any additional error messages or warnings that may provide more context on the issue.
Related Information:
If the issue persists after following these steps, 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.
MN586
No message relating to analysis function issued (internal error)
What causes this issue? There is no message relating to the analysis of the (retrospective) updating of supplier business volumes with respect to sch...
MN585
To date of condition record incompatible with period conditions
What causes this issue? The "To" date &V2& of the main condition record is earlier than the "From" date &V1& of t...
MN588
Items of documents belonging to category & cannot be processed
What causes this issue? This function is only intended for documents belonging to the category (document for which updating is carried out): The syst...
MN589
Index entry missing for document &, item &
What causes this issue? Document &V1&, item &V2&, is relevant to subsequent (end-of-period rebate) settlement with respect to a condi...
Click on this link to search all SAP messages.