How To Fix CRM_WFD_BOL_GENIL101 - Time allocation type &2 of rule &1 is inconsistent

CRM_WFD_BOL_GENIL101 - Overview

• Message type: E = Error

• Message class: CRM_WFD_BOL_GENIL - WFD BOL GenIL Messages

• Message number: 101

• Message text: Time allocation type &2 of rule &1 is inconsistent

What causes this issue?

In the service arrangements, a time allocation type (<(>&<)>V2&)
was found in the availability rules (<(>&<)>V1&) that is
inconsistent. This can happen if a time allocation type is no longer
defined in Customizing, or if the exception indicator is set for that
time allocation.

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?

Ensure that the Customizing for the time allocation types is consistent.
All allocation types that are used must be maintained, and the exception
indicator should not be set.

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 CRM_WFD_BOL_GENIL101 - Time allocation type &2 of rule &1 is inconsistent ?

  The SAP error message CRM_WFD_BOL_GENIL101 indicates that there is an inconsistency in the time allocation type of a rule in the Business Object Layer (BOL) of the SAP CRM Workflow. This error typically arises when the configuration of the workflow rules does not match the expected settings or when there are discrepancies in the time allocation types defined in the system.
  
  Cause:
  
  Inconsistent Configuration: The time allocation type defined in the workflow rule does not match the expected or valid types in the system.
  Missing or Incorrect Data: There may be missing or incorrect entries in the configuration tables related to time allocation types.
  Custom Development: If there are custom developments or modifications in the workflow, they may not align with the standard configurations.
  Transport Issues: If the workflow configuration was transported from one system to another, there may be inconsistencies due to missing dependencies.
  
  
  Solution:
  
  
  Check Workflow Configuration:
  
  Go to the transaction code SWDD (Workflow Builder) and