How To Fix /BCV/CFG118 - Workbench request not created

SAP Error Message - Details

• Message type: E = Error

• Message class: /BCV/CFG -

• Message number: 118

• Message text: Workbench request not created

Self-Explanatory Message

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.

What else can you do?

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message /BCV/CFG118 - Workbench request not created ?

  The SAP error message /BCV/CFG118 Workbench request not created typically occurs when there is an issue with the transport request creation process in the SAP system. This error can arise due to various reasons, and understanding the cause is essential for finding a solution.
  Causes:
  
  Authorization Issues: The user may not have the necessary authorizations to create a workbench request.
  Transport Directory Issues: Problems with the transport directory or configuration can prevent the creation of requests.
  System Configuration: Incorrect configuration settings in the transport management system (TMS) can lead to this error.
  Transport Layer Issues: The transport layer may not be properly defined or may have issues.
  Client-Specific Settings: The client settings may restrict the creation of workbench requests.
  Transport Request Locking: If there are existing transport requests that are locked or in a problematic state, it may prevent new requests from being created.
  
  Solutions:
  
  Check Authorizations: Ensure that the user has the necessary authorizations to create workbench requests. This can be done by checking the user's roles and authorizations in transaction SU53 or SU01.
  Review Transport Directory: Verify that the transport directory is correctly configured and accessible. You can check the transport directory settings in transaction STMS.
  Check TMS Configuration: Use transaction STMS to review the transport management system configuration. Ensure that the transport routes and layers are correctly set up.
  Client Settings: Check the client settings in transaction SCC4 to ensure that the client allows the creation of workbench requests.
  Unlock Transport Requests: If there are locked transport requests, you may need to unlock them or resolve any issues with them. This can be done using transaction SE01 or SE09.
  System Logs: Check the system logs (transaction SM21) for any related error messages that might provide more context on the issue.
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error or provide additional troubleshooting steps.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as STMS (Transport Management System), SE01 (Transport Organizer), SE09 (Workbench Organizer), and SU53 (Authorization Check).
  SAP Support: If the issue persists, consider reaching out to SAP Support for assistance, especially if it is a recurring problem or if it affects multiple users.
  Documentation: Review SAP documentation related to transport management and workbench requests for more detailed guidance.
  
  By following these steps, you should be able to identify the cause of the /BCV/CFG118 Workbench request not created error and implement a suitable solution.