How To Fix /SAPPO/ACR121 - &1: Changed by is set but change time stamp is initial

/SAPPO/ACR121 - Overview

• Message type: E = Error

• Message class: /SAPPO/ACR -

• Message number: 121

• Message text: &1: Changed by is set but change time stamp is initial

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 /SAPPO/ACR121 - &1: Changed by is set but change time stamp is initial ?

  The SAP error message /SAPPO/ACR121 &1: Changed by is set but change time stamp is initial typically occurs in the context of SAP applications that involve change management or document processing, such as SAP Purchase Order (PO) processing or other related modules. This error indicates that there is a discrepancy between the "Changed by" field and the "Change timestamp" field in the database.
  
  Cause:
  
  
  Data Inconsistency: The error usually arises when the system detects that a record has a "Changed by" user but does not have a corresponding "Change timestamp." This inconsistency can occur due to:
  
  Manual data manipulation in the database.
  Incomplete or failed updates during a transaction.
  Issues during data migration or system upgrades.
  Bugs in custom code or enhancements that manipulate these fields.
  
  
  
  System Configuration: Sometimes, the configuration settings in the system may not align properly, leading to this error.
  
  
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check the Database: Investigate the specific