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: TK - Transport Organizer
Message number: 675
Message text: Transport requests with no transport target, and piece lists
The following request types are included under this node:
Transport requests whose transport targets have not yet been specified.
Piece lists (normally have no transport target).
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.
TK675
- Transport requests with no transport target, and piece lists ?The SAP error message TK675 indicates that there are transport requests that do not have a transport target defined. This can occur in the context of SAP transport management when you are trying to manage or release transport requests, and it typically points to a configuration issue or a missing assignment in the transport landscape.
Cause:
- Missing Transport Target: The transport request is created without a defined target system. This can happen if the transport route is not properly configured.
- Transport Layer Issues: The transport layer may not be correctly assigned to the transport request.
- Transport Directory Issues: There may be issues with the transport directory or the transport management system (TMS) configuration.
- Transport Request Type: The type of transport request (e.g., customizing, workbench) may not be compatible with the target system.
Solution:
Check Transport Route Configuration:
- Go to the TMS configuration (transaction code
STMS
).- Verify that the transport routes are correctly defined and that the target systems are assigned to the appropriate transport layer.
Assign Transport Target:
- If the transport request is missing a target, you may need to manually assign a transport target to the request.
- Use transaction
SE09
orSE10
to find the transport request and check its details.Review Transport Layer:
- Ensure that the transport layer is correctly assigned to the transport request. You can check this in the transport request details.
Check Transport Directory:
- Ensure that the transport directory is correctly set up and that there are no issues with the transport files.
- You can check the transport directory settings in transaction
SE03
(Transport Organizer Tools).Recreate Transport Request:
- If the transport request is corrupted or cannot be fixed, consider recreating the transport request and ensuring that it has the correct target system assigned from the beginning.
Consult SAP Notes:
- Check for any relevant SAP Notes that may address this specific error. SAP frequently updates its knowledge base with solutions for known issues.
Related Information:
If the problem persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or reach out to SAP support for further assistance.
Get instant SAP help. Sign up for our Free Essentials Plan.
TK673
Specify at least one request type
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
TK672
System settings only allow &1 as target system
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
TK676
Local change requests
What causes this issue? This node includes Workbench and Customizing requests without a transport target. Any changes that are recorded in these requ...
TK678
Request/task &1 has target repository &2 instead of &3
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.