Do you have any question about this error?
Message type: E = Error
Message class: FVD_DEFAULT_OL - Loans Management: Default Application Logic
Message number: 010
Message text: No counter method created in Customizing for dunning procedure &1
A counter method has not been specified for the dunning procedure you
want to use.
The system counts how often a loan is dunned, based on the dunning run,
and increases the counter for a days past due category by one each time.
In this way, the days past due category corresponds to the respective
dunning level that has been entered for the contract.
You can use the following counter methods:
Cumulative method
In the cumulative method, the counter for the corresponding days past
due category is increased by one.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Single methodThe system creates a corresponding entry in the dunning log.
Make the entries required in the Customizing for <LS>Dunning</>.
Error message extract from SAP system. Copyright SAP SE.
FVD_DEFAULT_OL010
- No counter method created in Customizing for dunning procedure &1 ?The SAP error message FVD_DEFAULT_OL010 indicates that there is no counter method created in the Customizing settings for the specified dunning procedure. This error typically arises when you are trying to execute a dunning run or related processes, and the system cannot find the necessary configuration for the dunning procedure you are using.
Cause:
The primary cause of this error is that the dunning procedure specified in the transaction does not have a corresponding counter method defined in the system. Counter methods are used to track the number of dunning notices sent to a customer and are essential for the dunning process to function correctly.
Solution:
To resolve this error, you need to create or assign a counter method for the dunning procedure in the SAP Customizing settings. Here are the steps to do this:
Access Customizing:
- Go to the SAP Easy Access screen.
- Navigate to the following path:
Financial Accounting (New) -> Accounts Receivable -> Dunning -> Dunning Procedure -> Define Dunning Procedure
Select the Dunning Procedure:
- Find the dunning procedure that is causing the error (indicated by &1 in the error message).
- Click on the procedure to edit it.
Define Counter Method:
- In the dunning procedure settings, look for the section related to counter methods.
- If no counter method is assigned, you will need to create a new one or assign an existing one.
- Ensure that the counter method is properly configured with the necessary parameters.
Save Changes:
- After making the necessary changes, save your configuration.
Test the Dunning Run:
- After configuring the counter method, try to execute the dunning run again to see if the error persists.
Related Information:
OBD2
(for defining dunning procedures) and OBD3
(for defining counter methods) to access the relevant configuration screens directly.If you continue to experience issues after following these steps, it may be helpful to consult with your SAP administrator or a functional consultant who specializes in Financial Accounting (FI) to ensure that all necessary configurations are in place.
Get instant SAP help. Start your 7-day free trial now.
FVD_DEFAULT_OL009
Loan & : error writing stop
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FVD_DEFAULT_OL008
Loan & document & item & contains extension to &
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FVD_DEFAULT_OL011
Loan &: It is not possible to update counter for days past due category
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FVD_DEFAULT_OL012
Key date cannot be before last bill date & or last dunning date &
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.