How To Fix TK738 - Request cannot be created with this name

SAP Error Message - Details

• Message type: E = Error

• Message class: TK - Transport Organizer

• Message number: 738

• Message text: Request cannot be created with this name

What causes this issue?

You cannot create a request of request type &V2& with the name &V1&.

System Response

The function terminates.

How to fix this error?

If you want to create a piece list (request type F), stick to the
following rules:

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Character 1 - 3: not <LS>SAP</>
Character 4: not <LS>K</>
Character 4 - 5: not <LS>KP</> and not <LS>_P</>
or
Character 1 - 10: valid personal namespace (with delimiter
<LS>/</>)
Other characters: not just blanks
The namespace of the SAPK requests is split up into request types. If
you want to create one of these requests, choose the correct request
type from the following list:
Piece lists for upgrade (request type P)
SAPK<rel><(><<)>a><(><<)>xx>
SAPKI<xxxxx>, SAPKG<xxxxx>,
SAPKP<(><<)>cc><xxx>, where <(><<)>cc> is the country ISO key
SAPKJ<(><<)>pn><xxx>, where <(><<)>pn> is the partner number
SAPKC<nnnn><(><<)>a>
SAPKV<xxxxx>
SAPKB<rel><(><<)>nn>
SAPKL<rel><(><<)>nn>
Piece lists (request type F)
SAPKUD<(><<)>a><rel>
SAPKAA<(><<)>a><rel>, SAPKBB<(><<)>a><rel>, SAPKCC<(><<)>a> <rel>,
SAPKDD<(><<)>a><rel>,
SAPKMM<(><<)>a><rel>, SAPKMC<(><<)>a><rel>
SAPL<(><<)>a><nnnnn>
SAPM<rel>SP<(><<)>x>, SAPM<rel>CL<(><<)>x>
Support Packages/preliminary corrections (request type D)
SAPKA<rel><(><<)>xx>, SAPKB<rel><(><<)>xx>,
SAPKD<rel><(><<)>xx>, SAPKH<rel><(><<)>xx>,
SAPKU<rel><(><<)>xx>, SAPKW<rel><(><<)>xx>,
SAPKY<rel><(><<)>xx>,
SAPKI<xxxxx>, SAPKG<xxxxx>
SAPKP<(><<)>cc><xxx>, where <(><<)>cc> is the country ISO key
SAPKJ<(><<)>pn><xxx>, where <(><<)>pn> is the partner number
where
<(><<)>n> stands for a numeral (0-9)
<(><<)>a> stands for a letter (A-Z)
<(><<)>x> stands for any character
<rel> stands for a valid release of the SAP System.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message TK738 - Request cannot be created with this name ?

  The SAP error message TK738, which states "Request cannot be created with this name," typically occurs when there is an issue with the naming convention or the request type in the Transport Management System (TMS). Here are some common causes, solutions, and related information for this error:
  Causes:
  
  
  Invalid Naming Convention: The name of the transport request may not adhere to the naming conventions set by your organization or SAP standards. For example, it may contain invalid characters or exceed the maximum length.
  
  
  Request Already Exists: A transport request with the same name may already exist in the system, leading to a conflict.
  
  
  Authorization Issues: The user may not have the necessary authorizations to create a transport request with the specified name.
  
  
  System Configuration: There may be configuration issues in the Transport Management System that prevent the creation of requests.
  
  
  Transport Layer Issues: The transport layer might not be correctly configured, or the system might not be assigned to the correct transport layer.
  
  
  Solutions:
  
  
  Check Naming Convention: Ensure that the name of the transport request follows the correct naming conventions. Typically, transport request names start with a prefix (like "K" for customizing requests) followed by a number.
  
  
  Use a Unique Name: If a request with the same name already exists, try using a different, unique name for your transport request.
  
  
  Review Authorizations: Check the user’s authorizations to ensure they have the necessary permissions to create transport requests. You may need to consult with your SAP security team.
  
  
  Check Transport Layer Configuration: Verify that the transport layer is correctly configured in the Transport Management System. You can do this by checking the TMS configuration in transaction STMS.
  
  
  Consult SAP Notes: Look for relevant SAP Notes that might address this specific error. You can search for notes related to transport requests and naming conventions.
  
  
  Restart the Transport Management System: In some cases, restarting the TMS or the SAP system may resolve temporary issues.
  
  
  Related Information:
  
  Transaction Codes: You can use transaction codes like SE09 (for workbench requests) and SE10 (for customizing requests) to manage transport requests.
  SAP Documentation: Refer to the official SAP documentation for guidelines on transport management and naming conventions.
  SAP Community: The SAP Community forums can be a valuable resource for finding solutions to specific errors and issues encountered by other users.
  
  If the issue persists after trying the above solutions, it may be beneficial to contact SAP support for further assistance.