How To Fix MN729 - No update yet carried out for settlement document &1, item &2

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 729

• Message text: No update yet carried out for settlement document &1, item &2

What causes this issue?

Largely similar to MN728 and MN355 (&WHAT_TO_DO&)
Business volumes were not updated for item &V2& of settlement document
&V1&.

System Response

No business volume data was determined for this document. It is possible
that follow-on functions that require correct business volume data for
the condition record are not carried out.

How to fix this error?

In
<DS:GLOS.3526C095AFAB52B9E10000009B38F974>subsequent settlement</>,
business volumes for settlement documents are updated when the document
is released for Accounting.
Please look into this matter. Document &V1& may have to be released to
Accounting so that the business volume data can be updated. It is also
possible that the document could not be released because of an error
(e.g. account determination error).
Note that the business volumes relevant to settlement in the statistics
are currently incorrect. If you carry out, or have carried out,
settlement processing for the condition record in question, it is
possible that settlement contains errors. Therefore, check any
settlement processing that has already been carried out.

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

You can carry out settlement processing again to correct faulty
settlements (if necessary, cancel the settlement document).
If this relates to an interim settlement, business volumes are taken
into consideration in following settlements.
If the arrangement is settled in part at intervals, and final settlement
is defined on the basis of the total business volume (see settlement
type in Customizing), the business volume difference is taken into
account.
You can also ensure that a business volume difference is taken into
account in final settlement by means of a business volume comparison and
reconciliation.
The condition record concerned has (internal) number &V4& and belongs to
arrangement &V3&.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message MN729 - No update yet carried out for settlement document &1, item &2 ?

  The SAP error message MN729 "No update yet carried out for settlement document &1, item &2" typically occurs in the context of settlement processing in SAP, particularly when dealing with internal orders, projects, or other settlement-relevant objects. This error indicates that the system has not yet processed the update for the specified settlement document and item.
  Causes:
  
  Incomplete Settlement Process: The settlement process may not have been completed successfully, leading to the document not being updated.
  Missing Configuration: There may be missing or incorrect configuration settings in the settlement profile or related settings.
  Authorization Issues: The user may not have the necessary authorizations to perform the settlement.
  Technical Issues: There could be technical issues such as database locks or inconsistencies in the data.
  Timing Issues: The settlement document may be in a state where it cannot be processed yet, possibly due to timing or dependencies on other processes.
  
  Solutions:
  
  Check Settlement Status: Verify the status of the settlement document and ensure that it is in a state that allows for updates. You can use transaction codes like KO03 (Display Order) or KOB1 (Order Line Items) to check the status.
  Re-run the Settlement: If the settlement process was interrupted or incomplete, try to re-run the settlement for the document. Use transaction code KO88 (Order Settlement) or the appropriate transaction for your context.
  Review Configuration: Check the configuration settings for the settlement profile and ensure that all necessary settings are correctly defined. This includes checking the assignment of the settlement profile to the relevant objects.
  Check Authorizations: Ensure that the user has the necessary authorizations to perform the settlement. This may involve checking roles and permissions in the user profile.
  Consult Logs: Review the application logs (transaction SLG1) for any additional error messages or warnings that may provide more context about the issue.
  Database Locks: Check for any database locks that may be preventing the update. You can use transaction SM12 to view and manage locks.
  Contact Support: If the issue persists after trying the above solutions, consider reaching out to your SAP support team or consulting SAP Notes for any known issues related to this error message.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as KO03, KO88, KOB1, and SLG1 for monitoring and managing settlement documents.
  SAP Notes: Search for SAP Notes related to error MN729 in the SAP Support Portal for any specific patches or updates that may address this issue.
  Documentation: Review SAP documentation on settlement processes for internal orders or projects to ensure compliance with best practices.
  
  By following these steps, you should be able to diagnose and resolve the MN729 error in your SAP system.