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

SAP Error Message - Details

• 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 record that is causing the error. You can use transaction codes like SE16 or SE11 to view the relevant database table and check the values of the "Changed by" and "Change timestamp" fields.
  
  
  Update the Record: If you find that the "Change timestamp" is indeed missing, you may need to update the record to include a valid timestamp. This can often be done through a program or transaction that allows you to edit the record.
  
  
  Review Custom Code: If there are any custom developments or enhancements that interact with the affected records, review the code to ensure that it correctly sets both the "Changed by" and "Change timestamp" fields.
  
  
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error. There may be patches or updates available that resolve known issues.
  
  
  System Logs: Review system logs (transaction SLG1) for any additional error messages or warnings that may provide more context about the issue.
  
  
  Contact SAP Support: If the issue persists and you cannot identify the root cause, consider reaching out to SAP Support for assistance. They can provide more detailed guidance based on your specific system configuration and version.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE16 (Data Browser), SE11 (Data Dictionary), and SLG1 (Application Log) for troubleshooting.
  Documentation: Review SAP documentation related to change management and data integrity to understand how these fields are intended to work.
  Testing: If you make changes to resolve the issue, ensure to test thoroughly in a development or quality assurance environment before applying changes to production.
  
  By following these steps, you should be able to identify and resolve the underlying cause of the error message.