How To Fix CM_EHFND_BO_CRQ078 - Reason for request of &1 changed from 'new product' to 'new process'.

CM_EHFND_BO_CRQ078 - Overview

• Message type: E = Error

• Message class: CM_EHFND_BO_CRQ - Messages for Chemical Compliance Request

• Message number: 078

• Message text: Reason for request of &1 changed from 'new product' to 'new process'.

What causes this issue?

A compliance view has been assigned to this request. For manually
created requests and requests created from material master the reason
changes from 'new product' to 'new process' in case the requested
process is not yet assessed in the compliance view.

System Response

The reason for request changed to 'new process'.

How to fix this error?

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

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CM_EHFND_BO_CRQ078 - Reason for request of &1 changed from 'new product' to 'new process'. ?

  The SAP error message CM_EHFND_BO_CRQ078 indicates that there has been a change in the request type for a business object, specifically from 'new product' to 'new process'. This typically occurs in the context of SAP's Enterprise Architecture or Product Lifecycle Management (PLM) modules, where business objects are used to manage product data and processes.
  
  Cause:
  The error is triggered when a request that was initially categorized as a 'new product' is modified to be treated as a 'new process'. This can happen due to various reasons, such as:
  
  User Input Error: A user may have inadvertently changed the request type during data entry or processing.
  System Configuration: Changes in system settings or configurations that affect how requests are categorized.
  Workflow Changes: Modifications in the workflow or business process that dictate how requests should be handled.
  Data Integrity Issues: Conflicts or inconsistencies in the data that lead to a misclassification of the request.
  
  
  Solution:
  To resolve this error, you