Do you have any question about this error?
Message type: E = Error
Message class: CTE_FND_POSTING - ERP - Concur Integration: FIN Postings
Message number: 097
Message text: Number of documents retrieved &1 does not match expected number &2.
You have just tried to retrieve documents in multiple packages so as to
reduce the message size. Unfortunately, we received only &v1& of the
expected &v2& for the current package. Note that due to inconsistency
issues, the received documents will not be stored in the SAP system and
will therefore be retrieved again in the next feedback loop run.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Locating the missing document(s) depends on if you use the middleware or
not.
If you do not use the middleware, please open a ticket with Concur.
If you use the middleware, you can locate the missing document(s) by
comparing what you received with the inbound and outbound logs in the
middleware via the time stamp. If your trace logs are activated, use the
time stamp found in the error message itself. If your trace logs are not
activated, please activate them first and then complete the following
steps to get the time stamp:
Open transaction CTE_MONI.
In the Expense Report row, click on the Failed Objects.
In the Message List, double-click on the message "Json file for document
ID &1 is inconsistent."
In the Detailed View, the time stamp can be found under Created.
Note that the time stamp and the Document ID are necessary to find the
corresponding message in the logs.
Error message extract from SAP system. Copyright SAP SE.
The SAP error message CTE_FND_POSTING097 indicates a discrepancy between the number of documents retrieved during a posting operation and the expected number of documents. This error typically occurs in the context of financial postings, such as during the execution of a batch job or when processing multiple documents in a single transaction.
Cause:
- Data Inconsistency: There may be inconsistencies in the data being processed, such as missing or incomplete documents.
- Configuration Issues: Incorrect configuration settings in the system could lead to mismatches in expected document counts.
- Batch Processing Errors: If the system is processing documents in batches, there may be issues with how the batch is defined or how documents are being retrieved.
- Authorization Issues: Sometimes, the user may not have the necessary authorizations to view or process certain documents, leading to a mismatch in counts.
- System Bugs: There could be bugs or issues in the specific version of SAP being used that affect document retrieval.
Solution:
- Check Document Status: Verify the status of the documents being processed. Ensure that all expected documents are available and in the correct status for processing.
- Review Configuration: Check the configuration settings related to document processing in the relevant modules (e.g., Financial Accounting, Controlling) to ensure they are set up correctly.
- Analyze Batch Jobs: If the error occurs during batch processing, review the batch job logs to identify any issues or errors that occurred during document retrieval.
- User Authorizations: Ensure that the user executing the transaction has the necessary authorizations to access all relevant documents.
- Debugging: If you have access to technical resources, consider debugging the process to identify where the mismatch occurs.
- SAP Notes: Check the SAP Support Portal for any relevant SAP Notes or patches that address this specific error message or related issues.
- Consult Documentation: Review the SAP documentation for the specific module you are working with to understand the expected behavior and any known issues.
Related Information:
By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.
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 | ![]() |
![]() |
CTE_FND_POSTING096 Inconsistent JSON for FI queue document &1. Contact Concur support.
Self-Explanatory Message Since SAP believes that this specific error message is ...
CTE_FND_POSTING095 Please provide a &1 if you want to reverse a document.
Self-Explanatory Message Since SAP believes that this specific error message is ...
CTE_FND_POSTING098 &1 cannot be imported. Please execute the necessary wizards again.
What causes this issue? The document cannot be imported because the system is a...
CTE_FND_POSTING100 No attachments available for &1 &2.
Self-Explanatory Message Since SAP believes that this specific error message is ...
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.