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: TR_AUSL - Software Delivery Composer Messages
Message number: 117
Message text: Inclusion of change requests in &1 is scheduled (see log for job &2)
The inclusion of the flagged change requests in the delivery request
&V1& has been scheduled as background job <LB>&V2&</> (ID &V3&) to be
started immediately.
The action continues.
You are notified accordingly once the job <LB>&V2&</> has run
successfully.
You can then display the status of the delivery request &V1& by choosing
<LS>Edit</> -> <LS>Refresh</>.
To display the status of the job <LB>&V2&</>, choose <LS>System</> ->
<LS>Services</> -> <LS>Jobs</> -> <DS:TRAN.SM37>Job overview</> and
enter <LB>&V2&</> as the job name. Choose <PF>Enter</> to display a job
list.
Error message extract from SAP system. Copyright SAP SE.
TR_AUSL117
- Inclusion of change requests in &1 is scheduled (see log for job &2) ?The SAP error message TR_AUSL117 indicates that there is a scheduled job for including change requests in a transport request. This typically occurs when a transport request is being processed, and there are pending change requests that need to be included in that transport request.
Cause:
- Pending Change Requests: The transport request you are trying to work with has pending change requests that have not yet been included.
- Background Job: A background job has been scheduled to include these change requests, which means that the system is currently processing them.
- Locking Mechanism: The transport request may be locked due to the ongoing job, preventing further actions until the job is completed.
Solution:
Check Job Status:
- Go to transaction code SM37 to check the status of the background job mentioned in the error message. Look for the job with the job name specified in the error message (job &2).
- If the job is still running, you may need to wait for it to complete.
Review Job Log:
- Once the job is completed, review the job log for any errors or messages that might indicate issues with including the change requests.
Manual Inclusion:
- If the job has completed successfully and you still face issues, you can manually include the change requests in the transport request using transaction code SE09 or SE10.
- Select the transport request and use the option to include change requests.
Re-schedule Job:
- If the job has failed, you may need to re-schedule it or troubleshoot the underlying issue that caused the failure.
Consult Basis Team:
- If you are unable to resolve the issue, it may be necessary to consult your SAP Basis team for further assistance, especially if there are underlying system issues.
Related Information:
By following these steps, you should be able to resolve the TR_AUSL117 error and successfully manage your transport requests.
Get instant SAP help. Sign up for our Free Essentials Plan.
TR_AUSL116
Exclusion list &1 contains sub-object (&2 &3 &4)
What causes this issue? Exclusion lists can only contain complete objects. Exclusion list &V1& contains the sub-object &V2& &V3&a...
TR_AUSL115
Inclusion of change requests not possible for &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
TR_AUSL118
&3 not possible for delivery &1 of type &2
What causes this issue? Delivery requests of type &V3& are not valid for deliveries of type &V2&. Delivery &V1& is of type &a...
TR_AUSL119
&1 (type &2) has already been created
What causes this issue? Delivery request &V1& (of type &V2&) has already been created.System Response The activity has been cancelle...
Click on this link to search all SAP messages.