How To Fix CM_EHFND_API_CCI091 - &1: Cannot set "Produce In". Logistics role is not "Produced".

SAP Error Message - Details

• Message type: E = Error

• Message class: CM_EHFND_API_CCI - Messages for chemical compliance view API

• Message number: 091

• Message text: &1: Cannot set "Produce In". Logistics role is not "Produced".

What causes this issue?

You want to set the market coverage to <LS>Produce In</> for country
&V1&. However, you can set <LS>Produce In</> only for objects with the
logistic role <LS>Produced</>.

System Response

The system does not change the market coverage for this country.

How to fix this error?

Select another market coverage for country &V1&. Please note that you
must set at least one market coverage.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CM_EHFND_API_CCI091 - &1: Cannot set "Produce In". Logistics role is not "Produced". ?

  The SAP error message CM_EHFND_API_CCI091 indicates that there is an issue with setting the "Produce In" field in the context of a logistics role that is not designated as "Produced." This error typically arises in the context of SAP's Extended Warehouse Management (EWM) or similar logistics modules where production-related settings are being configured.
  Cause:
  The error occurs when you attempt to assign a production-related attribute (in this case, "Produce In") to a logistics role that does not support production. This can happen due to:
  
  Role Configuration: The logistics role assigned to the material or product does not include production capabilities.
  Data Inconsistency: There may be inconsistencies in the master data or configuration settings that prevent the system from recognizing the role as capable of production.
  Authorization Issues: The user may not have the necessary authorizations to make changes related to production settings.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Role Configuration:
  
  Verify the configuration of the logistics role in the system. Ensure that the role is set up to handle production-related activities.
  If the role should support production, you may need to adjust the configuration settings in the relevant customizing transactions (e.g., SPRO).
  
  
  
  Review Master Data:
  
  Check the material master data to ensure that the correct logistics role is assigned to the material.
  Make sure that the material is correctly classified and that all relevant fields are populated.
  
  
  
  Adjust Production Settings:
  
  If the logistics role is not intended to support production, consider whether you need to change the role or the settings you are trying to apply.
  If necessary, create a new role that includes production capabilities and assign it to the relevant materials.
  
  
  
  User Authorizations:
  
  Ensure that the user attempting to make the change has the necessary authorizations to modify production-related settings.
  Check the user's role assignments and authorization profiles.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for specific guidance on configuring logistics roles and production settings.
  
  
  
  Contact Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support or your internal SAP team for further assistance.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Transaction Codes: Familiarize yourself with transaction codes related to material master maintenance (e.g., MM01, MM02) and role configuration (e.g., PFCG).
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed.
  
  By following these steps, you should be able to identify the root cause of the error and implement a suitable solution.