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: NI - Document index processing
Message number: 094
Message text: Run with name & does not exist (see long text)
The purchasing documents already processed are saved under the name of
the program run. If the program is terminated because time is exceeded,
or for any other reason, you can continue processing with the next
document in the sequence. Enter the name of the run, and deselect the
"New run" indicator.
As additional selection parameters (such as document type, document
date, supplier etc.) are not saved, you should enter these as variants.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Check the name entered and the <LS>New run</> indicator.
Error message extract from SAP system. Copyright SAP SE.
NI094
- Run with name & does not exist (see long text) ?The SAP error message NI094 ("Run with name & does not exist (see long text)") typically occurs when you are trying to execute a job or a report that has not been defined or does not exist in the system. This can happen for various reasons, such as the job being deleted, not being scheduled, or the name being entered incorrectly.
Causes:
- Non-existent Job/Report: The job or report you are trying to run has not been created or has been deleted.
- Incorrect Name: There may be a typo or incorrect name in the job/report name you are trying to execute.
- Authorization Issues: You may not have the necessary authorizations to view or execute the job/report.
- Job Scheduling Issues: The job may not have been scheduled properly in the background job management.
Solutions:
- Verify Job/Report Name: Double-check the name of the job or report you are trying to run. Ensure that it is spelled correctly and matches the name in the system.
- Check Job Status: Use transaction code SM37 to check the status of background jobs. Look for the job name and see if it exists or if it has been deleted.
- Create or Schedule the Job: If the job does not exist, you may need to create it using transaction code SM36 (for scheduling background jobs) or ensure that the report is properly defined.
- Check Authorizations: Ensure that you have the necessary authorizations to execute the job/report. You may need to contact your SAP security team if you suspect authorization issues.
- Consult Long Text: The error message may have additional information in the long text. You can view this by clicking on the message or using the transaction code SE91 to look up the message class and find more details.
Related Information:
If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or technical support for further investigation.
Get instant SAP help. Sign up for our Free Essentials Plan.
NI093
No active LIS structures exist for document index
What causes this issue? At the moment, none of the LIS structures are active in the area of indexes for purchasing documents.System Response It does...
NI092
Condition origin not maintained (Please maintain)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
NI095
Report RMEBEIN& was terminated (see list log)
What causes this issue? The purchasing documents contained in the list display have already been processed. You can find the cause of the termination...
NI096
Data does not exist in any version for LIS structure &1
What causes this issue? Updated data (document indexes) do not exist in any version for LIS structure &V1& in the area of automatic document ...
Click on this link to search all SAP messages.