How To Fix MN355 - No update yet effected for purchasing document &1, item &2

SAP Error Message - Details

• Message type: E = Error

• Message class: MN - Message class for subsequent settlement (Purchasing)

• Message number: 355

• Message text: No update yet effected for purchasing document &1, item &2

What causes this issue?

No business volume data updated for purchasing document &V1&, item &V2&
as yet.

System Response

No business volume data was determined for this document. It is possible
that a follow-on function, required for correct business volume data for
the condition record, has not been carried out.

How to fix this error?

It is likely that no goods receipts or incoming invoices exist for
purchasing document &V1&, item &V2&.
You can establish whether or not goo ds receipts or incoming invoices
have been recorded by reference to the PO history. The list output of
the <LS>Detailed statement</> function includes a message for each
invoice receipt for which the supplementary supplier business volume
update has not taken place.
Be sure to note that the supplier business volumes relevant to rebate
settlement currently included in the statistics are incorrect. If you
now carry out (or have already carried out) settlement accounting with
for the affected condition record, the results of this process may be
incorrect. It is therefore essential that you check the results of any
settlement accounting already performed.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

You can correct the results of a faulty settlement accounting process by
repeating it (if necessary, cancel the settlement document).
If an interim settlement is involved, the relevant business volumes will
be taken into account in the next settlement.
If the rebate arrangement provides for periodic partial settlement and
provision has been made for final settlement to be effected on the basis
of the total business volume (see Customizing for the rebate arrangement
type), the difference in business volumes will be taken into account in
this final settlement.
You can allow for such a difference in business volume figures when
carrying out final settlement accounting for the rebate arrangement by
carrying out a prior business volume comparison and agreement process.
The condition record affected has the (internal) number &V4& and belongs
to rebate arrangement &V3&.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message MN355 - No update yet effected for purchasing document &1, item &2 ?

  The SAP error message MN355 "No update yet effected for purchasing document &1, item &2" typically occurs in the context of purchasing documents, such as purchase orders or purchase requisitions. This error indicates that an update to the specified purchasing document has not been successfully completed. Here are some potential causes, solutions, and related information for this error:
  Causes:
  
  Incomplete Document: The purchasing document may not be fully completed or may be in a status that does not allow updates.
  Locking Issues: The document might be locked by another user or process, preventing updates from being made.
  Authorization Issues: The user may not have the necessary authorizations to make changes to the purchasing document.
  System Errors: There could be a temporary system error or inconsistency in the database that is preventing the update.
  Background Job Failures: If the update is supposed to occur as part of a background job, that job may have failed.
  
  Solutions:
  
  Check Document Status: Verify that the purchasing document is in a status that allows updates. If it is in a blocked or completed status, you may need to change it or create a new document.
  Release Locks: If the document is locked, check with your system administrator or the user who has the document open to release the lock.
  Review Authorizations: Ensure that the user has the necessary authorizations to update the purchasing document. This may involve checking roles and permissions in the SAP system.
  Check for System Errors: Look for any system messages or logs that might indicate a broader issue with the SAP system. You can check transaction codes like SM21 (System Log) or ST22 (Dump Analysis) for errors.
  Re-run Background Jobs: If the update is part of a background job, check the job status in transaction SM37 and re-run it if necessary.
  Consult SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error message or provide patches or updates.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as ME21N (Create Purchase Order), ME22N (Change Purchase Order), and ME23N (Display Purchase Order) to manage purchasing documents.
  Debugging: If you have access to debugging tools, you can analyze the program logic to identify where the update is failing.
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  
  If the problem persists after trying the above solutions, it may be necessary to escalate the issue to your SAP support team or consult with SAP directly for further assistance.