Message type: E = Error
Message class: MN - Message class for subsequent settlement (Purchasing)
Message number: 380
Message text: Bus. vol. update for purchasing document &, item & incomplete (PO hist.)
Translation: Largely identical to MN 587
The update data created for purchasing document &V1&, item &V2&, for
rebate arrangement &V3& was re-checked for completeness, In the
process, it was discovered that a data record was missing.
Possible causes:
Previous error message
The update is not executed, but must have been carried out for the
purposes of recompilation
The purchase order history is incomplete (dataset missing).
The purchase order history has already been aggregated, for example.
Internal error in function 'Recompilation of business volume data'
Data is not updated.
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. Find the update transaction, and note the messages.
Check whether a purchase order history exists:
Do further messages exist?
If a purchase order history already exists, then there is an internal
program error in
If there is no purchase order history, you must recreate the missing
datasets, i.e. the purchase order history.
You may then have run the program again once you have corrected the
error.
If necessary, contact your system administrator.
The condition record belonging to rebate arrangement &V3& has the
(internal) number &V4&.
Error message extract from SAP system. Copyright SAP SE.
MN380
- Bus. vol. update for purchasing document &, item & incomplete (PO hist.) ?The SAP error message MN380 indicates that there is an issue with the business volume update for a purchasing document and item, specifically that the update is incomplete for the purchase order history. This error typically arises during the processing of purchasing documents, such as when trying to post goods receipts or invoice receipts.
Cause: The error can be caused by several factors, including: Incomplete Data: The purchasing document or item may have missing or incomplete data that is required for the business volume update.
Configuration Issues: There may be configuration issues in the system related to the purchasing document types or the business volume update settings. Document Status: The purchasing document may be in a status that does not allow for updates, such as being blocked or not fully processed. Custom Code or Enhancements: If there are custom developments or enhancements in the system, they may interfere with the standard processing of purchasing documents.
Solution: To resolve
Get instant SAP help. Sign up for our Free Essentials Plan.
MN379
No price determination carried out for purchasing document &, item &
What causes this issue? The system needs the price determination data for purchasing document &V1& in order to perform the function you reque...
MN378
No document data earmarked for subsequent compilation of statistics
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
MN381
No update data exists for condition record
What causes this issue? No update data (business volume data) exists or has been created for the condition record of rebate arrangement &V2&....
MN382
Settlement data (rebate income) inconsistent (internal error)
What causes this issue? The settlement data for a condition record belonging to rebate arrangement &V1& is inconsistent. There is a discrepan...
Click on this link to search all SAP messages.