Message type: E = Error
Message class: MN - Message class for subsequent settlement (Purchasing)
Message number: 379
Message text: No price determination carried out for purchasing document &, item &
The system needs the price determination data for purchasing document
&V1& in order to perform the function you requested relating to the
condition record with the internal number &V3&.
The system has recorded in a database table that purchasing document
&V1&, item &V2& is relevant to subsequent (end-of-period) rebate
settlement with regard to condition record &V3& belonging to rebate
arrangement &V4&. For this reason, pricing should have been carried
out.
However, no reference to the price determination data exists for
purchasing document &V1&.
A program error has probably occurred.
The invoice receipt relating to purchasing document &V1&, item &V2&
will not be taken into account when the function is performed (detailed
statement, compilation of statistics, etc.). The generated data is
consequently incomplete or incorrect.
Contact your R/3 system administrator.
Error message extract from SAP system. Copyright SAP SE.
MN379
- No price determination carried out for purchasing document &, item & ?The SAP error message MN379 ("No price determination carried out for purchasing document &, item &") typically occurs in the context of purchasing documents, such as purchase orders or purchase requisitions, when the system is unable to determine the price for a specific item. This can happen for several reasons, and understanding the cause is essential for resolving the issue. Causes: Missing or Incorrect Info Records: The system may not find a valid purchasing info record for the material and vendor combination. Missing Conditions: The pricing conditions (like discounts, surcharges, etc.) may not be maintained in the system for the relevant purchasing document. Material Master Data Issues: The material master may not have the necessary purchasing data set up, or it may be set to a status that prevents price determination. Vendor Master Data Issues: The vendor master data may not be correctly maintained, or the vendor may not be assigned to the relevant purchasing
Get instant SAP help. Sign up for our Free Essentials Plan.
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...
MN377
Price determ. data for purch. doc. &, item &, not available in system
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
MN380
Bus. vol. update for purchasing document &, item & incomplete (PO hist.)
What causes this issue? Translation: Largely identical to MN 587 The update data created for purchasing document &V1&, item &V2&, for...
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&....
Click on this link to search all SAP messages.