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: EARC - IS-U: Archiving
Message number: 389
Message text: No import logs available for the selection criteria
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.
EARC389
- No import logs available for the selection criteria ?The SAP error message EARC389, which states "No import logs available for the selection criteria," typically occurs when you are trying to access import logs in the SAP system, but there are no logs that match the criteria you have specified. This can happen in various contexts, such as during data imports, transport requests, or other operations that generate logs.
Causes:
- No Import Logs Exist: The most straightforward reason is that there are simply no import logs available for the specified selection criteria (e.g., date range, user, or specific transport request).
- Incorrect Selection Criteria: The criteria you are using to filter the logs may be too restrictive or incorrect, leading to no results being returned.
- Log Deletion: Import logs may have been deleted or purged from the system due to retention policies or manual deletion.
- Authorization Issues: You may not have the necessary authorizations to view the import logs, which could lead to the system not displaying any logs even if they exist.
Solutions:
- Check Selection Criteria: Review and adjust the selection criteria you are using to ensure they are correct and not overly restrictive. Try broadening the date range or removing filters to see if any logs appear.
- Verify Log Availability: Confirm that import logs are indeed generated for the operations you are interested in. If you are expecting logs from a recent import, ensure that the import was successful and that logging was enabled.
- Check for Deletion: If you suspect logs may have been deleted, check with your system administrator or the team responsible for system maintenance to see if there are any policies in place that might have led to log deletion.
- Authorization Check: Ensure that you have the necessary authorizations to view import logs. You may need to consult with your SAP security team to verify your access rights.
- Consult SAP Notes: If the issue persists, check the SAP Support Portal for any relevant SAP Notes or updates that might address this specific error message.
Related Information:
SE01
, SE09
, or SE10
for transport management, or SLG1
for application logs.If you continue to experience issues after trying these solutions, consider reaching out to SAP support for further assistance.
Get instant SAP help. Sign up for our Free Essentials Plan.
EARC388
Program stop: Error occurred during deletion from table TEML_EABLCONSHST
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
EARC387
Program stop: Error occurred deleting from the table TEML_MR_IMPLSBL
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
EARC390
Scheduled MR date selection must not be earlier than retent.period (&1)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
EARC391
Deletion was terminated because the runtime restriction has been exceeded
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.