Do you have any question about this error?
Message type: E = Error
Message class: MN - Message class for subsequent settlement (Purchasing)
Message number: 352
Message text: Subseq. settlement indicator for condition granter & cannot be cancelled
Rebate arrangements for which final settlement accounting has not yet
been effected exist for condition granter &V1& (purchasing organization
&V2&). For this reason, the indicator cannot be cancelled.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
If you wish to cancel the "subsequent settlement" indicator, you must
first
delete all rebate arrangements for which no relevant purchasing
documents yet exist
carry out final settlement accounting for all arrangements for which
relevant purchasing documents already exist. You can first set the
deletion indicator for the condition records if no rebate income is to
be settled. Any cumulative provisions for accrued income are dissolved.
You can determine the relevant rebate arrangement numbers using the
function <LS>List rebate arrangements</>. List all arrangements for
condition granter &V1&, purchasing organization &V2&, whose status is
not "Final settlement effected".
You can obtain details on the cumulative supplier business volume data/
purchasing documents via <LS>Detailed statement</> and <LS>Statement of
statistical data</>.
Error message extract from SAP system. Copyright SAP SE.
MN352
- Subseq. settlement indicator for condition granter & cannot be cancelled ?The SAP error message MN352 indicates that there is an issue with the subsequent settlement indicator for a condition granter in the context of a settlement process. This error typically arises in the context of billing or settlement processes in SAP, particularly when dealing with condition records in pricing or rebate agreements.
Cause:
The error message MN352 can occur due to several reasons:
- Subsequent Settlement Indicator: The condition granter (e.g., a vendor or customer) has a subsequent settlement indicator that is set in a way that does not allow for cancellation. This could be due to the configuration of the condition type or the status of the settlement process.
- Status of the Document: The document you are trying to cancel may already be in a status that does not permit cancellation, such as being fully settled or having been processed in a way that locks it for further changes.
- Configuration Issues: There may be configuration settings in the pricing procedure or condition types that are not aligned with the intended use of subsequent settlements.
Solution:
To resolve the MN352 error, you can take the following steps:
Check Condition Records: Review the condition records associated with the condition granter. Ensure that the subsequent settlement indicator is set correctly and that it allows for cancellation.
Review Document Status: Check the status of the document you are trying to cancel. If it has already been fully settled or processed, you may need to reverse or adjust the settlement before you can cancel it.
Configuration Review: Consult with your SAP configuration team to review the settings for the condition types and pricing procedures. Ensure that the subsequent settlement indicators are configured correctly to allow for the desired actions.
Transaction Codes: Use transaction codes like
VK13
(Display Condition) orVK12
(Change Condition) to check and modify the condition records as necessary.Consult Documentation: Refer to SAP documentation or help resources for specific details on the condition types and subsequent settlement indicators.
SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance on resolving it.
Related Information:
VK11
(Create Condition), VK12
(Change Condition), and VK13
(Display Condition) for managing condition records.If the issue persists after following these steps, it may be beneficial to involve your SAP support team or consult with an SAP expert for further assistance.
Get instant SAP help. Start your 7-day free trial now.
MN351
Purchasing document & does not exist in system
What causes this issue? Purchasing document &V1& no longer exists in the system, but is is relevant for a condition record for rebate arrange...
MN350
***** Function group WN06 (detailed statement) *****
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
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...
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&...
Click on this link to search all SAP messages.