How To Fix /SAPAPO/OM_SYNC021 - RPM obsolete or RPMCALL started

/SAPAPO/OM_SYNC021 - Overview

• Message type: E = Error

• Message class: /SAPAPO/OM_SYNC -

• Message number: 021

• Message text: RPM obsolete or RPMCALL started

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message /SAPAPO/OM_SYNC021 - RPM obsolete or RPMCALL started ?

  The SAP error message /SAPAPO/OM_SYNC021 typically indicates an issue related to the synchronization of data between the SAP Advanced Planning and Optimization (APO) system and the SAP ERP system. The specific message "RPM obsolete or RPMCALL started" suggests that there is a problem with the Resource Planning Module (RPM) or that a call to the RPM is currently in progress.
  Causes:
  
  Obsolete RPM Data: The RPM data may be outdated or no longer valid, which can occur if there have been changes in the master data or if the planning data has not been updated correctly.
  Concurrent Processes: If there are multiple processes trying to access or modify the RPM data simultaneously, it can lead to conflicts and this error message.
  System 
  Configuration Issues: Incorrect configuration settings in the APO or ERP system can lead to synchronization issues.
  Data Locking: If a process is currently using the RPM data, it may lock the data, preventing