Do you have any question about this error?
Message type: E = Error
Message class: FICO1 -
Message number: 159
Message text: Dependent dates do not exist
No dependent data exists for an object. This can be because you made
an unpermitted, retroactive change in Customizing to an existing
product that is in use already.
You must delete the object and create it again..
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.
FICO1159
- Dependent dates do not exist ?The SAP error message FICO1159, which states "Dependent dates do not exist," typically occurs in the context of financial accounting and controlling (FICO) when there is an issue with the date dependencies in a financial document or transaction. This error can arise in various scenarios, such as during the posting of documents, creation of invoices, or when executing certain financial reports.
Causes:
Missing Date Dependencies: The error often indicates that the system is unable to find the necessary dependent dates for a transaction. This can happen if the required date fields are not filled in or if there are inconsistencies in the date settings.
Incorrect Configuration: The configuration settings for date dependencies in the financial module may not be set up correctly, leading to this error.
Document Flow Issues: If there are issues in the document flow (e.g., a preceding document that is required for the current transaction is missing or not posted), it can lead to this error.
Data Inconsistencies: There may be inconsistencies in the master data or transaction data that affect the date dependencies.
Solutions:
Check Date Fields: Ensure that all required date fields are filled in correctly. This includes checking the posting date, document date, and any other relevant date fields.
Review Configuration: Verify the configuration settings related to date dependencies in the FICO module. This may involve checking the settings in the Financial Accounting (FI) and Controlling (CO) modules.
Document Flow Review: Check the document flow for the transaction you are trying to post. Ensure that all prerequisite documents are posted and available.
Data Consistency Check: Run consistency checks on the relevant master data and transaction data to identify any discrepancies that may be causing the issue.
Consult SAP Notes: Look for relevant SAP Notes that may address this specific error. SAP frequently releases notes that provide solutions or workarounds for known issues.
Contact Support: If the issue persists after checking the above points, consider reaching out to SAP support or your internal SAP support team for further assistance.
Related Information:
By following these steps, you should be able to identify the cause of the FICO1159 error and implement a solution to resolve it.
Get instant SAP help. Start your 7-day free trial now.
FICO1158
Missing entry in field &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FICO1157
Differentiation value &1 not allowed for differentiation category &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FICO1160
&2: Start date cannot be empty for &1.
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FICO1161
&2: Repetition period cannot be empty for &1.
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.