Message type: E = Error
Message class: TK - Transport Organizer
Message number: 132
Message text: Request with this type cannot be created
The request/task cannot be created in the Transport Organizer as the
request type you have selected is unknown to the Transport Organizer.
Your request type is not subject to the automatic number assignment by
this function. The internal function used can only create the following
request types:
local/transportable change request
customizing request
correction
repair
The function terminates.
Where necessary, repeat the function. Use the Transport Organizer
(SE09) to create a new request.
If this error occurs in an application function, send an error message
to the SAP Hotline.
Error message extract from SAP system. Copyright SAP SE.
TK132
- Request with this type cannot be created ?The SAP error message TK132, which states "Request with this type cannot be created," typically occurs in the context of transport requests in the SAP system. This error can arise due to various reasons, and understanding the cause is essential for finding a solution. Here are some common causes and their corresponding solutions: Causes: Incorrect Transport Request Type: The system may be trying to create a transport request of a type that is not allowed for the current operation (e.g., trying to create a customizing request when a workbench request is expected). Authorization Issues: The user may not have the necessary authorizations to create a transport request of the specified type. Transport Layer Configuration: The transport layer may not be correctly configured, or the transport routes may not allow the creation of certain types of requests. System Configuration: There may be system settings or configurations that restrict the creation of certain types of transport requests. Development
Get instant SAP help. Sign up for our Free Essentials Plan.
TK131
& is not a request in this system
What causes this issue? The object cannot be edited as it is locked by project &V1&. Project &V1& does not belong to this system. Onl...
TK130
Object &3 locked for request/task &1 (owner &2)
What causes this issue? The object &V3& cannot be locked to make changes because it is already locked for editing by user &V2& in req...
TK133
Request &1 is currently being edited by user &2
What causes this issue? Request/task &V1& is currently being edited by user &V2& and is therefore locked temporarily (editing lock).S...
TK134
Correction lock cannot be transferred (request & locked)
What causes this issue? The long-term lock (i.e. correction lock) on the object to be deleted could not be transferred to other linked tasks. Reason:...
Click on this link to search all SAP messages.