How To Fix CM_EHFND_CHECK_API006 - Request origin &1 is not supported. Compliance request is not created.

SAP Error Message - Details

• Message type: E = Error

• Message class: CM_EHFND_CHECK_API - Messages related to PMA Compliance Check API

• Message number: 006

• Message text: Request origin &1 is not supported. Compliance request is 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 CM_EHFND_CHECK_API006 - Request origin &1 is not supported. Compliance request is not created. ?

  The SAP error message CM_EHFND_CHECK_API006 indicates that a compliance request could not be created because the request origin specified is not supported. This error typically arises in the context of SAP's Environment, Health, and Safety (EHS) module, particularly when dealing with compliance management.
  Cause:
  The error can occur due to several reasons:
  
  Invalid Request Origin: The request origin specified in the API call is not recognized or is not configured in the system.
  Configuration Issues: The system may not be properly configured to handle the specific request origin.
  Authorization Issues: The user or system may lack the necessary authorizations to create a compliance request for the specified origin.
  Version Compatibility: There may be compatibility issues between the API version being used and the system configuration.
  
  Solution:
  To resolve the error, consider the following steps:
  
  
  Check Request Origin:
  
  Verify the request origin being used in the API call. Ensure that it is a valid and supported origin in your SAP system.
  
  
  
  Configuration Review:
  
  Review the configuration settings in the SAP EHS module to ensure that the request origin is properly set up. This may involve checking customizing settings in transaction codes like SPRO.
  
  
  
  Authorization Check:
  
  Ensure that the user or service account making the API call has the necessary authorizations to create compliance requests. This may involve checking roles and permissions in the user profile.
  
  
  
  Consult Documentation:
  
  Refer to the SAP documentation for the specific version of the EHS module you are using. This can provide insights into supported request origins and any necessary configurations.
  
  
  
  System Logs:
  
  Check system logs (transaction SLG1) for any additional error messages or warnings that may provide more context about the issue.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP Support for further assistance. They can provide insights based on the specific configuration and version of your system.
  
  
  
  Related Information:
  
  SAP Notes: Search for relevant SAP Notes that may address this specific error or provide patches and updates.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  API Documentation: Review the API documentation for the EHS module to understand the expected parameters and supported request origins.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.