Do you have any question about this error?
Message type: E = Error
Message class: DMCLG - DMC Tool Development
Message number: 774
Message text: Job execution has been discontinued on user request
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.
DMCLG774
- Job execution has been discontinued on user request ?The SAP error message DMCLG774 indicates that a job execution has been discontinued due to a user request. This typically means that a user or an administrator has manually stopped or canceled a job that was running in the SAP system.
Cause:
- Manual Cancellation: The most common cause is that a user or administrator has manually canceled the job through the SAP GUI or another interface.
- Job Scheduling Issues: Sometimes, jobs may be canceled due to scheduling conflicts or if they are taking too long to execute.
- Resource Constraints: If the system is under heavy load or if there are resource constraints, a user might decide to cancel a job to free up resources.
- Error Handling: If a job encounters an error and is set to stop on error, it may be canceled by the system or user intervention.
Solution:
- Check Job Status: Use transaction code
SM37
to check the status of the job. Look for any logs or messages that might indicate why the job was canceled.- Review Job Logs: Analyze the job logs for any errors or warnings that might have led to the cancellation.
- Re-run the Job: If the job was canceled unintentionally, you can re-schedule it. Ensure that the conditions for running the job are met.
- Communicate with Users: If the cancellation was intentional, communicate with the relevant users or teams to understand the reason and whether the job needs to be rescheduled.
- Monitor System Performance: If resource constraints are a recurring issue, consider monitoring system performance and optimizing resource allocation.
Related Information:
SM37
: Job MonitoringSM36
: Job SchedulingSM21
: System LogIf the issue persists or if you need further assistance, consider reaching out to your SAP Basis team or SAP support for more in-depth troubleshooting.
Get instant SAP help. Start your 7-day free trial now.
DMCLG773
Sender structure is not a single table; reading type 3 not possible
What causes this issue? Reading type 3 uses function module DB_SETGET to read data from the source system, but this is only possible if the sender st...
DMCLG772
Load of cluster data in the sender system completed on &1 at &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
DMCLG775
Save project &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
DMCLG776
Save subproject &1
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.