Do you have any question about this error?
Message type: E = Error
Message class: CRM_WEBREQ_CUST - Request Category Customizing and Associated Views
Message number: 035
Message text: No transaction types found
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.
CRM_WEBREQ_CUST035
- No transaction types found ?The SAP error message CRM_WEBREQ_CUST035: No transaction types found typically occurs in the SAP CRM (Customer Relationship Management) system when a user attempts to create or process a web request, but the system cannot find any valid transaction types associated with the request. This can happen for several reasons, and here are some common causes, solutions, and related information:
Causes:
- Missing Configuration: The transaction types may not be configured in the system. This can happen if the necessary settings have not been completed in the customizing settings.
- Authorization Issues: The user may not have the necessary authorizations to access the transaction types.
- Incorrect Settings: The settings for the web request or the CRM system may be incorrectly configured, leading to the inability to find transaction types.
- Data Inconsistency: There may be inconsistencies in the data or missing entries in the relevant tables that define transaction types.
Solutions:
Check Configuration:
- Go to the SAP Customizing Implementation Guide (IMG) and navigate to the relevant section for CRM Web Requests.
- Ensure that transaction types are defined and properly configured. You can check under:
- CRM > Transactions > Define Transaction Types.
- Make sure that the transaction types are active and assigned to the relevant business processes.
Verify Authorizations:
- Check the user roles and authorizations to ensure that the user has the necessary permissions to access the transaction types.
- Use transaction code SU53 to analyze authorization issues after the error occurs.
Check Web Request Settings:
- Review the settings for the web request in the CRM system to ensure that they are correctly set up.
- Ensure that the web request is linked to the appropriate transaction types.
Data Consistency Check:
- Use transaction codes like SE11 to check the relevant database tables for transaction types and ensure that the data is consistent.
- You may also want to run consistency checks or reports to identify any discrepancies.
Consult Documentation:
- Refer to SAP documentation or notes related to CRM web requests and transaction types for any specific guidance or known issues.
Related Information:
If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis or CRM support team for further assistance.
Get instant SAP help. Start your 7-day free trial now.
CRM_WEBREQ_CUST034
View &1 determined by business add-in is not valid; standard view is used
What causes this issue? There is no entry in the validity area of the processed Web request for view &v1& of request category &v2& de...
CRM_WEBREQ_CUST033
Request category group &1 does not exist
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CRM_WEBREQ_CUST036
View &2 for request category &1 not found
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CRM_WEBREQ_CUST040
* Additional messages Customizing request category
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.