Do you have any question about this error?
Message type: E = Error
Message class: FMFG - U.S. Federal Government Message Class
Message number: 070
Message text: Bad date added in customer implementation of BAdI RFFMFG_TREA_OFFSET
You are using BAdI 'RFFMFG_TREA_OFFSET'. The active implementation you
have created is returning a date with an incorrect value.
Error message issued.
Change the BAdI implementation to return a correct value. Correct
values include:
'ZFBDT'
'BUDAT'
'BLDAT'
'CPUDT'.
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.
FMFG070
- Bad date added in customer implementation of BAdI RFFMFG_TREA_OFFSET ?The SAP error message FMFG070, which indicates a "Bad date" in the context of the BAdI (Business Add-In) implementation RFFMFG_TREA_OFFSET, typically arises when there is an issue with date handling in the financial management processes, particularly related to the posting of transactions or offsets in the Funds Management module.
Cause:
- Invalid Date Format: The date being processed may not conform to the expected format or may be outside the acceptable range (e.g., a date in the future or a date that is too far in the past).
- Incorrect Date Logic: The logic implemented in the BAdI might be incorrectly calculating or manipulating dates, leading to an invalid date being generated or used.
- Configuration Issues: There may be configuration settings in the Funds Management module that are not aligned with the date being processed.
- Data Entry Errors: User input errors when entering dates in transactions can also lead to this error.
Solution:
- Check Date Format: Ensure that the date being passed to the BAdI is in the correct format (typically YYYYMMDD) and is valid.
- Review BAdI Implementation: Examine the code in the BAdI implementation RFFMFG_TREA_OFFSET to identify any logic that may be generating or manipulating dates incorrectly. Look for any calculations or conditions that could lead to an invalid date.
- Validate Configuration: Review the configuration settings in the Funds Management module to ensure they are set up correctly and are compatible with the date being processed.
- Test with Different Dates: If possible, test the implementation with various valid dates to see if the error persists, which can help isolate the issue.
- Debugging: Use debugging tools in SAP to step through the BAdI implementation and observe the values being processed, particularly around date handling.
- Consult Documentation: Refer to SAP documentation or notes related to the BAdI RFFMFG_TREA_OFFSET for any known issues or additional guidance.
Related Information:
If the problem persists after following these steps, it may be beneficial to reach out to SAP support for further assistance.
Get instant SAP help. Start your 7-day free trial now.
FMFG069
Accounting document &1 is currently being edited by user &2
What causes this issue? A lock requested by calling an ENQUEUE function module cannot be set up because another SAP transaction is using the lock in ...
FMFG068
New version. Obsolete entries from &1 deleted
What causes this issue? You are running either the FACTS II extract or footnote programs. The program version has been changed.System Response Obsol...
FMFG071
No Treasury Offset Records can be updated for entered 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...
FMFG072
&1 additional records remain on the FACTS II extract table
What causes this issue? You are running the FACTS II extract program for specific selection criterion that does not include &1 records. These rec...
Click on this link to search all SAP messages.