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: STC_SC_TASKS - System Copy Task Messages
Message number: 135
Message text: Note down task list run ID &1 for manual import after system copy
You have finished the export phase of a system copy refresh scenario.
The next step is to perform the physical system copy. During this phase
the database content of the system is completely exchanged by content
from another system. This will delete the runtime information for the
system copy refresh scenario as well.
To continue with the system copy refresh scenario after the physical
system copy the runtime information need to be recovered. Therefore the
task list run &V1& has been successfully exported to the file system.
<ZH>Note task list run identifier &V1& down!</>
It is required to import the task list run from the file system after
the physical system copy has been performed. Therefore you need to keep
the identifier of the task list run in mind, see
<DS:TX.STCT_SC_CONFIRM_COPY>task description</> for details.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
STC_SC_TASKS135
- Note down task list run ID &1 for manual import after system copy ?The SAP error message STC_SC_TASKS135 typically occurs during a system copy or system refresh process. This message indicates that there are tasks in the task list that need to be manually imported after the system copy is completed. Here’s a breakdown of the cause, solution, and related information for this error:
Cause:
- System Copy/Refresh: The error arises during a system copy or refresh when certain tasks in the task list cannot be executed automatically.
- Missing Dependencies: There may be dependencies or prerequisites that have not been met, preventing the automatic execution of certain tasks.
- Configuration Issues: There could be configuration issues in the target system that need to be resolved before the tasks can be executed.
Solution:
- Note the Run ID: As indicated in the error message, you should note down the task list run ID (denoted as &1). This ID is crucial for tracking the specific task list that encountered the issue.
- Manual Import: After the system copy is completed, you will need to manually import the tasks associated with the noted run ID. This can typically be done using transaction codes like STC01 (for managing background jobs) or STC02 (for managing task lists).
- Check Logs: Review the logs associated with the task list to identify any specific errors or warnings that may provide more context on why the tasks could not be executed automatically.
- Execute Tasks Manually: If the tasks are identified, you can execute them manually. This may involve running specific reports or transactions that were part of the task list.
- Consult SAP Notes: Check for any relevant SAP Notes that may provide additional guidance or patches related to this error. You can search for notes using the SAP Support Portal.
Related Information:
By following these steps, you should be able to resolve the STC_SC_TASKS135 error and successfully complete the system copy process.
Get instant SAP help. Sign up for our Free Essentials Plan.
STC_SC_TASKS134
No profiles found; check profile directory in file system
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
STC_SC_TASKS133
Could not import instance profile
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
STC_SC_TASKS136
Task list run &1 not exported automatically; perform manual export
What causes this issue? After the export phase of a system copy refresh scenario is finished the corresponding task list run must be exported to the ...
STC_SC_TASKS137
Task list run &1 export file could not be deleted after system copy
What causes this issue? You are performing a system copy refresh scenario and you have confirmed that the physical system copy is completed. Before t...
Click on this link to search all SAP messages.