How To Fix >4662 - Dunning by collection strategy is active in company code &1

>4662 - Overview

• Message type: E = Error

• Message class: >4 - SAP File Transfer Protocol

• Message number: 662

• Message text: Dunning by collection strategy is active in company code &1

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message >4662 - Dunning by collection strategy is active in company code &1 ?

  The SAP error message 4662 indicates that "Dunning by collection strategy is active in company code &1." This error typically arises when you attempt to perform a dunning run in a company code where dunning by collection strategy is enabled, but the necessary configuration or data is not set up correctly.
  
  Cause:
  
  Dunning Configuration: The company code has been configured to use dunning by collection strategy, but the relevant collection strategy or dunning parameters may not be properly defined.
  Missing Collection Strategy: The collection strategy that is supposed to be used for dunning may not be assigned to the customer accounts or may not exist.
  Inconsistent Data: There may be inconsistencies in the dunning data or settings that prevent the dunning run from being executed.
  
  
  Solution:
  
  
  Check Dunning Configuration:
  
  Go to the dunning configuration settings in SAP (Transaction code: OBD2).
  Verify that the dunning procedure and collection strategy are correctly set up for the company code in question.
  
  
  
  Review