Do you have any question about this error?
Message type: E = Error
Message class: FR - Messages for FI Reporting
Message number: 157
Message text: Last dunning date is later than the current dunning date
Last dunning date lies after the current dunning date. This entry is
not possible.
The selection would have no reasonable output. The entry is not
accepted.
Enter correct last dunning date or cancel processing.
Error message extract from SAP system. Copyright SAP SE.
The SAP error message FR157, which states "Last dunning date is later than the current dunning date," typically occurs in the context of the dunning process in SAP. This error indicates that there is a discrepancy between the last dunning date recorded for a customer and the current dunning date being processed.
Cause:
- Data Entry Error: The last dunning date may have been incorrectly entered or updated in the system.
- System Configuration: There may be issues with the configuration of the dunning program or the dunning levels.
- Dunning Run Sequence: The dunning run may be attempting to process a dunning notice for a date that is earlier than the last dunning date, which is not allowed.
- Manual Changes: If manual changes were made to the dunning dates or related data, it could lead to inconsistencies.
Solution:
- Check Last Dunning Date: Review the last dunning date for the customer in question. This can typically be found in the customer master data or the dunning history.
- Adjust Dunning Dates: If the last dunning date is indeed later than the current dunning date, you may need to adjust the dunning dates accordingly. This can involve:
- Updating the last dunning date to a more appropriate value.
- Ensuring that the current dunning date is set correctly.
- Review Dunning Configuration: Check the dunning configuration settings in the SAP system to ensure they are set up correctly. This includes reviewing the dunning levels and the parameters used in the dunning run.
- Run Dunning Program Again: After making the necessary adjustments, rerun the dunning program to see if the error persists.
- Consult Documentation: Refer to SAP documentation or help resources for specific guidance on dunning processes and error handling.
Related Information:
If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or a technical consultant who can provide more in-depth assistance.
Get instant SAP help. Start your 7-day free trial now.
Feature | Free Access | Free Trial |
---|---|---|
Basic SAP error explanation | ![]() |
![]() |
Step-by-Step Usage Guide | ![]() |
![]() |
Interactive SAP Coach Assistance | ![]() |
![]() |
AI Troubleshooting for T-Code Errors | ![]() |
![]() |
FR156 Only select one function
What causes this issue? No SAPScript form was specified.System Response RFWMAN...
FR155 Select one of the specified functions
What causes this issue? No SAPScript form was specified.System Response RFKQST...
FR158 0 is an invalid entry
What causes this issue? The calculation of the dunning level can only be carrie...
FR159 Account & is not defined for bill liability in comp.code &
What causes this issue? In the payment program configuration, account &V1&a...
SAP messages fall into 3 different categories: Error messages
(message type = E), Warnings (W) or Informational (I) messages.
An error message will prevent you from continuing your work - it is a hard stop and you need to fix the error before you can proceed. A warning message will stop your work, however, you can then bypass the warning by pressing the Enter key on your keyboard. That said, it is still good practice to investigate the cause of the warning message and address it. An information message will not stop your work and is truly just for informational purposes.
Click on this link to search all SAP messages.