How To Fix 6M021 - Change pointers for &1 &2 were skipped.

SAP Error Message - Details

• Message type: E = Error

• Message class: 6M - MDM Messages (Plugin)

• Message number: 021

• Message text: Change pointers for &1 &2 were skipped.

What causes this issue?

Some objects were skipped although they were listed in the change
pointers. The reason is that these objects were never initially
downloaded!

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 6M021 - Change pointers for &1 &2 were skipped. ?

  The SAP error message 6M021 indicates that change pointers for a specific object (identified by &1 and &2) were skipped. This typically occurs in the context of change pointer processing, which is used in SAP to track changes to certain objects for purposes such as data replication or data distribution.
  Cause:
  The error message can be triggered by several factors, including:
  
  Change Pointer Not Active: The change pointer mechanism may not be activated for the specific object type or the relevant configuration settings may not be properly set up.
  Object Not Found: The system may not find the object for which the change pointer is being processed.
  Data Inconsistency: There may be inconsistencies in the data that prevent the change pointer from being processed correctly.
  Authorization Issues: The user or process attempting to process the change pointers may not have the necessary authorizations.
  Technical Issues: There could be underlying technical issues, such as database locks or system performance problems.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check Change Pointer Activation:
  
  Ensure that change pointers are activated for the relevant object type. You can check this in the configuration settings (transaction code SPRO).
  Navigate to the relevant section for change pointers and verify that the settings are correct.
  
  
  
  Review Object Existence:
  
  Verify that the object identified by &1 and &2 exists in the system and is accessible.
  
  
  
  Check Data Consistency:
  
  Run consistency checks on the data related to the object. You can use transaction codes like SE11 to check the database table or SE16 to view the data.
  
  
  
  Review Authorizations:
  
  Ensure that the user or process has the necessary authorizations to process change pointers. You can check this in transaction SU53 or by reviewing the user roles.
  
  
  
  Monitor System Performance:
  
  Check for any performance issues or locks in the system that might be affecting the processing of change pointers. You can use transaction SM12 to check for locks and SM37 to monitor background jobs.
  
  
  
  Reprocess Change Pointers:
  
  If the issue is resolved, you may need to reprocess the change pointers. You can do this using transaction BD21 (for change pointer processing).
  
  
  
  Related Information:
  
  Change Pointers: Change pointers are a mechanism in SAP that allows the system to track changes to specific data objects. They are often used in conjunction with ALE (Application Link Enabling) for data distribution.
  Transaction Codes:
  
  SPRO: Access to the SAP Reference IMG for configuration.
  BD21: Reprocess change pointers.
  SE11: Data dictionary to check table definitions.
  SE16: Data browser to view table contents.
  SM12: Monitor and manage database locks.
  SM37: Monitor background jobs.
  
  
  
  If the issue persists after following these steps, it may be necessary to consult with your SAP Basis or technical team for further investigation.