How To Fix MN340 - Subseq. settlement index not maintained for supplier & and purch. org. &

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 340

• Message text: Subseq. settlement index not maintained for supplier & and purch. org. &

What causes this issue?

The indicator "Subsequent settlement index" for the retrospective
compilation of statistics has not been maintained for supplier &V1&
belonging to purchasing organization &V2&.

System Response

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

How to fix this error?

Set the indicator <LS>Subsequent settlement index</> in the supplier
master record (Purchasing data).
Then carry out a recompilation of the statistical structure 'S111'.
The recompilation ensures that all pertinent purchasing documents will
be taken into account in the cumulative business volume statistics.
If you do not carry out this recompilation, the system will take into
account only those documents that already constituted the basis of the
previously existing cumulative business volume figures. You can view
these documents using the <LS>Detailed statement</> function.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message MN340 - Subseq. settlement index not maintained for supplier & and purch. org. & ?

  The SAP error message MN340 indicates that there is an issue with the subsequent settlement index not being maintained for a specific supplier and purchasing organization combination. This error typically arises in the context of purchasing and invoice verification processes, particularly when dealing with subsequent settlement processes such as those related to consignment or subcontracting.
  Cause:
  
  
  Missing Subsequent Settlement Index: The primary cause of this error is that the subsequent settlement index for the specified supplier and purchasing organization has not been maintained in the system. This index is necessary for the system to process subsequent settlements correctly.
  
  
  Configuration Issues: There may be configuration issues in the purchasing organization settings or the vendor master data that prevent the subsequent settlement index from being created or accessed.
  
  
  Data Inconsistencies: There could be inconsistencies in the data related to the vendor or purchasing organization that lead to the inability to find the necessary index.
  
  
  Solution:
  
  
  Maintain Subsequent Settlement Index:
  
  Go to the transaction code MEK1 (Create Subsequent Settlement Index).
  Enter the relevant supplier and purchasing organization details.
  Create the subsequent settlement index if it does not exist.
  
  
  
  Check Vendor Master Data:
  
  Use transaction code XK03 (Display Vendor) to check the vendor master data for the supplier in question.
  Ensure that the vendor is correctly set up for the purchasing organization and that all necessary data is maintained.
  
  
  
  Review Configuration Settings:
  
  Check the configuration settings for the purchasing organization in the SAP system. This can be done through the SPRO transaction (Customizing).
  Navigate to Materials Management > Purchasing > Purchase Order > Subsequent Settlement and ensure that the settings are correctly configured.
  
  
  
  Consult Documentation: If the issue persists, refer to SAP documentation or consult with your SAP support team for further troubleshooting steps.
  
  
  Related Information:
  
  
  Transaction Codes:
  
  MEK1: Create Subsequent Settlement Index
  MEK2: Change Subsequent Settlement Index
  MEK3: Display Subsequent Settlement Index
  XK03: Display Vendor
  
  
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance.
  
  
  User Roles and Authorizations: Ensure that the user has the necessary authorizations to create or modify the subsequent settlement index.
  
  
  By following these steps, you should be able to resolve the MN340 error and maintain the necessary subsequent settlement index for the supplier and purchasing organization in question.