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: 122
Message text: Delivery request &1: inclusion of change requests finished (&2, &3, &4)
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.
TR_AUSL122
- Delivery request &1: inclusion of change requests finished (&2, &3, &4) ?The SAP error message TR_AUSL122 typically indicates an issue related to the transport request and its associated change requests. This message is often encountered when trying to include change requests in a transport request, and it signifies that the inclusion process has been completed for the specified change requests.
Cause:
- Transport Request Status: The transport request may already be released or completed, which means that no further changes can be included.
- Change Request Status: The change requests you are trying to include may have already been included in another transport request or may be in a status that does not allow them to be included.
- System Configuration: There may be configuration settings in the transport management system that restrict the inclusion of certain change requests.
Solution:
- Check Transport Request Status: Verify the status of the transport request you are working with. If it is already released, you will need to create a new transport request to include additional change requests.
- Review Change Request Status: Check the status of the change requests you are trying to include. If they are already included in another transport request, you will need to either release that transport request or create a new one.
- Use Transaction SE09/SE10: Use transaction codes SE09 or SE10 to manage transport requests and check the status of the change requests. You can also see if the change requests are locked or if there are any other issues.
- Create a New Transport Request: If the current transport request cannot be modified, consider creating a new transport request and including the necessary change requests there.
- Consult with Basis Team: If you are unsure about the transport management settings or if there are system-level issues, consult with your SAP Basis team for assistance.
Related Information:
By following these steps, you should be able to resolve the TR_AUSL122 error and manage your transport requests effectively.
Get instant SAP help. Sign up for our Free Essentials Plan.
TR_AUSL121
Delivery request &1: inclusion of change requests started (&2, &3, &4)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
TR_AUSL120
You can only use a released request/piece list
What causes this issue? The request or piece list &V1& has not been released, which means that you cannot use it for this function. You can u...
TR_AUSL123
Request &1 (type &2) is not assigned to delivery component &3
What causes this issue? Request &V1& is used as a component piece list for the delivery &V4& created in this SAP System. However, the...
TR_AUSL124
&1 (type &2) not released until delivery component &3 released
What causes this issue? You cannot directly release delivery requests of type <ZH>&V2&</>. You release them together with the rel...
Click on this link to search all SAP messages.