Message type: E = Error
Message class: MN - Message class for subsequent settlement (Purchasing)
Message number: 882
Message text: No subsequent business volume (documents) exists for document type &2
Translation: &V3& = purchasing documents, supplier billing documents or
settlement documents
For arrangement &V1&, there are no documents of category &V2& (&V3&)
that are to be checked with respect to the subsequent compilation of
statistics.
If you want to carry out recompilation of statistics for an arrangement,
the subsequent business volumes are determined and possibly also updated
in addition to the old documents.
Please look into this matter.
In the case of arrangements for which subsequent compilation of business
volume is not defined (see e.g. indicator in supplier master for
condition granter), this message is of no significance.
In Customizing, you can define that you do not use this document
category at all, or do not use it with subsequent business volume
update.
In this case, the program does not check the document category (improves
performance). In addition, this message is no longer issued.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
<DS:TRAN.WMN9>Set Up Control Table for Subsequent Settlement</>Error message extract from SAP system. Copyright SAP SE.
MN882
- No subsequent business volume (documents) exists for document type &2 ?The SAP error message MN882, which states "No subsequent business volume (documents) exists for document type &2," typically occurs in the context of document flow or business transactions where the system is unable to find related documents for a specified document type. This can happen in various modules, such as Materials Management (MM) or Sales and Distribution (SD).
Cause: Missing Subsequent Documents: The primary cause of this error is that there are no subsequent documents (like invoices, delivery notes, etc.) linked to the specified document type. This could be due to the document not being processed further or being deleted. Incorrect Document Type: The document type specified in the error message may not be valid or may not have any subsequent documents associated with it. Data Inconsistencies: There may be inconsistencies in the database or issues with the document flow that prevent the system from recognizing related documents. Authorization Issues: Sometimes, the user may not
Get instant SAP help. Sign up for our Free Essentials Plan.
MN881
Condition type &1 is not defined in calc. schema &2 (no updating)
What causes this issue? Condition type &V1& is not defined in calculation schema &V2& of the document.System Response There is no su...
MN880
Condition type &1 was removed from calc. schema &2 (no updating)
What causes this issue? Condition type &V1& no longer exists in calculation schema &V2& of the document.System Response Therefore, n...
MN883
Sales document type &1 is defined for SD rebate processing
What causes this issue? In the standard system, sales document category &V1& is defined for SD rebate processing.System Response You can ent...
MN884
Assign supplier billing document types to arrangement type &1 (long text)
What causes this issue? For credit-side settlement, you must assign settlement document types for interim/partial settlement and final settlement to ...
Click on this link to search all SAP messages.