Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: IDMX - Localization Mexico - Digital Invoice
Message number: 168
Message text: CFDI: Status records for request &1 does not exist
Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.
To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.
Unfortunately, there isn't any extra information in this error notice.
First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).
Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.
You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.
IDMX168
- CFDI: Status records for request &1 does not exist ?The SAP error message IDMX168, which states "CFDI: Status records for request &1 does not exist," typically occurs in the context of the Mexican CFDI (Comprobante Fiscal Digital por Internet) electronic invoicing process. This error indicates that the system is unable to find the status records for a specific CFDI request identified by the request number (&1).
Cause:
- Missing Status Records: The most common cause of this error is that the status records for the specified CFDI request have not been created or are missing from the database.
- Incorrect Request Number: The request number provided may be incorrect or does not correspond to any existing CFDI request in the system.
- Data Synchronization Issues: There may be issues with data synchronization between different systems or modules within SAP, leading to missing records.
- Processing Errors: There could have been an error during the processing of the CFDI request that prevented the status records from being created.
Solution:
- Verify Request Number: Check the request number you are using to ensure it is correct and corresponds to an existing CFDI request.
- Check Status Records: Use transaction codes like
SCDO
orSCDO2
to check if the status records exist for the given request number. If they do not exist, you may need to reprocess the CFDI request.- Reprocess the CFDI: If the status records are missing, you may need to reprocess the CFDI request. This can often be done through the relevant transaction for generating or sending CFDI documents.
- Review Logs: Check the application logs (transaction SLG1) for any errors or warnings related to the CFDI processing that might provide more context on why the status records are missing.
- Consult Documentation: Review SAP notes or documentation related to CFDI processing for any known issues or additional troubleshooting steps.
- Contact SAP Support: If the issue persists and you cannot resolve it, consider reaching out to SAP support for assistance, especially if this is a recurring issue.
Related Information:
SCDO
, SCDO2
, and others related to electronic invoicing.By following these steps, you should be able to diagnose and resolve the IDMX168 error in your SAP system.
Get instant SAP help. Sign up for our Free Essentials Plan.
IDMX167
CFDI: Request &1 does not exist
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
IDMX166
CFDI: Customer for FI document &1/&2/&3 can not be identified
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
IDMX169
CFDI: Request &1, idoc number for status '&2' could not be identified
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
IDMX170
CFDI: Request &1, idoc &3 for status '&2' could not be read
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.