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
No business volume data updated for purchasing document &V1&, item &V2&
as yet.
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.
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 byError message extract from SAP system. Copyright SAP SE.
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:
Get instant SAP help. Sign up for our Free Essentials Plan.
MN354
PO history for purchasing doc. &, item &, does not exist
What causes this issue? A data record belonging to the purchase order history (for a goods receipt, invoice receipt) is missing for item &V2&...
MN353
Item & of purchasing document & does not exist in system
What causes this issue? Purchasing document &V2&, item &V1&, is relevant for the business volume update of a condition record of reba...
MN356
Scope of statement & not defined
What causes this issue? Function module &V2& was invoked in order to list the business volume data at a certain aggregation level, denoted by...
MN357
Drawn condition records missing for purchasing document &, item &
What causes this issue? For the requested function involving the condition record with the internal number &V3&, the system needs the conditi...
Click on this link to search all SAP messages.