Do you have any question about this error?
Message type: E = Error
Message class: MN - Message class for subsequent settlement (Purchasing)
Message number: 685
Message text: Subs. sttlmnt indep. of bus. vol. does not permit settlmnt at plant level
Condition type group &V2& includes condition type &V1&. Condition type
&V1& is business volume-independent.
Arrangement type &V3& uses cross-company-code settlement at plant level
(settlement type &V4&).
However, cross-company-code settlement at plant level is not allowed
for condition types that have a rebate dependent on business volume.
Assignment is not possible.
Assign a different arrangement type to condition type &V1&.
You are advised to create separate arrangement types for subsequent
settlement that is independent of business volume.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
MN685
- Subs. sttlmnt indep. of bus. vol. does not permit settlmnt at plant level ?The SAP error message MN685, which states "Subs. sttlmnt indep. of bus. vol. does not permit settlmnt at plant level," typically occurs in the context of settlement processes in SAP, particularly when dealing with internal orders, projects, or cost centers. This error indicates that the system is configured in a way that does not allow for settlement at the plant level due to the settings of the settlement profile or the characteristics of the order or project.
Cause:
- Settlement Profile Configuration: The settlement profile assigned to the order or project may be set to allow settlement only at a higher level (e.g., company code or controlling area) rather than at the plant level.
- Order Type Restrictions: The type of order or project may not support plant-level settlement due to its configuration.
- Business Volume Independence: The error message suggests that the settlement is independent of business volume, which may not align with the plant-level settlement requirements.
- Master Data Settings: The master data for the order or project may not be set up to allow for plant-level settlement.
Solution:
Check Settlement Profile: Review the settlement profile assigned to the order or project. Ensure that it is configured to allow for plant-level settlement if that is required.
- Transaction Code: OPAF (Settlement Profile Configuration)
Review Order Type: Check the characteristics of the order type being used. If it does not support plant-level settlement, consider using a different order type that does.
- Transaction Code: OIOA (Order Type Configuration)
Adjust Master Data: If applicable, modify the master data settings for the order or project to enable plant-level settlement.
- Transaction Code: KO02 (Change Order) or KO03 (Display Order)
Consult Documentation: Review SAP documentation or consult with your SAP support team to understand the implications of changing settlement settings and ensure compliance with your organization's financial processes.
Testing: After making changes, perform a test settlement to ensure that the error is resolved and that the settlement process works as expected.
Related Information:
By following these steps, you should be able to identify the root cause of the MN685 error and implement a solution to allow for successful settlement at the desired level.
Get instant SAP help. Start your 7-day free trial now.
MN684
The business volume data from the user exit is inconsistent
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
MN683
Balance does not equal zero: &1 &2 (internal error)
What causes this issue? A balance of &V1& &V2& occurred. This is probably due to an internal program error. The key fields (Purchasin...
MN686
Condition type &1 is indep. of bus. vol. (no subseq. update of bus. vol.)
What causes this issue? Business volume updating is not required or defined for business-volume- independent condition type (here &V1& for ap...
MN687
No update rules exist at time &1
What causes this issue? There are no update rules at the time &V1& (table TMC2D or TMC2F) for update group &V2&. As the document to b...
Click on this link to search all SAP messages.