Do you have any question about this error?
Message type: E = Error
Message class: FZ - Payment Transactions
Message number: 035
Message text: Inconsistency after error; changes not saved cancelled
The processing of a change could not be carried out properly. As a
result, an inconsistency occurred with the data not yet saved.
The consistent situation which existed after the last saving is
restored automatically.
The changes not saved must be entered again.
Error message extract from SAP system. Copyright SAP SE.
FZ035
- Inconsistency after error; changes not saved cancelled ?The SAP error message FZ035 ("Inconsistency after error; changes not saved cancelled") typically occurs in the context of financial transactions, particularly when dealing with payment processing or document posting in SAP. This error indicates that there was an inconsistency detected in the system after an error occurred, and as a result, the changes made during the transaction were not saved.
Causes:
- Data Inconsistency: The error may arise due to inconsistencies in the data being processed, such as missing or incorrect entries in the relevant tables.
- System Errors: A system error or interruption during the transaction processing can lead to this message.
- Authorization Issues: Lack of proper authorizations for the user performing the transaction can also trigger this error.
- Configuration Issues: Incorrect configuration settings in the financial modules can lead to inconsistencies.
- Custom Code: If there are custom enhancements or modifications in the system, they may not handle certain scenarios correctly, leading to this error.
Solutions:
- Check for Data Consistency: Review the data being processed for any inconsistencies. Ensure that all required fields are filled out correctly and that there are no missing entries.
- Transaction Logs: Check the transaction logs for any specific errors that occurred before this message. This can provide insight into what went wrong.
- Reprocess the Transaction: If the error occurred during a specific transaction, try to reprocess it after ensuring that all data is correct.
- Authorization Check: Verify that the user has the necessary authorizations to perform the transaction.
- System Configuration: Review the configuration settings in the relevant financial modules to ensure they are set up correctly.
- Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error. There may be patches or updates available that resolve known issues.
- Debugging: If you have access to debugging tools, you can analyze the program flow to identify where the inconsistency is occurring.
- Contact SAP Support: If the issue persists and cannot be resolved internally, consider reaching out to SAP Support for assistance.
Related Information:
FB50
(G/L Account Document Entry), F-28
(Post Incoming Payments), etc.By following these steps, you should be able to identify the root cause of the FZ035 error and implement a solution to resolve it.
Get instant SAP help. Start your 7-day free trial now.
FZ034
Special G/L transaction for exception list; it cannot be changed
What causes this issue? You want to process a special G/L transaction which is not to be paid but is only to appear in the exception list.System Resp...
FZ033
Account & & is currently blocked; try again later
What causes this issue? If the account is blocked, it is possible to clear open items manually. To avoid manual clearing and a release for payment fo...
FZ036
Do not place the cursor on a line with exceptions
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FZ037
Block key & cannot be set in the payment proposal
What causes this issue? You are using a blocking key which may not be used in the payment proposal.How to fix this error? Choose another blocking ke...
Click on this link to search all SAP messages.