Do you have any question about this error?
Message type: E = Error
Message class: FM_EXPLAIN - Explain Dunning Decision
Message number: 017
Message text: Customer &1 does not exist in any of the dunned company codes
Account &v1& does not exist in any of the company codes selected in
payment run &v2& &v3&.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Use the <ls>Individual Dunning Notice</> function of the dunning program
to see if this account can be dunned. Start the <ls>Test run with log</>
.
Error message extract from SAP system. Copyright SAP SE.
FM_EXPLAIN017
- Customer &1 does not exist in any of the dunned company codes ?The SAP error message FM_EXPLAIN017 indicates that the customer specified (denoted by &1) does not exist in any of the company codes that are set up for dunning. This typically occurs during the dunning process when the system is trying to generate dunning notices for customers who have overdue invoices.
Cause:
- Customer Master Data Issues: The customer may not be created in the relevant company codes. Each customer must be set up in the specific company code where the dunning process is being executed.
- Dunning Area Configuration: The dunning area for the customer may not be properly configured, or the customer may not be assigned to a dunning area.
- Inactive Customer: The customer might be marked as inactive or blocked in the system, preventing dunning from being processed.
- Company Code Assignment: The customer may not be assigned to the company code that is being used for dunning.
Solution:
Check Customer Master Data:
- Go to the customer master data (transaction code
FD03
for display).- Verify that the customer exists in the relevant company code.
- If the customer does not exist, create the customer in the appropriate company code using transaction code
FD01
(create) orFD02
(change).Review Dunning Configuration:
- Check the dunning area settings in the configuration (transaction code
OBD2
).- Ensure that the customer is assigned to the correct dunning area.
Check Customer Status:
- Ensure that the customer is not blocked or inactive. You can check this in the customer master data screen.
Company Code Assignment:
- Ensure that the customer is assigned to the correct company code. You can check this in the customer master data under the company code view.
Dunning Run:
- After making the necessary changes, try to execute the dunning run again to see if the error persists.
Related Information:
FD01
: Create CustomerFD02
: Change CustomerFD03
: Display CustomerOBD2
: Dunning Area ConfigurationIf the issue persists after checking the above points, it may be beneficial to consult with your SAP support team or refer to SAP documentation for further troubleshooting.
Get instant SAP help. Start your 7-day free trial now.
FM_EXPLAIN016
Simulation is only possible for customers without a log
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FM_EXPLAIN015
There are no exceptions that meet the selection criteria
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FM_EXPLAIN018
You are not authorized to display exceptions for these company codes
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FM_EXPLAIN019
You are not allowed to call this program directly
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.