How To Fix CRM_DPP086 - Starting Index Rebuild in mode &1

SAP Error Message - Details

• Message type: E = Error

• Message class: CRM_DPP - CRM Data Privacy

• Message number: 086

• Message text: Starting Index Rebuild in mode &1

What causes this issue?

The process the rebuild CRM-specific End-of-Purpose relevant data from
CRM business transactions was started. The mode the process is executed
in is &V1&.

System Response

The following modes are available for execution:
1) This opertation mode indicates that the index rebuild should be
performed using a date selection (from and to date). All CRM documents
in the specified date range are determined and processed. Note that this
operation mode is to be used for exceptional cases only. The reason is
that this mode cannot be parallelized in a convienent way in every case.
E.g. if there are a lot of CRM documents for a single day this could
crash as there are too many documents processed at once. The
parallelization is done using packages of document GUIDs and calling
function module CRM_DPP_EOP_INDEX_REBUILD.
2) This operation mode indicates that the index rebuild should be
performed using a partner range. The parallelization is done using
packages of partners and calling function module
CRM_DPP_EOP_INDEX_REBUILD_BP. Note: It is not predictable how many CRM
documents are related to a single partner. Specifying packages that are
too big, i.e. that contain too many partners may result in a very long
runtime of CRM_DPP_EOP_INDEX_REBUILD_BP for a single package.
3) This operation mode indicates that the index rebuild should be
performed using a set of CRM document GUIDs. The parallelization is done
using packages of document GUIDs and calling function module
CRM_DPP_EOP_INDEX_REBUILD.
4) This operation mode indicates that the index rebuild should be
performed using a set of partner IDs. The parallelization is done using
packages of partner IDs and calling function module CRM_
DPP_EOP_INDEX_REBUILD_BP. Note: It is not predictable how many CRM
documents are related to a single partner. Specifying packages that are
too big, i.e. that contain too many partners may result in a very long
runtime of CRM_DPP_EOP_INDEX_REBUILD_BP for a single package.
5) This operation mode indicates that the index rebuild should be
performed using a set of partner GUIDs. The parallelization is done
using packages of partner GUIDs and calling function module
CRM_DPP_EOP_INDEX_REBUILD_BP. Note: It is not predictable how many CRM
documents are related to a single partner. Specifying packages that are
too big, i.e. that contain too many partners may result in a very long
runtime of CRM_DPP_EOP_INDEX_REBUILD_BP for a single package.
6) This operation mode indicates that the index rebuild should be
performed using a set of CRM document GUIDs and these GUIDs should be
determined from the log(s) specified as well as all subsequent logs.
These logs may contain certain messages from a previous index rebuild
run that indicate errors and the necessity to re-process these document
GUIDs. The parallelization is done using packages of document GUIDs and
calling function module CRM_DPP_EOP_INDEX_REBUILD.

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 CRM_DPP086 - Starting Index Rebuild in mode &1 ?

  The SAP error message CRM_DPP086, which indicates "Starting Index Rebuild in mode &1," typically occurs in the context of the SAP Customer Relationship Management (CRM) system when there are issues related to the indexing of data in the system. This message is often associated with the Data Processing Platform (DPP) and can arise during operations that involve data retrieval or processing.
  
  Cause:
  
  Index Corruption: The index used for data retrieval may be corrupted or inconsistent, leading to the need for a rebuild.
  Data Changes: Significant changes in the underlying data (e.g., mass updates, deletions) can necessitate an index rebuild to ensure that the index reflects the current state of the data.
  System Performance: The system may be experiencing performance issues, prompting the need to rebuild indexes to optimize data access.
  
  Configuration Issues: Incorrect configuration settings related to indexing or data processing can trigger this error.
  
  
  Solution:
  
  Rebuild the Index: Follow the prompts in the error message to