How To Fix EHPRC_CPM_CHECK079 - Product part &1 is compliant; binding compliance date is reached

EHPRC_CPM_CHECK079 - Overview

• Message type: E = Error

• Message class: EHPRC_CPM_CHECK - Messages for Checks

• Message number: 079

• Message text: Product part &1 is compliant; binding compliance date is reached

What causes this issue?

You have assigned product part &v1& (specification &v2&) to a binding
compliance date (&v3&) that is entered in the <LS>Compliance Declaration
</> property. This binding compliance date has been reached, the product
is defined as compliant.

System Response

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

How to fix this error?

Check that the compliance declaration is up-to-date and adjust or remove
the binding compliance date that is assigned to product part &v1&
(specification &v2&).
If necessary, ask your supplier for the compliance declaration.

Procedure for System Administrators

INCLUDE EHPRC_CPM_CHECK OBJECT DOKU ID TX
Compliance check 79

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message EHPRC_CPM_CHECK079 - Product part &1 is compliant; binding compliance date is reached ?

  The SAP error message EHPRC_CPM_CHECK079 indicates that a product part is compliant, but the binding compliance date has been reached. This message typically arises in the context of compliance management within SAP, particularly in industries that require adherence to regulatory standards, such as pharmaceuticals or chemicals.
  
  Cause:
  
  Compliance Date Reached: The binding compliance date for the product part has been reached, meaning that the product is now subject to compliance checks or regulations that must be adhered to.
  Regulatory Changes: Changes in regulations or compliance requirements may have occurred, necessitating a review of the product part's compliance status.
  Data Configuration: There may be issues with how the compliance data is configured in the system, leading to the error message being triggered.
  
  
  Solution:
  
  Review Compliance Dates: Check the compliance dates associated with the product part. If the date has indeed been reached, you may need to take action to ensure ongoing compliance.
  Update Compliance Information: If the product