Do you have any question about this error?
Message type: E = Error
Message class: FICO1 -
Message number: 358
Message text: Condition type &1: Data transferred for differentiation is inconsistent
The data transferred from the application for differentiation of
condition type &1 is inconsistent.
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.
FICO1358
- Condition type &1: Data transferred for differentiation is inconsistent ?The SAP error message FICO1358, which states "Condition type &1: Data transferred for differentiation is inconsistent," typically occurs in the context of pricing and condition records in the SAP FICO (Financial Accounting and Controlling) module. This error indicates that there is an inconsistency in the data being transferred for a specific condition type, which can lead to issues in pricing calculations or financial postings.
Cause:
The error can be caused by several factors, including:
- Inconsistent Condition Records: There may be condition records that are not properly maintained or have missing or incorrect data.
- Incorrect Configuration: The configuration settings for the condition type may not be set up correctly, leading to inconsistencies in how data is processed.
- Data Transfer Issues: If data is being transferred from one system to another (e.g., during a migration or integration), there may be issues with the data format or completeness.
- Missing Differentiation Criteria: The differentiation criteria required for the condition type may not be met, leading to inconsistencies in how the system interprets the data.
Solution:
To resolve the FICO1358 error, you can take the following steps:
Check Condition Records:
- Go to the condition records for the specific condition type (using transaction codes like
VK11
for creating orVK12
for changing).- Ensure that all required fields are filled out correctly and that there are no missing or inconsistent entries.
Review Configuration:
- Check the configuration settings for the condition type in the SAP Customizing Implementation Guide (SPRO).
- Ensure that the differentiation criteria and other settings are correctly defined.
Data Consistency Check:
- Run consistency checks on the condition records to identify any discrepancies.
- Use transaction codes like
VK31
to analyze condition records and ensure they are consistent.Analyze Data Transfer:
- If the error occurred during a data transfer, review the data mapping and transformation rules to ensure that all necessary data is being transferred correctly.
- Check for any logs or error messages that may provide additional context on the data transfer process.
Consult Documentation:
- Refer to SAP documentation or notes related to the specific condition type and error message for additional guidance.
Seek Help from SAP Support:
- If the issue persists after checking the above points, consider reaching out to SAP support for further assistance.
Related Information:
VK11
, VK12
, VK31
, and SPRO
for managing condition records and configuration.By following these steps, you should be able to identify and resolve the underlying cause of the FICO1358 error message.
Get instant SAP help. Start your 7-day free trial now.
FICO1357
Condition type &1 not defined in Customizing
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FICO1356
Condition type &1 requires 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...
FICO1359
Condition determination time &1 does not exist for condition type &2
What causes this issue? The application did not transfer a value for the <DS:DE.FICM_DTE_STD_COND_READ>condition determination time</> &a...
FICO1360
Required reference date does not exist
What causes this issue? The application did not transfer a <DS:DE.FICO_OREFSTARTDATE>reference date for the start date</>, even though a ...
Click on this link to search all SAP messages.