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. &
The indicator "Subsequent settlement index" for the retrospective
compilation of statistics has not been maintained for supplier &V1&
belonging to purchasing organization &V2&.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
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.
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
Get instant SAP help. Sign up for our Free Essentials Plan.
MN339
Condition type S000 not maintained in calculation schema &
What causes this issue? Condition type S000 has not been entered in calculation schema &V1& (usage &V2&, application &V3&). C...
MN338
Offsetting of income effected with different account key
What causes this issue? Account key &V1& has been entered against condition type 'S000' (settled income). This differs from account...
MN341
No updating carried out for any condition record of rebate arrangement &
What causes this issue? The rebate income for one or more condition records belonging to rebate arrangement &V1& could not be updated. This i...
MN342
Update data (rebate income) faulty (internal error)
What causes this issue? The update for item &V4& of settlement document &V3& for a condition record of rebate arrangement &V1&...
Click on this link to search all SAP messages.